[Gluster-devel] [Gluster-users] Mechanisms for automatic management of Gluster
avati at gluster.org
Wed Dec 11 23:06:26 UTC 2013
This is the right way to think about the problem. I have more specific
comments in the script, but just wanted to let you know this is a great
On Wed, Nov 27, 2013 at 7:42 AM, James <purpleidea at gmail.com> wrote:
> This is along the lines of "tools for sysadmins". I plan on using
> these algorithms for puppet-gluster, but will try to maintain them
> separately as a standalone tool.
> The problem: Given a set of bricks and servers, if they have a logical
> naming convention, can an algorithm decide the ideal order. This could
> allow parameters such as replica count, and
> The second problem: Given a set of bricks in a volume, if someone adds
> X bricks and removes Y bricks, is this valid, and what is the valid
> sequence of add/remove brick commands.
> I've written some code with test cases to try and figure this all out.
> I've left out a lot of corner cases, but the boilerplate is there to
> make it happen. Hopefully it's self explanatory. (gluster.py) Read and
> run it.
> Once this all works, the puppet-gluster use case is magic. It will be
> able to take care of these operations for you (if you want).
> For non puppet users, this will give admins the confidence to know
> what commands they should _probably_ run in what order. I say probably
> because we assume that if there's an error, they'll stop and inspect
> I haven't yet tried to implement the chained cases, or anything
> involving striping. There are also some corner cases with some of the
> current code. Once you add chaining and striping, etc, I realized it
> was time to step back and ask for help :)
> I hope this all makes sense. Comments, code, test cases are appreciated!
> @purpleidea (irc/twitter)
> Gluster-users mailing list
> Gluster-users at gluster.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-devel