Cloud Infrastructure Reference Model Elbrus and beyond October

Cloud Infrastructure Reference Model Elbrus and beyond October 2020

Agenda › Current state of RM Baraque release and GSMA release › Gaps and next RM focus areas › Accelerators › HW, NW & Cloud Infrastructure Management › Evolution towards multi/hybrid cloud model (including Edge) › Questions? New topic proposals? Etherpad: https: //etherpad. opnfv. org/p/RM_Elbrus_and_ beyond_2020 -10 -13 2

Current state of RM Baraque release and GSMA release 3

Introduction – role of Reference Model (RM) › RM provides technology agnostic directions for the CNTT Cloud Infrastructure specifications in Reference Architectures (RAs), and consequently in RIs and RCs › RM provides technology agnostic CNTT requirements for VNF/CNF vendors to guide them in their design of network applications › CNTT Reference Model is released as GSM PRD (Permanent Reference Documentation), and as such RM is a window into the CNTT work for a wider telco community

CNTT Reference Model overall diagram VNFs/CNFs Management clients Consume virtual resources Virtual Infrastructure Layer Hardware Infrastructure Layer Manage resources Virtual infrastructure manager Hardware resources Hardware infrastructure manager Cloud Infrastructure The Linux Foundation Internal Use Only 9/24/2020 5

CNTT Reference Model evolved! VNFs/CNFs Management clients Consume virtual resources Virtual Infrastructure Layer Hardware Infrastructure Layer Manage resources Virtual infrastructure manager Hardware resources Hardware infrastructure manager Baraque RM: New component Cloud Infrastructure The Linux Foundation Internal Use Only 9/24/2020 6

CNTT Reference Model realization diagram Baraque RM New component The Linux Foundation Internal Use Only 9/24/2020 7

Gaps and next RM focus areas 8

Topics requiring further study / gaps › Acceleration abstraction: Currently listed as profile extensions and generic principles. RM needs to provide a clear a simple model allowing abstracting acceleration but implementable using current and future technologies › Elaborate Model for HW, NW & Cloud Infrastructure Management, define functionality and interfaces › Evolution towards multi/hybrid cloud model: Model Enterprise Clouds as a Multi-Cloud Environment, interconnecting everything with vendors and users, for intelligent operability 9

Acceleration Intro Example of HW Acc. Abstraction options in usual server nodes In RM realization diagram Bottoms-up view on options (that need modeling)

Intro › RM: › Currently listed as profile extensions and generic principles › High priority for next release › Desired outcomes: simple clear model, Decoupled from VNF/CNF or tradeoffs understood and gaps identified › Start with Hardware Acceleration Abstraction

Example of HW Acc. Abstraction options in usual server nodes Application Level Acceleration: Controller • Node app 1 app 2 guest VM v. Switch… lib container bare metal SR-IOV VMM app 3 host OS Server Smart. NIC Above is an example for illustration, not exhaustive list of all possible options. Infrastructure Level Acceleration: • Acc SW library/framework (like DPDK) in VM provides Application level acceleration with (where available) HW-abstracted APIs to access platform HW Acceleration and also provides SW equivalent libraries when HW assist not available Smart. NICs provide Infrastructure acceleration (e. g. v. Switch, IPSec, Tunnel End Point termination) which can be leveraged agnostically by VNFs through the use of accelerated standard host interfaces (e. g. Virtio)

In CNTT Reference Model realization diagram VNF CNFs s Consume virtual resources Virtual Resources Containers Exposing it to Cloud Infra or App tenant Virtual svc Infrastructure Acc. Layer Inband VM VM Hypervisor mgr. Hardware Infrastructur e Layer Container Infrastructure VM Service Instance VM Comput Hardware Resources Network Acc. e Resourc HW es For tech. requirements or economic reasons es Resources Management clients CNFs Consume virtual resources Container Infrastructure Devic. Service Instance e Plugin Bare Metal Manage HW resources Container Infrastructure SDN 1 Service Manager Virtual Infrastructure Cybor Manager g SDN 2 svc Acc. HW Infrastructure mgr. SDN 3 Manager Storage Resourc es Cloud Infrastructure Manage virtual resources OOB Management software

