| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
|
| |
This adds custom set group support for users that might not have the
feature (I think it might only exist in RHS) and also to users who want
to add their own custom groups! Please ping me if the stock groups gain
or lose parameters, or if their set values change!
|
| |
|
|
|
|
|
|
|
|
| |
This adds support for setting volume set groups which are groups of
properties that are set all at once on a volume. This is managed in a
clever way, so that if the definition of what a certain group contains
gets updated by the package manager, your volumes will get updated too,
on the next puppet run.
|
| |
|
|
|
|
|
|
| |
This is useful for environments that don't include fping.
Usage of fping (or similar) is still recommended to make you less likely
to get an error on volume creation if one host isn't up.
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
It seems the seluser is now server_t. If someone thinks it should be
different, please let me know!
I think the --xml output of gluster volume status --xml <v> changed.
|
| |
|
| |
|
|
|
|
| |
See: https://bugzilla.redhat.com/show_bug.cgi?id=987555 for info.
|
|
|
|
|
|
|
|
|
|
|
| |
* Rename gluster::client to gluster::mount
* Add support to gluster::mount
* Add client machines and mounts to vagrant setup
* Fixed version interface for gluster::mount and gluster::server
* Improved firewall support for gluster::mount
* Update examples to use gluster::mount instead of gluster::client
* Update documentation
* Other small fixes
|
|
|
|
|
| |
Did this at the last minute for the "glusterfest". John Mark Walker now
owes me two t-shirts, and a polo. Now it's in the permanent record ;)
|
|
|
|
| |
Puppet-Gluster, now with Vagrant! - Initial release. Happy hacking!
|
| |
|
|
|
|
|
|
| |
If you choose your IP addresses manually, this won't affect you. If
you're automatically deploying Puppet-Gluster with Vagrant, this will
probably be the missing piece that makes your build more automatic.
|
|
|
|
|
|
|
| |
* If VIP comes and goes, the create script gets added/deleted too.
* If VIP isn't present on first run (it usually isn't) then the
Exec['again'] won't get run because it's inside the VIP check.
* This also consolidates the two identical conditional blocks.
|
|
|
|
| |
I've updated wrapper.pp too, but I haven't tested it recently.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds VRRP integration to puppet-gluster. All you need to do is
set vrrp => true, and set a vip, and the rest should happen
automatically. The shared keepalived password is built by a distributed
password selection algorithm that I made up. Feel free to review this if
you'd like. It's probably as secure as your puppet server and clients
are. If you'd prefer to specify each token manually, you can do so in
the gluster::host password argument, or you can set one global vrrp
password in the gluster::server or gluster::simple classes. There's a
chance that you'll see a bit of VRRP flip-flop when you add/remove hosts
because the distributed password should change. The benefit is that by
default you don't need to set or manage any of those passwords!
This doesn't add firewalling so that the VIP can be used by clients.
|
|
|
|
| |
Avoids any chance of a race due to modifying the file in place.
|
|
|
|
|
|
|
| |
* This will make magic things happen faster.
* This doesn't give you an option to disable it.
* This doesn't let you set the timeout.
* This isn't necessarily complete. There might be more notify's needed.
|
| |
|