Open Stack

I agree with Dan -- I think it's important to test on newer versions as well, considering we will have people running on other versions besides Ubuntu LTS -- Fedora 20, for instance, is on 1.1.3.4.

Additionally, considering bugs get fixed and features get implemented in each version of libvirt, we need to ensure that we *can* test code that uses features present in later versions of libvirt.  0.9.8 came out over two years ago making it fairly old.  I think it's important to keep up-to-date on what versions we test with.

Best Regards,
Solly Ross

----- Original Message -----
From: "Daniel P. Berrange" <berrange at redhat.com>
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Sent: Tuesday, March 18, 2014 10:11:54 AM
Subject: Re: [openstack-dev] Updating libvirt in gate jobs

On Tue, Mar 18, 2014 at 07:50:15AM -0400, Davanum Srinivas wrote:
> Hi Team,
> 
> We have 2 choices
> 
> 1) Upgrade to libvirt 0.9.8+ (See [1] for details)
> 2) Enable UCA and upgrade to libvirt 1.2.2+ (see [2] for details)
> 
> For #1, we received a patched deb from @SergeHallyn/@JamesPage and ran
> tests on it in review https://review.openstack.org/#/c/79816/
> For #2, @SergeHallyn/@JamesPage have updated UCA
> ("precise-proposed/icehouse") repo and we ran tests on it in review
> https://review.openstack.org/#/c/74889/
> 
> For IceHouse, my recommendation is to request Ubuntu folks to push the
> patched 0.9.8+ version we validated to public repos, then we can can
> install/run gate jobs with that version. This is probably the smallest
> risk of the 2 choices.

If we've re-run the tests in that review enough times to be confident
we've had a chance of exercising the race conditions, then using the
patched 0.9.8 seems like a no-brainer. We know the current version in
ubuntu repos is broken for us, so the sooner we address that the better.

> As soon as Juno begins, we can switch 1.2.2+ on UCA and request Ubuntu
> folks to push the verified version where we can use it.

This basically re-raises the question of /what/ we should be testing in
the gate, which was discussed on this list a few weeks ago, and I'm not
clear that there was a definite decision in that thread

  http://lists.openstack.org/pipermail/openstack-dev/2014-February/027734.html

Testing the lowest vs highest is targetting two different scenarios

  - Testing the lowest version demonstrates that OpenStack has not
    broken its own code by introducing use of a new feature.

  - Testing the highest version demonstrates that OpenStack has not
    been broken by 3rd party code introducing a regression.

I think it is in scope for openstack to be targetting both of these
scenarios. For anything in-between though, it is upto the downstream
vendors to test their precise combination of versions. Currently though
our testing policy for non-python bits is "whatever version ubuntu ships",
which may be neither the lowest or highest versions, just some arbitrary
version they wish to support. So this discussion is currently more of a
'what ubuntu version should we test on' kind of decision

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev