You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 88 Next »

Based on timeplan of modeling subcommittee, high level requirements need to be finished by M0, 

There are 4 categories of high level requirement,

The first category is that those requirement will be implemented and commited by the impacted projects in this release

the second category will document the current implementation in those projects.

Other two categories like lower priority and experimental will not be included in the release 3, the contributor will work with best effort to influence future release.

Owners of each requirement needs to coordinate the modeling spec commitment and code commitment with PTLs of impacted project.

1) Will be implemented and included in the release 3


Modeling Domain

Modeling Requirement

Modeling Requirement Description

Impacted

Projects

Use Case

Relevance

Modeling Spec

Commitment

Code

Commitment

Provider

Priority

Mapping to M1 requirementOwner

Resource

VNFD

ONAP Resource Data Model for Design Time?

-Agreement that the VNF Descriptor model for On-Boarding and the Internal ONAP models are distinct. (note: an internal model may be used as one of the on-boarding options)
•For R3 the VNF Descriptor On-Boarding options include: HEAT and TOSCA (SOL004 v2.5.1 VNF Package, ONAP R3 Resource DM) (see note)
-Acknowledgement that there are two Internal ONAP VNF Descriptor Data Models that, for R3, will evolve wherever possible in a coordinated way in support of the Casablanca Use Cases
•ONAP R2+ Design-Time Resource DM clean version enhancements for VoLTE, CCVPN, vCPE (stretch goal)
•ONAP SDC TOSCA AID enhancements for vCPE
-Engage impacted ONAP Components to understand the VNF Descriptor aspects of these two Internal ONAP R3 Resource Data Models are applied
•Document ONAP R3 VNFD on-boarding and internal models roadmap with all ONAP components stakeholders

SDC

A&AI

OOF

SO

VFC

Policy

VoLTE

VCPE

CCVPN

AT&T

Intel

AT&T

Intel

AT&T: High

SDC (Y)

A&AI

SO (Y)

OOF(?)

Policy (Y)

VFC (Y)

 PNF for 5G

 software version


SDC

SO

 5G
 Nokia

SDC (Y)

SO (under discussion)


2) Documentation after implemented, or implemented but not in the release

Modeling Domain

Modeling Requirement

Modeling Requirement Description

Impacted

Projects

Use Case

Relevance

Modeling Spec

Commitment

Code

Commitment

Provider

Priority

Mapping to M1 requirement Owner

 Service

 

Service Order

It includes the definition of the managed objects that allows a BSS system to create/delete/update/get an order of a service to a ONAP instance. The Service Order Modeling provided by Ext API R2 team must be reviewed to become part of the ONAP common service IM

(Service Order - Information Model View)

Ext API(y)

VoLTE

CCVPN

Change Mgt


CMCC

Huawei

ZTE

Vodafone

AT&T

Verizon

Orange

CMCC

Huawei

ZTE

Vodafone

Orange

CMCC: High

Vodafone: High

AT&T:  High

Verizon-High

ExtAPI

(y)

Andy Mayer (AT&T)

 Service Catalog A Service Catalog is a group of ServiceDescriptors that an organization provides to the consumers via ONAP.

https://wiki.mef.net/display/CESG/Service+Catalog

Ext API VoLTE

CCVPN

CMCC

Huawei

ZTE

Vodafone

AT&T

Verizon

Orange

CMCC

Huawei

ZTE

Orange

CMCC: High

Vodafone: High

AT&T:  High

Verizon-High

ExtAPI

(y)

 Kevin Scaggs (AT&T)

 Service DescriptorDesign time model: service descriptor model

correlating with the service instance in run time

A&AI

Ext API

SO(y)

SDC(->)

(All)

VoLTE

CCVPN

5G

vCPE

CMCC

Huawei

ZTE

Vodafone

AT&T

Verizon

Orange

CMCC

Huawei

ZTE

Orange

CMCC: High

Vodafone: High

AT&T: High

Verizon-High

 LIN MENG

(CMCC)

Resource  License Presently modeled and used in SDC

(ONAP license model)

SDC
 AT&T

Verizon


 AT&T:  Medium

Verizon-Medium

SDC Kevin Scaggs(AT&T)
Alloted resource SDCs current implementation SDC AllAT&T

Intel

AT&T

Intel

AT&T: High SDC

Andy Mayer (AT&T)

Scaling (HEAT template) Scaling Use Case Extension (VNF Design and Run time model extension to support scaling use case).

Ensure that the onboarding VNF model will properly updated.

SDC

A&AI

SO

Policy

Clamp

 vDNS (Scaling)CMCC

Huawei

ZTE

AT&T


CMCC: Medium

Vodafone: Medium

AT&T:  High

SDC

A&AI

SO

Policy

Clamp

 Andy Mayer (AT&T)
ResourceCompositeThe ResourceComposite includes several sub-requirements:
  • support composite relationship between different resource objects, e.g., a NS can be composed of VNF, VL, etc. (need to support TOSCA substitution mapping)
  • support semantics validation during onboarding and design time. For example, during design time, checking a NS can be composed of VNF, VL, nested NS, etc., but no irrelevant resources; during onboarding time, checking a VNFD doesn't contain more than one VNF node
SDC

VNFSDK(y)

 VoLTE

CCVPN

CMCC

Huawei

