According to ONAP Guilin Release requirement input Guilin Release Requirements
Reporting on the Guilin release to the TSC will begin nnn, so the deadline for the input of high level reuiqrement will be M0: Apr. 23rd. 2020.
Prioritize & Finalize:
before M1: May th 2020 , the requirement will be finalized.
There are other 5 categories of high level requirement,
- 1) Will be implemented in R7 by code commitment to different impacted projects/components.
- 2) Will document only for the Guilin 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 Guilin 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 the Guilin 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 |
|---|---|---|---|---|---|---|---|---|---|---|
| Resource IM/DM | ETSI VNF Model | Support mapping of ETSI NFV SOL001 v2.7.1 VNF Descriptor into AID DM | SDC | Byung-Woo Jun | ||||||
| Service DM | ETSI Network Service | Support mapping of ETSI NFV SOL001 v2.7.1 Network Service Descriptor into AID DM | SDC | Byung-Woo Jun | ||||||
VES IM VES DM Spec | StndDefined VES Notification Model Update | ONAP/3GPP & O-RAN Alignment: Standards Defined Notifications over VES MODELING-370 - Getting issue details... STATUS | DCAE VNF-REQT | ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES | damian.nowak | |||||
Service IM/DM | E2E Network Slicing Model Enhancement | Extend E2E Slicing design to support RAN, Transport and Core slice subnet | OOF, SO, AAI, SDN-C | E2E Network Slicing Use Case in R7 Guilin | guochuyi | |||||
Service IM/DM | Transport Slice Definition Model | Define the TN NSSI data model in AAI | OOF, SO, AAI, SDN-C | CCVPN - Transport Slicing | Henry Yu |
Category 2) Will document only for the Guilin 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-369 - Getting issue details... STATUS | Modeling | R7 5G Service Modeling | Benjamin Cheung | Documentation Only | REQ-320 - Getting issue details... STATUS | Benjamin Cheung | ||
| Resource IM | 5G Resource Model | Resource Modeling work to support a PNF creation MODELING-369 - Getting issue details... STATUS | Modeling | R7 5G Service Modeling | Benjamin Cheung | Documentation Only | REQ-320 - Getting issue details... STATUS | |||
| Resource IM/DM | Geolocation Model | Geolocation Model (and standards harmonization) MODELING-368 - Getting issue details... STATUS | Modeling | PNF Plug and Play (PNF Support Use Case) | Documentation Only | REQ-318 - Getting issue details... STATUS | Benjamin Cheung | |||
| Core/Resource IM | Introduction of Model Driven Application Data | Modeling | Documentation only |
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 | guochuyi |
Below tables are not downgrade, but Guilin won't make it
Category 4) Lower Priority:
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Owner |
|---|---|---|---|---|---|---|---|---|
Category 5) Experimental:
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Owner |
|---|---|---|---|---|---|---|---|---|
Resource IM/DM | Information and Data Model to support CNF | Add new information elements in the information model for MCIOP, container Descriptor, container image, ... | SDC, A&AI, SO, DCAE | Fernando Oliveira | ||||
| Resource IM/DM | CNF Inventory Information Model and AAI Schema Definition | Define a logical information model supporting CNF Inventory and develop the supporting AAI Schema Definition | AAI | CNFO | Seshu Kumar Mudiganti |
Per discussion in Paris, requirements can be based on:
- Release / project specific needs
- Recognized 'future' needs
- Documenting existing models
Some concepts may be complex enough, if we wait for the release / project requirement, we will be too late to properly develop the concept.