* 'master' of github.com:jclouds/jclouds: (31 commits)
fixed keypair on nova and added test
First set of api's for opsource
First set of api's for opsource
Issue 830: Update client get methods to use new error handler
README.md - improved
README.md
Issue 888: consolidate code that addresses naming conventions, using hyphen as default delimiter
organize imports
removed deprecated RunScriptOptions & TemplateOptions
added new properties object
passwordAuthentication is now default for keystone
refactored properties objects to be consistent w/keystone
corrected spacing and new lines for README.md
updated readme.md
Intermittent JAXB error
Issue 830: Use ResourceNotFoundException
Issue 830: Make RasdItemsList implement Set
Issue 830: Tidy up client imports and javadoc
Issue 830: Tidy up domain object imports and remove unnecessary annotations
Issue 830: Use XmlElementWrapper annotation where possible
...
When the security group is not generated by jclouds (e.g. when
using a custom group, or when in a VPC which generally requires
its own security groups), the group name to launch nodes into is
lost, since it is parsed from the generated security group ID.
This patch introduces a very local workaround: try to parse the
name from the key name, which if generated by jclouds has a format
that is very similar to the generated security group ID.
While probably not the ideal solution for persisting the group
name either (using user metadata might be), this fixes a blocking
issue for scenarios where you can't use a generated security group
ID (using a VPC in our case), but you can use a generated key pair
name.
Also it shouldn't interfere with existing usage: if a name can be
parsed from the security group, that is used, and if the key name
is not generated, the behaviour remains as it currently is (group
name is null if it can't be parsed from the security group).
