<div dir="ltr"><div><div><div><div>Hi,<br></div>Newer Vdsm will work with older engine, so in your case, I don't see any reason not to update the Vdsm.<br><br></div>BTW, can you describe what do you mean by "a very customized cinder/ceph setup" ?<br><br></div>Thanks,<br></div>Fred<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Apr 29, 2018 at 3:55 PM, Matthias Leopold <span dir="ltr"><<a href="mailto:matthias.leopold@meduniwien.ac.at" target="_blank">matthias.leopold@meduniwien.ac.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
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.<br>
<br>
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!<br>
<br>
matthias<br>
<br>
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
</blockquote></div><br></div>