-
Bug
-
Resolution: Done
-
Blocker
-
7.0.0.DR6
Thanks to a good foundation established in JBEAP-215, there is an elementary information about registered worker nodes available, e.g.
/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" => {}}}
}}}
}
One of the information that is missing is Load Balancing Group. This is a Blocker 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.
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
Note that the attribute "Domain" actually stands for "Load Balancing Group" and it is not related to "WildFly Domain".