๐ก OpenStack Nova/Neutron API 1000-Limit โ Executive Summary
Technical architectural analysis, practical configuration manifests, and deployment instructions for OpenStack Nova/Neutron API 1000-Limit.
Basis
References and Guidelines (NOTE)
In order to apply the config file, each daemon must be restarted, so there are many limitations in operating it in an operating cluster.
Nova
max_limit = 1000 (default)
Cinder
osapi_max_limit = 1000 (default)
Client-side bypass method
References and Guidelines (NOTE)
Receiving more than 1000 pieces of information through paging using parameters
(Example: GET {cinder}/v3/{project_id}/volumes/detail)
ex) Processing 1575 responses into 2 pages (The results of the two alternatives below are the same.)
- limit & offset
bash
#1page
curl ${OS_Volumev3}/volumes/detail?all_tenants=true\&limit=1000\&offset=0 -H"X-Auth-Token: $OS_PRJ_TOKEN" | jq "" | grep "\"name\"" -c
#>> 1000
#2page
curl ${OS_Volumev3}/volumes/detail?all_tenants=true\&limit=1000\&offset=1000 -H"X-Auth-Token: $OS_PRJ_TOKEN" | jq "" | grep "\"name\"" -c
#>> 575- limit & marker
bash
#1page
curl ${OS_Volumev3}/volumes/detail?all_tenants=true\&limit=1000 -H"X-Auth-Token: $OS_PRJ_TOKEN" | jq "" | grep "\"name\"" -c
#>> 1000
#2page
export LAST_VOLUME_ID= $(`์ด์ 1000๋ฒ์งธ ๋ณผ๋ฅจ`)
curl ${OS_Volumev3}/volumes/detail?all_tenants=true\&limit=1000\&marker=$LAST_VOLUME_ID -H"X-Auth-Token: $OS_PRJ_TOKEN" | jq "" | grep "\"name\"" -c
#>> 575
Leave a Reply