Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 95F80C89F for ; Sun, 10 Jun 2012 00:46:57 +0000 (UTC) Received: (qmail 7350 invoked by uid 500); 10 Jun 2012 00:46:56 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 7313 invoked by uid 500); 10 Jun 2012 00:46:56 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 7303 invoked by uid 99); 10 Jun 2012 00:46:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Jun 2012 00:46:56 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Chiradeep.Vittal@citrix.com designates 66.165.176.89 as permitted sender) Received: from [66.165.176.89] (HELO SMTP.CITRIX.COM) (66.165.176.89) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Jun 2012 00:46:50 +0000 X-IronPort-AV: E=Sophos;i="4.75,744,1330923600"; d="scan'208";a="27489004" Received: from sjcpmailmx01.citrite.net ([10.216.14.74]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/RC4-MD5; 09 Jun 2012 20:46:28 -0400 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.73]) by SJCPMAILMX01.citrite.net ([10.216.14.74]) with mapi; Sat, 9 Jun 2012 17:46:28 -0700 From: Chiradeep Vittal To: CloudStack DeveloperList CC: "jclouds-dev@googlegroups.com" Date: Sat, 9 Jun 2012 17:46:24 -0700 Subject: Re: EC2/S3 API testing Thread-Topic: EC2/S3 API testing Thread-Index: Ac1GongnKW6d24gbQ/CyjyF2c/YJsg== Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.13.0.110805 acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Both (jclouds and euca) are attractive options. Does jclouds use the AWS SOAP API or the Query API? CloudStack currently implements the SOAP and Query API for EC2 (although the latter is not tested) and the Query API for S3. On 6/9/12 9:28 AM, "Adrian Cole" wrote: >jclouds has an integration test suite for s3, ec2, cloudwatch, elb apis >(and many other apis) > >We need to run the ec2 and s3 tests against greenqloud (a cloudstack >service) before we release support for it. This is a normal part of our >release process for 3+ years now. > >VMware have a certification tool based on our test suite which breaks down >results of 250+ tests into categories and percentages. > >If you all were interested, we could collaborate on the same sort of tool >for AWS compatibility and take advantage of the hundreds of live tests we >already have for AWS apis (all written in java) > >As a reminder, jclouds is ASL and underpins many Apache projects' cloud >support including ACE, Whirr, Karaf, Camel. Using the same test codebase >will benefit apache significantly. > >Wdyt? >-A > On Jun 9, 2012 7:37 AM, "David Nalley" wrote: > >> My line of thinking is: >> >> 1: There's no reason to reinvent this test suite on our own (I am >> assuming that CloudStack doesn't have a complete test suite for EC2/S3 >> - but could be wrong) >> 2: Euca and CS have similar aims wrt testing for EC2/S3 API >> compliance, which means we can collaborate and as we both build tests >> both of us benefit. >> 3: My sense is that because it's one of Euca's sole focus is the AWS >> API compliance is tighter than ours - I certainly know that's been the >> case in the recent past, and thus we benefit from their rigidity. >> >> So the real questions are: >> >> 1. Do we have a AWS API test suite I am unaware of? >> 2. If not, we should look at collaborating (even if it is with some >> other test suite as Sam pointed out) as it's less work than >> reinventing the wheel. >> >> >> --David >> >> On Sat, Jun 9, 2012 at 4:01 AM, Sam Robertson >> wrote: >> > The test scripts they have are very limited, but it's a good framework >> for >> > what it is. >> > >> > On 6/8/12 8:07 PM, "Rajesh Battala" wrote: >> > >> >>Hi Kevin, >> >>I had gone through the code and found that it's doing a very basic >> >>testing of S3. >> >> >> >>Thanks >> >>Rajesh Battala >> >>> -----Original Message----- >> >>> From: Kevin Kluge [mailto:Kevin.Kluge@citrix.com] >> >>> Sent: Saturday, June 09, 2012 8:10 AM >> >>> To: cloudstack-dev@incubator.apache.org >> >>> Subject: RE: EC2/S3 API testing >> >>> >> >>> Rajesh, do you think it's limited in the sense of number of test >>cases >> >>>and/or >> >>> coverage? If not, what do you mean by 'limited'? >> >>> >> >>> -kevin >> >>> >> >>> > -----Original Message----- >> >>> > From: Rajesh Battala [mailto:rajesh.battala@citrix.com] >> >>> > Sent: Thursday, June 07, 2012 8:39 AM >> >>> > To: cloudstack-dev@incubator.apache.org >> >>> > Subject: RE: EC2/S3 API testing >> >>> > >> >>> > Thanks a lot for the info. >> >>> > But I see this file is testing S3 >> >>> > https://raw.github.com/eucalyptus/eutester/master/eucaops/s3ops.py >> >>> > which are very much limited. >> >>> > >> >>> > > -----Original Message----- >> >>> > > From: David Nalley [mailto:david@gnsa.us] >> >>> > > Sent: Thursday, June 07, 2012 8:21 PM >> >>> > > To: cloudstack-dev@incubator.apache.org >> >>> > > Subject: EC2/S3 API testing >> >>> > > >> >>> > > Hi folks, >> >>> > > >> >>> > > So I was talking with some of the Euca folks recently and they >>told >> >>> > > me they have an EC2/S3 test platform called Eutester, that >> >>> > > essentially runs a ton of tests by calling the EC2/S3 API calls >> >>> > > against their endpoints. Don't know if you find this useful or >>not, >> >>> > > but it's located >> >>> > > here: >> >>> > > >> >>> > > https://github.com/eucalyptus/eutester >> >>> > > >> >>> > > --David >> > >>