According to ONAP R9 Release requirement input Guilin Release RequirementsINKinput LINK
Reporting on the R9 release to the TSC will begin nnnon DATE, so the deadline for the input of high level requirement will be M0: DATE 2020 2021.
Prioritize & Finalize:
before M1: DATE 2020 2021, the requirement will be finalized.
...
There are other 5 categories of high level requirement,
1) Will be implemented in R9 by code commitment to different impacted projects/components.
2) Will document only for the R9 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 R9 release
the second category will document the current implementation in those projects.
Other two categories like 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 included mature in the release 3, the contributor will work with best effort to help influence future release.
Owners of each requirement needs 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 Honolulu to Istanbul release, modeling subcommittee request related to projects to approve those related submission.
...
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) | R8 PNF Plug and Play Use Case | Benjamin Cheung | damian.nowak |
This is the REQ Jira for the R9 PNF Plug and Play Use Case. | Benjamin Cheung | Resource IM/DM | ETSI VNF Model | Support mapping of ETSI NFV SOL001 v3.3.1 VNF Descriptor + CNF enhancements from IFA011 v4.1.1 into AID DM | SDC, SO |
| Fernando Oliveira | Byung-Woo Jun |
| Service IM/DM | E2E Network Slicing – Enhanced solution of 3 domain network combination |
| OOF, SO, AAI, SDN-C | R8 E2E Network Slicing use case
| @LIN MENG |
|---|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
@LIN MENG
(may have S/W impact / implementation - may move to Category 1)
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Overview Slides:
ConfigurationPersistenceSvcDDF_202010Oc15v12.pdf
Potential Impacts to SDC and affects associated Use cases that use CPS such as E2E Network Slicing and OOF SON use cases.
- UML modeling for interface to represent information elements provided on the CPS APIs ( Toine Siebelink )
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Related discussion
Category 2) Will document only for the R9 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 Contact | Service IM | 5G Service Model | Modeling work for creating a 5G Service | Modeling | R8 5G Service Modeling | Benjamin Cheung | Documentation Only |
Overview slides: | Benjamin Cheung | Resource IM | 5G Resource Model | Resource Modeling Work to support a live 5G PNF | Modeling | R8 5G Service Modeling | Benjamin Cheung | Documentation Only |
Architecture Review completed. Meetings scheduled monthly at 5G - Use Case Realization Calls | Benjamin Cheung | Resource IM | Model update for StndDefined VES | Update VES7.2 in Papyrus | Modeling | R8 ONAP/3GPP & O-RAN Alignment: Standard Defined VES | Benjamin Cheung | Documentation Only |
| Benjamin Cheung | Marge Hillis | Resource IM | Abstract Topology Modeling | Begin development of an Abstract Topology Model | Modeling | ONAP / O-RAN Alignment | Documentation Only |
| Andy MayerMartin Skorupski | ||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Category 3) Documentation Only after implemented in prior 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 | Common | Policy model | Update policy model based on implementation of policy project | Documentation Only | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Jira Legacy | |||||||||||||||
| server | System Jira | ||||||||||||||
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 | MODELING-439 | guochuyi | ||||||||||||
Below tables are not downgrade, but Guilin won't make itproduce modeling activity for the current release
Category 4) Lower Priority:
...
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | JIRA Link | Owner | IM / DM | (in R9 Istanbul release) Vertical Industry Use Case will investigate E2E NS & CPS modeling interactions | Vertical Industry Use Case | Proof of Concept in R9 | PoC |
| Cheng Huang |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Requirements can be based on:
...