This Prezi was presented @: January 16th, 2013 (meetup / conversation details here)
In continuation to a Chef Introduction session we had last week on meetup, I thought a blog post was called for in order to emphasize the process of writing a recipie. And/Or working with chef in general as a buy product of that.
I will be using the basic "ntp" example Opscode uses on their wiki, but in order to understand the components of a recipe I will streach it a bit further in order to show the true power of Attributes and Templates.
Following the Fuse day (#6) and the very poor documentation and the amount of bugs found in the Chef Solo cookbooks for the Chef OSS server, I put together a set of script which will attempt to clear all the clutter around installing a Cehf OSS server.
As part of Tikal Fuse day #6 we planned to establish a management framework for a private cloud which will be used by the build management / Dev team(s).
The “building blocks” of this solution consists of:
Introduction to Chef, an open source systems configuration management and integration framework. It covers why people use Chef, benefits of using it and gives an overview of how it works.
A true story with a practical approach, emphasizing the milestones needed in order to shift from Continuous Integration to Continuous delivery & deployment. The presentation will cover a walk-through of methodologies & tools such as CI,CD combined with Jenkins, Jenkins MultiJob plugin and others.
There is some confution on what is the best method to use Chef [ Some may argue why do I need Chef Anyway ? - see this blog post ... ]
The following blog post should give you a "Kick Start" with Chef.
MercadoLibre - the "eBAY of latin america" - Managing 1,000 physical servers and more than 6,000 virtual machines ... must be automated - acording to this article OpenSource Chef is the ultimate orchestrator of this kind of deployments.