OSAPI: Enforce quota for server metadata controller
Bug #742807 reported by
Dan Prince
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Medium
|
Dan Prince | ||
Bug Description
The new v1.1 server metadata controller does not currently limit the amount of metadata that can be entered. We should have a mechanism to limit the maximum number of metadata items per server in the /servers/<id>/meta sub-resource controller.
Note: see quota.allowed_
Related branches
lp:~rackspace-titan/nova/server_metadata_quotas
- Jay Pipes (community): Approve
- Rick Harris (community): Approve
- Brian Waldon (community): Approve
- termie (community): Needs Fixing
- justinsb: Pending requested
-
Diff: 440 lines (+147/-99)6 files modifiednova/api/openstack/server_metadata.py (+22/-7)
nova/api/openstack/servers.py (+1/-11)
nova/compute/api.py (+27/-26)
nova/db/sqlalchemy/api.py (+3/-2)
nova/tests/api/openstack/test_server_metadata.py (+50/-9)
nova/tests/integrated/test_servers.py (+44/-44)
| Changed in nova: | |
| assignee: | nobody → Titan (rackspace-titan) |
| Changed in nova: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| Changed in nova: | |
| assignee: | Titan (rackspace-titan) → Dan Prince (dan-prince) |
| Changed in nova: | |
| status: | Confirmed → In Progress |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → diablo-1 |
| Changed in nova: | |
| milestone: | diablo-1 → 2011.3 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
