1DEVOPS ISSUSTAINABLE OPS&INFRASTRUCTUREIMMUNOLOGYV0.4 prepared and presented by Julie TsaiDec. 17, 2012
History2       Concepts borrows heavily (or stolen) from        classic papers “Bootstrapping an        Infrastructure” b...
What does this fix?3       How do I keep X (files, permissions, services) from        changing unpredictably?       When...
Centralized, Automated4    Standards     Sounds intutive, but….     Obvious examples in SA world –     LDAP, DNS, logserve...
What does this look like?5    1) Version-Controlled Published Configurations    2) Master Fileserver Repository    3) Auto...
Version-Controlled Published6    Configurations       Git, svn, perforce, cvs – SCM of choice       Promise Theory – con...
Master Fileserver Repository7       “Gold” configurations               http://opensource.sys-con.com/node/1734347
Automated Propagation and8    Maintenance                 http://puppetlabs.com
Monitoring & Self-Healing9       What’s the current state       Post-change state       Event-driven hooks from monitor...
What do we gain?10     A lot:      Known configs/profiles assured to reflect live       system state      auditable easy...
Good Reading11        Classic “Bootstrapping an Infrastructure,” LISA ’98 -         http://www.infrastructures.org/papers...
Prochain SlideShare
Chargement dans... 5
×

Dev ops and_infrastructure_immunology_v0.4

2,011

Published on

2 commentaires
4 mentions J'aime
Statistiques
Remarques
Aucun téléchargement
Vues
Total des vues
2,011
Sur Slideshare
0
À partir des ajouts
0
Nombre d'ajouts
1
Actions
Partages
0
Téléchargements
16
Commentaires
2
J'aime
4
Ajouts 0
No embeds

No notes for slide
  • What does DevOps mean generally? - cross-discipline pollination – code as infrastructure, continuous improvement, surgical changes, holistic view, end-to-end visibility, self-healing systems - shared risk/responsibility for classic responsibilties - potential areas to be careful: blurred responsibilities, defining expertise down, mistaking outsourcing for management (i.e. a lot of startups leveraging Amazon – DevOps as NoOps)
  • + add diagram of roadmap (puppet cfengine/chef?)+ complexity management
  • Dev ops and_infrastructure_immunology_v0.4

    1. 1. 1DEVOPS ISSUSTAINABLE OPS&INFRASTRUCTUREIMMUNOLOGYV0.4 prepared and presented by Julie TsaiDec. 17, 2012
    2. 2. History2  Concepts borrows heavily (or stolen) from classic papers “Bootstrapping an Infrastructure” by Steve Traugott and Joel Huddleston, and Mark Burgess’s “Computer Immunology” and Promise Theory  Personal experience – syncing scripts, predicting change, better communication
    3. 3. What does this fix?3  How do I keep X (files, permissions, services) from changing unpredictably?  When did change happen? Is it related to the downtime incident we had? Or unpredictable deployments?  Who/what group made that change?  The system is growing (or has) arms and legs in unpredictable, astonishing directions making it difficult/impossible to reproduce. Or make minor changes: Deployments are the equivalent of leveling the whole house to change one light bulb.  Critical parts of the infrastructure reside in peoples heads - bad for scaling the company, bad for individual development. Put the real estate to better use.
    4. 4. Centralized, Automated4 Standards Sounds intutive, but…. Obvious examples in SA world – LDAP, DNS, logservers, data consistency, NFS fileservers Same principle as programmers’ DRY
    5. 5. What does this look like?5 1) Version-Controlled Published Configurations 2) Master Fileserver Repository 3) Automated Propagation and Maintenance The heart of where much of today’s DevOps work exists: This is where tools like cfengine, puppet, and chef literally “level-up” the way your infrastructure is managed. See links on last slide for more information. 4) Monitoring the Infrastructure 5) Self-Healing
    6. 6. Version-Controlled Published6 Configurations  Git, svn, perforce, cvs – SCM of choice  Promise Theory – connected but independent agents cannot wrest guarantees from each other – they can only truly obligate themselves. But this can be leveraged to coordinate.
    7. 7. Master Fileserver Repository7  “Gold” configurations http://opensource.sys-con.com/node/1734347
    8. 8. Automated Propagation and8 Maintenance http://puppetlabs.com
    9. 9. Monitoring & Self-Healing9  What’s the current state  Post-change state  Event-driven hooks from monitoring back to automation tool creates self-healing  i.e. Nagios, Empirix, monitoring tool of choice  End-to-end change visibility – intended changes, logged changes, monitoring events
    10. 10. What do we gain?10 A lot:  Known configs/profiles assured to reflect live system state  auditable easy-to-administer security configurations  predictable change and rollback  Large-scale updates that are seamless, uniform, and logged.  Agile compliance!  Uptime!  More free time! To devote to higher-level activities
    11. 11. Good Reading11  Classic “Bootstrapping an Infrastructure,” LISA ’98 - http://www.infrastructures.org/papers/bootstrap/bootstr ap.html  Self-Healing Networks - http://onlamp.com/pub/a/onlamp/2006/05/25/self- healing-networks.html?page=1  Relative origins of cfengine, puppet, chef - http://verticalsysadmin.com/blog/uncategorized/relativ e-origins-of-cfengine-chef-and-puppet  Promises of DevOps - http://cfengine.com/markburgess/blog_devops.html  Promise Theory - http://en.wikipedia.org/wiki/Promise_theory
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×