Puppetizing Multitier Architecture - Reid Vandewiele, Puppet Labs

1. 2014
presented by
Puppetizing
Multi-Tier
Architecture
Reid Vandewiele
Solutions Engineer | Puppet Labs

4. Monolithic Install Split Install

5. Monolithic Install Split Install

8. Agenda
• Introduction
Multi-Tier Challenges
• How to Define
• How to Classify
• How to Deploy

9. Multi-Tier Challenges
• How to Define
• How to Classify
• How to Deploy

15. Profiles

21. class
puppet_enterprise
(
$interface,
...
)
{
##
REPRESENT
THIS
#
#
#
#
#
#
#
#
#
#
}

24. Application Classes
class
pe
(
$puppetdb_port
=
8081,
...
)
{
}
class
pe::puppet_master
(
$puppetdb_port
=
$pe::puppetdb_host,
...
)
inherits
pe
{
...
}
class
pe::puppetdb
(
$puppetdb_port
=
$pe::puppetdb_host,
...
)
inherits
pe
{
...
}

25. Application Class
class
pe
(
$puppet_master_host
=
undef,
$puppet_master_port
=
undef,
$puppet_console_host
=
undef,
$puppet_console_port
=
undef,
$puppetdb_database_host
=
undef,
$puppetdb_database_port
=
undef,
$puppetdb_database_name
=
undef,
$puppetdb_database_username
=
undef,
$puppetdb_database_password
=
undef,
...
)
{
...

26. Application Component Profile
class
pe::puppet_master
(
$certificate_authority_host
=
$pe::certificate_authority_host,
$certificate_authority_port
=
$pe::certificate_authority_port,
$certificate_authority_proxy
=
true,
$puppetdb_host
=
$pe::puppetdb_host,
$puppetdb_port
=
$pe::puppetdb_port,
$console_host
=
$pe::puppet_console_host,
$console_port
=
$pe::puppet_console_port
$reports
=
undef,
$node_terminus
=
undef,
)
inherits
pe
{
...

27. Accomplished
• Model the Application
Not Yet Accomplished
• Dynamism / Elasticity

28. ?

29. Pool_member
<<|
filter
|>>
pool_member
{
'master_1':
}
pool_member
{
'master_2':
}
@@pool_member
{
'master_1':
}
@@pool_member{
'master_2':
}
storeconfigs

30. storeconfigs
class
pe::load_balancer
(
...
)
inherits
pe
{
Pool_member
<<|
filter
|>>
...
}
class
pe::puppet_master
(
...
)
inherits
pe
{
@@pool_member
{
$::ipaddress:
}
...
}

32. clientcert=www1
app_pubkey=
ensure keypair!
clientcert=www1
app_pubkey=abc123
ensure keypair!

33. Multi-Tier Challenges
• How to Define
• How to Classify
• How to Deploy

34. Set
A
collec+on
of
"things"
(objects
or
numbers,
etc).
Each
member
is
called
an
element
of
the
set.
There
should
be
only
one
of
each
member
(all
members
are
unique).

35. Evaluation Order Matters
• Works
class
{
'pe':
instance_id
=>
'central';
}
class
{
'pe::puppet_master':
}
• Breaks
class
{
'pe::puppet_master':
}
class
{
'pe':
instance_id
=>
'central';
}

36. Hiera
-­‐-­‐-­‐
:hierarchy:
-­‐
"clientcert/%{clientcert}"
-­‐
"app_instance/%{app_instance}"
-­‐
"env_tier/%{env_tier}"
-­‐
global
:backends:
-­‐
yaml
:yaml:
:datadir:
"/etc/puppetlabs/puppet/environments/%{environment}/data"

37. Hiera
All
Managed
Nodes
env_tier=development
env_tier=production
appid=dev1
appid=dev2
appid=prod1
appid=prod2

38. Application Class
class
pe
(
$puppet_master_host
=
undef,
$puppet_master_port
=
undef,
$puppet_console_host
=
undef,
$puppet_console_port
=
undef,
$puppetdb_database_host
=
undef,
$puppetdb_database_port
=
undef,
$puppetdb_database_name
=
undef,
$puppetdb_database_username
=
undef,
$puppetdb_database_password
=
undef,
...
)
{
...

39. Application Class
class
pe
(
$puppet_master_host
=
$::puppet_master_host
,
$puppet_master_port
=
$::puppet_master_port
,
$puppet_console_host
=
$::puppet_console_host,
$puppet_console_port
=
$::puppet_console_port
,
$puppetdb_database_host
=
$::puppetdb_database_host,
$puppetdb_database_port
=
$::puppetdb_database_port,
$puppetdb_database_name
=
$::puppetdb_database_name,
$puppetdb_database_username
=
$::puppetdb_database_username,
$puppetdb_database_password
=
$::puppetdb_database_password,
...
)
{
...

40. Multi-Tier Challenges
• How to Define
• How to Classify
• How to Deploy

42. 1 2 Run Puppet!
Run Puppet!

43. Run Puppet!
Run Puppet!
Run Puppet!
Run Puppet!
1 2 3 4

44. Puppetizing Multi-Tier Architecture
Multi-Tier Challenges
• How to Define
• How to Classify
• How to Deploy

45. Anchors
class
pe
(
...
)
{
#
ANCHORS
#
When
building
a
complex
multi-­‐tier
model,
it
is
not
known
up
front
which
#
profiles
will
be
deployed
to
a
given
node.
However,
some
profiles
when
#
deployed
together
have
dependencies
which
must
be
expressed.
For
example,
#
the
CA
must
be
set
up
and
configured
before
certificates
can
be
requested.
#
Therefore
the
CA
must
be
configured
before
any
certificate-­‐requiring
#
service.
Since
the
profiles
cannot
express
those
dependencies
directly
#
against
each
other,
since
they
may
or
may
not
exist
in
a
given
node's
#
catalog,
we
instead
have
them
express
dependencies
against
common
anchors.
anchor
{
'barrier:
pe
certificate_authority':
}
-­‐>
anchor
{
'barrier:
pe
puppetdb_database':
}
-­‐>
anchor
{
'barrier:
pe
puppetdb':
}
-­‐>
...

46. Puppetizing Multi-Tier Architecture
• Model the app as a class
– Most important consideration is the interface
• Assign parameters to app, not just nodes
– Complementary to the assignment of classes to nodes
• Take central control of Puppet run schedule
– Or else account for eventual consistency

47. Questions?