Polling for port status is the easiest solution. In some cases excessive polling does not scale very well. For instance in large cloud with 1000s of compute nodes, this will put a bit of a strain on the neutron server.
This why Aaron a while ago implemented [1] for interfacing neutron with nova. Basically in this way nova won't have to poll for neutron's port status - it will receive events for vif plugged and unplugged over a RESTful interface. I'm not sure if this is feasible or not, but perhaps you could think about listening for those events on your container manager. Salvatore [1] http://git.openstack.org/cgit/openstack/neutron/tree/neutron/notifiers/nova.py On 22 April 2015 at 15:10, Gurucharan Shetty <shet...@nicira.com> wrote: > > > > I was expecting that once the port status made it up to Neutron from > > OVN, that we would update the port state in the Neutron db, as well. > > That would be reflected in the neutron API for getting the port details > > that you reference. > Yes, that would work. > > > > > -- > > Russell Bryant > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
