Return-Path: Delivered-To: apmail-incubator-deltacloud-dev-archive@minotaur.apache.org Received: (qmail 27087 invoked from network); 4 Nov 2010 13:38:26 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 4 Nov 2010 13:38:26 -0000 Received: (qmail 76902 invoked by uid 500); 4 Nov 2010 13:38:57 -0000 Delivered-To: apmail-incubator-deltacloud-dev-archive@incubator.apache.org Received: (qmail 76830 invoked by uid 500); 4 Nov 2010 13:38:55 -0000 Mailing-List: contact deltacloud-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: deltacloud-dev@incubator.apache.org Delivered-To: mailing list deltacloud-dev@incubator.apache.org Received: (qmail 76822 invoked by uid 99); 4 Nov 2010 13:38:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Nov 2010 13:38:54 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=10.0 tests=RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of clalance@redhat.com designates 209.132.183.28 as permitted sender) Received: from [209.132.183.28] (HELO mx1.redhat.com) (209.132.183.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Nov 2010 13:38:48 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id oA4DcPeF005427 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 4 Nov 2010 09:38:25 -0400 Received: from localhost.localdomain (ovpn-113-24.phx2.redhat.com [10.3.113.24]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id oA4DcM8S010997 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 4 Nov 2010 09:38:24 -0400 Date: Thu, 4 Nov 2010 09:37:53 -0400 From: Chris Lalancette To: Sang-Min Park Cc: deltacloud-devel@lists.fedorahosted.org, deltacloud-dev@incubator.apache.org Subject: Re: [deltacloud-devel] Acceptance test Message-ID: <20101104133752.GD2706@localhost.localdomain> Reply-To: Chris Lalancette References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22 On 11/02/10 - 03:10:15PM, Sang-Min Park wrote: > Dear all, > > > > I am a software engineer at Eucalyptus systems. > > We’re planning to work on getting Eucalyptus to work with DeltaCloud. > > Probably, we’re going to use the existing EC2 drivers with minimal changes. > > > > I have one question regarding testing procedure. Are there any acceptance > tests for a new driver implementation? > > We want to know in general the QA process for DeltaCloud. There are actually two separate pieces of deltacloud that currently share the same name: the deltacloud API, and the deltacloud aggregator[1]. The API consists of core deltacloud server bits, including the drivers, and also consists of a ruby library to talk to the deltacloud server. All of that is hosted under Apache; the mailing list is deltacloud-dev@incubator.apache.org (which I've CC'ed on this message). The aggregator is a UI that allows you to combine multiple cloud providers in various ways. That is the mailing list that is hosted here. What I *think* you are looking for is the deltacloud API section, hosted at apache. In terms of acceptance tests, there are some tests in the deltacloud API core repository, but I'm not sure what they test in terms of acceptance. The right place to ask about this is at the apache project; now that I have CC'ed them, hopefully someone with a little more knowledge will respond. If you run into problems with the drivers and eucalyptus, please report them; it is one of the target clouds that we would like to support! Thanks, -- Chris Lalancette [1] We plan to rectify this situation in the near future by having a different name for the aggregator.