FORUM: Edge Computing Groups MVP Architecture; StarlingX making it - PowerPoint PPT Presentation

FORUM: Edge Computing Group’s MVP Architecture; StarlingX making it real! James Penick, Verizon Greg Waines, StarlingX, Wind River Systems

OpenStack’s Edge Computing Group ▪ “Edge” has been a matter of opinion “Edge” Majority use General cases � Find the overlap which addresses infra needs the majority use cases

Define “Edge”

Reference Architectures #1 : Greater autonomy during partitions, with a higher operational cost. #2 : Lower operational cost, but no autoscale during network partition events.

Federated identity Federation at scale using an � identity provider (IdP) No syncing necessary �

Federated identity

Reference Architecture 1

Reference Architecture 1

Reference Architecture 1: Image distribution

Reference Architecture 2

Reference Architecture 2

Reference Architecture 2: Image distribution

OpenStack StarlingX StarlingX provides a deployment-ready, scalable, highly reliable Edge infrastructure software platform Services from the StarlingX virtualization platform focus on • Easy deployment • Low touch manageability • Rapid response to events • Fast recovery A complete Edge orchestration platform for Bare Metal, VM and Container workloads

OpenStack StarlingX: Distributed Cloud § Based on OpenStack Regions, Central Cloud § Central Central Region: Region – Hosting Shared Services and – System-wide Infrastructure Orchestration functions: § Deployment and Management of Subclouds, § Configuration portal for shared configuration across all Subclouds, Layer 3 Network § Fault aggregation, § Patching orchestration. § Remote Edge / Subcloud Regions: Edge / Subcloud – Geographically dispersed, Region Edge / Subcloud Region – Connected via L3 network, Edge / Subcloud – Running reduced Control Plane. Region § Inter-Region Communications strictly REST APIs / L3.

OS StarlingX: DC: Synchronizing Keystone -- API-based Synchronization -- -- DB-based Synchronization -- Client ( showing NOVA as example ) ( showing KEYSTONE as example ) 1 1 Add DB-based Synchronization support for OpenStack Services where API- DC Sync Framework OpenStack Keystone OpenStack Nova Nova Keystone synchronization is NOT sufficient. 2 2 API-PROXY API-PROXY KEYSTONE-API NOVA-API 4 NOVA-CONDUCTOR KEYSTONE DC Orchestration Engine Service Module in ’DC Orchestration Engine’ 4 NOVA-SCHEDULER synchronizes DB Records by Audit 3 3 Nova Keystone Directly querying/setting Services’ DB • 5 OE-Module OE-Module ( using SqlAlchemy DB Reflection ), and API Client DB Sync Client Using a new DC DB SYNC API which • Central Cloud exposes the DB operations remotely for NOVA API DC DB SYNC API – DB Table Record Post/Set/Delete synchronization purposes. 5 6 Edge Cloud OpenStack Keystone OpenStack Nova API Proxy triggers DB sync of affected row(s) DC Sync Framework of DB table(s), due to particular API request, KEYSTONE-API NOVA-API AGENT NOVA-CONDUCTOR KEYSTONE Generic Audit (default every 10 mins) deals with NOVA-SCHEDULER DB Sync API Server unexpected events/errors to ensure required 6 DB Table(s) are in-sync. 7 NOTE that this includes any non-API • triggered events that result in DB Table Changes.

OS StarlingX: DC: Glance Edge Caching Centralized Image Management for Usability with Distributed Image Caching for Image Download Performance § Glance == OpenStack Image Management Service § Glance supports sharing Storage Backend – è Edge Glances share Centralized CEPH Backend § Leverage StarlingX Synchronization Framework – To API/DB Synchronize Glance DBs – REQUIRED for “autonomous” behavior when network partitioning occurs. § Glance supports Image Caching for remote backends

OS StarlingX: DC: Identity Management DEMO OPTIONAL / TIME PERMITTING

OpenStack Edge Computing & StarlingX § OpenStack Edge Computing Group MVP Architecture – Centralized Control Plane Scenario – Distributed Control Plane Scenario – Initial Focus Areas § User / Identity Management – Federated and Synchronized Solutions § Image Management – Leveraging Multiple Shared Backends & Caching § StarlingX – Implementing the Distributed Control Plane Scenario § Adding Keystone and Glance to OpenStack Services synchronized by STX-DIST-CLOUD – Providing centralized management of identity and images, and – Still maintaining Edge Cloud functionality when isolated.

QUESTIONS ?