On Mon, Oct 3, 2016 at 12:21 PM, Hari Gowtham <[email protected]> wrote:
> Hi, > > The current add and remove brick commands aren't sufficient to support > add/remove brick on tiered volumes.So the commands need minor changes > like mentioning which tier we are doing the operation on. So in order > to specify the tier on which we are performing the changes, I thought > of using the following commands for add and remove brick > > adding brick on tiered volume: > gluster volume tier <volname> add-hot-brick/add-cold-brick <brick> ... > <force> > > removing brick on tierd volume: > gluster volume tier <volname> remove-hot-brick/remove-cold-brick <brick> > ... <start|stop|status|commit|force> > > I have framed it this way because once we mention details about tiering > these commands become specific to tier and the syntax that we follow for > commands are gluster volume component <VOLNAME> ... > So i have made sure that the keyword tier comes after volume. > Need suggestions to make these commands better. > > Similarly once we support add/remove brick we will be having rebalance > commands and the idea is to support rebalance separately for each tier. > So once we will have to rebalance status to display for which we need > rebalance commands specific to tier. so these are the commands we have > thought of: > gluster v tier <VOLNAME> hot-rebalance/cold-rebalance <start|stop|status> > > Need your comments regarding this. > Overall it makes sense. Just a comment here. Instead of mentioning remove/add/rebalance-hot/cold-brick can we have an additional arg called tier-type <hot/cold> and continue with the existing semantics like remove-brick, add-brick and rebalance? > -- > Regards, > Hari. > > _______________________________________________ > Gluster-devel mailing list > [email protected] > http://www.gluster.org/mailman/listinfo/gluster-devel > -- --Atin
_______________________________________________ Gluster-users mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-users
