Uploaded byOutlyer
Murat Karslioglu, VP Solutions @ OpenEBS - Containerized storage for containers on OpenEBS
1) OpenEBS provides container-attached storage that aims to make storage for containerized applications as containerized as the applications themselves. 2) It does this by running storage services within Kubernetes as microservices, allowing each application pod to have its own dedicated storage with policies for data protection, availability and performance. 3) This approach aims to eliminate many of the concerns of traditional distributed storage systems while providing the benefits of DAS with increased utilization, mobility and cloud independence.
More Related Content
Similar to Murat Karslioglu, VP Solutions @ OpenEBS - Containerized storage for containers on OpenEBS
![Coded Agents – with UiPath SDK + LangGraph [Virtual Hands-on Workshop]](https://cdn.slidesharecdn.com/ss_thumbnails/codedagentsdeck-251215155422-5497c599-thumbnail.jpg?width=640&height=640&fit=bounds)
Murat Karslioglu, VP Solutions @ OpenEBS - Containerized storage for containers on OpenEBS
- 1. September 2017 @OpenEBS Murat Karslioglu- @muratkarslioglu Containerized Storage for Containers
- 2. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 2 Who? v Team of storage and DevOps engineers with a 5 year track record of delivering containerized storage (built on jails) to NTT, eSilicon, TCS and other service providers. CloudByte – our SDS brand. 2017 CloudByte Inc. All Rights Reserved
- 3. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 3 OpenEBS stars on GitHub (vanity) 2017 CloudByte Inc. All Rights Reserved
- 4. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 4 What if storage for container native applications was itself container native? 2017 CloudByte Inc. All Rights Reserved
- 5. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 5 Architecture: Kubernetes K8S Master Minion POD Container Container Container Kubele t POD Container Container Container Kubele t POD Container Container Container Kubele t Minion POD Container Container Container Kubele t POD Container Container Container Kubele t POD Container Container Container Kubele t Minion POD Container Container Container Kubele t POD Container Container Container Kubele t POD Container Container Container Kubele t etcd APIs Cntrl Schl d Minions run on physical nodes PODs group containers, share an IP address, and each include a Kubelet agent K8S Master services include: etcd, APIs, the scheduler, the control manager & others 2017 CloudByte Inc. All Rights Reserved
- 6. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 6 Architecture: Kubernetes + OpenEBS K8S Master Minion POD Container Container Container Kubele t POD Container Container Container Kubele t POD Container Container Container Kubele t Minion POD Container Container Container Kubele t POD Container Container Container Kubele t POD Container Container Container Kubele t Minion POD Container Container Container Kubele t POD Container Container Container Kubele t POD Container Container Container Kubele t etcd APIs Cntrl Schld OpenEBSAPIs Schld Data Containers run in PODs on physical machines Data Containers group physical disks local or remote, manage replicas, provide QoS control & more OpenEBS brain runs on the Master; delivers services such as: APIs, a storage scheduler, analytics… 2017 CloudByte Inc. All Rights Reserved
- 7. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 7 DAS increasingly preferred to NAS/SAN DAS Benefits: Simple Ties application to storage Predictable for capacity planning App deals with resiliency Can be faster Concerns: Under-utilized hardware ○ 10% or less utilization Wastes data center Difficult to manage Lacks storage features Cannot be repurposed - made for one workload Does not support mobility of workloads via containers Cross cloud impossible “We have ~100k nodes of Cassandra alone, and use DAS because it is easier even if it burns energy and capEx.” Other example DAS users moving to Kubernetes: 2017 CloudByte Inc. All Rights Reserved
- 8. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 8 DAS increasingly preferred to NAS/SAN DAS Benefits: Simple Ties application to storage Predictable for capacity planning App deals with resiliency Can be faster Concerns: Under-utilized hardware ○ 10% or less utilization Wastes data center Difficult to manage Lacks storage features Cannot be repurposed - made for one workload Does not support mobility of workloads via containers Cross cloud impossible Other example DAS users moving to Kubernetes: “We have ~100k nodes of Cassandra alone, and use DAS because it is easier even if it burns energy and capEx.” 2017 CloudByte Inc. All Rights Reserved
- 9. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 9 DAS and Distributed DAS Benefits: Simple Ties application to storage Predictable for capacity planning App deals with resiliency Can be faster Concerns: Under-utilized hardware ○ 10% or less utilization Wastes data center Difficult to manage Lacks storage features Cannot be repurposed - made for one workload Does not support mobility of workloads via containers Cross cloud impossible Distributed Benefits: Centralized management Greater density and efficiency Storage features such as: ○ Data protection ○ Snapshots for versioning Concerns: Additional complexity Enormous blast radius Expensive Requires storage engineering Challenged by container dynamism No per microservice storage policy I/O blender impairs performance Locks customers into vendor Cross cloud impossible 2017 CloudByte Inc. All Rights Reserved
- 10. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 10 DAS and Distributed DAS Benefits: Simple Ties application to storage Predictable for capacity planning App deals with resiliency Can be faster Concerns: Under-utilized hardware ○ 10% or less utilization Wastes data center Difficult to manage Lacks storage features Cannot be repurposed - made for one workload Does not support mobility of workloads via containers Cross cloud impossible Distributed Benefits: Centralized management Greater density and efficiency Storage features such as: ○ Data protection ○ Snapshots for versioning Concerns: Additional complexity Enormous blast radius Expensive Requires storage engineering Challenged by container dynamism No per microservice storage policy I/O blender impairs performance Locks customers into vendor Cross cloud impossible 2017 CloudByte Inc. All Rights Reserved
- 11. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 11 DAS Under-utilized hardware Hard to manage Lacks all storage features Hard to support workload mobility 2017 CloudByte Inc. All Rights Reserved
- 12. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 12 YASSS: yet another scale out storage system 2017 CloudByte Inc. All Rights Reserved
- 13. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 13 YASSS: yet another scale out storage system Huge blast radius2017 CloudByte Inc. All Rights Reserved
- 14. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 14 !YASSS Yet Another Scale Out Storage System 2017 CloudByte Inc. All Rights Reserved
- 15. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 15 !YASSS Yet Another Scale Out Storage System 2017 CloudByte Inc. All Rights Reserved
- 16. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 16 Container Attached Storage = DAS++ DAS Benefits: Simple Ties application to storage Predictable for capacity planning App deals with resiliency Can be faster Concerns: Under-utilized hardware ○ 10% or less utilization Wastes data center Difficult to manage Lacks storage features Cannot be repurposed - made for one workload Does not support mobility of workloads via containers Cross cloud impossible OpenEBS = “CAS” ✓ Simple ✓ No new skills required ✓ Per microservice storage policy ✓ Data protection & snapshots ✓ Reduces cloud vendor lock-in ✓ Eliminates storage vendor lock-in ✓ Highest possible efficiency ✓ Large & growing OSS community ✓ Natively cross cloud Distributed Benefits: Centralized management Greater density and efficiency Storage features such as: ○ Data protection ○ Snapshots for versioning Concerns: Additional complexity Enormous blast radius Expensive Requires storage engineering Challenged by container dynamism No per microservice storage policy I/O blender impairs performance Locks customers into vendor Cross cloud impossible 2017 CloudByte Inc. All Rights Reserved CAS DAS Distributed
- 17. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 17 Container Attached Storage No special skills needed!2017 CloudByte Inc. All Rights Reserved
- 18. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 18 Why per micro-service granularity important? Today’s scale out storage systems are almost infinitely configurable. Matching their configurations to static workloads is difficult. In a world of dynamic, ever evolving workloads due to micro-services and multi-cloud deployments, it is not a tractable problem for humans. Let’s say you want to benchmark for your workload: Source: Alex Aizman’s blog: https://storagetarget.com/author/alexaizman/ 2017 CloudByte Inc. All Rights Reserved
- 19. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 19 Today’s scale out storage systems are almost infinitely configurable. Matching their configurations to static workloads is difficult. In a world of dynamic, ever evolving workloads due to micro services and multi-cloud deployments, it is not a tractable problem for humans. Let’s say you want to benchmark for your workload: Duration of run 6,700 years Source: Alex Aizman’s blog: https://storaget arget.com/auth or/alexaizman/ Why per micro-service granularity important? 2017 CloudByte Inc. All Rights Reserved
- 20. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 20 Normal behavior POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet Data Center 1 Maya POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet Data Center 2 POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet EBS AWS EBS EBS EBS POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet GPD GCE GPD GPD GPD 1. CI/CD pipeline deploys: 2. OpenEBS reads intent FROM K8S For example: - 2 sync copies - 50 / 50 cloud - 2 Data centers 2017 CloudByte Inc. All Rights Reserved
- 21. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 21 Normal behavior POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet Data Center 1 Maya POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet Data Center 2 POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet EBS AWS EBS EBS EBS 1. CI/CD pipeline deploys: 2. OpenEBS reads intent FROM K8S For example: - 2 sync copies - 50 / 50 cloud - 2 Data centers POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet GPD GCE GPD GPD GPD 2017 CloudByte Inc. All Rights Reserved
- 22. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 22 Normal behavior POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet Data Center 1 Maya POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet Data Center 2 POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet EBS AWS EBS EBS EBS 1. CI/CD pipeline deploys: 2. OpenEBS reads intent FROM K8S For example: - 2 sync copies - 50 / 50 cloud - 2 Data centers 3. writes STORED locally: - working set in NVM - rebalancing in background POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet GPD GCE GPD GPD GPD 2017 CloudByte Inc. All Rights Reserved
- 23. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 23 2017 CloudByte Inc. All Rights Reserved Normal behavior: differentiation POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet Data Center 1 Maya POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet Data Center 2 POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet EBS AWS EBS EBS EBS 1. Transparency: - works across clouds, & CAS, seamlessly 2. FAST: - Much faster than DAS or network attached - Could be 100 or even 1000x faster POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet GPD GCE GPD GPD GPD
- 24. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 24 2017 CloudByte Inc. All Rights Reserved Normal behavior: differentiation POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet Data Center 1 Maya POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet Data Center 2 POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet EBS AWS EBS EBS EBS 1. Transparency: - works across clouds, & CAS, seamlessly 2. FAST: - Much faster than DAS or network attached - Could be 100 or even 1000x faster 3. Happier Cassandra: - When Cassandra nodes fail, rebalancing, which degrades performance, typically NOT needed POD Container Container ContainerKubelet POD Container Container ContainerKubelet POD Container Container ContainerKubelet GPD GCE GPD GPD GPD 4. Happier CFO: - Far greater utilization - No more cloud lock-in
- 25. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 25 Storage Orchestration - K8s Vs OpenEBS Functionality K8s OpenEBS Volume Life-cycle - provisioning, attaching/detach, de- provisioning ✓ Monitoring the volume data ✓ Scheduling the volume provisioning intelligently ✓ Smart space management ✓ Availability of volume ✓ Application aware backup/snapshots ✓ QoS guarantee (latency guarantee) ✓ Smart movement of the volumes across racks and regions ✓ Cataloging of storage requirements for different applications ✓ 2017 CloudByte Inc. All Rights Reserved
- 26. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 26 Storage just fades away as a concern 2017 CloudByte Inc. All Rights Reserved
- 27. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 27 Benefits of Cloud Native approach OpenEBS always available multi-cloud block services are delivered via containerized microservices Granularity: Each pod has its own block protocol stack, tiering engine, QoS engine and more. SLAs per POD. Performance & efficiency: access patterns maintained per-volume. Hot-data on NVMe-Flash or on 3DX-Memory. Cold- data on slower disks / SAN/ Cloud-Storage/S3. Scalability: Metadata based on “size of the volume” & not on “number of volumes”. Can reduce metadata traversal 100x. Blast radius: Eliminates risk of scale out storage system corruption. And much, much more such as cost savings due to resource efficiency, innate multitenancy, and cross cloud portability The Conway’s Law benefits might be the most important - innovation unlocked ✓ ✓ ✓ ✓ 2017 CloudByte Inc. All Rights Reserved
- 28. 2017 Storage DeveloperConference. © CloudByte Inc.. All Rights Reserved. 28 Q&A Please tell us we are crazy. Find out HOW it works! Meet some folks who want storage to be fixed once and for all. Slack.openebs.io blog.openebs.io Github.com/openEBS @openebs Me: @muratkarslioglu 2017 CloudByte Inc. All Rights Reserved
Editor's Notes
- #2 Going to cover current trends and introduce you to OpenEBS. Also going to specifically talk about an example of a normal behavior of storage and how we might want ”storage” to behave.
- #8 As they say - just sit with that for a while.
- #9 Mention Randy and blast radius here.
- #10 Existential dread. If this does not fill u with dread - it should.
- #12 But – being built into Kubernetes. It is happening! Go through each of the YASSS points - maybe mention the Mule. More importantly - you are doing distributed at the application layer - how distributed do you need the storage to really be?
- #13 But – being built into Kubernetes. It is happening! Talk specifically about latency claims. With numbers.
- #14 But – being built into Kubernetes. It is happening!
- #16 It’s like applications changed completely – and someone forgot to tell storage.
- #17 Summarize into three for us DRaaS a frequent use case.
- #18 But – being built into Kubernetes. It is happening!
- #19 It is also possible to have a couple of different storage policies and to see which is performing better and to have this kind of blue / green happening at the storage level, all the time, behind the scenes.
- #25 Be more specific - on utilization