Re: Moving ec2stack and gstack to the cloudstack repos.

2014-11-27 Thread Sebastien Goasguen
.apache.org<mailto:dev@cloudstack.apache.org>" > mailto:dev@cloudstack.apache.org>> > Subject: Re: Moving ec2stack and gstack to the cloudstack repos. > > I think unit tests are great for type checking and the like, but are > there any integration tests? > > At

Re: Moving ec2stack and gstack to the cloudstack repos.

2014-11-26 Thread Chiradeep Vittal
<mailto:dev@cloudstack.apache.org>" mailto:dev@cloudstack.apache.org>> Date: Wednesday, November 26, 2014 at 4:46 AM To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" mailto:dev@cloudstack.apache.org>> Subject: Re: Moving ec2stack and gstac

Re: Moving ec2stack and gstack to the cloudstack repos.

2014-11-26 Thread sebgoa
gt; > > > > > > > > -- Original ------ > From: "Sebastien Goasguen"; > Date: Tue, Nov 25, 2014 06:29 AM > To: "dev"; > > Subject: Re: Moving ec2stack and gstack to the cloudstack repos. > > &g

Re: Moving ec2stack and gstack to the cloudstack repos.

2014-11-26 Thread sebgoa
d, without tests and which state in >> the release is unknown >> >> and >> >> -a new implementation < 6 months old, smaller code base, up to date with >> AWS version number, tested manually with boto, eutester and awscli and with >> 99% unit test coverage. >>

Re: Moving ec2stack and gstack to the cloudstack repos.

2014-11-26 Thread Ian Duffy
t; -- > Regards, > > > ChunFeng > > > > > > > > > > ---------- Original -------------- > From: "Sebastien Goasguen"; > Date: Tue, Nov 25, 2014 06:29 AM > To: "dev"; > > Subject: Re: Moving ec2stack and gstack to th

Re: Moving ec2stack and gstack to the cloudstack repos.

2014-11-25 Thread ChunFeng
udstack.apache.org>" > mailto:dev@cloudstack.apache.org>> > Date: Monday, November 24, 2014 at 1:36 PM > To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" > mailto:dev@cloudstack.apache.org>> > Subject: Re: Moving ec2stack and gsta

Re: Moving ec2stack and gstack to the cloudstack repos.

2014-11-25 Thread Carlos Reategui
>> > > Reply-To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" > mailto:dev@cloudstack.apache.org>> > > Date: Monday, November 24, 2014 at 1:36 PM > > To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" < > dev@clou

Re: Moving ec2stack and gstack to the cloudstack repos.

2014-11-25 Thread Chiradeep Vittal
>" mailto:dev@cloudstack.apache.org>> Subject: Re: Moving ec2stack and gstack to the cloudstack repos. 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

Re: Moving ec2stack and gstack to the cloudstack repos.

2014-11-24 Thread Ian Duffy
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

Re: Moving ec2stack and gstack to the cloudstack repos.

2014-11-24 Thread Sebastien Goasguen
ot; > mailto:dev@cloudstack.apache.org>> > Date: Monday, November 24, 2014 at 1:36 PM > To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" > mailto:dev@cloudstack.apache.org>> > Subject: Re: Moving ec2stack and gstack to the cloudstack re

Re: Moving ec2stack and gstack to the cloudstack repos.

2014-11-24 Thread Chiradeep Vittal
:dev@cloudstack.apache.org>" mailto:dev@cloudstack.apache.org><mailto:dev@cloudstack.apache.org>> Date: Monday, November 24, 2014 at 11:39 AM To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org><mailto:dev@cloudstack.apache.org>" mailto:dev@cloud

Re: Moving ec2stack and gstack to the cloudstack repos.

2014-11-24 Thread Sebastien Goasguen
ovember 24, 2014 at 11:39 AM > To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" > mailto:dev@cloudstack.apache.org>> > Subject: Re: Moving ec2stack and gstack to the cloudstack repos. > > > On Nov 24, 2014, at 7:19 PM, Chiradeep Vittal > mailto:c

Re: Moving ec2stack and gstack to the cloudstack repos.

2014-11-24 Thread Chiradeep Vittal
apache.org>" mailto:dev@cloudstack.apache.org>> Date: Monday, November 24, 2014 at 11:39 AM To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" mailto:dev@cloudstack.apache.org>> Subject: Re: Moving ec2stack and gstack to the cloud

Re: Moving ec2stack and gstack to the cloudstack repos.

2014-11-24 Thread sebgoa
On Nov 24, 2014, at 7:19 PM, Chiradeep Vittal 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 > un

Re: Moving ec2stack and gstack to the cloudstack repos.

2014-11-24 Thread sebgoa
e.org>> > Date: Monday, November 24, 2014 at 10:56 AM > To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" > mailto:dev@cloudstack.apache.org>> > Subject: Re: Moving ec2stack and gstack to the cloudstack repos. > > Chiradeep, >

Re: Moving ec2stack and gstack to the cloudstack repos.

2014-11-24 Thread Chiradeep Vittal
@cloudstack.apache.org<mailto: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

Re: Moving ec2stack and gstack to the cloudstack repos.

2014-11-24 Thread Ian Duffy
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 wrote: > Seems legit, but from (bitter) experience, there is no point in a > compatible API layer unless some

Re: Moving ec2stack and gstack to the cloudstack repos.

2014-11-24 Thread 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, thi