CNTT ODIM Collaboration October 2020 Agenda CNTT RM

CNTT – ODIM Collaboration October 2020

Agenda › CNTT RM Baraque Release › Current State of ODIM Specification › CNTT Alignment Points › Collaboration Discussion › Call to Action(Tomas) Etherpad: EEEE 2

Current RM Baraque 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 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 The Linux Foundation Internal Use Only 9/24/2020 7

ODIM Overview 8

The Emergence Of Edge Computing And 5 G 1 Increasing numbers of distributed data centers as workloads move to the Edge 2 Workload and commercial demands can vary massively per location 3 Proliferation of infrastructure management APIs 9

Lack of Physical Infrastructure Management Consistency Upstream COTS/OSS service/resource MANO stacks Physical Infrastructure Management Physical Infrastructure Resources › Too many integration points, rigid, brittle architectures 10 The Linux Foundation Internal Use Only 6/25/2020 10

ODIM Intends to simplify and scale open infrastructure management Upstream COTS/OSS service/resource MANO stacks ODIM Presents consistent on/off-premises HWaa. S interfaces for Physical Infrastructure management Physical Infrastructure Resources › Reduce the number of disparate, reinvented shims, adaptors and plug-ins 11 The Linux Foundation Internal Use Only 6/25/2020 11

Key Use Cases • Multi-site, multi-vendor physical infrastructure management • Remote distributed management across multiple deployment locations • Vendor-neutral discovery, exposure/visibility and control of infrastructure resources and their capabilities • Closed loop physical infrastructure management (OODA, MAPI, etc…) Provision Monitor • Discover • Search • Reserve • Edit • Remove • Health • Performance Manage • Lifecycle management • Power management • Batch Operations Infrastructure Lifecycle Use Cases The Linux Foundation Internal Use Only 6/25/2020 12

ODIM: DMTF Redfish® compliant functions and interfaces Upstream Clients/Users Operating Systems Cluster Frameworks Resource Managers Service Managers COTS/OSS MANO Offerings Integration Interface Adapters ODIM Presents consistent on/off-premises HWaa. S interfaces for Physical Infrastructure management DMTF Redfish® Interfaces DMTF Redfish® Data Model Account Event Aggregation Session Composition … DMTF Redfish® Based Services ODIM Resource Abstraction Layer Resource API Adapters Native Physical Resource/Device Interfaces IPMI The Linux Foundation Internal Use Only Redfish Open. Config Proprietary DMTF Redfish® APIs … Native Interfaces 6/25/2020 13

ODIM community consumers and contributors Upstream COTS/OSS service/resource MANO stacks Functional Consumers and Contributors Alignment and Influence Physical Infrastructure Resources 14 The Linux Foundation Internal Use Only 6/25/2020 14

CNTT and ODIM Alignment Points / Collaboration Discussion 15

CNTT Reference Model Logical Architecture 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

Potential alignment of CNTT with ODIM Current discussion on alignment areas between CNTT and ODIM projects 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 Compute Resource m Storage Resource Container SDNo Infrastructure Service Manager Virtual SDNo SDNu Infrastructure Manager HW Status/ Provisioning/Fulfillment 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 HW Infrastructure Management Orchestrator(s) Virtual Infrastructure Management HW Equipment Management OSS/BSS Management and Orchestration Network Resource HW Resource Management HW Infrastructure Manager SDNu ODIM as potential implementation of HW IM Cloud Infrastructure CNTT reference point Redfish. Non-CNTT API as areference potentialpoint RM standard direction + ODIM support for vendor specific plug-ins DMTF Red. Fish as potential data model for this integration ETSI NFV reference point

CNTT/ODIM Alignment/Collaboration discussion topics 1. DMTF Redfish as a potential realization of the CNTT reference 2. 3. 4. 5. 6. point between HW IM and VIM/CISM CNTT Application Profiles (requirements) and DMTF Redfish discovered physical infrastructure resource capabilities CNTT Hardware Profiles & Redfish API/Model SDNu model & Redfish Fabric Model Building a CNTT reference architecture Others? Feedback/input from the telco and LFN communities welcome!