AAI R7 Guilin Release: Functional Use Cases



Use Case

Status

Description

E2E Network Slicing

Accepted 

into Release

WIKI PAGE: E2E Network Slicing Use Case in R7 Guilin

JIRA: REQ-342: E2E Network Slicing requirements for Guilin releaseDone , AAI-2916: E2E Network Slicing: RAN Subnet SlicingClosed , AAI-2917: E2E Network Slicing: Transport Subnet SlicingClosed

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

https://gerrit.onap.org/r/c/aai/schema-service/+/110625

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: REQ-329: Guilin-R7 - Support for Intent-based NetworkDone

IMPACT: INVESTIGATION. Identified A&AI. Contact @Huang ZongHe . Presented at the Architecture S/C. Possibly moved to POC status:

Linked to: https://lf-onap.atlassian.net/browse/ONAPARC-589 Arch S/C recordings: ONAPARC 2020 Meetings

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

Slides: https://wiki.lfnetworking.org/pages/viewpage.action?pageId=34606297#id-2020JuneVirtualLFNDeveloper&TestingForumTopicProposals-ONAP-E2ENetworkSlicingSession2

JIRA:REQ-347: CCVPN-Transport Slicing for Guilin ReleaseDone , AAI-2920: CCVPN - Transport Slicing: AAI schema for TN NSSIClosed

Schema Update (for Guilin): Adding endpoint object

https://gerrit.onap.org/r/c/aai/schema-service/+/110925/2/aai-schema/src/main/resources/onap/oxm/v20/aai_oxm_v20.xml

PNF Software Upgrade

Accepted 

into Release

WIKI PAGE: Support xNF Software Upgrade in association to schema updates

JIRA:REQ-324: Support xNF Software Upgrade in association to schema updatesDone , AAI-2935: VNF software-version informationClosed

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

https://gerrit.onap.org/r/c/aai/schema-service/+/106824/2/aai-schema/src/main/resources/onap/oxm/v20/aai_oxm_v20.xml

CNF Orchestration

T/O

WIKI PAGE: Guilin release - functional requirements proposed list#SupportforContainerizedNetworkFunctionorchestrationthroughONAPserviceorchestrator

JIRA:REQ-341: ONAP CNF orchestration - EnhancementsDone

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

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: REQ-334: ETSI-Alignment for GuilinDone

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:  REQ-340: ONAP to support Multi - tenancy Done

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

https://gerrit.onap.org/r/c/aai/schema-service/+/108567/1/aai-schema/src/main/resources/onap/dbedgerules/v20/DbEdgeRules_v20.json

Bulk PM / PM Data Control Extension

Accepted into Release

JIRA: DCAEGEN2-2164: Bulk PM / PM Data Control Extension - PMSH EnhancementsClosed

IMPACT: Slight schema update to include sdc blueprint info

Schema Update (for Guilin): Not delivered yet