Hi All
I am looking to report on all servers that are "Out of sync".
Currently we run puppet in noop mode hourly, and so we get reports saying
there are X resources Out of sync.
Unfortunately, because it is a noop, puppet reports those X resources out of
date as successfully applied, which makes Puppet Dashboard (downloaded the
HEAD this morning) think that everything is good and green, which isn''t
what
I was hoping for.
- - !ruby/sym applied
- Applied
- 12
- - !ruby/sym out_of_sync
- Out of sync
- 12
How do others report on "Out of sync", and will/does Dashboard (or
Foreman)
support reporting noop Out of sync as an warning? My google, and reading of
issues/roadmaps were not illuminating
Thanks
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Hi John, On Tue, Sep 21, 2010 at 10:44 PM, John Warburton <jwarburton@gmail.com>wrote:> Hi All > > I am looking to report on all servers that are "Out of sync". > > Currently we run puppet in noop mode hourly, and so we get reports saying > there are X resources Out of sync. >> Unfortunately, because it is a noop, puppet reports those X resources out > of date as successfully applied, which makes Puppet Dashboard (downloaded > the HEAD this morning) think that everything is good and green, which isn''t > what I was hoping for. > > - - !ruby/sym applied > - Applied > - 12 > - - !ruby/sym out_of_sync > - Out of sync > - 12 > > How do others report on "Out of sync", and will/does Dashboard (or Foreman) > support reporting noop Out of sync as an warning? My google, and reading of > issues/roadmaps were not illuminating >A ticket already exists for this feature. It may be worth noting that a differentiation between applied changes as opposed to reported changes (with noop) would be useful. http://projects.puppetlabs.com/issues/3535> Thanks > > John > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Thanks Dan The subject line to Feature #3535 wasn''t obvious that was what I was looking for. I have updated the feature with my reasons we need an out of sync report Regards John On 27 September 2010 07:31, Dan Bode <dan@puppetlabs.com> wrote:> Hi John, > > On Tue, Sep 21, 2010 at 10:44 PM, John Warburton <jwarburton@gmail.com>wrote: > >> Hi All >> >> I am looking to report on all servers that are "Out of sync". >> >> Currently we run puppet in noop mode hourly, and so we get reports saying >> there are X resources Out of sync. >> > > > > >> Unfortunately, because it is a noop, puppet reports those X resources out >> of date as successfully applied, which makes Puppet Dashboard (downloaded >> the HEAD this morning) think that everything is good and green, which isn''t >> what I was hoping for. >> >> - - !ruby/sym applied >> - Applied >> - 12 >> - - !ruby/sym out_of_sync >> - Out of sync >> - 12 >> >> How do others report on "Out of sync", and will/does Dashboard (or >> Foreman) support reporting noop Out of sync as an warning? My google, and >> reading of issues/roadmaps were not illuminating >> > > A ticket already exists for this feature. It may be worth noting that a > differentiation between applied changes as opposed to reported changes (with > noop) would be useful. > > http://projects.puppetlabs.com/issues/3535 > > > >> Thanks >> >> John >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To post to this group, send email to puppet-users@googlegroups.com. >> To unsubscribe from this group, send email to >> puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- John Warburton Ph: 0417 299 600 Email: jwarburton@gmail.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
John Warburton wrote:> Thanks Dan > > The subject line to Feature #3535 wasn''t obvious that was what I was > looking for. > > I have updated the feature with my reasons we need an out of sync report >John Have you also seen the pseudo-Tripwire audit capability introduced in 2.6.0? http://www.puppetlabs.com/blog/all-about-auditing-with-puppet/ That might interest too. James Turnbull -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On 27 September 2010 13:09, James Turnbull <james@puppetlabs.com> wrote:> > Have you also seen the pseudo-Tripwire audit capability introduced in > 2.6.0? > > http://www.puppetlabs.com/blog/all-about-auditing-with-puppet/ > > That might interest too. > > Thanks JamesNo - I haven''t seen the audit capability - but it looks like what I am needing. It isn''t mentioned in the Release Notes. Should I be looking somewhere else? Cheers John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Sun, 26 Sep 2010, James Turnbull wrote:> Have you also seen the pseudo-Tripwire audit capability introduced in 2.6.0? > http://www.puppetlabs.com/blog/all-about-auditing-with-puppet/It would have been nice if this had been documented somewhere. The release notes for puppet-2.6.0 at <http://projects.puppetlabs.com/projects/1/wiki/Release_Notes> do not mention "audit". The metaparameters documentation at <http://docs.puppetlabs.com/references/latest/metaparameter.html> does not mention "audit". --apb (Alan Barrett) -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Alan Barrett wrote:> On Sun, 26 Sep 2010, James Turnbull wrote: >> Have you also seen the pseudo-Tripwire audit capability introduced in 2.6.0? >> http://www.puppetlabs.com/blog/all-about-auditing-with-puppet/ > > It would have been nice if this had been documented > somewhere. The release notes for puppet-2.6.0 at > <http://projects.puppetlabs.com/projects/1/wiki/Release_Notes>I apologise - I thought it was in the Release Notes. There was a lot of content in 2.6.0 and this one must have been missed. It is now: http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes#Audit+Metaparameter> do not mention "audit". The metaparameters documentation at > <http://docs.puppetlabs.com/references/latest/metaparameter.html> does > not mention "audit".No sure why it''s not showing up in the documentation. I will take a look today. Regards James Turnbull -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
----- "James Turnbull" <james@puppetlabs.com> wrote:> > do not mention "audit". The metaparameters documentation at > > <http://docs.puppetlabs.com/references/latest/metaparameter.html> > does > > not mention "audit". > > No sure why it''s not showing up in the documentation. I will take a > look today.the ''latest'' documentation isnt. see http://docs.puppetlabs.com/references/2.6.1/metaparameter.html -- R.I.Pienaar -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
R.I.Pienaar wrote:> ----- "James Turnbull"<james@puppetlabs.com> wrote: > >>> do not mention "audit". The metaparameters documentation at >>> <http://docs.puppetlabs.com/references/latest/metaparameter.html> >> does >>> not mention "audit". >> No sure why it''s not showing up in the documentation. I will take a >> look today. > > the ''latest'' documentation isnt. >Ah okay - it looks like the deployment script isn''t updating the symlinks. I will fix shortly. Regards James Turnbull -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Mon, 27 Sep 2010, James Turnbull wrote:> I apologise - I thought it was in the Release Notes. There was a > lot of content in 2.6.0 and this one must have been missed. > > It is now: > > http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes#Audit+MetaparameterThanks. --apb (Alan Barrett) -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.