Ok, I'm fairly sure the issue only shows up when you use the ec2 API directly. When you go with aws-ec2, groupId is used instead of groupName and things work. That said, I've opened https://issues.apache.org/jira/browse/JCLOUDS-394 - I'd like to see us figure out exactly what to do with the ec2 API's security group handling before we push 1.7.0.
A. On Fri, Dec 6, 2013 at 1:18 PM, Andrew Bayer <andrew.ba...@gmail.com> wrote: > Ah, there is an issue - the security group name vs ID thing. I'll see what > I can figure out about fixing that. > > A. > > > On Fri, Dec 6, 2013 at 1:05 PM, Andrew Bayer <andrew.ba...@gmail.com>wrote: > >> I believe they should work without issue, but I'll need to double-check >> to be safe. Will do that this weekend. >> >> A. >> >> >> On Fri, Dec 6, 2013 at 8:32 AM, Andrew Phillips <andr...@apache.org>wrote: >> >>> Is jclouds EC2 support compromised by this? >>>> >>> >>> I'm not sure if this fully answers your question, Duncan, but with >>> jclouds you *can* specify the VPC into which you want your instance >>> launched, although (from memory) you need the AWS-specific API to do so. >>> >>> So I can't say whether things still work nicely "by default", but it >>> should still be possible to launch instances successfully even after this >>> change. >>> >>> Hope this helps! >>> >>> ap >>> >> >> >
