In v2, we use the link header during paginations to know when there are
more images available in the server that could be returned in the same
request. This way, it's possible to iterate over the generator returned
by list and consume the images in the server.
However, it's currently not possible to tell glanceclient the exact
number of images we want, which basically means that it'll *always* go
through the whole list of images in the server unless the limit is
implemented by the consumer.
Reviewed: https:/ /review. openstack. org/150416 /git.openstack. org/cgit/ openstack/ python- glanceclient/ commit/ ?id=93c9bc1fe0a e3f5c95395e7a88 3fdffcc79d7151
Committed: https:/
Submitter: Jenkins
Branch: master
commit 93c9bc1fe0ae3f5 c95395e7a883fdf fcc79d7151
Author: Flavio Percoco <email address hidden>
Date: Tue Jan 27 14:20:27 2015 +0100
Add a `--limit` parameter to list operations
In v2, we use the link header during paginations to know when there are
more images available in the server that could be returned in the same
request. This way, it's possible to iterate over the generator returned
by list and consume the images in the server.
However, it's currently not possible to tell glanceclient the exact
number of images we want, which basically means that it'll *always* go
through the whole list of images in the server unless the limit is
implemented by the consumer.
DocImpact 6320e5c7d94d03f cd1bbc93e33
Change-Id: I9f65a40d4eafda
Closes-bug: #1415035