You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Commit an API spec (using any file type or tool you want) for the NBI part of the Infrastructure Abstraction that manages the creation, deletion, manipulation of the basic VIM-related entities, namely users, computes, networks, and their chunks.
The idea is to study the OpenStack client of https://github.com/5GCity/5GCity-slice-manager/tree/master/src/clients and design an OpenStack-agnostic API on top of it, which will however be able to invoke all of its functions. For example, the terms "compute-chunk" and "network-chunk" shall be probably used instead of the terms "openstack-project" and "openstack-vlan", and the input parameters shall be sometimes enriched and sometimes hidden in order to make the NBI "multi-VIM-compatible".
The text was updated successfully, but these errors were encountered:
Determine the types of VIMs (and their NBI) that need to be abstracted
There are three VIMs in the 5GCity architecture: Core VIM (Vanilla OpenStack), Edge VIM (VOSYS - OpenStack extensions) and Extended Edge VIM (Fog05). The Core and the Edge VIM have the same OpenStack NBI. The Ext. Edge VIM communicates directly with the MEAO and is not under the hood of the Infrastruction Abstraction layer. At the current state of the project the only VIM interface that needs to be abstracted is the NBI of OpenStack.
Use D2.1, D2.2 and mostly D4.1 for a common source of terminology throughout the project (chunks, slices, users, etc.)
Based on the input of the steps above, starting from the existing openstack.py client (up to now part of slice manager, link above) design the VIM-related API
Commit an API spec (using any file type or tool you want) for the NBI part of the Infrastructure Abstraction that manages the creation, deletion, manipulation of the basic VIM-related entities, namely users, computes, networks, and their chunks.
The idea is to study the OpenStack client of https://github.com/5GCity/5GCity-slice-manager/tree/master/src/clients and design an OpenStack-agnostic API on top of it, which will however be able to invoke all of its functions. For example, the terms "compute-chunk" and "network-chunk" shall be probably used instead of the terms "openstack-project" and "openstack-vlan", and the input parameters shall be sometimes enriched and sometimes hidden in order to make the NBI "multi-VIM-compatible".
The text was updated successfully, but these errors were encountered: