Presenter: Adam Miller As the Release Engineer and a member of Operations team for OpenShift Online, a downstream consumer of OpenShift Origin and the largest Public implementation of OpenShift to date, Adam Miller will discuss what it's like behind the scenes at OpenShift.com and share lessons learned and bring his thoughts and feedback on the future direction of Origin.

1. 1 by
OpenShift DevOps
From Origin to Online
Adam Miller
OpenShift Release Engineer
Boston 2013

2. 2 by
From Origin to Online
In this session we're going to discuss:
- How OpenShift Online consumes Origin
- How OpenShift Online contributes to Origin
- How code goes from development environments to
production.

3. 3 by
What is DevOps?
“ a software development method that stresses
communication, collaboration and integration between
Dev and Ops” (paraphrased from Wikipedia)
Devs Op and Ops Dev ... see what they did there?

4. 4 by
The Flow of Code
origin
Public
Cloud
Service
On-premise
or Private
Cloud
Software
Open
Source
Project

5. 5 by
OpenShift Architecture – Contents of a DevEnv

6. 6 by
How Jenkins Orchestrates DevEnv Creation
Jenkins
Development
Environments
Base AMI Clean OS Image
(RHEL/Fedora)
used to build on
top of.
Register Image with
EC2 to launch
instances to build
DevEnvs in Jenkins
Register
Image with
EC2 to launch
DevEnvs

7. 7 by
How DenEnvs are Built
Jenkins
Base AMI
API Calls
Code
Test Results
clone master branch
Launch instance of
latest Base AMI
Use Base AMI to
build new devenv
Sync code to devenv, build
rpms from source.
Report Test
results, register
DevEnv AMI
OpenShift Origin

8. 8 by
How Development Happens
Jenkins
DevEnv
Code (Local branch
from GitHub)
Sync code
Run Cucumber and rake
tests, get output
Pull
Request
OpenShift-bot
DevEnv
OpenShift Origin

9. 9 by
How Deployment Works in OpenShift Online
Staging:
Release Candidate
code deployed here
for final round of QA
and sign off.
Integration:
Daily deployment
from RPM package
sets.
Production:
Production Code
deployed here,
OpenShift.com
OpenShift Origin
Master branch (where continued development happens)
stage
Code

10. 10 by
What The Environments Look like
Brokers Nodes
ActiveMQ
Load Balancers
DNSDNSREST APIREST API
SSOSSO

11. 11 by
Thank You.
Questions?
Adam Miller
admiller@redhat.com