| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| | |
|
| |
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Elegant system using a Makefile to build base image "boxes".
It's recommended that you use the pre-built boxes, but the
infrastructure is being provided here for completeness.
You'll probably want to set the $(OUTPUT) variable first. Then use the
'box' target (make box) to produce output into the $(OUTPUT) directory.
|
| |
|
|
| |
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.
|
| |
|
|
|
| |
Not sure how this bug ever happened. Did the format of the xml ever
change? In any case, now it's squashed.
|
| |
|
|
| |
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.
|
| | |
|
| | |
|
