Added support for NS autoloadbalancing

[HaruChebrolu]

Description

Changes to support NS autoloadbalancing
Doc: https://docs.google.com/document/d/1bpx21903Sof1JzGTg81lG7lnk4QeCcqo6uF28Au_zEc/edit#heading=h.m22j2pb1oqna
Polarion:
CEPH-83598716
CEPH-83598717

Logs link: http://magna002.ceph.redhat.com/cephci-jenkins/harika/cephci-run-YR9PMT/

click to expand checklist

• Create a test case in Polarion reviewed and approved.
• Create a design/automation approach doc. Optional for tests with similar tests already automated.
• Review the automation design
• Implement the test script and perform test runs
• Submit PR for code review and approve
• Update Polarion Test with Automation script details and update automation fields
• If automation is part of Close loop, update BZ flag qe-test_coverage “+” and link Polarion test

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: HaruChebrolu

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[rahullepakshi]

Can we avoid running "gw info" command so many times? It creates confusion while analyzing logs

Also namespace list or probably any CLI output is logged twice. Any idea why? can we avoid it?

[HaruChebrolu]

Can we avoid running "gw info" command so many times? It creates confusion while analyzing logs

Also namespace list or probably any CLI output is logged twice. Any idea why? can we avoid it?

Can we avoid running "gw info" command so many times? It creates confusion while analyzing logs - "gw info" was running for each GW entity operation like "subsystem add", "listener add" for 2 reasons.

• to check the GW health after evry operation
• to use the few properties from "gw info" output to subsequent operations instead of hardcoding things
  Also namespace list or probably any CLI output is logged twice. Any idea why? can we avoid it? - its being printed twice because of pretty_print and our own logger to check on exit_code. We need them inorder to diagnose on automation errors.