Eliminate use of with_lockmode('update')
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Morgan Fainberg | ||
Icehouse |
Fix Released
|
Medium
|
Morgan Fainberg |
Bug Description
As discussed here: http://
the use of "with_lockmode(
We currently only use with_lockmode(
We should eliminate this and handle the coordination of consumption to ensure only the specified number of tokens can be issued from a trust. Unfortunately, this is not as straightforward as it could be, we need to handle the following deployment scenarios:
* Eventlet
* Multiple Keystone Processes (same physical server) [same issue as mod_wsgi]
* Multiple Keystone Processes (different physical servers)
The first and second ones could be handled with the lockutils (external file-based) locking decorator. The last scenario will take more thought.
Changed in keystone: | |
importance: | Undecided → High |
status: | New → Triaged |
tags: | added: icehouse-backport-potential |
Changed in keystone: | |
importance: | High → Medium |
description: | updated |
Changed in keystone: | |
milestone: | none → juno-3 |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | juno-3 → 2014.2 |
Fix proposed to branch: master /review. openstack. org/97059
Review: https:/