...
| Requirement | Operator Near-term (2019) vs Long-term (Beyond 2019) |
|---|---|
1.Consolidated view of deployed management component micro-services (in Central and other locations such as Edge) and their relationship for central Orchestrator | AT&T - near-term Bell Canada - long-term Orange - long-term Verizon- near-term |
2.For a given application configuration management mechanism is the same independent of location (Central and Edge), including dynamic configuration support | AT&T - near-term Bell Canada - long-term Orange - long-term Verizon- long-term |
| 3. In relation to No. 2, retain the capability to integrate with Central ONAP Policy and DMaap BusController (for secure topic/feed) | AT&T - near-term Bell Canada - long-term Orange - long-term Verizon - long-term |
4.Retain the ability to support TOSCA artifacts distributed from SDC and CLAMP. | AT&T - near-term Bell Canada - long-term Orange - long-term Verizon - long-term |
5.Design flow integration (SDC, DCAE-DS) and Standardized configuration modelling support by Central Orchestrator | AT&T - near-term Bell Canada - near-term Orange - near-term Verizon - near-term |
6.Dynamic Control Loop flow deployment and support through CLAMP/Policy Integration by Central Orchestrator | AT&T - near-term Bell Canada - long-term Orange - near-term Verizon - long-term |
7.Multi-tenant infrastructure management - Install relevant K8S clusters if they are not already present | AT&T - near-term Bell Canada - long-term Orange - NO. No the ONAP purposes according to us Verizon - near-term |
8.Support for non-K8S based workload deployment | AT&T - near-term Bell Canada - long-term Orange - long-term Verizon - near-term |
...