[
https://issues.jboss.org/browse/JBIDE-20402?page=com.atlassian.jira.plugi...
]
Jeff Cantrill updated JBIDE-20402:
----------------------------------
Description:
To make this happen we will need docker tooling to provide:
* ports
* env variables
* volumes
A user will 'deploy to openshift'...I think they might see portions of the
'run image..' menus that are attached but not all. The workflow would be:
* Ask user about ports, additional env besides those already provided in the image,
volumes,
* Ask about # of replicas, triggers
* push image to OS registry if
** image is not currently in Dockerhub
** OS registry has a route (this we might have to ask about. fail if it doesnt exist? )
* create an ImageStream for the selected image
* create a deploymentConfig for the selected image
* create a service for the image
* optionally create a route
Consider running oc new-app on an image to see what it generates
==================================================================
It's possible to contribute a new menu/handler to the Docker Tooling Images view.
We'd like to be able to select a Docker image from the Docker tooling view,
right-click on it and the "Deploy to Openshift"
The following infos are required to actually be able to deploy the selected image onto
OS:
- the local docker registry. OS will need a route to be able to access it
- the docker hub registry
- environment variables
- ports
- volumes
The docker tooling code is available at :
http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git
The IDockerImage is accessible from the image view :
http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Example of menu contribution:
http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Currently the search image wizard is not reusable (internal package), if needed, this will
require exposing it in Docker tooling for Mars SR1
was:
To make this happen we will need docker tooling to provide:
* ports
* env variables
* volumes
A user will 'deploy to openshift'...I think they might see portions of the
'run image..' menus that are attached but not all. The workflow would be:
* Ask user about ports, additional env besides those already provided in the image,
volumes,
* Ask about # of replicas, triggers
* push image to OS registry if
** image is not currently in Dockerhub
** OS registry has a route (this we might have to ask about. fail if it doesnt exist? )
* create an ImageStream for the selected image
* create a deploymentConfig for the selected image
* create a service for the image
* optionally create a route
==================================================================
It's possible to contribute a new menu/handler to the Docker Tooling Images view.
We'd like to be able to select a Docker image from the Docker tooling view,
right-click on it and the "Deploy to Openshift"
The following infos are required to actually be able to deploy the selected image onto
OS:
- the local docker registry. OS will need a route to be able to access it
- the docker hub registry
- environment variables
- ports
- volumes
The docker tooling code is available at :
http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git
The IDockerImage is accessible from the image view :
http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Example of menu contribution:
http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Currently the search image wizard is not reusable (internal package), if needed, this will
require exposing it in Docker tooling for Mars SR1
Contribute "Deploy to Openshift" menu in Docker Tools'
Image view
-----------------------------------------------------------------
Key: JBIDE-20402
URL:
https://issues.jboss.org/browse/JBIDE-20402
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.3.0.Beta2
Reporter: Fred Bricon
Assignee: Andre Dietisheim
Labels: openshift_v3
Fix For: 4.3.0.CR1
Attachments: deployment_config.json, run image - screen 1.png, run image 2.png
To make this happen we will need docker tooling to provide:
* ports
* env variables
* volumes
A user will 'deploy to openshift'...I think they might see portions of the
'run image..' menus that are attached but not all. The workflow would be:
* Ask user about ports, additional env besides those already provided in the image,
volumes,
* Ask about # of replicas, triggers
* push image to OS registry if
** image is not currently in Dockerhub
** OS registry has a route (this we might have to ask about. fail if it doesnt exist? )
* create an ImageStream for the selected image
* create a deploymentConfig for the selected image
* create a service for the image
* optionally create a route
Consider running oc new-app on an image to see what it generates
==================================================================
It's possible to contribute a new menu/handler to the Docker Tooling Images view.
We'd like to be able to select a Docker image from the Docker tooling view,
right-click on it and the "Deploy to Openshift"
The following infos are required to actually be able to deploy the selected image onto
OS:
- the local docker registry. OS will need a route to be able to access it
- the docker hub registry
- environment variables
- ports
- volumes
The docker tooling code is available at :
http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git
The IDockerImage is accessible from the image view :
http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Example of menu contribution:
http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Currently the search image wizard is not reusable (internal package), if needed, this
will require exposing it in Docker tooling for Mars SR1
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)