Hi, The storage protocol is really independent of how the volumes are stored, and whether or not they are resize-capable. For example, I can take an iSCSI or FC lun and either format it ext3, mount it as local storage, and put qcow2 images on it, or I can put it into a volume group and carve out logical volumes. When it gets down to it, the VMs are currently either using qcow2 images, logical volumes, RBD volumes, or using LUNs directly via something like the SolidFire plugin. A qcow2 image resizes like a qcow2, regardless of how it's attached.
On Thu, Jul 25, 2013 at 6:23 AM, Pavan Bandarupally < pavan.bandarupa...@citrix.com> wrote: > Hai Marcus,**** > > ** ** > > I am looking at the matrix that will be supported for this feature and I > am bit confused regarding the supported things. I am not sure how the API > calls for Disk Resize are made. So can you please clear my doubts.**** > > ** ** > > In the design page [ > https://cwiki.apache.org/CLOUDSTACK/resize-data-volumes.html ] nothing is > mentioned about the storage protocols (iSCSI or NFS or FC). Only QCOW2 and > CLVM are mentioned. Does it matter if the Disk is stored on local storage > or iSCSI/FC LUN or on NFS based Storage device ? I mean does the > CloudStack API send different parameters for different storage devices or > is it dependant only on the Disk type ? **** > > ** ** > > I am looking at something like this: **** > > ** ** > > ** ** > > QCOW2**** > > CLVM**** > > ** ** > > Grow**** > > Shrink**** > > Grow**** > > Shrink**** > > KVM**** > > ** ** > > ** ** > > Xen**** > > ** ** > > ** ** > > VmWare**** > > ** ** > > ** ** > > ** ** > > Or **** > > ** ** > > Are we supposed to create something like this :**** > > ** ** > > ** ** > > NFS**** > > iSCSI**** > > FC**** > > Local Storage**** > > CLVM**** > > QCOW2**** > > LVM ?**** > > KVM**** > > ** ** > > ** ** > > ** ** > > ** ** > > ** ** > > ** ** > > ** ** > > Xen**** > > ** ** > > ** ** > > ** ** > > ** ** > > ** ** > > ** ** > > ** ** > > VmWare**** > > ** ** > > ** ** > > ** ** > > ** ** > > ** ** > > ** ** > > ** ** > > ** ** > > ** ** > > Please correct me if something is wrong. Thanks for you help.**** > > ** ** > > Regards,**** > > Pavan**** >
