Open Stack

Hi Diego, 

Thanks for your ideas about vm storage.
In my
proposal/question, I got in mind (for now) volume more than vm storage
(with the zfs property allowing nfs sharing, I believe that vm storage
can already be done with zfs backend). 

--- Nicolas 

On 2012-06-10
17:58, Diego Parrilla Santamaría wrote: 

> Nicolas, 
> it makes a lot
of sense what you want to do. ZFS+iSCSI is a perfect fit for vm storage,
some other IaaS solutions already use this combination (and I have
developed some). Keep in mind that Nexenta is only a distro based upon
OpenSolaris: OpenIndiana, FreeBSD... there are a lot of options with
ZFS. 
> There are several things you should consider to implement this
feature: 
> 1) The code that matters is mostly in
nova/virt/libvirt/connection.py for libvirt 
> 2) You need to implement
a new storage type: iscsi
(http://libvirt.org/storage.html#StorageBackendISCSI [1]) 
> 3) You need
to implement a feature to block-copy the source image to the backend
iscsi storage 
> 4) _cache_image method and most of _create_image should
be developed thinking in 3) 
> I think the only reason to implement this
feature is to develop a highly scalable storage system for instances, so
a single storage system does not make sense. It should be able to manage
a list storage systems as a pool and load balance them. 
> Some quick
thoughts, good luck! 
> Diego 
> 
> -- 
> 
> Diego Parrilla
> CEO
> |
diego.parrilla at stackops.com [2] | +34 649 94 43 29 |
skype:diegoparrilla

 

Links:
------
[1]
http://libvirt.org/storage.html#StorageBackendISCSI
[2]
mailto:diego.parrilla at stackops.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120610/f2f23b93/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: blocked.gif
Type: image/gif
Size: 118 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120610/f2f23b93/attachment.gif>