[jbosstools-issues] [JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: Default routing port selection need more info for users

[Marián Labuda (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13318957#comment-13318957 ] 

Marián Labuda commented on JBIDE-23352:
---------------------------------------

Well, are there any images which have ports for being listened on running container and it is not documented in Dockerfile? Mostly EXPOSE in docker file is about telling a docker where to listen. When deploying a docker image from web UI or oc binary, you dont have a choice to add ports to being listened in advance. So if user uses such image (without exposes port) for OpenShift, then oc binary and web UI cant handle it but we have a workaround for such "use cases" in tooling. Not sure whether that's correct way.

Also, there was a JIRA whether a replication controller should take values from the table, if we decide to add more port mapping. If there would be no exposed ports (listening ports) it would not be possible to connect a service to such port.

My 2 cents.

> 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
>            Assignee: Jeff MAURY
>              Labels: deploy_docker_wizard, openshift_v3
>             Fix For: 4.4.2.Final
>
>         Attachments: no_route_selected.png, refdoc-services-1.png, refdoc-services-2.png, webui-deploy-docker-image.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
(v7.2.3#72005)