Elastic Secure Infrastructure (ESI): I Learned to Share my Hardware; You Can Too!
summary
Builds a working hardware-leasing stack for the Mass Open Cloud: adds ironic node multi-tenancy by adding owner/lessee fields and policy rules, implements a simple leasing service called esi-leap that sets lessee fields and auto-cleans nodes, extends Neutron/ML2 with Cisco Nexus and trunk-on-NIC support, and ships simplified CLI commands like openstack esi node network list. Demoed end-to-end leasing, provisioning with MetalSmith, and switch verification; trial deployment at MOC is next, missing attestation and some iSCSI work.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:52Yes, But What Is ESI Doing? ESI is an enablement initiative that aims to fill the gaps in OpenStack in order to accomplish its stated goal. We
- 3:24Provisioning Workflow
- 3:52Partial Requirements Breakdown (2019) Service Requirement
- 5:34Ironic Node Multi-Tenancy • Update nodes to have owner and lessee fields • Expose owner/lessee fields to policy
- 7:24Networking Updates • Implemented support for Cisco Nexus switch with guidance from the networking-ansible team
- 8:13Simplified User Commands • Why? Because figuring out how networks are attached to a single node requires...
- 9:02Leasing Service • Started by looking at OpenStack Blazar, but...
- 10:08Hardware Leasing System Design, Revisited
- 18:58What's Next? • Trial Hardware Leasing System Implementation • Additional ESI Scenarios
related talks
01h 18mElastic Secure Infrastructure (ESI): Q&A and looking forward
35mPCEI at the EDGE
31mUsing European Open Source to build a Sovereign Multi-Cloud
04mLinux Event TV: CloudStack's Joe Brockmeier
06mIGNITE: Unleashing the Magic: Building SaaS Platforms
09mOSCON 2010: Marten Mickos
27mSupporting Security Sensitive Tenants in a Bare-Metal Cloud
17mLessons learned: scaling confidential clusters on OpenStack