[jboss-jira] [JBoss JIRA] (WFLY-4983) Undertow mod_cluster CLI: Display node's protocol://hostname:port

[Michal Karm Babacek (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-4983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Karm Babacek closed WFLY-4983.
-------------------------------------


Verified in Beta9.

> Undertow mod_cluster CLI: Display node's protocol://hostname:port
> -----------------------------------------------------------------
>
>                 Key: WFLY-4983
>                 URL: https://issues.jboss.org/browse/WFLY-4983
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow)
>    Affects Versions: 10.0.0.Alpha5
>            Reporter: Michal Karm Babacek
>            Assignee: Stuart Douglas
>            Priority: Blocker
>              Labels: mod_cluster
>             Fix For: 10.0.0.Beta1
>
>
> As a follow up to JBEAP-215, this bug report is a member of a series addressing crucial CLI management capabilities.
> h3. Display node's protocol://hostname:port
> At the moment, this is all there is to see:
> {noformat}
> "balancer" => {
>     "qa_balancer" => {"node" => {"worker-2" => {
>         "load" => 89,
>         "status" => "NODE_UP",
>         "context" => {"/clusterbench" => {
>             "requests" => 0,
>             "status" => "enabled"
>         }}
>     }}},
> ...
> {noformat}
> h3. Call to action
> We need to display node's connection details, e.g. {{ajp://karm.brq.redhat.com:8019}} or {{https://192.168.1.100:8009}}.
> I set {color:red}Blocker{color} priority, because without this information available, it is impossible to test anything more than rudimentary smoke-test scenarios. From the user's perspective, inability to identify JVMRoutes (node names) with their connection strings renders any larger enterprise setup very hard to manage and maintain.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)