Persistent resource claims

Registered by jiang, yunhong on 2014-02-15

Currently when resource claimed in compute node, the resource tracker will not keep the claim object, it will only change the resource information and save the updated resource information to DB. In each periodic time, the resource tracker will recalculate the resource usage for each instance. This BP will try to persistent the claim into DB, and keep the claim as the instance request. It will simplify the recalculation and also bring other benefit as stated in the spec.

Blueprint information

Status:
Not started
Approver:
John Garbutt
Priority:
Low
Drafter:
jiang, yunhong
Direction:
Needs approval
Assignee:
jiang, yunhong
Definition:
Pending Approval
Series goal:
Accepted for trunk
Implementation:
Not started
Milestone target:
None

Related branches

Sprints

Whiteboard

belliott: I like the idea. This would keep claims consistent through nova-compute restarts as well as simplify some of the resource tracker logic.

There may also be an opportunity here to remove some of the retry logic from computes because resource will be pre-claimed from the conductor.

---
Since feature freeze happens already, I will try to push this into J-1. Brian, is it ok? -- yjiang5

---
belliott: I have no objections. J1 sound good. Thanks.

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguybelliott: I like the idea. This would keep claims consistent through nova-compute restarts as well as simplify some of the resource tracker logic.

There may also be an opportunity here to remove some of the retry logic from computes because resource will be pre-claimed from the conductor.

---
Since feature freeze happens already, I will try to push this into J-1. Brian, is it ok? -- yjiang5

---
belliott: I have no objections. J1 sound good. Thanks.

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy

Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)

I'm coding on this now. Sure I will submit it through nova-specs. -- yjiang5

Spec not approved yet, un-targeting blueprint from juno-1 --johnthetubaguy (28th May 2014)

Gerrit topic: https://review.openstack.org/#q,topic:bp/plans,n,z

Addressed by: https://review.openstack.org/84906
    Persistent resource claim

You should not set a milestone target unless the blueprint has been properly prioritized by the project drivers.

Gerrit topic: https://review.openstack.org/#q,topic:bp/persistent-resource-claim,n,z

Addressed by: https://review.openstack.org/108555
    Add persistent claims support

Addressed by: https://review.openstack.org/108556
    Update the resource tracker for persistent claims

Addressed by: https://review.openstack.org/108557
    Change resource tracker for remote claim

Addressed by: https://review.openstack.org/108558
    Conductor remotely claim resource

Feature Proposal Freeze means this must not land in juno, because it appears like the code is not all currently ready to be reviewed. To be able to merge in kilo, we would first need to merge a kilo spec. More details on the exact process will be available on the ML shortly. --johnthetubaguy 22nd August 2014

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.