Difference between revisions of "Pci resource management"
(Created page with "<gallery> Example.jpg|Caption1 Example.jpg|Caption2 </gallery> a) Same PCI had different Objects, one in the stats and another in the instance b) when RESIZE secondary host g...") |
|||
| Line 15: | Line 15: | ||
<sub> | <sub> | ||
problem 1: | problem 1: | ||
| − | + | 'claimed' status must be used to keep old device on source machine. | |
| − | + | we use node_id, not hostname, so use claimed status to keep out other machine's device out. | |
| − | + | solution A: get compute node from instance's hostname --> get compute_node_id | |
| − | 方法2: | + | risk: always reading DB can not cache. |
| + | 方法2: keep claimed status | ||
</sub> | </sub> | ||
Revision as of 01:17, 13 January 2015
- Example.jpg
Caption1
- Example.jpg
Caption2
a) Same PCI had different Objects, one in the stats and another in the instance b) when RESIZE secondary host get other instances Objects
Resize:
-> new host claim -> old host stop (instance going to new HOST)-> new host starting new instance
Confirm:
new machine call source machines’s drop_resize_claim ( a new resource tracker been setting up)
Aborting:
new: stop new instance, drop claim -- > old: reverting old status and stating machine
problem 1: 'claimed' status must be used to keep old device on source machine. we use node_id, not hostname, so use claimed status to keep out other machine's device out. solution A: get compute node from instance's hostname --> get compute_node_id risk: always reading DB can not cache. 方法2: keep claimed status
