Upgrade to Pro — share decks privately, control downloads, hide ads and more …

DevOps?!@

 DevOps?!@

DevOps. What iit is? The responsbilities it HAZ! Utilities helping @tasks.

Abhishek Kumar

March 21, 2013
Tweet

More Decks by Abhishek Kumar

Other Decks in Technology

Transcript

  1. DevOps ?!@
    what? HAZ! @utilities
    abionic@twitter
    abhishekkr@github

    View full-size slide

  2. Found DevOps
    http://www.youtube.com/watch?v=EOveXZhJpr4

    View full-size slide

  3. What Is DevOps?
    Solution to a Human Problem.

    View full-size slide

  4. ● From what I heard... around mid 2009,
    Patrick Debois started formulating the term DevOps.
    Main consideration being increased feedback loops
    between business, software delivery and operations.
    idea?

    View full-size slide

  5. ● From what I heard... around mid 2009,
    Patrick Debois started formulating the term DevOps.
    Main consideration being increased feedback loops
    between business, software delivery and operations.
    ● DevOps << Development IT Operations
    idea?

    View full-size slide

  6. ● From what I heard... around mid 2009,
    Patrick Debois started formulating the term DevOps.
    Main consideration being increased feedback loops
    between business, software delivery and operations.
    ● DevOps << Development IT Operations
    ● CAMS : Culture, Automation, Measurement, Sharing
    soon became, CALMS ~ Lean CAMS
    Now even Wikipedia has a decent description ( after
    loads of revision ) around the Idea.
    Go read. Form your own opinion.
    idea?
    John Willis said
    Jez Humble
    added

    View full-size slide

  7. What Is DevOps?
    Id
    e
    a

    View full-size slide

  8. culture?
    ● organization
    ○ ops perspective in inceptions, showcases and retro
    ○ one product one team ~ you build you run (amazon)
    ○ trust your people or stop being agile

    View full-size slide

  9. culture?
    ● organization
    ○ ops perspective in inceptions, showcases and retro
    ○ one product one team ~ you build you run (amazon)
    ○ trust your people or stop being agile
    ● team
    ○ mixed stand-ups
    ○ devs rotation for tasks, collaborating all the time
    ○ devs and ops, both on release call and alert panel

    View full-size slide

  10. culture?
    ● organization
    ○ ops perspective in inceptions, showcases and retro
    ○ one product one team ~ you build you run (amazon)
    ○ trust your people or stop being agile
    ● team
    ○ mixed stand-ups
    ○ devs rotation for tasks, collaborating all the time
    ○ devs and ops, both on release call and alert panel
    ● personal
    ○ broaden perspective beyond localhost
    ○ find a common ground between change and stability
    ○ automate and measure every aspect of ecosystem

    View full-size slide

  11. What Is DevOps?
    Id
    e
    a
    C
    u
    ltu
    re

    View full-size slide

  12. practice?
    ● inception
    ○ scrap out legacy ops, or fake-API-fy them
    ○ evaluate scalability over size, geo-location & time
    ○ analyze current practices and the shift required

    View full-size slide

  13. practice?
    ● inception
    ○ scrap out legacy ops, or fake-API-fy them
    ○ evaluate scalability over size, geo-location & time
    ○ analyze current practices and the shift required
    ● development
    ○ repeatable and reliable
    ○ reviewable and rapid
    ○ resilient and robust

    View full-size slide

  14. practice?
    ● inception
    ○ scrap out legacy ops, or fake-API-fy them
    ○ evaluate scalability over size, geo-location & time
    ○ analyze current practices and the shift required
    ● development
    ○ repeatable and reliable
    ○ reviewable and rapid
    ○ resilient and robust
    ● delivery
    ○ automate the automation
    ○ secure the security
    ○ pin the lynchpin, and get rolling

    View full-size slide

  15. What Is DevOps?
    Id
    e
    a
    C
    u
    ltu
    re
    Practice
    Solution to a Human Problem in Industry.
    Being Agile.

    View full-size slide

  16. Agile Manifesto
    ● Individuals and Interactions
    over Processes and Tools
    ● Working Software
    over Comprehensive Documentation
    ● Customer Collaboration
    over Contract Negotiation
    ● Responding to Change
    over Following a Plan

    View full-size slide

  17. DevOps a Community
    http://www.youtube.com/watch?v=ucc-Q_F1Gvg
    Culture where idea of continuous delivery is practiced from
    infrastructure, data and configuration management to business.

    View full-size slide

  18. No matter how well we
    ideate, create, test, surround & provide
    the entire product.
    $#!t happens
    Need to 'Monitor' every important aspect of
    product and product ambience.
    Place 'Alert' on events, that you can wiki-fy on
    how to handle.

    View full-size slide

  19. DevOps HAZ!
    Alerting

    View full-size slide

  20. Softwares don't breath on Developer nodes.
    They are born there.
    Softwares live in varied environments like
    QA/Staging/Production.
    To understand how our product works, we
    need to notice its activities on environments.
    Log & Analyze

    View full-size slide

  21. DevOps HAZ!
    Analyzing
    Alerting

    View full-size slide

  22. either you will be using
    ● PaaS (no system level tasks) Platform
    ● IaaS (no physical maintenance) Infras.
    ● NaaS (seriously, you Dinosaurus) Null
    automate everything
    required for an auto-
    scaled environment on
    that NodeModel

    View full-size slide

  23. DevOps HAZ!
    Infrastructure
    Analyzing
    Alerting

    View full-size slide

  24. more complex application's architecture is;
    the more components to interact;
    hence more to scale, monitor, log and secure...
    Analyze and Update
    Component's Properties

    View full-size slide

  25. DevOps HAZ!
    Application
    Infrastructure
    Analyzing
    Alerting

    View full-size slide

  26. predictable, reliable;
    fast feedback, quickly respond to demand;
    fail fast, continuous improvement;
    delivery power in hands of business
    Continuous Integration
    Continuous Deployment
    Continuous Delivery

    View full-size slide

  27. DevOps HAZ!
    Application
    Infrastructure
    Analyzing
    Alerting
    Continuous
    delivery

    View full-size slide

  28. Lean
    ● Eliminate Waste like unnecessary code & functionality, unclear
    requirements, less testing, bureaucracy, slow communication
    ● Amplify Learning instead of adding to documentation or planning, try &
    learn
    ● Decide as late as possible until they can be made on facts not
    assumptions. Set-based development flow allows better solutions.
    ● Deliver as fast as possible, without speed decisions can't be delayed.
    ● Empower the team, find capable people and let them use their capability.
    Enable their access to customer.
    ● Build integrity in product quality, keep it flexible, maintainable, efficient &
    responsive. Solve requirements simultaneously as the information flows in both
    direction, not sequentially.
    ● See the whole... larger the system, the more organizations &/or teams
    involved, greater the importance of having well defined relationship. A part of
    strong team is much more beneficial than minimum interaction departments.

    View full-size slide

  29. DevOps Required
    http://www.youtube.com/watch?v=jAQ7WZWr0mo

    View full-size slide

  30. until now... DevOps
    https://www.youtube.com/watch?v=lLvfCTgRtmw
    https://www.youtube.com/watch?v=o7-IuYS0iSE

    View full-size slide