Switch to ovslib
Bug #1489095 reported by
Armando Migliaccio
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-l2gw |
Fix Released
|
Critical
|
Ofer Ben-Yacov |
Bug Description
One L2GW implementation relies on hardware vtep schema and for that agents need to talk to OVSDB. At the time this was initially developed considerations were made in relation to what to use: the python ovsdb library or straight ovsdb over a tcp socket. The latter was chosen and rationale was documented in [1].
We should reassess whether these considerations are still valid, and if they are not, switch to the ovsdb library itself that will allow us to reduce the l2gw code footprint.
[1] https:/
[2] https:/
Changed in networking-l2gw: | |
assignee: | nobody → Ofer Ben-Yacov (ofer-benyacov) |
Changed in networking-l2gw: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
Changed in networking-l2gw: | |
status: | Confirmed → In Progress |
Changed in networking-l2gw: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Ofer, the missing piece (Manager table support) in Python ovs lib is blocking us from switching to Python OVS library.
Please let us know if you have any update.