ONAP Frankfurt Release Architecture Requirements

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

• Label with stories with the projects that are impacted and include a description of that impact

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

Orchestration Scenarios: ONAPARC-403

REQ-101 - Getting issue details... STATUS

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   ONAPARC-234 - Getting issue details... STATUS

REQ-92 - Getting issue details... STATUS

INT-1131 - Getting issue details... STATUS

SO-2070 - Getting issue details... STATUS

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). ONAPARC-509 - Getting issue details... STATUS

REQ-17 - Getting issue details... STATUS

Service Resolver:

Status: Not Archcom Approved ( ONAPARC-507 - Getting issue details... STATUS )

REQ-13 - Getting issue details... STATUS

Model Driven ONAP

Status: Not yet ArchCom approved ( ONAPARC-436 - Getting issue details... STATUS )

Orchestration of Container Based VNFs (Srini)

???

Applications on ONAP

Status: Not yet ArchCom approved ( ONAPARC-500 - Getting issue details... STATUS )

API-GW

Status: Not Yet AchCom approved ONAPARC-494 - Getting issue details... STATUS

RunTime DB

Status: not yet approved: ONAPARC-514 - Getting issue details... STATUS

5G CONFIGURATION (RunTime DB)

 5G / ORAN & 3GPP Standards Harmonization

Status:ArchCom Approved ONAPARC-516 - Getting issue details... STATUS

REQ-38 - Getting issue details... STATUS

ONAP CLI for VNF

Status: Note yet Archcom approved

ONAPARC-478 - Getting issue details... STATUS

Slicing Evolution

REQ-60 - Getting issue details... STATUS REQ-158 - Getting issue details... STATUS REQ-159 - Getting issue details... STATUS

Multidomain Optical Service

Status: Not Archcom approved

REQ-37 - Getting issue details... STATUS

Integrate Acumos with DCAE

Status: not ArchCom approved

REQ-166 - Getting issue details... STATUS

Self Service Control Loop

REQ-9 - Getting issue details... STATUS

Misc:

• Orchestration of container based VNFs (Srini)?
• Service mesh (srini/mike)??
• ONAP CLI For VNF (NB) and architecture (also make sure Dan Timony joins)
• Service Resolver (Rene/Seshu)
• DBaaS (what has been done, what we should do next) - (Yuri, Mike, Joanne)?? (session at subcommittee mtg).
  • Centalized DB technologies for the ONAP platform applications to use.  DB is responsible for their own schema.

Notes: to be removed at the end.

• Assume that slicing is driven by the use case work as per in previous releases, and this will implicitly cover the needs for the alloted resource and hierarchal orchestration.

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.