<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
One of the things I don't like very much in oVirt is the LVM on
Shared Block storage, but unfortunately there are no other options.
One day perhaps a VMFS5 equivalent will come up somewhere.<br>
<br>
I would avoid it and put a server in between the SAN and the oVirt
Nodes and use NFS in order to abstract it, that would give you more
flexibility and keep you away from LVM. But in your case if you
don't have 10GbE interfaces you will loose on performance using 1GbE
interfaces.<br>
<br>
With regards the migration of VMs between different CPU families
I'm not sure what is the tolerance of oVirt with it. Depending on
the CPUs and the cluster types you may be able to do migrations.So I
would keep different CPU families in different clusters.<br>
<br>
Fernando<br>
<br>
<div class="moz-cite-prefix">Em 15/07/2016 07:07, Neil escreveu:<br>
</div>
<blockquote
cite="mid:CAPdW-3JbjUo0X7mSc93txUSij-GQwk0a6C0L0+CuQ+i4-7pzSA@mail.gmail.com"
type="cite">
<div dir="ltr">Hi guys,
<div><br>
</div>
<div>I'm soon going to have the following equipment and I'd like
to find the best way to utilise it....</div>
<div><br>
</div>
<div>1.) One NEW FC SAN, and 3 new Dell Hosts with FC cards.</div>
<div><br>
</div>
<div>2.) One OLD FC SAN with 2 older HP hosts with FC cards.
(old VMWare environment)</div>
<div><br>
</div>
<div>3.) Another OLDER FC SAN with 2 older HP Hosts with FC
cards. (old VMWare environment)</div>
<div><br>
</div>
<div>4.) I have an existing oVirt 3.5 DR cluster with two hosts
and NFS storage that is current in use and works well.</div>
<div><br>
</div>
<div>Each of the above SAN's will only have FC ports to connect
to their existing hosts, so all hosts won't be connected to
all SAN's. All hosts would be the same Centos 7.x release etc.</div>
<div><br>
</div>
<div>All existing VM's are going to be moved to the option 1 via
a baremetal restore from backup onto a NEW oVirt platform.
Once installed I'd then like to re-commission 2 and 3 above to
make use of the old hardware and SAN's as secondary or
possibly a "new" DR platform to replace or improve on option
4.</div>
<div><br>
</div>
<div>Bearing in mind the older hardware will be different CPU
generations, would it be best to add the older hosts and SAN's
as new clusters within the same NEW oVirt installation? Or
should I rather just keep 2, 3 and 4 as separate oVirt
installations?</div>
<div><br>
</div>
<div>I know in the past live migration wouldn't work with
different CPU generations, and of course my SAN's won't be
physically connected to each of the hosts.</div>
<div><br>
</div>
<div>In order to move VM's between 1, 2 and 3 would I need to
shut the VM down and export and import, or is there another
way to do this? </div>
<div><br>
</div>
<div>Could LSM work between across all three SANS and hosts?</div>
<div><br>
</div>
<div>I know I can do a baremetal restore from backup directly
onto either 1, 2 or 3 if needed, but I'd like to try tie all
of this into one platform if there is good reason to do so.
Any thoughts, suggestions or ideas here?</div>
<div><br>
</div>
<div>Any guidance is greatly appreciated.</div>
<div><br>
</div>
<div>Thank you</div>
<div><br>
</div>
<div>Regards.</div>
<div><br>
</div>
<div>Neil Wilson.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</body>
</html>