My tool of choice is vagrant - it's super easy to create a Vagrantfile,
write a quick shell script that idempotently installs any required puppet
modules, and then run puppet itself. An older example is the
puppet-storyboard module: git checkout, vagrant up, and you're off to the
races.
(sorry, mail client failure)
On Tue, Aug 30, 2016 at 4:59 PM, Joshua Hesketh
wrote:
>
>
> On Fri, Aug 26, 2016 at 1:31 AM, Simon McCartney
> wrote:
>>
>>
>>
>>
> However, I'm not sure Vagrant provides a good solution for testing puppet
>> modules
On Fri, Aug 26, 2016 at 1:31 AM, Simon McCartney wrote:
>
>
>
>
However, I'm not sure Vagrant provides a good solution for testing puppet
> modules in isolation (I think it's great for the
> system-config/project-config scenario, where you want to see how applying
> the full
On Thu, Aug 25, 2016 at 7:48 AM, James E. Blair wrote:
> Joshua Hesketh writes:
>
>> There's probably further discussions here but I don't have enough knowledge
>> in this area to comment further. The aim though should be to make it easy
>> to
> 2) Is Vagrant a good fit for this? Otherwise should we consider an
> ansible-playbook to bootstrap an environment?
>
Just while you mention ansible, we've been looking at the infra-ansible[1]
& ansible-role-cloud-launcher[2] that Ricardo and others have been working
on, and as that project is
>
> We should look for a way to make developing, debugging and testing our
> puppet modules locally easier and more consistent.
> Short of bootstrapping an entire clone of openstack-infra, how do
>
This is pretty much what we do at the moment to maintain our internal
openstack-infra CI pipeline,
Joshua Hesketh writes:
> There's probably further discussions here but I don't have enough knowledge
> in this area to comment further. The aim though should be to make it easy
> to bootstrap a server with the module you're developing on so you can
> easily verify and
Hey all,
We should look for a way to make developing, debugging and testing our
puppet modules locally easier and more consistent.
Short of bootstrapping an entire clone of openstack-infra, how do
developers currently set up an environment to investigate how a puppet
module behaves? This brings