...
| Category | Requirement Item | Priority | Added by | Management Apps as traditional Apps/VNFs - Option 1 (Not considered as it is not satisfying the critical requirement of supporting existing Cloudify-TOSCA based management applications) | AT&T EOM Mapping (Option 2) | Cloud Native K8S Ecosystem (which includes current OOM helm charts ) Mapping (Option 3) | DCAE Analytics Mapping | |||
|---|---|---|---|---|---|---|---|---|---|---|
| Open source Current | Open source in progress (approx. timeline desired) | Open source Current | Open source in progress (approx. timeline desired) | Requirements | Current Implementation Status | |||||
| 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 | Yes (Using SDC. SDC allows to define it as VNF with multiple management applications as VNFCs. SDC allows multiple VNFs in a service and there could be multiple services) | Allow new MS/applications/components to be onboarded independently | Supported through DCAE, SDC*, Policy, CLAMP | |||||
| 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 | Yes (SDC now supports Helm, based description. It is possible to introduce dependency via initContainers and helm hooks) | Allow Service assurance flow composition and deployment of individual or group of component | Supported through DCAE, SDC*, CLAMP | |||||
| Onboarding | Shall have a way to specific licensing options for third party management applications (similar to VNF licensing) | high | Srinivasa Addepalli | Yes (SDC has a way to provide licensing information) | ||||||
| Instantiation | Ability to deploy management applications in selected cloud regions that are owned by ONAP operator | high | Partially (SO has ability to select the cloud-region while deploying the VNF. But there is no bulk deployment by selecting multiple cloud regions.It require enhancements. But we believe this requirement is needed for NFs too) | Allow Service assurance flow composition and deployment of individual or group of component | DCAE (WIP) | |||||
| Instantiation | Ability to deploy management applications that are ephemeral (example: Analytics applications) | high | Yes (Complete control at the SO. One can terminate the VNF/VFM at any time) | Allow Service assurance flow composition and deployment of individual or group of component | DCAE (Yes) | |||||
| 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 | Yes (Multi-Cloud has ability to deploy workloads in any cloud-region - whether owned by operators or even public clouds as long as right credentials are used) | DCAE (WIP) | ||||||
| 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 | Yes (SO provides API at various granularity) | Allow Service assurance flow composition and deployment of individual or group of component | DCAE (Yes) | |||||
| Instantiation | Ability to deploy few management applications based on VNF instantiations and bring down when VNF is terminated | high | Yes (SDC/SO with their bundling approaches - management app can be added as VFC in a VNF or as a VNF in a service) | Dynamic deployment of MS based on xNF instantiation | DCAE (Partial - can be manually triggered from CLAMP) | |||||
| Instantiation | Ability to apply configuration (Day0 configuration) of management applications at the time of deployment | high | Yes (SDC supports adding default Day0 configuration of workloads) | DCAE (Yes) | ||||||
| Instantiation | Support for various Day0 configuration profiles (e.g. different profiles for different cloud regions w/ differing capabilities) | high | Yes (SDC supports multiple Day0 profles - either through customization or as artifacts in case of K8S) | Supported through Policy/DCAE | ||||||
| Instantiation | Support for placement of management applications based on platform features (example: GPU, FPGA etc...) | high | Yes (SO can talk to OOF to get the right flavor for workloads in a VFM) | DCAE (No) | ||||||
| Instantiation | Support for consistent Day0 configuration mechanisms - should be the same path as Day 2. | high | Vijay Venkatesh Kumar | Yes (Work is going on in K8S plugin to ensure that Day 2 configuration is also supported as Helm charts as Day0 configuration. This is made possible due to microservices supporting K8S operators for their configurations) | DCAE(Yes) | |||||
| Run time | Support for Day 2 configuration of single or multiple instances of management applications in various cloud regions | high | Yes (APPC support for Day2 configuration. Also Day2 configuration support in K8S plugin - Ongoing. One can select cloud-region, instance while applying Day2 configuration) | DCAE (Yes) | ||||||
| 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 | Yes (In case of K8S world, as long as day2 configuration is also supported via K8S resources, it is possible. K8s Plugin does support this) | Dynamic topics(MR) and feeds(DR) provisioning and role assignment for MS | DCAE (Partial) | |||||
| 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 | WIP | Dynamic reconfiguration of MS based on xNF instantiations | DCAE (Functionality supported; but not currently exist in ONAP) | |||||
| Networking | Secure connectivity between central ONAP and management applications in cloud regions | high | Yes (Using SSL/TLS) | DCAE (Partial) and dependent on DMAAP | ||||||
| Networking | Support for various connectivity protocols (Kafka, HTTP 1.1, 2.0, GRPC, Netconf etc...) between ONAP-Central and management components in cloud regions | high | Yes (No restriction. it is based on management application) | DCAE (Partial) | ||||||
| Run time | Monitoring and visualization of management applications of cloud-regions along with ONAP components at the ONAP-Central | high | Partial (Same monitoring schemes as available for VNFs) | Complete view of MS and relation maintained at single/multisite K8S scenarios Healthcheck of all deployment component to be available for CLAMP/external system | DCAE (Yes) | |||||
| Run time | Scale-out of management application components at the cloud-regions & traffic (transaction) distribution | high | No (This work is slated for Release E) | DCAE (Yes relies on k8s) | ||||||
| Run time | Ability to upgrade management application components without loss of functionality | low | No (This work is slated for Release E) | DCAE (Yes; relies on k8s) | ||||||
| Run time | High availability of management applications in the cloud regions | high | Yes (It is part of K8S) | DCAE (Yes; relies on k8s) | ||||||
| Miscellaneous | Support for ONAP-compliant third party management applications that provide similar functionality as ONAP management applications.
| high | Yes (As long as third party management applications are described using Helm) | If complying to Onboarding requirements (#1)- DCAE (Y) | ||||||
| Miscellaneous | Support management applications as containers | high | @Srinivasa Addepalli | Yes (Using K8S plugin) | DCAE (Yes) | |||||
| Miscellaneous | Support management applications as VMs | low | Yes (Using K8S plugin) | DCAE (Yes) | ||||||
| Security | Security and privacy aspects of management applications (To be expanded) | high | It is generic requirement and to be taken care outside of this work item | |||||||
| Instantiation | Support for MS deployment not binded to any VNF/service; these are application which are service agnostic can be managed by dynamic configuration rule to support different usecases | Yes (If management application is not bound to any network function, this can be deployed as a separate VSP) | DCAE (yes) | |||||||
| Miscellaneous | Backward compatibility with existing application based on TOSCA | Critical | No | |||||||
| Miscellaneous | Single orchestrator for both managed (VNFs/Apps) and management applications that are to be deployed in cloud-regions | low (but highly preferred) | Srinivasa Addepalli | Yes | ||||||
...