Open Stack

The only thing is that you need to create the volumes on your ISCSI backend first, so libvirt can use them, otherwise as a shared storage, works fine. ISCSI always gave me nice speeds compared to NFS

On Oct 28, 2013, at 10:04, Chris Friesen <chris.friesen at windriver.com> wrote:

> That works for one client.  How do you synchronize access between multiple clients?
> 
> Also, for iSCSI it looks like libvirt can't create/delete volumes, that needs to be done on the server.
> 
> Chris
> 
> On 10/28/2013 10:49 AM, Razique Mahroua wrote:
>> Libvrit does support ISCSI LUN as backends, meaning you can mount the ISCSI block on every compute node and you should be fine
>> - Razique
>> 
>> On Oct 28, 2013, at 8:54, Chris Friesen <chris.friesen at windriver.com> wrote:
>> 
>>> On 10/28/2013 09:35 AM, Ray Sun wrote:
>>>> Daniel,
>>>> Thanks for you response. But I am still confusing about use a iscsi
>>>> device, if I want to use it as shared storage, first I need to attach to
>>>> a node as a block storage, then I mount it to other compute nodes using
>>>> NFS. The problem is that this will make a big lost on performance.
>>>> Currently nova already support to create a new VM on ceph RBD, but why
>>>> we can not create it on a block storage?
>>> 
>>> ceph and NFS are both designed for simultaneous access by multiple clients.
>>> 
>>> iSCSI is not.
>>> 
>>> Chris
>>> 
>>> 
>>> _______________________________________________
>>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>> Post to     : openstack at lists.openstack.org
>>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 535 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20131028/b59e5255/attachment.sig>