...
The ones that are "agreed" in the architecture sub-committee are marked as: This is still to be decided.
Summary / Status
Requirement/UseCase/... | Status |
---|
Serivce Orchestration Scenarios Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key |
---|
|
|
ONAPARC403Reqs not yet LCM API Evolution
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key |
---|
|
|
REQ92 ArchCom approved |
LCM API Evolution Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key |
---|
|
|
ONAPARC234 << Edge Automation >> | Frankfurt scope ...? |
3rd Party Operational Domain Controller
| ArchCom approved Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key |
---|
|
|
REQ17 ArchCom 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). 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-509 |
---|
|
| Service Resolver
Jira Legacy |
---|
server | System Jira |
---|
columns | key |
Edge Automation | Distributed Management Task Force - not ArchCom approved - Scope for Franfurt - "Extend Central K8S to register Edge Clouds"
- Centrally manage k8s Edge Clouds (k8s-clusters)
- Use Custom Resource Definition as Registry
- Provide ability to extend CRD to contain metadata
-Location label -Edge type (ICN, AWS, Azure, etc.) -External IP -Namespaces, user for authorization
- Edge Cloud Naming
- Follow Cloud (AWS etc.) naming convention with additional operator name?
Questions: still to be answered: - how to determine the location
- Is it OK to use different services for the applications centrally and distributed. Which applications are taking these up.
|
3rd Party Operational Domain Controller 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- |
---|
|
|
13 Jira Legacy |
---|
server | System Jira |
---|
Not Yet Archcom approved
ArchCom 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). 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-509 |
---|
|
|
Model Driven ONAP << req >> | Not Yet Archcom approved |
Service Resolver 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-13 |
---|
|
| Not Yet Archcom approved 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-509 |
---|
|
|
Model Driven ONAP << req >> | Not Yet Archcom approved 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-436 |
---|
|
|
Orchestration of Contain Based VNFs <<>> | Frankfurt Release ?? |
Applications on ONAP <<?? >> | Not Yet Archcom approved 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-500 |
---|
|
|
API-GW <<>> | There will not be a proposal for Frankfurt. 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-494 |
---|
|
|
Runtime DB << >> | Status: need and concept OK 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 | ONAPARC-514 |
---|
|
|
5G / ORAN & 3GPP Standards Harmonization 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-38 |
---|
|
| Status: Archcom approved 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-516 |
---|
|
|
ONAP CLI for VNF <<??>> | Status: Note yet Archcom approved 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-478 |
---|
|
|
Slicing Evolution 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-60 |
---|
|
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-158 |
---|
|
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-159 |
---|
|
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-146 |
---|
|
| Not Archcom Approved |
Multidomain optical service 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-37 |
---|
|
| Archcom Approved 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-519 |
---|
|
|
Integrate Acumos with DCAE 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-166 |
---|
|
Self Service Control Loop 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-9 |
---|
|
| Archcom approved |
xNF licencing with ONAP | Archcom approved (principles) (licening server outside ONAP) 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-520 |
---|
|
|
ETSI catalogue as a common service | Archom approved. Part of ETSI-ONAP alignment requirements 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-523 |
---|
|
|
CDS support of K8S | Archcom approved 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-522 |
---|
|
|
Analytics (or VNF) at the edge using Akrono antaticis orchestrated by ONAP | Not Archcom approved 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-519 |
---|
|
|
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 | REQ-101 |
---|
|
Status: Archcom approved:
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-320 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution,labels |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = REQ-101 OR parent in ("REQ-101") or parent in linkedissues(REQ-101) |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
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
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-234 |
---|
|
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 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).
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- |
---|
|
...
Orchestration of Contain Based VNFs
<<>>
...
Applications on ONAP
<<?? >>
...
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key |
---|
|
...
API-GW
<<>>
...
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution,labels |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = REQ-17 OR parent in ("REQ-17") or parent in linkedissues(REQ-17) |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
...
Runtime DB
<< >>
...
Service Resolver:
Status: Not Archcom Approved (
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- |
---|
|
...
) 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- |
---|
|
...
Status: Note yet Archcom approved
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee |
---|
|
...
,reporter,priority,status,resolution,labels | maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = REQ-13 OR parent in ("REQ-13") or parent in linkedissues(REQ-13) |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
...
Orchestration Scenarios: ONAPARC-403Model Driven ONAP
Status: Not yet ArchCom approved (
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 | ONAPARC-436 |
---|
|
)
Orchestration of Container Based VNFs (Srini)
???
Applications on ONAP
Status: Not yet ArchCom approved (
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) ,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
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
)
API-GW
Status: Closed - there will not be a proposal for frankfurt timeframe
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-234494 |
---|
|
RunTime DB
Status: direction approved, some more work to be done on project aspects (not an archcom issues) and flows:
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 |
---|
key | ONAPARC-514 |
---|
|
CONFIGURATION PERSISTENCE SERVICE R6
5G / ORAN & 3GPP Standards Harmonization
Status:ArchCom Approved
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 |
---|
key | ONAPARC-516 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | INTREQ-113138 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution,labels |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = INTREQ-1131 OR parent in ("INT-1131") or parent in linkedissues(INT-1131) 38 OR parent in ("REQ-38") or parent in linkedissues(REQ-38) |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
ONAP CLI for VNF
Status: Note yet Archcom approved
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-478 |
---|
|
Slicing Evolution
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).
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 Operational Domain Manager
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | ONAPARCREQ-509158 |
---|
|
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-17159 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution,labels |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = REQ-17 60 OR parent in ("REQ-1760") or parent in linkedissues(REQ-17) |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
Service Resolver:
Status: Not Archcom Approved (
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution-60) |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 | key | ONAPARC-507 |
---|
|
) Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution,labels |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = REQ-158 OR parent in ("REQ-158") or parent in linkedissues(REQ-158) |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 | key | REQ-13 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution,labels |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = REQ-13 159 OR parent in ("REQ-13159") or parent in linkedissues(REQ-13159) |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
Model Driven ONAPMultidomain Optical Service
Status: Not yet ArchCom Archcom approved (
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-436 |
---|
|
)Orchestration of Container Based VNFs (Srini)
???
Applications on ONAP
Status: Not yet ArchCom approved (
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-37 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type |
---|
|
,created,updated,due,assignee,reporter,priority,status,resolution,created,updated,due,assignee,reporter,priority,status,resolution,labels | maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = REQ-37 OR parent in ("REQ-37") or parent in linkedissues(REQ-37) |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
key | ONAPARC-500 |
)API-GW
Status: Not Yet AchCom Integrate Acumos with DCAE
Status: not ArchCom approved
Status: not yet approved: 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-494 | RunTime DB
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-514 |
---|
5G CONFIGURATION (RunTime DB)
5G / ORAN & 3GPP Standards Harmonization
Status:Not yet ArchCom Approved,labels | maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = REQ-166 OR parent in ("REQ-166") or parent in linkedissues(REQ-166) |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
Self Service Control Loop
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | ONAPARCREQ-5169 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status |
---|
|
,resolution,resolution,labels | maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = REQ-9 OR parent in ("REQ-9") or parent in linkedissues(REQ-9) |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
key | REQ-38
xNF licencing.
Status: principles archcom approved.
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution,labels |
---|
maximumIssues | 20 |
---|
jqlQuery | "Epic Link" = REQ-38 OR parent in ("REQ-38") or parent in linkedissues(REQ-38) |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | ONAPARC-520 |
---|
|
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.
Runtime DB
Notes: to be removed at the end.
...