You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@jclouds.apache.org by Nirmal Fernando <ni...@wso2.com> on 2014/03/04 04:50:21 UTC

Re: Setting availability zone via placement group didn't work

Hi All,

Any help on this please?

On Thu, Feb 20, 2014 at 7:32 AM, Nirmal Fernando <ni...@wso2.com> wrote:

> Hey all,
>
> We are using jclouds 1.7 and it seems $subject. AFAIR this used to work
> previously. Was there any change along these lines?
>
> Sent via my mobile
> -- Nirmal --
>

-- 

Thanks & regards,
Nirmal

Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/

Re: Setting availability zone via placement group didn't work

Posted by Andrew Phillips <an...@apache.org>.

> Will try to reproduce the wire logs again.

That would be great - especially if you can get logs that show this  
*working* and then (newer version) *not working*...

Thanks!

ap

Re: Setting availability zone via placement group didn't work

Posted by Nirmal Fernando <ni...@wso2.com>.

Hi Andrew,

Thanks, yes I actually had a look at the wire logs, then I realized that
placement group had not made any effect on it.

Will try to reproduce the wire logs again.

On Wed, Mar 5, 2014 at 12:03 AM, Andrew Phillips <an...@apache.org> wrote:

> Now, there's no error, but jclouds seems to neglect this and spawn
>> instances in random zones.
>>
>
> Can you have a look at the wire and header logging to see if any options
> related to the placement group are actually being sent to EC2? If something
> looks wrong, could you post the relevant logs to a Gist or Pastie..?
>
> Thanks!
>
> ap
>

-- 

Thanks & regards,
Nirmal

Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/

Re: Setting availability zone via placement group didn't work

Posted by Andrew Phillips <an...@apache.org>.

> Now, there's no error, but jclouds seems to neglect this and spawn
> instances in random zones.

Can you have a look at the wire and header logging to see if any  
options related to the placement group are actually being sent to EC2?  
If something looks wrong, could you post the relevant logs to a Gist  
or Pastie..?

Thanks!

ap

Re: Setting availability zone via placement group didn't work

Posted by Nirmal Fernando <ni...@wso2.com>.

Hi Andrew,

The code that used to work is like below;

template.getOptions().as(AWSEC2TemplateOptions.class)
                    .placementGroup(zone);

Now, there's no error, but jclouds seems to neglect this and spawn
instances in random zones.

On Tue, Mar 4, 2014 at 7:23 PM, Andrew Phillips <an...@apache.org> wrote:

> Any help on this please?
>>
>
> The only relatively recent change to group logic in EC2 I can recall is
> JCLOUDS-242 [1], but that was about *security groups*, not AZs. Can you
> post a short example of a code snippet that used to work, and the error
> you're now seeing?
>
> Thanks!
>
> ap
>
> [1] https://issues.apache.org/jira/browse/JCLOUDS-242
>

-- 

Thanks & regards,
Nirmal

Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/

Re: Setting availability zone via placement group didn't work

Posted by Andrew Phillips <an...@apache.org>.

> Any help on this please?

The only relatively recent change to group logic in EC2 I can recall  
is JCLOUDS-242 [1], but that was about *security groups*, not AZs. Can  
you post a short example of a code snippet that used to work, and the  
error you're now seeing?

Thanks!

ap

[1] https://issues.apache.org/jira/browse/JCLOUDS-242