ZTE

Vodafone

AT&T

Verizon

Intel

CMCC

Huawei

ZTE Intel

CMCC: High

Vodafone: High

AT&T:  High

Verizon-High

SDC ()

VNFSDK

(y)

Network Service

(modeling subcommitee  DM approve firstly)

Network service is already modeled in R2 but is now moved as a Resource Composite.
  1. In R3, NSD can be composed of VNFD, VLD in design time at least to support VOLTE usecase.
  2. In R3, NSD can be composed of nested NSD, and other resources(VNFD, PNFD,VLD, etc) in design time if possible

Networkservice IM

Networkservice DM

 SDCVoLTE

CCVPN

5G

CMCC

Huawei

ZTE

AT&T

CMCC

Huawei

ZTE

CMCC: High

Vodafone: High

AT&T:  Medium

SDCChuyi Guo

Telemetry

Events & VES

VES Event Descriptor Model according to VES spec v6.0

DCAE

SDC


AT&T

Verizon


AT&T:  High

Verizon-High

DCAE

SDC


Below tables are not downgrade, but casablanca won't make it

3) Lower Priority:

Modeling Domain

Modeling Requirement

Modeling Requirement Description

Impacted

Projects

Use Case

Relevance

Modeling Spec

Commitment

Code

Commitment

Provider

Priority

 Owner

Service


servicecomposite Design/run time model : Service IM review according to the agreed Service Composite pattern. (Composite Pattern UML diagram) SDC (L)

Ext API (=SDC)

SO

 VoLTE

CCVPN

 CMCC

Huawei

ZTE

Vodafone

AT&T

Verizon

 CMCC

Huawei

ZTE

CMCC: High

Vodafone: High

AT&T:  High

Verizon-High

 Service Scaling A run time service instance could be updated by scaling in/out its capacity via deleting/adding new resources instances, e.g. sites in CCVPN usecase. SDC

SO

AAI

VoLTE

CCVPN

CMCC

Huawei

ZTE

Vodafone

AT&T

Verizon


 CMCC: High

Vodafone: High

AT&T:  Medium

Verizon-Medium

Service Instance

Run time model: service instance model

in relation to the design time model and Service Composite pattern. (Composite Pattern UML diagram)

A&AI

Ext API

SO

SDC

(All)

VoLTE

CCVPN

5G

vCPE

 CMCC

Huawei

ZTE

Vodafone

AT&T

Verizon

Orange


CMCC: High

Vodafone: High

AT&T: High

Verizon-High

Resource

 

ResourceComposite

Design time model: Resource composite model introduction according to the agreed Service Composite pattern. It includes the NS model review from Service component to Resource Composite and change of Modeling Domain (Composite Pattern UML diagram)

The ResourceComposite includes below sub-requirements:

  • support composite pattern (i.e., ResourceAtomic and ResourceComposite) in the IM and DM

SDC(->)

VNFSDK

VoLTE

CCVPN


CMCC

Huawei

ZTE

Vodafone

AT&T

Verizon

Intel

CMCC

Huawei

ZTE
Intel


CMCC: High

Vodafone: High

AT&T:  High

Verizon-High


 VNF instance (run time) Run time model of a VNF instance

(low)

 A&AI VoLTE

CCVPN

5G

vCPE

CMCC

Huawei

ZTE

AT&T

Verizon
Intel

CMCC

Huawei

ZTE

CMCC: High

Vodafone: High

AT&T:  High

Verizon-High

 Kevin Scaggs (AT&T)
PNF instance (run time)Run time model of a PNF Instance.SDNC

A&AI

SO

VoLTE

CCVPN

5G

CMCC

Huawei

ZTE

Vodafone

CMCC

Huawei

ZTE

CMCC: Medium

Vodafone: Medium

Weitao Gao
 WAN Connection Wan Connection Information Model


SDC(->)

SO

A&AI

SDNC

VoLTE

CCVPN

CMCC

Huawei

ZTE

AT&T

Verizon

CMCC

Huawei

ZTE

CMCC: High

Vodafone: High

AT&T:  Medium

Verizon-Medium

Zhuoyao Huang
SD-WANCCVPN SD-WAN Information Model

CMCC

Huawei

AT&T

Verizon


CMCC: High

Vodafone: High

AT&T:  Medium

Verizon-High

Chuanyu Chen
ElementGroup enhancement

(lower)

Tied to modeling of Scaling, Homing, Placement, etc.SDC

SO


 AT&T
 AT&T:  MediumAndy Mayer (AT&T)

Infrastructure

Multi-cloud

The cloud abstractions needed for homing in the edge cloud across public cloud and service-provider-owned-cloudMulticloud

Edge automation

AT&T


AT&T:  Medium

Telemetry









4) Experimental:

Modeling Domain

Modeling Requirement

Modeling Requirement Description

Impacted

Projects

Use Case

Relevance

Modeling Spec

Commitment

Code

Commitment

Provider

Priority

 Owner

Resource

Container

Resource modeling changes in the IM, design time DM and runtime DMMulti-Cloud


Intel

Intel


Acceleration Management (BoF)

Discussing the requirement for acceleration management in ONAP, including research motivation,problem statement, as well as proposals. Welcome to join this thread.

( Acceleration Management (BoF) )






Lei Huang












  • No labels