1 / 22

People and Process

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

webb
Download Presentation

People and Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. People and Process Michael Osmond

  2. John Monash

  3. People and Process We value people and interactions over process and tools (Agile Manifesto)

  4. Network Days • Controlling Configurations • Static • Dynamic • Commodity components

  5. Configuration Management Create Versions Edit Build Disks Release Test Production Master copies of configurations Multiple versions

  6. Build from Source • Master configuration is not the running node • Generate standard parts – the boot file • Regenerate the disks • Rollback

  7. Dynamic Configuration Changes made Directly to routers Then saved. Central Copy of Configurations

  8. Commodity Components • Bulk and Cheap • Replaceable

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

  10. SOE Projects • Builds • Value of Automation • Team process

  11. 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

  12. Builds – Distribution Dev / Test IGOR Master Builds

  13. Team Processes • Develop team processes • People need to know their roles • It takes repetition

  14. The 10 Minute Rule 1000 x 10 minutes = 10,000 minutes = 166 Hours = 20 Man Days = Lots of Automation

  15. Networking should be boring, if you’re having a good time something is going horribly wrong

  16. Software Development • Install is a Development Concern • Control • Install verses Update

  17. 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

  18. Install or Updates – Same Result Update Version X Update Update

  19. Incremental Updates Release Build Build Build Build Build

  20. 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

  21. Summary • Teams • Balance of People and Roles • Develop team processes • Commodity Components • You should be able to replace any component

  22. Post Script What about Monash? • What about DevOps?

More Related