Page History

Project Name:

• Proposed name for the project: Multi-VIM for Cloud Providers
• Proposed name for the repository:  
• MultiVIM
• multivim (suggestion to be decided)

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?

...

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

Resources:

• Primary Contact Person: 
  • Danny Lin, lind@vmware.com, VMware
  Initial Committers:
• Names, gerrit IDs, and company affiliations of the committers
  
  • Anbing Zhang, (need to add an e-mail), China Mobile
  • Andrew Philip, aphilip@microsoft.com, Microsoft
  • Bin Yang, bin.yang@windriver.com, Wind River
  • Kanagaraj Manickam (mkr1481), (need to add an e-mail), Huawei
  • Xinhui Li, lxinhui@vmware.com, VMware
• Anbing Zhang, China Mobile
• Kanagaraj Manickam (mkr1481), Huawei
• Names and affiliations of any other contributors
  • Ethan Lynn, (need to add an e-mail), VMware
  • Gil Hellmann, gil.hellmann@windriver.com, Wind River
  Contributors
  • Isaku Yanahata, isaku.yamahata@intel.com, Intel
  • Matti Hiltunen, (need to add an e-mail), AT&T
  • Ethan Lynn, VMware
  Gil Hellmann, Wind River
• Project Roles (include RACI chart, if applicable)

Other Information:

• link to seed code (if applicable)
  • seed code for MultiVIM framework: https://gerrit.open-o.org/r/multivimdriver-broker
  • seed code for OpenStack: https://gerrit.open-o.org/r/multivimdriver-openstack
  • seed code for VMware VIO: https://gerrit.open-o.org/r/multivimdriver-vmware-vio
• 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: multivim (suggestion to be decided)
• JIRA project prefix: multivim (suggestion to be decided)

Repo name:

• org.onap.multivim/framework (suggestion to be decided)
• org.onap.multivim/openstack (suggestion to be decided)
• org.onap.multivim/vmware-vio (suggestion to be decided)
• org.onap.multivim/azure (suggestion to be decided)

Lifecycle State: incubation
Primary Contact: Danny Lin, VMware
Project Lead: To Be Elected
mailing list tag [Should match Jira Project Prefix] multivim] (suggestion to be decided)

Committers:

• Anbing Zhang (need to replace with an e-mail)
• aphilip@microsoft.com
• bin.yang@windriver.com
• Kanagaraj Manickam (need to replace with an e-mail)
• lxinhui@vmware.com

Contributors

• Ethan Lynn (need to replace with an e-mail)
• gil.hellmann@windriver.com
• isaku.yamahata@intel.com
• Matti Hiltunen (need to replace with an e-mail)

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

...