Re: [ovirt-users] Move a VM between 2 setups

2016-11-15 Thread Yaniv Dary 
In general ever since 3.5 you don't need a export domain to do this.
It is advised you use import storage domain feature to do the same thing.
You create a new storage domain move VM to it and then remove it and attach
it to the new engine.
This should be much faster than the export domain.

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com
IRC : ydary


On Tue, Nov 15, 2016 at 4:04 PM, Robert Story  wrote:

> On Mon, 14 Nov 2016 19:42:46 + 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 /
>   / 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
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Move a VM between 2 setups

2016-11-15 Thread Robert Story 
On Mon, 14 Nov 2016 19:42:46 + 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 /   
/ 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

Re: [ovirt-users] Move a VM between 2 setups

2016-11-15 Thread Christophe TREFOIS 
Hi,

The reason I use this term is because it is indeed 2 engines, or two different 
setups / environments.

I’m not talking about moving a VM from a virtual DC to another virtual DC in 
the same engine.

Best,
-- 

Dr Christophe Trefois, Dipl.-Ing.  
Technical Specialist / Post-Doc

UNIVERSITÉ DU LUXEMBOURG

LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
Campus Belval | House of Biomedicine  
6, avenue du Swing 
L-4367 Belvaux  
T: +352 46 66 44 6124 
F: +352 46 66 44 6949  
http://www.uni.lu/lcsb <http://www.uni.lu/lcsb>
 <https://www.facebook.com/trefex>   <https://twitter.com/Trefex>   
<https://plus.google.com/+ChristopheTrefois/>   
<https://www.linkedin.com/in/trefoischristophe>   <http://skype:Trefex?call>

This message is confidential and may contain privileged information. 
It is intended for the named recipient only. 
If you receive it in error please notify me and permanently delete the original 
message and any copies. 


  

> On 14 Nov 2016, at 22:51, c...@endlessnow.com wrote:
> 
> 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.).
> 
> The language "export domains  'between' engines" is a bit confusing...
> 
> 
> 
> - Original Message -
> From:
> "Christophe TREFOIS" <christophe.tref...@uni.lu>
> 
> To:
> "Beckman Daniel" <daniel.beck...@ingramcontent.com>, "users" <users@ovirt.org>
> Cc:
> 
> Sent:
> Mon, 14 Nov 2016 20:10:16 +
> Subject:
> Re: [ovirt-users] Move a VM between 2 setups
> 
> 
> Hi Daniel,
> 
> 
> 
>  
> Fantastic information. Thanks so much for this.
> 
> 
> 
>  
> I was already using export domains inside my current engine, but not sure if 
> it would also work “between” engines so to speak.
> 
> 
> 
>  
> Have a great evening!
> 
> 
> Christophe
> 
> 
> 
>  
> From: Beckman, Daniel [mailto:daniel.beck...@ingramcontent.com] 
> Sent: lundi 14 novembre 2016 20:43
> To: Christophe TREFOIS <christophe.tref...@uni.lu>; users <users@ovirt.org>
> Subject: Re: [ovirt-users] Move a VM between 2 setups
> 
> 
> 
>  
> Hi Christophe,
> 
> 
> 
>  
> 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.
> 
> 
> 
>  
> 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.
> 
> 
> 
>  
> 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 /  
>  / VM Import, try importing the VM you had previously exported.
> 
> 
> 
>  
> This is covered (sparsely) in the oVirt documentation at 
> https://www.ovirt.org/documentation/admin-guide/administration-guide/ 
> <https://www.ovirt.org/documentation/admin-guide/administration-guide/>, and 
> it’s covered more coherently in the commercial RHV documentation at 
> 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>.
> 
> 
> 
>  
> Best,
> 
> 
> Daniel
> 
> 
> 
>  
> From: <users-boun...@ovirt.org <mailto:users-boun...@ovirt.org>> on behalf of 
> Christophe TREFOIS <christophe.tref...@uni.lu 
> <mailto:christophe.tref...@uni.lu>>
> Date: Monday, November 14, 2016 at 11:14 AM
> To: users <users@ovirt.org <mailto:users@ovirt.org>>
> Subject: [ovirt-users] Move a VM between 2 setups
> 
> 
> 
>  
> Hi,
> 
> 
> 
>  
> We have a setup where we want to deploy 2 engines as the network between 2 
> buildings is unreliable.
> 
> 
> 
>  
> With 2 engines, we then want to be able to move V

