----- Original Message -----
> From: "Josh" <[email protected]>
> To: [email protected]
> Sent: Friday, April 12, 2013 10:01:13 AM
> Subject: [Puppet Users] MCollective and Puppet with periodic runs disabled
>
> Hi,
>
> I have looked all over the place and can't seem to find a complete answer
> to my query
>
> I am setting up MCollective to run alongside my puppet deployment and am
> having some problems getting it to play as I want it to
>
> Basically, I need to make sure that puppet NEVER makes any changes without
> them being triggered by someone (I honestly can't see how anyone would ever
> want that not to the the case but there you go).
>
> I was going to just run puppet in cron in --noop mode for monitoring and
> manually run it for changes, but the 'mco rpc puppet' command requires that
> it be running in daemon mode. Thats fine and working but I am unable to
you do not need to have puppet running for the agent to work, just stop it
entirely and then trigger runs through mcollective - in that setup it will
happily pass custom arguments like --noop or --no-noop etc
if you did want periodic noop runs then just cron
puppet agent --daemonize --onetime --noop
> find a way to make this work and disable the puppet auto-runs. I found the
> --no-client option for the agent, which the docs seem to imply would do
> this for me, but when I use this option and trigger a puppet run it doesn't
> not report success back to MCollective client:
>
> With the daemon running normally I get:
> myserver : OK
> {:summary=>"Signalled the running Puppet Daemon"}
>
> With no-client mode (which does prevent the auto-runs) I get:
> myserver : execution expired
> execution expired
>
> It actually triggers a puppet run and all works, but I would like to know
> which hosts have sucessfully started a puppet run. Am I just misreading the
> error?
>
> Am I just missing something here? Is there another way of making sure that
> puppet never makes automated changes in daemon mode?
>
> I thought that maybe I could have the daemon in noop mode all the time and
> pass in the --no-noop flag but this gives:
> myserver : Cannot specify any custom puppet
> options when the daemon is running
> {:summary=> "Cannot specify any custom puppet options when the
> daemon is running"}
>
> I am using puppet 3.1 and the mcollective-puppet-common|agent|client plugin
>
> Any ideas welcome, I just seem to be going round in circles now
>
> Thanks
> Josh
>
> --
> 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 [email protected].
> To post to this group, send email to [email protected].
> 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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
