Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Architectural Scenarios to consider:

ONAP components can run in Central and/or Edge Clouds

Scenario 1: Different services providers for Central & Edge Clouds

Scenario 2: Single service provider for Central & Edge Clouds 

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

...

Outcome of Edge Automation Discussions on 01/16/2019:


Non-ONAP Central

ONAP Central

Edge using ONAP Orchestration/Near-term Priority

Edge using non-ONAP Orchestration/Near-term Priority

Edge and Central Provider are same

Not Applicable

Yes for all combinations of edge

  • Allows ONAP Central to install their ONAP SW components (incl K8S cluster)
  • Support ONAP managed workloads on edge
High?
  • Can install ONAP SW components (incl K8S cluster) via other mechanisms

Medium?

Edge and Central Providers are different

Not Applicable

Yes for all combinations of edge

Use Existing VPCs (VPC creation out of scope for ONAP)

  • Allows ONAP Central to install their ONAP SW (incl K8S cluster)
  • Support ONAP managed workloads on edge
  • Can use Edge provider Services
High/Medium?

Use Existing VPCs (VPC creation out of scope for ONAP)

  • Can install their ONAP SW via other mechanisms
  • Can use Edge provider Services
Medium?

...

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

...

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

...