cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcus Sorensen <>
Subject pluggable storage implementation
Date Mon, 10 Dec 2012 19:06:11 GMT
Just curious, hadn't thought about this before but it seems that at least
on KVM (probably similar in Xen and VMware too?), there are two separate
issues with storage in the existing code. First, adding a new storage type
is a matter of adding in a new 'else if' or something in a bunch of
different places, as well as tweaking behavior to match the storage type.
Second, everything about the storage is tightly integrated with Libvirt,
meaning that if your storage type is not supported by Libvirt it's much,
much more difficult to implement.

Are these both being addressed by the storage changes, for example can we
write a storage plugin that creates pools/volumes that libvirt doesn't know
about and still attach those to instances? Or would we need to patch
libvirt to utilize our storage first?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message