jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-394) EC2 Security Group logic won't work in non-default VPC
Date Tue, 10 Dec 2013 00:38:07 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843762#comment-13843762

ASF subversion and git services commented on JCLOUDS-394:

Commit b351406fc934f707d0dc41a0eb179413ea08bbd9 in branch refs/heads/pr-44-alternative from
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=b351406 ]

JCLOUDS-394. Add note to ec2 README in re: live tests and new accounts

> EC2 Security Group logic won't work in non-default VPC
> ------------------------------------------------------
>                 Key: JCLOUDS-394
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-394
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-compute
>    Affects Versions: 1.6.3
>            Reporter: Andrew Bayer
>            Priority: Blocker
>             Fix For: 1.7.0, 1.6.4
> Due to the change EC2 just made such that all new accounts are only in EC2-VPC for security
groups, with their own default VPC set up for each account, all of our code that uses group
*names* for parameters etc will fail for new accounts. This works (I'm pretty sure) from aws-ec2
where we're specifying groupId instead of groupName in a lot of places (hopefully all?), but
I think we need to answer how to deal with this for the EC2 api proper as well.

This message was sent by Atlassian JIRA

View raw message