Versions Compared

Old Version 86

changes.mady.by.user Bin Hu

Saved on

compared with

New Version Current

changes.mady.by.user Gil Hellmann

Saved on

Key

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

...

The scope of Multi-VIM/Cloud project is a plugable and extensible framework that

  1. provides a Multi-VIM/loud Cloud Mediation Layer which includes the following functional modules
    1. Provider Registry to register infrastructure site/location/region and their attributes and capabilities in A&AI
    2. Infra Resource to manage resource request (compute, storage and memory) from SO, DCAE, or other ONAP components, so as to get VM created and VNF instantiated at the right infrastructure
    3. SDN Overlay to configure overlay network via local SDN controllers for the corresponding cloud infrastructure
    4. VNF Resource LCM to perform VM lifecycle management as requested by VNFM (APP-C or VNF-C)
    5. FCAPS to report infrastructure resource metrics (utilization, availability, health, performance) to DCAE Collectors for Close Loop Remediation
  2. provides a common northbound interface (NBI) / Multi-Cloud APIs of the functional modules to be consumed by SO, SDN-C, APP-C, VF-C, DCAE etc.
  3. provides a common abstraction model
  4. provides the ability to
    1. handle differences in models
    2. generate or extend NBI based on the functional model of underlying infrastructure
    3. implement adapters for different providers.

...

The proposed Multi-VIM/Cloud Mediation Layer consists of five functional modules, which interacts with SO, SDN-C, APP-C, VF-C, DCAE and A&AI respectively. It will act as the single access point to be called by these components for accessing the cloud and virtual infrastructure. Furthermore, it will interact with SDN-C component to configure overlay network via local SDN controllers for both intra-DC connectivity and inter-DC connectivity of the corresponding cloud infrastructure. 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).

Image RemovedImage Added


  • Is there any overlapping overlap with other ONAP components or other Open Source projects?

    • There is no intentional or unintentional overlap with other ONAP components or other Open Source projects to the best of our knowledge

  • What other ONAP projects does this project depend on?

    • Consumers of Multi-VIM/Cloud – SO, SDN-C, APP-C, VF-C, DCAE

    • Producers for Multi-VIM/Cloud – DCAE, A&AI\

    • Dependencies – Modeling

    • Alignment of Reusable APIs – Common Controller Framework

    • Indirect Impact and Collaboration – SNIRO, SDC

  • 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:

...

Lifecycle State: incubation
Primary Contact: Danny Lin, VMware
Project Lead: To Be Elected
PTL: Bin Yang, Wind River
mailing list tag: multicloud

...

Contributors

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

...