<div dir="ltr"><div>Glad to hear the news. Thanks, Daniel and Michael.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 3, 2016 at 5:19 PM, Daniel P. Berrange <span dir="ltr"><<a href="mailto:berrange@redhat.com" target="_blank">berrange@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mon, May 02, 2016 at 11:27:01AM +0800, ZhiQiang Fan wrote:<br>
> Hi Nova cores,<br>
><br>
> There is a spec[1] submitted to Telemetry project for Newton release,<br>
> mentioned that a new feature requires libvirt >= 1.3.4 , I'm not sure if<br>
> this will have bad impact to Nova service, so I open this thread and wait<br>
> for your opinions.<br>
><br>
> [1]: <a href="https://review.openstack.org/#/c/311655/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/311655/</a><br>
<br>
</span>Nova's policy is that we pick a minimum requires libvirt that everyone<br>
must have, this is shown in this table<br>
<br>
  <a href="https://wiki.openstack.org/wiki/LibvirtDistroSupportMatrix#Nova_release_min_version" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/LibvirtDistroSupportMatrix#Nova_release_min_version</a><br>
<br>
Nova will accept code changes which use features from a newer libvirt,<br>
as long as they don't cause breakage for people with older libvirt.<br>
Generally this means that we'll use newer libvirt features, only for<br>
features which are new to nova - we don't change existing Nova code<br>
to use new libvirt features, since that would cause regression.<br>
<br>
IOW, I don't see any problem with you using newer libvirt version,<br>
provided you gracefully fallback without error if run against the<br>
current min required libvirt Nova declares.<br>
<br>
Regards,<br>
Daniel<br>
<span class="HOEnZb"><font color="#888888">--<br>
|: <a href="http://berrange.com" rel="noreferrer" target="_blank">http://berrange.com</a>      -o-    <a href="http://www.flickr.com/photos/dberrange/" rel="noreferrer" target="_blank">http://www.flickr.com/photos/dberrange/</a> :|<br>
|: <a href="http://libvirt.org" rel="noreferrer" target="_blank">http://libvirt.org</a>              -o-             <a href="http://virt-manager.org" rel="noreferrer" target="_blank">http://virt-manager.org</a> :|<br>
|: <a href="http://autobuild.org" rel="noreferrer" target="_blank">http://autobuild.org</a>       -o-         <a href="http://search.cpan.org/~danberr/" rel="noreferrer" target="_blank">http://search.cpan.org/~danberr/</a> :|<br>
|: <a href="http://entangle-photo.org" rel="noreferrer" target="_blank">http://entangle-photo.org</a>       -o-       <a href="http://live.gnome.org/gtk-vnc" rel="noreferrer" target="_blank">http://live.gnome.org/gtk-vnc</a> :|<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>