[Bugs] [Bug 1294548] New: Enhancement: The cli could manage state

[bugzilla at redhat.com]

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

            Bug ID: 1294548
           Summary: Enhancement: The cli could manage state
           Product: GlusterFS
           Version: 3.7.6
         Component: cli
          Severity: low
          Assignee: bugs at gluster.org
          Reporter: joe at julianfamily.org
                CC: bugs at gluster.org, gluster-bugs at redhat.com



puppet, salt, etc all manage gluster state from a 3rd party standpoint to
manage the steps necessary to change a volume, peer state, etc. They do this by
taking output from the cli, determining state, then passing change commands
back in to the cli.

This is something the cli could manage directly. For instance, a volume of:

Volume Name: myvolume
Type: Distribute
Volume ID: 1fb52916-7fbf-4ef3-99e3-ec06b5b6407a
Status: Started
Number of Bricks: 1 x 1 = 1
Transport-type: tcp
Bricks:
Brick1: host1:/srv/gluster/myvolume/brick1
Brick2: host2:/srv/gluster/myvolume/brick1

A command like:

gluster volume state myvolume host1:/srv/gluster/myvolume/brick1
host2:/srv/gluster/myvolume/brick1 host3:/srv/gluster/myvolume/brick1

Would add a 3rd brick on host3.

Or:

gluster volume state myvolume replica 2 host1:/srv/gluster/myvolume/brick1
host3:/srv/gluster/myvolume/brick1 host2:/srv/gluster/myvolume/brick1
host4:/srv/gluster/myvolume/brick1

Would convert the distribute volume to a replicated volume. 

If the bricks were listed in the wrong order, host1, host2, host3, host4, the
cli should warn and abort without some sort of switch or keyword that makes
excessive changes complete. With that override option, however, the cli would
replace brick, migrating the data from 2 to 3, then add brick with replica 2.

Optimally, the state management command would also accept volume options, ie.:

gluster volume state myvolume host1:/srv/gluster/myvolume/brick1
host2:/srv/gluster/myvolume/brick1 option cluster.eager-lock=enable option
performance.stat-prefetch=off

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