ONAP Dublin Release Architecture Requirements (Copy)
- Chaker Al-Hakim
The Architecture Requirements are finally captured in the ONAP Achitecture Project in Jira, Grouped by Epics, Stories;
Lable 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.
The ones that are "agreed" in the architecture sub-committee are marked as: This is still to be decided.
ONAPARC-280
ONAPARC-280: Service Assurance with Big Data Analytics Open
ONAPARC-281
ONAPARC-281: Service Mesh - Using K8S and ISTIO as infrastructure for ONAPOpen
ONAPARC-282
ONAPARC-282: K8S Cloud region support - E2E integration with rest of ONAPOpen
ONAPARC-285
REQ-100: ETSI Alignment requirements for Frankfurt ReleaseDone
ONAPARC-301
ONAPARC-301: Modularity within ONAP componentsOpen
ONAPARC-309
REQ-110: Items of joint interest and alignment between architecture and modellingDone
ONAPARC-311
ONAPARC-311: Architectural support for 5G use casesOpen
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 |
|---|
Stories All stories and sub-tasks.