Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Contents

Table of Contents

Goal

To support latency-sensitive, high-bandwidth network functions and applications driven by 5G, Edge Computing, VoLTE use cases from a Cloud Infrastructure perspective, there are several requirements to be met. While the detailed requirements are described in the respective use cases, the key business requirements are summarized in the next section for convenience. 

...

A preliminary list of various ONAP components for realizing these requirements is in a following section.

Business Requirements Summary

To support latency-sensitive, high-bandwidth network functions and applications driven by 5G, Edge Computing, VoLTE use cases the requirements from a Cloud Infrastructure perspective are summarized below.  The detailed requirements are described in the respective use cases.

1) A single Cloud Region needs to be able to manage multiple one or more distributed (typically Edge) physical DCs

...

5) Inter-Cloud (typically Edge) Workload (especially Data Plane) Placement/Scheduling/Change Management decisions to leverage metrics and analytics information at an aggregate object level 

ONAP Components (Preliminary List)

A&AI

DCAE

Multi VIM/Cloud

OOF

Policy

SDN-C

Current Progress

Multi-Cloud Object Hierarchy & Capability Information Model Document (Focus on Summarized Requirement 2)

Multi-Cloud Object Hierarchy & Capability Information Model

Jira 

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMULTICLOUD-153

Document Contributors 

VMware: Ramki KrishnanSumit Verdi, Giridhar Jayavelu, Chris Dent, Former user (Deleted)

...

Wind River: Gil HellmannBin Yang

Document Reviewers

Huawei: Zhipeng Huang

AT&T: Arun Guptaalok411

VMware: Richard Boswell

Planned Next Steps on Document

  • Update to Modelling Sub Committee

Document Highlights

Objectives

The specification aims to define and standardize an information model which can drive cloud agnostic abstraction across various cloud provider platforms. The specification includes definitions of information objects and their relationships as they represent an individual infrastructure resource and aggregations classes.

...

  • Infrastructure Class - Representation for a NFVI resource, its information model, relationships, hierarchies, and aggregations.

  • Cloud Capability Class - Representation for cloud profiles and capabilities including technology, architecture, hardware, configurations, and so on.

  • Application Class - Representation for various workloads and their compositions to deliver end-to-end services such as vEPC, vIMS, vCPE, etc. This is out of scope for this specification.


Business Context

In the current solution landscape, Multi-vendor Cloud (OpenStack-based, VMware VIO, Microsoft Azure etc.) management involves a Cloud-specific Service Provider Design time (on-boarding, infrastructure policy authoring etc.), Deployment time (workload management etc.), Operational time (data management etc.).

...