Page History

Deployment Model

Edge using certain ONAP management workload functions as an Offload

Note: In this context, Offload is the process of moving certain functions from central to edge locations to address various requirements such a WAN bandwidth constraint, higher resiliency, real-time service assurance etc.

Edge and Central Provider are same

• Allows ONAP Central Controller function to install ONAP SW components (purely ONAP mgmt. based or 3rd party integrated with ONAP mgmt.).
• This also supports ONAP specific K8S cluster installation.

Priority - ?High

Rationale:

• Analytics and closed loop offloads are key edge use cases.

Note: Analytics is currently addressed by a Distributed DCAE Orchestrator based on Cloudify.

Participant Operator Priority

• AT&T - High; To distribute DCAE services (Analytics, collectors etc.) and other ONAP components for resiliency.
• Verizon - Medium; Primarily distributed DCAE collectors and data mediation
• Vodafone - High; Distribute both DCAE and ONAP components

Edge and Central Providers are different

Note: In this case, Central provider is still managing the management functionality running at the edge, but using another operators infrastructure.

• Use Existing VPCs (VPC creation out of scope for ONAP)
• Rest - Same as above.

Note: A Virtual Private Cloud (VPC) provides a dedicated pool of compute/network/storage resources using a infrastructure as a service approach.Same as above.

Priority - Medium

Vodafone (question): should this model be at a lower priority? For a first phase it's sufficient to enable the case where edge and central providers are the same.

• Valid point - lowered priority to medium