Re: [ovirt-users] Move a VM between 2 setups

2016-11-15 Thread ccox 
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.).

The language "export domains  'between' engines" is a bit
confusing...

- Original Message -
From:
 "Christophe TREFOIS" <christophe.tref...@uni.lu>

To:
"Beckman Daniel" <daniel.beck...@ingramcontent.com>, "users"
<users@ovirt.org>
Cc:

Sent:
Mon, 14 Nov 2016 20:10:16 +
Subject:
Re: [ovirt-users] Move a VM between 2 setups

Hi Daniel,

 

Fantastic information. Thanks so much for this.

 

I was already using export domains inside my current engine, but not
sure if it would also work “between” engines so to speak.

 

Have a great evening!

Christophe

 

FROM: Beckman, Daniel [mailto:daniel.beck...@ingramcontent.com] 
SENT: lundi 14 novembre 2016 20:43
TO: Christophe TREFOIS <christophe.tref...@uni.lu>; users
<users@ovirt.org>
SUBJECT: Re: [ovirt-users] Move a VM between 2 setups

 

Hi Christophe,

 

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. 

 

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.

 

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 /   / VM Import, try importing the
VM you had previously exported. 

 

This is covered (sparsely) in the oVirt documentation at
https://www.ovirt.org/documentation/admin-guide/administration-guide/
[1], and it’s covered more coherently in the commercial RHV
documentation at
https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/administration-guide#Storage_properties
[2]. 

 

Best,

Daniel

 

FROM: <users-boun...@ovirt.org [3]> on behalf of Christophe TREFOIS
<christophe.tref...@uni.lu [4]>
DATE: Monday, November 14, 2016 at 11:14 AM
TO: users <users@ovirt.org [5]>
SUBJECT: [ovirt-users] Move a VM between 2 setups

 

Hi, 

 

We have a setup where we want to deploy 2 engines as the network
between 2 buildings is unreliable.

 

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.

 

Is there a recommended workflow for doing this?

We have access to shared NFS for this task if required.

 

Thanks for any pointers,

Christophe

-- 

DR CHRISTOPHE TREFOIS, DIPL.-ING.  

Technical Specialist / Post-Doc

UNIVERSITÉ DU LUXEMBOURG

LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE

Campus Belval | House of Biomedicine  

6, avenue du Swing 

L-4367 Belvaux  

T: 
+352 46 66 44 6124
 

F: 
+352 46 66 44 6949
  

http://www.uni.lu/lcsb
 [6]

 [7]  

 [8]  

 [9]  

 [10]  

 [11]


This message is confidential and may contain privileged information. 

It is intended for the named recipient only. 

If you receive it in error please notify me and permanently delete the
original message and any copies. 



  

 

 

Links:
--
[1]
https://www.ovirt.org/documentation/admin-guide/administration-guide/
[2]
https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/administration-guide#Storage_properties
[3] mailto:users-boun...@ovirt.org
[4] mailto:christophe.tref...@uni.lu
[5] mailto:users@ovirt.org
[6] http://www.uni.lu/lcsb
[7] https://www.facebook.com/trefex
[8] https://twitter.com/Trefex
[9] https://plus.google.com/+ChristopheTrefois/
[10] https://www.linkedin.com/in/trefoischristophe
[11] http://skype?call

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Move a VM between 2 setups

2016-11-14 Thread Christophe TREFOIS 
Hi Daniel,

 

Fantastic information. Thanks so much for this.

 

I was already using export domains inside my current engine, but not sure if it 
would also work “between” engines so to speak.

 

Have a great evening!

Christophe

 

From: Beckman, Daniel [mailto:daniel.beck...@ingramcontent.com] 
Sent: lundi 14 novembre 2016 20:43
To: Christophe TREFOIS <christophe.tref...@uni.lu>; users <users@ovirt.org>
Subject: Re: [ovirt-users] Move a VM between 2 setups

 

Hi Christophe,

 

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. 

 

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.

 

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 /   
/ VM Import, try importing the VM you had previously exported. 

 

This is covered (sparsely) in the oVirt documentation at 
https://www.ovirt.org/documentation/admin-guide/administration-guide/, and it’s 
covered more coherently in the commercial RHV documentation at 
https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/administration-guide#Storage_properties.
 

 

