...
| Requirement Item | Priority | Added by | Modified by and modification |
|---|---|---|---|
| Ability to deploy ONAP management applications in selected cloud regions that are owned by ONAP operator | Srinivasa Addepalli | ||
Ability to deploy ONAP 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) | Srinivasa Addepalli | ||
| Ability to apply common configuration (Day0 configuration) of ONAP components at the time of deployment | |||
| Support for various Day0 configuration profiles | |||
| Support for Day 2 configuration of single or multiple instances of ONAP components in various cloud regions | Srinivasa Addepalli | ||
| Secure connectivity between central ONAP and ONAP management applications in cloud regions | |||
| Support for various connectivity protocols (Kafka, HTTP 1.1, 2.0, GRPC etc...) between ONAP-Central and ONAP components in cloud regions | |||
| Monitoring and visualization of ONAP components of cloud-regions along with ONAP components at the ONAP-Central | |||
| Scale-out of ONAP components at the cloud-regions & traffic (transaction) distribution | |||
| Ability to upgrade ONAP components without loss of functionality | |||
| High availability of ONAP component in the cloud regions | |||
| Support for third party management applications that provide similar functionality as ONAP management applications (Modularity) |
Assumptions
| Item | Added by | Modified by | |
|---|---|---|---|
| ONAP Management components can only be brought up in cloud-regions that are based on Kubernetes | |||
Architectural Scenarios to consider:
...