| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
This isn't necessary, but is more correct. I realized how I could do
this, and have now implemented it.
|
|
|
|
|
|
|
| |
This isn't needed anymore because of:
https://github.com/pradels/vagrant-libvirt/commit/0ac7498f4d73d4100462ac34b5cd89c308622fc5
Let me know if I broke anything or if this still works perfectly!
|
|
|
|
| |
Thanks to victorg for reminding me to bump the version in the Modulefile.
|
|
|
|
| |
New git project at: https://github.com/purpleidea/vagrant-builder
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Like "Back to the Future" (the movie), we can only affect the future,
unless we go back to the past (rebasing) to add this feature earlier. So
this should only work for versions that are newer that 0.0.3, since I
don't want to rebase git master.
|
| |
|
| |
|
|
|
|
|
| |
In newer puppet versions the parser changed... I think it's requiring
code in parse order now.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This patch is dedicated to Gilles who didn't like the findmnt patch
initially, but now loves it because it is cross distro friendly :)
Thanks for all your time testing Puppet-Gluster... More eyes helps!
|
|
|
|
|
|
| |
The Fedora changes are specific to F20 era changes. If you are
interested in having this compatible with an old version of Fedora, you
can drop in a Fedora version specific yaml file.
|
|
|
|
|
| |
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 program paths.
|
|
|
|
| |
This patch includes package names.
|
|
|
|
|
|
|
|
| |
Don't let the small version number fool you. Puppet-Gluster is quite
grown up :)
Thanks to Gilles for lots of testing.
Thanks to Andrea for working on packaging.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This wasn't necessary in previous versions of vagrant-libvirt because
this option specified the uri, and the domain type defaulted to kvm. In
newer releases, you have to specify this for performance, otherwise it
will default to qemu software only virtualization. This depends on:
https://github.com/pradels/vagrant-libvirt/commit/67734f003273d3fadcca3893c994f691fee1b629
also available at:
https://github.com/purpleidea/vagrant-libvirt/commit/67734f003273d3fadcca3893c994f691fee1b629
|
| |
|
|
|
|
|
|
|
|
|
|
| |
You can easily configure this by settings the disks integer in the
puppet-gluster.yaml file or with the --gluster-disks= parameter.
If this is set to the default of zero (0) then no disks are added.
This patch depends on:
https://github.com/pradels/vagrant-libvirt/issues/162
|
|
|
|
| |
Useful for setups where getting nfs sync working is a PITA.
|
| |
|
|
|
|
|
|
| |
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).
|
|
|
|
|
|
|
| |
This adds the ability to do LVM thin provisioning. If you haven't fully
read 'man 7 lvmthin' then please do as this will answer most of your
questions. LVM thin provisioning is used for doing one form of GlusterFS
snapshots.
|
|
|
|
| |
Although if you remove all the features, it's not as awesome anymore :)
|
|
|
|
|
|
| |
There could be some cases when you want to omit these choices.
Bug reported by Gilles Dubreuil.
|
|
|
|
|
| |
This is actually valid in Puppet 3.x, but removing the colons doesn't
break the 3.x tree.
|
|
|
|
|
| |
This lets you set which management network gets used, and is useful if
you need to avoid conflicts with a network on your host.
|
|
|
|
|
|
|
| |
(I guess this means I'm now a vagrant os image maintainer.)
NOTE: you can create your own personal scripts in builder/versions/ !
(See the template.sh file there for more information.)
|
|
|
|
| |
Special thanks to Kaleb Keithley for his wizard RPM skills.
|
|
|
|
|
|
| |
I wasn't able to test this patch, for lack of hardware at the moment. A
patch for: https://github.com/pradels/vagrant-libvirt/issues/162 would
also help solve my testing issue. Please report any issues!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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!
|