Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Boris Devouge - UK Azure Containers Service

1.002 Aufrufe

Veröffentlicht am

As containers and micros services technologies arise, the first part of this talk will concentrate on the evolution of infrastructures towards containerization, best practices, deployment models as well as lessons learned from early adopters. The second part we’ll explore the Azure container Service preview, what it provides and what will come next.

BIO:

Boris Devouge, Director of Open Source Strategy, Microsoft.

Boris’s background lies in High Performance infrastructures, Virtualization, Cloud and OpenSource technologies. Starting out in his career, Boris worked for HP, supporting the CERN Linux deployment for the LHC in Switzerland. He then served as Sales Engineering Manager at Red Hat, dealing with early adoption of Linux in Large Organizations and the rise of virtualization stacks. At Canonical, the company behind Ubuntu Linux, Boris led a team bundling the first version of Eucalyptus Private Cloud within the server distribution. As Director of Global services for Nebula, Inc, a start-up based in Palo Alto, he was part of the team that created the OpenStack project along with NASA employees. Boris then worked as an OpenStack Lead Technologist for HP cloud Services and HP Helion. Today Boris is leading and spearheading the Open and Innovation efforts of Microsoft in the United Kingdom.

Veröffentlicht in: Technologie
  • Als Erste(r) kommentieren

  • Gehören Sie zu den Ersten, denen das gefällt!

Boris Devouge - UK Azure Containers Service

  1. 1. Azure Container Service preview Boris Devouge OpenSource Strategy Lead Microsoft UK The Bell Pub – 01/03/2016 – UK Azure User Group
  2. 2. The NEW Microsoft Dead and buried: Microsoft's holy war on open-source software “Years ago, Microsoft's CEO described open source as a cancer. Times have changed. Just ask 22-year Redmond veteran and open-source proponent Mark Hill.” Charles Cooper Redmond top man Satya Nadella: 'Microsoft LOVES Linux‘ Neil McAllister Microsoft: the Open Source Company “This is not your dad’s Microsoft” Steven J. Vaughan-Nichols Tweet “Azure Container Service is different and offers the broadest hint yet that Microsoft wants to build real products with open source, not merely leverage it where it's convenient” Serdar Yegulalp
  3. 3. = Managed by customer Traditional IT = Managed by vendor Cloud Service Models
  4. 4. • API programmatic interface to manage the deployment of resources (Compute, Storage, Network) • Elasticity – Scaling without preplanning or any topology changes • Layer on top of virtualization framework – multiple hypervisors working together • Underlying hardware and physical limits abstracted • Runs static VM images with ephemeral local storage (erased/lost on termination) • Implements different pieces of infrastructure as a web services (block and object stores, metadata, scheduler, networks and many more)
  5. 5. • Self Service IT o Cuts down the internal provisioning time • Test/Dev environments o Or similar “Build and Tear” environments – Agility • Sporadic dynamic platforms: one time use / repurpose • Continuous Integration (CI), GTM testing • Automation of Infrastructure / stacks deployment • Programmatic operations on VMs / scenarios
  6. 6. • Mass Horizontal applications (i.e. web farms) o Ideal scale-out model (presentation/http layer) o Single basic image – quick scale up and down, lightweight and good density • Service / Hosting / Cloud providers o The new Standard (Cloud based) o Want to become a cloud provider instead? o Who want to compete with the big Cloud vendors?
  7. 7. • Applications that are CPU or I/O bound o Number crunching, factorizations, compilations o Heavy/Large/Clustered DB or background I/O • Ultra Critical applications o Do not expect zero downtime in cloud - just resilience • VDI Hosts o Despite the popular idea • Dynamic application clusters o Lack of Multicast in virtual networks
  8. 8. Observations • Needs adapted workloads: scale out, stateless and resilient • Needs Configuration Management and/or Orchestration to be properly exploited with Automation • IaaS uses virtualization o Poor virtualization use cases will be poor on IaaS
  9. 9. Containers
  10. 10. Containers
  11. 11. Containers
  12. 12. Server Host OS Hypervisor Server Host OS Docker Engine Guest OS Guest OS Guest OS Bins/Libs Bins/Libs Bins/Libs App A App A’ App B Bins/Libs Bins/Libs AppA AppA’ AppB AppB’ AppB AppB’ AppB AppB’ Containers are isolated, but share OS and, where appropriate, bins/libraries
  13. 13. • Scales by cloning the app on multiple servers/VMs/Containers Monolithic application approach Microservices application approach • A microservice application separates functionality into separate smaller services. • Scales out by deploying each service independently creating instances of these services across servers/VMs/containers • A monolith app contains domain specific functionality and is normally divided by functional layers such as web, business and data App 1 App 2App 1
  14. 14. Service FabricHigh Availability Hyper-Scale Hybrid Operations High Density Microservices Rolling Upgrades Stateful services Low Latency Fast startup & shutdown Container Orchestration & lifecycle management Replication & Failover Simple programming models Resource balancing Self-healingData Partitioning Automated Rollback Health Monitoring Placement Constraints Azure Private cloud Other clouds
  15. 15. Azure Container Service High AvailabilityHyper-Scale Microservices Container hosts as cattle Flexible programming models Azure Private cloud Other clouds Open Source Orchestration Host cluster management Open Source Container ManagementHigh Availability High Density Placement Constraints Fast startup & shutdown Self-healing
  16. 16. • Scales by cloning the app on multiple servers/VMs/Containers Monolithic application approach Microservices application approach • A microservice application separates functionality into separate smaller services. • Scales out by deploying each service independently creating instances of these services across servers/VMs/containers • A monolith app contains domain specific functionality and is normally divided by functional layers such as web, business and data App 1 App 2App 1
  17. 17. Docker Hub
  18. 18. Announcing You can deploy a Docker capable, Apache Mesos cluster today from : http://go.microsoft.com/fwlink/?linkid=733370&clcid=0x409
  19. 19. Containers Container ToolingService Tooling Layer Supported Technologies Configuration as Code ARM, Dockerfile, Docker Compose Host cluster management VM Scale Sets Container orchestration Docker Swarm, Chronos, Marathon, Apache Mesos Monitoring OMS, App Insights
  20. 20. Deploy using Portal or ARM
  21. 21. • • • • • Layer Supported Technologies (2015) Configuration as Code ARM, Dockerfile, Docker Compose Host cluster management VM Scale Sets Container orchestration Docker Swarm, Chronos, Marathon, Apache Mesos Monitoring OMS, App Insights
  22. 22. DevOps with Containers Developers Operations automates deployment and monitors deployed apps from central repository Operations collaborates with developers to provide app metrics and insights Developers update, iterate, and deploy updated containers Central Repository Containers pushed to central repository
  23. 23. Build Continuous Integration Continuous Delivery
  24. 24. Open Cloud
  25. 25. All platforms, All clients https://github.com/azure
  26. 26. https://azure.microsoft.com/en-us/documentation/articles/xplat-cli/
  27. 27. https://azure.microsoft.com/en-us/documentation/templates/
  28. 28. h

×