Platform as a Service with Kubernetes and Mesos
Download as PPTX, PDF8 likes3,149 views
The document discusses the design and management of a Platform as a Service (PaaS) using Kubernetes, Mesos, and OpenStack. Key topics include resource management, container orchestration, high availability, and security considerations for multi-tenant environments. It emphasizes the importance of using a private Docker registry and employing continuous integration and deployment practices for efficient service rollout.
Platform as a Service with Kubernetes and Mesos
- 1. Platform as a Service Kubernetes/Mesos + Openstack Miguel Zuniga about.me/miguelzuniga Freenode miguelzuniga
- 2. Agenda • Design your Platform • Architecture • Managing Resources • Managing Containers • High Availability • Security • Design your Platform Services • Rolling out new services • Questions
- 3. Design your Platform 3Copyright © 2014 Symantec Corporation
- 4. Design your Platform • Who will be your users/customers? – Developers / Architects / Ops – Customers • Identify workloads and applications – CPU / Memory / IO – Stateful or Stateless • How secure do you need to be? – Multi-tenant – Network Isolation • Multi Cloud? Multi Datacenter? Hybrid? 4 Copyright © 2014 Symantec Corporation
- 5. Architecture 5Copyright © 2014 Symantec Corporation
- 6. Architecture – Mesos + Openstack 6 Copyright © 2014 Symantec Corporation
- 7. Architecture – Kubernetes + Openstack Copyright © 2014 Symantec Corporation 7
- 8. Architecture – Kubernetes/Mesos + Openstack Copyright © 2014 Symantec Corporation 8
- 9. Managing your Resources 9Copyright © 2014 Symantec Corporation
- 10. Managing your Resources • Resource management is done by mesos framework. • All the kubernetes components run as marathon tasks. • All the pods/containers are run as mesos tasks. • Mesos can manage either VM or Physical Servers. 10 Copyright © 2014 Symantec Corporation
- 11. Managing your Containers 11Copyright © 2014 Symantec Corporation
- 12. Managing your Containers • Kubernetes takes care of Pod / Replica and Service Orchestration. • Each pod and its respective containers are created by the mesos KM executor. • Users can interact with Kubernetes either by CLI or API. • Kubernetes maintains containers in replica controllers running constantly. 12 Copyright © 2014 Symantec Corporation
- 13. High Availability 13Copyright © 2014 Symantec Corporation
- 14. High Availability Mesos Kubernetes Kubernetes / Mesos • Use Marathon to keep containers up and running • Requires external LB (hardware or software) to balance across containers. • HA for kubernetes componentes is out of scope. • Replicas controllers to keep pods and containers up and running • Kube Proxy takes care of load balancing • HA for kubernetes components is managed by mesos and marathon. • HA for pods is handle by replicas. • Load balancing can be done with External LB (i.e. haproxy) or kube- proxy. 14 Copyright © 2014 Symantec Corporation
- 15. Security 15Copyright © 2014 Symantec Corporation
- 16. Security • Network Security is provided by SDN isolation. • Provision mesos-kubernetes cluster by project or user. • Run docker with SE Linux enabled (RHEL based). • Enable Iptables Drop policy by default on each mesos slave. 16 Copyright © 2014 Symantec Corporation
- 17. Design your Platform Services 17Copyright © 2014 Symantec Corporation
- 18. Design your Platform Services • Think of cattle. • Think of processes not VMs. • VM or Container? • Complexity of access… To many jumps? • You have Marathon… Use it. • Use a private docker registry. • Microservices? What is that? • Your PaaS, even when is generic enough, is not a silver bullet. 18 Copyright © 2014 Symantec Corporation
- 19. Rolling out new services 19Copyright © 2014 Symantec Corporation
- 20. Rolling out new services • Use a private docker registry to track the container images required for each application/process stack. • Create a level of abstraction (UI) easy to use for your users. • Manage clustered services with Marathon. • Remember containers are processes… not condensed VM’s. • Use CICD to create new versions of your containers. • OSS – Continuous + Strategos 20 Copyright © 2014 Symantec Corporation
- 21. Rolling out new services Copyright © 2014 Symantec Corporation 21
- 22. Links and References • Continuous http://github.com/symantec/continuous • Strategos available June 30 http://strategos.io • Kubernetes http://kubernetes.io • Mesos http://mesos.apache.org/ • Marathon https://mesosphere.github.io/marathon/ Copyright © 2014 Symantec Corporation 22
- 23. Thank you! Copyright © 2014 Symantec Corporation. All rights reserved. Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This document is provided for informational purposes only and is not intended as advertising. All warranties relating to the information in this document, either express or implied, are disclaimed to the maximum extent allowed by law. The information in this document is subject to change without notice. Miguel Zuniga Twitter @mikezuniga Freenode miguelzuniga Google plus +MiguelZuniga 23 Questions?
Editor's Notes
- #2: Tip: simple SEO adjustments can make your presentation more discoverable. Read this PDF for best practices: http://seo.ges.symantec.com/seo-best-practices-for-file-optimization.pdf