agile deployments with puppet

Agile Deploymentswith Puppet

Gary LarizzaPuppet Labs

@glarizza

Saturday, October 22, 2011

Agile Deploymentswith Puppet

Gary LarizzaPuppet Labs

@glarizza

http://bit.ly/garydevops




DevOps• Culture not tools?

• Release Management?

• http://slidesha.re/itweapon

• http://bit.ly/toolsmatter

• http://slidesha.re/devopstools


http://slidesha.re/itweapon

http://slidesha.re/itweapon

http://speakerdeck.com/u/lusis/p/sometimes-tools-matter

http://speakerdeck.com/u/lusis/p/sometimes-tools-matter

http://www.slideshare.net/jedi4ever/devops-tools-fools-and-other-smart-things

http://www.slideshare.net/jedi4ever/devops-tools-fools-and-other-smart-things

Example of ‘poor

deployment’


Developer

Operations


Developer

Production

Operations


Developer

Production

Staging

Operations


Developer

Production

Staging

Build Time

Operations

Day(s)


Developer

Production

Staging QA

Build Time

Operations

Day(s)


Developer

Production

Staging QA

Build Time

Operations

Day(s) Week(s)


Developer

Production

Staging QA

UK

Build Time

Operations

Day(s) Week(s)


Developer

Production

Staging QA

UK

China

Build Time

Operations

Day(s) Week(s)


Developer

Production

Staging QA

UK

China

Canada

Build Time

Operations

Day(s) Week(s)


Developer

Production

Staging QA

UK

China

Canada

Build Time

Operations

Day(s) Week(s) ???


Rampinationhttp://bit.ly/pconfkeynote


http://bit.ly/pconfkeynote

http://bit.ly/pconfkeynote

Example of ‘Agile’


Developer

Operations


Developer

Production

Operations


Developer

Production

Operations

Configuration Data


Developer

Production

StagingOperations

Configuration Data


Developer

Production

Staging

Build Time

Operations

10 Minutes

Configuration Data


Developer

Production

Staging QA

Build Time

Operations

10 Minutes 1-2 Hours

Configuration Data


Developer

Production

Staging QA

Build Time

Operations

10 Minutes 1-2 Hours 3 Hours

Configuration Data

Developer Reach


What can Ops learn from Dev?

• Do developers re-write their code at every step?

• Version control

• Testing frameworks

• Expose ‘settings’ through configuration data


Infrastructure as Code with Puppet

• Define what needs to be done

• Model your ideal state with simple resources

• Configured State vs. Running State

• Choose your level of commitment


Resource Abstraction Layer


Resource Abstraction Layer

/usr/bin/yum -y install httpd


Bare Machine

Provisioning

Base Install

Configure

Assigned Role

Maintenance

Puppet’s Task


Puppet Resources

service { 'httpd': ensure => running, enable => true, hasstatus => true, hasrestart => true,}


Type

Puppet Resources



Type Title

Puppet Resources



Type Title

Attributes

Puppet Resources



Facter

• Describes aspects of your machine - “facts”

• Facts written in Ruby

• Nice library of existing facts

• Custom facts are easy


garys-mbp:$ facterdomain => puppetlabs.lanfacterversion => 1.5.8fqdn => garys-mbp.puppetlabs.lanhardwaremodel => x86_64hostname => garys-mbpkernel => Darwinmacosx_buildversion => 10K549macosx_productname => Mac OS Xmacosx_productversion => 10.6.8macosx_productversion_major => 10.6macosx_productversion_minor => 8<...>

Facter


Facter.add("computername") do confine :kernel => :darwin setcode('scutil --get ComputerName'.chomp)end

computername scutil --get ComputerName

Custom Fact




Fact name

Custom Fact




Command to Execute

Fact name

Custom Fact


Custom Fact

ENV.each do |key,val| Facter.add("env_#{key}") do setcode do val end endend


Separate Data from Logic

• Configuration Data adapts to environment

• Easy deployment - Puppet modules do not change

• Eliminate SSH access for deployment


Data Separation Examples


Node Inheritancenode common { $dnsserver = '8.8.8.8' $searchdomain = 'puppetlabs.vm'}

node devops inherits common { $dnsserver = '10.13.1.3'}

node 'agent.puppetlabs.vm' inherits devops { file { '/etc/resolv.conf': content => "search ${searchdomain}\n nameserver ${dnsserver}\n", }}


Data Class in Moduleclass dns::params { $dnsserver = '8.8.8.8' $searchdomain = 'puppetlabs.vm'}

class dns( $dnsserver = $dns::params::dnsserver, $searchdomain = $dns::params::searchdomain) inherits dns::params {

file { '/etc/resolv.conf': content => "search ${searchdomain}\n nameserver ${dnsserver}\n", }}


Extlookup

dnsserver, 8.8.8.8searchdomain, puppetlabs.vm

dnsserver, 10.13.1.2

common.csv devops.csv

$extlookup_datadir = "/etc/puppetlabs/puppet/data"$extlookup_precedence = [$clientcert, $environment, $architecture, 'common']

node 'agent.puppetlabs.vm' { include dns}

class dns { $dnsserver = extlookup('dnsserver') $searchdomain = extlookup('searchdomain')}


External Node Classifier

---classes: - dnsparameters: searchdomain : ‘puppetlabs.vm’ dnsserver : ‘10.13.1.2’


Hiera

• Hierarchal data lookup system

• Structured data backend

• YAML, JSON, and current Puppet state

• http://bit.ly/hieradata


Global Defaults


Global Defaults

Environment


Global Defaults

Environment

Role


Global Defaults

Environment

Role

Resultant Data Configuration


Global Defaults


Global Defaults

---ntpserver : time.puppetlabs.compuppetserver : puppet.puppetlabs.comenvironment: production


Global Defaults

---ntpserver: time.puppetlabs.compuppetserver: puppet.puppetlabs.comenvironment: production


Global Defaults

Environment



Global Defaults

Environment

---stompserver : stomp-qa.puppetlabs.compuppetserver : puppet-qa.puppetlabs.comenvironment: qa



Global Defaults

Environment

---ntpserver: time.puppetlabs.com

stompserver: stomp-qa.puppetlabs.comenvironment: qapuppetserver: puppet-qa.puppetlabs.com


Global Defaults

Environment

Role




Global Defaults

Environment

Role

---storeconfigs: true




Global Defaults

Environment

Role


stompserver: stomp-qa.puppetlabs.comenvironment: qa

storeconfigs: true

puppetserver: puppet-qa.puppetlabs.com


DEMO TIME


Devops Survey

• http://bit.ly/devopssurvey


http://bit.ly/devopssurvey

http://bit.ly/devopssurvey

Code is online

https://github.com/glarizza/puppet-datademo




Gary Larizza

• Twitter : @glarizza

• Email: [email protected]

• Web: http://www.puppetlabs.com


mailto:[email protected]

mailto:[email protected]

http://www.puppetlabs.com

http://www.puppetlabs.com

agile deployments with puppet

Technology

developer operationssaturday

puppet resources service

puppet resources type

puppet congured state

lytoolsmatter http

reitweapon http

rampination http

lygarydevopsagile deployments