You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Ignasi Barrera (JIRA)" <ji...@apache.org> on 2013/08/01 11:31:48 UTC
[jira] [Resolved] (JCLOUDS-208) Datacenter/enterprise limitation
procedure changes in Abiquo version 2.4
[ https://issues.apache.org/jira/browse/JCLOUDS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ignasi Barrera resolved JCLOUDS-208.
------------------------------------
Resolution: Fixed
> Datacenter/enterprise limitation procedure changes in Abiquo version 2.4
> ------------------------------------------------------------------------
>
> Key: JCLOUDS-208
> URL: https://issues.apache.org/jira/browse/JCLOUDS-208
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-labs
> Affects Versions: 1.6.1
> Environment: Abiquo server version 2.4
> Reporter: Carlos García Ibáñez
> Assignee: Ignasi Barrera
> Priority: Minor
> Labels: abiquo
> Fix For: 1.7.0, 1.6.2
>
> Attachments: JCLOUDS-208.patch
>
>
> The current release of the jclouds-labs/abiquo framework does not support the new procedure for establishing limitations between enterprises and physical datacenters.
> Up to Abiquo version 2.3 this was achieved by sending the id of the datacenter as a query string parameter of the URL the limit creation request was posted to:
> http://<abiquo_server>/api/admin/enterprises/166/limits?datacenter=1
> But from version 2.4 that's not the way any more: now the relation is established by means of a "datacenter" link within the representation of the limit itself.
> <link rel="datacenter" href="http://<abiquo_server>/api/admin/datacenters/1" />
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira