jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-1278) Implement the TemplateOptions.networks option in Azure ARM
Date Fri, 28 Apr 2017 07:04:08 GMT

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

ASF subversion and git services commented on JCLOUDS-1278:

Commit eeccc63d25319b902c9573cbfab8d738ccc41e32 in jclouds-labs's branch refs/heads/2.0.x
from [~nacx]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-labs.git;h=eeccc63 ]

JCLOUDS-1278: Allow to configure virtual machine NICs

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

View raw message