You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@libcloud.apache.org by "Trevor Powell (RMS) (JIRA)" <ji...@apache.org> on 2013/04/23 21:49:17 UTC

[dev] [jira] [Updated] (LIBCLOUD-320) vCloud 5.1 vm memory Support / Repatch

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

Trevor Powell (RMS) updated LIBCLOUD-320:
-----------------------------------------

    Attachment: libcloud-320.patch

Here is another patch against the current code base. Have a look :)
                
> vCloud 5.1 vm memory Support  / Repatch
> ---------------------------------------
>
>                 Key: LIBCLOUD-320
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-320
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Compute
>    Affects Versions: 0.12.3
>            Reporter: Trevor Powell (RMS)
>              Labels: vcloud
>         Attachments: libcloud-320.patch
>
>
> In LIBCLOUD-314 a patch was submitted for memory support for VCD 5.1 .
> It seems the patch that was submitted was not correctly inserted into the code base.
> Submitted patch: https://issues.apache.org/jira/secure/attachment/12578585/vcd5_1.patch
> Patch in the code base: https://svn.apache.org/viewvc/libcloud/trunk/libcloud/compute/drivers/vcloud.py?r1=1467555&r2=1467554&pathrev=1467555
> If you notice, the submitted patch has
> +            elif api_version == '5.1':
> +                cls = VCloud_5_1_NodeDriver
> Where as what was actually patched has 
> +            elif api_version == '5.1':
> +                cls = VCloud_1_5_NodeDriver

--
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