...
The ones that are "agreed" in the architecture sub-committee are marked as: This is still to be decided.
Summary / Status
| Requirement/UseCase/... | Status | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Orchestration Scenarios
| Reqs not yet ArchCom approved | ||||||||||||||||||||
LCM API Evolution
| ArchCom approved
| ||||||||||||||||||||
| << Edge Automation >> | Frankfurt scope ...? | ||||||||||||||||||||
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 <<>> | Not Yet AchCom approved
| ||||||||||||||||||||
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
| ||||||||||||||||||||||||||||||
Slicing Evolution
| Not Archcom Approved | ||||||||||||||||||||||||||||||
Multidomain optical service
| Not Archcom Approved (no conceptual issue identified, only due diligence required for CCVPN alignent). | ||||||||||||||||||||||||||||||
Integrate Acumos with DCAE
Self Service Control Loop
|
| Archcom approved |
Orchestration Scenarios: ONAPARC-403
...