OpenIO Summit'17 - ARM, Object Storage and more
•
0 gefällt mir•247 views
1) The document discusses the OpenIO Summit '17 which covered topics including ARM hardware, object storage deployment frameworks and APIs, and demonstrations. 2) It describes OpenIO SDS technology as having a very lightweight software stack that is easy to scale across nodes without rebalancing and features load balancing for optimal data placement. 3) ARM boards are presented as a good hardware option for OpenIO SDS due to their low cost, power consumption, and heat, with the potential benefit of one board per disk for failure domain isolation and cost-effective scaling. 4) The OVH IAAS API is highlighted for its ability to deploy OpenIO SDS clusters on ARM nodes through automated builds, installations, and aggregation using REST APIs.
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie OpenIO Summit'17 - ARM, Object Storage and more
Ähnlich wie OpenIO Summit'17 - ARM, Object Storage and more (20)
Mehr von OpenIO Object Storage
Mehr von OpenIO Object Storage (13)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
OpenIO Summit'17 - ARM, Object Storage and more
- 1. OpenIO Summit ‘17 ARM, Object Storage and More
- 2. OpenIO Summit’17 Topics 1 2 3 Genesis Hardware review Deployment frameworks and APIs 4 Demo
- 3. OpenIO Summit’17 Very lite software stack • Written in C • 1 core • 2GB ram Grid of nodes with no consistent hashtable Easy to scale Never rebalance Conscience technology Real time load balancing for optimal data placement Very few communication between nodes When a node is working others are free We think different OpenIO SDS technology
- 4. OpenIO Summit ‘17 Hardware limitation • 1 node ~1PB • Scalability at the enclosure level Lets find a hardware that fits OpenIO SDS flexibility
- 5. OpenIO Summit ‘17 Why ARM is great? • Cheap • Low power consumption • Low heat • Enough resources One board per disk
- 6. OpenIO Summit ‘17 One board per disk benefits • Failure domain • Scaling at the disk level • Cost effective We need a flexible method to provide and install the servers… Here comes OVH’s IAAS API
- 7. OpenIO Summit’17 • Large range of OS (~130) • Automatic build factory • Large scale infrastructure to deploy OS • ~ 500 builds or rebuilds per day • User defined Installation Backend - key facts
- 8. OpenIO Summit’17 How it works OpenIO SDS deployment on OVH’s ARM nodes Install process OVH Rest API OpenIO SDS cluster HW OS HW OS HW OS Deploy OpenIO SDS Build Aggregate
- 9. OpenIO Summit’17 HDAAS - Architecture • 1 switch module • 24 hard drive modules Hardware
- 10. OpenIO Summit’17 HDAAS - Module • Dual core Cortex A9 ARMv7 CPU • Up to 1 GHz per core • 2 GB DDR3 • 2 x GbE ports SGMII / RGMII Hardware
- 11. OpenIO Summit’17 HDAAS - Module - NIC Speed • Up to 2.5 Gb/s • Misleading info from ethtool Hardware
- 12. OpenIO Summit’17 HDAAS - Module - NIC Speed • Iperf Hardware
- 13. OpenIO Summit’17 OVH API - Install main steps • Boots on rescue (live system) • Build partitioning layout and mount it • Copy image and layout • Make it bootable • Reboot on system • Customize system Deployment framework and API
- 14. OpenIO Summit’17 OVH API - Tools • Rescue = live, adapted for ARMv7 • Base images • Scripts to drive tftp config Deployment framework and API
- 15. OpenIO Summit’17 OVH API - Tools • First images: cross compiling from an x86 build machine • Problems on more advanced packages • Advanced images directly built on final target using deboostrap Build rescue and images
- 16. OpenIO Summit’17 OVH API - Tools • From network (using uboot > pxe > syslinux) • Main drawback: users are not independent on us regarding the kernel upgrades Boot on local drive v1
- 17. OpenIO Summit’17 OVH API - Tools • Entirely from local disk • uBoot still boots on network first (so as to keep rescue available) • syslinux chains back on local disk • With U-boot-tools: we persist a localcmd in uboot firmware direcly from rescue • Limitations: uboots only knows how to boot from ext* filesystems Boot on local drive v2
- 18. OpenIO Summit’17 Using the API for our use case
- 19. OpenIO Summit’17 1. Create a template
- 20. OpenIO Summit’17 2. Add a scheme partition
- 21. OpenIO Summit’17 3. List of schemes available for a template
- 22. OpenIO Summit’17 4. Add a partition in a partitioning scheme
- 23. OpenIO Summit’17 4. Add a partition in a partitioning scheme
- 24. OpenIO Summit’17 5. List of partitions defined
- 25. OpenIO Summit’17 6. Customized template
- 26. OpenIO Summit’17 7. Launch install
- 27. OpenIO Summit’17 8. Monitoring a bunch of installs I
- 28. OpenIO Summit’17 What can you expect from Grid for Apps in the near future? Questions? OpenIO