Bottoms-up view on options (that need modeling) Acc. technology/HW Example implementation Activation/LCM/ support Comment (New) CPU instructions SW lib recognize and use none for HW all SW so easiest Fixed function accelerator crypto, GPU, v. RANspecific adapter rare updates mostly for NF acc. Network adapter Firmware image rare updates in multivendor environment Smart. NIC programmable acc. for v. Switch/v. Router and/or NF programmable by Infra operator and/or NF tenant tech gaps Smart. Switch-based Programmable node/TOR programmable by Infra operator and/or NF tenant … The Linux Foundation Internal Use Only 6/3/2021 14

HW, NW & Cloud Infrastructure Management 15

CNTT RM Logical Architecture - Baraque Management and Orchestration Or-Vnfm CNF Container. RT +Secondary. NW Virtual Infrastructure Layer Vn-Nf Container Infrastructure Service Instance (Caa. S on Bare Metal) Container Infrastructure Service Instance VM Container Management VM Virtual Machine Manager (Iaa. S Hypervisor) Nf-Vi Vl-Ha HW Resource Pool with Abstraction Model Compute Resource 1 Vi-Vnfm (Caa. S on Iaa. S) Vn-Nf Vl-Ha Hardware Infrastructure Layer VNF Manager VNF Compute Resource m Storage Resource Network Resource HW Infrastructure Management Orchestrator(s) Virtual Infrastructure Management HW Equipment Management OSS/BSS Container SDNo Infrastructure Service Manager Virtual SDNo SDNu Infrastructure Manager HW Status/ Provisioning/Fulfillment HW Resource Management HW Infrastructure Manager SDNu Cloud Infrastructure CNTT reference point Non-CNTT reference point ETSI NFV reference point

CNTT RM – RAs task to align these areas - Add RM Requirement for RAs Management and Orchestration OSS/BSS CNF Container. RT +Secondary. NW Vn-Nf Container Infrastructure Service Instance (Caa. S on Bare Metal) VNF Manager VNF Container SDNo Infrastructure Service Manager Container Management (Caa. S on Iaa. S) Virtual Machine Manager Nf-Vi Vl-Ha Virtual SDNo Infrastructure Manager Compute Resource m Storage Resource › SDNu HW Status/ Provisioning/Fulfillment HW Resource Pool with Abstraction Model Compute Resource 1 › Multiple NW › Separation › Treatment Multi-Tenancy Accelerators What more? ? ? Vn-Nf (Iaa. S Hypervisor) Hardware Infrastructure Layer Add requirements for RAs › › › Vi-Vnfm VM Container Infrastructure Service Instance VM HW Infrastructure Management HW Equipment Management CNF Virtual Infrastructure Management Orchestrator(s) Or-Vnfm Virtual Infrastructure Layer › Network Resource HW Resource Management HW Infrastructure Manager SDNu Cloud Infrastructure CNTT reference point Non-CNTT reference point ETSI NFV reference point Models, Interfaces, APIs › › › CNF – CISI CISM – CISI SDNctrl – CISM

CNTT RM – HW Infrastructure NBI definition Define HW Infrastructure Management North Bound (NBI) Management and Orchestration OSS/BSS Container. RT +Secondary. NW Vn-Nf Container Infrastructure Service Instance (Caa. S on Bare Metal) VNF Manager VNF Vi-Vnfm VM Container Infrastructure Service Instance Vn-Nf Virtual Machine Manager Nf-Vi (Iaa. S Hypervisor) Vl-Ha Hardware Infrastructure Layer Virtual SDNo Infrastructure Manager Compute Resource 1 Compute Resource m Storage Resource SDNu HW Status/ Provisioning/Fulfillment HW Resource Pool with Abstraction Model Network Resource HW Resource Management HW Infrastructure Manager SDNu Cloud Infrastructure CNTT reference point Non-CNTT reference point › › › Container SDNo Infrastructure Service Manager Container Management (Caa. S on Iaa. S) VM HW Infrastructure Management CNF Virtual Infrastructure Management HW Equipment Management CNF Functionality System › Fault Management › FW & SW Upgrades › Security › Composability › Networking › Compute › Acceleration › Storage Orchestrator(s) Or-Vnfm Virtual Infrastructure Layer › ETSI NFV reference point › State, Topologies & Telemetry Services › › › L 3 aa. S LBaa. S FWaa. S Models, Interfaces, APIs › › › SDO › Host OS VIM CISM Cloud Infrastructure Management Redfish

