| 2019-02-01 02:25:56 |
Yikun Jiang |
description |
Currently, volume transfer API does not support pagination. As in large scale deployment the number of migration records can be also very large and querying them all can lead to performance bottleneck, it will be very useful to support pagination
Also, there is a unexpected behavior, we can only get max to CONF.osapi_max_limit records when we list volume transfers under the current implementation, that means if we have more than CONF.osapi_max_limit items in db, we can only get first CONF.osapi_max_limit record.
So, we should support volume transfer pagination.
[1] https://github.com/openstack/cinder/blob/master/cinder/api/contrib/volume_transfer.py#L66
[2] https://github.com/openstack/cinder/blob/c0efaa1/cinder/api/common.py#L136 |
Currently, volume transfer API does not support pagination. As in large scale deployment the number of migration records can be also very large and querying them all can lead to performance bottleneck, it will be very useful to support pagination
Also, there is a unexpected behavior, we can only get max to ``CONF.osapi_max_limit`` records when we list volume transfers under the current implementation, that means if we have more than ``CONF.osapi_max_limit`` items in db, we can only get first CONF.osapi_max_limit records.
So, we should support volume transfer pagination.
[1] https://github.com/openstack/cinder/blob/master/cinder/api/contrib/volume_transfer.py#L66
[2] https://github.com/openstack/cinder/blob/c0efaa1/cinder/api/common.py#L136 |
|
