ONAP R7 Modeling High Level Requirements
- Andy Mayer
- guochuyi
- Vimal Begwani
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 | End of Release Status | 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 | @Fernando Oliveira @Byung-Woo Jun | @Byung-Woo Jun | 2.7.1 IM changes were accepted and merged. Initial proposal for mapping to SDC AID DM in review. Continue to R8 with possible move to v3.3.1 of ETSI SOL001. | @Fernando Oliveira @Byung-Woo Jun | @Fernando Oliveira @Byung-Woo Jun | ||
Service IM/DM | ETSI Network Service | Support mapping of ETSI NFV SOL001 v2.7.1 Network Service Descriptor into AID DM | SDC | @Fernando Oliveira @Byung-Woo Jun | @Byung-Woo Jun | 2.7.1 IM changes were accepted and merged. Initial proposal for mapping to SDC AID DM in review. Initial support for NS and Virtual Link mapping were introduced in R7. Continue to R8 with possible move to v3.3.1 of ETSI SOL001. | @Fernando Oliveira @Byung-Woo Jun | @Fernando Oliveira @Byung-Woo Jun | ||
VES IM VES DM Spec | StndDefined VES Notification Model Update | ONAP/3GPP & O-RAN Alignment: Standards Defined Notifications over VESMODELING-370: Standards Defined Notifications over VES - Modelling WorkClosed | DCAE VNF-REQT | ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES | @Vimal Begwani @marge.hillis | @damian.nowak | Update this model: VES 7.1 | |||
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 | @Borislav Glozman @guochuyi @Fei Zhang (Ericsson) | @Swaminathan Seetharaman @LIN MENG | Done Modeling work for R7 has finished, Jira has been closed. | REQ-342: E2E Network Slicing requirements for Guilin releaseDone https://lf-onap.atlassian.net/browse/MODELING-367 | @guochuyi | @LIN MENG @Swaminathan Seetharaman | |
Service IM/DM | Transport Slice Definition Model | Define the TN NSSI data model in AAI | OOF, SO, AAI, SDN-C | @Henry Yu @guochuyi | @Henry Yu @LIN MENG | Done Related changes for AAI have been delivered. | @Henry Yu | @LIN MENG @Henry Yu | ||
Service IM | Service Monitoring and Reporting | Define information model for External API Service Monitoring and Reporting based on TM Forum 628 | Modeling ExtAPI | E2E Network Slicing | @Adrian OSullivan | @Priyadharshini B @Swaminathan Seetharaman | Move to R8 | EXTAPI-450: EXT-API impacts for support of TMF 628 APIs for KPI monitoringClosed | @Adrian OSullivan | @Priyadharshini B @Swaminathan Seetharaman |
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 | End of Release Status | Mapping to M1 requirement | Owner | Use Case Contact |
|---|---|---|---|---|---|---|---|---|---|---|
Service IM | 5G Service Model | Modeling work for creating a 5G service MODELING-369: 5G Service Modeling in R7 - Modeling WorkClosed | Modeling | @Benjamin Cheung | Documentation Only | Continue to R8 | @Benjamin Cheung | @Benjamin Cheung @guochuyi | ||
Resource IM | 5G Resource Model | Resource Modeling work to support a PNF creation MODELING-369: 5G Service Modeling in R7 - Modeling WorkClosed | Modeling | @Benjamin Cheung | Documentation Only | Continue to R8 | @Benjamin Cheung | @Benjamin Cheung @guochuyi | ||
Resource IM/DM | Geolocation Model | Geolocation Model (and standards harmonization) | Modeling | PNF Plug and Play (PNF Support Use Case) | @Benjamin Cheung @Jacqueline Beaulac [Ericsson] | Documentation Only | Completed | @Benjamin Cheung | @Benjamin Cheung @Jacqueline Beaulac [Ericsson] | |
Core/Resource IM | Model Driven Model introduction in relation to C&PS | Introduction of Model Driven Application Data | Modeling | @Jacqueline Beaulac [Ericsson] @Michela Bevilacqua | Documentation only | @Jacqueline Beaulac [Ericsson] | @Jacqueline Beaulac [Ericsson] @Michela Bevilacqua | |||
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 | End of Release Status | Mapping to M1 requirement | Owner |
|---|---|---|---|---|---|---|---|---|---|
Common | Policy model | Update policy model based on implementation of policy project | @guochuyi @Michela Bevilacqua | Documentation Only | Move to R8 | @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 | End of Release Status | JIRA Link | Owner |
|---|---|---|---|---|---|---|---|---|---|
Category 5) Experimental:
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | End of Release Status | JIRA Link | 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 @Byung-Woo Jun | Initial proposal aligned with ETSI v4.1.1 IFA011 for the changes to the resource IM are available. ETSI IFA011 v3.3.1 & v4.1.1 Changes to ONAP Resource Model. Continue to R8 with a possible PoC | @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 @Andy Mayer | CNF Modeling Task Force group is awaiting Use Case input to help scope the modeling. Will continue this activity in R8 release. | @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.