cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chiradeep Vittal <>
Subject Re: Moving ec2stack and gstack to the cloudstack repos.
Date Mon, 24 Nov 2014 19:01:44 GMT
Good to know, but are there any automated tests?

From: Ian Duffy <<>>
Reply-To: "<>" <<>>
Date: Monday, November 24, 2014 at 10:56 AM
To: "<>" <<>>
Subject: Re: Moving ec2stack and gstack to the cloudstack repos.


During the development of ec2stack we tested it using boto, awscli,
vagrant-aws and eutester.

Hope this satisfy your concerns.

On 24 November 2014 at 18:19, Chiradeep Vittal <<>>

Seems legit, but from (bitter) experience, there is no point in a
compatible API layer unless somebody puts in the elbow grease to test the
compatibility. Since the actual EC2 API as implemented by AWS changes
frequently and has undocumented semantics and  behavior that varies from
the WSDL, this takes some work. So, my question would be how would this
benefit the community (unless someone has tested out the compatibility with
various tools such as boto, ec2-* CLI).

From: Sebastien Goasguen <<><>>
Reply-To: "<><>"
Date: Saturday, November 22, 2014 at 12:41 PM
To: "<><>"
Subject: Moving ec2stack and gstack to the cloudstack repos.


Some of you may know of the existence of:

These represent a EC2 and a GCE interface to cloudstack.
Flask applications that map the requests to the cloudstack API.

There was only 3 contributors, myself, Ian (PMC and committer on CS) and
Darren Brogan.
Darren worked on this during his GSoC 2014 summer project.

Both projects are on Apache V2 license.

The three of us (Ian, Darren and myself) agree that we would like to move
them under the umbrella of cloudstack and manage separate releases like we
do cloud monkey.

Any objections ?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message