The content of this template is expected to be fill out for M1 Release Planning Milestone.
...
AAI R7 Guilin Release: TSC must have requirements
Requirements
...
Use Cases:
USE CASE REQUIREMENTS | DESCRIPTION & DISCUSSION | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
E2E Network Slicing | 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 | ||||||||||||||||||||||||
Configuration & Persistency Service | WIKI PAGE: Configuration & Persistency Service R7 JIRA: Test Only IMPACT: Test Only | ||||||||||||||||||||||||
| Intent Based Networking | 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 | 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: | ||||||||||||||||||||||||
| PNF Software Upgrade | 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) | ||||||||||||||||||||||||
| CNF Orchestration | 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 | ||||||||||||||||||||||||
| ETSI Alignment | 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 | ||||||||||||||||||||||||
Multi-Tenancy | 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. |
TSC MUST HAVES : AAI R7 Guilin Release: TSC must have requirements
Minimum Viable Product
- A&AI Core: Resources - CRUD REST API endpoints for A&AI inventory resources
- A&AI Core: Traversal - REST APIs for graph traversals. Some APIs use the Gremlin Server
- UI - An ONAP portal application used by operations for visualizing and searching
- Data Router: Makes decisions about workloads to be dispatched to search and tabular microservces. Includes logic to recognize and direct requests based on request archetypes.
- Search - Enable complex searches for sub graphs and functions that need to perform well across deeply nested structures using Elasticsearch. Used by the UI
- Cacher - The Response Caching Microservice (Cacher) is built to deliver multiple mechanisms of making API calls and populating the responses into a JSON datastore. The datastore is an embedded mongodb datastore, that stores cached API responses, which are updated via DMAAP events or can be synced by timed tasks or calls to the force sync endpoint.
- ESR - External System Registry component (provided community can deliver support, update vulnerable dependencies, and maintain the project)
...
| Name | Description | Version |
|---|---|---|
| JanusGraph | Open-source, distributed graph database | 0.2.3 |
| Cassandra | Open-source distributed storage system | 3.11 |
| Docker | VM container | |
| SpringBoot | Open-source Microservice application sever | 1.5.22 or 2.x |
| ElasticSearch | Search framework | 6.8 |
| HAPROXY | microservice front end | 1.8 |
| Centos/Alpine | OS | See docker config files |
...