Overriding the Security Group and Keypair Name

[Tom Barber]

Currently we create nodes like:

            NodeMetadata node = getOnlyElement(client.createNodesInGroup(groupName+userGroup, 1, templateBuilder.build()));


Which creates fun Security Group and Keypair names like:

jclouds#cloudBIbob#us-east-1

How do I/Can I assign a node to a preexisting security group, and how do I change the keypair name so i can get ride of the #'s and make it play nice with the Ruby URI parser?

Cheers

Tom

[magicaltrout]

Okay a quick google found me opt.as(EC2TemplateOptions.class).keyPair and opt.as(EC2TemplateOptions.class).securityGroups(securityGroups);

I assume this is because Security Groups and Keypairs are EC2 Variant specific and in other providers you'd have to do things differently when using the computeapi?

Cheers

Tom

[Adrian Cole]

yeah. right now, keypair is not something we have portable means to
apply across providers. I do think that we can carry the
Optional<KeyPairClient> design from OpenStack over to the
ComputeService at some point, though.

-A

> --
> You received this message because you are subscribed to the Google Groups
> "jclouds" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/jclouds/-/z92wLp8sWlQJ.
> To post to this group, send email to jcl...@googlegroups.com.
> To unsubscribe from this group, send email to
> jclouds+u...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/jclouds?hl=en.