[Bugs] [Bug 1415590] New: removing old tier commands under the rebalance commands

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1415590

            Bug ID: 1415590
           Summary: removing old tier commands under the rebalance
                    commands
           Product: GlusterFS
           Version: mainline
         Component: tiering
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: hgowtham at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org



Description of problem:
gluster v rebalance <volname> tier {start|status} spawns a new tier daemon and
shows status for that.
The tier daemon spawned under service framework and the one with rebalance
command are different and we end up with two tier daemons. the older one has to
be removed. 

Version-Release number of selected component (if applicable):
mainline

How reproducible:
100%

Steps to Reproduce:
1.create a volume (any configuration)
2.attach a tier to this volume using the gluster v tier <volname> attach ...
command (spawns a tier daemon)
3.issue gluster v rebalance <volname> tier start (spawns another tier for the
same volume)

Actual results:
creates a new daemon and ends up showing the status for that daemon also.

Expected results:
gluster v rebalance <volname> tier start/status should not create new daemon.
or should connect to the actual tier daemon from service framework.

Additional info:
both the commands can be made to work with one tierd but that will make the new
tierd under service framework ugly and hard to maintain. As the rebalance
commands are being separated from tier commands, its better to remove the
support for the older tier commands under rebalance.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.