Leverage existing capabilities, and select what; or motivate new approaches
Management Workload:
- Align on a single orchestrator solution for all management workloads
Managed Workload:
- Enhance SDC, SO, A&AI, MC etc. to support containerized functions
- Leverage ONAP for deploying and managing non-network functions
Longer-term:
- Explore feasibility for orchestration alignment between managed workload and management workload
Cloud-Native-foundation:
- Leverage K8S (Operators, Custom Resource Definitions etc.) for Distributed Systems Management
  - Image management – at scale rolling upgrade
  - Policy/Configuration change – notify only deltas
- Leverage Istio Service Mesh (Distributed Tracing etc.) for Component Performance Management

Distributed Management application Requirements / Considerations

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		Srinivasa Addepalli
Support for various Day0 configuration profiles		Srinivasa Addepalli
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		Srinivasa Addepalli
Support for various connectivity protocols (Kafka, HTTP 1.1, 2.0, GRPC etc...) between ONAP-Central and ONAP components in cloud regions		Srinivasa Addepalli
Monitoring and visualization of ONAP components of cloud-regions along with ONAP components at the ONAP-Central		Srinivasa Addepalli
Scale-out of ONAP components at the cloud-regions		Srinivasa Addepalli
Ability to upgrade ONAP components without loss of functionality		Srinivasa Addepalli
High availability of ONAP component in the cloud regions		Srinivasa Addepalli

Architectural Scenarios to consider:

ONAP components can run in Central and/or Edge Clouds

Scenario 1: 1) Different services providers for Central Cloud & Edge Clouds

Scenario 2) : Single service provider for for Central Cloud & Edge Clouds

Bring up for VIM each Preparatory Steps – Edge Cloud Bring up & Connectivity - Out of Scope scope for ONAPPreparatory Steps – Edge Cloud Bring up

...

& Connectivity

Communication between Central Cloud, where ONAP Central runs on K8S, and Edge Cloud

Setup a private VPN - In scope for ONAP
- for management network connectivity, any networking

Private connectivity to Edge Cloud may already be available; If not, setup a private VPN

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).

...