The content of this template is expected to be fill out for M1 Release Planning Milestone.
...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Guilin |
| Project Lifecycle State | Incubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | AT&T, Amdocs, Orange, Huawei, ZTE, Nokia, IBM, TechMahindra, Fujitsu |
...
The scope of the Guilin Release of AAI will address Platform Maturity Requirements, as well the approved use cases.
...
AAI R7 Guilin Release: TSC must have requirements
Requirements
WIKI PAGE: E2E Network Slicing Use Case in R7 Guilin
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Use Cases:
...
USE CASE
REQUIREMENTS
...
E2E Network Slicing
...
IMPACT: (see Jiras) Impacts to mS to extract fields from SDC. Need to investigate. E2E Slicing. Key contact: Swaminathan Seetharaman
...
Configuration & Persistency
Service
...
...
JIRA: Test Only
IMPACT: Test Only
...
WIKI PAGE: Intent-Based Network
JIRA: Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-329
IMPACT: INVESTIGATION. Identified A&AI. Contact Huang ZongHe . Presented at the Architecture S/C. Possibly moved to POC status:
Linked to:
Arch S/C recordings: ONAPARC 2020 Meetings (Copy)Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key ONAPARC-589
Presentation https://jira.onap.org/secure/attachment/16127/16127_ONAP_Proposal_IBN+V1.7.pptx
...
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:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
IMPACT:
...
WIKI PAGE: Support xNF Software Upgrade in association to schema updates
JIRA:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
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)
...
JIRA:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
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
Support for provisioning CNFs using an external K8s Manager
Support the Helm based orchestration
leverage the existing functionality of Multi cloud in SO
Bring in the advantages of the K8s orchestrator and
Set stage for the Cloud Native functioanl scenarios to be demosntarted through ONAP
Led by Seshu Kumar Mudiganti Srinivasa Addepalli Lukasz Rajewski
...
WIKI PAGE: Guilin release - functional requirements proposed list
and model planning page: ONAP R7 Modeling High Level Requirements
JIRA:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
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 Legacy | ||||||
|---|---|---|---|---|---|---|
|
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).
...
Guilin Release: Functional Use Cases
TSC MUST HAVES : AAI R7 Guilin Release: TSC must have requirements
...
Deliverable Name | Deliverable Description |
|---|---|
| A&AI resources | Executable. REST CRUD interface to graph database |
| A&AI traversal | Executable. REST Interface for complex queries |
| Data router | Executable |
| Search-data-service | Executable |
| Router-core | Library |
| Sparky-fe | Library |
| Sparky-be | Executable (AAI UI) |
| Schema-service | Executable (delivers schema to other AAI mS) |
| Graphadmin | Executable (graph administration functions) |
| ESR | Exectuable |
| OOM Config | Source code - configuration using AAI dockers in the k8 OOM environments |
| Cacher | Executable - caching interface |
Sub-Components
See Resources and Repositories (Deprecated)#ActiveandAvailableInventory
Architecture
High level architecture diagram
...
Please fill out the centralized wiki page: Guilin Release Platform Maturity
AAI data is filled out
API Incoming Dependencies
...
| 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 |
...
Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.
TBDAAI R7 Guilin: Functional Test Cases
Gaps
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.
...
Please update any risk on the centralized wiki page - Guilin Risks
Resources
TBD
Release Milestone
The milestones are defined at the Guilin Release Planning and all the supporting project agreed to comply with these dates.
...