[
https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-23352 at 10/17/16 4:56 PM:
--------------------------------------------------------------------
[~jeffmaury] I believe that we should add an explanatory label or info that tells the
user, that when no port is selected for the route, the route will round-robin to all
available ones.
I also believe that we should either remove Add/remove/Edit ports (neither oc nor web-ui
offers these) or mark the custom (edited, added) ports as not being exposed in the docker
image/container - and the user should be sure that there are actual processes on the
docker container that listen to these.
was (Author: adietish):
[~jeffmaury] I believe that we should add an explanatory label or info that tells the
user, that when no port is selected for the route, the route will round-robin to all
available ones.
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)