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(?) Policy (Y) VFC (Y) | |
PNF for 5G | software version | SDC SO | 5G | Nokia | SDC (Y) SO (under discussion) |
2) Documentation after implemented, or implemented but not in the 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 |
---|---|---|---|---|---|---|---|---|---|
Service | Service Order | It includes the definition of the managed objects that allows a BSS system to create/delete/update/get an order of a service to a ONAP instance. The Service Order Modeling provided by Ext API R2 team must be reviewed to become part of the ONAP common service IM | Ext API(y) | VoLTE CCVPN Change Mgt | CMCC Huawei ZTE Vodafone AT&T Verizon Orange | CMCC Huawei ZTE Vodafone Orange | CMCC: High Vodafone: High AT&T: High Verizon-High | ExtAPI (y) | Andy Mayer (AT&T) |
Service Catalog | A Service Catalog is a group of ServiceDescriptors that an organization provides to the consumers via ONAP. | Ext API | VoLTE CCVPN | CMCC Huawei ZTE Vodafone AT&T Verizon Orange | CMCC Huawei ZTE Orange | CMCC: High Vodafone: High AT&T: High Verizon-High | ExtAPI (y) | Kevin Scaggs (AT&T) | |
Service Descriptor | Design time model: service descriptor model correlating with the service instance in run time | A&AI Ext API SO(y) SDC(->) | (All) VoLTE CCVPN 5G vCPE | CMCC Huawei ZTE Vodafone AT&T Verizon Orange | CMCC Huawei ZTE Orange | CMCC: High Vodafone: High AT&T: High Verizon-High | LIN MENG (CMCC) | ||
Resource | License | Presently modeled and used in SDC (ONAP license model) | SDC | AT&T Verizon | AT&T: Medium Verizon-Medium | SDC | Kevin Scaggs(AT&T) | ||
Alloted resource | SDCs current implementation | SDC | All | AT&T Intel | AT&T Intel | AT&T: High | SDC | Andy Mayer (AT&T) | |
Scaling (HEAT template) | Scaling Use Case Extension . Casablanca focus: Document the Policy Model that is being implemented by the ONAP Policy Framework. | SDC (no impact) A&AI (no impact) SO (no impact) Policy Clamp (no impact) | vDNS (Scaling) | CMCC Huawei ZTE AT&T | CMCC: Medium Vodafone: Medium AT&T: High | SDC (no impact) A&AI (no impact) SO (no impact) Policy (Y) Clamp (no impact) | Andy Mayer (AT&T) Gil Bullard ((AT&T) | ||
ResourceComposite | The ResourceComposite includes several sub-requirements:
| SDC VNFSDK(y) | VoLTE CCVPN | CMCC Huawei ZTE Vodafone AT&T Verizon Intel | CMCC Huawei ZTE Intel | CMCC: High Vodafone: High AT&T: High Verizon-High | SDC () VNFSDK (y) | ||
Network Service (modeling subcommitee DM approve firstly) | Context:
Network service is agreed in resource IM group. Networkservice IM 4. SDC progress org.openecomp.resource.vfc.NSD has been imported in ONAP catalog in R2 SDC functionality does not support NSD yet in R2
1. SDC design UI, catalog(FE,BE,Database, API) shall support NS and related package base R2 link 2. In resource design, NS descriptor shall be composed of VNFD, and VLD at least to support VoLTE 3. In service design, service descriptor could be composed of the NSD. 4. NS descriptor shall refinement to support R3 NS DM Proposal( Stretch goal) | SDC | VoLTE CCVPN 5G | CMCC Huawei ZTE AT&T | CMCC Huawei ZTE | CMCC: High Vodafone: High AT&T: Medium | SDC | Chuyi Guo | |
Telemetry | Events & VES | VES Event Descriptor Model according to VES spec v6.0 | DCAE SDC | AT&T Verizon | AT&T: High Verizon-High | DCAE(Y) SDC |
Below tables are not downgrade, but casablanca won't make it
3) Lower Priority:
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Owner |
---|---|---|---|---|---|---|---|---|
Service | servicecomposite | Design/run time model : Service IM review according to the agreed Service Composite pattern. (Composite Pattern UML diagram) | SDC (L) Ext API (=SDC) SO | VoLTE CCVPN | CMCC Huawei ZTE Vodafone AT&T Verizon | CMCC Huawei ZTE | CMCC: High Vodafone: High AT&T: High Verizon-High | |
Service Scaling | A run time service instance could be updated by scaling in/out its capacity via deleting/adding new resources instances, e.g. sites in CCVPN usecase. | SDC SO AAI | VoLTE CCVPN | CMCC Huawei ZTE Vodafone AT&T Verizon | CMCC: High Vodafone: High AT&T: Medium Verizon-Medium | |||
Service Instance | Run time model: service instance model in relation to the design time model and Service Composite pattern. (Composite Pattern UML diagram) | A&AI Ext API SO SDC | (All) VoLTE CCVPN vCPE | CMCC Huawei ZTE Vodafone AT&T Verizon Orange | CMCC: High Vodafone: High AT&T: High Verizon-High | Kevin Scaggs(AT&T) | ||
Resource | ResourceComposite | Design time model: Resource composite model introduction according to the agreed Service Composite pattern. It includes the NS model review from Service component to Resource Composite and change of Modeling Domain (Composite Pattern UML diagram) The ResourceComposite includes below sub-requirements:
| SDC(->) VNFSDK | VoLTE CCVPN | CMCC Huawei ZTE Vodafone AT&T Verizon Intel | CMCC Huawei ZTE | CMCC: High Vodafone: High AT&T: High Verizon-High | |
VNF instance (run time) | Run time model of a VNF instance (low) | A&AI | VoLTE CCVPN 5G vCPE | CMCC Huawei ZTE AT&T Verizon | CMCC Huawei ZTE | CMCC: High Vodafone: High AT&T: High Verizon-High | Kevin Scaggs (AT&T) | |
PNF instance (run time) | Run time model of a PNF Instance. | SDNC A&AI SO | VoLTE CCVPN 5G | CMCC Huawei ZTE Vodafone | CMCC Huawei ZTE | CMCC: Medium Vodafone: Medium | Weitao Gao | |
WAN Connection | Wan Connection Information Model | SDC(->) SO A&AI SDNC | VoLTE CCVPN | CMCC Huawei ZTE AT&T Verizon | CMCC Huawei ZTE | CMCC: High Vodafone: High AT&T: Medium Verizon-Medium | Zhuoyao Huang | |
SD-WAN | CCVPN SD-WAN Information Model | CMCC Huawei AT&T Verizon | CMCC: High Vodafone: High AT&T: Medium Verizon-High | Chuanyu Chen | ||||
ElementGroup enhancement (lower) | Tied to modeling of Scaling, Homing, Placement, etc. | SDC SO | AT&T | AT&T: Medium | Andy Mayer (AT&T) Kevin Scaggs (AT&T) | |||
Infrastructure | Multi-cloud | The cloud abstractions needed for homing in the edge cloud across public cloud and service-provider-owned-cloud | Multicloud | AT&T | AT&T: Medium | |||
Telemetry |
4) Experimental:
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Owner |
---|---|---|---|---|---|---|---|---|
Resource | Container | Resource modeling changes in the IM, design time DM and runtime DM | Multi-Cloud | Intel | Intel | |||
Acceleration Management (BoF) | Discussing the requirement for acceleration management in ONAP, including research motivation,problem statement, as well as proposals. Welcome to join this thread. | Lei Huang |