The document outlines changes to a company's infrastructure and software development lifecycle processes before and after implementing improvements. Key aspects include migrating from manual processes to automated tools for configuration, deployment, and release of code and applications. Infrastructure is now treated as part of the overall software development lifecycle.

1. Before
NOC server
templates
TAR
RPM restarts
TAR
TAR
code,
EC2
content pupp
deploys et RS
studio RS deployment
devs deployment
S3
yum
repo
Provision-time builds
reconfigs
TAR EXE
TAR AUTO
server
TOOLS
code templates
TAR
RPM
middleware
devs platform CONTROL PROVISION RELEASE
system
admins
Tuesday, May 10, 2011

2. After
process apache/php
messaging, memcached
queuing mysql
app middleware 3rd party
yum yum
winning.c rundeck
om
code, "D
content, te" e plo
metas o mo y"
"pr job &
jo "Re
jenkins yum b leas
e"
builds
dev prod
Tuesday, May 10, 2011

3. Infrastructure as SDLC
SVN
hud agent cfg
yum pup
son repo pet
packages
active users run packages
directory deck
commands
nag
splunk
ios
resource model
sys cfg
right instance create
scale
events
new node Node a log data
CONTROL PROVISION RELEASE
Tuesday, May 10, 2011

4. dtosolutions.com
John Willis
john@dtosolutions
Tuesday, May 10, 2011