Return-Path: X-Original-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5FB68E796 for ; Thu, 7 Mar 2013 11:28:15 +0000 (UTC) Received: (qmail 10204 invoked by uid 500); 7 Mar 2013 11:28:09 -0000 Delivered-To: apmail-incubator-cloudstack-users-archive@incubator.apache.org Received: (qmail 9954 invoked by uid 500); 7 Mar 2013 11:28:09 -0000 Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-users@incubator.apache.org Delivered-To: mailing list cloudstack-users@incubator.apache.org Received: (qmail 9924 invoked by uid 99); 7 Mar 2013 11:28:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Mar 2013 11:28:08 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Asmita.Vagyani@sigma-systems.com designates 207.46.163.27 as permitted sender) Received: from [207.46.163.27] (HELO co9outboundpool.messaging.microsoft.com) (207.46.163.27) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Mar 2013 11:28:01 +0000 Received: from mail64-co9-R.bigfish.com (10.236.132.252) by CO9EHSOBE036.bigfish.com (10.236.130.99) with Microsoft SMTP Server id 14.1.225.23; Thu, 7 Mar 2013 11:27:38 +0000 Received: from mail64-co9 (localhost [127.0.0.1]) by mail64-co9-R.bigfish.com (Postfix) with ESMTP id C45D3401E0 for ; Thu, 7 Mar 2013 11:27:38 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.238.5;KIP:(null);UIP:(null);IPV:NLI;H:BY2PRD0512HT001.namprd05.prod.outlook.com;RD:none;EFVD:NLI X-SpamScore: -6 X-BigFish: PS-6(zzbb2dI98dI9371I542I1432I14ffIzz1ee6h1202h1e76h1d2ahzz8275bh8275dhz31h2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1155h) Received-SPF: softfail (mail64-co9: transitioning domain of sigma-systems.com does not designate 157.56.238.5 as permitted sender) client-ip=157.56.238.5; envelope-from=Asmita.Vagyani@sigma-systems.com; helo=BY2PRD0512HT001.namprd05.prod.outlook.com ;.outlook.com ; Received: from mail64-co9 (localhost.localdomain [127.0.0.1]) by mail64-co9 (MessageSwitch) id 1362655655779304_29832; Thu, 7 Mar 2013 11:27:35 +0000 (UTC) Received: from CO9EHSMHS026.bigfish.com (unknown [10.236.132.251]) by mail64-co9.bigfish.com (Postfix) with ESMTP id B29CD200A3 for ; Thu, 7 Mar 2013 11:27:35 +0000 (UTC) Received: from BY2PRD0512HT001.namprd05.prod.outlook.com (157.56.238.5) by CO9EHSMHS026.bigfish.com (10.236.130.36) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 7 Mar 2013 11:27:35 +0000 Received: from BY2PRD0512MB623.namprd05.prod.outlook.com ([169.254.5.237]) by BY2PRD0512HT001.namprd05.prod.outlook.com ([10.255.243.34]) with mapi id 14.16.0275.006; Thu, 7 Mar 2013 11:27:34 +0000 From: Asmita Vagyani To: "'cloudstack-users@incubator.apache.org'" Subject: RE: Cloudstack S3 (Simple Storage Service) Support Thread-Topic: Cloudstack S3 (Simple Storage Service) Support Thread-Index: Ac3+tI/h1MUZHF7rS/C72rkxk0gyQQBSFwgABspVtaA= Date: Thu, 7 Mar 2013 11:27:34 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [115.113.153.54] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: sigma-systems.com X-Virus-Checked: Checked by ClamAV on apache.org Hi all, I can see that cloudstack has S3 support , and we can enable the S3 flag in= Cloudstack. However, I want to know if I can let user create storage buckets and give u= sers a key with which they can put data into these storage buckets. I think, I can have my own huge single NFS storage server, and as the user = come I can assign buckets on the server. Let me know if this is possible from cloudstack, if yes then which API docu= mentation can help me find a solution. Thanks and Regards. Asmita=20 -----Original Message----- From: Chiradeep Vittal [mailto:Chiradeep.Vittal@citrix.com]=20 Sent: 01 February 2013 AM 03:20 To: cloudstack-users@incubator.apache.org Subject: Re: Cloudstack S3 (Simple Storage Service) Support The storage.root parameter in cloud-bridge.properties can point to any filesystem: with this you will get a filesystem-backed S3 service. However the reliability, durability and scalability are guaranteed by the c= hoice of filesystem. For example if the filesystem is an NFS mount provided= by a NetApp server, the reliability properties of the NetApp server would = apply. On 1/29/13 10:39 PM, "Asmita Vagyani" wrote: >Hi all, > > > >I've been doing some reading there are definitely implementation that=20 >make use of Cloudstack and provide a Storage Instance type server. > > > >Essentially we want the same type of service as the Amazon S3 (Simple=20 >Storage Service). > > > >Cloudstack has an S3 interface though it is not enabled by default=20 >(need to change Global Setting): >https://cwiki.apache.org/CLOUDSTACK/s3-api-in-cloudstack.html > > > >Even though Cloudstack supports the S3 API , do we still need a storage=20 >implementation - like CAStor, or Cloudian, or GlusterFS? > > > >Still not clear to me if we configure anything in the Cloudstack=20 >Manager to enable this or if it is just enabling the S3 API and=20 >implementing the storage layer? > >Please clarify. > > > >Thanks and Regards. > >Asmita Patil Vagyani. > >Tech Lead, Sigma Software Solutions, Pune, > >T: +91-20-25661992 / 93 / 94. Extn. : 286 >