Re: [openstack-dev] [qa][requirements] CentOS libvirt versus newton/ocata libvirt-python
On 01/12/2018 02:53 PM, Matthew Thode wrote: First, about newton, it's dead (2017-10-11). Yeah, there were a few opt-outs, which is why I think devstack still runs it. Not worth a lot of effort. Next, about ocata, it looks like it can support newer libvirt, but just because a distro updated a library doesn't mean we have to update. IIRC, for ubuntu they use cloud-archives to get the right version of libvirt, does something like that exist for centos/redhat? Well cloud-archives is ports of more recent things backwards, whereas I think we're in a situation of having too recent libraries in the base platform. The CentOS 7.3 v 7.4 situation is a little more subtle than Trusty v Xenial, say, but fundamentally the same I guess. The answer may be "Ocata not supported on 7.4". p.s. I hope I'm understanding the python-libvirt compat story correctly. AIUI any newer python-binding release will build against older versions of libvirt. But an old version of python-libvirt may not build against a newer release of the C libraries? -i __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [qa][requirements] CentOS libvirt versus newton/ocata libvirt-python
On 18-01-12 12:42:49, Ian Wienand wrote: > Hi, > > So I guess since CentOS included libvirt 3.2 (7-1708, or around RHEL > 7.4), it's been incompatible with libvirt-python requirements of 2.1.0 > in newton [1] and 2.5.0 in ocata [2] (pike, at 3.5.0, works). > > Do we want to do anything about this? I can think of several options > > * bump the libvirt-python versions on older branches > > * Create an older centos image (can't imagine we have the person > bandwidth to maintain this) > > * Hack something in devstack (seems rather pointless to test > something so far outside deployments). > > * Turn off CentOS testing for old devstack branches > > None are particularly appealing... > > (I'm sorry if this has been discussed, I have great déjà vu about it, > maybe we were talking about it at summit or something). > I thought I remembered something about it, but couldn't find it in the archives. First, about newton, it's dead (2017-10-11). Next, about ocata, it looks like it can support newer libvirt, but just because a distro updated a library doesn't mean we have to update. IIRC, for ubuntu they use cloud-archives to get the right version of libvirt, does something like that exist for centos/redhat? -- Matthew Thode (prometheanfire) signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [qa][requirements] CentOS libvirt versus newton/ocata libvirt-python
Hi, So I guess since CentOS included libvirt 3.2 (7-1708, or around RHEL 7.4), it's been incompatible with libvirt-python requirements of 2.1.0 in newton [1] and 2.5.0 in ocata [2] (pike, at 3.5.0, works). Do we want to do anything about this? I can think of several options * bump the libvirt-python versions on older branches * Create an older centos image (can't imagine we have the person bandwidth to maintain this) * Hack something in devstack (seems rather pointless to test something so far outside deployments). * Turn off CentOS testing for old devstack branches None are particularly appealing... (I'm sorry if this has been discussed, I have great déjà vu about it, maybe we were talking about it at summit or something). -i [1] http://logs.openstack.org/48/531248/2/check/legacy-tempest-dsvm-neutron-full-centos-7/80fa903/logs/devstacklog.txt.gz#_2018-01-09_05_14_40_960 [2] http://logs.openstack.org/50/531250/2/check/legacy-tempest-dsvm-neutron-full-centos-7/1c711f5/logs/devstacklog.txt.gz#_2018-01-09_20_43_08_833 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