CNTT RM – HW Infrastructure SBI definition Define HW Infrastructure Management South Bound (SBI) Management and Orchestration OSS/BSS Vn-Nf Container Infrastructure Service Instance (Caa. S on Bare Metal) VNF Manager VNF Vi-Vnfm › Models, Interfaces VM Container Infrastructure Service Instance Container SDNo Infrastructure Service Manager Container Management (Caa. S on Iaa. S) VM Nf-Vi (Iaa. S Hypervisor) Vl-Ha Virtual SDNo Infrastructure Manager --- Resource Block Equipment Pool --Accelerator Resource Storage Fabric Manager & Equipment Switch Fabric Manager & Equipment SDNu Resource Management Equipment Management HW Infrastructure Manager › › HW Equipment (Redfish preferred) Resource Management › Smart. NIC Management CNTT reference point Non-CNTT reference point ETSI NFV reference point › › SDO › Liaison SDNu Cloud Infrastructure Events Discovery Configuration/Intents State, Topologies & Telemetry Security › HW Status/ Provisioning/Fulfillment Composed System Infrastructure Components Comput e Resourc e › › › Vn-Nf Virtual Machine Manager Storage Drive Resourc e HW Infrastructure Management CNF Virtual Infrastructure Management HW Equipment Management CNF Container. RT +Secondary. NW Hardware Infrastructure Layer Functionality Orchestrator(s) Or-Vnfm Virtual Infrastructure Layer › › › Switch Fabric Management Storage Fabric Redfish Open. Config OVN ODIM

CNTT RM – Abstract HW Host i/f definition › Management and Orchestration OSS/BSS Vn-Nf Container Infrastructure Service Instance (Caa. S on Bare Metal) VNF Manager VNF Vi-Vnfm Container SDNo Infrastructure Service Manager Container Management (Caa. S on Iaa. S) Abstract ID › › Telemetry Events Nf-Vi (Iaa. S Hypervisor) Vl-Ha Virtual SDNo Infrastructure Manager HW Status/ Provisioning/Fulfillment Composed System Infrastructure Components --- Resource Block Equipment Pool --Accelerator Resource Storage Drive Resourc e Storage Fabric Manager & Equipment Switch Fabric Manager & Equipment SDNu HW Resource Management HW Infrastructure Manager SDNu Cloud Infrastructure CNTT reference point Non-CNTT reference point ETSI NFV reference point › › › Server Host Block/Volume Accelerator NW Models, Interfaces › › Vn-Nf Virtual Machine Manager Comput e Resourc e › VM Container Infrastructure Service Instance VM HW Infrastructure Management CNF Virtual Infrastructure Management HW Equipment Management CNF Container. RT +Secondary. NW Hardware Infrastructure Layer › Orchestrator(s) Or-Vnfm Virtual Infrastructure Layer Functionality › › Security › TPM/TXT › Deprecate SR-IOV High Performance Abstract NIC i/f Application Smart. NIC Management NVMe SDO / Open Source › › › Linux ETSI Redfish

