| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
The purpose of this PR is to allow failed fstab entries to not cause an
OS to hang on boot. This is particularly problematic on cloud providers
like AWS where there is not a quick way to manage an instance and select
a skip option prior to SSH access becoming available.
|
| |
|
|
| |
doesn't exist on Ubuntu systems, see : http://askubuntu.com/questions/138972/what-is-the-equivalent-user-for-nobodynobody-from-centos
|
| | |
|
| |
|
|
| |
Thanks to: "Vincent--" for reporting the issue.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 is dedicated to Gilles who didn't like the findmnt patch
initially, but now loves it because it is cross distro friendly :)
Thanks for all your time testing Puppet-Gluster... More eyes helps!
|
| |
|
|
| |
This patch includes program paths.
|
| |
|
|
| |
This patch includes package names.
|
| | |
|
| |
|
|
|
|
|
| |
This adds the ability to do LVM thin provisioning. If you haven't fully
read 'man 7 lvmthin' then please do as this will answer most of your
questions. LVM thin provisioning is used for doing one form of GlusterFS
snapshots.
|
| |
|
|
| |
Although if you remove all the features, it's not as awesome anymore :)
|
| |
|
|
|
|
| |
There could be some cases when you want to omit these choices.
Bug reported by Gilles Dubreuil.
|
| |
|
|
|
|
|
|
|
|
| |
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 support to specify the brick device values as a hash.
It also allows for separate defaults that apply to the whole cluster.
|
| | |
|
| |
|
|
|
|
|
| |
Secret pop quiz
Q: What characters are [in]valid in LVM VG names?
Hint: The + char is valid, but the # char is not.
|
| |
|
|
|
|
|
|
| |
* Add LVM support.
* Add optional partitioning.
* Set xfs inode size, for xattr performance.
* Set xfs logical block size for directory performance.
* Set xfs stripe unit size and stripe width for RAID alignment.
|
| |
|
|
| |
I've updated wrapper.pp too, but I haven't tested it recently.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
| |
The added example should make this obvious. Heed the warning in using
this feature. I find it most useful for rapid prototyping using vm's.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
bodepd!
|
| | |
|
| | |
|
| | |
|
| |
|
