1. Christian Huebner, Principal Architect
Lacking structure in your infra? Try CI/CD.
It's not just for application development
Christian Huebner, Principal Architect

2. Reliability Simplicity Supportability Full LCM “Script Horizon”
Why?
Goals:
Reliability
Simplicity
Supportability
Full LCM
Obstacles:
“Script Horizon”
Tribal knowledge
Fat Fingering
Diverging configs
Poor action tracking
Event Horizon: More and more scripts sucked into the black hole of the project

3. Infrastructure as code Code review Automated code deployment
What?
Infrastructure as code
One model per cloud/cluster
Code review
Automated code deployment
Changes are made to code base, not environment
Automated testing controlled by single entity
Staging environment to ensure functionality
No manual interaction with any cloud node
Continuity across individuals, teams (“night shift”)

4. (Initial Deployment or new hardware add)
How?
Creates, Tests, Packages, Configurations and Artifacts
Artifacts (Update Scope)
Deployed Clouds
Stage
Source Code Review & Mgt
Node
Classification
Software Automation
Configuration Management
Prod1
Config changes (LCM Scope)
Prod2
Jenkins triggered by updates, configuration changes
StackLight
Operations Support System (OSS)
Configurations
Salt formulas
Model Designer UI
(Initial Deployment or new hardware add)

5. From the field The old way CI/CD Deployment tooling Manual adjustments
Puppet, Web GUI
Manual adjustments
Risks
CI/CD
Lifecycle management with Mirantis MCP
Saltstack based with Gerrit/Jenkins CI/CD environment
Customer experiences
Supportability

6. Thank You
Please see us at the Mirantis booth for a demo or contact me.
@ossarchitect