<div dir="ltr">Doesn't it make more sense for this major upgrade to be a simple new install of engine v4, and importing the existing SDs?</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 24, 2016 at 6:34 AM, Barak Korren <span dir="ltr"><<a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On 24 August 2016 at 12:32, Christophe TREFOIS <span dir="ltr"><<a href="mailto:christophe.trefois@uni.lu" target="_blank">christophe.trefois@uni.lu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
Really? That’s strange, as the engine should be backward compatible with previous versions no?
<div><br></div></div></blockquote><div> </div></span><div>Think about it like this - When an update comes out it gets pushed to the repos/channels. If you then go and provision a new host with some automated system like Foreman, you end up with the new VDSM. Also, since you can have a large amount of hosts, you may reasonably choose to use some automated system to keep them up to date. It is more reasonable to expect the engine machine to have a steadier/slower life cycle.<br></div></div><span class=""><br><br clear="all"><br>-- <br><div data-smartmail="gmail_signature"><div dir="ltr"><div><b>Barak Korren</b><br></div><div><a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a><br></div>RHEV-CI Team<br></div></div>
</span></div></div>
<br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>