| 2019-11-07 05:43:44 |
YAMAMOTO Takashi |
description |
network-vif-plugged and friends are not well documented.
the timing when those events are sent varies among drivers.
inter-project api like this should be defined and documented super-clearly.
the behaviour isn't consistent even within reference implementations.
nova folks call them bind-time events vs plug-time events.
https://review.opendev.org/#/c/667177/
networking-midonet always make compute ports ACTIVE. (create-time events?)
https://github.com/openstack/networking-midonet/blob/stable/stein/midonet/neutron/ml2/mech_driver.py#L178
it stopped working recently.
https://bugs.launchpad.net/networking-midonet/+bug/1839169
networking-ovn has a relevant dirty hack.
https://review.opendev.org/#/c/673803/
it has a nice bug description.
https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1834045
references:
https://wiki.openstack.org/wiki/Nova/ExternalEventAPI |
network-vif-plugged and friends are not well documented.
the timing when those events are sent varies among drivers.
inter-project api like this should be defined and documented super-clearly.
the behaviour isn't consistent even within reference implementations.
nova folks call them bind-time events vs plug-time events.
https://review.opendev.org/#/c/667177/
networking-midonet always make compute ports ACTIVE. (say, create-time events?)
https://github.com/openstack/networking-midonet/blob/stable/stein/midonet/neutron/ml2/mech_driver.py#L178
it stopped working recently after a nova change.
https://bugs.launchpad.net/networking-midonet/+bug/1839169
networking-ovn has a relevant dirty hack.
https://review.opendev.org/#/c/673803/
it has a nice bug description.
https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1834045
references:
https://wiki.openstack.org/wiki/Nova/ExternalEventAPI |
|
