-----------
Based on discussion in yesterday's meeting http://eavesdrop.openstack.org/meetings/ironic/2013/ironic.2013-12-09-19.01.log.html
I am going to target the related bug report to I-2 (it's already set to HIGH priority), and also lower this blueprint's priority and untarget it from the Icehouse cycle. We need a way to manually break locks held by dead conductors and prevent users from setting a lock in the API (both addressed by the bug) but we don't need automatic, time-based lock timeouts (discussed at the summit, fraught with potential issues).
Copy of whiteboard:
Addressed by: https:/ /review. openstack. org/#/c/ 55549/
Allow clean reservation at update node
----------- eavesdrop. openstack. org/meetings/ ironic/ 2013/ironic. 2013-12- 09-19.01. log.html
Based on discussion in yesterday's meeting
http://
I am going to target the related bug report to I-2 (it's already set to HIGH priority), and also lower this blueprint's priority and untarget it from the Icehouse cycle. We need a way to manually break locks held by dead conductors and prevent users from setting a lock in the API (both addressed by the bug) but we don't need automatic, time-based lock timeouts (discussed at the summit, fraught with potential issues).
--Devananda, 2013-12-10
Gerrit topic: https:/ /review. openstack. org/#q, topic:bug/ 1250348, n,z
Addressed by: https:/ /review. openstack. org/55549
Allow clean reservation at update node
Gerrit topic: https:/ /review. openstack. org/#q, topic:bp/ breaking- resource- locks,n, z
Addressed by: https:/ /review. openstack. org/70273 clear_reservati on
Minor update for _check_
Addressed by: https:/ /review. openstack. org/71212
Add ability to break TaskManager locks via REST API
I'm still inclined to see this work happen, personally...
// jroll 2015-10-15