--meta
option of the crm_resource
command.
Tabella 5.2. Opzioni per una Primitive Resource
Campo | Default | Descrizione |
---|---|---|
priority
|
0
| |
target-role
|
Started
|
In quale stato il cluster deve cercare di tenere questa risorsa? Valori permessi:
* Stopped - Force the resource to be stopped
* Started - Allow the resource to be started (In the case of multi-state resources, they will not promoted to master)
|
is-managed
|
TRUE
| |
resource-stickiness
|
Calculated
| |
requires
|
Calculated
|
Under what conditions can the resource be started. (Since 1.1.8)
Defaults to
fencing unless stonith-enabled is false or class is stonith - under those conditions the default is quorum . Possible values:
* nothing - can always be started
* quorum - The cluster can only start this resource if a majority of the configured nodes are active
* fencing - The cluster can only start this resource if a majority of the configured nodes are active and any failed or unknown nodes have been powered off.
|
migration-threshold
|
INFINITY (disabled)
| |
failure-timeout
|
0 (disabled)
| |
multiple-active
|
stop_start
|
Cosa dovrebbe fare il cluster se mai trovasse la risorsa attiva su più di un nodo. Valori permessi:
* block - mark the resource as unmanaged
* stop_only - stop all active instances and leave them that way
* stop_start - stop all active instances and start the resource in one location only
|
# crm_resource --meta --resource Email --set-parameter priority --property-value 100 # crm_resource --meta --resource Email --set-parameter multiple-active --property-value block
Esempio 5.3. Una risorsa LSB con le opzioni cluster
<primitive id="Email" class="lsb" type="exim"> <meta_attributes id="meta-email"> <nvpair id="email-priority" name="priority" value="100"/> <nvpair id="email-active" name="multiple-active" value="block"/> </meta_attributes> </primitive>