On Wed, Apr 22, 2015 at 8:28 AM, Russell Bryant <rbry...@redhat.com> wrote:
> On 04/22/2015 09:21 AM, Salvatore Orlando wrote: > > 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 > > I think it would be cool to be able to register your own port status > callback when you create a port. It would work similarly to the nova > notifier, but would call the custom callback instead of the nova API. > > We have a callback mechanism in Neutron now [1], Armando implemented it late in Kilo [2]. I've copied him here as well to loop him in. It seems reasonable that we could use this for what you want Russell. [1] http://git.openstack.org/cgit/openstack/neutron/tree/neutron/callbacks [2] http://git.openstack.org/cgit/openstack/neutron/commit/?id=ad6a3ef5f6eb783fe9a8a2d907908ec3a8cece97 -- > 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
