<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div>Hi,</div><div>Thank you for your reply.</div><div><br data-mce-bogus="1"></div><div>I have a short plan for the migration, but I have some question about it. Please correct me if something wrong.</div><div><br data-mce-bogus="1"></div><div>- I will install ovirt nodes to the new machines. </div><div>- I would like to use same storage, so i will make an new NFS export for the new ovirt-engine.</div><div>- I will make hosted engine setup that will placed on the new nfs share.</div><div>- I want to come some new features , like vlans and new IP range for engine, management, etc, so I will make these settings on the new setup</div><div>- This is the point where I will stop the whole old system. I have to stop VM-s, disconnect storge from old cluster and I will attach to the new cluster.</div><div>- This is the point, where I'm not sure in all things. If I had attach to the new cluster, the VM-s will show on the new ovirt-engine? What about the settings for example, memory, cpu, etc? It will be came from storage? Or I have to recreate these settings on every VM-s?</div><div>- Need I'm doing other things, or it will be enought to start vms in the new cluster?</div><div><br data-mce-bogus="1"></div><div>Thanks in advance.</div><div><br data-mce-bogus="1"></div><div>Regards,</div><div><br data-mce-bogus="1"></div><div>Tibor</div><div></div><div data-marker="__SIG_PRE__"><p></p></div><div><br><span id="zwchr" data-marker="__DIVIDER__">----- 2016. nov.. 15., 16:45, Yaniv Dary <ydary@redhat.com> írta:<br></span></div><div data-marker="__QUOTED_TEXT__"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div dir="ltr">Yes, this is possible, since import storage domain exists since oVirt 3.5.<div>Doing a test is always advised due.<br><div><div class="gmail_extra"><br clear="all"><div><div class="m_6833894296823500120gmail_signature"><div dir="ltr"><div><div dir="ltr"><pre><span style="font-family:arial,helvetica,sans-serif">Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : <a href="tel:%2B972%20%289%29%207692306" target="_blank">+972 (9) 7692306</a>
8272306
Email: <a href="mailto:ydary@redhat.com" target="_blank">ydary@redhat.com</a>
IRC : ydary</span></pre>
</div></div></div></div></div>
<br><div class="gmail_quote">On Tue, Nov 15, 2016 at 4:37 PM, Demeter Tibor <span dir="ltr"><<a href="mailto:tdemeter@itsmart.hu" target="_blank">tdemeter@itsmart.hu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:arial,helvetica,sans-serif;font-size:12pt;color:#000000"><div>Dear users,</div><br><div>We have an ovirt cluster with three nodes and centralized storage.(nfs based). The clusters based on centos6 os.</div><br><div>We bought some new server for more resources, but we want to upgrade to 4.0 . Is it possible to make brand new install and import all of VM-s from storage?</div><div>The storage will be remain, so I just wondering, I will make a clean install and connect the storage to this cluster. </div><div>Is it possible?</div><div><br>We don't have users, or special settings on this cluster, but I don't want to make the difficult upgrade process from 3.5 to 4.x and centos 6 to 7. </div><br><div>What is our possibilities? </div><br><div>Thank in advance,</div><br><div>Regards,</div><br><div>Tibor.</div><br><div><p></p></div></div></div><br>_______________________________________________<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/listinfo/users</a><br>
<br></blockquote></div></div></div></div></div><br></blockquote></div></div></body></html>