Updates:
Status: Fixed
Comment #1 on issue 143 by [email protected]: gnt-node list doesn't handle
properly non-vm_capable nodes
http://code.google.com/p/ganeti/issues/detail?id=143
This was fixed:
commit effab4c
Author: Iustin Pop <[email protected]>
Date: Thu Feb 17 14:42:57 2011 +0100
NodeQuery: mark live fields as UNAVAIL for non-vm_capable nodes
Since we don't have the data per design, UNAVAIL is appropriate here,
while NODATA is not.
The patch also adds a comment: if we extend the live fields list to
contain other data in the future, we need to reevaluate this solution.
This should fix issue 143. The listing now shows (node2==ofline,
node3==not vm_capable):
Node DTotal DFree MTotal MNode MFree Pinst Sinst
node1 698.6G 630.5G 32.0G 1.0G 30.0G 8 7
node2 (offline) (offline) (offline) (offline) (offline) 9 4
node3 (unavail) (unavail) (unavail) (unavail) (unavail) 0 0
Signed-off-by: Iustin Pop <[email protected]>
Reviewed-by: Michael Hanselmann <[email protected]>
commit 74f258b
Author: Iustin Pop <[email protected]>
Date: Thu Feb 17 14:41:29 2011 +0100
NodeQuery: don't query non-vm_capable nodes
Because non-vm_capable nodes most likely don't have a hypervisor
configured and/or storage, so the call will fail anyway.
Signed-off-by: Iustin Pop <[email protected]>
Reviewed-by: Michael Hanselmann <[email protected]>
