Hi Adrian - I was wondering if you were able to run the jclouds tests on
the public CS instance? I might be able to find some machines to run the
tests on but it will be internal for now. We're happy to publish the
results. Let me know if there is anything required.
On Sat, Aug 04, 2012 at 01:50:0
Thanks! I look forward to it.
-A
On Aug 3, 2012 6:45 PM, "David Nalley" wrote:
> On Fri, Aug 3, 2012 at 7:55 PM, Adrian Cole
> wrote:
> > Certainly, a public endpoint is easier on devs than a work-in-progress
> > devstack. I'm not sure I will have time to work through that process in
> > the s
On Fri, Aug 3, 2012 at 7:55 PM, Adrian Cole wrote:
> Certainly, a public endpoint is easier on devs than a work-in-progress
> devstack. I'm not sure I will have time to work through that process in
> the short term. I am happy to help test an existing endpoint and maintain
> tests, though.
>
> -
We've got two weeks to get it in good shape -- sounds
> > like
> > > > plenty to me!
> > > >
> > > > Ewan.
> > > >
> > > > > -Original Message-
> > > > > From: fernc...@gmail.com [mailto:fernc...@gmail
l Message-
> > > > From: fernc...@gmail.com [mailto:fernc...@gmail.com] On Behalf Of
> > > > Adrian Cole
> > > > Sent: Thursday, August 02, 2012 12:54 PM
> > > > To: cloudstack-dev@incubator.apache.org
> > > > Cc: Prachi Damle
> >
Hi Chip,
I have committed the change to remove WSDLs from the source tree.
-Prachi
-Original Message-
From: Chip Childers [mailto:chip.child...@sungard.com]
Sent: Thursday, August 02, 2012 4:51 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: ec2 API compatibility (WSDL vs Query
t; >
> > > Ewan.
> > >
> > > > -Original Message-
> > > > From: fernc...@gmail.com [mailto:fernc...@gmail.com] On Behalf Of
> > > > Adrian Cole
> > > > Sent: Thursday, August 02, 2012 12:54 PM
> > > > To: cloudst
On Thu, Aug 2, 2012 at 7:41 PM, Prachi Damle wrote:
> After removing the AWS WSDLs from source, I tested that awsapi EC2 builds
> fine and basic EC2 calls using the tools worked.
> So looks like we can do away with the WSDL files from source tree without
> harm.
>
> -Prachi
Great! Can you let
PM
To: cloudstack-dev@incubator.apache.org
Cc: Prachi Damle
Subject: Re: ec2 API compatibility (WSDL vs Query)
Good point, Kelven.
I think there will be no shortage of bindings. Except .NET, I know there is at
least one binding to EC2 Query api for each language you mention. Also
remember many
iginal Message-
> >> From: Duncan Johnston Watt
> >> [mailto:duncan.johnstonw...@cloudsoftcorp.com]
> >> Sent: Thursday, August 02, 2012 1:05 PM
> >> To: cloudstack-dev@incubator.apache.org
> >> Cc: Prachi Damle
> >> Subject: Re: ec2 API compatibili
r tool that
>needs it.
>
>-kevin
>
>
>> -Original Message-
>> From: Duncan Johnston Watt
>> [mailto:duncan.johnstonw...@cloudsoftcorp.com]
>> Sent: Thursday, August 02, 2012 1:05 PM
>> To: cloudstack-dev@incubator.apache.org
>> Cc: Prachi Daml
ursday, August 02, 2012 1:05 PM
> To: cloudstack-dev@incubator.apache.org
> Cc: Prachi Damle
> Subject: Re: ec2 API compatibility (WSDL vs Query)
>
> Adrian/All
>
> +1 to focusing on Query API.
>
> Best
>
> Duncan
>
> On 2 August 2012 22:01, Adrian Cole wrote
t; > > Adrian Cole
> > > Sent: Thursday, August 02, 2012 12:54 PM
> > > To: cloudstack-dev@incubator.apache.org
> > > Cc: Prachi Damle
> > > Subject: RE: ec2 API compatibility (WSDL vs Query)
> > >
> > > Right, so here's the opportu
e
> plenty to me!
>
> Ewan.
>
> > -Original Message-
> > From: fernc...@gmail.com [mailto:fernc...@gmail.com] On Behalf Of
> > Adrian Cole
> > Sent: Thursday, August 02, 2012 12:54 PM
> > To: cloudstack-dev@incubator.apache.org
> > Cc: Prachi Damle
>
t; Sent: Thursday, August 02, 2012 12:54 PM
> To: cloudstack-dev@incubator.apache.org
> Cc: Prachi Damle
> Subject: RE: ec2 API compatibility (WSDL vs Query)
>
> Right, so here's the opportunity!
>
> Clear out 50 bugs and a legacy of code to support, and replace them
>
...@eu.citrix.com]
> Sent: Thursday, August 02, 2012 10:57 AM
> To: cloudstack-dev@incubator.apache.org
> Cc: Prachi Damle
> Subject: RE: ec2 API compatibility (WSDL vs Query)
>
> The only metric that we have (to my knowledge) is that the Query API was
> broken for a long time (a pr
200 +
Defects can be found in JIRA
Thanks
/Sudha
-Original Message-
From: Ewan Mellor [mailto:ewan.mel...@eu.citrix.com]
Sent: Thursday, August 02, 2012 10:57 AM
To: cloudstack-dev@incubator.apache.org
Cc: Prachi Damle
Subject: RE: ec2 API compatibility (WSDL vs Query)
The only metric
ter.
Ewan.
> -Original Message-
> From: fernc...@gmail.com [mailto:fernc...@gmail.com] On Behalf Of
> Adrian Cole
> Sent: 02 August 2012 10:29
> To: cloudstack-dev@incubator.apache.org
> Cc: Prachi Damle
> Subject: Re: ec2 API compatibility (WSDL vs Query)
>
> Do we have
-Original Message-
From: Chip Childers [mailto:chip.child...@sungard.com]
Sent: Thursday, August 02, 2012 10:35 AM
To: cloudstack-dev@incubator.apache.org
Cc: Prachi Damle
Subject: Re: ec2 API compatibility (WSDL vs Query)
On Thu, Aug 2, 2012 at 1:27 PM, Ewan Mellor wrote:
>
On Thu, Aug 2, 2012 at 1:27 PM, Ewan Mellor wrote:
> One correction: Prachi is a "she" ;-)
How rude of me. Apologies Prachi!
k and has never worked". If someone can convince me that
> >> > it will be working in the next 2 weeks (1 week of open development, 1
> >> > week stability and bugfixing) then I'm happy to take that step and
> >> > remove the SOAP API and declare 4
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: 02 August 2012 10:12
> To: cloudstack-dev@incubator.apache.org
> Cc: Prachi Damle
> Subject: Re: ec2 API compatibility (WSDL vs Query)
>
> Ewan,
>
> First, thanks fo
lly get what they're asking for. If the group decides that it
> wants to slip to October or beyond, then that's a decision that's open to
> them.
>
> Ewan.
>
>
>
>> -Original Message-----
>> From: fernc...@gmail.com [mailto:fernc...@gmail.com] On Behalf
27;s a decision that's open to them.
Ewan.
> -Original Message-
> From: fernc...@gmail.com [mailto:fernc...@gmail.com] On Behalf Of
> Adrian Cole
> Sent: 02 August 2012 09:14
> To: cloudstack-dev@incubator.apache.org
> Cc: Prachi Damle
> Subject: Re: ec2 API com
next two
> weeks then we're talking about slipping the release, and no-one wants that.
>
> Ewan.
>
> > -Original Message-
> > From: Chip Childers [mailto:chip.child...@sungard.com]
> > Sent: 02 August 2012 08:37
> > To: cloudstack-dev@incubator.apa
; Sent: 02 August 2012 08:37
> To: cloudstack-dev@incubator.apache.org
> Cc: Prachi Damle
> Subject: Re: ec2 API compatibility (WSDL vs Query)
>
> From Chiradeep's note:
>
> > Currently the EC2 API layer implements both the WSDL interface as well
> > as the Query API.
>
s [mailto:chip.child...@sungard.com]
> >> Sent: 02 August 2012 07:58
> >> To: cloudstack-dev@incubator.apache.org
> >> Subject: Re: ec2 API compatibility (WSDL vs Query)
> >>
> >> On Thu, Aug 2, 2012 at 10:56 AM, Adrian Cole
> >> wrote:
> >> >
nding?
-chip
On Thu, Aug 2, 2012 at 11:33 AM, Ewan Mellor wrote:
>> -Original Message-
>> From: Chip Childers [mailto:chip.child...@sungard.com]
>> Sent: 02 August 2012 07:58
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: ec2 API compatibility (WS
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: 02 August 2012 07:58
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: ec2 API compatibility (WSDL vs Query)
>
> On Thu, Aug 2, 2012 at 10:56 AM, Adrian Cole
> wrote:
>
On Thu, Aug 2, 2012 at 10:56 AM, Adrian Cole wrote:
> Just curious.
>
> If this is the first apache release, and cloudbridge was formerly in a
> different repo, why don't we just rip out the SOAP interface? That's a
> heck of a lot simpler than deprecating the first version of something.
>
> -A
Just curious.
If this is the first apache release, and cloudbridge was formerly in a
different repo, why don't we just rip out the SOAP interface? That's a
heck of a lot simpler than deprecating the first version of something.
-A
On Aug 2, 2012 5:51 AM, "Chip Childers" wrote:
> On Wed, Aug 1,
On Wed, Aug 1, 2012 at 9:09 PM, Chiradeep Vittal
wrote:
> It appears that the WSDL-based toolset is being deprecated by AWS [1].
>
> Currently the EC2 API layer implements both the WSDL interface as well as
> the Query API.
> However the Query API is not well tested.
> Furthermore the implemented
I agree as well.
It would be better to spend time on supporting a newer query API version.
On Aug 1, 2012, at 11:09 PM, David Nalley wrote:
> On Wed, Aug 1, 2012 at 9:09 PM, Chiradeep Vittal
> wrote:
>> It appears that the WSDL-based toolset is being deprecated by AWS [1].
>>
>> Currently the
On Wed, Aug 1, 2012 at 9:09 PM, Chiradeep Vittal
wrote:
> It appears that the WSDL-based toolset is being deprecated by AWS [1].
>
> Currently the EC2 API layer implements both the WSDL interface as well as
> the Query API.
> However the Query API is not well tested.
> Furthermore the implemented
+1 (non-binding)
there's no value to maintaining crufty code no-one wants
On Wed, Aug 1, 2012 at 6:09 PM, Chiradeep Vittal <
chiradeep.vit...@citrix.com> wrote:
> It appears that the WSDL-based toolset is being deprecated by AWS [1].
>
> Currently the EC2 API layer implements both the WSDL inter
It appears that the WSDL-based toolset is being deprecated by AWS [1].
Currently the EC2 API layer implements both the WSDL interface as well as
the Query API.
However the Query API is not well tested.
Furthermore the implemented WSDL is of 2010-08 vintage.
Does it make sense to likewise deprecat
36 matches
Mail list logo
