SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
Implementing Infrastructure as Code ConfigMgtCamp 2017
23.
BUILD COMPLIANCE INTO THE PIPELINE
Humans focus on the
implementation of the
pipeline and audit trailsUse the pipeline to continuously
validate operational requirements and
compliance, and to implement controls
24.
INFRASTRUCTURE
DESIGN PATTERNS
Organizing code for dynamic
infrastructure
25.
One definition,
multiple
environments
our-project/main.tf
staging
production
26.
INFRASTRUCTURE
DESIGN PRINCIPLE
Structure your code to minimize risks for
making (small, frequent) changes
27.
our-project/staging/main.tf
staging
production
our-project/production/main.tf
One definition
per environment
28.
our-project/main.tf
staging
production
development
Single
definition
template,
promoted
across
environments
29.
How do we build and test
this stuff?
It runs sooooo sloooooow! L
30.
Nginx Cookbook
ORGANIZE INFRASTRUCTURE INTO
SEPARATELY TESTABLE PIECES
Tomcat Cookbook
JDK Cookbook
MyApp Vhost Cookbook
MyApp.war
Application
Server
Web
Server
31.
FAN-IN PIPELINES
TEST
TOMCAT
COOKBOOK
TEST MYAPP
CODE
TEST JDK
COOKBOOK
TEST APP
SERVER
TEST MYAPP
DEPLOYMENT
Test components
individually
Cumulatively integrate and
test components together
32.
DESIGNING FOR CHANGE
Cope with growth, evolving
requirements, expanding teams
33.
DESIGN TO ENABLE FREQUENT
CHANGES
Split infrastructure
according to the
scope of typical
changes
Minimize the risk of
changes by limiting
the blast radius
Keep infrastructure
units loosely
coupled
34.
ALIGN INFRASTRUCTURE DESIGN WITH
ORGANIZATION STRUCTURE