<div style="line-height:1.7;color:#000000;font-size:14px;font-family:arial"><br>thanks,i know a little more. but i do not understand fully. distrubute filesystem is more understandable.<div style="font-family: Helvetica, 'Microsoft Yahei', verdana;">specially,,for SAN(iscsi,fc) it is hard to share luns between nodes(not reliable), even use LVM,CLVM.</div><div style="font-family: Helvetica, 'Microsoft Yahei', verdana;"><br></div><div style="font-family: Helvetica, 'Microsoft Yahei', verdana;">would you explain it ( SAN case)?and it is hard to connect '<span style="white-space: pre-wrap; line-height: 1.7;">local directory</span><span style="line-height: 1.7;">' with distrbuted repo.</span></div><div style="font-family: Helvetica, 'Microsoft Yahei', verdana;"><br><br>thanks.<br></div><div><br></div><br><br><br><div></div><div id="divNeteaseMailCard"></div><br><pre><br>At 2013-02-27 17:55:45,"Gianluca Cecchi" <gianluca.cecchi@gmail.com> wrote:
>On Wed, Feb 27, 2013 at 10:44 AM, bigclouds wrote:
>> there is a sentense 'Implements a distributed image repository over the
>> supported storage types (local directory, FCP, FCoE, iSCSI, NFS, SAS)
>> ' on http://www.ovirt.org/Architecture.
>>
>> what is "distributed image repository"?
>>
>> thanks.
>
>Example
>I have a test environment where a Host is connected to several FCP LUNs.
>Each LUN becomes a storage domain for this host and the other hosts in
>the same cluster.
>So I have many VMs whose images resides on different storage domains
>(and so different LUNs).
>I can move a disk of a VM from a storage domain to another one.
>I think you can also have a mixed situation where a two disks' VM has
>one disk on a storage domain and the other one in another.
>
>So I think it is to be explained this way the "distributed image repository".
>
>And also "distributed" in the sense of different storage domain types,
>even if I think at this time one DC cannot have a mix of different
>storage domain types...
>
>Gianluca
</pre></div><br><br><span title="neteasefooter"><span id="netease_mail_footer"></span></span>