jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignasi Barrera (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCLOUDS-208) [jclouds-abiquo] - Datacenter/enterprise limitation procedure changes in Abiquo version 2.4
Date Thu, 01 Aug 2013 09:25:48 GMT

     [ https://issues.apache.org/jira/browse/JCLOUDS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Ignasi Barrera updated JCLOUDS-208:

    Assignee: Ignasi Barrera
> [jclouds-abiquo] - Datacenter/enterprise limitation procedure changes in Abiquo version
> -------------------------------------------------------------------------------------------
>                 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
> 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

View raw message