[JBoss JIRA] (JBIDE-15936) Application wizard: should only show gear sizes appropriate for the selected domain
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15936?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-15936:
----------------------------------------
Sprint: Sprint Beta2 CF
> Application wizard: should only show gear sizes appropriate for the selected domain
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-15936
> URL: https://issues.jboss.org/browse/JBIDE-15936
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Michelle Murray
> Labels: application_wizard
> Fix For: 4.2.x
>
>
> in the openshift application wizard, I selected a domain. The gear profile field shows three sizes but only small is allowed for the domain I have. If I am a user who doesn't know this I might select medium but then only after three pages of wizard, when trying to create app, does it tell me:
> {noformat}Could not create application "MyApp"
> Could not request https://openshift.redhat.com/broker/rest/domain/myjbdsdomain/applications...: App gear sizes: medium is not valid for this domain. Allowed sizes: small.{noformat}
> If I click Back to change the gear profile, all of the info is removed from the wizard and I have to input it all again. Frustrating. See JBIDE-14002.
> The openshift application wizard could be improved to only show appropriate gear sizes for the selected domain.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-13162) Cannot deploy dynamic web project to OpenShift without a web.xml
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13162?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-13162:
----------------------------------------
Sprint: Sprint Beta2 CF
> Cannot deploy dynamic web project to OpenShift without a web.xml
> ----------------------------------------------------------------
>
> Key: JBIDE-13162
> URL: https://issues.jboss.org/browse/JBIDE-13162
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift, upstream
> Affects Versions: 4.0.0.CR1
> Reporter: Stefan Bunciak
> Fix For: 4.2.x
>
>
> Dynamic web project should should be deployable to OpenShift (is visible when merging OpenShift application and the workspace project).
> After publishing, following output is returned from server:
> {code}
> [INFO] Packaging webapp
> [INFO] Assembling webapp [dw] in [/var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/target/dw]
> [INFO] Processing war project
> [INFO] Webapp assembled in [19 msecs]
> [INFO] Building war: /var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/deployments/ROOT.war
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 33.330s
> [INFO] Finished at: Tue Nov 27 11:27:40 EST 2012
> [INFO] Final Memory: 8M/169M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.1.1:war (default-war) on project dw: Error assembling WAR: webxml attribute is required (or pre-existing WEB-INF/web.xml if executing in update mode) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> hot_deploy_added=false
> Found 127.3.36.1:8080 listening port
> /usr/libexec/openshift/cartridges/abstract/info/lib/util: line 992: /var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/.openshift/action_hooks/post_start_jbossas-7: Permission denied
> Failed to start jbossas-7
> {code}
> Shouldn't this be a part of openshift maven profile?
> {code}
> <failOnMissingWebXml>false</failOnMissingWebXml>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-11903) Explorer: add Application start/stop/restart
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11903?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-11903:
----------------------------------------
Sprint: Sprint Beta2 CF
> Explorer: add Application start/stop/restart
> ---------------------------------------------
>
> Key: JBIDE-11903
> URL: https://issues.jboss.org/browse/JBIDE-11903
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta2
> Environment: Eclipse plugin
> Reporter: Nam Duong
> Labels: explorer, new_and_noteworthy
> Fix For: 4.2.x
>
>
> The OpenShift Console view should contain controls for application start|stop|restart to match the functionality of the CLI. Currently, if you select Window->Show View->Others->OpenShift Express Console, then login in and select an application. The right-click menu doesn't have start|stop|restart so users have to either install the rhc client tools or ssh onto the OpenShift host gear.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBDS-2838) OpenShift Usability
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2838?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2838:
--------------------------------------
Sprint: Sprint Beta2 CF
> OpenShift Usability
> -------------------
>
> Key: JBDS-2838
> URL: https://issues.jboss.org/browse/JBDS-2838
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: openshift, requirements
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.GA
>
>
> This task is to explore the overall usability of the OpenShift Wizard, OpenShift Explorer, the adapter in the Servers Tab and review things like Run As on OpenShift (JBIDE-16069)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBDS-2776) Support quickstarts in OpenShift UI
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2776?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2776:
--------------------------------------
Sprint: Sprint Beta2 CF
> Support quickstarts in OpenShift UI
> -----------------------------------
>
> Key: JBDS-2776
> URL: https://issues.jboss.org/browse/JBDS-2776
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: openshift, requirements
> Affects Versions: 7.0.0.GA
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: QE_JBDS80_needinfo
> Fix For: 8.0.0.GA
>
> Attachments: new-application-2.png
>
>
> OpenShift offers a comprehensive list of available cartridges and quickstarts In the Web-UI:
> !new-application-2.png!
> JBoss Tools/JBDS should offer the same to provide a smoother experience for newbie users.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-14744) Allow users to choose from quickstarts/templates when creatingApplication wizard: new application
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14744?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-14744:
----------------------------------------
Sprint: Sprint Beta2 CF (was: Sprint to Beta1 CF)
> Allow users to choose from quickstarts/templates when creatingApplication wizard: new application
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14744
> URL: https://issues.jboss.org/browse/JBIDE-14744
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: application_wizard
> Fix For: 4.2.0.Beta2
>
> Attachments: 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.png, alternative-cartridges.png, crobson_2014-01-28 16.11.bmml, crobson_2014-01-28 16.11.bmml, crobson_2014-01-28 16.11.png, openshift-quickstart.png, promoted-quickstarts.json, quickstarts.json
>
>
> The web ui offers a large set of quickstarts/templates:
> !openshift-quickstart.png!
> in a mail from clayton on the 4th of june:
> {quote}
> For QuickStarts, brokers may choose to
> a) enable community quickstarts
> (the URL you saw below, set by COMMUNITY_QUICKSTART_URL being a URL in /etc/openshift/broker.conf)
> b) enable their own list of quickstarts
> (a different url, /broker/rest/quickstarts, configured from /etc/openshift/quickstarts.json)
> c) disable the quickstarts link
> (delete /etc/openshift/quickstarts.json)
> To correctly fetch the quickstarts for a server, retrieve the API document
> /broker/rest/api
> and look for the LIST_QUICKSTARTS link. If it is present, you may retrieve quickstarts. If it is absent, you should assume there are no quickstarts.
> Retrieving the list of quickstarts, unlike other REST API feed calls, is very specific:
> * API versioning is not supported
> * Only JSON is supported
> * The body of the response is slightly different than standard REST API feed results
> * If you encounter a parse error or an unexpected data value you are required to handle it gracefully by omitting the entry - the API may change without warning (although hopefully not)
> The format of the JSON response (in either a) or b) above) is:
> {quote}
> {code}
> {
> data: [
> quickstart: {
> id: "<string id>",
> href: "<absolute URL to a display URL for the quickstart>",
> name: "<name>",
> updated: "<last update date in seconds from the epoch>",
> summary: "<brief HTML body of the item>",
> body: "<full HTML body of the item>",
> cartridges: "<cartridge spec>",
> website: "<URL of metadata about the source of the quickstart or the technology>",
> tags: "<comma delimited list of tags>",
> language: "<display name of the type of quickstart>",
> initial_git_url: "<absolute URL or Git reference to source>",
> provider: "openshift|reviewed|partner|community", # default is community
> },
> ]
> }
> {code}
> {quote}
> You should assume that arbitrary content could be injected into any of these fields and defend yourself against XSS appropriately. You should also assume that the structure could be changed at any time.
> Cartridge spec:
> The cartridge spec is defined as either:
> a) a comma delimited list of cartridge name search conditions
> b) a string containing a JSON array
> If the leading character of the cartridge spec is '[', you must convert the cartridge spec to JSON and submit the value provided to the server on creation as the "cartridges" field.
> Otherwise,
> 1) split the string by "," into "segments"
> 2) trim whitespace from each segment
> 3) split each segment by "|" into "matches" - these represent logical ORs
> 4) strip leading and trailing "*" characters
> 5) For each segment, return all cartridges that have a case-insensitive substring match on any of the "matches" in that segment for the user to select.
> See https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea...
> and https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea...
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-15897) Make all relevant OpenShift Explorer actions available from Server Adapter
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15897?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-15897:
----------------------------------------
Sprint: Sprint Beta2 CF (was: Sprint to Beta1 CF)
> Make all relevant OpenShift Explorer actions available from Server Adapter
> --------------------------------------------------------------------------
>
> Key: JBIDE-15897
> URL: https://issues.jboss.org/browse/JBIDE-15897
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Max Rydahl Andersen
> Fix For: 4.2.0.Beta2
>
> Attachments: explorer-context-menu.png, server-adapter-context-menu.png
>
>
> JBIDE-11841 was done earlier but only added the missing actions - when new actions are added we tend to forget to add them.
> Explorer:
> !explorer-context-menu.png!
> Server adapter:
> !server-adapter-context-menu.png!
> We should make it so these actions (when relevant) gets added to both places (openshift explorer / server adapter) and optimally also available in an OpenShift context menu on a project.
> Meaning you don't have to navigate to explorer view constantly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months