1 / 35

Bridging the DEV-OPS gap with Windows Server 2012 and Visual Studio 2012

Bridging the DEV-OPS gap with Windows Server 2012 and Visual Studio 2012. Kenneth Hansen Principal Program Manager Hemant Mahawar Senior Program Manager 2-023. Basic agenda. Deploy demo environment Philosophical moment on DevOps …

oberon
Download Presentation

Bridging the DEV-OPS gap with Windows Server 2012 and Visual Studio 2012

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. Bridging the DEV-OPS gap with Windows Server 2012 and Visual Studio 2012 Kenneth Hansen Principal Program Manager Hemant Mahawar Senior Program Manager 2-023

  2. Basic agenda • Deploy demo environment • Philosophical moment on DevOps… • Key elements of deploy automation (PowerShell and Workflow Code) • Create self-service portal over automation (JavaScript and REST Code) • Party

  3. Demo Environment VM Host • Admin Client • Where IT pro does their work • Deploys Management server and Machines • Ongoing Management Connects to Management Server • Infrastructure Server • AD • DHCP • DNS • Web Servers • Machines for demo app (website) • Management Server • PowerShell WebService (O’Data) • VM Management Cmdlets

  4. Start deployment

  5. Observation one • Customer experience is king Site-up is queen

  6. Observation two • Scale “great and terrible”Systems failSystems change

  7. Netflix and Chaos Monkey “…One of the first systems our engineers…is called the Chaos Monkey. The Chaos Monkey’s job is to randomly kill instances and services within our architecture. If we aren’t constantly testing our ability to succeed despite failure, then it isn’t likely to work when it matters most – in the event of an unexpected outage…” http://techblog.netflix.com/2010/12/5-lessons-weve-learned-using-aws.html

  8. Failure – embrace it “…change our minds to assume that every machine can fail at any time without notice and that that’s OK and expected, not an OMG moment where you freak out trying to bring it back…” Friend: Mir Rosenberg

  9. Change • Business requires change • Internet businesses require rapid change • Change is the root cause of most site-downs • Hmmm…

  10. Change – embrace it “…“In the last week there were 67 deploys of 496 changes by 18 people” – Flickr Dev Blog.…”

  11. Ok – How?

  12. DevOps - Born june 2009 at Velocity conference John Allspaw & Paul Hammond“10 deploys per day; Dev& Ops cooperation at Flicker” http://velocityconf.com/velocity2009/public/schedule/detail/7641

  13. DevOps success… • CultureAutomationMeasurementSharing

  14. DevOps success… • CultureAutomationMeasurementSharing

  15. Choices • DEVops or devOPS orDevOps

  16. DevOps – frequent job posting B.S. in computer science or engineering; X+ years professional experience in software development; work experience with system configuration and deployment automation technologies

  17. Career: Opportunities and…

  18. DevOps success… • CultureAutomationMeasurementSharing

  19. “Hindsight is a Jerk”... • The trigger for this event was a network configuration change • We will audit our change process and increase the automationto prevent this mistake from happening in the future • …we focus on building software and services to survive failures http://aws.amazon.com/message/65648/ Quote: Daniel Hansen

  20. DevOps implementation success… • CultureIdempotent automationMeasurementSharing

  21. Idempotent automation • Wikipedia: “Idempotence ( /ˌaɪdɨmˈpoʊtəns/ EYE-dəm-POH-təns) is the property of certain operations in mathematics and computer science, that they can be applied multiple times without changing the result beyond the initial application.…” http://en.wikipedia.org/wiki/Idempotent

  22. Microsoft “service”... • Customer agent tried to fix something, but made it worse • PM (program manager) fixed automation to be idempotent

  23. Demo Environment VM Host • Admin Client • Where IT pro does their work • Deploys Management server and Machines • Ongoing Management Connects to Management Server • Infrastructure Server • AD • DHCP • DNS • Web Servers • Machines for demo app (website) • Management Server • PowerShell WebService (O’Data) • VM Management Cmdlets

  24. Automate deployment

  25. Not too hard (For that much benefit) Workflow Reboot Parallel Cmdlets Scripting Standards (not demoed)

  26. Doing it right…makes it simpler

  27. Automating the environment • Step one: Create task oriented objects and cmdlets • Step two: Automate deployment • Step three: Automate Self service • Step four: …

  28. Automate self-service

  29. Summary • Site-up is queen • Systems fail, systems change • Think DevOps (CAMS) • Use automation We will keep investing and improving!!

  30. PARTICIPATE IN DESIGN RESEARCH MICROSOFT DEVELOPER DIVISION DESIGN RESEARCH RETURN THE ENROLLMENT FORM TO: KARLM BY THE DOOR (OR) FILL IT ONLINE AT http://bit.ly/x6dtHt

  31. Resources • Follow us on Twitter @WindowsAzure • Get Started: www.windowsazure.com/build Please submit session evals on the Build Windows 8 App or at http://aka.ms/BuildSessions

  32. Backup

  33. Related sessions • 3-007 DevOps: Integrating development and operations for the last mile velocity • Please submit session evals on the Build Windows 8 App or at http://aka.ms/BuildSessions

  34. DevOps success… • Site-up focusMulti-disciplineBusiness focused innovation

More Related