1 / 14

Running Micro Services on Arm-Based Microserver Architecture

Learn about the limitations and advantages of running micro services on ARM-based microserver architecture, including high density, low power consumption, and integrated Kubernetes features with Ceph.

weatherly
Download Presentation

Running Micro Services on Arm-Based Microserver Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Running Micro Services on Arm-Based Microserver Architecture OpenStack Summit Berlin 2018 November 13

  2. K8S Pods Density Limitation • No matter how powerful the CPU is, one server node can deploy 110 pods. • 110 pods/node is a hard limitation • Does all kind of micro service need such powerful server?

  3. Decentralized ARM MicroserverArchitecture 8x 1.2GHz ARM A72 QUAD Core Micro-servers - 4G Bytes DRAM - 8G Bytes Flash: System disk - 5 Gbps LAN - < 5 Watts power consumption Storage Device - 8x SATA3 HDD/SSD OSD - 8x SATA3 M.2 SSD Dual uplink switches - 4 x 10 Gbps

  4. Micro Server Architecture Advantages • High Density: 8 nodes x 100 pod= 800 Pods/1U • Low Power: 105 Watts • No NUMA issue: Dedicate CPU & memory

  5. Demonstration Deploy Kubernetes Nodes Deploy nginx server with 700 replicas and load balancing

  6. Use Apache Bench to test 10K connections with 20 concurrent connections

  7. Use Apache Bench to test 1M connections with 100 concurrent connection Check resource allocated

  8. Integrated with Ceph as Persistent Volume

  9. Use CephFS as back storage

  10. Deploy 100 Apache http server with CephFS as Persistent Volume Connections respond from different pods

  11. The Next – Container Converged • Integrated K8S features on Ambedded Ceph Management UI • Create standalone or multiple masters in HA mode • Collocate etcddatastore with masters • Create multiple HA etcd nodes • Add and remove Kubernetes nodes • Deploy SDN on masters and nodes • Auto Provision CEPH storage based on user request • Provide Role Based Access Control , LDAP & Active Directory • Provide ARM64 compatible Docker images for popular languages and database

More Related