Status: Accepted
Owner: ----
Labels: Milestone-Release2.8 Type-Documentation Priority-High
New issue 537 by [email protected]: document hbal placement behavior wrt
drained nodes
http://code.google.com/p/ganeti/issues/detail?id=537
hbal(1) says:
PLACEMENT RESTRICTIONS
At each step, we prevent an instance move if it would cause:
· a node to go into N+1 failure state
· an instance to move onto an offline node (offline nodes are either
read from the cluster or declared with -O)
· an exclusion-tag based conflict (exclusion tags are read from the
cluster and/or defined via the --exclusion-tags option)
· a max vcpu/pcpu ratio to be exceeded (configured via --max-cpu)
· min disk free percentage to go below the configured limit
(configured via --min-disk)
This doesn't mention drained nodes at all. We should verify that the
behavior with drained nodes is indeed "an instance won't be moved *to* a
drained node" and then update the documentation.
--
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
