Quentin Pradet commented on LIBCLOUD-991:

Ah, you're right! So this functionality exists in two places: Ansible and 
Libcloud itself, and we were about to add it in a third place!

I think you need to use driver.ex_list(driver.list_nodes) instead of calling 
driver.list_nodes() directly. Then you get an iterator that you can use (no 
need to call page()). See 

I think Ansible should have done that too, but they probably did not see the 
GCEList feature, just like me. Sorry, even if I can approve pull requests, I'm 
still quite new to libcloud.

Feel free to close the issue if your problem is solved.

> Can not retrieve more than 500VM on Google cloud
> ------------------------------------------------
>                 Key: LIBCLOUD-991
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-991
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Compute
>         Environment: Google cloud project with more than 500VMs (python 3 and 
> last libcloud version AVL on pip)
>            Reporter: charles walker
>            Priority: Minor
> Today I notice that some of our VMs were not retrieve by our internal 
> toolings. After some investigation it seems that libcloud "list_nodes()" 
> method on google can only retrieve max 500VMs:
> [root@stackviewer-5cbcd8695-x964t /]# grep -o Vm response.log | wc -l
> 500
> when we have in reality around 750 VMs. So i had a quick look and my first 
> guess is that it comes from the call made by liblcoud using this REST API:
> [https://cloud.google.com/compute/docs/reference/rest/v1/instances/aggregatedList]
> with an optional argument "maxResults" that has a default value of 500 (which 
> seems also to be the max value BTW). I think i m on the good lead due to this 
> 500 limit mentioned in the doc and also observe on my side.
> I will have a deeper look but just quickly open this ticket in case other 
> people already saw this limit

This message was sent by Atlassian JIRA

Reply via email to