2:05 a.m.
This is a multi-part message in MIME format.
--------------000007090803090504000509
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
On 2-1-2017 22:53, Paul Groeneweg | Pazion wrote:
Hi,
I am finally planning to start our oVirt hosted engine upgrade. I am
not sure how stable my hosted engine storage is ( it shows wrong
status in web GUI ) So I arranged a new shared storage and plan to do
a fresh install ( altough I noticed there is also an option to
upgrade "hosted-engine --upgrade-appliance" ).
After I installed the oVirt 4 hosted engine on a host node I want to
move all my running VMs to the new environment. With VMs at first
running on the current data storage domain. My storage domain is FC based.
My idea is to:
1. stop all VMs
2. detach Storage domain on old ovirt 3.6 environment ( and keep data ).
3. import and activate the storage domain on the new ovirt 4 environment.
To prevent any data loss or copy too much data I have the follwoing
questions:
1. Is this storage domain import from 3.6 to 4.0 available?
Yes, done it multiple
times.
2. I read I should import all VMs, this means I need to copy all
data
or is it just a matter of importing a config, so all VM data /image
remains on the imported storage domain?
I think it copies the info into the
database and thats it. It might also
adjust the info on the storagedomain metadata that it is now part of a
new install.
3. When for some reason I want to roll back when I have imported the
storage domain without having any VM imported, can I just detach and
re-attach the storage domain to the previous 3.6 environment?
That should work too. Only problem you could run into is if the detach
doesn't work for example when your new install suddenly went belly up.
People have had that and you need to adjust the metadata and then you
can import it back into 3.6 or another 4.0 install.
If there might be a better path to get my VMs to a clean oVirt 4.0
environment I am glad to hear.
The long way is to really export to an export domain and then import
from it.
Joop
--------------000007090803090504000509
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 2-1-2017 22:53, Paul Groeneweg |
Pazion wrote:<br>
</div>
<blockquote
cite="mid:CAE1B0QLF7JGd_6_usQ9pnKkOG+QEGkdxocfQHfkbb0kQ_iuvWA@mail.gmail.com"
type="cite">
<div dir="ltr">Hi,
<div><br>
</div>
<div>I am finally planning to start our oVirt hosted engine
upgrade. I am not sure how stable my hosted engine storage is
( it shows wrong status in web GUI ) So I arranged a new
shared storage and plan to do a fresh install ( altough I
noticed there is also an option to upgrade <span
style="color:inherit;font-size:inherit;background-color:transparent">"</span><span
style="color:inherit;font-size:inherit;background-color:transparent;font-family:menlo,monaco,consolas,"courier
new",monospace;white-space:pre-wrap">hosted-engine
--upgrade-appliance</span>"
).</div>
<div><br>
</div>
<div>After I installed the oVirt 4 hosted engine on a host node
I want to move all my running VMs to the new environment. With
VMs at first running on the current data storage domain. My
storage domain is FC based.</div>
<div><br>
</div>
<div>My idea is to:</div>
<div><br>
</div>
<div>1. stop all VMs</div>
<div>2. detach Storage domain on old ovirt 3.6 environment ( and
keep data ).</div>
<div>3. import and activate the storage domain on the new ovirt
4 environment.</div>
<div><br>
</div>
<div>To prevent any data loss or copy too much data I have the
follwoing questions: </div>
<div><br>
</div>
<div>1. Is this storage domain import from 3.6 to 4.0
available?</div>
</div>
</blockquote>
Yes, done it multiple times.<br>
<br>
<blockquote
cite="mid:CAE1B0QLF7JGd_6_usQ9pnKkOG+QEGkdxocfQHfkbb0kQ_iuvWA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>2. I read I should import all VMs, this means I need to
copy all data or is it just a matter of importing a config, so
all VM data /image remains on the imported storage domain?<br>
</div>
</div>
</blockquote>
I think it copies the info into the database and thats it. It might
also adjust the info on the storagedomain metadata that it is now
part of a new install.<br>
<br>
<blockquote
cite="mid:CAE1B0QLF7JGd_6_usQ9pnKkOG+QEGkdxocfQHfkbb0kQ_iuvWA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>3. When for some reason I want to roll back when I have
imported the storage domain without having any VM imported,
can I just detach and re-attach the storage domain to the
previous 3.6 environment?</div>
<div><br>
</div>
</div>
</blockquote>
That should work too. Only problem you could run into is if the
detach doesn't work for example when your new install suddenly went
belly up. People have had that and you need to adjust the metadata
and then you can import it back into 3.6 or another 4.0 install.<br>
<br>
<blockquote
cite="mid:CAE1B0QLF7JGd_6_usQ9pnKkOG+QEGkdxocfQHfkbb0kQ_iuvWA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>If there might be a better path to get my VMs to a clean
oVirt 4.0 environment I am glad to hear.</div>
<br>
</div>
</blockquote>
The long way is to really export to an export domain and then import
from it.<br>
<br>
Joop<br>
<br>
</body>
</html>
--------------000007090803090504000509--