[jbosstools-issues] [JBoss JIRA] (JBIDE-21376) Application wizard: should allow to create an app from an image (currently only from template)
Andre Dietisheim (JIRA)
issues at jboss.org
Wed Jan 6 13:40:00 EST 2016
[ https://issues.jboss.org/browse/JBIDE-21376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145583#comment-13145583 ]
Andre Dietisheim edited comment on JBIDE-21376 at 1/6/16 1:39 PM:
------------------------------------------------------------------
We discussed how to provide this given the timely constraint we currently have. We currently also cannot provide a way for the user to create an app based on wildfly given we dont support app creation via images currently.
We saw 5 different options:
{quote}
1) Use server side template
Pros:
* Works today
Cons:
* requires server side setup of templates
** (e.g. pushing builder image up, possibly pushing template up)
* We (jbossteam?) need to write and maintain template
2) Use server side image (conceptually create a template based on builder image + github info)
(mimicking webconsole)
Pros:
* Will not require custom template setup on server side
Cons:
* needs new UI/workflow in New App to mimic webconsole
3) Use eclipse side template
Pros:
* will work without server side setup
* faster to implement
Cons:
* fragile (requires specific builder images we rely on)
* add custom logic for UI/workflow in "create from source"
* Won't be (immediatly) visibile in eclipse
4) Create eclipse side templates based on server side builder images
Pros:
* will not require custom additional UX flow (or will it?)
Cons:
* will have to hardcode services/routes
5) rely on serverside new-app feature
Pros:
* no custom logic (we think)
Cons:
* don't know when
{quote}
We decided to go for now for eclipse side templates in a 1st step (*3*) since this is the option with the least effort.
was (Author: adietish):
We discussed how to provide this given the timely constraint we currently have. We currently also cannot provide a way for the user to create an app based on wildfly given we dont support app creation via images currently.
We saw 5 different options:
{quote}
# Use server side template
Pros:
* Works today
Cons:
* requires server side setup of templates
** (e.g. pushing builder image up, possibly pushing template up)
* We (jbossteam?) need to write and maintain template
# Use server side image (conceptually create a template based on builder image + github info)
(mimicking webconsole)
Pros:
* Will not require custom template setup on server side
Cons:
* needs new UI/workflow in New App to mimic webconsole
*
# Use eclipse side template
Pros:
* will work without server side setup
* faster to implement
Cons:
* fragile (requires specific builder images we rely on)
* add custom logic for UI/workflow in "create from source"
* Won't be (immediatly) visibile in eclipse
# Create eclipse side templates based on server side builder images
Pros:
* will not require custom additional UX flow (or will it?)
Cons:
* will have to hardcode services/routes
# rely on serverside new-app feature
Pros: no custom logic (we think)
Cons: don't know when
{quote}
We decided to go for now for eclipse side templates in a 1st step (*3*) since this is the option with the least effort.
> Application wizard: should allow to create an app from an image (currently only from template)
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-21376
> URL: https://issues.jboss.org/browse/JBIDE-21376
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Xavier Coulon
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: Screenshot 2015-12-21 16.44.02.png, Screenshot 2015-12-21 16.44.24.png, Screenshot 2015-12-21 18.06.40.png
>
>
> The application wizard in the Eclipse tooling currently only allows to create application from templates. The web console additionally allows creating from images and git source.
> One can see the difference when comparing the listing of options in Eclipse vs the listing in the web console (which also includes images):
> {quote}
> Running OpenShift using our openshift-vagrant box, I can see different proposals between the web console and the Eclipse tooling when adding an application in a project. For example, {{jboss-eap64-openshift:1.1}} is not proposed in the Eclipse tooling.
> See attached screenshots.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list