You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by "Ignasi Barrera (JIRA)" <ji...@apache.org> on 2017/04/28 07:06:04 UTC

[jira] [Resolved] (JCLOUDS-1278) Implement the TemplateOptions.networks option in Azure ARM

     [ https://issues.apache.org/jira/browse/JCLOUDS-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ignasi Barrera resolved JCLOUDS-1278.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.2
                   2.1.0

> Implement the TemplateOptions.networks option in Azure ARM
> ----------------------------------------------------------
>
>                 Key: JCLOUDS-1278
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1278
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-compute
>    Affects Versions: 2.0.1
>            Reporter: Ignasi Barrera
>            Assignee: Ignasi Barrera
>              Labels: azurecompute-arm
>             Fix For: 2.1.0, 2.0.2
>
>
> The Azure ARM compute service does not implement the {{TemplateOptions.networks}} option. It creates a default network with a range taken from the context properties and a subnet in it, and all created nodes are assigned there.
> Having a default network and subnet is fine when users don't provide networking information, but we should support the {{TemplateOptions.networks}} option to connect the VMs to the subnets with the given IDs. We could also support more sophisticated networking options in the {{AzureTemplateOptions}} class to let users configure not only the subnet but also the ip configuration (static, dynamic), as allowed by the provider.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)