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

Ignasi Barrera commented on JCLOUDS-416:
----------------------------------------

The TemplateBuilder should contain portable options to "find" a Template. That 
is: operating system, hardware configuration (cpu, ram, disk). Jclouds uses the 
template builder to find an Image in the provider that matches the "template 
spec" defined by the TemplateBuilder.

Which network should be used for the Nodes being deployed is not part of that 
process, and the natural place for such options is the TemplateOptions object. 
Properties there are used to "customize" the deployment once a Template has 
already been chosen. These options may include network configuration, bootstrap 
scripts, etc.

Most providers have their custom TemplateOptions object, and as [~abayer] 
suggests, the NovaTemplateOptions seems a good candidate.

However, there are several providers that have the concept of "network", and 
having a networkId option in the common TemplateOptions class could be a good 
idea:

* It could be used when deploying in an AWS VPC.
* It could be used in the Abiquo provider when addressing: 
https://issues.apache.org/jira/browse/JCLOUDS-330
* CloudSigma already has private networks, and that would help configuring 
which IPs are selected for the deployed Nodes.
* OpenStack clouds seem to fit there too.

Could it be worth adding the networkId property directly in the portable 
TemplateOptions class?

> 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)

Reply via email to