[jira] [Commented] (JCLOUDS-381) Allow creating nodes through ComputeService with explicitly specified names

["Andrew Bayer (JIRA)" <ji...@apache.org>]

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

Andrew Bayer commented on JCLOUDS-381:
--------------------------------------

Well, that was actually stupid easy, I think. Initial PR up at https://github.com/jclouds/jclouds/pull/206, but I need to run live tests before I'm sure of it.

> Allow creating nodes through ComputeService with explicitly specified names
> ---------------------------------------------------------------------------
>
>                 Key: JCLOUDS-381
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-381
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-compute
>            Reporter: Andrew Bayer
>            Assignee: Andrew Bayer
>             Fix For: 1.8.0
>
>
> Currently, instance naming for nodes created through ComputeService.createNodesInGroup() etc uses a combination of the specified group name and GroupNamingConvention's unique suffix - generally that's a three character random string, but for EC2 it's the id string for the instance. While this is fine for many cases where the instance name doesn't need to be referenced directly by actual humans, say, it's a pain for those cases. Currently, you can work around this by creating instances through the per-api/provider clients/apis, or through some hacks for single instance creation through ComputeService utilizing provider-specific TemplateOptions classes, but there's no generalized way to get real control over the names given to instances through ComputeService. This should be possible.



--
This message was sent by Atlassian JIRA
(v6.1#6144)