Scaling Chef at Facebook with Phil Dibowitz

The Meetup tonight will start at 6:30pm, and we will have food and beverages thanks to our amazing sponsor Ooyala (http://www.ooyala.com/)!

Agenda:
6:35pm - 7:00pm: Food, networking, etc.
7:00pm - 8:30pm: Phil's presentation + time for Q&A
8:30pm - 9:00pm: more networking for people who want to hangout more.

----

Earlier this year Phil Dibowitz (http://www.phildev.net/) presented at ChefConf (http://chefconf.opscode.com/chefconf/) how Facebook is using Chef and what challenges they faced when migrating from cfengine. We are very excited to have Phil (https://twitter.com/ThePhilD) present at our meetup group and this should be a great opportunity to learn more about Facebook's lessons learned when implementing chef at such a large scale.

For many years, Facebook managed its systems with cfengine2. With many individual clusters over 10k nodes in size, a slew of different constantly-changing system configurations, and small teams, this system was showing its age and the complexity was steadily increasing, limiting its effectiveness and usability. It was difficult to integrate with internal systems, testing was often impractical, and it provided no isolation of configurations, among many other problems. After an extensive evaluation of the tools and paradigms in modern systems configuration management – open source, proprietary, and a potential home-grown solution – we built a system based on Chef.

The evaluation process involved understanding the direction we wanted to take in managing the next many iterations of systems, clusters, and teams. More importantly, we evaluated the various paradigms behind effective configuration management and the different kinds of scale they provide. What we ended up with is an extremely flexible system that allows a tiny team to manage an incredibly large number of systems with a variety of unique configuration needs. In this talk we will look at the paradigms behind the system we built, the software we chose and why, and the system we built using that software. Further, we will look at how the philosophies we followed can apply to anyone wanting to scale their systems infrastructure.