People and Process

Preview:

DESCRIPTION

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 - PowerPoint PPT Presentation

Citation preview

People and ProcessMichael Osmond

John Monash

We value people and interactions

over process and tools

(Agile Manifesto)

People and Process

Controlling Configurations- Static- Dynamic

Commodity components

Network Days

Configuration Management

Create Versions

EditBuild Disks

Release

Test

Production

Master copies of configurationsMultiple versions

Master configuration is not the running node

Generate standard parts – the boot file Regenerate the disks Rollback

Build from Source

Dynamic Configuration

Central Copy of Configurations

Changes madeDirectly to routersThen saved.

Bulk and Cheap Replaceable

Commodity Components

Move your people up the protocol stack. People aren’t hot swappable Do you have a Rodney?

People

Builds Value of Automation Team process

SOE Projects

Builds

Gather Configuration Information

Copy down Windows source and set Unattended install

Unattended Windows Install

Install required software

Controlled from A floppy boot disk

Format Disk

Boot into DOS and connect to network

Across multiple Reboots

User profile configured on logon

Builds – Distribution

Master Builds

IGOR

Dev / Test

Develop team processes People need to know their roles It takes repetition

Team Processes

1000 x 10 minutes = 10,000 minutes= 166 Hours= 20 Man Days

= Lots of Automation

The 10 Minute Rule

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

Software Development

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

Install or Updates – Same Result

Version X

Update

Update Update

Incremental UpdatesRelease

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

Summary

Teams◦ Balance of People and Roles◦ Develop team processes

Commodity Components◦ You should be able to replace any component

Summary

What about Monash?

What about DevOps?

Post Script

Recommended