[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.Final
(was: 4.4.2.AM3)
> 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.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)
9 years, 5 months
[JBoss JIRA] (JBIDE-22375) Improve HCR OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22375?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22375:
-------------------------------------
Fix Version/s: 4.4.x
(was: 4.4.2.AM3)
> Improve HCR OpenShift
> ---------------------
>
> Key: JBIDE-22375
> URL: https://issues.jboss.org/browse/JBIDE-22375
> Project: Tools (JBoss Tools)
> Issue Type: Epic
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Priority: Blocker
> Fix For: 4.4.x
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23279) Exception generated when OS 3 connection URL is invalid
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23279?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23279:
-------------------------------------
Fix Version/s: 4.4.2.Final
(was: 4.4.2.AM3)
> Exception generated when OS 3 connection URL is invalid
> -------------------------------------------------------
>
> Key: JBIDE-23279
> URL: https://issues.jboss.org/browse/JBIDE-23279
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM1
> Reporter: Jeff MAURY
> Labels: openshift, openshift_v3
> Fix For: 4.4.2.Final
>
>
> EXEC: launch application wizard via file menu: New > OpenShift > OpenShift application
> EXEC: select <New Connection>
> EXEC: enter invalid URL in the host field
> ASSERT: an com.openshift.restclient.OpenShiftException: Unable to initialize client exception is logged into the console
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months