<html><body style="font-family: Helvetica,Arial,sans-serif; font-size: 12px;">Export domains are to move VMs between oVirt environments. As already mentioned, you attach the export domain to one data center, export the vm, maint/detach, attach to different data center, attach and import (then maint/detach, etc.).<br><br>The language "export domains .... 'between' engines" is a bit confusing...<br><br><br><blockquote><br>----- Original Message -----<br><div id="origionalMessageFromField" style="width:100%;background:rgb(228,228,228);"><div style="font-weight:bold;">From:</div> "Christophe TREFOIS" <christophe.trefois@uni.lu></div><br><div id="origionalMessageToField" style="font-weight:bold;">To:</div>"Beckman Daniel" <Daniel.Beckman@ingramcontent.com>, "users" <users@ovirt.org><br><div id="origionalMessageSentField" style="font-weight:bold;">Cc:</div><br><div style="font-weight:bold;">Sent:</div>Mon, 14 Nov 2016 20:10:16 +0000<br><div id="origionalMessageSubjectField" style="font-weight:bold;">Subject:</div>Re: [ovirt-users] Move a VM between 2 setups<br><br><br><div class="WordSection1"><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us">Hi Daniel,</span></p><p></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us"></span></p><p> </p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us">Fantastic information. Thanks so much for this.</span></p><p></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us"></span></p><p> </p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us">I was already using export domains inside my current engine, but not sure if it would also work “between” engines so to speak.</span></p><p></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us"></span></p><p> </p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us">Have a great evening!</span></p><p></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us">Christophe</span></p><p></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us"></span></p><p> </p><div style="border:none;border-left:solid #0000FF 1.5pt;padding:0cm 0cm 0cm 4pt;"><div><div style="border:none;border-top:solid #E1E1E1 1pt;padding:3pt 0cm 0cm 0cm;"><p class="MsoNormal"><b><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us">From:</span></b><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us"> Beckman, Daniel [mailto:Daniel.Beckman@ingramcontent.com] <br><b>Sent:</b> lundi 14 novembre 2016 20:43<br><b>To:</b> Christophe TREFOIS <christophe.trefois@uni.lu>; users <users@ovirt.org><br><b>Subject:</b> Re: [ovirt-users] Move a VM between 2 setups</span></p><p></p></div></div><p class="MsoNormal"></p><p> </p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us">Hi Christophe,</span></p><p></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us"></span></p><p> </p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us">An “export domain” is made for just this purpose. Create a NFS (version 3) share and make it accessible to the hypervisors for each engine. (It should be a dedicated NFS share, not used for anything else.) As I recall it should be owned by vdsm:vdsm (36:36). In one of the engines (doesn’t matter which), in the web admin page go to Storage and add a new NFS based export domain, using the NFS share you created. Once it’s activated, test it out; try right-clicking on a VM to “export” it. </span></p><p></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us"></span></p><p> </p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us">Note that there can only be one engine connected to a given export domain at any one time. When you’re done testing the export domain on the first engine, you need to put it into “maintenance” and ultimately “detach” it.</span></p><p></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us"></span></p><p> </p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us">Then go to the other engine, and this time under Storage instead of “new domain” click “import domain” and enter the same NFS share information. It should recognize that you already have an export domain setup under that NFS share. Attach and activate it, and under Storage / <your export domain name> / VM Import, try importing the VM you had previously exported. </span></p><p></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us"></span></p><p> </p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us">This is covered (sparsely) in the oVirt documentation at <a href="https://www.ovirt.org/documentation/admin-guide/administration-guide/">https://www.ovirt.org/documentation/admin-guide/administration-guide/</a>, and it’s covered more coherently in the commercial RHV documentation at <a href="https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/administration-guide#Storage_properties">https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/administration-guide#Storage_properties</a>. </span></p><p></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us"></span></p><p> </p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us">Best,</span></p><p></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us">Daniel</span></p><p></p><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri, sans-serif;" lang="en-us"></span></p><p> </p><div style="border:none;border-top:solid #B5C4DF 1pt;padding:3pt 0cm 0cm 0cm;"><p class="MsoNormal"><b><span style="font-family:Calibri, sans-serif;color:#000000;" lang="en-us">From: </span></b><span style="font-family:Calibri, sans-serif;color:#000000;" lang="en-us"><<a href="mailto:users-bounces@ovirt.org">users-bounces@ovirt.org</a>> on behalf of Christophe TREFOIS <<a href="mailto:christophe.trefois@uni.lu">christophe.trefois@uni.lu</a>><br><b>Date: </b>Monday, November 14, 2016 at 11:14 AM<br><b>To: </b>users <<a href="mailto:users@ovirt.org">users@ovirt.org</a>><br><b>Subject: </b>[ovirt-users] Move a VM between 2 setups</span></p><p></p></div><div><p class="MsoNormal"><span lang="en-us"></span></p><p> </p></div><p class="MsoNormal"><span lang="en-us">Hi, </span></p><p></p><div><p class="MsoNormal"><span lang="en-us"></span></p><p> </p></div><div><p class="MsoNormal"><span lang="en-us">We have a setup where we want to deploy 2 engines as the network between 2 buildings is unreliable.</span></p><p></p></div><div><p class="MsoNormal"><span lang="en-us"></span></p><p> </p></div><div><p class="MsoNormal"><span lang="en-us">With 2 engines, we then want to be able to move VMs (one time) from current engine where they are running to new engine in the other building.</span></p><p></p></div><div><p class="MsoNormal"><span lang="en-us"></span></p><p> </p></div><div><p class="MsoNormal"><span lang="en-us">Is there a recommended workflow for doing this?</span></p><p></p></div><div><p class="MsoNormal"><span lang="en-us">We have access to shared NFS for this task if required.</span></p><p></p></div><div><p class="MsoNormal"><span lang="en-us"></span></p><p> </p></div><div><p class="MsoNormal"><span lang="en-us">Thanks for any pointers,</span></p><p></p></div><div><p class="MsoNormal"><span lang="en-us">Christophe</span></p><p></p></div><div><div><div><div><div><p class="MsoNormal" style="line-height:12pt;"><span style="font-size:10pt;font-family:Arial, sans-serif;color:#3D3B3B;" lang="en-us">-- </span><span style="font-size:10pt;font-family:Arial, sans-serif;color:#212121;" lang="en-us"></span></p><p></p><p class="MsoNormal" style="line-height:12pt;"><b><span style="font-size:10pt;font-family:Arial, sans-serif;color:#3D3B3B;" lang="en-us">Dr Christophe Trefois, Dipl.-Ing.</span></b><span class="apple-converted-space"><span style="font-size:10pt;font-family:Arial, sans-serif;color:#212121;" lang="en-us"> </span></span><span style="font-size:10pt;font-family:Arial, sans-serif;color:#212121;" lang="en-us"><br></span><span style="font-size:7.5pt;font-family:Arial, sans-serif;color:#3D3B3B;" lang="en-us">Technical Specialist / Post-Doc</span><span style="font-size:10pt;font-family:Arial, sans-serif;color:#212121;" lang="en-us"></span></p><p></p><p class="MsoNormal" style="line-height:12pt;"><b><span style="font-size:7.5pt;font-family:Arial, sans-serif;color:#3D3B3B;" lang="en-us">UNIVERSITÉ DU LUXEMBOURG</span></b><span style="font-size:7.5pt;font-family:Arial, sans-serif;color:#000000;" lang="en-us"><br><br></span><b><span style="font-size:7.5pt;font-family:Arial, sans-serif;color:#3D3B3B;" lang="en-us">LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE</span></b><span style="font-size:7.5pt;font-family:Arial, sans-serif;color:#000000;" lang="en-us"><br></span><span style="font-size:7.5pt;font-family:Arial, sans-serif;color:#3D3B3B;" lang="en-us">Campus Belval | House of Biomedicine<span class="apple-converted-space"> </span><br><span class="apple-converted-space">6, avenue du Swing </span><br>L-4367 Belvaux<span class="apple-converted-space"> </span></span><span style="font-size:7.5pt;font-family:Arial, sans-serif;color:#000000;" lang="en-us"><br></span><span style="font-size:7.5pt;font-family:Arial, sans-serif;color:#3D3B3B;" lang="en-us">T:<span class="apple-converted-space"> </span>+352 46 66 44 6124</span><span class="apple-converted-space"><span style="font-size:7.5pt;font-family:Arial, sans-serif;color:#000000;" lang="en-us"> </span></span><span style="font-size:7.5pt;font-family:Arial, sans-serif;color:#000000;" lang="en-us"><br></span><span style="font-size:7.5pt;font-family:Arial, sans-serif;color:#3D3B3B;" lang="en-us">F:<span class="apple-converted-space"> </span>+352 46 66 44 6949</span><span class="apple-converted-space"><span style="font-size:7.5pt;font-family:Arial, sans-serif;color:#000000;" lang="en-us"> </span></span><span style="font-size:7.5pt;font-family:Arial, sans-serif;color:#000000;" lang="en-us"><br><a href="http://www.uni.lu/lcsb"><span style="color:#006DBD;">http://www.uni.lu/lcsb</span></a></span></p><p></p><p class="MsoNormal" style="line-height:12pt;"><span style="font-size:10.5pt;font-family:Arial, sans-serif;color:#000000;" lang="en-us"><a href="https://www.facebook.com/trefex"><span style="text-decoration:none;"></span></a><span class="apple-converted-space"> </span><a href="https://twitter.com/Trefex"><span style="text-decoration:none;"></span></a><span class="apple-converted-space"> </span><a href="https://plus.google.com/+ChristopheTrefois/"><span style="text-decoration:none;"></span></a><span class="apple-converted-space"> </span><a href="https://www.linkedin.com/in/trefoischristophe"><span style="text-decoration:none;"></span></a><span class="apple-converted-space"> </span><a href="http://skype?call"><span style="text-decoration:none;"></span></a></span></p><p></p><p class="MsoNormal" style="line-height:12pt;"><span style="font-size:7pt;font-family:Arial, sans-serif;color:#3D3B3B;" lang="en-us">----<br>This message is confidential and may contain privileged information.<span class="apple-converted-space"> </span><br>It is intended for the named recipient only.<span class="apple-converted-space"> </span><br>If you receive it in error please notify me and permanently delete the original message and any copies.<span class="apple-converted-space"> </span><br>----</span></p><p></p><p class="MsoNormal"><span style="color:#000000;" lang="en-us"> <span class="apple-converted-space"> </span></span></p><p></p></div></div></div></div><p class="MsoNormal"><span lang="en-us"></span></p><p> </p></div></div></div> </blockquote></body></html>