GroupNamingConvention is hard to work around

[abayer]

Or at least there aren't good examples of how to work around it. If you want/need more control over the names of the instances you're creating, createNodesInGroup is not particularly flexible - you can cheat this with some providers (i.e., the underlying createNodeWithGroupEncodedIntoName in CloudStackComputeServiceAdapter ignores the group argument, or with EC2, you can set the "Name" tag in the template options userMetadata to what you want the instance name to be, so long as you're only creating one instance from the Template), but it's not easy to do generally, at least so far as I can tell.

So I'd like it if either GroupNamingConvention was easier to punch into doing what I want, or at least if there were some examples of overriding the default.

[demobox]

Also recently came up on IRC.

[demobox]

See also https://github.com/jclouds/jclouds/issues/1499#issuecomment-16061941