| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
| |
I've updated wrapper.pp too, but I haven't tested it recently.
|
| |
|
|
| |
This prevents an unnecessary template change on puppet runs.
|
| |
|
|
|
|
| |
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 should really be switched based on the operating gluster version. A
table of values and gluster versions is needed. The gluster version
could be created as a fact.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
If you would like to be ultra lazy and not specify any uuid's manually,
the puppet module can now generate them on your behalf. This will take
at least two puppet runs because of the distributed nature of gluster
and because the uuid facts must be exported to all the nodes for
peering.
Please note that if you rebuild a node from scratch, you probably won't
get the same UUID. You can either set it manually, or paste one in the
/var/lib/puppet/tmp/gluster/uuid/uuid file. Watch the formatting!
|
| |
|
