...
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).
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
...