]
Rodney Russ commented on JBDS-3256:
-----------------------------------
Understood, [~kconner], thanks. What would be the best way for us to follow what images
will be available and the schedule around that?
[~burrsutter] my assumption is that you would just like JBDS to provide access to the
images that CE is creating (e.g. what Kevin mentions above) which means no WildFly.
JBoss specific Docker Tooling (Basic Integration)
-------------------------------------------------
Key: JBDS-3256
URL:
https://issues.jboss.org/browse/JBDS-3256
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: openshift, requirements
Reporter: Burr Sutter
Assignee: Xavier Coulon
Attachments: multiview_properties_docker_idea.bmml,
multiview_properties_docker_idea.png
Goal: to allow the Eclipse user to easily discover, pull, run, deploy my .war or .ear to
it, stop, commit, push for docker images/containers.
Expected end-user flow 1:
0) Installation - assumes boot2docker pre-installed on the end-user's machine
1) I, the Java developer, need to browse a docker registry (either DockerHub or private
registry), identify the image that I wish to have local and download (docker pull) for
that image+tag.
2) Assumption: the docker image includes not only the operating system + JVM but also the
EAP, Wildfly or Tomcat installed in a 'known' location.
3) I start (docker run) the image which auto-starts the embedded app server
4) I can then deploy my .war or .ear to the running app server
5) I can restart the running app server in debug mode and run the debugger
6) I can undeploy and redeploy my .war or .ear
7) I can stop/restart the running, embedded app server
8) I can then commit (docker commit)
9) then I can publish my changes (docker push)