Data Center Design / Microservices
17 likes•3,265 views
The document discusses Samsung's initiatives around containerization and microservices, highlighting their role in transforming IT infrastructure by improving efficiency and operational automation. It emphasizes the shift of container usage from large service providers to enterprises, enabling new architectures, DevOps practices, and better management of applications. Additionally, it outlines key considerations for future data center designs, advocating for open-source solutions and container orchestration for enhanced control and cost reduction.
Data Center Design / Microservices
- 1. Data Center Design Microservices Bob Wise Samsung SDS Research America Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 2
- 2. Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved This presentation is intended to provide information concerning Samsung’s efforts around containers and container orchestration. We do our best to make sure that information presented is accurate and fully up-to-date. However, the presentation may be subject to technical inaccuracies, information that is not up-to-date or typographical errors. As a consequence, Samsung does not in any way guarantee the accuracy or completeness of information provided on this presentation. Samsung reserves the right to make improvements, corrections and/or changes to this presentation at any time. The information in this presentation or accompanying oral statements may include forward-looking statements. These forward-looking statements include all matters that are not historical facts, statements regarding the Samsung Data System' intentions, beliefs or current expectations concerning, among other things, market prospects, growth, strategies, and the industry in which Samsung operates. By their nature, forward-looking statements involve risks and uncertainties, because they relate to events and depend on circumstances that may or may not occur in the future. Samsung cautions you that forward looking statements are not guarantees of future performance and that the actual developments of Samsung, the market, or industry in which Samsung operates may differ materially from those made or suggested by the forward-looking statements contained in this presentation or in the accompanying oral statements. In addition, even if the information contained herein or the oral statements are shown to be accurate, those developments may not be indicative developments in future periods. Logos remain the property of their respective owners. So there. 3
- 3. Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved This presentation is intended to provide information concerning Samsung’s efforts around containers and container orchestration. We do our best to make sure that information presented is accurate and fully up-to-date. However, the presentation may be subject to technical inaccuracies, information that is not up-to-date or typographical errors. As a consequence, Samsung does not in any way guarantee the accuracy or completeness of information provided on this presentation. Samsung reserves the right to make improvements, corrections and/or changes to this presentation at any time. The information in this presentation or accompanying oral statements may include forward-looking statements. These forward-looking statements include all matters that are not historical facts, statements regarding the Samsung Data System' intentions, beliefs or current expectations concerning, among other things, market prospects, growth, strategies, and the industry in which Samsung operates. By their nature, forward-looking statements involve risks and uncertainties, because they relate to events and depend on circumstances that may or may not occur in the future. Samsung cautions you that forward looking statements are not guarantees of future performance and that the actual developments of Samsung, the market, or industry in which Samsung operates may differ materially from those made or suggested by the forward-looking statements contained in this presentation or in the accompanying oral statements. In addition, even if the information contained herein or the oral statements are shown to be accurate, those developments may not be indicative developments in future periods. Logos remain the property of their respective owners. So there! 4
- 4. Classic IT usually starts here… Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 5
- 5. Containers Fueling Pace of Reinven4on “The New IT” Containers allow devs to build complex, distributed apps and services on their notebook, which can then run, unmodified, on public or private infrastructure • They provide isolation • They are highly efficient (low memory footprint, low startup time, rapid scale up/down – often 10X overall improvement) An entire ecosystem is rapidly building… • Operations automation • Lifecycle management • Homogenous, super-efficient datacenters
- 6. Containers Fueling Pace of Reinven4on “The New IT” Containers allow devs to build complex, distributed apps and services on their notebook, which can then run, unmodified, on public or private infrastructure • They provide isolation • They are highly efficient (low memory footprint, low startup time, rapid scale up/down – often 10X overall improvement) An entire ecosystem is rapidly building… • Operations automation • Lifecycle management • Homogenous, super-efficient datacenters
- 7. DisrupCve Effects on Classic IT • Low Entry Barrier • Serverless Startups • ShadowIT • Deprecates exis4ng technologies • Shared block storage (SANs) • Shared filesystems (NAS) • Legacy networking, e.g. h/w firewalls • Less Labor (Tinier Empire!!!) • Automated deployment, scaling, repair, teardown • Cheaper servers and network h/w • Strictly regimented, homogenous • CaQle, not pets. • Key technologies open sourced Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 8
- 13. What’s a Microservice??? • Not: 10-100 lines of code. Ack PhQQ! • Loosely coupled architecture • Pieces independently… – Upgradeable – Scalable – Developed • If you have to upgrade everything you are doing it wrong. • Mostly, single team (or even, dev) Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 14
- 14. Org Impacts • Microservices = Reorg • Devops = Reorg • High premium on product management • High premium on devops engineering, pipeline, and internal planorm Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 15
- 17. Here’s a future that sucks… • Deploy some Openstack • Deploy some VMware • Deploy some Mesos for Hadoop and Spark • Deploy some Cloud Foundry on Openstack • Deploy some Cloud Foundry on metal • Use AWS but get locked into their very nice services • Use some GCE • Deploy dedicated Unix/Windows/Linux • Throw swarm, kubernetes, GKE, and ECS into the mix for good measure. Run some on Mesos, some on Openstack. • Run some Mesos on Openstack for good measure. Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 18
- 18. More suck… • Build experCse on all of those systems… $$$, if you can even do it. • Pay lots for support since you have too many different distributed systems • Try to figure out how to log, alarm, debug all of that. • Try to figure out how secure all of that • Try to manage complexity by assigning each system it’s own dedicated cluster • Enjoy < 10% system uClizaCon • Have unsaCsfied customers due to reliability and performance issues. Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 19
- 19. • 70% Datacenter uClizaCon • MulCple releases a day / CD • 10,000-40,000 servers per admin • DestrucCve tesCng in producCon • No-ops (Self service deployment) • Go very fast and break nothing • Commodity hardware • Extremely low licensing spend (open source) • Comprehensive AutomaCon • Extensive AnalyCcs High Bar - Industrial Grade Compute #GIFEE
- 20. Yeah, we want that! Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 21
- 23. Open Source ContainerizaCon • Breaking vendor lock to expensive proprietary soluCons • More efficiency in data center uClizaCon • Easier path to commodity compute / white box infrastructure • Greater portability to and from public cloud systems • More agility in development and deployment • Rapid development and deployment • Deployment freedom/portability • Scaleup/Scale down • Lowest possible cost deployments (capex and opex)
- 24. Strategic Elements • The dedicated cluster is dead. • Collorary: We need large shared clusters. • Only one kind of turtle at the boQom – AWS Turtles or Google Turtles? – StandardizaCon – CommodiCzaCon – AutomaCon – Do one thing well, keep it as simple as possible • Need to support legacy applicaCon porCng and cloud naCve • Control: Open source, no lock-in Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 25
- 25. ExecuCon Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 26
- 26. Target Data Center Stack Bare Metal Container-opCmized host Container Mgr Container OpCmized Clustering and Resource AllocaCon PaaS apps Java/Scala Ruby Web Dev Non-PaaS Apps Back end processing Legacy Apps 3rd Party Public Cloud Bare Metal Container-opCmized host Container Mgr Public Cloud Bare Metal Container-opCmized host Container Mgr Public Cloud PaaS Cluster PaaS Cluster RelaConal DB Big Data DB AnalyCcs Cluster Big Data DB AnalyCcs Cluster Apps Apps Databases and Analy4cs Hadoop Non-SQL DB (Cassandra, Mongo, etc) SQL DB (MySQL, Postgress, etc) Container OpCmized Network
- 27. Target Data Center Stack Bare Metal Container-opCmized host Container Mgr Container OpCmized Clustering and Resource AllocaCon PaaS apps Java/Scala Ruby Web Dev Non-PaaS Apps Back end processing Legacy Apps 3rd Party Public Cloud Bare Metal Container-opCmized host Container Mgr Public Cloud Bare Metal Container-opCmized host Container Mgr Public Cloud PaaS Cluster PaaS Cluster RelaConal DB Big Data DB AnalyCcs Cluster Big Data DB AnalyCcs Cluster Apps Apps Databases and Analy4cs Hadoop Non-SQL DB (Cassandra, Mongo, etc) SQL DB (MySQL, Postgress, etc) Container OpCmized Network
- 28. Container OpCmized • Container OpCmized Hosts – Very small footprint – only what is needed to run containers – Very fast booCng – Very fast update – security requires up-to-date infrastructure – Examples: – CoreOS – Atomic (Redhat) – Snappy (Ubuntu) – RancherOS • Container OpCmized Network – Explosion of IP addresses: IP Address per container – IPV6 • Container OpCmized OrchestraCon – High rate of container start/stop – Higher density per server
- 29. “Opinionated” Cats Ahead… Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 30
- 30. Wrong Turtles at the BoQom Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 31 Openstack Kubernetes
- 31. Upside Down Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 32 Kubernetes Swarm
- 32. Much More Sensible Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 33 Swarm Kubernetes
- 33. Turtles Stacked Too Deep Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 34 Openstack Kubernetes Mesos Kubernetes is not a PaaS. Type I Kubernetes User: Wants to manage a single app Type II Kubernetes User: Wants to manage data centers
- 34. BeQer Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 35 Openstack Kubernetes Mesos
- 35. BeQer sCll… Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 36 Mesos Openstack Kubernetes
- 36. Where we are headed… Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 37 The VMs, too. In containers. Mesos Openstack Swarm Kubernetes PaaS
- 37. Strategic Conclusion Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 38 There Can Be Only One* * For each enterprise. IF you really want GIFEE.
- 38. OpCon: Openstack • MulCple support opCons – no support lockin. • Wrong type of turtle • Burdened by featuriCs – Collorary: Not keeping it simple • Lack of strong technical leadership • Known issues at scale • Too much religious fervor – Nobody expects the Pythonistas! • Have used this in produc6on, opinion is qualified. Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 39
- 39. OpCon: Mesos • A decent choice, proven track record at scale • Single vendor contributor ecosystem – Feels like lock-in to Mesosphere if you want commercial support – Confusing posiCon from Mesosphere vs DCOS • Complex and needing significant experCse to configure operate – …but beQer than openstack! • Good ecosystem around big data (Spark, Hadoop) • Roots in scienCfic compuCng, not modern service development…. – Container networking – Service discovery • Have not used this in produc6on. Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 40
- 40. OpCon: Swarm • Not really in the same category as these other systems, but Docker seems headed that way • Really a deployment tool, not a cluster management system • Not suitable for large scale • Single vendor dominated • Support for APCC, RKT, etc seems challenged. • Very small contributor base • Wouldn’t consider using this in produc6on at scale, so opinion is unlikely to change for a while. Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 41
- 41. Choice: Kubernetes • Good design by a vibrant, healthy community – MulC-contributor • Built from scratch for modern service develop/deploy – Pods are the right abstracCon • Rapid pace of improvement – Behind Mesos at point in Cme, but higher velocity – Our “Best Future” bet • MulC-vendor support opCons (no support lock-in) – SCll nascent. • Great contributors with the right experience • Best high scale public cloud container opCon – Google Container Engine • Supports mulCple container specs: Docker and APCC 42
- 42. Kubernetes Concerns • CNCF is the right direcCon, but slow ge|ng off the ground. • Featuri6s risk is ever present. • We are concerned and will con6nue to push as priori6es: – HA – Scaling – Reliability – OperaCons tooling • Accessibility for new users is criCcal to ecosystem health: – Quick start – DocumentaCon – UIs • Looking forward to more companies in the direct support ecosystem. 43
- 43. A Few Words About PaaS • We need to support mulCple PaaS frameworks. • We do not want to dedicate clusters to each PaaS system. – Cloud Foundry / Diego/ BOSH • PaaS workload needs to shared with other workloads • A PaaS should not be in the container scheduling business! Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 44
- 44. A Few More Words About PaaS • Cloud Foundry needs to rebase to Kubernetes (and Mesos) to live in this world. – Ditch BOSH – Ditch Diego – Focus on value up the stack rather than down. • Kudos to Deis, Apache Stratos, and OpenShig Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 45
- 46. Samsung Kubernetes Engagement • We are not forking • We are pushing back our work either into kubernetes or into our github repo – Samsung-AG. • 2016 – more work on networking and storage, with 1000 node clusters as the baseline Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 47
- 47. Why are we involved in K8Scale? • We want very large clusters with cross applicaCon resource sharing – Also looking forward to Ubernetes • We believe we can make a posiCve contribuCon to make this happen faster and beQer. • We believe we need deep technical involvement to build/deploy/operate at scale. • We learn by doing. Copyright © 2015 Samsung SDS Co., Ltd. All rights reserved 48