| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
| |
This makes it easier to test and try out these features!
|
| | |
|
| | |
|
| |
|
|
|
| |
Since different brick layouts are now implemented, it makes sense to
remove any remaining traces of the algorithmic work from the fact...
|
| |
|
|
|
|
|
|
|
|
| |
* 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.
|
| | |
|
| |
|
|
| |
This option is available in newer vagrant-libvirt.
|
| |
|
|
| |
(I think it's a resource hog...)
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
Thanks: rwmjones in #libguestfs for help and discussion.
|
| | |
|
| |
|
|
| |
This adds the --gluster-replica=N flag to the 'vagrant up' command.
|
| |
|
|
|
|
|
|
|
|
|
| |
* 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
|
| |
|
|
|
|
|
| |
Cachier needs at least one patch to work properly with vagrant-libvirt.
This patch is: https://github.com/fgrehm/vagrant-cachier/pull/68
The author has said he likes the patch, but has seemingly gone awol.
Until this is merged or gets a new maintainer, we'll disable cachier.
|
| | |
|
| |
|
|
|
| |
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 ;)
|
| | |
|
| | |
|
| |
|
|
| |
This patch adds a --gluster-firewall=true|false option for vagrant.
|
