You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@libcloud.apache.org by "Michal Galet (JIRA)" <ji...@apache.org> on 2012/05/02 10:38:57 UTC

[dev] [jira] [Updated] (LIBCLOUD-183) Implement support for vCloud v1.5

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

Michal Galet updated LIBCLOUD-183:
----------------------------------

    Attachment: LIBCLOUD-183-vcloud_1_5-5fixed.patch

Here is a fixed version of the patch: LIBCLOUD-183-vcloud_1_5-5fixed.patch. The problem was caused by a difference between galet/libcloud/trunk and apache/libcloud/trunk. This has been fixed so it shouldn't happen any more.

Applying the fixed patch succeeded on svn repo:
$ svn patch LIBCLOUD-183-vcloud_1_5-5fixed.patch
U         libcloud/compute/drivers/vcloud.py
U         test/compute/fixtures/vcloud_1_5/api_org_96726c78_4ae3_402f_b08b_7a78c6903d2a.xml
U         test/compute/fixtures/vcloud_1_5/api_vApp_vapp_8c57a5b6_e61b_48ca_8a78_3b70ee65ef6a.xml
A         test/compute/fixtures/vcloud_1_5/api_vApp_vapp_8c57a5b6_e61b_48ca_8a78_3b70ee65ef6b.xml
A         test/compute/fixtures/vcloud_1_5/api_vApp_vm_test.xml
U         test/compute/fixtures/vcloud_1_5/api_vdc_3d9ae28c_1de9_4307_8107_9356ff8ba6d0.xml
A         test/compute/fixtures/vcloud_1_5/get_api_vApp_vm_test_virtualHardwareSection_cpu.xml
A         test/compute/fixtures/vcloud_1_5/get_api_vApp_vm_test_virtualHardwareSection_disks.xml
A         test/compute/fixtures/vcloud_1_5/get_api_vApp_vm_test_virtualHardwareSection_memory.xml
A         test/compute/fixtures/vcloud_1_5/put_api_vApp_vm_test_virtualHardwareSection_cpu.xml
A         test/compute/fixtures/vcloud_1_5/put_api_vApp_vm_test_virtualHardwareSection_disks.xml
A         test/compute/fixtures/vcloud_1_5/put_api_vApp_vm_test_virtualHardwareSection_memory.xml
U         test/compute/test_vcloud.py

All tests are passing.
                
> Implement support for vCloud v1.5
> ---------------------------------
>
>                 Key: LIBCLOUD-183
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-183
>             Project: Libcloud
>          Issue Type: New Feature
>          Components: Compute
>    Affects Versions: 0.9.1
>            Reporter: Michal Galet
>         Attachments: LIBCLOUD-183-networks-typo.patch, LIBCLOUD-183-vcloud_1_5-2.patch, LIBCLOUD-183-vcloud_1_5-3.patch, LIBCLOUD-183-vcloud_1_5-4.patch, LIBCLOUD-183-vcloud_1_5-5.patch, LIBCLOUD-183-vcloud_1_5-5fixed.patch, LIBCLOUD-183-vcloud_1_5.patch, create_node_ex_net.recommended.xml, create_node_ex_net.test.txt
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> The current version of libcloud has support only for vCloud v0.8 and is incompatible with the recent version of vCloud v1.5. 
> It would be nice if the newer version was supported by libcloud: http://communities.vmware.com/thread/302725

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira