Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

No IT Left Behind - Connecting the Software-Defined Data Center to Multi-Modal IT

337 views

Published on

No IT Left Behind - Connecting the Software-Defined Data Center to Multi-Modal IT

Published in: Technology
  • You can ask here for a help. They helped me a lot an i`m highly satisfied with quality of work done. I can promise you 100% un-plagiarized text and good experts there. Use with pleasure! ⇒ www.WritePaper.info ⇐
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No IT Left Behind - Connecting the Software-Defined Data Center to Multi-Modal IT

  1. 1. NOITLEFT BEHIND Connecting the software- defined data center to multi-modal IT 1
  2. 2. • Setting the Stage • BiModal Vs. MultiModal • Our Approach • Summary and Lessons Learned AGENDA 2
  3. 3. 18 Years in Business SETTINGTHE STAGE 3
  4. 4. Focused on Developing Solutions for the DoD, DHS and other Federal Agencies • Wide Range of Compliance Challenges SETTINGTHE STAGE 4
  5. 5. Diverse Staff • 300+ Software Engineers • 150+ Field Personnel • 100+ Active Projects at any time SETTINGTHE STAGE 5
  6. 6. 150+ Corporate Systems • 3rd Party and Homegrown! SETTINGTHE STAGE 6
  7. 7. Development • Research and Development • Enhancement • Bug fixes Life Cycle • Configuration Mgmt • Release Mgmt • Packaging Infrastructure • Test & Integration • Documentation • Help Desk Customers • Maintenance • Training • Pro Services SETTINGTHE STAGE 7
  8. 8. LANDSCAPE 8
  9. 9. LANDSCAPE 9
  10. 10. LANDSCAPE 10
  11. 11. APPLICATIONS • Unanet, JIRA, SharePoint, Finance, HR… FABRIC • VMWare, NSX, Laas, Paas, ... NETWORK • Routers, Phones, VTC, … COMPUTE • UCS, Towers, Laptops, ... STORAGE • NetApp, EMC, OneDrive, … LANDSCAPE 11
  12. 12. 12 We have built infrastructure PROGRESS
  13. 13. 13 But building infrastructure is not the goal. PROGRESS
  14. 14. • We need to be more Agile to keep up with rapidly changing business needs • Virtualization Alone Not Sufficient! • Tenets NEEDFORCHANGENOMOREISLANDS 14
  15. 15. Traditional IT focused on Stability and Efficiency BIMODALOPTION 15
  16. 16. BIMODALOPTION DevOps IT focused on new tools and agile processes 16
  17. 17. PROS: • Reduced risk for ongoing core business activities • Frees forward looking teams to not worry about the day to day BIMODALOPTION 17
  18. 18. PROS: • Reduced risk for ongoing core business activities • Frees forward looking teams to not worry about the day to day • Ignores the interdependence between past and future • Near term increase in resource needs • Significant cultural impact • ”haves and have nots” • Latent talent ignored BIMODALOPTION CONS: 18
  19. 19. • Systems evolve at a natural pace • Some applications will die off MULTI-MODALOPTION Migrate Everything 19
  20. 20. • Responsiveness and reliability are the same thing! MULTI-MODALOPTION Treat All Systems as Agile 20
  21. 21. • Each piece of the enterprise is at a different place on the continuum and will move forward at a different speed (crawl/walk/run) • Dynamic on-premise environment that supports flexible, timely and relevant capabilities while adhering to a wide range of compliance challenges MULTI-MODALOPTION DevOps approach spanning the entire enterprise 21
  22. 22. 22 HOWAREWEDOINGTHIS?
  23. 23. 23 APPROACH Collaborate and Communicate Fail Fast, Recover Fast and learn Always Keep Learning Technologies Small Batch Size Dsmorse_iss
  24. 24. 24 • Ad hoc is bad hoc • Solution “discovered” on production • No one person has whole story • Configuration drift • Non existent Documentation • Any manual task can introduce human error • We shouldn’t have to call you on your on day off • Goals: • Repeatable, Repeatable, Repeatable, … • Known state • DRY (yeah I used to be a dev) WHYDEVOPS Dsmorse_iss
  25. 25. 25 • Ad hoc is bad hoc • Solution “discovered” on production • No one person has whole story • Configuration drift • Non existent Documentation • Any manual task can introduce human error • We shouldn’t have to call you on your on day off • Goals: • Repeatable, Repeatable, Repeatable, … • Known state • DRY (yeah I used to be a dev) WHYDEVOPS Dsmorse_iss
  26. 26. 28 Frequent small changes are less risky than a Large release SMALLBATCH SIZE Dsmorse_iss
  27. 27. 29 SMALLBATCH SIZE Fail Fast: Tracking MTTR • Small Batch • Easy to ID change • Disciplined about Config Management • Known state before & after • Automated scripts for backup & deploy • Scripts also verify expected stat Anti-fragile thinking to allow us to upgrade live systems during regular hours Dsmorse_iss
  28. 28. 30 • Desired state configuration ANSIBLE- WHATGOESWHERE Dsmorse_iss
  29. 29. 31 • Desired state configuration • It is just a YML file ANSIBLE- WHATGOESWHERE Dsmorse_iss
  30. 30. 32 • Desired state configuration • It is just a YML file • Agentless! Uses SSH ANSIBLE- WHATGOESWHERE Dsmorse_iss
  31. 31. 33 • Desired state configuration • It is just a YML file • Agentless! Uses SSH • Idempotent Idempo-What: “Operations in mathematics and computer science, that can be applied multiple times without changing the result beyond the initial application.” – wikipedia ANSIBLE- WHATGOESWHERE Dsmorse_iss
  32. 32. 34 • Docker containers increase portability DOCKER,DOCKER DOCKER Dsmorse_iss
  33. 33. 35 • Docker containers increase portability • Increase density & VM utilization DOCKER,DOCKER DOCKER Dsmorse_iss
  34. 34. 36 • Docker containers increase portability • Increase density & VM utilization • Easier Deployment DOCKER,DOCKER DOCKER Dsmorse_iss
  35. 35. 37 • Docker containers increase portability • Increase density & VM utilization • Easier Deployment • Immutable images removes complexity, changes the way we take care of our apps DOCKER,DOCKER DOCKER Dsmorse_iss
  36. 36. 38 SYSTEM DIAGRAM Dsmorse_iss
  37. 37. 39 SYSTEM DIAGRAM Dsmorse_iss
  38. 38. 40 SYSTEM DIAGRAM Dsmorse_iss
  39. 39. 41 A critical part of DevOps is looking at change metrics • Did we achieve the desired outcome? • Should we pivot or persevere? • What problems do we not know we have COLLABORATEAND COMMUNICATE Dsmorse_iss
  40. 40. 42 A critical part of DevOps is looking at change metrics • Did we achieve the desired outcome? • Should we pivot or persevere? • What problems do we not know we have Closed systems have been replaced by Open JIRA projects • All changes are public! COLLABORATEAND COMMUNICATE Dsmorse_iss
  41. 41. 43 A critical part of DevOps is looking at change metrics • Did we achieve the desired outcome? • Should we pivot or persevere? • What problems do we not know we have Closed systems have been replaced by Open JIRA projects • All changes are public! HipChat was brought in to allow automated flow of relevant data into tailored rooms • Provide context to the sequence of events • Real-time discussion, feedback and change! COLLABORATEAND COMMUNICATE Dsmorse_iss
  42. 42. 44 Team Development • Ongoing cross-training and mentoring • Pair programing workstation to enhance our ability to mentor each other KEEPLEARNING Dsmorse_iss
  43. 43. 45 Team Development • Ongoing cross-training and mentoring • Pair programing workstation to enhance our ability to mentor each other Git Flow • Pull Requests • Peer Review KEEPLEARNING Dsmorse_iss
  44. 44. 46 Team Development • Ongoing cross-training and mentoring • Pair programing workstation to enhance our ability to mentor each other Git Flow • Pull Requests • Peer Review Blameless Retrospectives • Posted to Confluence • 100% transparency KEEPLEARNING Dsmorse_iss
  45. 45. 47 • Reliable alerts on public facing systems. • The structures we put in place to support 12 factor apps, can also be applied to our legacy systems to increase commonality o Decrease cognitive shift o Embrace changes on both sides • Growing number of Anisble roles for common tasks o Firewalls, NTP, SMNP, common tools • Performed our first few canary rollouts WHEREAREWE TODAY? Dsmorse_iss
  46. 46. 48 More of the same! • Scripting • Containerization • Monitoring • Collaboration • Next 6 months Dsmorse_iss
  47. 47. 49 More of the same! • Scripting • Containerization • Monitoring • Collaboration New Stuff! • vRealize/NSX for Self- Service • vSphere integrated containers • Docker data center • Next 6 months Dsmorse_iss
  48. 48. 50 More of the same! • Scripting • Containerization • Monitoring • Collaboration New Stuff! • vRealize/NSX for Self- Service This is working! NEXT6MONTHS Dsmorse_iss
  49. 49. 51 After 9 Months • Cleared more than 3 years of backlog! • Migrated from manual changes to scripted changes • Containerized workloads running on their own • Containers as a Service SUMMARYANDLESSONSLEARNED Dsmorse_iss
  50. 50. 52 After 9 Months • Cleared more than 3 years of backlog! • Migrated from manual changes to scripted changes • Containerized workloads running on their own • Containers as a Service Lessons Learned • Establish Metrics Early On • Change Takes Time • Expect and Embrace Failure • Technology Enables, but Not a Panacea SUMMARYANDLESSONSLEARNED Dsmorse_iss

×