[jira] [Commented] (JCLOUDS-416) TemplateBuilder is lacking network id support

["Everett Toews (JIRA)" <ji...@apache.org>]

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

Everett Toews commented on JCLOUDS-416:
---------------------------------------

TemplateBuilder is part of the cloud agnostic jclouds-compute layer. Being part of the jclouds-compute layer means that several clouds would have to implement it. Or it could be implemented as an extension, like the [SecurityGroupExtension|https://github.com/jclouds/jclouds/blob/master/compute/src/main/java/org/jclouds/compute/extensions/SecurityGroupExtension.java].

You mention Rackspace specifically in the description. Is your use case already covered by using [CreateServerOptions.networks()|http://javadocs.jclouds.cloudbees.net/org/jclouds/openstack/nova/v2_0/options/CreateServerOptions.Builder.html#networks(java.lang.Iterable)] when creating a Server?

Would this feature really need to be part of the jclouds-compute layer?

If so, can we get a little more detail about what you're trying to accomplish?

Could you give us a code snippet of how you would like to use such a feature?



> TemplateBuilder is lacking network id support
> ---------------------------------------------
>
>                 Key: JCLOUDS-416
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-416
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-compute
>    Affects Versions: 1.7.0
>            Reporter: Izek Greenfield
>              Labels: features, openstack, rackspace
>
> You can choose which network to assign to the new VM (Rackspace).
> need to add  public and internal networks.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)