Testing catalog run on REAL node as git pre-push hook?

[Ryan Bowlby]

Hi All,

We'd like to do some form of testing of our module changes against
production nodes before being released into production. While somewhat
expensive it seems doing a noop against all nodes using the modified
module is the best way to determine unexpected results.

The question then is how are people implementing this? Any real world
talks or posts describing something like this would be great. Ideally
we want to put a git pre-push hook in place within the production
branch that performs a noop catalog run against the affected nodes and
reports results and determines if errors were encountered.

Thanks!!!
Ryan Bowlby

[Brian Troutwine]

It's not uncommon to run a small staging environment for just this
purpose. Have you evaluated something like that and found it wanting?

> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>

--
Brian L. Troutwine

[Dominik Zyla]

I agree with Brian.. We have three main environments (development, staging, production) for puppet master. All based on git branches. Having such setup you can use small staging environment for tests and while everything looks fine just merge it with your production. You can read more about such concept here: http://puppetlabs.com/blog/git-workflow-and-puppet-environments/

Also git flow may be helpful here if there are few sysadmins developing modules in your company.

Best,

--
Dominik Zyla
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)

On Saturday, 3 March 2012 at 04:41, Brian Troutwine wrote:

> It's not uncommon to run a small staging environment for just this
> purpose. Have you evaluated something like that and found it wanting?
>

> On Fri, Mar 2, 2012 at 7:26 PM, Ryan Bowlby <rbow...@gmail.com (mailto:rbow...@gmail.com)> wrote:
> > Hi All,
> >
> > We'd like to do some form of testing of our module changes against
> > production nodes before being released into production. While somewhat
> > expensive it seems doing a noop against all nodes using the modified
> > module is the best way to determine unexpected results.
> >
> > The question then is how are people implementing this? Any real world
> > talks or posts describing something like this would be great. Ideally
> > we want to put a git pre-push hook in place within the production
> > branch that performs a noop catalog run against the affected nodes and
> > reports results and determines if errors were encountered.
> >
> > Thanks!!!
> > Ryan Bowlby
> >
> > --
> > You received this message because you are subscribed to the Google Groups "Puppet Users" group.

> > To post to this group, send email to puppet...@googlegroups.com (mailto:puppet...@googlegroups.com).
> > To unsubscribe from this group, send email to puppet-users...@googlegroups.com (mailto:puppet-users...@googlegroups.com).

> > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>
>
>
>
>
> --
> Brian L. Troutwine
>

> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.

> To post to this group, send email to puppet...@googlegroups.com (mailto:puppet...@googlegroups.com).
> To unsubscribe from this group, send email to puppet-users...@googlegroups.com (mailto:puppet-users...@googlegroups.com).