You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Mike Tutkowski (JIRA)" <ji...@apache.org> on 2013/08/27 23:09:52 UTC

[jira] [Created] (CLOUDSTACK-4527) Extend support of CloudStack-managed storage to KVM

Mike Tutkowski created CLOUDSTACK-4527:
------------------------------------------

             Summary: Extend support of CloudStack-managed storage to KVM
                 Key: CLOUDSTACK-4527
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4527
             Project: CloudStack
          Issue Type: New Feature
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: KVM
    Affects Versions: Future
            Reporter: Mike Tutkowski
            Assignee: Mike Tutkowski
             Fix For: Future


>From Review Request 13865:

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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira