[Gluster-users] Automatically Deploying GlusterFS with Puppet-Gluster+Vagrant!

[Kaushal M]

I finally got vagrant working. Had to roll back to v1.3.5 to get it
working. I can get the puppet vm up, but the provisioning step always
fails with a puppet error [1]. Puppet complains about not finding a
declared class. This happens with and without vagrant-cachier. I'm
using the latest box (uploaded on 22-Jan).

~kaushal

[1] - https://gist.github.com/kshlm/a39eb61c561a5587cefd

On Tue, Jan 21, 2014 at 10:14 PM, James <purpleidea at gmail.com> wrote:
> Top posting because it's bed time...
>
> I just pushed a HUGE bunch of changes... There are more new features,
> rather than some magical fix to make vagrant run everywhere...
>
> In any case, it adds in easy client support. So you can now do:
>
> $ vagrant up puppet
> $ sudo -v && vagrant up annex{1..4} --gluster-replica=2
> --gluster-clients=2 --no-parallel
> $ # wait until volume has been started... maybe there's an easy ssh
> spin lock someone can write
> $ vagrant up client{1..2} # boom, now you have two clients to use to
> throw workloads at. Default mnt path is /mnt/gluster/<volname> If this
> should be different, let me know.
>
> Cheers,
> James
>
>
> On Tue, Jan 21, 2014 at 4:13 AM, James <purpleidea at gmail.com> wrote:
>> On Tue, 2014-01-21 at 03:53 -0500, James wrote:
>>> >
>>> > I had to modify your patch for vagrant-cachier as the plugin has
>>> been
>>> > updated to 0.5.1. After this, I tried to get the puppet vm up and
>>> > failed.
>>> I could simply exclude vagrant-cachier from the default setup. It's
>>> only
>>> an optimization, and isn't required.
>>> I'll patch this to change the default shortly.
>>
>> Try the latest master. It includes this patch:
>>
>> https://github.com/purpleidea/puppet-gluster/commit/bee4993d4304730da27424dbdc73819b99d8ab5b
>>
>> Let me know if it fixes your issue.
>>
>> James
>>