Mohammed Rafi K C
2016-Nov-14 04:58 UTC
[Gluster-users] Feature Request: Lock Volume Settings
I think it is worth to implement a lock option. +1 Rafi KC On 11/14/2016 06:12 AM, David Gossage wrote:> On Sun, Nov 13, 2016 at 6:35 PM, Lindsay Mathieson > <lindsay.mathieson at gmail.com <mailto:lindsay.mathieson at gmail.com>> wrote: > > As discussed recently, it is way to easy to make destructive changes > to a volume,e.g change shard size. This can corrupt the data with no > warnings and its all to easy to make a typo or access the wrong volume > when doing 3am maintenance ... > > So I'd like to suggest something like the following: > > gluster volume lock <volname> > > Setting this would fail all: > - setting changes > - add bricks > - remove bricks > - delete volume > > gluster volume unlock <volname> > > would allow all changes to be made. > > Just a thought, open to alternate suggestions. > > Thanks > > + > sounds handy > > -- > Lindsay > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org <mailto:Gluster-users at gluster.org> > http://www.gluster.org/mailman/listinfo/gluster-users > <http://www.gluster.org/mailman/listinfo/gluster-users> > > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20161114/e8d7224c/attachment.html>
Atin Mukherjee
2016-Nov-14 12:27 UTC
[Gluster-users] [Gluster-devel] Feature Request: Lock Volume Settings
This would be a straight forward thing to implement at glusterd, anyone up for it? If not, we will take this into consideration for GlusterD 2.0. On Mon, Nov 14, 2016 at 10:28 AM, Mohammed Rafi K C <rkavunga at redhat.com> wrote:> I think it is worth to implement a lock option. > > +1 > > > Rafi KC > > On 11/14/2016 06:12 AM, David Gossage wrote: > > On Sun, Nov 13, 2016 at 6:35 PM, Lindsay Mathieson < > lindsay.mathieson at gmail.com> wrote: > >> As discussed recently, it is way to easy to make destructive changes >> to a volume,e.g change shard size. This can corrupt the data with no >> warnings and its all to easy to make a typo or access the wrong volume >> when doing 3am maintenance ... >> >> So I'd like to suggest something like the following: >> >> gluster volume lock <volname> >> >> Setting this would fail all: >> - setting changes >> - add bricks >> - remove bricks >> - delete volume >> >> gluster volume unlock <volname> >> >> would allow all changes to be made. >> >> Just a thought, open to alternate suggestions. >> >> Thanks >> >> + > sounds handy > >> -- >> Lindsay >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users at gluster.org >> http://www.gluster.org/mailman/listinfo/gluster-users >> > > > > _______________________________________________ > Gluster-users mailing listGluster-users at gluster.orghttp://www.gluster.org/mailman/listinfo/gluster-users > > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-devel >-- ~ Atin (atinm) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20161114/322c2dbe/attachment.html>