search

ecklm / adaptive-network-slicing

Project holding the implementation and results of my thesis project at University of Trento, Italy
20 stars 5 forks source link

controller: Separate measurement scope from QoS setting scope #26

Closed ecklm closed 4 years ago

ecklm commented 4 years ago

As measurements are done per switch, adaptation time increases by the number of switches along different flows. It is because a switch only receives traffic let through by the previous switch, and therefore it does not have the same average values, it still needs to grow to be adapted as well.

If we say that controlling the network and not separate routes is enough, -- which I'd say is enough for the thesis -- the separation of measurements and configuration can offer a solution to this problem. Luckily, switch_id can be all in the API calls to the rest_qos application, so network-scope rule setting should be rather easy.

ryu/app/rest_qos.py:
47: # =============================
48: #          REST API
49: # =============================
50: #
51: #  Note: specify switch and vlan group, as follows.
52: #   {switch-id} : 'all' or switchID
53: #   {vlan-id}   : 'all' or vlanID

This could also decrase significantly the number of calls necessary to make modifications to the switches.

ecklm commented 4 years ago

Logging may keep the per-switch aproach as it helps pointing out the differences in the scopes and give another point to the "Future work" section.