Difference between revisions of "Pci resource management"
Line 1: | Line 1: | ||
− | |||
PCI_resize_Design.png | PCI_resize_Design.png | ||
− | + | ||
a) Same PCI had different Objects, one in the stats and another in the instance | a) Same PCI had different Objects, one in the stats and another in the instance | ||
b) when RESIZE secondary host get other instances Objects | b) when RESIZE secondary host get other instances Objects |
Revision as of 01:19, 13 January 2015
PCI_resize_Design.png
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