[jbosstools-issues] [JBoss JIRA] (JBDS-3250) Support for OpenShift 3 with Docker and Kubernetes

[CDW Engine (JIRA)]

     [ https://issues.jboss.org/browse/JBDS-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

CDW Engine reassigned JBDS-3250:
--------------------------------



> Support for OpenShift 3 with Docker and Kubernetes
> --------------------------------------------------
>
>                 Key: JBDS-3250
>                 URL: https://issues.jboss.org/browse/JBDS-3250
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Epic
>          Components: openshift, requirements
>            Reporter: Max Rydahl Andersen
>            Assignee: Andre Dietisheim
>             Fix For: 9.0.0.GA
>
>
> Copied from JBDS-3278:
> As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, etc. for applications targeting the v3 API. 
> The UI for OpenShift Explorer will need to be expanded (or replaced) to handle  v3's new terminology and architecture.
> For June @Burr tells us to implement (Mail "Forget everything you know about OpenShift"):
> {quote}
> It could be as simple as…somewhere in OpenShift v3 is the git URL to a source repo….
> Our Eclipse end-user needs to be able to “browse” for it and select it
> git clone it
> make changes
> git push it back
> {quote}
> This gives us 3 main use cases (as in mail and chats):
> # Import existing OpenShift project (JBDS-3297)
> # Push Changes to Existing OpenShift project (JBDS-3298)
> # New Project from Template (template should have a default buildconfig, deployconfig and docker image) (JBDS-3306)
> {quote}
> Use Case #1 assumes a TON about what has happened before me. 
> - Assumes that OpenShift Enterprise is installed, configured and running happily at an accessible URL
> - Assumes end-user is already logged in (there is no auth method at this time)
> - Assumes that someone else (not our eclipse end-user) has manually created his/her “project” with an image, a git repo, a deployment config, a build config, defined routes, defined services, etc.
> {quote}
> We have a more extensive document that outlines the usecases:
> https://docs.google.com/a/redhat.com/document/d/1VwYNuKWUzuorU-6GcF420Vl_YjkfzdRxRxl3XeevphM/edit#
> {quote}
> These are features/capabilities currently NOT planned for OpenShift v3's Eclipse Tooling:
> 1) Create SSH Keys
> 2) Upload SSH Keys
> 3) Create Domain
> 4) Add a database, message broker, cache (embeddable cartridge)
> 5) Show In Web Browser
> 6) Review Env Vars
> 7) Edit Env Vars
> 8) Review Logs
> 9) Log Streaming
> 10) SSH in
> 11) Delete/Destroy
> 12) Remote Debugging (though that might "just work")
> 13) Snapshot creation
> 14) Snapshot restore
> 15) Port Forwarding
> 16) Marker Files
> 17) Node.js
> 18) PHP
> 19) Python
> 20) C++
> 21) Perl
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)