Hi, I've drawn up a Review Board Request for 4.3 and assigned it to myself.
https://reviews.apache.org/r/13865/ Here is the JIRA ticket: https://issues.apache.org/jira/browse/CLOUDSTACK-4527 Here is the gist: This patch is part two of the SolidFire plug-in. Part one is described in Review Request 11479 and was implemented in CS 4.2. The focus of this patch is to support a one-to-one mapping between a CloudStack volume and a SolidFire volume when using KVM. The hypervisor plug-ins were initially developed to expect storage was preallocated from a storage device. In 4.2, with the storage plug-in framework, this model has changed to additionally support Primary Storage representing a storage device itself (ex. a SAN) as opposed to it having to represent preallocated storage (ex. a volume from a SAN). In the new model, Primary Storage can represent a SAN like SolidFire's. When a CloudStack volume is attached to a VM for the first time, the storage framework asks the storage plug-in to execute some logic. In the SolidFire case, this is where a volume is created on the SolidFire SAN. In CS 4.2, I created the SolidFire plug-in and modified necessary parts of the storage framework as well as XenServer and VMware plug-in logic to enable a one-to-one mapping between a CS volume and a SolidFire volume when using XenServer and ESX(i). This patch aims to extend this support to KVM. Please let me know if you have any comments. Thanks! -- *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> *™*
