Puppet is used at Janrain to provision cloud servers, deploy applications, and manage infrastructure in an automated and repeatable way. Key aspects include: - Cloud servers are provisioned using a Ruby script that launches instances with Puppet pre-configured via cloud-init. - Puppet signs certificates and installs a base configuration including users, SSH keys, common applications, and monitoring tools. - Version control and environments are used to collaborate and safely roll out changes. - Puppet manages DNS, storage volumes, application deployments and more, keeping infrastructure in a known state. - Tools like Puppetcommander help avoid load issues and keep Puppet runs orderly as the infrastructure scales

1. Puppet at Janrain
James Loope

2. In the beginning...

3. Awesomeness

4. More awesomeness

5. Less awesome

6. Opposite of awesome

7. Totally awesome

8. Wagons Ho!

9. We're not in Kansas
Anymore

10. On demand resources!
Features!
APIs!

11. Impermanence!
Competition!
APIs!

12. Sometimes you have to let go
it's not your puppy, it's just an instance

13. Persistence does not make it better
Entropy will get you in the end

14. Do it right the first time, make it
repeatable

15. Puppet keeps us sane
class apps::zookeeper-server ( $nodes ) {
package { "zookeeperd" : ensure => installed }
service { "zookeeper":
ensure => running,
enable => true,
hasstatus => true,
pattern => "zookeeper",
require => Package["zookeeperd"]
}
file { "/etc/zookeeper/conf/zoo.cfg" :
content => template("apps/zookeeper/zoo.cfg.erb")
}
}

16. Version control lets us work together
>git branch -r
origin/HEAD -> origin/master
origin/development
origin/master

17. Environments keep us safe
development > staging > production

18. Scary API's?

19. Simple tools keep us efficient
> createaserver.rb -a ami-e2af508b -n test1.janrain.com -S
Fog launches an Ubuntu base ami
server = compute.servers.create(:image_id => options[:ami], :flavor_id =>
options[:type], :groups => options[:groups], :user_data => '
puppet:
conf:
agent:
server: 'puppet.janrain.com'
certname: '"test1.janrain.com"'
environment: "development"
pluginsync: true
waitforcert: true

20. ● Ubuntu cloud-init installs puppet
○ https://help.ubuntu.com/community/CloudInit
○ also: work around for provider prerequisite problem
● Puppet starts up and waits for signing
○ our utility signs the cert over the REST api
■ http://docs.puppetlabs.com/guides/rest_api.html
curl -i --cert ~/.puppetcred/puppet.crt --key ~/.
puppetcred/puppet.key --cacert ~/.puppetcred/ca_crt.pem
https://puppet.janrain.com/development/certificate_status/
test1.janrain.com -H 'Content-Type: text/pson' -X PUT --data
'{"desired_state":"signed"}'

21. ● Puppet starts up and installs our base from
common modules
○ users
○ groups
○ ssh pubkeys
○ common apps
○ metrics and monitors
■ collectd
■ nagios
■ mcollective

22. ● Puppet sets up the DNS
○ via REST API
○ http://dyn.com/dns/dynect-managed-dns/
● Puppet manages our instance volumes with lvm
○ https://github.com/puppetlabs/puppet-lvm
● Puppet deploys application code with vcsrepo
○ https://github.com/puppetlabs/puppet-vcsrepo

23. Tadah!
ssh test1.janrain.com
Welcome to Ubuntu 11.04 (GNU/Linux 2.6.38-8-virtual i686)
jloope@test1.janrain.com:~$

24. The dashboard gives us insight

25. Avoiding the Stampede
● It's hard to keep the PuppetMaster's load predictable
● Puppetcommander
● Initiates runs in an orderly fashion
● Can be globally disabled
https://github.com/puppetlabs/mcollective-plugins/tree/master/agent/puppetd/commander/

26. What's next?
● External Node classifier
● LXC Development Environment
● Build => Bundle => Scale
● Puppet and Zookeeper via Facter

27. In conclusion