...
| Requirement Item | Priority | Added by | Modified by and modification | Mapping to requirements from DCAE team |
|---|---|---|---|---|
| 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 | ||
| 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 | ||
| Ability to deploy management applications in selected cloud regions that are owned by ONAP operator | high | Srinivasa Addepalli | Allow Service assurance flow composition and deployment of individual or group of component | |
| 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 | ||
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) | mediumlow | Srinivasa Addepalli | ||
| 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 | ||
| 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 | ||
| Ability to apply configuration (Day0 configuration) of management applications at the time of deployment | high | |||
| Support for various Day0 configuration profiles | high | |||
| Support for Day 2 configuration of single or multiple instances of management applications in various cloud regions | high | Srinivasa Addepalli | ||
| 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 | Srinivasa Addepalli | Dynamic topics provisioning and role assignment for MS | |
| 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 | Srinivasa Addepalli | Dynamic reconfiguration of MS based on xNF instantiations | |
| Secure connectivity between central ONAP and management applications in cloud regions | high | |||
| Support for various connectivity protocols (Kafka, HTTP 1.1, 2.0, GRPC etc...) between ONAP-Central and management components in cloud regions | high | |||
| 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 | ||
| Scale-out of management application components at the cloud-regions & traffic (transaction) distribution | high | |||
| Ability to upgrade management application components without loss of functionality | low | |||
| High availability of management applications in the cloud regions | high | |||
| Support for third party management applications that provide similar functionality as ONAP management applications (Modularity) | high | |||
| Support management applications as containers | high | @Srinivasa Addepalli | ||
| Support management applications as VMs | low |
...
Deploy-ment Model | Non-ONAP Central | ONAP Central | Edge using certain ONAP management workload functions as an Offload NoteClarification Notes: In this case, ONAP central is interfacing with edge directly using Multi-Cloud APIs for workload deploymenttheir is no hierarchical orchestration. | Edge using ONAP Orchestration NoteClarification Notes: In this case, their is a two (or more) level orchestration hierarchy when ONAP Central is interfacing with ONAP Edge Orchestrator using SO style APIs for workload deployment. | Edge *not* using ONAP Orchestration NoteClarification Notes: This assumes at least a two level hierarchy for orchestration - ONAP Central Orchestrator and 3rd party Edge Orchestrator. This is specific to Service (VNF/App) Orchestration and *not* Cloud infrastructure orchestration. Interfacing to cloud infrastructure is already covered through ONAP multi-cloud. | ||||||
| Description | Architecture Near-term Priority for VNFs | Architecture Near-term Priority for Apps | Description | Architecture Near-term Priority for VNF Orchestration | Architecture Near-term Priority for App Orchestration | Description | Architecture Near-term Priority for VNF Orchestration | Architecture Near-term Priority for App Orchestration | |||
Edge and Central Provider are same | NA | Yes for all cases |
| Priority - High? Rationale:
Note: Analytics is currently addressed by a Distributed DCAE orchestrator based on Cloudify Participant Operator Priority
| Priority - Medium? Rationale:
Participant Operator Priority
|
| Priority - Medium? Rationale:
Participant Operator Priority
| Priority - Medium? Rationale:
Participant Operator Priority
|
| Priority - Medium? Rationale:
Participant Operator Priority
| Priority - Medium? Rationale:
Participant Operator Priority
|
Edge and Central Providers are different | NA | Yes for all cases | Use Existing VPCs (VPC creation out of scope for ONAP)
| Priority - High? Rationale:
Participant Operator Priority
| Priority - Medium? Rationale:
Participant Operator Priority
| Use Existing VPCs (VPC creation out of scope for ONAP)
| Priority - Medium? Rationale:
Participant Operator Priority
| Priority - Medium? Rationale:
Participant Operator Priority
| Use Existing VPCs (VPC creation out of scope for ONAP)
| Priority - Medium? Rationale:
Participant Operator Priority
| Priority - Medium? Rationale:
Participant Operator Priority
|
...