3:44 a.m.
This is a multi-part message in MIME format.
--------------070402090107030306050908
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Hi Roberto,
Thanks for your information but....
When I'm writing about DC I mean defined DC in oVirt and so far I could
see that when you define a storage domain in one oVirt DC it will not be
available in another DC and I don't know what would happen if I would
import it on the second DC.
In your setup, did you just define 1 DC and multiple clusters?
Regards,
Arsène
On 05/01/2016 01:37 PM, NUNIN Roberto wrote:
Hi
I have in production the scenery something similar to what you've
described.
The "enabling factor" is represented by an "storage virtualization"
set of appliances, that maintain mirrored logical volume over fc
physical volumes across two distinct datacenters, while giving rw
simultaneus access to cluster hypervisors split between datacenters,
that run the VMs.
So: cluster also is spread across dc, no need to import nothing.
Regards,
*Roberto*
Il giorno 01 mag 2016, alle ore 10:37, Arsène Gschwind
<arsene.gschwind(a)unibas.ch <mailto:arsene.gschwind@unibas.ch>> ha scritto:
> Hi,
>
> Is it possible to have a shared Storage domain between 2 Datacenter
> in oVirt?
> We do replicate a FC Volume between 2 datacenter using FC SAN storage
> technology and we have an oVirt cluster on each site defined in
> separate DCs. The idea behind this is to setup a DR site and also
> balance the load between each site.
> What happens if I do import a storage domain already active in one
> DC, will it break the Storage domain?
>
> Thanks for any information..
> Regards,
> Arsène
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org <mailto:Users@ovirt.org>
> http://lists.ovirt.org/mailman/listinfo/users
------------------------------------------------------------------------
Questo messaggio e' indirizzato esclusivamente al destinatario
indicato e potrebbe contenere informazioni confidenziali, riservate o
proprietarie. Qualora la presente venisse ricevuta per errore, si
prega di segnalarlo immediatamente al mittente, cancellando
l'originale e ogni sua copia e distruggendo eventuali copie cartacee.
Ogni altro uso e' strettamente proibito e potrebbe essere fonte di
violazione di legge.
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately, deleting
the original and all copies and destroying any hard copies. Any other
use is strictly prohibited and may be unlawful.
--------------070402090107030306050908
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 text="#000000" bgcolor="#FFFFFF">
Hi Roberto,<br>
<br>
Thanks for your information but....<br>
When I'm writing about DC I mean defined DC in oVirt and so far I
could see that when you define a storage domain in one oVirt DC it
will not be available in another DC and I don't know what would
happen if I would import it on the second DC.<br>
In your setup, did you just define 1 DC and multiple clusters?<br>
<br>
Regards,<br>
Arsène<br>
<br>
<div class="moz-cite-prefix">On 05/01/2016 01:37 PM, NUNIN Roberto
wrote:<br>
</div>
<blockquote
cite="mid:C5D87583-C722-4DD1-B8A3-CC8947AF2D96@comifar.it"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div>Hi</div>
<div id="AppleMailSignature">I have in production the scenery
something similar to what you've described.</div>
<div id="AppleMailSignature">The "enabling factor" is
represented
by an "storage virtualization" set of appliances, that maintain
mirrored logical volume over fc physical volumes across two
distinct datacenters, while giving rw simultaneus access to
cluster hypervisors split between datacenters, that run the VMs.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">So: cluster also is spread across dc,
no need to import nothing.</div>
<div id="AppleMailSignature">Regards,<br>
<br>
<p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt;
line-height: 12.05pt;"><span style="background-color:
rgba(255, 255, 255, 0);"><b>Roberto</b><br>
</span></p>
<p class="MsoNormal" style="margin: 0cm 0cm
0.0001pt;"><span
style="background-color: rgba(255, 255, 255,
0);"> </span></p>
</div>
<div><br>
Il giorno 01 mag 2016, alle ore 10:37, Arsène Gschwind <<a
moz-do-not-send="true"
href="mailto:arsene.gschwind@unibas.ch"><a
class="moz-txt-link-abbreviated"
href="mailto:arsene.gschwind@unibas.ch">arsene.gschwind@unibas.ch</a></a>>
ha scritto:<br>
<br>
</div>
<blockquote type="cite">
<div><span>Hi,</span><br>
<span></span><br>
<span>Is it possible to have a shared Storage domain between 2
Datacenter in oVirt?</span><br>
<span>We do replicate a FC Volume between 2 datacenter using
FC SAN storage technology and we have an oVirt cluster on
each site defined in separate DCs. The idea behind this is
to setup a DR site and also balance the load between each
site.</span><br>
<span>What happens if I do import a storage domain already
active in one DC, will it break the Storage domain?</span><br>
<span></span><br>
<span>Thanks for any information..</span><br>
<span>Regards,</span><br>
<span>Arsène</span><br>
<span>_______________________________________________</span><br>
<span>Users mailing list</span><br>
<span><a moz-do-not-send="true"
href="mailto:Users@ovirt.org">Users@ovirt.org</a></span><br>
<span><a moz-do-not-send="true"
href="http://lists.ovirt.org/mailman/listinfo/users">http://...
</div>
</blockquote>
<br>
<hr>
<font face="Courier New" size="2"
color="Black"><br>
Questo messaggio e' indirizzato esclusivamente al destinatario
indicato e potrebbe contenere informazioni confidenziali,
riservate o proprietarie. Qualora la presente venisse ricevuta
per errore, si prega di segnalarlo immediatamente al mittente,
cancellando l'originale e ogni sua copia e distruggendo
eventuali copie cartacee. Ogni altro uso e' strettamente
proibito e potrebbe essere fonte di violazione di legge.<br>
<br>
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private
information. If you have received it in error, please notify the
sender immediately, deleting the original and all copies and
destroying any hard copies. Any other use is strictly prohibited
and may be unlawful.<br>
</font>
</blockquote>
<br>
</body>
</html>
--------------070402090107030306050908--