Chiradeep,

Of course, check out the git repository at
https://github.com/brogand1993/ec2stack the code is pretty clean and there
is 99% test coverage. TravisCI is setup to run on every commit and execute
the tests along with pylint for static analysis.

There's a screencast here of a rough overview
https://www.youtube.com/watch?v=xvu-gc8h4Qg&list=UUoGs2iiOIGrfXofp-3g-Qqg
It looks at installation, configuration and basic usage against exoscale
using awscli.


Regards,

Ian


On 24 Nov 2014 19:02, "Chiradeep Vittal" <chiradeep.vit...@citrix.com>
wrote:

> Good to know, but are there any automated tests?
>
> From: Ian Duffy <i...@ianduffy.ie<mailto:i...@ianduffy.ie>>
> Reply-To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <
> dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
> Date: Monday, November 24, 2014 at 10:56 AM
> To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <
> dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
> Subject: Re: Moving ec2stack and gstack to the cloudstack repos.
>
> Chiradeep,
>
> 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 <
> chiradeep.vit...@citrix.com<mailto:chiradeep.vit...@citrix.com>>
> wrote:
>
> 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 <run...@gmail.com<mailto:run...@gmail.com
> ><mailto:run...@gmail.com>>
> Reply-To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org
> ><mailto:dev@cloudstack.apache.org>" <
> dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org><mailto:
> dev@cloudstack.apache.org>>
> Date: Saturday, November 22, 2014 at 12:41 PM
> To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org><mailto:
> dev@cloudstack.apache.org>" <
> dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org><mailto:
> dev@cloudstack.apache.org>>
> Subject: Moving ec2stack and gstack to the cloudstack repos.
>
> Folks,
>
> Some of you may know of the existence of:
>
> https://github.com/BroganD1993/ec2stack
> https://github.com/NOPping/gstack
>
> 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 ?
>
> -Sebastien
>
>
>

Reply via email to