jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Graeme Miller (JIRA)" <j...@apache.org>
Subject [jira] [Created] (JCLOUDS-1308) Azure ARM Default Network
Date Wed, 14 Jun 2017 14:39:00 GMT
Graeme Miller created JCLOUDS-1308:

             Summary: Azure ARM Default Network
                 Key: JCLOUDS-1308
                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1308
             Project: jclouds
          Issue Type: Bug
            Reporter: Graeme Miller

For Azure ARM, the default behaviour when creating a VM has changed with regards to VNETs/Subnets.

Previously, if no networking configuration was provided JClouds would create a default VNET
per region. The implementation of this can be found [here|https://github.com/jclouds/jclouds-labs/blob/4f50e7d65a6d7e1a3d06efcf557b363e55118238/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/compute/strategy/CreateResourceGroupThenCreateNodes.java#L147].
This was useful as it meant that a user could rely on VMs being able to access one another
on their subnet IP addresses, even when a network was not provided (I believe this is the
same as other clouds, but I am not too familiar with JClouds).

Now, when no networking configuration is provided we create a VNET per group id. For our usage,
this is a bit of a problem as it means by default each VM is getting it’s own network.

To see a history of these changes please see the commit [here|https://github.com/jclouds/jclouds-labs/commit/54e5ce50a43250c4f87414506b3bba4d8365284e]
that moved to having a VNET per resource group and then [here|https://github.com/jclouds/jclouds-labs/commit/dbadb279f14848f21879f7eb6c7136e1a5f11192],
that moved to using just the groupID.

I propose we go back to the old way, where we have a default resource group, VNET and subnet
per region. This will mean that by default, VMs will be able to speak to each other on there
private IPs. If that is not possible, could we have a template option that will allow us to
turn this behaviour on? 

I am very happy to work on the solution myself, but would like direction form the community
before investing too much time.

This message was sent by Atlassian JIRA

View raw message