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

[Fred Bricon (JIRA)]

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

Fred Bricon resolved JBDS-3250.
-------------------------------
    Fix Version/s: 9.0.0.CR1
                       (was: 9.0.0.GA)
       Resolution: Done


I guess we can consider this Epic done. The following features have been implemented:
* JBIDE-19009 As a user, I want to create OpenShift resources from a template
* JBIDE-19010	 As a user, I want to create OpenShift resources that support an existing “deployment” that does not require source code from a template	
* JBDS-3297	Download/Import Existing OpenShift Project
* JBIDE-19008	 As a user, I want to delete OpenShift resources
* JBDS-3306	Create Deployment from Template
* JBIDE-19001	As a user I want to create an Eclipse project from an OpenShift build config
* JBDS-3298	Push changes to Existing OpenShift Project
* JBIDE-18999	 As a user I want to connect to a v3 OpenShift instance 
* JBIDE-19000	 As a user I want to browse the resources for my projects
* JBIDE-19006	As a user, I want to display details about an OpenShift resource
* JBDS-3278	OpenShift v3
* JBIDE-19007	 As a user, I want to retrieve the build hook URL for a build config so I can configure my git repo to trigger a build on commit
* JBIDE-19035 Fix Connection refactor to support v2 and v3 connections
* JBIDE-19048  separate the v2 from the v3 code, move it to new v3 plugins
* JBIDE-19162	 add new plugins to openshift pom and create feature
* JBIDE-19252	 merge v3 branch into master
* JBIDE-19274	 Make sure/verify OpenShift v3 tooling can be installed in binary form
* JBIDE-19787 As a user I want to import existing OpenShift projects into my Eclipse workspace
* JBIDE-19849	 As a user I want to easily show my (v3) application in a browser

Not done: 
* JBDS-3130 [RFE] Add tooling to manage openshift databases	Enhancement	
* JBIDE-18739	 Support for easy management/start/stop of Vagrant machines
* JBDS-3489	Publishing existing eclipse project to OpenShift

> 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.CR1
>
>
> 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.4.11#64026)