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-1311) Azure ARM: Create network if it does not exist
Date Fri, 16 Jun 2017 14:59:00 GMT

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

Graeme Miller commented on JCLOUDS-1311:
----------------------------------------

So, I get where you are coming from and that's fine- I am already exploring other options.

However, just to be clear, I am not suggesting we allow more things to be configurable for
Azure, only that we change the config so that is is easier to use and understand. Currently,
for Azure there is a provider specific option called subnet. This is a resource id in a format
like:
/subscriptions/sub-91121212/resourceGroups/jclouds-default-resource-group-northeurope/providers/Microsoft.Network/virtualNetworks/jclouds-default-network-northeurope/subnets/jclouds-default-subnet-northeurope

>From this we extract resource group, network and subnet, link to code [here|https://github.com/jclouds/jclouds-labs/blob/master/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/compute/strategy/CreateResourcesThenCreateNodes.java#L226].


My suggestion was to allow users to specify resource, network and subnet directly, rather
than specifying them in the resource ID format above. This seems to be more user-friendly
in my opinion, and doesn't rely on decoding the URL to extract the config.

---------------------------------------------------------------
To understand why I suggested the above, I want the ability to create a network if it doesn't
exist. It would be weird if we did have that functionality, but you had to specify the network/subnet
name by using the resource ID format as you would have to create the URL.

---------------------------------------------------------------

However, as I said above, I am exploring other issues. If changing how we specify the config,
and creating networks by default is not acceptable that's fine, happy to close the ticket
and move on.



> Azure ARM: Create network if it does not exist
> ----------------------------------------------
>
>                 Key: JCLOUDS-1311
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1311
>             Project: jclouds
>          Issue Type: Improvement
>            Reporter: Graeme Miller
>
> An initial discussion was had in JCLOUDS-1308.
> Currently, when deploying a VM to Azure, a user can specify a Network and Subnet by specifying
a subnet resource ID (the network ID is retrieved from the resource id). If this network and
subnet does not exist the deployment fails.
> I would like to modify the Azure Arm code to create the network if it does not exist.
To achieve this I propose:
> *) Modifying IpOptions so that a user can specify a NetworkName, SubnetName and NetworkResourceGroup
(optional, will use the groups resource group if not specified)
> *) We either replace the current subnet config (which is actually a subnet resource id)
or we keep it and make it mutually exclusive with the above
> *) If the Network/Subnet does not exist we create it in the NetworkResourceGroup specified.
We would do that in the normalizeNetworkOptions method [here|https://github.com/jclouds/jclouds-labs/blob/master/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/compute/strategy/CreateResourcesThenCreateNodes.java#L219]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message