infrastructure as data - puppetconf 2013

Infrastructure as DataNick LewisDeveloper | Puppet Labs @nick_lewis

Friday, August 23, 13

puppetconf.com #puppetconf

Infrastructure as Data

• Specified data• Manifests

• Hiera

• Node classification

• Observed data• Facts

• Generated/derived data• Catalogs

• Reports



as aminecraft addict

I would liketime to be correct on my computer

so thatI can stop playing minecraft and go to sleep



Infrastructure as Code

• tangible artifact

• easy to change

• documented

• repeatable

• idempotent



yum install -y ntpif ! grep 'server 0.pool.ntp.org' /etc/ntp.conf; then echo 'server 0.pool.ntp.org' >> /etc/ntp.conffi/etc/init.d/ntpd status || /etc/init.d/ntpd start



yum check-update ntpif [ $? -eq 100 ]; then yum install -y ntp && restart_ntp='y'fi

if ! grep 'server 0.pool.ntp.org' /etc/ntp.conf; then echo 'server 0.pool.ntp.org' >> /etc/ntp.conf restart_ntp='y'fi

if [ -n "$restart_ntp" ]; then /etc/init.d/ntpd restartelif ! /etc/init.d/ntpd status; then /etc/init.d/ntpd startfi



Infrastructure as Bash

• platform-specific

• imperative

• ad-hoc relationships

• brittle in the face of failure



if install_package ntp; then restart_ntp='y'fi

if add_file_line 'server 0.pool.ntp.org'; then /etc/ntp.conf && restart_ntp='y'fi

if [ 'y' = "$restart_ntp" ]; then restart_service ntpelse start_service ntpfi



Infrastructure as Bash

• platform-specific

• slightly less imperative

• ad-hoc relationships

• brittle in the face of failure



package { 'ntp': ensure => 'present', notify => Service[ntp], } file_line { 'ntp server': path => '/etc/ntp.conf', line => 'server 0.pool.ntp.org', require => Package[ntp], notify => Service[ntp], } service { 'ntp': ensure => 'running', }



Infrastructure as Puppet

• platform-independent

• mostly declarative

• relationships are explicit

• understands failure



class ntp { package { 'ntp': ensure => 'present', notify => Service[ntp], } file_line { 'ntp server': path => '/etc/ntp.conf', line => 'server 0.pool.ntp.org', require => Package[ntp], notify => Service[ntp], } service { 'ntp': ensure => 'running', }



include ntp



tell me what you wantwhat you really really want



include magical_time_synchronization



configuration managementthe art of making your monitoring checks pass



abstractiongiving a name to something and then cutting it out of your life



class ntp { package { 'ntp': ensure => 'present', notify => Service[ntp], } file_line { 'ntp server': path => '/etc/ntp.conf', line => 'server 0.pool.ntp.org', require => Package[ntp], notify => Service[ntp], } service { 'ntp': ensure => 'running', }



package { 'ntp': }

file_line { 'ntp server': }

service { 'ntp': }



time sync



time sync

ntpd service



time sync

ntpd service

ntp package



time sync

ntpd service

ntp package ntp.conf



time sync

ntpd service


yum



time sync

ntpd service


yum

python



time sync

ntpd service


yum

rpmpython



time sync

ntpd service


yum

rpmpython

...



time sync

ntpd service


yum

rpmpythonntp server...



time sync

ntpd service


yum

rpmpython networkntp server...



time sync

ntpd service


yum


...



time sync

ntpd service


filesystem

yum


...



time sync

ntpd service


filesystem

yum


......



time sync

ntpd service


filesystem

yum

rpmpythonelectricity

networkntp server...

......



time sync

ntpd service


filesystem

yum



...... ...



time sync

ntpd service


filesystem

yum



...... ...

the very concept of time itself



if you wanna be my loveryou gotta apt-get with my

friends



requiresubscribe



Package installs ServiceFile is the source of PackageUser owns FileFile configures ServiceUser is a member of GroupFile is the directory of FileFile is executed by Exec



File / FileFile / UserFile / GroupUser / GroupCron / UserExec / FileExec / User

?



file { "/home/sweet/home": ensure => present, owner => sweet, require => User[sweet],}

user { "sweet": ensure => present,}



file { "/home/sweet/home": ensure => absent, owner => sweet, require => User[sweet],}

user { "sweet": ensure => absent,}



file { "/home/sweet/home": ensure => present, owner => sweet, require => User[sweet],}




file { "/home/sweet/home": ensure => present, owner => User[sweet],}





file { "/home/sweet/home": ensure => present,}





--ordering manifest





--ordering random



concat { "/etc/motd": }

concat::fragment { "motd_hello": target => "/etc/motd", content => "Hello PuppetConf!\n", order => 1,}

concat::fragment { "motd_goodbye": target => "/etc/motd", content => "Goodbye PuppetConf :(", order => 2,}



file { "/etc/motd": ensure => present, content => "Hello PuppetConf!\nGoodbye PuppetConf :(",}



concat::fragment { "motd_hello": target => "/etc/motd", content => "Hello PuppetConf!\n", order => 1,}

concat::fragment { "motd_goodbye": target => "/etc/motd", content => "Goodbye PuppetConf :(", order => 2,}

file { "/etc/motd": ensure => present, content => "Hello PuppetConf!\nGoodbyePuppetConf :(",


Thank YouNick LewisDeveloper | Puppet Labs @nick_lewis

Collaborate. Automate. Ship.


Follow us on Twitter @puppetlabs

youtube.com/puppetlabsinc

slideshare.net/puppetlabs

Collaborate. Automate. Ship.


infrastructure as data - puppetconf 2013

Technology

puppetconf class ntp

rpmpython ntp server

puppetconf package

y ntp restart

rpmpython network ntp

puppetconf infrastructure

checkupdate ntp

puppetconf abstraction