Introduction to Configuration Management

R.I.Pienaar
Malta DevOps August 2016
Introduction to
Conﬁguration Management

R.I.Pienaar | rip@devco.net | http://devco.net | @ripienaar
Who am I?
• Malta since December 2015
• Consultant for 20+ years
• Government, Finance, Health, Social Media,
Fortune 50, Startups
• DevOps, Automation, Architect,
Development
• Open Source @ github.com/ripienaar
• Linux since Kernel 99 alpha p11

Conﬁguration
Management
for Devs and Ops

CM - What’s the problem?
Not CONSISTENT

Not REPRODUCABLE

Not INTERESTING

Not SCALABLE

Not COMPLETE

Not PREDICTABLE

Hypothetical Toolset

CM - Wishes?
Programmable
Infrastructure
Domain Speciﬁc Language

CM - Wishes?
Programmable
Infrastructure
Platform and OS Independent

CM - Wishes?
Programmable
Infrastructure
Complete Server Lifecycle

CM - Wishes?
Programmable
Infrastructure
Extendible via Plugins and APIs

CM - Wishes?
Programmable
Infrastructure
Learns from Development

CM - Wishes?
Open
Source,APIs and Docs
Community, IRC, Slack, GitHub, Users

CM - Wishes?
Commercial
Owned
Support,Training, Conferences, Certs

Puppet
• 10 years old
• Commercially owned Open Source
• Client Server or Standalone Architecture
• Used by 10s of 1000s of companies
• Useful to small and large companies, even
single servers
• 4 400 reusable modules, write your own

Puppet Resources
package{“httpd”:
ensure => “present”
}
file{“/etc/httpd/conf/httpd.conf”:
owner => “root”,
group => “root”,
mode => “0644”,
source => “puppet:///modules/apache/httpd.conf”
}
service{“httpd”:
ensure => “running”,
enable => true
}

Puppet Types
}
mode => “0644”,
}
enable => true
}

Puppet Titles
}
mode => “0644”,
}
enable => true
}

Puppet Parameters
}
mode => “0644”,
}
enable => true
}

Puppet Relationships
…
}
…,
require => Package[“httpd”],
notify => Service[“httpd”]
}
…,
require => File[“/etc/httpd/conf/httpd.conf”]
}

Puppet Collections
class apache {
include apache::install
include apache::config
include apache::service
}
class apache::install {
package{ … }; package{ … }
}
class apache::config {
file{ … }; file{ … }
}
class apache::service {
service{ … }; service{ … }
}

Puppet Relations
…
}
…,
require => Class[“apache::install”],
notify => Class[“apache::service”]
}
…,
require => Class[“apache::config”]
}

Puppet Nodes
node “dev1.example.net” {
include roles::lamp_dev
}
class roles::lamp_dev {
include profile::lamp_webserver
include profile::lamp_mysqlserver
}
class profile::lamp_webserver {
include php
include apache
}
class profile::lamp_mysqlserver {
include mysql
}

Puppet Facts
$ facter
…
os => {
architecture => "x86_64",
distro => {
codename => "Core",
description => "CentOS Linux release 7.2.1511 (Core)",
id => "CentOS",
release => {
full => "7.2.1511",
major => "7",
minor => "2"
},
specification => ":core-4.1-amd64:core-4.1-noarch"
},
family => "RedHat",
hardware => "x86_64",
name => "CentOS",
release => {
full => "7.2.1511",
major => "7",
minor => "2"
},
selinux => {
enabled => false
}
}
…

Puppet Facts
class site::common {
if $facts[“os”][“family”] == “RedHat” {
include site::redhat_common
} elsif $facts[“os”][“family”] == “Debian” {
include site::debian_common
} else {
fail(“Unknown operating system family”)
}
}

Puppet Site Policies
• /srv/www - root:root
• /etc/httpd/conf.d/<site>.conf
• /srv/www/<site> - root:root
• /srv/www/<site>/html - owner:owner
• /srv/www/<site>/logs/access_log - root:root
• /srv/www/<site>/logs/error_log - root:root
• <site> log rotation
• <site> backups

site::vhost{“example.com”: }
Day to Day Usage
$client_sites = [“example1.com”, “example2.com”]
site::vhost{$client_sites: }
site::vhost{“example.com”:
aliases => [“www.example.com”, “www.other.com”],
owner => “acme”,
allow_override => “All”,
options => “Indexes”
}

Policy Set by Web Team - Creates Utility
define site::vhost ( $port, $owner, $group, … ) {
apache::vhost{$name:
port => $port,
docroot => “/srv/www/${name}/html”,
docroot_owner => $owner,
docroot_group => $group,
}
bacula::backup_policy{$name: …}
sensu::monitor{$name: …}
}

Puppet Testing
Learning from Development - Unit Testing
describe “site::vhost” do
let(:title) { “example.com” }
it {
is_expected to contain_apache__vhost(“example.com”)
.with (
“port” => “80”,
“docroot” => “/srv/www/example.com/html”
…
)
}
end

Puppet Testing
Learning from Development - Integration Testing
describe package(“httpd”) do
it { should be_installed }
end
describe service(“httpd”) do
it { should be_enabled }
it { should be_running }
end
describe file(“/srv/www/example.com/html”) do
it { should exist }
it { should be_directory }
it { be_owned_by “root” }
end

Puppet Reporting
http://theforeman.org

Questions?
twitter: @ripienaar
email: rip@devco.net
blog: www.devco.net
github: ripienaar
freenode: Volcane
slack.puppet.com: ripienaar
http://learn.puppet.com/
https://www.devco.net/

Introduction to Configuration Management

Recommended

Recommended

More Related Content

Similar to Introduction to Configuration Management

Similar to Introduction to Configuration Management (20)

Recently uploaded

Recently uploaded (20)

Introduction to Configuration Management