Open Stack

In fact, both of you are correct. When passing '--limit -1' to the Nova
client, it will issue multiple requests to the API using the --marker
option until it receives no more data [1]. So the server-side limit
(osapi_max_limit parameter) isn't by-passed, it's just the client that
deals with it.
BR,
Simon

[1]
https://github.com/openstack/python-novaclient/blob/stable/mitaka/novaclient/v2/servers.py#L723-L755

On Thu, May 19, 2016 at 2:28 AM, David Medberry <openstack at medberry.net>
wrote:

> I don't think --marker does at all what I want. The --limit -1 does doe
> multiple successive queries (with a marker) automagically returning a
> single list as CLI output to nova list. That really IS what I want (and
> what some of our automation is written around.)
>
> Thanks!
>
> On Wed, May 18, 2016 at 5:26 PM, James Downs <egon at egon.cc> wrote:
>
>> On Wed, May 18, 2016 at 04:37:42PM -0600, David Medberry wrote:
>>
>> > It seems to bypass it... or I'm running into a LOWER limit
>> (undocumented).
>> > So help on  limit -1 says it is still limited by osapi_max_limit
>>
>> You're looking for:
>>
>> --marker <marker>             The last server UUID of the previous page;
>>                                 displays list of servers after "marker".
>>
>> This is much faster than increasing the size of results, at least in
>> sufficiently
>> large environments.
>>
>> Cheers,
>> -j
>>
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160519/1c6e100a/attachment.html>