Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NBI part for VIM core entities management #1

Open
papagap opened this issue Dec 7, 2018 · 1 comment
Open

NBI part for VIM core entities management #1

papagap opened this issue Dec 7, 2018 · 1 comment
Assignees

Comments

@papagap
Copy link
Contributor

papagap commented Dec 7, 2018

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

@sechkova
Copy link

sechkova commented Jan 10, 2019

Inital steps:

  • 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
  • Extend the API with the output of issue NBI part for Dashboard-related VIM info #2

@sechkova sechkova assigned Charlemagne2017 and unassigned sraho and sechkova Jan 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants