/
ONAP R10 Modeling High Level Requirements

ONAP R10 Modeling High Level Requirements

According to ONAP R10 Release requirement input LINK

Reporting on the R10 release to the TSC will begin on DATE, so the deadline for the input of high level requirement will be M0: DATE 2021.

Prioritize & Finalize: 

before M1: DATE 2021, the requirement will be finalized.



There are other 5 categories of high level requirement,

1) Will be implemented in R10 by code commitment to different impacted projects/components. 

2) Will document only for the R10 release.

3) Documentation after implemented in prior release

4) Lower Priority

5) Experimental

Category 1 includes those  modeling requirements that will be implemented during the current release

Category 2 includes modeling requirements that produce models that will be documented, but not implemented in the current release

Category 3 is for modeling activities that are documenting models that are already implemented in ONAP

Category 4 and Category 4 are lower priority and experimental and will not be mature in the release, the contributor will work with best effort to help influence future release.

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



Below High Level Requirements have been agreed by modeling subcommitee with code commitment promise to Istanbul release, modeling subcommittee request related to projects to approve those related submission.

Category 1) will be implemented in the R10 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

Use Case Owner

Modeling Domain

Modeling Requirement

Modeling Requirement Description

Impacted

Projects

Use Case

Relevance

Modeling Spec

Commitment

Code

Commitment

Provider

Priority

Mapping to M1 requirement

Owner

Use Case Owner

resource IM

ONAPMODEL-37: Basic CNF Resource ObjectClosed

Create CNF Object in AAI associated with vf-module/generic-vnf/cloud-region that holds basic information about ANY CNF's k8s resource

AAI, SO, Multicloud (Implementation already present)

CNFO (REQ-627: ONAP CNF orchestration - Istanbul EnhancementsDone)

@Konrad Bańka , @Lukasz Rajewski

@Konrad Bańka , @Lukasz Rajewski

TBD

TBD

@Konrad Bańka , @Lukasz Rajewski

@Seshu Kumar Mudiganti , @Lukasz Rajewski

resource IM

ONAPMODEL-40: Create ASD onboarding information modelClosed

Create ASD onboarding information model

SDC

REQ-993: Create ASD onboarding package IM / DM Done

@Marian Darula 

@Zu Qiang 

@Byung-Woo Jun 





@Marian Darula 

@Zu Qiang 

@Marian Darula