The Architecture Requirements are finally captured in the ONAP Achitecture Project in Jira, Grouped by Epics, StoriesSummarized 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
...
The ones that are "agreed" in the architecture sub-committee are marked as: This is still to be decided.
Orchestration Scenarios: ONAPARC-403
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | ONAPARC-403 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution,labels |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = "ONAP Architecture Committee" and labels in (ARC-REQ-FRANKFURT) AND "Epic Link" = ONAPARC-403 OR parent in ("ONAPARC-403") or parent in linkedissues(ONAPARC-281) |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
Other topics (EPICs to be created)
Controller Evolution:
Controller Evolution towards combined GNFC: https://wiki.onap.org/download/attachments/53248195/Controller%20EvolutionElAlto04012019.pptx?version=2&modificationDate=1554220494764&api=v2
...
INT-1131,
...
The approach has been approved by ArchCom
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-92 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution,labels |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | "Epic Link" = REQ-92 OR parent in ("REQ-92") or parent in linkedissues(REQ-92) |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | INT-1131 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution,labels |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | "Epic Link" = INT-1131 OR parent in ("INT-1131") or parent in linkedissues(INT-1131) |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SO-2070 |
|---|
|
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
...