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

• pinion

Find the overlap which addresses the majority use cases

“Edge” Majority use cases General infra needs

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

§ Based on OpenStack Regions, § Central Central Region:

– Hosting Shared Services and – System-wide Infrastructure Orchestration functions:

§ Deployment and Management of Subclouds, § Configuration portal for shared configuration across all Subclouds, § Fault aggregation, § Patching orchestration.

§ Remote Edge / Subcloud Regions:

– Geographically dispersed, – Connected via L3 network, – Running reduced Control Plane.

§ Inter-Region Communications strictly REST APIs / L3.

OpenStack StarlingX: Distributed Cloud

Central Cloud Region

Edge / Subcloud Region Edge / Subcloud Region Edge / Subcloud Region

Layer 3 Network

OS StarlingX: DC: Synchronizing Keystone

Central Cloud Edge Cloud

Client

DC Orchestration Engine

Nova OE-Module Nova API-PROXY

OpenStack Nova

NOVA-API NOVA-CONDUCTOR NOVA-SCHEDULER

1 2 4 3 5

DC Sync Framework

Audit

( showing NOVA as example ) OpenStack Keystone

KEYSTONE-API KEYSTONE

3

Keystone OE-Module Keystone API-PROXY

1 2

NOVA API

4 5

OpenStack Keystone

KEYSTONE-API KEYSTONE

OpenStack Nova

NOVA-API NOVA-CONDUCTOR NOVA-SCHEDULER

6

Generic DB Sync API Server DC Sync Framework AGENT

6 7

DC DB SYNC API – DB Table Record Post/Set/Delete

• - DB-based Synchronization --
• - API-based Synchronization --

( showing KEYSTONE as example )

Add DB-based Synchronization support for OpenStack Services where API- synchronization is NOT sufficient. Service Module in ’DC Orchestration Engine’ synchronizes DB Records by

• Directly querying/setting Services’ DB

( using SqlAlchemy DB Reflection ), and

• Using a new DC DB SYNC API which

exposes the DB operations remotely for synchronization purposes. API Proxy triggers DB sync of affected row(s)

• f DB table(s), due to particular API request,

Audit (default every 10 mins) deals with unexpected events/errors to ensure required DB Table(s) are in-sync.

• NOTE that this includes any non-API

triggered events that result in DB Table Changes.

DB Sync Client API Client

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 ?