On 02/10/2015 05:39 PM, Michael Burman wrote:
Hello Yaniv and all!
So i did this:
I tried to install clean rhel7.1 host with the right libvirt
version(libvirt-1.2.8-16.el7.x86_64,vdsm-4.17.0-394.gitb237397.el7.x86_64) and
failed to join this host under 3.6 cluster.
Host red-vds2.qa.lab.tlv.redhat.com is compatible with versions
(3.0,3.1,3.2,3.3,3.4,3.5) and cannot join Cluster mb3.6 which is set to version
3.6.
After failing i checked the /usr/share/vdsm/dsaversion.py and saw that:
version_info = {
'version_name': version_name,
'software_version': software_version,
'software_revision': software_revision,
'supportedENGINEs': ['3.0', '3.1', '3.2', '3.3', '3.4', '3.5'],
'supportedProtocols': ['2.2', '2.3'],
'clusterLevels': ['3.0', '3.1', '3.2', '3.3', '3.4', '3.5'],
So i added the 3.6 for cluster levels and engine support lines, restarted vdsm
and finally managed to join my rhel7.1 host to 3.6 Cluster.
All of this means that rhel7.1 hosts with vdsm 4.17.0 and libvirt version
-libvirt-1.2.8-16.el7.x86_64 are still not supported by default for 3.6
clusters and dsaversion.py file must be edited manually in order to join to
cluster 3.6.
I guess this must be changed.
of course it doesn't.. we still didn't merge
http://gerrit.ovirt.org/#/c/37384/ . but with libvirt >1.2.3 you are
able to hack dsaversion to report also 3.6 and use it.
we still struggling to define the approach to go with
http://gerrit.ovirt.org/#/c/37598/
one of those patches need to get in to allow adding any host to 3.6
cluster without additional hack
Best regards,
Michael B
----- Original Message -----
From: "Michael Burman" <[email protected]>
To: "ybronhei" <[email protected]>
Cc: [email protected], [email protected]
Sent: Monday, February 9, 2015 10:50:28 AM
Subject: Re: [ovirt-devel] Can't join vdsm(4.17.0-390.gita3163f3.el7.x86_64)
to Cluster 3.6
Thank you all!
Ok, so how can i get this right libvirt version for rhel7? not7.1 and without
any dependencies issues??
I want to join rhel7 host, with the right libvirt version to 3.6 cluster..is it
possible?
Michael B
----- Original Message -----
From: "ybronhei" <[email protected]>
To: "Oved Ourfali" <[email protected]>, "Sandro Bonazzola" <[email protected]>, "Dan
Kenigsberg" <[email protected]>
Cc: [email protected], [email protected], "Michael Burman" <[email protected]>
Sent: Monday, February 9, 2015 10:03:56 AM
Subject: Re: [ovirt-devel] Can't join vdsm(4.17.0-390.gita3163f3.el7.x86_64) to
Cluster 3.6
On 02/09/2015 08:35 AM, Oved Ourfali wrote:
On Feb 9, 2015 9:31 AM, Sandro Bonazzola <[email protected]> wrote:
Il 08/02/2015 16:15, Michael Burman ha scritto:
Hi everyone!
Is any one knows when it will be possible to join vdsm-4.17.0 to 3.6 Cluster??
I know that the libvirt version is not supported, but isn't should be? even if
it's rhel7..?
I changed the /usr/share/vdsm/dsaversion.py file to:
'supportedENGINEs': ['3.0', '3.1', '3.2', '3.3', '3.4', '3.5', '3.6'],
'supportedProtocols': ['2.2', '2.3'],
'clusterLevels': ['3.0', '3.1', '3.2', '3.3', '3.4', '3.5', '3.6'],
But caps.py is still:
if not hasattr(libvirt, 'VIR_MIGRATE_AUTO_CONVERGE'):
return _dropVersion('3.6',
'VIR_MIGRATE_AUTO_CONVERGE not found in libvirt,'
' support for clusterLevel >= 3.6 is disabled.'
' For Fedora 20 users, please consider upgrading'
' libvirt from the virt-preview repository')
if not hasattr(libvirt, 'VIR_MIGRATE_COMPRESSED'):
return _dropVersion('3.6',
'VIR_MIGRATE_COMPRESSED not found in libvirt,'
' support for clusterLevel >= 3.6 is disabled.'
' For Fedora 20 users, please consider upgrading'
' libvirt from the virt-preview repository')
libvirt is still disabled for 3.6 clusters...
I already tried to rebuild from fedora(with Sandro appreciated help), but had a
lot of issues dependencies.
I'm running on-
ovirt-engine-3.6.0-0.0.master.20150206122208.gitd429375.el6.noarch
vdsm-4.17.0-390.gita3163f3.el7.x86_64
libvirt-1.1.1-29.el7_0.7.x86_64
I would like to know if and when it will be possible to join rhel7
host(vdsm-4.17.0) to Cluster 3.6?
Moving to devel list, not really an infra issue.
Yaniv, you had a patch for that, but it was abandoned. Why?
because we don't need it- i explained there
the cluster check is only after the supportedVDSMVersion does not catch.
we failed to add the host to the cluster because the libvirt version .
as it is now, with the right versions, you should be able to add vdsm
4.17 to lastest engine regardless the cluster level
Best regards,
Michael B
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
_______________________________________________
Devel mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/devel
--
Yaniv Bronhaim.
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
