On Mon, 14 Nov 2016 19:42:46 +0000 Daniel wrote: BD> 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. BD> BD> 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. BD> BD> 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.
What I did in the past was to create a nfs share for each engine in subdirectories on the same filesystem (eg /srv/ovirt/export/beta, /srv/ovirt/export/production). After exporting from one, log in the the nfs machine and move (or cp -al) the exported domain from one to the other. It's pretty much instantaneous since it's the same file system. Saves the hassle of the disconnect/reconnect. Robert -- Senior Software Engineer @ Parsons
pgpXcCviDGxLk.pgp
Description: OpenPGP digital signature
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
