Versions Compared

Old Version 34

changes.mady.by.user Bin Hu

Saved on

compared with

New Version 35

changes.mady.by.user Bin Hu

Saved on

Key

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

...

  • ONAP needs underlying virtualized infrastructure to deploy, run, and manage network services and VNFs. The service provider looks for flexibility in its choice of on-premise private cloud, public cloud, or hybrid cloud implementations, and related network backends. This project aims to enable ONAP to support multiple infrastructure environments, for example, OpenStack and its different distributions from various vendors, private clouds (e.g VMware), private cloud (e.g.Azure, Azure etc.), and micro services containers, etc.
  • ONAP needs to maintain platform backward compatibility with every new release. This project decouples the evolution of ONAP platform from the evolution of underlying cloud infrastructure to enable the deployed ONAP intact when upgrading the underlying cloud infrastructures.

...

  1. Add capability in infrastructure controller to allow for registration, discovery (or homing), and invocation of a VIM provider.
  2. A plugable and extensible framework that
    1. allows Infrastructure Controller to register, discover and choose one or more VIM(s) to use
    2. allows global SDN Controller to choose and work with multiple local SDN Controller backends
    3. enables multiple local SDN Controller backends to interoperate collaboratively and simultaneously
    4. implements adapters for different providers.
    In R1, we expect VMware VIO, OpenStack (Wind River), and Microsoft Azure.
  3. Close loop remediation — Monitoring API collection for multi-cloud resource metrics (utilization, availability, health, performance), potential integration with DCAE collectors
  4. SDC VNF template customization and/or optimization to establish close match to the underline capabilities of the infrastructure provider(s)

Deliverables of Release One:

Note: this section is for brainstorming and informational purpose, and subject to change during release planning stage

In R1, we target to support

  • Minimal
    • Demo use case within a single site, supported by any single VIM provider.
    • For vVoLTE or vCPE, enable single VIM provider across multi-site 
  • Stretch goal
    • Implementation of the adapters for VMware VIO, OpenStack (Wind River), and Microsoft Azure.
    • For vVoLTE or vCPE, enable mix of different VIM providers across multi-site

Architecture Alignment:

  • How does this project fit into the rest of the ONAP Architecture?

...