ONAP R6 Modeling High Level Requirements
- Hui Deng
- Zu Qiang
- Andy Mayer
According to ONAP Frankfurt Release requirement input Frankfurt Release Requirements
Gather requirement: July 1-31
Refine requirement: Aug. 1-31
Reporting on the Frankfurt release to the TSC will begin Aug 22, so the deadline for the input of high level reuiqrement will be Aug 22.
Prioritize & Finalize: Sep. 1-23
before M1: Sep. 23rd , the requirement will be finalized.
There are other 5 categories of high level requirement,
1) Will be implmented in R6 by code commitment to different impacted projects/components.
2) Will document only for the Frankfurt release.
3) Documentation after implemented in prior release
4) Lower Priority
5) Experimental
The first category is that those requirement will be documented only in Frankfurt 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.
Below High Level Requirements have been agreed by modeling subcommitee with code commitment promise to Frankfurt release, modeling subcommittee request related to projects to approve those related submission.
Category 1) will be implemented in R6
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 |
|---|---|---|---|---|---|---|---|---|---|---|
Service DM | Enhanced Nested and Shared Service Information Model | SDC,SO, OOF,AAI
| Network Slicing | @guochuyi | @Borislav Glozman @Shankaranarayanan Puzhavakath Narayanan @Swaminathan Seetharaman | @guochuyi | @Borislav Glozman @Shankaranarayanan Puzhavakath Narayanan @Swaminathan Seetharaman | |||
Resource IM/DM | RunTime DB U/C: VES Model relations, VES CM model (CM Notify). | AAI, Controller (RunTime DB component), DCAE | RunTime DB (5G Use Case) | @Kevin Scaggs | @N.K. Shankaranarayanan @Sandeep Shah | @Joanne Liu Rudel @Benjamin Cheung | ||||
Resource IM/DM | Software Versions support for PNF S/W Upgrade REQ-88: Enable PNF software version at onboardingDone | SDC | PNF S/W Upgrade (PNF Support Use Case) | @Fei Zhang (Ericsson) | @Zu Qiang | @Zu Qiang | ||||
Service IM, Resource DM | End to End Layer 1 Service Management. Modeling the Optical Service. | Multi-domain Optical Service L0/L1 Orchestration | @Xin Miao (Unlicensed) | @Xin Miao (Unlicensed) | @Raghavan Subramanian | |||||
Resource IM/DM | Data type & Node type for 5G NRM. | SDC, SO, CDS REQ-49: 5G NRM Configuration Management with RESTFul protocolDone | 5G NRM Configuration | @wangyaoguang | @wangyaoguang | @wangyaoguang |
Category 2) Will document only for the Frankfurt release
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects |
|---|