| 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
|
|
|
|
|
| |
Depending of gluster use, performances could be very impacted by this choice.
See http://www.gluster.org/community/documentation/index.php/Gluster_3.2:_Using_NFS_with_Gluster
|
|
|
|
| |
This is needed in order to run "onlyif" option properly.
|
|
|
|
|
| |
Workaround for : "Stopping volume make its data inaccessible. Do you want to continue? (y/n)"
See https://access.redhat.com/documentation/en-US/Red_Hat_Storage/2.0/html/Installation_Guide/ch08.html
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This resolves repeated modification to
--- /var/lib/glusterd/glusterd.info
@@ -1,2 +1 @@
UUID=abc.def.xyz
-operating-version=1
|
|
|
|
| |
Thanks to: "Vincent--" for reporting the issue.
|
|
|
|
| |
"${::gluster::versions::operating_version}"
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This does some small fixes to rbarlow's original commit (merged).
Originally, I wasn't sure it was the correct patch, and I implemented
something different to try it out a different way, but in the end, I
realized that rbarlow's method was better! rbarlow, you're on your way
to becoming a puppet superstar!
This patch just makes some small changes so that the code is consistent,
and nitpitcks a bit.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Feature: Persistent caching of connected NFS-clients
Source: http://review.gluster.org/#/c/4430/
Note: this property will apply for all your gluster node.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Many thanks to CyrilP for filing in a lot of this data file.
|
| |
|
|
|
|
|
|
| |
This can be set with hiera: gluster::params::include_puppet_facter can
be set to false or 'false' to make puppet::facter optional. The downside
is that setting gluster::params::program_gluster won't apply to facts.
|
|
|
|
|
| |
This isn't necessary, but is more correct. I realized how I could do
this, and have now implemented it.
|
| |
|
| |
|
|
|
|
|
| |
In newer puppet versions the parser changed... I think it's requiring
code in parse order now.
|
| |
|
| |
|
|
|
|
|
|
| |
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 also generalizes the service name, so that other operating
systems will also benefit from this patch by dropping in a yaml file.
|
| |
|
|
|
|
| |
This patch includes program paths.
|
|
|
|
| |
This patch includes package names.
|
| |
|
|
|
|
|
|
| |
In the future this package should only be pulled in when a known
dependency tells puppet-gluster that it needs it. For now it's fine.
In any case, this is Mostly Harmless (tm).
|
|
|
|
|
|
|
| |
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 is actually valid in Puppet 3.x, but removing the colons doesn't
break the 3.x tree.
|
|
|
|
|
|
| |
I wasn't able to test this patch, for lack of hardware at the moment. A
patch for: https://github.com/pradels/vagrant-libvirt/issues/162 would
also help solve my testing issue. Please report any issues!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've had most of this patch in my head for at least a week, and I
finally got the time to implement it! If you are building a symmetrical
cluster, that has consistent device naming across all of the hosts, then
this patch is the magic that should make your life _significantly_
easier. (*cough, cough*: Ben England...)
In the corner case that some of your device have different names, you
can still use this feature in conjunction with the other parameters to
first set global defaults, and then override as needed.
If you don't specify an overriding parameter (such as $count) then the
number of elements in this array will be used as the brick count!
Please note that this patch provides the $brick_params_defaults option
which is different from the $brick_param_defaults option which will
still work, and is useful in conjunction with this option as the way to
set brick defaults across the whole cluster.
For more questions you'll be happy to see that this patch comes with
documentation and example updates.
|
|
|
|
| |
Fixed the logic that was backwards when you chose a UUID manually.
|
|
|
|
| |
Small bug due to lesser used code path, now squashed!
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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 isn't essential, as ensuring this is race-free is really up to
glusterfs, but with this patch you reduce the likelihood to ~0% that
you'll see a: "volume set: failed: Another transaction is in progress."
error. The error isn't harmful, but now we'll see less unnecessary red.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* Don't use this feature unless you _really_ know what you're doing.
* Managing chained volumes is much harder than managing normal ones.
* If some of the volumes in the cluster use this, and others don't, then
you'll probably have an even crazier time with management.
* Please verify my algorithm and feel free to suggest changes.
* Some edge cases haven't been tested.
* This patch breaks out brick layout ordering into individual functions.
|