| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds btrfs support to puppet-gluster. This is not (yet)
officially supported by GlusterFS but should work. It is being added
here to make it easier to test with GlusterFS and report bugs.
Special thanks to Eric Sandeen for adding --uuid support to mkfs.btrfs:
https://bugzilla.redhat.com/show_bug.cgi?id=1094857
Tracker bug for this feature is:
https://bugzilla.redhat.com/show_bug.cgi?id=1094860
|
| |
|
|
| |
This patch includes package names.
|
| |
|
|
|
|
|
|
|
|
| |
This automatically generates UUID's for each physical filesystem, or
alternatively, you can specify one manually with the $fsuuid argument.
This will make a _big_ difference when using gluster::simple to
automatically deploy a large cluster of physical machines, since you
don't have to manually generate one uuid per device (which is time
consuming and could be a lot to do and a lot to maintain).
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds preliminary FSM support. This will be used and abused
more extensively in later patches. Automatic brick ordering is an
advanced feature and is meant for experienced puppet users. Changing the
available bricks before the cluster is built is not currently supported.
For that type of magic, please wait for gluster::elastic.
This feature expects that you name your bricks and hosts intelligently.
Future patches will recommend a specific nomenclature, but for now as
long as the brick paths and hostnames follow a padded, incrementing
integer pattern, with a common prefix, you shouldn't see any problems.
|
| |
|
|
|
|
|
| |
While the module can still be used in a simple way:
* It is pretty complicated at this point. It does some advanced stuff.
* I wanted to avoid confusion with gluster::simple which is coming soon.
|
| | |
|
| |
|
|
| |
bodepd!
|
| |
|
