[Devops] Follow-up links regarding the Meetup yesterday

[Stefan Schlesinger]

	Hi

thank you for the links Aaron.

I'd also like to point out, there was some discussion about Chefs inherent
ability to process recipes from top to bottom and how to overcome this missing
feature in Puppet.

RI.Pienaar wrote about a nice module pattern, which lets you structure modules
likewise, without caring too much about dependencies at each resource
declaration.

http://www.devco.net/archives/2009/09/28/simple_puppet_module_structure.php

Another point which I missed in the comparison, was 'Hiera' (which was added to
the Puppet source tree with version 3.0). Basically it adds similar
functionality as Chef's json attributes. In since Puppet 3.0 it looks up class
parameters automatically.

A..

class ntp ($timeservers) {}

..would issue a hiera lookup for $ntp::timeservers and thus allows module
authors to provide sane defaults, which can easily be overwritten when you want
to integrate the module into your environment.

Stefan

On Mar 19, 2013, at 3:29 PM, Aaron Zauner wrote:

> marciej described a pattern in which he usually reacts to on-call-duty messages and if it might be possible to automate initial debugging.
> there is a very nice article in ACM queue by brendan gregg on this topic (performance analysis/debugging, which i recommend reading: http://queue.acm.org/detail.cfm?id=2413037
> 
> couple of other things that came up during conversations (some have been posted earlier already on this list - i guess):
> http://rspec-puppet.com/
> http://puppet-lint.com/
> http://projects.puppetlabs.com/projects/cucumber-puppet/wiki
> http://docs.puppetlabs.com/guides/style_guide.html (e.g. Modulefile, general style recommendation)
> 
> http://cfengine.com/
> https://cfengine.com/network-appliances
> 
> http://www.amazon.com/Continuous-Delivery-Deployment-Automation-Addison-Wesley/dp/0321601912
> 
> […]
> 
> Aaron