The Architecture Requirements are Summarized here: The full release requirements (including Architecture requirements) are captured here: Frankfurt Release Requirements;

These are listed with EPIC, then the following stories.  The Epics are added manually, hence a complete list of Epics are included below.







To appear here, the JIRAs need the label ARC-REQ-FRANKFURT.  Mark the release as Frankfurt


EPIQs and stories here should be approved by ArchCom

The ones that are "agreed" in the architecture sub-committee are marked as:  This is still to be decided.


Summary / Status

Requirement/UseCase/...Status

Orchestration Scenarios

ArchCom approved

 LCM API Evolution

 ArchCom approved

  Edge Automation

Distributed Management Task Force - not ArchCom approved

  • Scope for Franfurt - "Extend Central K8S to register Edge Clouds"
    • Centrally manage k8s Edge Clouds (k8s-clusters)
    • Use Custom Resource Definition as Registry
    • Provide ability to extend CRD to contain metadata
      • -Location label 

      • -Edge type (ICN, AWS, Azure, etc.) 

      • -External IP 

      • -Namespaces, user for authorization

    • Edge Cloud Naming
      • Follow Cloud (AWS etc.) naming convention with additional operator name?

Questions: still to be answered:

  • how to determine the location
  • Is it OK to use different services for the applications centrally and distributed.  Which applications are taking these up. 

3rd Party Operational Domain Controller

 

 ArchCom approved for current direction.

Note: Not full functionality in Frankfurt.  One open issue to resolve as to whether the external service needs to be wrapped in an ONAP service to have consistent orchestation approach (or not).

 Service Resolver

 Not Yet Archcom approved

 Model Driven ONAP

<< req >>

 Not Yet Archcom approved

 Orchestration of Contain Based VNFs

<<>>

 Frankfurt Release ??

 Applications on ONAP

<<?? >>

 Not Yet Archcom approved

 API-GW

<<>>

 There will not be a proposal for Frankfurt.

 Runtime DB

<< >>

 Status: need and concept OK by Archcom:

 5G / ORAN & 3GPP Standards Harmonization

 Status: Archcom approved

 ONAP CLI for VNF

<<??>>

 

Status: Note yet Archcom approved

 Slicing Evolution

 Not Archcom Approved

 Multidomain optical service

 Archcom Approved

 Integrate Acumos with DCAE

Self Service Control Loop

 Archcom approved
xNF licencing with ONAP

Archcom approved (principles) (licening server outside ONAP)

ETSI catalogue as a common service

Archom approved.  Part of ETSI-ONAP alignment requirements

CDS support of K8S

Archcom approved

Analytics (or VNF) at the edge using Akrono antaticis orchestrated by ONAP

Not Archcom approved




Orchestration Scenarios: ONAPARC-403

Status: Archcom approved:


Controller Evolution:

Controller Evolution towards combined GNFC: https://wiki.onap.org/download/attachments/53248195/Controller%20EvolutionElAlto04012019.pptx?version=2&modificationDate=1554220494764&api=v2

STATUS: The approach has been approved by ArchCom  





Edge Automation, (Ramki to inform)



ONAP 3rd Party Operational Domain Manager

Status: Architectureal Direction approved for current direction.  Note: Not full functionality in Frankfurt.  One open issue to resolve as to whether the external service needs to be wrapped in an ONAP service to have consistent orchestation approach (or not).


Service Resolver:

Status: Not Archcom Approved ()


Model Driven ONAP

Status: Not yet ArchCom approved ()


Orchestration of Container Based VNFs (Srini)

???

Applications on ONAP

Status: Not yet ArchCom approved ()


API-GW

Status: Closed - there will not be a proposal for frankfurt timeframe


RunTime DB

Status: direction approved, some more work to be done on project aspects (not an archcom issues) and flows:

CONFIGURATION PERSISTENCE SERVICE R6


 5G / ORAN & 3GPP Standards Harmonization

Status:ArchCom Approved


ONAP CLI for VNF

Status: Note yet Archcom approved


Slicing Evolution



Multidomain Optical Service

Status: Archcom approved

Integrate Acumos with DCAE

Status: not ArchCom approved


Self Service Control Loop


xNF licencing.

Status: principles archcom approved.


Misc:



Notes: to be removed at the end.


The full list of the Epics are included here. This is to identify if there is a missing Epic above.


Stories All stories and sub-tasks.