ONAP Frankfurt Release Architecture Requirements

The Architecture Requirements are finally captured in the ONAP Achitecture Project in Jira, Grouped by Epics, Stories;

• 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.

ONAPARC-403

ONAPARC-403 - Getting issue details... STATUS

Other topics (EPICs to be created)

• Controller Evolution towards combined GNFC: https://wiki.onap.org/download/attachments/53248195/Controller%20EvolutionElAlto04012019.pptx?version=2&modificationDate=1554220494764&api=v2 
• Controller Evolution - Self Service API to support LCM actions (Oskar)
  • Note: EPIC exists, will include.

    INT-1131,

    LCM API is SO-2070

    
    

• Edge Automation, (Ramki to inform)
• ONAP 3rd party op manager (telstra proposal)?,
• service resolver(rene/seshu)?

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.