Object reference validation should occur in drivers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Ken Thomas | ||
Folsom |
Fix Released
|
Medium
|
Joseph Heck |
Bug Description
Bug 963056 introduced object validation at the controller level for simplicity, but this would be more efficiently handled by the backends themselves.
For example, in the current implementation, "delete role" behaves as follows against all drivers:
1) Controller fetches the role from the driver
2) Driver executes a select, returning an object reference or None (1st backend operation)
3) Controller raises 404 if None is returned
4) Controller issues a delete for the role
5) Driver executes a delete (2nd backend operation)
This could be more efficiently handled in the SQL driver as follows:
1) Controller issues a delete for the the role
2) Driver executes a delete, raises 404 if no rows affected (1st backend operation)
Changed in keystone: | |
assignee: | nobody → Dolph Mathews (dolph) |
importance: | Undecided → Medium |
milestone: | none → folsom-1 |
status: | New → Confirmed |
Changed in keystone: | |
status: | Confirmed → In Progress |
Changed in keystone: | |
milestone: | folsom-1 → folsom-2 |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | folsom-2 → 2012.2 |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
tags: | removed: in-stable-folsom |
Fix proposed to branch: master /review. openstack. org/6875
Review: https:/