ONAP R8 Modeling High Level Requirements
- Andy Mayer
- Benjamin Cheung
- Fei Zhang (Ericsson)
According to ONAP R8 Release requirement input LINK
Reporting on the R8 release to the TSC will begin nnn, so the deadline for the input of high level requirement will be M0: DATE 2020.
Prioritize & Finalize:
before M1: DATE 2020 , the requirement will be finalized.
There are other 5 categories of high level requirement,
1) Will be implemented in R8 by code commitment to different impacted projects/components.
2) Will document only for the R8 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 R8 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 Honolulu release, modeling subcommittee request related to projects to approve those related submission.
Category 1) will be implemented in the R8 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 |
|---|---|---|---|---|---|---|---|---|---|---|
A&AI Schema DM | Place Model | Uses the Place Information Model to associate instance of it to PNF in AAI | SO (AssignpnfBB) | @Benjamin Cheung | @damian.nowak |