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

Compare with Current View Page History

« Previous Version 70 Next »

Project Name:

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

Project description:

  • 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 (e.g., openstack.org, Wind River, etc...), public and private clouds (e.g., VMware, Azure), 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 and minimize the impact to the deployed ONAP while upgrading the underlying cloud infrastructures.

Scope:

  1. A plugable and extensible framework that
    1. provides a Mediation Layer which includes
      1. A common northbound interface (NBI) / Multi-Cloud APIs
      2. A common abstraction model
      3. The ability to handle differences in models
    2. generates or extends NBI based on the functional model of underlying infrastructure
    3. allows Infrastructure Controller to register with capacity info & capabilities (for supporting EPA), discover and choose one or more VIM(s) to use
    4. allows global SDN Controller to choose and work with multiple local SDN Controller backends
    5. implements adapters for different providers.
  2. Across the project the implementation of any differentiated functionalities will be done in a way where ONAP users can decide if to use or not to use those functionalities.
  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. Should align with the Common Controller Framework to enable reuse by different ONAP elements.

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
    • Implementation of the adapters for VMware, OpenStack (Wind River), and Microsoft Azure.
    • Demo use case within a single site, supported by any single cloud provider.
    • For vVoLTE or vCPE, enable single cloud provider across multi-site
  • Stretch goal
    • For vVoLTE or vCPE, enable mix of different cloud 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, APP-C/VNF-C, Modeling, and will act as the single access point to be called by these components for accessing the cloud and virtual infrastructure. Furthermore, it will align with SDN-C component for both intra DC connectivity as well as inter-DC connectivity. Thus it is also the single access point for SDN-C to work with other local SDN Controllers. 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).



  • What other ONAP projects does this project depend on?

Common Services, AAI, Modeling, SDC, SO, APP-C/VNF-C, DCAE, SDN-C

  • How does this align with external standards/specifications?
    • Support existed functions
    • Information/data models by ONAP modeling project
    • Compliant with ETSI NFV architecture framework
      • VIM, NFVI, Nf-Vi, Vi-Vnfm, and Or-Vi
  • Are there dependencies with other open source projects?

    • Cassandra, OpenStack java sdk, AWS Java sdk, Azure and Bare metal.

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-multicloud

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:


Save

  • No labels