[JBoss JIRA] (JBIDE-20937) Create resource(s) from json
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20937?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-20937 at 5/3/16 2:27 PM:
------------------------------------------------------------------
Trying to use the "Workspace..." button didnt work for me. The workspace project were presented in a dialog, but choosing one and hitting "OK" or double clicking it had the dialog being closed but the selected project wasnt filled into the source text field in the wizard.
Beside the few minors I commented in the jira, the wizard worked for me with a json file that specifies an imagestream: [^cakephp-example-imagestream.json]
It also worked for me trying to create a service with the following file: [^cakephp-example-service.json].
The service showed up in the OpenShift Explorer right after creating it in the wizard. Nice!
was (Author: adietish):
beside the few minors I commented in the jira, the wizard worked for me with a json file that specifies an imagestream: [^cakephp-example-imagestream.json]
It also worked for me trying to create a service with the following file: [^cakephp-example-service.json].
The service showed up in the OpenShift Explorer right after creating it in the wizard.
> Create resource(s) from json
> ----------------------------
>
> Key: JBIDE-20937
> URL: https://issues.jboss.org/browse/JBIDE-20937
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR2
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 4.4.0.Alpha2
>
> Attachments: cakephp-example-imagestream.json, cakephp-example-service.json, New Resource Wizard Mockup.bmml, New Resource Wizard Mockup.png
>
>
> It would be nice to have feature to create a new resource, e.g. image stream or pod, from provided json. Similar to "oc create -f some_resource.json"
> Currently it would be very usable for MW application templates, because jboss-eap basic s2i template requires image stream which is defined in another json. Also there are applications which are consisting of separately defined resources (e.g. in openshift origin repo is hello world application and its having defined pod in separated json).
> This could be available via context menu New - Resource (like we have for application, projects and connections). And it could be accessible via context menu of a project and specific resource type (e.g. for tree item Image Streams).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-20937) Create resource(s) from json
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20937?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20937:
-------------------------------------
Attachment: cakephp-example-service.json
> Create resource(s) from json
> ----------------------------
>
> Key: JBIDE-20937
> URL: https://issues.jboss.org/browse/JBIDE-20937
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR2
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 4.4.0.Alpha2
>
> Attachments: cakephp-example-imagestream.json, cakephp-example-service.json, New Resource Wizard Mockup.bmml, New Resource Wizard Mockup.png
>
>
> It would be nice to have feature to create a new resource, e.g. image stream or pod, from provided json. Similar to "oc create -f some_resource.json"
> Currently it would be very usable for MW application templates, because jboss-eap basic s2i template requires image stream which is defined in another json. Also there are applications which are consisting of separately defined resources (e.g. in openshift origin repo is hello world application and its having defined pod in separated json).
> This could be available via context menu New - Resource (like we have for application, projects and connections). And it could be accessible via context menu of a project and specific resource type (e.g. for tree item Image Streams).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-20937) Create resource(s) from json
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20937?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-20937 at 5/3/16 1:59 PM:
------------------------------------------------------------------
beside the few minors I commented in the jira, the wizard worked for me with a json file that specifies an imagestream: [^cakephp-example-imagestream.json]
It also worked for me trying to create a service with the following file: [^cakephp-example-service.json].
The service showed up in the OpenShift Explorer right after creating it in the wizard.
was (Author: adietish):
beside the few minors I commented in the jira, the wizard worked for me with a json file that specifies an imagestream: [^cakephp-example-imagestream.json]
> Create resource(s) from json
> ----------------------------
>
> Key: JBIDE-20937
> URL: https://issues.jboss.org/browse/JBIDE-20937
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR2
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 4.4.0.Alpha2
>
> Attachments: cakephp-example-imagestream.json, New Resource Wizard Mockup.bmml, New Resource Wizard Mockup.png
>
>
> It would be nice to have feature to create a new resource, e.g. image stream or pod, from provided json. Similar to "oc create -f some_resource.json"
> Currently it would be very usable for MW application templates, because jboss-eap basic s2i template requires image stream which is defined in another json. Also there are applications which are consisting of separately defined resources (e.g. in openshift origin repo is hello world application and its having defined pod in separated json).
> This could be available via context menu New - Resource (like we have for application, projects and connections). And it could be accessible via context menu of a project and specific resource type (e.g. for tree item Image Streams).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3879) AERI - Closing the 'configure projects' dialog disables enabled projects
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3879?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3879:
-------------------------------
Attachment: before.png
after.png
> AERI - Closing the 'configure projects' dialog disables enabled projects
> ------------------------------------------------------------------------
>
> Key: JBDS-3879
> URL: https://issues.jboss.org/browse/JBDS-3879
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: aeri
> Affects Versions: 10.0.0.Alpha1
> Environment: Version: 10.0.0.Alpha1
> Build id: Alpha1-v20160430-1625-B5264
> Build date: 20160430-1625
> Reporter: Len DiMaggio
> Attachments: after.png, before.png
>
>
> To recreate:
> * Navigate to: Preferences->General->Error Reporting
> * Open 'configure projects' dialog
> * Enable one or more projects, click on "Enable"
> * Open 'configure projects' dialog
> * Close the dialog (select the 'x' at upper right)
> * Open 'configure projects' dialog
> * Observe that the selections are now disabled
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3879) AERI - Closing the 'configure projects' dialog disables enabled projects
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3879?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3879:
-----------------------------
> AERI - Closing the 'configure projects' dialog disables enabled projects
> ------------------------------------------------------------------------
>
> Key: JBDS-3879
> URL: https://issues.jboss.org/browse/JBDS-3879
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: aeri
> Affects Versions: 10.0.0.Alpha1
> Environment: Version: 10.0.0.Alpha1
> Build id: Alpha1-v20160430-1625-B5264
> Build date: 20160430-1625
> Reporter: Len DiMaggio
>
> To recreate:
> * Navigate to: Preferences->General->Error Reporting
> * Open 'configure projects' dialog
> * Enable one or more projects, click on "Enable"
> * Open 'configure projects' dialog
> * Close the dialog (select the 'x' at upper right)
> * Open 'configure projects' dialog
> * Observe that the selections are now disabled
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3879) AERI - Closing the 'configure projects' dialog disables enabled projects
by Len DiMaggio (JIRA)
Len DiMaggio created JBDS-3879:
----------------------------------
Summary: AERI - Closing the 'configure projects' dialog disables enabled projects
Key: JBDS-3879
URL: https://issues.jboss.org/browse/JBDS-3879
Project: Red Hat Developer Studio (DevStudio)
Issue Type: Bug
Components: aeri
Affects Versions: 10.0.0.Alpha1
Environment: Version: 10.0.0.Alpha1
Build id: Alpha1-v20160430-1625-B5264
Build date: 20160430-1625
Reporter: Len DiMaggio
To recreate:
* Navigate to: Preferences->General->Error Reporting
* Open 'configure projects' dialog
* Enable one or more projects, click on "Enable"
* Open 'configure projects' dialog
* Close the dialog (select the 'x' at upper right)
* Open 'configure projects' dialog
* Observe that the selections are now disabled
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21720) Server Adapter: user choose default route when creating the server
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21720?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21720 at 5/3/16 1:35 PM:
-----------------------------------------------------------------------
ServerSettingsWizardPageModel.setRoute(IRoute newRoute) fails to pass newRoute to method update().
[~adietish], please take a look at the pull request https://github.com/jbosstools/jbosstools-openshift/pull/1138
was (Author: scabanovich):
ServerSettingsWizardPageModel.setRoute(IRoute newRoute) fails to pass newRoute to method update().
> Server Adapter: user choose default route when creating the server
> ------------------------------------------------------------------
>
> Key: JBIDE-21720
> URL: https://issues.jboss.org/browse/JBIDE-21720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.0.Alpha2
>
>
> Currently the Show in Web Browser always asks the user which route to open, which tends to be annoying when using the menu several times. For LiveReload support, it's even worse, the 1st route is always selected, which always leads to some problems when several routes are available.
> I believe it would be best to let the user select the server adapter' default route in the OpenShift 3 Server wizard
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21720) Server Adapter: user choose default route when creating the server
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21720?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21720:
-----------------------------------------------
ServerSettingsWizardPageModel.setRoute(IRoute newRoute) fails to pass newRoute to method update().
> Server Adapter: user choose default route when creating the server
> ------------------------------------------------------------------
>
> Key: JBIDE-21720
> URL: https://issues.jboss.org/browse/JBIDE-21720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.0.Alpha2
>
>
> Currently the Show in Web Browser always asks the user which route to open, which tends to be annoying when using the menu several times. For LiveReload support, it's even worse, the 1st route is always selected, which always leads to some problems when several routes are available.
> I believe it would be best to let the user select the server adapter' default route in the OpenShift 3 Server wizard
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21228) DeploymentConfig for Deploying a docker image should point the image container to the imagestream
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21228?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21228:
---------------------------------------
I am unable to reproduce this behavior on master using the context menu 'deploy image' from the docker explorer view: https://gist.github.com/jcantrill/4a2db8ace7c08590762f160a87df3e00 If I choose an image and allow the wizard to populate it, I get what is shown in the gist. If I explicitly add 'docker.io' as the repo (e.g. docker.io/openshift/hello-openshift). The IS and DC are created with 'docker.io' since looking at the code we explicitly retain the repo. This is for cases where the repo is not one of the defaults. IMO this is desired behavior. If you can list the steps that are different from what I describe here I will continue investigation. I otherwise believe this is working as I would expect it. The only obvious thing I can think we may wish to do is whitelist 'docker.io' and remove it if the docker URI includes it.
> DeploymentConfig for Deploying a docker image should point the image container to the imagestream
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21228
> URL: https://issues.jboss.org/browse/JBIDE-21228
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Priority: Minor
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> Deploying a docker image from a local machine will create resources. When the image is pushed to OS, the DC should assume it will be namespaced to the same project in which the resources are created. Ref: https://gist.github.com/jcantrill/cb84b919e1a7a4791440#file-gistfile1-txt...
> This image was deployed to the 'helloworld' namespace and the image spec should not include the original docker namespace.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months