827c2d30b8
The previous rate limit defaults were unusable in any deployment. Rate limiting to 10 POSTS per minute and 50 servers per day seems to low, especially when we can use quotas to actually limit the amount of resources a user can consume. Update docstring to explain what the rate limiting is used for. Fixes bug 1178529 DocImpact changed default values Change-Id: I8cc93423f76d9b0a5135adf69babc4ff355a0951
86 lines
2.6 KiB
JSON
86 lines
2.6 KiB
JSON
{
|
|
"limits": {
|
|
"absolute": {
|
|
"maxImageMeta": 128,
|
|
"maxPersonality": 5,
|
|
"maxPersonalitySize": 10240,
|
|
"maxSecurityGroupRules": 20,
|
|
"maxSecurityGroups": 10,
|
|
"maxServerMeta": 128,
|
|
"maxTotalCores": 20,
|
|
"maxTotalFloatingIps": 10,
|
|
"maxTotalInstances": 10,
|
|
"maxTotalKeypairs": 100,
|
|
"maxTotalRAMSize": 51200
|
|
},
|
|
"rate": [
|
|
{
|
|
"limit": [
|
|
{
|
|
"next-available": "2012-11-27T17:22:18Z",
|
|
"remaining": 120,
|
|
"unit": "MINUTE",
|
|
"value": 120,
|
|
"verb": "POST"
|
|
},
|
|
{
|
|
"next-available": "2012-11-27T17:22:18Z",
|
|
"remaining": 120,
|
|
"unit": "MINUTE",
|
|
"value": 120,
|
|
"verb": "PUT"
|
|
},
|
|
{
|
|
"next-available": "2012-11-27T17:22:18Z",
|
|
"remaining": 120,
|
|
"unit": "MINUTE",
|
|
"value": 120,
|
|
"verb": "DELETE"
|
|
}
|
|
],
|
|
"regex": ".*",
|
|
"uri": "*"
|
|
},
|
|
{
|
|
"limit": [
|
|
{
|
|
"next-available": "2012-11-27T17:22:18Z",
|
|
"remaining": 120,
|
|
"unit": "MINUTE",
|
|
"value": 120,
|
|
"verb": "POST"
|
|
}
|
|
],
|
|
"regex": "^/servers",
|
|
"uri": "*/servers"
|
|
},
|
|
{
|
|
"limit": [
|
|
{
|
|
"next-available": "2012-11-27T17:22:18Z",
|
|
"remaining": 120,
|
|
"unit": "MINUTE",
|
|
"value": 120,
|
|
"verb": "GET"
|
|
}
|
|
],
|
|
"regex": ".*changes-since.*",
|
|
"uri": "*changes-since*"
|
|
},
|
|
{
|
|
"limit": [
|
|
{
|
|
"next-available": "2012-11-27T17:22:18Z",
|
|
"remaining": 12,
|
|
"unit": "MINUTE",
|
|
"value": 12,
|
|
"verb": "GET"
|
|
}
|
|
],
|
|
"regex": "^/os-fping",
|
|
"uri": "*/os-fping"
|
|
}
|
|
]
|
|
}
|
|
}
|