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: Handle HTTP errors and exceptions when setting OVSDB address #7

Closed ecklm closed 4 years ago

ecklm commented 4 years ago

Some timing circumstances may cause the setting of OVSDB address to fail either by a legit HTTP response or simply closing the connection. As a result, the corresponding switch would not be available to operate on.

ecklm commented 4 years ago

Quite unsure, where it comes from...

127.0.0.1 - - [24/Apr/2020 07:58:51] "PUT /v1.0/conf/switches/0000000000000005/ovsdb_addr HTTP/1.1" 201 144 0.000328
(27913) accepted ('127.0.0.1', 49000)
127.0.0.1 - - [24/Apr/2020 07:58:51] "POST /qos/rules/0000000000000005 HTTP/1.1" 200 247 0.000760
(27913) accepted ('127.0.0.1', 49004)
127.0.0.1 - - [24/Apr/2020 07:58:51] "POST /qos/rules/0000000000000005 HTTP/1.1" 200 247 0.000733
(27913) accepted ('127.0.0.1', 49008)
127.0.0.1 - - [24/Apr/2020 07:58:51] "POST /qos/rules/0000000000000005 HTTP/1.1" 200 247 0.000709
(27913) accepted ('127.0.0.1', 49012)
127.0.0.1 - - [24/Apr/2020 07:58:51] "POST /qos/queue/0000000000000005 HTTP/1.1" 200 248 0.000328
200 - [
    {
        "command_result": {
            "details": "ovs_bridge is not exists",
            "result": "failure"
        },
        "switch_id": "0000000000000005"
    }
]
ecklm commented 4 years ago

It's most likely related to slow request processing, so that should be solved first.