You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 31 Next »

Project Name:

  • Proposed name for the project: Multi VIM/Cloud for Cloud Providers
  • Proposed name for the repository: multicloud

Project description:

  • ONAP needs underline virtual and cloud 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. This project aims to enable ONAP to support multiple infrastructure environments including OpenStack (across different distributions), VMware, Azure, and micro services containers.
  • 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.

Scope:

  1. Add capability in infrastructure controller to allow for registration, discovery (or homing), and invocation of a VIM provider.
  2. A plugable framework that 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)
  5. 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
      • 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?

            The proposed Multi VIM/Cloud layer will be added into the infrastructure controller. It has dependencies with SO, DCAE, A&AI, and will act as the single access point to be called by these components for accessing the cloud and virtual infrastructure. Furthermore, we expect to align with SDN-C component for both intra DC connectivity as well as inter-DC connectivity. Applications/VNFs can be homed to the different cloud providers through the standard ONAP methods. For automated homing (SNIRO), different cloud providers can register attributes that differentiate their cloud platforms (e.g., reliability, latency, other capabilities) in A&AI and application placement policies/constraints can request for these specific properties (e.g., reliability > 0.999).


  • How does this align with external standards/specifications?
    • Support existed functions
    • Information/data models by ONAP modeling project
    • Compliant with ETSI NFV architecture framework
      • This project aligns with ETSI NFV VIM and NFVi
  • Are there dependencies with other open source projects?

Resources:

Other Information:

  • link to seed code (if applicable)

OPEN-O

ECOMP

Use the above information to create a key project facts section on your project page

Key Project Facts

Project Name:

  • JIRA project name: multicloud
  • JIRA project prefix: multicloud

Repo name:

  • org.onap.multicloud/framework
  • org.onap.multicloud/openstack
  • org.onap.multicloud/vmware
  • org.onap.multicloud/azure

IRC: http://webchat.freenode.net/?channels=onap-multivim

Lifecycle State: incubation
Primary Contact: Danny Lin, VMware
Project Lead: To Be Elected
mailing list tag: multicloud

Committers:

Contributors

*Link to TSC approval: 
Link to approval of additional submitters:


  • No labels