Updates:
Status: Fixed
Comment #2 on issue 1128 by [email protected]: Support state-of-record
backend for htools
https://code.google.com/p/ganeti/issues/detail?id=1128
commit 1e9f49ba5e9b5ff51bf1c6abc4887ddfc6b994a0
Author: Klaus Aehlig <[email protected]>
Date: Mon Oct 26 10:38:00 2015 +0100
Make hspace support --state-of-record
In this way, hspace can be told to use precisely the data
that hail will be provided with.
Signed-off-by: Klaus Aehlig <[email protected]>
Reviewed-by: Oleg Ponomarev <[email protected]>
commit b2f6c65a79a07ee9fd0954c6835bc5d2c720cbf8
Author: Klaus Aehlig <[email protected]>
Date: Mon Oct 26 09:47:41 2015 +0100
Honor the --state-of-record option in the luxi backend
That is, make the luxi backend not ask for the operational memory,
but only for the backend parameter, if this option is given.
Signed-off-by: Klaus Aehlig <[email protected]>
Reviewed-by: Oleg Ponomarev <[email protected]>
commit 3aa5c99bd91190edddb70303cebb900dbfbb14da
Author: Klaus Aehlig <[email protected]>
Date: Fri Oct 23 14:06:14 2015 +0200
Add a new option --state-of-record
This option will tell htools to use state-of-record data instead of
live ("state of world") data. A difference between the two occurs,
e.g., if an instance is resized but not rebooted.
Signed-off-by: Klaus Aehlig <[email protected]>
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
