Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 44 Next »

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 requirementOwnerUse Case Owner
Resource IM/DMETSI VNF ModelSupport mapping of ETSI NFV SOL001 v2.7.1 VNF Descriptor into AID DMSDC
Byung-Woo Jun

REQ-334 - Getting issue details... STATUS

Service DMETSI Network ServiceSupport mapping of ETSI NFV SOL001 v2.7.1 Network Service Descriptor into AID DMSDC
Byung-Woo Jun

REQ-334 - Getting issue details... STATUS

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 VESdamian.nowak


Update this model: VES 7.1

REQ-327 - Getting issue details... STATUS



Service

IM/DM


E2E Network Slicing Model EnhancementExtend E2E Slicing design to support RAN,  Transport and Core slice subnetOOF, SO, AAI, SDN-CE2E Network Slicing Use Case in R7 Guilin

REQ-342 - Getting issue details... STATUS

MODELING-367 - Getting issue details... STATUS


guochuyi

Service

IM/DM

Transport Slice Definition ModelDefine the TN NSSI data model in AAIOOF, SO, AAI, SDN-CCCVPN - Transport Slicing

REQ-347 - Getting issue details... STATUS

AAI-2920 - Getting issue details... STATUS

Henry Yu
Service IMService Monitoring and ReportingDefine information model for External API Service Monitoring and Reporting based on TM Forum 628

Modeling

ExtAPI

E2E Network Slicing

EXTAPI-450 - Getting issue details... STATUS

EXTAPI-453 - Getting issue details... STATUS

Adrian OSullivan


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 requirementOwnerUse Case Contact
Service IM5G Service Model

Modeling work for creating a 5G service

MODELING-369 - Getting issue details... STATUS

ModelingR7 5G Service ModelingBenjamin CheungDocumentation Only

REQ-320 - Getting issue details... STATUS

Benjamin Cheung
Resource IM5G Resource Model

Resource Modeling work to support a PNF creation

MODELING-369 - Getting issue details... STATUS

ModelingR7 5G Service ModelingBenjamin CheungDocumentation Only

REQ-320 - Getting issue details... STATUS

Resource IM/DMGeolocation Model

Geolocation Model (and standards harmonization)

MODELING-368 - Getting issue details... STATUS

ModelingPNF Plug and Play (PNF Support Use Case)Documentation Only

REQ-318 - Getting issue details... STATUS

Benjamin Cheung
Core/Resource IMModel Driven Model introduction in relation to C&PS

Introduction of Model Driven Application Data

MODELING-382 - Getting issue details... STATUS

ModelingConfiguration & Persistency Service R7Documentation only

REQ-322 - Getting issue details... STATUS

REQ-384 - Getting issue details... STATUS

Jacqueline Beaulac [Ericsson]












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

MODELING-389 - Getting issue details... STATUS

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

JIRA Link Owner










Category 5) Experimental:

Modeling Domain

Modeling Requirement

Modeling Requirement Description

Impacted

Projects

Use Case

Relevance

Modeling Spec

Commitment

Code

Commitment

Provider

Priority

JIRA Link Owner

Resource IM/DM

Information and Data Model to support CNFAdd new information elements in the information model for MCIOP, container Descriptor, container image, ...SDC, A&AI, SO, DCAE



Fernando Oliveira
Resource IM/DMCNF Inventory Information Model and AAI Schema DefinitionDefine a logical information model supporting CNF Inventory and develop the supporting AAI Schema DefinitionAAICNFO


Seshu Kumar Mudiganti
Resource IM/DMC&PS

Model Topology

C&PS PoC



Benjamin Cheung

Model Topology

Configuration & Persistency Service R7





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.



  • No labels