----- Original Message ----- > From: "Tom Poulton" <poulton...@gmail.com> > To: puppet-users@googlegroups.com > Sent: Monday, May 13, 2013 4:06:56 PM > Subject: Re: [Puppet Users] MCollective deployment pattern > > Thanks for the quick reply > > The -W environment=foo tip is very useful and definitely solves one
see http://docs.puppetlabs.com/mcollective/reference/basic/basic_cli_usage.html for the details on the cli, discovery etc, thats a little primer to get you going > problem. I appreciate that the synchronous part could get pretty nasty, > rather you than me :) In the meantime have you got any tips on the best > (most reliable) way to check up on triggered runs, you mentioned inspecting > them or querying my reporting infrastructure: to be honest I'm > pretty familiar with puppet in terms of writing modules etc, but I haven't > really looked into the reporting or querying side of things at all, and > I'm definitely a newcomer to MCollective, feel free to just dump a load of > keywords and I can google around if that's easier? > > We're running Puppet Open Source but we do have Puppet Dashboard running if > that offers any querying options against the DB or something? well lets say your deployment updates some package, or you have a define like myapp{"acme": ensure => 1.2.3} and your upgrade is gong to do that, then this is something you can interrogate via mco to figure out the state of things. but that sux. if you know you dont manage mcollective and these deploy runs tend to have a reasonable short run time that doesnt fluctuate hugely, I'd just write a little agent that runs puppet in the foreground for you to do it synchronously there's nothing inherently wrong with running puppet synchronously like this as long as you know you wont be restarting mco or doing stuff that fluctuate in times heavily. alternative you can use the config_version feature in puppet and set the current catalog version to lets say a git tag or svn revision and interrogate the number via the last_run_summary action on the puppet agent which will show you the catalog version of the most recent run or puppet reports etc, there's an annoying amount of solutions to this problem and the right one depends on your environment unfortunately > > Thanks > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
