Building self-service on demand infrastructure with Puppet and VMware
Apr. 1, 2013•0 likes
Be the first to like this
Number of embeds
Download to read offline
"Building self-service infrastructure with Puppet and VMware: An intro to vSphere automation" by Cody Herriges of Puppet Labs at Puppet Camp London 2013. Find a Puppet Camp near you: https://puppetlabs.com/community/puppet-camp/
• A little about Operations at Puppet Labs.
• Why we choose on premise virtualization over
giving everyone EC2/Rackspace credentials.
• How we’re tackling the ramifications of that ^
2 | CONFIDENTIAL & PROPRIETARY
Who am I?
• Cody Herriges
• Operations Engineer
• Joined Puppet Labs in 2010
• Been using Puppet for 5.5 years
• Currently responsible for internal Virtualization
and Storage architectures.
4 | CONFIDENTIAL & PROPRIETARY
Puppet Labs Operations
• Three senior infrastructure engineers.
• Two desktop support engineers.
• Two Jr-ish infrastructure engineers.
• Both start while I am here in Europe.
5 | CONFIDENTIAL & PROPRIETARY
Our current strategy
• In the cloud?
• Our production web applications; forge,
redmine, ask, puppetlabs.com.
• All other production?
• On premise data center.
6 | CONFIDENTIAL & PROPRIETARY
• We were always chasing things that were
• We weren’t making any personal growth.
• No time to innovate.
• Infrastructure design and implementation never
7 | CONFIDENTIAL & PROPRIETARY
• Our implementation was holding us back.
• Rebuilt everything.
• Networking infrastructure provided by 1GbE Cisco
and 10GbE Juniper.
• Storage over iSCSI, backed by EMC VNX and
8 | CONFIDENTIAL & PROPRIETARY
• Operational over a capital investment.
• You get off the ground fast.
• Don’t have to worry about power, rack space,
cooling, cable management, networking.
• On demand unlimited resources at your finger
9 | CONFIDENTIAL & PROPRIETARY
• Performance is expensive.
• Scale is expensive.
• Redundancy can increase cost and/or
• You lose most of your control over networking.
10 | CONFIDENTIAL & PROPRIETARY
• Performance and scale per dollar is much less.
• Redundancy is loads simpler when you control
• Infrastructure can fit into the way you work
• During an outage there is always something
you can do about it.
11 | CONFIDENTIAL & PROPRIETARY
• You have to buy things.
• There is a datacenter to manage.
• Initial roll out will take time.
12 | CONFIDENTIAL & PROPRIETARY
• Other considerations
• If you have a physical office you’ll will have
some amount of internal infrastructure.
• There will always be a point where you out
grow that converted coat closet.
• The product you develop may require it.
13 | CONFIDENTIAL & PROPRIETARY
• vSphere hypervisor (ESXi) uses kickstart.
• Razor, capable of loading ESXi to non-volatile
• vCenter’s built in gPXE system, vSphere Auto
• We’ve used both.
14 | CONFIDENTIAL & PROPRIETARY