Hi,
The style in which I want to run Puppet is:
1) The agent daemon does not take any actions but is running
so that it detects any changes to managed files, directories, services,
packages, etc. as defined in the manifests
2) Only a manual action: "e.g. puppet apply init.pp" is required
to initiate any change.
Is there anything beyond the above other than simply placing --noop
in the puppet agent call in /etc/init.d/puppet, i.e.
:
daemonopts="--pidfile $pidfile --noop
:
start() {
:
daemon $daemonopts $puppetd ${PUPPET_OPTS} ${PUPPET_EXTRA_OPTS}
:
:
and using
puppet apply init.pp
or an MCollective equivalent.
Stuart
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/d11c081a-dbf9-4db5-a541-7d236fd816fa%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
On Mon, Nov 25, 2013 at 11:04:40AM -0800, Stuart Cracraft wrote:> Hi, > The style in which I want to run Puppet is: > 1) The agent daemon does not take any actions but is running > so that it detects any changes to managed files, directories, > services, > packages, etc. as defined in the manifestsWhile I don''t know the answer, I''m curious why you would prefer this over enforcing the correct configuration in the first place. Would you care to expound?> 2) Only a manual action: "e.g. puppet apply init.pp" is required > to initiate any change. > Is there anything beyond the above other than simply placing --noop > in the puppet agent call in /etc/init.d/puppet, i.e. > : > daemonopts="--pidfile $pidfile --noop > : > start() { > : > daemon $daemonopts $puppetd ${PUPPET_OPTS} ${PUPPET_EXTRA_OPTS} > : > : > and using > puppet apply init.pp > or an MCollective equivalent. > Stuart > > -- > 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+unsubscribe@googlegroups.com. > To view this discussion on the web visit > [1]https://groups.google.com/d/msgid/puppet-users/d11c081a-dbf9-4db5-a541-7d236fd816fa%40googlegroups.com. > For more options, visit [2]https://groups.google.com/groups/opt_out. > > References > > Visible links > 1. https://groups.google.com/d/msgid/puppet-users/d11c081a-dbf9-4db5-a541-7d236fd816fa%40googlegroups.com > 2. 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+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20131125195342.GA497%40iniquitous.heresiarch.ca. For more options, visit https://groups.google.com/groups/opt_out.
Notes with ++ On Monday, November 25, 2013 11:53:42 AM UTC-8, Christopher Wood wrote:> > On Mon, Nov 25, 2013 at 11:04:40AM -0800, Stuart Cracraft wrote: > > Hi, > > The style in which I want to run Puppet is: > > 1) The agent daemon does not take any actions but is running > > so that it detects any changes to managed files, directories, > > services, > > packages, etc. as defined in the manifests > > While I don''t know the answer, I''m curious why you would prefer this over > enforcing the correct configuration in the first place. Would you care to > expound? > >++ Hi Chris. ++ The correct configuration in the first place is put in with Puppet. ++ We just don''t want Puppet, initially, to be running classes regularly after the ++ initial configuration - but instead just report. The reasons are: trust in the product, ++ ensuring tracking and repair of root cause of issue in app, database, OS, rather ++ than simply "covering it with Puppet". One could simply use the logfile generated ++ to try to track it down, after Puppet had fixed it, and/or create some massive ++ class for forensic tracking. ++ Generally it is also a distrust of automation, busy fingers of superusers, and ++ a distrust even of the operating system itself and stray gamma-rays. ++ I kid you not.> 2) Only a manual action: "e.g. puppet apply init.pp" is required > > to initiate any change. > > Is there anything beyond the above other than simply placing --noop > > in the puppet agent call in /etc/init.d/puppet, i.e. > > : > > daemonopts="--pidfile $pidfile --noop > > : > > start() { > > : > > daemon $daemonopts $puppetd ${PUPPET_OPTS} ${PUPPET_EXTRA_OPTS} > > : > > : > > and using > > puppet apply init.pp > > or an MCollective equivalent. > > Stuart > > > > -- > > 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...@googlegroups.com <javascript:>. > > To view this discussion on the web visit > > [1] > https://groups.google.com/d/msgid/puppet-users/d11c081a-dbf9-4db5-a541-7d236fd816fa%40googlegroups.com. > > > For more options, visit [2]https://groups.google.com/groups/opt_out. > > > > References > > > > Visible links > > 1. > https://groups.google.com/d/msgid/puppet-users/d11c081a-dbf9-4db5-a541-7d236fd816fa%40googlegroups.com > > 2. 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+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e6078c43-2c86-483c-8cdc-207ab6378122%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.