[jboss-jira] [JBoss JIRA] (WFLY-5017) Undertow mod_cluster proxy: CLI does not display/control load balancing groups

[Stuart Douglas (JIRA)]

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

Stuart Douglas moved UNDERTOW-489 to WFLY-5017:
-----------------------------------------------

              Project: WildFly  (was: Undertow)
                  Key: WFLY-5017  (was: UNDERTOW-489)
    Affects Version/s:     (was: 1.3.0.Beta3)
          Component/s: Web (Undertow)
                           (was: Proxy)


> Undertow mod_cluster proxy: CLI does not display/control load balancing groups
> ------------------------------------------------------------------------------
>
>                 Key: WFLY-5017
>                 URL: https://issues.jboss.org/browse/WFLY-5017
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow)
>            Reporter: Michal Karm Babacek
>            Assignee: Stuart Douglas
>            Priority: Blocker
>
> Thanks to a good foundation established in JBEAP-215, there is an elementary information about registered worker nodes available, e.g.
> {noformat}
> /subsystem=undertow/configuration=filter/mod-cluster=modcluster:read-children-resources(child-type=balancer,recursive=true)
> {
>     "outcome" => "success",
>     "result" => {"mycluster" => {"node" => {
>         "worker-2" => {"context" => {"/clusterbench" => {}}},
>         "worker-1" => {"context" => {"/clusterbench" => {}}}
>     }}}
> }
> {noformat}
> One of the information that is missing is *Load Balancing Group*. This is a {color:red}Blocker{color} issue, because absence of Load Balancing Group display and control capabilities blocks:
> * customer scenarios with rolling upgrades
> * customer scenarios with heterogeneous deployments
> * customer scenarios with clustering migration
> * all test cases linked to Load Balancing Group functionality
> The Load Balancing Group functionality appears to be present, so this issue might be resolved with adding CLI operations.
> {noformat}
> UT005054: MCMP processing, key: JVMRoute, value: worker-2
> UT005054: MCMP processing, key: Domain, value: LB-GROUP-1
> UT005054: MCMP processing, key: Host, value: karm.brq.redhat.com
> UT005054: MCMP processing, key: Maxattempts, value: 1
> UT005054: MCMP processing, key: Port, value: 8029
> UT005054: MCMP processing, key: StickySessionForce, value: No
> UT005054: MCMP processing, key: Type, value: ajp
> UT005054: MCMP processing, key: ping, value: 10
> {noformat}
> Note that the attribute "Domain" actually stands for  "Load Balancing Group" and it is not related to "WildFly Domain".



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