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

June2019 Meetup: Click a Button and your Enterprise IT runs in the Cloud. How far can we really go? by Stefano Malle

June2019 Meetup: Click a Button and your Enterprise IT runs in the Cloud. How far can we really go? by Stefano Malle

WHY is automation important and WHAT are the prerequisites to automate your IT landscape? HOW does Microsoft IT (CSEO) do it and WHICH options do you have for your landscape? This session gives an overview about topics such as "Infrastructure as Code (IaC)", DevSecOps, Pipelines, ARM and Azure Governance.

Speaker: Stefano Mallè, Chief Technology Officer at Microsoft Switzerland
After his graduation in Computer Science at the Swiss Federal Institute of Technology, Stefano Mallè has worked initially in the Swiss financial sector, including positions at UBS and Credit Suisse, before joining Microsoft in 2003. At Microsoft, he has been mainly responsible for the adoption of new technologies, working closely with enterprises, ISVs, and startups and leading teams of technical evangelists and cloud solution architects.
In April 2014, he became member of the Executive Board of Microsoft Switzerland before assuming the role of Chief Technology Officer in October 2018, with focus on helping IT Leaders being successful with their adoption of cloud computing and on exploring with Business Leaders the potential of the latest technologies.

You can find him at:
http://www.linkedin.com/in/smalle
https://twitter.com/stefanomalle
https://blog.smalle.com/

Azure Zurich User Group
PRO

June 11, 2019
Tweet

More Decks by Azure Zurich User Group

Other Decks in Technology

Transcript

  1. https://blog.smalle.com

  2. To Cloud Native June 2019, #OnlyWhatYouDeployMatters Stefano Mallè CTO Microsoft

    Switzerland
  3. None
  4. None
  5. Once Upon A Time… We Had Many, Many Datacenters…

  6. Our Journey to the Cloud

  7. Our Journey to the Cloud

  8. Our Journey to the Cloud

  9. Our Journey to the Cloud

  10. Our Journey to the Cloud

  11. Our Journey to the Cloud

  12. Our Journey to the Cloud

  13. Our Journey to the Cloud

  14. Our Journey to the Cloud

  15. Why microservices? • Independent development and freedom to choose technology

    • Independent deployment and release cycle • Granular scaling • Simplicity • Fault isolation Microservice applications are composed of small, independently versioned, and scalable customer-focused services that communicate with each other over standard protocols with well-defined interfaces. Microservice is intended as a unit of (business) capability that at minimum undergoes the same needs for security and (frequency of) usage (which impact scalability).
  16. None
  17. DevOp-pers are from Mars

  18. DevOps DevOps is the union of people, process, and products

    to enable continuous delivery of value to your end users. “ ”
  19. DevOps

  20. The union of people, process, and tools to deliver continuous

    value to customers DevOps
  21. DevOps

  22. DevOps

  23. DevOps

  24. DevOps

  25. DevOps Never Roll Back! Use Feature Flags Telemetry Shift-Left Test

    earlier, Pull-Request Shift-Right There is no place like production, Canary Release
  26. DevOps Don’t aim for perfection. Start where it hurts the

    most.
  27. None
  28. 50 Shades of Code

  29. Infrastructure Platform

  30. Infrastructure Platform Platform Azure Microsoft

  31. Infrastructure Platform Platform Definition Files (Scripts/Code) Azure Azure Customer -as-Code

  32. Infrastructure Characteristics • Consistent and repeatable routines • Changes are

    made to definitions • DevOps practices applies • Versioning & Auditing • Automated Testing &TDD • CI/CD -as-Code Benefits • “No deployment fear” – Continuous delivery and improvement • Reduction of repetitive tasks, more time for adding value • Application teams define, provision, and manage the resources they need, without needing the Platform team to do it for them. • Recovery from failures are quicker and easier An approach to infrastructure automation based on practices from software development. Azure
  33. Key Take-Away! Everything is Code! You can build a full

    platform in minutes/hours. DevOps is the bread & butter for all engineers (app AND platform). ➔ Shift in culture(skills, organization, processes,…)
  34. None
  35. Peter Pan

  36. The Big Picture: IT-as-Code (Cloud Native Operation) Network Landing Zones

    Git Repositories Git Repositories App (App & Infra Code) App (App & Infra Code) App (App & Infra Code) Shared Services Guardrails for the App Teams (Policies, RBAC, Blueprints…) Git Repositories Git Repositories Git Repositories Platform Applications API Management Everything is Code!
  37. Platform The Big Picture: IT-as-Code (Cloud Native Operation) Network Landing

    Zones Git Repositories Git Repositories App (App & Infra Code) App (App & Infra Code) App (App & Infra Code) Shared Services Guardrails for the App Teams (Policies, RBAC, Blueprints…) Git Repositories Git Repositories Git Repositories Applications API Management Everything is Code!
  38. Shift Left (Deliver Compliant Code Earlier/Faster) DELIVER OPERATE DE VELOP

    Security
  39. Control: First Cloud Approach Security? Compliance? Control! Developers Operations

  40. Control: Cloud Native Governance Management Groups Policy Templates RBAC Blueprints

    Policies Sentinel Security Center Advisor Activity Alerts Monitor Metrics Insights Developers Operations
  41. DevOps: First Cloud Approach • Definitions for a given application’s

    infrastructure is managed separately from the code for that application. • Often, each is managed by a separate team. This follows the tradition of separating development and operations concerns, but it creates dependencies and can add technical and organizational overhead. • The overhead of changes to infrastructure increases exponentially with the number of applications and services that share it. • This overhead is reflected in time, cost, and risk.
  42. DevOps: Cloud Native Manage application software and its supporting infrastructure

    as a single concern. Having the code together makes it easy to manage, test, and deliver them as a unit.
  43. Copyright Eleonora Gianinetto It is time to leave Neverland and

    embrace a grown-up DevSecOps Culture!
  44. Business Services Microservices DevOps Infrastructure as-Code Cloud Native Operation

  45. Business Services Microservices DevOps Infrastructure as-Code Cloud Native Operation Deployments

    per day with 96’000 Engineers using Azure DevOps.
  46. [email protected] https://www.linkedin.com/in/smalle/ https://blog.smalle.com Thank you! Deployment Capacity = (Microservices+DevOps+Infrastructure-as-Code)*Culture

  47. An example

  48. Introducing Azure DevOps Deliver value to your users faster using

    proven agile tools to plan, track, and discuss work across your teams. Build, test, and deploy with CI/CD that works with any language, platform, and cloud. Connect to GitHub or any other Git provider and deploy continuously. Get unlimited, cloud-hosted private Git repos and collaborate to build better code with pull requests and advanced file management. Test and ship with confidence using manual and exploratory testing tools. Create, host, and share packages with your team, and add artifacts to your CI/CD pipelines with a single click. Azure Boards Azure Repos Azure Pipelines Azure Test Plans Azure Artifacts https://azure.com/devops ➔
  49. None
  50. Git Repositories App (App & Infra Code) App (App &

    Infra Code) 1-Click Virtual Datacenter IAM Network (Perimeter) Landing Zones Hardened Services (catalog) App (App & Infra Code) Service Templates (catalog) Define the guardrails for the App Teams (Policies, RBAC Groups, vNets, DMZ, AAD, hub-spoke…) Platform Team App Team Git Repositories Git Repositories Git Repositories Git Repositories Deployment/Release Gates Shared Services
  51. 1-Click Virtual Datacenter Network (Perimeter) Landing Zones Organization Master (Shared

    Services) App 1 App n