...
Architectural Deployment Scenarios to consider:
Management Workloads
Deployment Model | Edge using certain ONAP management workload functions as an Offload | |
| Description | Architecture Near-term Priority | |
Edge and Central Provider are same |
| Priority - ? Rationale:
Note: Analytics is currently addressed by a Distributed DCAE Orchestrator based on Cloudify. Participant Operator Priority
|
Edge and Central Providers are different |
| Same as above. |
Managed Workloads
- Managed workload instantiation is always started by ONAP Central components
- If "Edge using certain ONAP management workload functions as an Offload" as described in the previous table, the corresponding workload LCM functions will be taken care of by offloaded ONAP management components
- If "Edge using certain ONAP management workload functions as an Offload" as described in the previous table, the corresponding workload LCM functions will be taken care of by offloaded ONAP management components
...
Management application: Can be ONAP component or equivalent component from third parties
| Category | Requirement Item | Priority | Added by | Modified by and modification | Mapping to requirements from DCAE team |
|---|---|---|---|---|---|
| Onboarding | Ability to onboard management applications, that are to be deployed in cloud-regions, in ONAP-Central. Shall not have any expectations that all management applications are onboarded as a single bundle. | high | Allow new MS/applications/components to be onboarded independently | ||
| Onboarding | Ability to compose multiple management applications to be part of one management bundle and defining the dependency graph of applications belonging to a bundle | high | Allow Service assurance flow composition and deployment of individual or group of component | ||
| Instantiation | Ability to deploy management applications in selected cloud regions that are owned by ONAP operator | high | Allow Service assurance flow composition and deployment of individual or group of component | ||
| Instantiation | Ability to deploy management applications that are ephemeral (example: Analytics applications) | high | Allow Service assurance flow composition and deployment of individual or group of component | ||
| Instantiation | Ability to deploy management applications in selected cloud regions that are not owned by ONAP operator, but has business relationship (Examples: Public Clouds or Edge Clouds owned by some other organization) | low | |||
| Instantiation | Support for deploying management applications independent of each other when there are no dependencies (no expectation that all management applications are brought up together). | high | Allow Service assurance flow composition and deployment of individual or group of component | ||
| Instantiation | Ability to deploy few management applications based on VNF instantiations and bring down when VNF is terminated | high | Dynamic deployment of MS based on xNF instantiation | ||
| Instantiation | Ability to apply configuration (Day0 configuration) of management applications at the time of deployment | high | |||
| Instantiation | Support for various Day0 configuration profiles (e.g. different profiles for different cloud regions w/ differing capabilities) | high | |||
| Instantiation | Support for placement of management applications based on platform features (example: GPU, FPGA etc...) | high | |||
| Instantiation | Support for consistent Day0 configuration mechanisms | high | Vijay Venkatesh Kumar | ||
| Run time | Support for Day 2 configuration of single or multiple instances of management applications in various cloud regions | high | |||
| Run time | Support for management applications depending on other management applications - Support for configuration (Day2 configuration) of provider services when the consuming service is being instantiated and removal of the configuration on provider services when consuming service is terminated (Example: When analytics applications are brought up, analytics/collection framework need to be updated with additional configuration such as DB table, Kafka topic etc..) | high | Dynamic topics provisioning and role assignment for MS | ||
| Run time | Support for Day 2 configuration (add/delete) of appropriate management applications upon VNF instantiation/termination (Example: configuration of analytics & collection services when VNFs are brought up and removing the added configuration upon VNF termination) | high | Dynamic reconfiguration of MS based on xNF instantiations | ||
| Run time | Support for consistent Day 2 configurations across management components | high | |||
| Run time | Secure connectivity between central ONAP and management applications in cloud regions | high | |||
| Run time | Support for various connectivity protocols (Kafka, HTTP 1.1, 2.0, GRPC, Netconf etc...) between ONAP-Central and management components in cloud regions | high | |||
| Run time | Monitoring and visualization of management applications of cloud-regions along with ONAP components at the ONAP-Central | high | Complete view of MS and relation maintained at single/multisite K8S scenarios Healthcheck of all deployment component to be available for CLAMP/external system | ||
| Run time | Scale-out of management application components at the cloud-regions & traffic (transaction) distribution | high | |||
| Run time | Ability to upgrade management application components without loss of functionality | low | |||
| Run time | High availability of management applications in the cloud regions | high | |||
| Miscellaneous | Support for third party management applications that provide similar functionality as ONAP management applications (Modularity) | high | |||
| Miscellaneous | Support management applications as containers | high | @Srinivasa Addepalli | ||
| Miscellaneous | Support management applications as VMs | low |
Assumptions
| Item | Added by | Modified by | |
|---|---|---|---|
| ONAP Management components can only be brought up in cloud-regions that are based on Kubernetes | |||
Definition of done:
- This activity is closed when there is a:
- Description of alternative concepts for distributing the ONAP functionality.
- A recommendation for which alternatives to pursue (and when).
...