Difference between revisions of "Persistent resource claim"
(Created page with "[Summary] Whenever a instance_claim/resize_claim request back") |
|||
| Line 1: | Line 1: | ||
| − | + | ===Summary=== | |
| − | + | When a resource claim happens for instance_claim or resize_claim request, the compute resource tracker will allocate the resource and persistent the claim result in the DB, then return the ID of the persistent claims. | |
| + | |||
| + | ===Benefit=== | ||
| + | Persistent the resource claim has a lot of benifits: | ||
| + | |||
| + | |||
| + | ===Details=== | ||
| + | The claim fields: | ||
| + | uuid: the identification for this claim. | ||
| + | instance_uuid: the owner instance of the | ||
Revision as of 06:10, 15 February 2014
Summary
When a resource claim happens for instance_claim or resize_claim request, the compute resource tracker will allocate the resource and persistent the claim result in the DB, then return the ID of the persistent claims.
Benefit
Persistent the resource claim has a lot of benifits:
Details
The claim fields: uuid: the identification for this claim. instance_uuid: the owner instance of the
