Updates:
Labels: -Milestone-Release2.14 Milestone-Release2.17
Comment #1 on issue 1001 by [email protected]: Implement potential master
candidates
https://code.google.com/p/ganeti/issues/detail?id=1001
Just adding a bit more info.
Terminology:
"potential master candidates" are all nodes that are *master capable* (when
the set of master capable nodes is frozen).
Steps necessary for this:
- Implement a cluster-wide boolean config parameter "freeze potential
master candidates". This parameter should be settable to true/false via the
CLI, but only to false via RAPI. The parameter is intended to indicate when
the set of potential master candidates is unextendable via RAPI.
- If the parameter is 'true', block the operation of making a normal node
master_capable via RAPI (and possibly CLI, but that's not the point here).
If the parameter is 'false', keep the current behavior.
- Implement that the management of the SSH keys considers the status of
potential master candidates. Currently it assumes that all nodes are
potential master candidates. (See config.py's
GetAllPotentialMasterCandidates).
- If a node is made 'master_capable' that wasn't 'master_capable' before,
make sure its key is added to the ganeti_pub_key files on all nodes.
Reverse this operation when a node is made not master_capable.
--
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
