Infrastructure as Data and Code

Infrastructure as Data
Nick Lewis
Developer | Puppet Labs
@nick_lewis
Friday, August 23, 13

puppetconf.com #puppetconf
Infrastructure as Data
• Speciﬁed data
• Manifests
• Hiera
• Node classiﬁcation
• Observed data
• Facts
• Generated/derived data
• Catalogs
• Reports

as a
minecraft addict
I would like
time to be correct on my computer
so that
I can stop playing minecraft and go to sleep

Infrastructure as Code
• tangible artifact
• easy to change
• documented
• repeatable
• idempotent

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

yum check-update ntp
if [ $? -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 restart
elif ! /etc/init.d/ntpd status; then
/etc/init.d/ntpd start
fi

Infrastructure as Bash
• platform-speciﬁc
• 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 ntp
else
start_service ntp
fi

Infrastructure as Bash
• platform-speciﬁc
• slightly less imperative
• ad-hoc relationships
• brittle in the face of failure

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

Infrastructure as Puppet
• platform-independent
• mostly declarative
• relationships are explicit
• understands failure

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

include ntp

tell me what you want
what you really really want

include magical_time_synchronization

configuration management
the art of making your monitoring checks
pass

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

package { 'ntp': }
ﬁle_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
rpmpython
ntp server...

time sync
ntpd service
yum
rpmpython network
ntp server...

time sync
ntpd service
yum
rpmpython network
ntp server...
...

time sync
ntpd service
ﬁlesystem
yum
rpmpython network
ntp server...
...

time sync
ntpd service
ﬁlesystem
yum
rpmpython network
ntp server...
...
...

time sync
ntpd service
ﬁlesystem
yum
rpmpython
electricity
network
ntp server...
...
...

time sync
ntpd service
ﬁlesystem
yum
rpmpython
electricity
network
ntp server...
...
... ...

time sync
ntpd service
ﬁlesystem
yum
rpmpython
electricity
network
ntp server...
...
... ...
the very concept of time itself

if you wanna be my lover
you gotta apt-get with my
friends

require
subscribe

Package installs Service
File is the source of Package
User owns File
File conﬁgures Service
User is a member of Group
File is the directory of File
File is executed by Exec

File / File
File / User
File / Group
User / Group
Cron / User
Exec / File
Exec / User
?

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

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

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

ensure => present,
owner => User[sweet],
}
user { "sweet":
ensure => absent,
}

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

user { "sweet":
ensure => absent,
}
ensure => present,
}
--ordering manifest

user { "sweet":
ensure => absent,
}
ensure => present,
}
--ordering random

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

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

concat::fragment { "motd_hello":
content => "Hello PuppetConf!n",
order => 1,
}
concat::fragment { "motd_goodbye":
content => "Goodbye PuppetConf :(",
order => 2,
}
ﬁle { "/etc/motd":
ensure => present,
content => "Hello PuppetConf!nGoodbyePuppetConf :
(",

Thank You
Nick Lewis
Developer | Puppet Labs
@nick_lewis
Collaborate. Automate. Ship.

Follow us on Twitter @puppetlabs
youtube.com/puppetlabsinc
slideshare.net/puppetlabs
Collaborate. Automate. Ship.

Infrastructure as Data and Code

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Destacado

Destacado (6)

Similar a Infrastructure as Data and Code

Similar a Infrastructure as Data and Code (20)

Más de Puppet

Más de Puppet (20)

Último

Último (20)

Infrastructure as Data and Code