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 WiFi management #3

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

NBI part for WiFi management #3

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

@papagap papagap added this to the First Release Roadmap milestone Dec 7, 2018
@sechkova
Copy link

sechkova commented Jan 10, 2019

The WiFi related API should be able to abstract both the SDN-WiFI AP (work of i2CAT) as well as the Ruckus WiFi (Bristol).

Initial steps:

  • Study the sdn_wifi_access_point client NBI from slice manager (link into the comments above)

The API already exists, check with i2CAT for potential updates

  • Study the Ruckus API

UniBristol is the only source of information here.

  • Based on the collected information design the new API capable of abstracting both components

@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