CNTT RM – Cloud Infrastructure Manager definition › Management and Orchestration OSS/BSS HW Equipment Management Or-Vnfm CNF Container. RT +Secondary. NW Vn-Nf Container Infrastructure Service Instance Virtual Infrastructure Layer (Caa. S on Bare Metal) VNF Manager VNF VM Container Infrastructure Service Instance VM Container Management Virtual Machine Manager Nf-Vi Virtual Infrastructure Manager Comput e Resourc e Accelerator Resource Storage Fabric Manager & Equipment Switch Fabric Manager & Equipment VIM/CISM Deployer Status, Topologies & Telemetry External NW connectivity › › › Cloud policy control SDSaa. S L 3 aa. S LBaa. S FWaa. S Reference Points, Models, Interfaces › › › › SDO / Open Source › › VIM CISM Resource Management Equipment Management HW Infrastructure Manager SDNu O-RAN O 2 ONAP Redfish CNCF Cloud Infrastructure ONS CNTT reference point Cloud Infra optimizations Services VNFMs SDN o HW Status/ Provisioning/Fulfillment Composed System Infrastructure Components Storage Drive Resourc e HW v. POD Deployer HW Infrastructure Management Vl-Ha --- Resource Block Equipment Pool --- SDNu › › › › Service Orchestrators Container SDNo Infrastructure Service Manager Vn-Nf Vl-Ha Cloud Infrastructure Manager Cluster Manager (Caa. S on Iaa. S) (Iaa. S Hypervisor) Hardware Infrastructure Layer Vi-Vnfm Cloud Infra & Policy Management Cloud Deployment Management Orchestrator(s) Functionality Non-CNTT reference point ETSI NFV reference point

Evolution towards multi/hybrid cloud model (including Edge) 22

Evolution towards hybrid multi-cloud model Potential Topic Areas › Enterprise Cloud Environment as a Hybrid Multi-Cloud Environment › Enterprise Enablement: Interconnecting everything for intelligent operability › Extended Enterprise: Granular interconnecting with vendors and users › What does an Enterprise Cloud look like › Others? * Enterprise Cloud Environment includes Corporate Cloud (IT and Network) and external Customers

Enterprise Cloud (EC): Use Scenario › › › › Multiple interconnected Private, Public and Hybrid Clouds Multiple Technology support (e. g. , Open. Stack, Kubernetes) Near “Unlimited” Capacity Locality: Local capacity but Services may differ Scaling: within a Cloud and Burst across Clouds Specialised Capabilities: Custom services offered by a specific cloud (for example, Smart. NIC offloads) Colocation of multiple clouds at an EC location Cloud A Private – Own On Prem Region Cloud B Private – Cloud Vendor* On Prem Zone * Cloud Vendor: Commercial Cloud Provider, Cloud Tech Vendor (VMware, Ericsson, Nokia, etc. ) Cloud C Private – Commercial Cloud Provider (AWS, Azure, . . ) Availability Zone (AZ) Cloud D Public Cloud Provider

Enterprise Cloud: Independent Clouds Model Cloud A › › › Cloud B Workload components deployable on multiple Clouds Workload components deployed on most appropriate cloud › Use of that Cloud’s specific services Mix and match services from different Clouds › For example, CDN service from Cloud A and customer service application on Cloud B 25

Enterprise Cloud: Shared Resources Model › › HW Infrastructure Layer Resource Pool Supports multiple Iaa. S and Caa. S Virtualization Instances where an Instance may span multiple Clouds 26

Enterprise Cloud: Requirements › Nature of interconnectivity › Cloud Agnostic Standardised Services or a common Paa. S › › › › At Cloud (required), Zone, Region, AZ Cloud Independent APIs (NB) Cluster APIs › › consistently provision machines, load balancers, etc. , across any infrastructure provider and any location automate cluster lifecycle management Are kubernetes and microservices based sw enough Cloud Agnostic Broker Cloud Agnostic OAM Support for NFaa. S/NSaa. S across clouds, locations, etc. What else needs to be covered?

Example: Commercial Cloud Svc located in CSP Edge Location › Applications can be deployed to multiple Wavelength Zones across different CSPs › Seamlessly connect to the full range of cloud services › Simplifies the operations and management processes and enabling large scale deployments. 28

Questions? Other topic proposals? We need your feedback and contributions! 29

30