----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/13865/#review28483 -----------------------------------------------------------
Reminder - Hi, This review has been pending for long. Please update to "submitted" if this has already been committed. Thanks - Amogh Vasekar On Aug. 27, 2013, 9:17 p.m., Mike Tutkowski wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/13865/ > ----------------------------------------------------------- > > (Updated Aug. 27, 2013, 9:17 p.m.) > > > Review request for cloudstack. > > > Bugs: CLOUDSTACK-4527 > https://issues.apache.org/jira/browse/CLOUDSTACK-4527 > > > Repository: cloudstack-git > > > Description > ------- > > 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. > > Support is offered in the form of Disk Offerings (not Compute Offerings). > > > Diffs > ----- > > > Diff: https://reviews.apache.org/r/13865/diff/ > > > Testing > ------- > > > Thanks, > > Mike Tutkowski > >