Puppet Camp 2012: Boston, Massachusetts

Puppet Camp is a community oriented gathering of Puppet users and developers. You’ll have the opportunity to network with a diverse group of Puppet users, benefit from insightful lectures delivered by prominent community members, and be able to share experiences and discuss potential implementations of Puppet during our attendee generated breakout sessions.
Puppet Camp Boston is hosted in conjunction with the Boston DevOps Meetup .
Our event space has been graciously donated by Microsoft.
9:00am… Show more - Welcome from Puppet Labs from Community Manager Mike Stahnke
10:00am - Pascal Hahn, Nokia
Nokias' Location and Commerce division is heavily utilizing puppet to manage services in multiple datacenters around the world. Last year we set out to build a multi tenant puppet-infrastructure to provide deployment services to a multitude of R&D teams with a really diverse set of services that they develop. Oliver Hookins gave a talk last year on this and we came a long way from there. Uptake of the platform has been stunning ever-since. During the last year we had to overcome challenges around scalability due to growth in many areas: - Amount of teams we support - Growth of the machine-base - Diversity of customers - Puppet-infrastructure - Test-infrastructure
10:40am - Barry Jaspan - Aquia
Continuous Integration when Infrastructure is the Product Continuous Integration and Deployment are powerful approaches for improving software development and release engineering, but they are easier to apply in some domains than others. It is pretty straightforward to release changes to HTML, CSS, JavaScript, and web business logic 37 times per day. Releases containing database schema updates are a little trickier, but less frequent. You have to manage your application's infrastructure, too, but it doesn't change that often, and that is what Puppet is for! The story is different when your product is the infrastructure running other people's applications. Releases involve reconfiguring of the servers or the daemons, possibly restarting them. You have to update them in a carefully choreographed way to maintain high availability, and you cannot schedule downtime for thousands of customers who really don't even want to know that a release is happening. You can't even upgrade all your servers "at once" because when there are 3000+ of them, there is no such thing as "at once", so running multiple versions simultaneously is standard procedure. In this talk, I'll describe some of the techniques Acquia Cloud uses to handle these issues and still release multiple times per day.
11:20am - Robert Terhaar, Atlantic Dynamic
Puppet in the Cloud: How you can best utilize Puppet to manage your cloud infrastructure.

Show less