2:51 p.m.
Hi,
First of all, sorry for the naive question, but I have not been able
to find good guidance on the docs.
I come from the VMWare environment, now I am starting to migrate
some workload from VMWare to oVirt (v4.1.4 , CentOS 7.3 hosts).
In VMWare I am used to have one datacenter, several host clusters,
and a bunch of iSCSI Datastores, but we do not map every iSCSI
LUN/datastore to every host. Actually we used to do that, but we hit
limits on the number of iSCSI paths with our infrastructure.
Rather than that, we have groups of LUNs/Datastores mapped to the
ESXi hosts which form a given VMware cluster. Then we have a couple of
datastores mapped to every ESXi in the vmware datacenter, and we use
those to store the ISO images and as storage that we use when we need to
migrate VMs between clusters for some reason.
Given the role of the Master data domain and the SPM in oVIrt it is
my understanding that I cannot replicate this kind of setup in oVirt: a
data domain in an oVirt Data Center must be available to every Host on
the Data Center: Am I right?
So, our current setup is still small, but I am concerned that as it
grows, if I stay with one Datacenter, several clusters and a group of
data domains mapped to every host I may run again into problems with the
number of iSCSI paths (the limit in VMWare was around 1024), it is easy
to reach that limit as it is (number of hosts) * (number of LUNs) *
(number of paths/LUN).
If I split my setup in several datacenters controlled by a single
oVirt-engine in order to keep the number of iSCSI paths reasonable. Can
I manually migrate VMs between Datacenters? I assume that in order to do
that, those datacenters will need to share some data domain , Can this
be done? Maybe with NFS?
Thanks for your help!
--
Eduardo Mayoral Jimeno (emayoral(a)arsys.es)
Administrador de sistemas. Departamento de Plataformas. Arsys internet.
+34 941 620 145 ext. 5153
12:14 p.m.
Hi Eduardo,
Welcome aboard!
First, you may find some relevant information in here: http://www.ovirt.org/
documentation/admin-guide/administration-guide/ .
Regarding your questions:
* A data domain in an oVirt Data Center must be available to every Host on
the Data Center: Am I right?
Yes, you're right.
* Can I manually migrate VMs between Datacenters?
VM migration can't be performed between data canters, so you can't use the
'migrate VM' function.
In order to "migrate" your VM between different data canters, you can use
'export' and 'import' functions and an 'export domain':
By creating an export domain for one of your DC's (each DC can have up to
one export domain), and exporting your VM to that storage domain,
you can then detach the export domain from that DC and attach it to the
other DC, and by importing there your VM you'll finish the transaction.
Another option is to detach the VM's storage domain from one DC and attach
it the second one.
That way you'll move the whole storage domain between your DCs.
If you have any further questions, don't hesitate to ask :)
*Regards,*
*Shani Leviim*
On Thu, Aug 24, 2017 at 2:51 PM, Eduardo Mayoral <emayoral(a)arsys.es> wrote:
Hi,
First of all, sorry for the naive question, but I have not been able
to find good guidance on the docs.
I come from the VMWare environment, now I am starting to migrate
some workload from VMWare to oVirt (v4.1.4 , CentOS 7.3 hosts).
In VMWare I am used to have one datacenter, several host clusters,
and a bunch of iSCSI Datastores, but we do not map every iSCSI
LUN/datastore to every host. Actually we used to do that, but we hit
limits on the number of iSCSI paths with our infrastructure.
Rather than that, we have groups of LUNs/Datastores mapped to the
ESXi hosts which form a given VMware cluster. Then we have a couple of
datastores mapped to every ESXi in the vmware datacenter, and we use
those to store the ISO images and as storage that we use when we need to
migrate VMs between clusters for some reason.
Given the role of the Master data domain and the SPM in oVIrt it is
my understanding that I cannot replicate this kind of setup in oVirt: a
data domain in an oVirt Data Center must be available to every Host on
the Data Center: Am I right?
So, our current setup is still small, but I am concerned that as it
grows, if I stay with one Datacenter, several clusters and a group of
data domains mapped to every host I may run again into problems with the
number of iSCSI paths (the limit in VMWare was around 1024), it is easy
to reach that limit as it is (number of hosts) * (number of LUNs) *
(number of paths/LUN).
If I split my setup in several datacenters controlled by a single
oVirt-engine in order to keep the number of iSCSI paths reasonable. Can
I manually migrate VMs between Datacenters? I assume that in order to do
that, those datacenters will need to share some data domain , Can this
be done? Maybe with NFS?
Thanks for your help!
--
Eduardo Mayoral Jimeno (emayoral(a)arsys.es)
Administrador de sistemas. Departamento de Plataformas. Arsys internet.
+34 941 620 145 ext. 5153
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
1:52 p.m.
This is a multi-part message in MIME format.
--------------EF9DB308729751D8A73B2BAB
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Thank you very much, Mr Leviim!
This made things clear.
Eduardo Mayoral Jimeno (emayoral(a)arsys.es)
Administrador de sistemas. Departamento de Plataformas. Arsys internet.
+34 941 620 145 ext. 5153
On 28/08/17 11:14, Shani Leviim wrote:
Hi Eduardo,
Welcome aboard!
First, you may find some relevant information in here:
http://www.ovirt.org/documentation/admin-guide/administration-guide/
<http://www.ovirt.org/documentation/admin-guide/administration-guide/> .
Regarding your questions:
* A data domain in an oVirt Data Center must be available to every
Host on the Data Center: Am I right?
Yes, you're right.
* Can I manually migrate VMs between Datacenters?
VM migration can't be performed between data canters, so you can't use
the 'migrate VM' function.
In order to "migrate" your VM between different data canters, you can
use 'export' and 'import' functions and an 'export domain':
By creating an export domain for one of your DC's (each DC can have up
to one export domain), and exporting your VM to that storage domain,
you can then detach the export domain from that DC and attach it to
the other DC, and by importing there your VM you'll finish the
transaction.
Another option is to detach the VM's storage domain from one DC and
attach it the second one.
That way you'll move the whole storage domain between your DCs.
If you have any further questions, don't hesitate to ask :)
*Regards,
*
*Shani Leviim
*
On Thu, Aug 24, 2017 at 2:51 PM, Eduardo Mayoral <emayoral(a)arsys.es
<mailto:emayoral@arsys.es>> wrote:
Hi,
First of all, sorry for the naive question, but I have not
been able
to find good guidance on the docs.
I come from the VMWare environment, now I am starting to migrate
some workload from VMWare to oVirt (v4.1.4 , CentOS 7.3 hosts).
In VMWare I am used to have one datacenter, several host clusters,
and a bunch of iSCSI Datastores, but we do not map every iSCSI
LUN/datastore to every host. Actually we used to do that, but we hit
limits on the number of iSCSI paths with our infrastructure.
Rather than that, we have groups of LUNs/Datastores mapped to the
ESXi hosts which form a given VMware cluster. Then we have a couple of
datastores mapped to every ESXi in the vmware datacenter, and we use
those to store the ISO images and as storage that we use when we
need to
migrate VMs between clusters for some reason.
Given the role of the Master data domain and the SPM in oVIrt
it is
my understanding that I cannot replicate this kind of setup in
oVirt: a
data domain in an oVirt Data Center must be available to every Host on
the Data Center: Am I right?
So, our current setup is still small, but I am concerned that
as it
grows, if I stay with one Datacenter, several clusters and a group of
data domains mapped to every host I may run again into problems
with the
number of iSCSI paths (the limit in VMWare was around 1024), it is
easy
to reach that limit as it is (number of hosts) * (number of LUNs) *
(number of paths/LUN).
If I split my setup in several datacenters controlled by a single
oVirt-engine in order to keep the number of iSCSI paths
reasonable. Can
I manually migrate VMs between Datacenters? I assume that in order
to do
that, those datacenters will need to share some data domain , Can this
be done? Maybe with NFS?
Thanks for your help!
--
Eduardo Mayoral Jimeno (emayoral(a)arsys.es <mailto:emayoral@arsys.es>)
Administrador de sistemas. Departamento de Plataformas. Arsys
internet.
+34 941 620 145 ext. 5153 <tel:%2B34%20941%20620%20145%20ext.%205153>
_______________________________________________
Users mailing list
Users(a)ovirt.org <mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
<http://lists.ovirt.org/mailman/listinfo/users>
--------------EF9DB308729751D8A73B2BAB
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thank you very much, Mr Leviim! <br>
</p>
<p>This made things clear.<br>
</p>
<pre class="moz-signature" cols="72">Eduardo Mayoral Jimeno
(<a class="moz-txt-link-abbreviated"
href="mailto:emayoral@arsys.es">emayoral@arsys.es</a>)
Administrador de sistemas. Departamento de Plataformas. Arsys internet.
+34 941 620 145 ext. 5153</pre>
<div class="moz-cite-prefix">On 28/08/17 11:14, Shani Leviim
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAMO6KYr-Nd4xuXPNMaGsJUv-ZmZ2xg1x-d8CD9gnwJ-VgOpLBA@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<div dir="ltr">
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">Hi
Eduardo,</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">Welcome
aboard! <br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small"><br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">First,
you may find some relevant information in here: <a
href="http://www.ovirt.org/documentation/admin-guide/administration-...
target="_blank"
moz-do-not-send="true">http://www.ovirt.org/<wbr>docum...
.</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small"><br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">Regarding
your questions:</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">* A data
domain in an oVirt Data Center must be available to every Host
on the Data Center: Am I right?<br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">Yes,
you're right.</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small"><br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">* Can I
manually migrate VMs between Datacenters?</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">VM
migration can't be performed between data canters, so you
can't use the 'migrate VM' function.<br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">In order
to "migrate" your VM between different data canters, you can
use 'export' and 'import' functions and an 'export
domain':<br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">By
creating an export domain for one of your DC's (each DC can
have up to one export domain), and exporting your VM to that
storage domain, <br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">you can
then detach the export domain from that DC and attach it to
the other DC, and by importing there your VM you'll finish the
transaction. <br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small"><br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">Another
option is to detach the VM's storage domain from one DC and
attach it the second one.<br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">That way
you'll move the whole storage domain between your DCs. <br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small"><br>
</div>
<div class="gmail_default"
style="font-family:tahoma,sans-serif;font-size:small">If you
have any further questions, don't hesitate to ask :)<br>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div
class="m_2439165819232262882gmail-m_286038821312995006gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div><span
style="font-family:tahoma,sans-serif"><b>Regards,<br>
</b></span></div>
<span
style="font-family:tahoma,sans-serif"><b>Shani
Leviim<br>
</b></span></div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On Thu, Aug 24, 2017 at 2:51 PM,
Eduardo Mayoral <span dir="ltr"><<a
href="mailto:emayoral@arsys.es" target="_blank"
moz-do-not-send="true">emayoral(a)arsys.es</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
First of all, sorry for the naive question, but I have
not been able<br>
to find good guidance on the docs.<br>
<br>
I come from the VMWare environment, now I am starting
to migrate<br>
some workload from VMWare to oVirt (v4.1.4 , CentOS 7.3
hosts).<br>
<br>
In VMWare I am used to have one datacenter, several
host clusters,<br>
and a bunch of iSCSI Datastores, but we do not map every
iSCSI<br>
LUN/datastore to every host. Actually we used to do that,
but we hit<br>
limits on the number of iSCSI paths with our
infrastructure.<br>
<br>
Rather than that, we have groups of LUNs/Datastores
mapped to the<br>
ESXi hosts which form a given VMware cluster. Then we have
a couple of<br>
datastores mapped to every ESXi in the vmware datacenter,
and we use<br>
those to store the ISO images and as storage that we use
when we need to<br>
migrate VMs between clusters for some reason.<br>
<br>
Given the role of the Master data domain and the SPM
in oVIrt it is<br>
my understanding that I cannot replicate this kind of
setup in oVirt: a<br>
data domain in an oVirt Data Center must be available to
every Host on<br>
the Data Center: Am I right?<br>
<br>
So, our current setup is still small, but I am
concerned that as it<br>
grows, if I stay with one Datacenter, several clusters and
a group of<br>
data domains mapped to every host I may run again into
problems with the<br>
number of iSCSI paths (the limit in VMWare was around
1024), it is easy<br>
to reach that limit as it is (number of hosts) * (number
of LUNs) *<br>
(number of paths/LUN).<br>
<br>
If I split my setup in several datacenters controlled
by a single<br>
oVirt-engine in order to keep the number of iSCSI paths
reasonable. Can<br>
I manually migrate VMs between Datacenters? I assume that
in order to do<br>
that, those datacenters will need to share some data
domain , Can this<br>
be done? Maybe with NFS?<br>
<br>
Thanks for your help!<br>
<span
class="m_2439165819232262882gmail-m_286038821312995006HOEnZb"><font
color="#888888"><br>
--<br>
Eduardo Mayoral Jimeno (<a
href="mailto:emayoral@arsys.es" target="_blank"
moz-do-not-send="true">emayoral(a)arsys.es</a>)<br>
Administrador de sistemas. Departamento de
Plataformas. Arsys internet.<br>
<a href="tel:%2B34%20941%20620%20145%20ext.%205153"
value="+34941620145" target="_blank"
moz-do-not-send="true">+34 941 620 145 ext.
5153</a><br>
<br>
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank"
moz-do-not-send="true">Users(a)ovirt.org</a><br>
<a
href="http://lists.ovirt.org/mailman/listinfo/users"
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://lists.ovirt.org/mailman<wbr...
</font></span></blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>
--------------EF9DB308729751D8A73B2BAB--
2641
days inactive
2648
days old
2 comments
2 participants
participants (2)
-
Eduardo Mayoral -
Shani Leviim