| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
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 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).
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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!
|
| |
|
|
|
| |
Support for other operating systems will have to come later, even if
this needs to be refactored. For now, CentOS/RHEL are automatic.
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Appropriate firewalling support is a hard thing in gluster if you take
in to account all the bootstrapping problems of what needs to be open
before subsequent things can work. Hopefully this patch is a good first
step in finally doing the right things.
|
| | |
|
| |
|
|
| |
At the moment, this is redundant, and not needed.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
bodepd!
|
| | |
|
| | |
|
| |
|
