ONAP R3 Modeling High Level Requirements
Based on timeplan of modeling subcommittee, high level requirements need to be finished by M0,
There are 4 categories of high level requirement,
The first category is that those requirement will be implemented and commited by the impacted projects in this 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.
1) Will be implemented and included in the release 3
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Mapping to M1 requirement | Owner |
---|---|---|---|---|---|---|---|---|---|
Resource | VNFD | ONAP Resource Data Model for Design Time? -Agreement that the VNF Descriptor model for On-Boarding and the Internal ONAP models are distinct. (note: an internal model may be used as one of the on-boarding options) | SDC A&AI OOF SO VFC Policy | VoLTE VCPE CCVPN | AT&T Intel | AT&T Intel | AT&T: High | SDC (Y) A&AI (Y) SO (Y) OOF(Y) Policy (Y) VFC (Y) | @Andy Mayer (AT&T) @Anatoly Katzman (AT&T) |