Michael Osmond
We value
people and interactions
over
process and tools
(Agile Manifesto)

Controlling Configurations
- Static
- Dynamic

Commodity components
Create Versions
Edit
Build Disks
Release
Test
Production
Master copies of configurations
Multiple versions




Master configuration is not the running node
Generate standard parts – the boot file
Regenerate the disks
Rollback
Changes made
Directly to routers
Then saved.
Central Copy of Configuration


Bulk and Cheap
Replaceable



Move your people up the protocol stack.
People aren’t hot swappable
Do you have a Rodney?



Builds
Value of Automation
Team process
Boot into DOS and connect to network
Controlled from
A floppy boot disk
Gather Configuration Information
Format Disk
Copy down Windows source and set
Unattended install
Across multiple
Reboots
Unattended Windows Install
Install required software
User profile configured on logon
Dev / Test
IGOR
Master Builds



Develop team processes
People need to know their roles
It takes repetition
1000 x 10 minutes
= 10,000 minutes
= 166 Hours
= 20 Man Days
= Lots of Automation
Networking should be boring,
if you’re having a good time something is
going horribly wrong



Install is a Development Concern
Control
Install verses Update

Development concern
◦ Its the same process
◦ Until you take every last thing seriously you will
have problems doing deployment

Integrate into Build Process
◦ Output of a build is installable package
◦ Can’t install – broken build

Give it to non experts to use
Update
Update
Update
Version
X
Release
Build
Build
Build
Build
Build

Configuration Management
◦ Like source control for software
◦ Repeatable / Automated
◦ Everything gets updated more than it gets installed

Devolve control
◦ Control what is really necessary
◦ Always push control out to others

Teams
◦ Balance of People and Roles
◦ Develop team processes

Commodity Components
◦ You should be able to replace any component
What about Monash?

What about DevOps?