[
https://issues.apache.org/jira/browse/LIBCLOUD-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16436112#comment-16436112
]
Quentin Pradet commented on LIBCLOUD-991:
-----------------------------------------
You're right: page() is needed. I have to agree that it's surprising, and I
probably would not have done it this way: libcloud should abstract those
things. At the same time GCEList and ex_list are quite powerful, and they
should continue to work in the next versions. I don't know if it's possible to
extend list_nodes to retrieve all nodes while not breaking any existing code?
I won't be able to help here. Sorry! You could take it to the
d...@libcloud.apache.org mailing list to see what the more experienced libcloud
contributors think.
> 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
(v7.6.3#76005)
