Hi Amit, As I mentioned on a different thread, I would recommend looking at the SolidFire plug-in.
Also, John Burwell and I can work with you on changes in 4.3 in the storage framework that might impact your development. The SolidFire plug-in was designed to provide Min and Max IOPS guarantees to CloudStack data volumes. In this model, the CloudStack volume maps on to a single SAN volume (as opposed to the traditional technique in CloudStack where a volume (say, on a SAN) would house many CloudStack volumes). Also, feel free to a look at the JIRA ticket I wrote up for 4.2: https://issues.apache.org/jira/browse/CLOUDSTACK-2778 Thanks On Wed, Aug 7, 2013 at 11:47 PM, Amit Das <amit....@cloudbyte.com> wrote: > I would like to implement a new storage plugin based on the recently > refactored CloudStack(CS) storage code. > > This plugin will allow a CS Admin to interact with ElastiStor's APIs to > provision and manage QoS-aware storage volumes for VMs. > > CloudByte's ElastiStor is a full-featured software-defined storage QoS > solution. > > Any suggestions ? > > Regards, > Amit > *CloudByte Inc.* <http://www.cloudbyte.com/> > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *™*
