Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

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.


Orchestration Scenarios: ONAPARC-403

ONAPARC-403 - Getting issue details... STATUS

key summary type created updated due assignee reporter priority status resolution labels
Refresh


Controller Evolution:

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

The approach has been approved by ArchCom

REQ-92 - Getting issue details... STATUS

key summary type created updated due assignee reporter priority status resolution labels
Refresh


INT-1131 - Getting issue details... STATUS

key summary type created updated due assignee reporter priority status resolution labels
Refresh



SO-2070 - Getting issue details... STATUS


Edge Automation, (Ramki to inform)

  • ONAP 3rd party op manager (telstra proposal)?,
  • service resolver(rene/seshu)?
  • model driven onap (ciaran)? (note: Also connect up to CDS work as a possible example))
  • Orchestration of container based VNFs (Srini)?
  • API-GW?? (PoC developed, demo in end oct)
  • Service mesh (srini/mike)??
  • ONAP CLI For VNF (NB) and architecture (also make sure Dan Timony joins)
  • Service Resolver (Rene/Seshu)
  • Applications on ONAP (Davide)
  • 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.
  • Runtime DB



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.

key summary type updated due assignee reporter priority status resolution issuelinks subtasks
Refresh


Stories All stories and sub-tasks.

key summary type created updated due assignee reporter priority status resolution issuelinks
Refresh

  • No labels