Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Project NameEnter the name of the project
Target Release NameFrankfurt Release
Project Lifecycle StateEither Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company (Alphabetical order) AT&T, Amdocs, Bell Canada, CMCC, DT, Fujitsu, Huawei, Intel, Nokia, Orange, Samsung, Tech Mahindra 

...

  • Integrate the AAF and upgrade the APIs to Https - ATT
  • ETSI alignment improvements - Ericcson, Huawei, Verizon
    • SOL005 adaptation
    • SOL003 adaptation
  • PNF orchestration Enhancements - Ericcson, Huawei, Nokia
    • PNF sotware upgrade  
    • PNF PNP enhancement  
  • CCVPN Enhancement
    • ODM MDONS support -  Fujitsu
    • Eline support - Bell, Huawei, CMCC
  • 5G Slicing - ATT, Amdocs, CMCC, Huawei, Wipro
  • CDS integration enhancement - ATT, Bell, Tech Mahindra
  • (SO Multi Cloud plugin improvements - Intel)
  • HPA -  Intel (Testing effort)
  • Component Upgrades to new Policy Lifecycle API : Resource commitment is being checked (ATT??)


Release Requirements

Features Being considered for F releaserelease (As per the resource availability):


SOL005 Adapter supports communication security
SOL005 Adapter supports NS/VNF Package Management and NS LCM
Multi-domain Optical Network Service Orchestration Support in SO
SOL002 Adapter - supports EM-triggered VNF/VNFC Management
SO Catalog Management Support
Frankfurt release planning milestone
Initiate/ Terminate slice service; Activate/deactivate Slice service
SO support of Network Slicing Demo in Frankfurt
ETSI Alignment Support - SOL003 Adapter Enhancement for Frankfurt
AAI update for VNF improvements
SO Multicloud plugin to Multicloud improvements
SO to CDS Enhancement for Generic Implementation
S3P improvement Requirements  
Upgrade the APIs to Policy


Minimum Viable Product

Same as was defined for E-alto, but is going to add AAF integration with external APIs updated to https.

...

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

...

List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

API Name

API Description

API Definition Date

API Delivery date

API Definition link (i.e.swagger)

Interface Type
SDCAPIs for distribute service modelsDefined in AmsterdamDelivered in Amsterdam

SO interfaces


Incoming and Out going
A&AIAPIs for inventory dataDefined in AmsterdamDelivered in Amsterdam

SO interfaces


Out Going
SDN-CAPIs for network controllerDefined in AmsterdamDelivered in Amsterdam

SO interfaces


Out going
APP-CAPIs for application controllerDefined in AmsterdamDelivered in Amsterdam

SO interfaces


Out Going
VF-CAPIs for Network ServiceDefined in AmsterdamDelivered in Amsterdam

SO interfaces


Out Going
Multi-VIMAPIs for Multi-VIMDefined in CasablancaDelivered in Casablanca and enhancements expected in F release.

SO interfaces


Out Going
OOFAPIs for placement and homingDefined in BeijingDelivered in Beijing

SO interfaces


Out Going
DCAEFor PNF instantiation message from DCAE over DMaapDefined in CasablancaDelivered in Casablanca

SO interfaces


Incoming
SOL003ETS SOL003 interafces between SO and VNFMDefined in D releaseDelivered in D release

SO interfaces


Out Going
CDSgRPC APIs between SO and CDSDefined in D releaseDelivered in D release

06

Detailed doc in SO

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2504

Out Going
SOl005ETSI SOL005 interface between SO and NFVO (VFC / external)Defined in F releaseDelivered in F release

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2504

Out Going


  • Third Party Products Dependencies

...

Risk identifiedMitigation PlanContingency Plan
To fill outTo fill outTo fill out
  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

...