...
| Requirement/UseCase/... | Status | ||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Orchestration Scenarios
| Reqs not yet ArchCom approved |
| REQ
| 92 ArchCom approved
| |||||||||||||||||||||||||||||||||||||||||
LCM API Evolution
| |||||||||||||||||||||||||||||||||||||||||||||
| << Edge Automation >> | Frankfurt scope ...? | ||||||||||||||||||||||||||||||||||||||||||||
3rd Party Operational Domain Controller
| ArchCom approved 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).
ArchCom approved for current direction.
| ||||||||||||||||||||||||||||||||||||||||||||
| Edge Automation | Distributed Management Task Force - not ArchCom approved
Questions: still to be answered: | ||||||||||||||||||||||||||||||||||||||||||||
3rd Party Operational Domain Controller
| 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).
| ||||||||||||||||||||||||||||||||||||||||||||
Service Resolver
| Not Yet Archcom approved
| ||||||||||||||||||||||||||||||||||||||||||||
Model Driven ONAP << req >> | Not Yet Archcom approved
| ||||||||||||||||||||||||||||||||||||||||||||
Orchestration of Contain Based VNFs <<>> | Frankfurt Release ?? | ||||||||||||||||||||||||||||||||||||||||||||
Applications on ONAP <<?? >> | Not Yet Archcom approved
| ||||||||||||||||||||||||||||||||||||||||||||
API-GW <<>> | There will not be a proposal for Frankfurt.
| ||||||||||||||||||||||||||||||||||||||||||||
Runtime DB << >> | Status: need and concept OK by Archcom:
| ||||||||||||||||||||||||||||||||||||||||||||
5G / ORAN & 3GPP Standards Harmonization
| Status: Archcom approved
| ||||||||||||||||||||||||||||||||||||||||||||
ONAP CLI for VNF <<??>> | Status: Note yet Archcom approved
| Model Driven ONAP << req >> | Not Yet Archcom approved
| ||||||||||||||||||||||||||||||||||||||||||
Slicing Evolution
| |||||||||||||||||||||||||||||||||||||||||||||
Orchestration of Contain Based VNFs <<>> | Frankfurt Release ?? | ||||||||||||||||||||||||||||||||||||||||||||
Applications on ONAP <<?? >> | Not Yet Archcom approved
Not Yet AchCom approved
| API-GW <<>> |
| Runtime DB << >> |
| Not Archcom Approved | |||||||||||||||||||||||||||||||||||||||
Multidomain optical service
| Archcom Approved Status: Note yet Archcom approved
| ONAP CLI for VNF <<??>> |
| ||||||||||||||||||||||||||||||||||||||||||
Integrate Acumos with DCAE
Self Service Control Loop
| Archcom approved | ||||||||||||||||||||||||||||||||||||||||||||
| xNF licencing with ONAP | Archcom approved (principles) (licening server outside ONAP)
| ||||||||||||||||||||||||||||||||||||||||||||
| ETSI catalogue as a common service | Archom approved. Part of ETSI-ONAP alignment requirements Multidomain optical service
| Not Archcom Approved |
| ||||||||||||||||||||||||||||||||||||||||||
| CDS support of K8S | Archcom approved
| Not Archcom Approved (no conceptual issue identified, only due diligence required for CCVPN alignent). | |||||||||||||||||||||||||||||||||||||||||||
| Integrate Acumos with DCAEAnalytics (or VNF) at the edge using Akrono antaticis orchestrated by ONAP | Not Archcom approved
|
Orchestration Scenarios: ONAPARC-403
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
|
...
Orchestration Scenarios: ONAPARC-403Status: Archcom approved:
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
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 | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
Status: Not yet ArchCom approved (
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
API-GW
Status: Not Yet AchCom approved Closed - there will not be a proposal for frankfurt timeframe
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
RunTime DB
Status: not yet approveddirection approved, some more work to be done on project aspects (not an archcom issues) and flows:
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
5G CONFIGURATION (RunTime DB)CONFIGURATION PERSISTENCE SERVICE R6
5G / ORAN & 3GPP Standards Harmonization
...
Multidomain Optical Service
Status: Not Archcom approvedArchcom approved
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
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,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
xNF licencing.
Status: principles archcom approved.
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
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.
...