jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Gaul (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCLOUDS-488) vDC Limits cannot be forced when deploying new VMs
Date Tue, 27 Jan 2015 05:30:34 GMT

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

Andrew Gaul updated JCLOUDS-488:
    Labels: abiquo  (was: )

> vDC Limits cannot be forced when deploying new VMs
> --------------------------------------------------
>                 Key: JCLOUDS-488
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-488
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-labs
>    Affects Versions: 1.7.1
>            Reporter: Carlos García Ibáñez
>              Labels: abiquo
> We have recently migrated to the version 2.6 of the Abiquo API. In this version, in order
to force the vDC soft limits when deploying a new VM, the flag forceVdcLimits must be set
to true.
> Currently, the VirtualMachine class does not allow to specify such flag when invoking
the deploy() method. 
> Moreover, the underlying VirtualMachineTaskDto class used to execute the operation does
not accept this flag neither. But this class is located in the api-model-transport dependency,
and I wonder how this change request should be managed.

This message was sent by Atlassian JIRA

View raw message