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

Compare with Current View Page History

« Previous Version 6 Next »

Project Name:

  • Proposed name for the project: VIM for Cloud Providers
  • Proposed name for the repository: 
    • MultiVIM

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.

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 VoLTE or vCPE, enable single VIM provider across multi-site 
    • Stretch goal
      • For VoLTE 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 MultiVIM 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

  • How does this align with external standards/specifications?
    • Support existed functions
    • Information/data models
    • Compliant with ETSI NFV architecture framework
  • Are there dependencies with other open source projects?

Resources:

  • Primary Contact Person:  Xinhui Li, VMware;  Bin Yang, Wind River
  • Initial Committers:
    • Andrew Philip, Microsoft
    • Bin Yang, Wind River
    • Xinhui Li, VMware
    • Anbing Zhang, China Mobile
  • Contributors
    • Isaku Yanahata, Intel
    • Matti Hiltunen, AT&T
    • Ethan Lynn, VMware

Other Information:

  • link to seed code (if applicable)
  • Vendor Neutral
    • if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
  • Meets Board policy (including IPR)

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

Key Project Facts

Project Name:

  • JIRA project name:
  • JIRA project prefix:

Repo name:
Lifecycle State:
Primary Contact:
Project Lead:
mailing list tag [Should match Jira Project Prefix] 
*Link to TSC approval: 
Link to approval of additional submitters:


  • No labels