7:41 a.m.
What is the procedure to use when migrating Ovirt to or from RHEV? I'm
assuming of course that there's little difference for the two
directions. Is it just a matter of detaching the storage domain(s),
dumping the engine database and attaching/importing them into the other
system?
regards,
John
11:21 p.m.
Bump.
On 17/11/14 15:41, John Gardeniers wrote:
What is the procedure to use when migrating Ovirt to or from RHEV?
I'm
assuming of course that there's little difference for the two
directions. Is it just a matter of detaching the storage domain(s),
dumping the engine database and attaching/importing them into the
other system?
regards,
John
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
11:27 p.m.
Not an official answer here, but I'd assume the procedure would be to
redeploy the engine and hosts, and use export domains
On Thu, Nov 20, 2014 at 3:21 PM, John Gardeniers <
jgardeniers(a)objectmastery.com> wrote:
Bump.
On 17/11/14 15:41, John Gardeniers wrote:
> What is the procedure to use when migrating Ovirt to or from RHEV? I'm
> assuming of course that there's little difference for the two directions.
> Is it just a matter of detaching the storage domain(s), dumping the engine
> database and attaching/importing them into the other system?
>
> regards,
> John
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
11:42 p.m.
This is a multi-part message in MIME format.
--------------050301050103020805000209
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Thanks Dan,
If that's the case it would be an extremely time-consuming and painful
process, even to the point where it may not even be viable. :-(
It's increasingly looking to me like a deliberate decision has been
taken to make it as difficult as possible to migrate VMs away from
Ovirt/RHEV. It's the only virtualisation system I've encountered that
doesn't have a real export system (export domains don't cut it).
regards,
John
On 21/11/14 07:27, Dan Yasny wrote:
Not an official answer here, but I'd assume the procedure would
be to
redeploy the engine and hosts, and use export domains
On Thu, Nov 20, 2014 at 3:21 PM, John Gardeniers
<jgardeniers(a)objectmastery.com <mailto:jgardeniers@objectmastery.com>>
wrote:
Bump.
On 17/11/14 15:41, John Gardeniers wrote:
What is the procedure to use when migrating Ovirt to or from
RHEV? I'm assuming of course that there's little difference
for the two directions. Is it just a matter of detaching the
storage domain(s), dumping the engine database and
attaching/importing them into the other system?
regards,
John
_______________________________________________
Users mailing list
Users(a)ovirt.org <mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
______________________________________________________________________
This email has been scanned by the Symantec Email
Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
_______________________________________________
Users mailing list
Users(a)ovirt.org <mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
--------------050301050103020805000209
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Thanks Dan,<br>
<br>
If that's the case it would be an extremely time-consuming and
painful process, even to the point where it may not even be viable.
<span class="moz-smiley-s2"><span> :-(
</span></span><br>
<br>
It's increasingly looking to me like a deliberate decision has been
taken to make it as difficult as possible to migrate VMs away from
Ovirt/RHEV. It's the only virtualisation system I've encountered
that doesn't have a real export system (export domains don't cut
it).<br>
<br>
regards,<br>
John<br>
<br>
<br>
<div class="moz-cite-prefix">On 21/11/14 07:27, Dan Yasny
wrote:<br>
</div>
<blockquote
cite="mid:CALLXwb6EZDsVw5SNBbsJ1pkj=BibiZWJG_2jXkv8ZK=FOm7tCA@mail.gmail.com"
type="cite">
<div dir="ltr">Not an official answer here, but I'd assume the
procedure would be to redeploy the engine and hosts, and use
export domains</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Nov 20, 2014 at 3:21 PM, John
Gardeniers <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:jgardeniers@objectmastery.com"
target="_blank">jgardeniers(a)objectmastery.com</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Bump.<br>
<br>
On 17/11/14 15:41, John Gardeniers wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
What is the procedure to use when migrating Ovirt to or
from RHEV? I'm assuming of course that there's little
difference for the two directions. Is it just a matter of
detaching the storage domain(s), dumping the engine
database and attaching/importing them into the other
system?<br>
<br>
regards,<br>
John<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Users@ovirt.org"
target="_blank">Users(a)ovirt.org</a><br>
<a moz-do-not-send="true"
href="http://lists.ovirt.org/mailman/listinfo/users"
target="_blank">http://lists.ovirt.org/mailman/listinfo/user...
<br>
______________________________________________________________________<br>
This email has been scanned by the Symantec Email
Security.cloud service.<br>
For more information please visit <a
moz-do-not-send="true"
href="http://www.symanteccloud.com"
target="_blank">http://www.symanteccloud.com</a><br>
______________________________________________________________________<br>
</blockquote>
<br>
_______________________________________________<br>
Users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Users@ovirt.org"
target="_blank">Users(a)ovirt.org</a><br>
<a moz-do-not-send="true"
href="http://lists.ovirt.org/mailman/listinfo/users"
target="_blank">http://lists.ovirt.org/mailman/listinfo/user...
</blockquote>
</div>
<br>
</div>
<br clear="all">
______________________________________________________________________<br>
This email has been scanned by the Symantec Email Security.cloud
service.<br>
For more information please visit <a class="moz-txt-link-freetext"
href="http://www.symanteccloud.com">http://www.symanteccloud.com</a><br>
______________________________________________________________________<br>
</blockquote>
<br>
</body>
</html>
--------------050301050103020805000209--
11:49 p.m.
Not going to argue with that, it's rather pointless, but:
http://www.ovirt.org/OVirt_3.5_Release_Notes#Import_Storage_Domain
Now this feature only needs to make it into RHEV.
My suggestion is as safe as it gets, in fact I migrated a large setup from
2.2 to 3.4 this summer with no problems
On Thu, Nov 20, 2014 at 3:42 PM, John Gardeniers <
jgardeniers(a)objectmastery.com> wrote:
Thanks Dan,
If that's the case it would be an extremely time-consuming and painful
process, even to the point where it may not even be viable. :-(
It's increasingly looking to me like a deliberate decision has been taken
to make it as difficult as possible to migrate VMs away from Ovirt/RHEV.
It's the only virtualisation system I've encountered that doesn't have a
real export system (export domains don't cut it).
regards,
John
On 21/11/14 07:27, Dan Yasny wrote:
Not an official answer here, but I'd assume the procedure would be to
redeploy the engine and hosts, and use export domains
On Thu, Nov 20, 2014 at 3:21 PM, John Gardeniers <
jgardeniers(a)objectmastery.com> wrote:
> Bump.
>
> On 17/11/14 15:41, John Gardeniers wrote:
>
>> What is the procedure to use when migrating Ovirt to or from RHEV? I'm
>> assuming of course that there's little difference for the two directions.
>> Is it just a matter of detaching the storage domain(s), dumping the engine
>> database and attaching/importing them into the other system?
>>
>> regards,
>> John
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>> ______________________________________________________________________
>> This email has been scanned by the Symantec Email Security.cloud service.
>> For more information please visit http://www.symanteccloud.com
>> ______________________________________________________________________
>>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
3655
days inactive
3658
days old
4 comments
2 participants
participants (2)
-
Dan Yasny -
John Gardeniers