[ 
https://issues.apache.org/jira/browse/LIBCLOUD-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649019#comment-13649019
 ] 

ASF subversion and git services commented on LIBCLOUD-323:
----------------------------------------------------------

Commit 1479041 from [~kami]
[ https://svn.apache.org/r1479041 ]

Various improvements and bug-fixes in the VCloud driver.

Contributed by Michel Samia, part of LIBCLOUD-323.
                
> Make vCloud driver more robust
> ------------------------------
>
>                 Key: LIBCLOUD-323
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-323
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Compute
>    Affects Versions: 0.12.3
>            Reporter: Michel Samia
>            Priority: Minor
>         Attachments: LIBCLOUD-323_withTests.patch, 
> LIBCLOUD-vcloud_minor_patches.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> There are several small and easy-to-fix problems in VCloud driver:
> # VCloud_1_5_NodeDriver._validate_vm_memory(): now there is a specialized 
> list of acceptable Virtual memory sizes for vCloud 1.5, but it seems that 
> these values don't work in version 1.5. The old values from vCloud 0.8 work 
> well
> # VCloudNodeDriver.ex_list_nodes(): because node listing has two phases (in 
> first phase we send request for getting URLs of all the VMs and in the second 
> we send one request per VM for getting all info about the VM), there can 
> happen a situation where some VM is deleted between these two phases. Then we 
> want to ignore this VM and we don't want to report any error (=raise an 
> exception). The existing checker of this situation is too generic and can 
> silence any other exception satisfying some other conditions
> # VCloud_1_5_NodeDriver._to_node(): the OS XML element is not required, so 
> when not present, we cannot get its attributes
> We have fixed all these three problems in the patch attached below

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

Reply via email to