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] [Commented] (JCLOUDS-1308) Azure ARM Default Network
Date Thu, 15 Jun 2017 16:22:00 GMT

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

Graeme Miller commented on JCLOUDS-1308:
----------------------------------------

hello, thank you both for your comments. I had a bash at adding back the default network,
you can see the changes [here|https://github.com/Graeme-Miller/jclouds-labs/commit/f32df4f9f0ec096024e49c7c35b082043c410eb5]
to get an idea of what I am thinking. Any comments would be appreciated.

[~nacx] for our use case, we want VMs in different groups to be deployed to the same network
by default (as was previously the case with Azure ARM). I totally understand that the current
implementation is better than the previous one, for the reasons you have stated- but it would
be cool if we could keep the default network approach as it was quite handy. 

> Azure ARM Default Network
> -------------------------
>
>                 Key: JCLOUDS-1308
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1308
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-compute
>    Affects Versions: 2.0.1
>            Reporter: Graeme Miller
>              Labels: azurecompute-arm
>
> 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
(v6.4.14#64029)

Mime
View raw message