220 likes | 387 Views
People and Process. Michael Osmond. John Monash. People and Process. We value people and interactions over process and tools (Agile Manifesto). Network Days. Controlling Configurations Static Dynamic Commodity components. Configuration Management. Create Versions Edit
E N D
People and Process Michael Osmond
People and Process We value people and interactions over process and tools (Agile Manifesto)
Network Days • Controlling Configurations • Static • Dynamic • Commodity components
Configuration Management Create Versions Edit Build Disks Release Test Production Master copies of configurations Multiple versions
Build from Source • Master configuration is not the running node • Generate standard parts – the boot file • Regenerate the disks • Rollback
Dynamic Configuration Changes made Directly to routers Then saved. Central Copy of Configurations
Commodity Components • Bulk and Cheap • Replaceable
People • Move your people up the protocol stack. • People aren’t hot swappable • Do you have a Rodney?
SOE Projects • Builds • Value of Automation • Team process
Builds Boot into DOS and connect to network Gather Configuration Information Controlled from A floppy boot disk Format Disk Copy down Windows source and set Unattended install Unattended Windows Install Across multiple Reboots Install required software User profile configured on logon
Builds – Distribution Dev / Test IGOR Master Builds
Team Processes • Develop team processes • People need to know their roles • It takes repetition
The 10 Minute Rule 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
Software Development • Install is a Development Concern • Control • Install verses Update
Install • 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
Install or Updates – Same Result Update Version X Update Update
Incremental Updates Release Build Build Build Build Build
Summary • 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
Summary • Teams • Balance of People and Roles • Develop team processes • Commodity Components • You should be able to replace any component
Post Script What about Monash? • What about DevOps?