restricting release version when upgrading/installing Linux Enterprise hosts?
Hi, is it possible to restrict the oVirt version when installing or upgrading CentOS hypervisor hosts? let's say: 4.2.3 is already released, but i want to update/install certain hosts only to version 4.2.2 to have the same version in the whole cluster/data center. i know i could to this manually with yum and specifying rpm package versions but is there an "oVirt way"? or is this not necessary at all and newer hosts will always work smoothly with older engine and other hosts? still i think this is a topic that must be of interest to others. besides that: please excuse my impatience sometimes, my upgrade of our oVirt installation (4.1.9 to 4.2.2) worked perfectly, even with a very customized cinder/ceph setup. thanks a lot for this great software! matthias
Hi, Newer Vdsm will work with older engine, so in your case, I don't see any reason not to update the Vdsm. BTW, can you describe what do you mean by "a very customized cinder/ceph setup" ? Thanks, Fred On Sun, Apr 29, 2018 at 3:55 PM, Matthias Leopold < matthias.leopold@meduniwien.ac.at> wrote:
Hi,
is it possible to restrict the oVirt version when installing or upgrading CentOS hypervisor hosts? let's say: 4.2.3 is already released, but i want to update/install certain hosts only to version 4.2.2 to have the same version in the whole cluster/data center. i know i could to this manually with yum and specifying rpm package versions but is there an "oVirt way"? or is this not necessary at all and newer hosts will always work smoothly with older engine and other hosts? still i think this is a topic that must be of interest to others.
besides that: please excuse my impatience sometimes, my upgrade of our oVirt installation (4.1.9 to 4.2.2) worked perfectly, even with a very customized cinder/ceph setup. thanks a lot for this great software!
matthias
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Thanks! Maybe the cinder/ceph setup is not so "very" customized, but we are using a current librbd1 (12.2.x) instead of the version in CentOS 7. For this we had to switch from upstream Ceph RPMs (depending on lttng-ust/userspace-rcu from epel repo) to self-compiled Ceph RPMs (depending on lttng-ust/userspace-rcu from centos-ceph-luminous repo) on virtualization hosts when upgrading to oVirt 4.2. We have been using a Ceph 12.2.x cluster as storage with oVirt 4.1 (now 4.2) for quite some time with good results. Of course we would be happy to see further Cinder integration in oVirt ("Future Work?" on https://ovirt.org/develop/release-management/features/storage/cinder-integra...), but we understand that oVirt is focused on Gluster. matthias Am 2018-04-30 um 11:12 schrieb Fred Rolland:
Hi, Newer Vdsm will work with older engine, so in your case, I don't see any reason not to update the Vdsm.
BTW, can you describe what do you mean by "a very customized cinder/ceph setup" ?
Thanks, Fred
On Sun, Apr 29, 2018 at 3:55 PM, Matthias Leopold <matthias.leopold@meduniwien.ac.at <mailto:matthias.leopold@meduniwien.ac.at>> wrote:
Hi,
is it possible to restrict the oVirt version when installing or upgrading CentOS hypervisor hosts? let's say: 4.2.3 is already released, but i want to update/install certain hosts only to version 4.2.2 to have the same version in the whole cluster/data center. i know i could to this manually with yum and specifying rpm package versions but is there an "oVirt way"? or is this not necessary at all and newer hosts will always work smoothly with older engine and other hosts? still i think this is a topic that must be of interest to others.
besides that: please excuse my impatience sometimes, my upgrade of our oVirt installation (4.1.9 to 4.2.2) worked perfectly, even with a very customized cinder/ceph setup. thanks a lot for this great software!
matthias
_______________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>
-- Matthias Leopold IT Systems & Communications Medizinische Universität Wien Spitalgasse 23 / BT 88 /Ebene 00 A-1090 Wien Tel: +43 1 40160-21241 Fax: +43 1 40160-921200
participants (2)
-
Fred Rolland -
Matthias Leopold