Open Stack

On Wed, May 21, 2014 at 6:21 AM, Assaf Muller <amuller at redhat.com> wrote:

> Dear Nova aficionados,
>
> Please make sure I understand this correctly:
> Each nova compute instance selects a single VM out of all of the VMs
> that it hosts, and every <heal_instance_info_cache_interval> seconds
> queries Neutron for all of its networking information, then updates
> Nova's DB.
>
> If the information above is correct, then I fail to see how that
> is in anyway useful. For example, for a compute node hosting 20 VMs,
> it would take 20 minutes to update the last one. Seems unacceptable
> to me.
>
> Considering Icehouse's Neutron to Nova notifications, my question
> is if we can change the default to 0 (Disable the feature), deprecate
> it, then delete it in the K cycle. Is there a good reason not to do this?
>

Based on the patch that introduced this function [0] you may be on to
something, but AFAIK unfortunately the neutron to nova notifications only
work in libvirt right now [1], so I don' think we can fully deprecate this
periodic task. That being said turning it off by default may be an option.
Have you tried disabling this feature and seeing what happens (in the gate
and/or in production)?


[0] https://review.openstack.org/#/c/4269/
[1] https://wiki.openstack.org/wiki/ReleaseNotes/Icehouse


>
>
> Assaf Muller, Cloud Networking Engineer
> Red Hat
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140527/277995bd/attachment.html>