| Trees | Indices | Help |
|
|---|
|
|
Verifies the cluster status.
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
Inherited from Inherited from Inherited from |
|||
|
|||
HPATH = "cluster-verify"
|
|||
HTYPE = "CLUSTER"
|
|||
_OP_REQP = ["skip_checks"]
|
|||
REQ_BGL = False
|
|||
|
Inherited from |
|||
|
|||
|
Inherited from |
|||
|
|||
Expand names for this LU. This method is called before starting to execute the opcode, and it should update all the parameters of the opcode to their canonical form (e.g. a short node name must be fully expanded after this method has successfully completed). This way locking, hooks, logging, ecc. can work correctly. LUs which implement this method must also populate the self.needed_locks member, as a dict with lock levels as keys, and a list of needed lock names as values. Rules:
If you need to share locks (rather than acquire them exclusively) at one level you can modify self.share_locks, setting a true value (usually 1) for that level. By default locks are not shared. Examples:
# Acquire all nodes and one instance
self.needed_locks = {
locking.LEVEL_NODE: locking.ALL_SET,
locking.LEVEL_INSTANCE: ['instance1.example.tld'],
}
# Acquire just two nodes
self.needed_locks = {
locking.LEVEL_NODE: ['node1.example.tld', 'node2.example.tld'],
}
# Acquire no locks
self.needed_locks = {} # No, you can't leave it to the default value None
|
Run multiple tests against a node. Test list:
|
Verify an instance. This function checks to see if the required block devices are available on the instance's node. |
Verify if there are any unknown volumes in the cluster. The .os, .swap and backup volumes are ignored. All other volumes are reported as unknown. |
Verify the list of running instances. This checks what instances are running but unknown to the cluster. |
Verify N+1 Memory Resilience. Check that if one single node dies we can still start all the instances it was primary for. |
Check prerequisites. Transform the list of checks we're going to skip into a set and check that all its members are valid.
|
Build hooks env. Cluster-Verify hooks just ran in the post phase and their failure makes the output be logged in the verify output and the verification to fail.
|
Verify integrity of cluster, performing various test on nodes.
|
Analyze the post-hooks' result This method analyses the hook result, handles it, and sends some nicely-formatted feedback back to the user.
|
| Trees | Indices | Help |
|
|---|
| Generated by Epydoc 3.0.1 on Fri Sep 3 12:34:39 2010 | http://epydoc.sourceforge.net |