Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5C1F010779 for ; Mon, 21 Oct 2013 22:00:02 +0000 (UTC) Received: (qmail 63516 invoked by uid 500); 21 Oct 2013 21:54:27 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 61401 invoked by uid 500); 21 Oct 2013 21:51:59 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 59829 invoked by uid 500); 21 Oct 2013 21:49:27 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 58308 invoked by uid 99); 21 Oct 2013 21:46:56 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Oct 2013 21:46:56 +0000 Date: Mon, 21 Oct 2013 21:46:56 +0000 (UTC) From: "Animesh Chaturvedi (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CLOUDSTACK-4527) Extend support of CloudStack-managed storage to KVM MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-4527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-4527: ------------------------------------------- ACS 4.3 feature freeze date is November 8th. Please provide update on your items as a comment. > 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: 4.3.0 > Reporter: Mike Tutkowski > Assignee: Mike Tutkowski > Fix For: 4.3.0 > > > 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. > Support is offered in the form of Disk Offerings (not Compute Offerings). -- This message was sent by Atlassian JIRA (v6.1#6144)