[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: Default routing port selection need more info for users
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23352:
-------------------------------------
Fix Version/s: 4.4.2.AM3
(was: 4.4.2.AM2)
> Deploy Docker Wizard: Default routing port selection need more info for users
> -----------------------------------------------------------------------------
>
> Key: JBIDE-23352
> URL: https://issues.jboss.org/browse/JBIDE-23352
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM3
>
> Attachments: no_route_selected.png
>
>
> In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open.
> If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening.
> steps to reproduce:
> # EXEC: In Docker Explroer: pick an image and choose "Deploy to OpenShift..." in the context menu
> # EXEC: get to the "Services & Routing Settings" page
> !no_route_selected.png!
> It's not obvious to the user what the wizard will create: A service that "exposes" pod ports and a route that points to this service. Furthermore it's not obvious that without a "checked" (used by route) port, the route will round-robin through the available ports. Additionally we should show the user what ports are exposed by the pod, and which ones are ports that the user added while no explicit exposure is defined in the pod (so he's on his own, if there's nothing listening on them he'll have users face non-functional or no reposonses at all).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: Default routing port selection need more info for users
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23352:
-------------------------------------
Affects Version/s: 4.4.1.AM2
(was: 4.4.2.AM1)
> Deploy Docker Wizard: Default routing port selection need more info for users
> -----------------------------------------------------------------------------
>
> Key: JBIDE-23352
> URL: https://issues.jboss.org/browse/JBIDE-23352
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM3
>
> Attachments: no_route_selected.png
>
>
> In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open.
> If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening.
> steps to reproduce:
> # EXEC: In Docker Explroer: pick an image and choose "Deploy to OpenShift..." in the context menu
> # EXEC: get to the "Services & Routing Settings" page
> !no_route_selected.png!
> It's not obvious to the user what the wizard will create: A service that "exposes" pod ports and a route that points to this service. Furthermore it's not obvious that without a "checked" (used by route) port, the route will round-robin through the available ports. Additionally we should show the user what ports are exposed by the pod, and which ones are ports that the user added while no explicit exposure is defined in the pod (so he's on his own, if there's nothing listening on them he'll have users face non-functional or no reposonses at all).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: Default routing port selection need more info for users
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23352:
-------------------------------------
Description:
In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open.
If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening.
steps to reproduce:
# EXEC: In Docker Explroer: pick an image and choose "Deploy to OpenShift..." in the context menu
# EXEC: get to the "Services & Routing Settings" page
!no_route_selected.png!
It's not obvious to the user what the wizard will create: A service that "exposes" pod ports and a route that points to this service. Furthermore it's not obvious that without a "checked" (used by route) port, the route will round-robin through the available ports. Additionally we should show the user what ports are exposed by the pod, and which ones are ports that the user added while no explicit exposure is defined in the pod (so he's on his own, if there's nothing listening on them he'll have users face non-functional or no reposonses at all).
was:
In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open.
If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening.
!no_route_selected.png!
> Deploy Docker Wizard: Default routing port selection need more info for users
> -----------------------------------------------------------------------------
>
> Key: JBIDE-23352
> URL: https://issues.jboss.org/browse/JBIDE-23352
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.AM1
> Reporter: Marián Labuda
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM2
>
> Attachments: no_route_selected.png
>
>
> In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open.
> If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening.
> steps to reproduce:
> # EXEC: In Docker Explroer: pick an image and choose "Deploy to OpenShift..." in the context menu
> # EXEC: get to the "Services & Routing Settings" page
> !no_route_selected.png!
> It's not obvious to the user what the wizard will create: A service that "exposes" pod ports and a route that points to this service. Furthermore it's not obvious that without a "checked" (used by route) port, the route will round-robin through the available ports. Additionally we should show the user what ports are exposed by the pod, and which ones are ports that the user added while no explicit exposure is defined in the pod (so he's on his own, if there's nothing listening on them he'll have users face non-functional or no reposonses at all).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-23016.
---------------------------------
Resolution: Done
Current code functions as expected
> When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23016
> URL: https://issues.jboss.org/browse/JBIDE-23016
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.2.AM2
>
>
> The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already).
> This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights.
> When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23371) Deploy image wizard: "Services and Routing Settings" page needs to explain to user what the settings result in.
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23371?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-23371.
--------------------------------------
Resolution: Duplicate Issue
> Deploy image wizard: "Services and Routing Settings" page needs to explain to user what the settings result in.
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23371
> URL: https://issues.jboss.org/browse/JBIDE-23371
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Andre Dietisheim
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM3
>
> Attachments: services-and-routing-page.png
>
>
> steps to reproduce:
> # EXEC: In Docker Explroer: pick an image and choose "Deploy to OpenShift..." in the context menu
> # EXEC: get to the "Services & Routing Settings" page
> Result:
> !services-and-routing-page.png!
> The page allows to add/remove/edit ports and to configure a route. It's not obvious to the user what these settings are for and what they result in being created (a single service and route are created).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23371) Deploy image wizard: "Services and Routing Settings" page needs to explain to user what the settings result in.
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23371?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-23371:
----------------------------------------
Assignee: Andre Dietisheim
> Deploy image wizard: "Services and Routing Settings" page needs to explain to user what the settings result in.
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23371
> URL: https://issues.jboss.org/browse/JBIDE-23371
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM3
>
> Attachments: services-and-routing-page.png
>
>
> steps to reproduce:
> # EXEC: In Docker Explroer: pick an image and choose "Deploy to OpenShift..." in the context menu
> # EXEC: get to the "Services & Routing Settings" page
> Result:
> !services-and-routing-page.png!
> The page allows to add/remove/edit ports and to configure a route. It's not obvious to the user what these settings are for and what they result in being created (a single service and route are created).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23368) Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23368?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23368:
-------------------------------------
Fix Version/s: 4.4.2.AM3
> Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23368
> URL: https://issues.jboss.org/browse/JBIDE-23368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM3
>
>
> When deploying a docker image via Deploy Docker Wizard to an OpenShift instance, there is a wizard page with mapping of pod ports to service ports. If I add a new port mapping there, it is propagated to a created Service. But created replication controller does not contain those new mappings (results into creating pods without those ports available)
> Either way this should be fixed, to also Replication Controller should contain mapped ports, because having a service which has mapped pod ports to service ports but pods itself does not have this port exposes is useless. Or having Add... button does not make sense there, or there is no known use case where it would be useful (existing mapping could be edited but a new one would be useless).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23368) Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23368?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23368:
------------------------------------------
[~mlabuda] talked about this to [~jcantrill] today and I believe that the port setting should not be set to the replication controller.
I believe that we should either remove Add/remove/Edit ports or mark them as not being exposed in the docker image/container
[~jeffmaury] Thoughts?
> Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23368
> URL: https://issues.jboss.org/browse/JBIDE-23368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Labels: deploy_docker_wizard, openshift_v3
>
> When deploying a docker image via Deploy Docker Wizard to an OpenShift instance, there is a wizard page with mapping of pod ports to service ports. If I add a new port mapping there, it is propagated to a created Service. But created replication controller does not contain those new mappings (results into creating pods without those ports available)
> Either way this should be fixed, to also Replication Controller should contain mapped ports, because having a service which has mapped pod ports to service ports but pods itself does not have this port exposes is useless. Or having Add... button does not make sense there, or there is no known use case where it would be useful (existing mapping could be edited but a new one would be useless).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4054) publish rpms + metadata to /latest/ locations so they can be easily installed by QE
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4054?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4054:
-----------------------------
Description:
Next step is publishing these yum repos (metadata + rpms) to a location that can be made easily available to RHEL users, eg.,
* https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_master/l...
* https://devstudio.redhat.com/10.0/snapshots/rpms/10.2.0/x86_64/
And, we have an empty placeholder site for the eventual release:
* https://devstudio.redhat.com/static/10.0/stable/rpms/x86_64/
was:
Next step is publishing these yum repos (metadata + rpms) to a location that can be made easily available to RHEL users, eg.,
* https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_master/l...
* https://devstudio.redhat.com/10.0/snapshots/rpms/10.2.0/x86_64/
> publish rpms + metadata to /latest/ locations so they can be easily installed by QE
> -----------------------------------------------------------------------------------
>
> Key: JBDS-4054
> URL: https://issues.jboss.org/browse/JBDS-4054
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build, rpm
> Affects Versions: 10.1.0.GA, 10.2.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: doc_writer_needed, docs_installation_guide, new_and_noteworthy
> Fix For: 10.2.0.AM2
>
> Attachments: rh-eclipse46-devstudio.repo
>
>
> Next step is publishing these yum repos (metadata + rpms) to a location that can be made easily available to RHEL users, eg.,
> * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_master/l...
> * https://devstudio.redhat.com/10.0/snapshots/rpms/10.2.0/x86_64/
> And, we have an empty placeholder site for the eventual release:
> * https://devstudio.redhat.com/static/10.0/stable/rpms/x86_64/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months