5gcity/5gcity-infrastructure-abstraction

An abstraction layer for 5GCity that enables the support of different access network technologies

5gcity-infrastructure-abstraction's Issues

NBI part for VIM core entities management

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

NBI part for WiFi management

Commit an API spec (using any file type or tool you want) for the NBI part of the Infrastructure Abstraction that manages the basic WiFi-related entities, namely devices, interfaces, virtual APs, VLANs etc.

The idea is to study the sdn_wifi_access_point client under https://github.com/5GCity/5GCity-slice-manager/tree/master/src/clients and design a technology-agnostic API on top of it, which will however be able to invoke all of its functions. Beneath the agnostic API we will later have the mentioned client as well as the Ruckus WiFi client used by Bristol, so a look into the API of the latter will be necessary.

NBI part for Dashboard-related VIM info

Commit an API spec (using any file type or tool you want) for the NBI part of the Infrastructure Abstraction that is used to deliver VIM info required by the 5GCity Dashboard (and potentially others).

Examples are "quotas", "resource utilization info", and similar.
Coordinate with the Dashboard developers to make a list and then design the NBI spec (again in OpenStack-agnostic terms, though, of course probably OpenStack-inspired).

This should later lead to extensions of the OpenStack client (currently at https://github.com/5GCity/5GCity-slice-manager/tree/master/src/clients and later in the Infrastructure Abstraction component).

Integrate OSM WIM implementation in 5GCity

Define the steps for bringing the OSM WIM into the 5GCity project.
The OSM WIM is considered to be the NFVO-related part of the WAN Resource Manager.
The rest of the WAN Resource Management functionality is implemented here, inside the Infrastructure Abstraction repository.