[ https://issues.jboss.org/browse/JBIDE-9927?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-9927: ----------------------------------------- service#listEmbeddableCartridges and user#getEmbeddableCartridges is implemented, tested and committed. The next step now is to embed a cartridge to an application. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9927?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-9927 at 11/12/11 9:00 AM: ------------------------------------------------------------------- {code} OpenShiftService#listEmbeddableCartridges {code} and {code} User#getEmbeddableCartridges {code} are implemented, tested and committed (see https://github.com/adietish/openshift-java-client/commit/0c0cafc9092cb5ad...) The next step now is to embed a cartridge to an application. was (Author: adietish): {code} OpenShiftService#listEmbeddableCartridges {code} and {code} User#getEmbeddableCartridges {code} are implemented, tested and committed. The next step now is to embed a cartridge to an application. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9927?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-9927 at 11/12/11 9:06 AM: ------------------------------------------------------------------- {code} OpenShiftService#listEmbeddableCartridges {code} and {code} User#getEmbeddableCartridges {code} are implemented, tested and committed (see https://github.com/adietish/openshift-java-client/commit/0c0cafc9092cb5ad...) The next step now is to embed a cartridge to an application. * Embedding is done via rhc-ctl-app in the rhc cli tools: https://github.com/openshift/os-client-tools/blob/master/express/bin/rhc-... The logic is the the main RHC class: https://github.com/openshift/os-client-tools/blob/master/express/lib/rhc-... * rhc-create-app also has an option to create and embed: https://github.com/openshift/os-client-tools/blob/master/express/bin/rhc-... was (Author: adietish): {code} OpenShiftService#listEmbeddableCartridges {code} and {code} User#getEmbeddableCartridges {code} are implemented, tested and committed (see https://github.com/adietish/openshift-java-client/commit/0c0cafc9092cb5ad...) The next step now is to embed a cartridge to an application. Embedding is done via rhc-ctl-app in the rhc cli tools: https://github.com/openshift/os-client-tools/blob/master/express/bin/rhc-... The logic is the the main RHC class: https://github.com/openshift/os-client-tools/blob/master/express/lib/rhc-... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9927?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-9927: ----------------------------------------- a first implementation is committed, a first successful integration test (for mysql) is committed. The only bump in the road I found so far is that the cli tooling calls "add" what the service actually wants to be called "configure" (and "remove" in rhc-ctl-app is actually "deconfigure") -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9927?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-9927 at 11/15/11 3:13 PM: ------------------------------------------------------------------- add an embedded cartridge now pretty much works. The integration test works embedding * mysql * phpmyadmin * jenkins see here: https://github.com/adietish/openshift-java-client/blob/master/org.jboss.t... what's missing now is remove, start, stop etc. was (Author: adietish): embedding now pretty much works. The integration test works embedding * mysql * phpmyadmin * jenkins see here: https://github.com/adietish/openshift-java-client/blob/master/org.jboss.t... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9927?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-9927: ------------------------------------ Attachment: app-page.png embed-page.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9927?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-9927 at 11/17/11 11:55 AM: -------------------------------------------------------------------- I now implemented a first version of UI. I chose to have 2 pages when creating a new app: * 1) name and cartridge * 2) embeddable cartridges There are 2 reasons for that: 1) if I put both on 1 page we'd have doubled the initial wait time while the wizard loads the available cartridges and the available embeddable cartridges. By splitting both into 2 different pages the wizard initially only loads the cartridges. Loading the embeddable ones is done on page 2. 2) Apps may only be edited to have different embedded cartridges. So editing an app is choosing the cartridges to embed. I can reuse the page with those embeddable cartridges when editing an app. !app-page.png! !embed-page.png! was (Author: adietish): I now implemented a first version of UI. I chose to have 2 pages when creating a new app: * 1) name and cartridge * 2) embeddable cartridges !embed-page.png! There are 2 reasons for that: 1) if I put both on 1 page we'd have doubled the initial wait time while the wizard loads the available cartridges and the available embeddable cartridges. By splitting both into 2 different pages the wizard initially only loads the cartridges. Loading the embeddable ones is done on page 2. 2) Apps may only be edited to have different embedded cartridges. So editing an app is choosing the cartridges to embed. I can reuse the page with those embeddable cartridges when editing an app. !app-page.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9927?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-9927: ----------------------------------------- "New Application" is not working for the moment, it tries to create an application twice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9927?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-9927 at 11/21/11 1:36 PM: ------------------------------------------------------------------- embedding now works, I fixed it. (waiting for the app to be active is not in place though). I also added a field in the application details dialog. It currently reports the embedded cartridges as comma separated list. what's still missing is the capability to report url, username & password for the embedded cartridge. was (Author: adietish): embedding now works, I fixed it. I also added a field in the application details dialog. It currently reports the embedded cartridges as comma separated list. what's still missing is the capability to report url, username & password for the embedded cartridge. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9927?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-9927 at 11/22/11 4:27 AM: ------------------------------------------------------------------- url, username and pw when embedding are reported at different places: * mysql: when EMBEDDING (in the "result" property of the json reponse object): {code} "\nMysql 5.1 database added. Please make note of these credentials:\n\n Root User: admin\n Root Password: _XfAHDfukMx1\n Database Name: 1321349005433\n\nConnection URL: mysql://127.1.19.129:3306/\n\nYou can manage your new Mysql database by also embedding phpmyadmin-3.4.\n" {code} * phpmyadmin: when EMBEDDING (in the "result" property of the json response): {code} "\nphpMyAdmin 3.4 added. Please make note of these credentials:\n\n Root User: admin\n Root Password: zUgAZitsSPpJ\n\nURL: https://1321355683066-1321105990374.stg.rhcloud.com/phpmyadmin/\n" {code} * jenkins: when CREATING THE JENKINS APP (in the "result" property of the json response): {code} "\nJenkins created successfully. Please make note of these credentials:\n\n User: admin\n Password: Q9-4krz2Cj7y\n\nNote: You can change your password at: http://jen-1320662908628.rhcloud.com/me/configure\n\n" {code} was (Author: adietish): url, username and pw when embedding are reported at different places: * mysql: when embedding (in the "result" property of the json reponse object): {code} "\nMysql 5.1 database added. Please make note of these credentials:\n\n Root User: admin\n Root Password: _XfAHDfukMx1\n Database Name: 1321349005433\n\nConnection URL: mysql://127.1.19.129:3306/\n\nYou can manage your new Mysql database by also embedding phpmyadmin-3.4.\n" {code} * phpmyadmin: when embedding (in the "result" property of the json response): {code} "\nphpMyAdmin 3.4 added. Please make note of these credentials:\n\n Root User: admin\n Root Password: zUgAZitsSPpJ\n\nURL: https://1321355683066-1321105990374.stg.rhcloud.com/phpmyadmin/\n" {code} * jenkins: when creating the jenkins app (in the "result" property of the json response): {code} "\nJenkins created successfully. Please make note of these credentials:\n\n User: admin\n Password: Q9-4krz2Cj7y\n\nNote: You can change your password at: http://jen-1320662908628.rhcloud.com/me/configure\n\n" {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9927?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-9927: ------------------------------------ Attachment: embedded-cartridges.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9927?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-9927: ------------------------------------ Attachment: create-jenkins.png jenkins-log.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9927?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-9927: ----------------------------------------- it would be very nice to have those urls displayed as links. The widget (styled text) I use to display the logs has support for this: http://git.eclipse.org/c/platform/eclipse.platform.swt.git/tree/examples/...). We first need to check if symply displaying the log as text (with or without links) is good enough for us. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9927?page=com.atlassian.jira.plugin... ] Andre Dietisheim resolved JBIDE-9927. ------------------------------------- Resolution: Done -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9927?page=com.atlassian.jira.plugin... ] Lucia Jelinkova closed JBIDE-9927. ---------------------------------- Ok, in that case closing the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9927?page=com.atlassian.jira.plugin... ] Isaac Rooskov closed JBIDE-9927. -------------------------------- Resolution: Done Re-closing issue -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira