...
| Use Case | Status | Description | ||||||||||||||||||||||||
E2E Network Slicing | Accepted into Release | WIKI PAGE: E2E Network Slicing Use Case in R7 Guilin JIRA:
IMPACT: (see Jiras) Impacts to mS to extract fields from SDC. Need to investigate. E2E Slicing. Key contact: Swaminathan Seetharaman Schema Update (for Guilin): Add model-role to model object | ||||||||||||||||||||||||
Configuration & Persistency Service | T/O | WIKI PAGE: Configuration & Persistency Service R7 JIRA: Test Only IMPACT: Test Only Schema Update (for Guilin): None | ||||||||||||||||||||||||
| Intent Based Networking | Not accepted | WIKI PAGE: Intent-Based Network JIRA: IMPACT: INVESTIGATION. Identified A&AI. Contact Huang ZongHe . Presented at the Architecture S/C. Possibly moved to POC status: Linked to: Presentation https://jira.onap.org/secure/attachment/16127/16127_ONAP_Proposal_IBN+V1.7.pptx | ||||||||||||||||||||||||
| CC VPN Transport Slicing | Accepted into Release | WIKI PAGE: Guilin release - functional requirements proposed list#ccvpnTransportSlicingCCVPN-TransportSlicing An End-to-End 5G Network Slice consists of RAN, Transport and Core network slice sub-nets. This requirement is devoted to the realization Transport Slice sub-nets. It implements TN NSSMF, of which the functionality includes the modeling, orchestration and assurance of a Transport Slice. While TN NSSMF is a self-contained entity and thus this requirement can be independent, ensuring the integration with the E2E Network Slicing is an important aspect of this requirement. Standards-based interfaces and architectural framework (e.g., ETSI ZSM, IETF) are used by this requirement. Storing Slice ID, and which Element participating in the Slice. Swaminathan Seetharaman ; https://wiki.lfnetworking.org/display/LN/2020+June+Virtual+Recordings JIRA:
IMPACT: Schema Update (for Guilin): Add model-role to model object | ||||||||||||||||||||||||
| PNF Software Upgrade | Accepted into Release | WIKI PAGE: Support xNF Software Upgrade in association to schema updates JIRA:
IMPACT: Lead: Zu Qiang , Support xNF Software Upgrade in association to schema updates. VNF S/W version into A&AI. Done in eComp? ported to ONAP (confirmed) (from Chris Rapposelli-Manzo). Email sent from Lukasz to Zu Qiang Generic-VNF object in A&AI will have software-version attribute. It should be optional and should be of string type. Exemplary values are: "1.0", "1.0.1", "2.0.0" It is in the S/W but Not in Swagger file yet (version 19). Perhaps swagger not generated yet. How is the swagger file updated? Targeted for V20? still needs to generated and published. (will be other changes too) Schema Update (for Guilin): Software version added for generic-vnf | ||||||||||||||||||||||||
| CNF Orchestration | T/O | JIRA:
IMPACT: DDF Presentation: https://wiki.lfnetworking.org/download/attachments/40370243/CNF%20Orchestration%20through%20ONAP.mp4?api=v2 Provide CNF orchestration support through integration of K8s adapter in ONAP SO
Led by Seshu Kumar Mudiganti Srinivasa Addepalli Lukasz Rajewski Schema Update (for Guilin): None | ||||||||||||||||||||||||
| ETSI Alignment | Accepted into Release | WIKI PAGE: Guilin release - functional requirements proposed list and model planning page: ONAP R7 Modeling High Level Requirements JIRA:
IMPACT: Note: if AAI needs some minor schema changes for ETSI modeling, one of the ETSI-Alignment participating companies will update the AAI schema. It is part of the user stories. Fernando Oliveira leading this work. Byung-Woo Jun Schema Update (for Guilin): TBD | ||||||||||||||||||||||||
Multi-Tenancy | Accepted into Release | WIKI PAGE: ff JIRA: IMPACT: Lead Olivier Phenix , Mike Elliott (AMdocs OOM) schema, multiple tenant pointing to same A&AI instance. Retreive operate on their own PNFs. (not available in A&AI yet). How to support multiple ONAP components on same cluster. Access Control. Can't tag PNFs. Schema Update (for Guilin): Edge rule added for pnf to owning entity relationship |