DEVOPS WEEKLY ISSUE #167 - 16th March 2014
Lots of pretty in-depth discussions about configuration management, or at least configuration management tooling, this week. Lots of differing opinions, solid theory, innovation in low level systems and more to mull over.
Sponsor
Devops Weekly is sponsored by Brightbox Cloud - launch cloud servers in multiple UK datacentres in seconds…
http://brightbox.com/devopsweekly
News
A fantastic two part blog post about bringing continuous deployment and configuration management together. Lots of theory, discussion of how containers and microservices fit in and points about operators and developers prioritising seemingly different things.
http://markburgess.org/blog_cd.html
http://markburgess.org/blog_cd2.html
Building software systems out of many small services is becoming increasingly common. This post delves into what a microservices architecture is, why it’s an important pattern and also what it might look like.
http://martinfowler.com/articles/microservices.html
Configuration Management isn’t stupid, but it should be according to this next post. Some tools introduce (rather than address) complexity, determinism and reproducibility in systems and this post argues that better ones are needed to fix the problem.
http://blog.hatofmonkeys.com/blog/2014/03/15/configuration-management-isnt-stupid/
And another post riffing on why current configuration management tools aren’t perfect, focusing on the Nix package management tool as a potential solution.
https://www.domenkozar.com/2014/03/11/why-puppet-chef-ansible-arent-good-enough-and-we-can-do-better
Introducing devops practices into an organisation needs some understanding of how to bring about change. This next slide deck is a nice introduction to being a change agent, with lots of tips about what to expect and how to get people on-board.
http://www.slideshare.net/john.clapham/reluctant-change-agents-guide
A description of the human moments experienced during a complex systems failure, and a case made for these being consistent between typical web operations work and other domains. The better we understand error, hopefully the better we’ll be able to deal with it.
http://www.kitchensoap.com/2014/03/13/high-tempo-high-consequence/
Vagrant has a new release out with lots of new features. As well as Hyper-V support and rsync for shared folders, Vagrant now has an inbuilt box hosting service called Vagrant Cloud.
http://www.vagrantup.com/blog/vagrant-1-5-and-vagrant-cloud.html
https://vagrantcloud.com/
A detailed look at why it’s difficult to get at memory usage details from within an LXC container, along with how this might be resolved in the future.
http://fabiokung.com/2014/03/13/memory-inside-linux-containers/
A nice example of analysing nginx logs with pandas and matplotlib. The ipython notebook formats nicely shows off the results as it goes along, including nicely formatted graphs of the results.
http://nbviewer.ipython.org/github/grokcode/ipython-notebooks/blob/master/nginx-log-analysis.ipynb
Events
A postmortem analysis, conducted in an open, blameless way, is the best way to learn from outages (and other failures and near-misses). April 15th at #ChefConf will feature a full-day workshop with Dave Zwieback, covering the theory and practice of conducting and participating in awesome postmortems.
https://chefconf2014.busyconf.com/bookings/new
Tools
Gunnery is described as a remote execution frontend. It’s a web based interface for executing commands on groups of servers, and features nice integration with ant, phing, fabric, capistrano, make and puppet out of the box.
http://eyjafjallajokull.github.io/gunnery/
https://github.com/Eyjafjallajokull/gunnery