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-1273) Cannot work with multiple resource groups in Azure ARM
Date Tue, 25 Apr 2017 22:13:04 GMT

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

ASF subversion and git services commented on JCLOUDS-1273:

Commit 40d29820ebd2f3fbece1f55e359e2ddf21f8bf56 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=40d2982 ]

JCLOUDS-1273/JCLOUDS-1226: Support multiple resource groups in ARM

> Cannot work with multiple resource groups in Azure ARM
> ------------------------------------------------------
>                 Key: JCLOUDS-1273
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1273
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-compute
>    Affects Versions: 2.0.1
>            Reporter: Ignasi Barrera
>            Assignee: Ignasi Barrera
>              Labels: azurecompute-arm
> Currently the Azure ARM provider assumes one resource group for each location, with a
name in the form: {{prefix-location}}. Whenever a resource is created or looked up, jclouds
builds that resource group name and uses it, ignoring all others.
> The {{ComputeService.listNodes}} implementation, however, lists the VMs in all resource
groups, and that causes conflicts, since the transformation functions and other parts of the
code only consider the "default" resource group.
> A more flexible approach should be used:
> * Let users configure the name of a default resource group to be used to create resources.
> * When listing existing resources, jclouds should try to find them in *any* resource
> * It would be good to change the IDs of the entities returned by jclouds from {{location/name}}
to {{resourcegroup/name}}, as it better identifies the resource.

This message was sent by Atlassian JIRA

View raw message