Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A720DF8AD for ; Tue, 9 Apr 2013 06:34:10 +0000 (UTC) Received: (qmail 2748 invoked by uid 500); 9 Apr 2013 06:34:10 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 2612 invoked by uid 500); 9 Apr 2013 06:34:09 -0000 Mailing-List: contact dev-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 dev@cloudstack.apache.org Received: (qmail 2596 invoked by uid 99); 9 Apr 2013 06:34:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Apr 2013 06:34:09 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Chiradeep.Vittal@citrix.com designates 66.165.176.63 as permitted sender) Received: from [66.165.176.63] (HELO SMTP02.CITRIX.COM) (66.165.176.63) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Apr 2013 06:34:04 +0000 X-IronPort-AV: E=Sophos;i="4.87,436,1363132800"; d="scan'208";a="17400001" Received: from sjcpmailmx02.citrite.net ([10.216.14.75]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/RC4-MD5; 09 Apr 2013 06:33:18 +0000 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.73]) by SJCPMAILMX02.citrite.net ([10.216.14.75]) with mapi; Mon, 8 Apr 2013 23:33:18 -0700 From: Chiradeep Vittal To: "dev@cloudstack.apache.org" Date: Mon, 8 Apr 2013 23:33:13 -0700 Subject: Re: [DIscuss]Storage image store plugin framework refactoring Thread-Topic: [DIscuss]Storage image store plugin framework refactoring Thread-Index: Ac407B75UWXGHnlpRw+ZVf5Q1W3JdQ== Message-ID: In-Reply-To: <6E004C34C1C59E45A35B4338808BC31501445D1F6F8B@SJCPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.1.130117 acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org We can't deprecate APIs unless we are changing to 5.0 AFAIK the next release in plan is 4.2 How does an upgrade from 4.0/4.1 to 4.2 work with this proposal? - what happens to existing SSVMs? - if there are multiple SSVMs? - current cache-like deployments for S3 and Swift The SSVM code also does duty for VMWare deployments to aid in data movement. How does this change? On 4/8/13 6:34 PM, "Sangeetha Hariharan" wrote: >Min, > >Could you also include the details of the API changes (new parameters) >that will be proposed as part of this feature? >Also it would be helpful if you list the request and response parameters >for the new API calls. >For all the API calls that are being deprecated , is there any specific >error message that will be returned? > >-Thanks >Sangeetha=20 > >-----Original Message----- >From: Min Chen [mailto:min.chen@citrix.com] >Sent: Monday, April 08, 2013 4:45 PM >To: dev@cloudstack.apache.org >Subject: [DIscuss]Storage image store plugin framework refactoring > >Hi All, > >Currently CloudStack does not offer a flexible pluggable framework for >users to easily integrate and configure any 3rd-party object stores for >such backup services as registering templates, taking snapshots, etc. >Along with Edison's recent refactored storage subsystem 2.0 that mainly >refactored current CloudStack primary storage implementation, we are >proposing to develop a storage backup object store plugin framework to >allow CloudStack to systematically manage and configure various types of >backup data stores from different vendors, like NFS, S3, Swift, etc. With >this new plugin framework, we would like to achieve following >functionalities: >1. Support different object store providers in a uniform and pluggable >fashion. >2. Enable region wide object backup using S3-like object store. >3. Provide pluggable data motion strategies to handle data transfer from >one data store to another data store. >4. Provide a scalable cache storage framework while moving data between >primary storage and backup storage for certain hypervisor needs. >5. Support flexible combinations of primary storage, secondary storage >and hypervisors, such as (NFS, NFS, Xen), (NF3, S3, Vmware), (ISCSI, >Swift, KVM), ...., etc. >The proposed ImageStore plugin framework architecture is detailed in our >FS here:=20 >https://cwiki.apache.org/confluence/display/CLOUDSTACK/Storage+Backup+Obje >ct+Store+Plugin+Framework. >The JIRA ticket to track this feature is: >https://issues.apache.org/jira/browse/CLOUDSTACK-1975. The work is >currently carried out in feature branch "object_store". >Please let me know your comments and suggestions. > >Thanks >-min > >