| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Introduced a split between repo management and version choosing.
You can now:
* Choose a package version or leave it at the default (latest).
If you choose a package version it must include the release string.
eg: in foobar-3.2.1-42.el6 the release is 42.el6
This doesn't check to see if your version is valid!
* Choose whether you want a gluster repo added automatically.
If you did specify a version, it will pick the correct repo.
This doesn't check that the repo for your os/version exists!
|
|
|
|
| |
This should help users figure out they have a DNS problem sooner.
|
|
|
|
|
| |
Support for other operating systems will have to come later, even if
this needs to be refactored. For now, CentOS/RHEL are automatic.
|
| |
|
|
|
|
|
|
|
| |
If a user decides to manually set a host UUID, then save that UUID so
that subsequent removal of manual UUID settings won't cause the UUID to
change. This is useful if you want to start using automatic UUID's when
you weren't previously.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
This lets us specify the VIP in ::server, and inherit it in all volumes.
|
| |
|
|
|
|
|
|
| |
Puppet-gluster now correctly picks the operating-version value from a
table of known version -> value correspondences. Future value additions
should be added to this table.
|
|
|
|
|
|
|
|
|
|
| |
This is usually only relevant right after initial peering if we're doing
a hot (clean) puppet build. This probably happens because puppet is
eager to run things as soon as possible, and after glusterd is
restarted, it takes a short moment for glusterd to see the other nodes
as fully peered. Ideally puppet should really only check the $onlyif
conditions *right* before it runs the command. I think that it might be
cheating here and running it in parallel slightly before... Who knows.
|
|
|
|
|
|
| |
This moves the command into a separate file. This also adds temporary
saving of stdout and stderr to /tmp for easy debugging of command
output.
|
|
|
|
| |
It seems the propagate up isn't 100% reliable.
|