Understood. But, we have some real good troubleshooters here.
And we want to get at core fixes. Not just log-examination, esoteric thought and bandaids. > On Nov 26, 2013, at 12:49 PM, Christopher Wood <[email protected]> > wrote: > > (inline) > >> On Tue, Nov 26, 2013 at 10:43:31AM -0800, Stuart Cracraft wrote: >> We have this exact same requirement. >> Enforce a non-changing policy on the cloud, avoid automatic >> drift-prevention, await errors and reports, >> track down cause, fix root cause, apply puppet manifests to right things >> back, etc. >> Using Puppet to bandaid things without root-cause drill-down/post-mortem, >> is unwise!!!! > > I don't see how it's wise to let configuration deviations loiter in your > systems until a human has the time to manually fix them. This applies even > more if you're working at scale. Surely the ticket generated from (whatever > is monitoring agent runs that unpredictably change things) will still be > there once your configs are back in conformance? > > Short form would be that I think you'll experience fewer pain points if you > let puppet enforce your configuration like it's designed to. > >> We need a simple report-formatting mechanism like David says! >> >> On Tuesday, November 26, 2013 8:54:03 AM UTC-8, David Portabella wrote: >> >> puppet agent --verbose shows a verbose output of the changes done by >> puppet, such as: >> >> notice: >> >> /Stage[main]/Logstash::Config/Logstash::Configdir[agent]/File[/etc/logstash/agent/config]/owner: >> owner changed 'root' to 'logstash' >> notice: /Stage[main]/Varnish/Service[varnish]/ensure: ensure changed >> 'stopped' to 'running' >> >> I'd need to make some analysis about these changes, but it is not >> trivial to correctly parse this output. >> is there an option to get an structured version of this output (such as >> in xml or yaml)? >> so that I can make queries such as: >> - list all the files that have changed >> - list all the services that changed from stopped to running. >> ... >> >> yes, i can use sed and the like as a temporal workaround, but I'd need >> to have a robust approach. >> >> option1: maybe there is a tool that correctly parses this output? >> option2: or maybe there is a "puppet agent" equivalent command that >> directly produces a structured output? >> >> otherwise, how much time would it required to implement option2 (i am a >> software developer, and a puppet-user (not currently a >> puppet-developer)? >> >> Regards, >> David >> >> -- >> 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 view this discussion on the web visit >> >> [1]https://groups.google.com/d/msgid/puppet-users/5907f644-2285-4298-9a07-3d5e8de63a24%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/5907f644-2285-4298-9a07-3d5e8de63a24%40googlegroups.com >> 2. https://groups.google.com/groups/opt_out > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/cHpZlKkPmr4/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/20131126204924.GA4749%40iniquitous.heresiarch.ca. > 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/696AE1AA-FE9D-4788-AE1E-0EC6FEBB03A7%40me.com. For more options, visit https://groups.google.com/groups/opt_out.