Best,

Daniel

 

From: <users-boun...@ovirt.org <mailto:users-boun...@ovirt.org> > on behalf of 
Christophe TREFOIS <christophe.tref...@uni.lu 
<mailto:christophe.tref...@uni.lu> >
Date: Monday, November 14, 2016 at 11:14 AM
To: users <users@ovirt.org <mailto:users@ovirt.org> >
Subject: [ovirt-users] Move a VM between 2 setups

 

Hi, 

 

We have a setup where we want to deploy 2 engines as the network between 2 
buildings is unreliable.

 

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.

 

Is there a recommended workflow for doing this?

We have access to shared NFS for this task if required.

 

Thanks for any pointers,

Christophe

-- 

Dr Christophe Trefois, Dipl.-Ing.  
Technical Specialist / Post-Doc

UNIVERSITÉ DU LUXEMBOURG

LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
Campus Belval | House of Biomedicine  
6, avenue du Swing 
L-4367 Belvaux  
T: +352 46 66 44 6124 
F: +352 46 66 44 6949  
 <http://www.uni.lu/lcsb> http://www.uni.lu/lcsb

 <https://www.facebook.com/trefex><https://twitter.com/Trefex>
<https://plus.google.com/+ChristopheTrefois/>
<https://www.linkedin.com/in/trefoischristophe><http://skype:Trefex?call> 


This message is confidential and may contain privileged information. 
It is intended for the named recipient only. 
If you receive it in error please notify me and permanently delete the original 
message and any copies. 


  

 



smime.p7s
Description: S/MIME cryptographic signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Move a VM between 2 setups

2016-11-14 Thread Beckman, Daniel 
Hi Christophe,

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.

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.

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 /   
/ VM Import, try importing the VM you had previously exported.

This is covered (sparsely) in the oVirt documentation at 
https://www.ovirt.org/documentation/admin-guide/administration-guide/, and it’s 
covered more coherently in the commercial RHV documentation at 
https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/administration-guide#Storage_properties.

Best,
Daniel

From: <users-boun...@ovirt.org> on behalf of Christophe TREFOIS 
<christophe.tref...@uni.lu>
Date: Monday, November 14, 2016 at 11:14 AM
To: users <users@ovirt.org>
Subject: [ovirt-users] Move a VM between 2 setups

Hi,

We have a setup where we want to deploy 2 engines as the network between 2 
buildings is unreliable.

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.

Is there a recommended workflow for doing this?
We have access to shared NFS for this task if required.

Thanks for any pointers,
Christophe
--
Dr Christophe Trefois, Dipl.-Ing.
Technical Specialist / Post-Doc
UNIVERSITÉ DU LUXEMBOURG

LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
Campus Belval | House of Biomedicine
6, avenue du Swing
L-4367 Belvaux
T: +352 46 66 44 6124
F: +352 46 66 44 6949
http://www.uni.lu/lcsb
[acebook]<https://www.facebook.com/trefex>  [witter] 
<https://twitter.com/Trefex>   [oogle Plus] 
<https://plus.google.com/+ChristopheTrefois/>   [inkedin] 
<https://www.linkedin.com/in/trefoischristophe>   [kype] 
<http://skype:Trefex?call>

This message is confidential and may contain privileged information.
It is intended for the named recipient only.
If you receive it in error please notify me and permanently delete the original 
message and any copies.



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Move a VM between 2 setups

2016-11-14 Thread Christophe TREFOIS 
Hi,

We have a setup where we want to deploy 2 engines as the network between 2 
buildings is unreliable.

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.

Is there a recommended workflow for doing this?
We have access to shared NFS for this task if required.

Thanks for any pointers,
Christophe
-- 

Dr Christophe Trefois, Dipl.-Ing.  
Technical Specialist / Post-Doc

UNIVERSITÉ DU LUXEMBOURG

LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
Campus Belval | House of Biomedicine  
6, avenue du Swing 
L-4367 Belvaux  
T: +352 46 66 44 6124 
F: +352 46 66 44 6949  
http://www.uni.lu/lcsb 
       
   
   

This message is confidential and may contain privileged information. 
It is intended for the named recipient only. 
If you receive it in error please notify me and permanently delete the original 
message and any copies. 


  



smime.p7s
Description: S/MIME cryptographic signature
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users