crm_standby(8) [suse man page]

CRM_STANDBY(8)							  [FIXME: manual]						    CRM_STANDBY(8)

NAME

       crm_standby - manipulate a node's standby attribute to determine whether resources can be run on this node

SYNOPSIS

	   crm_standby [-?|-V] -D -u|-U node -r resource

	   crm_standby	[-?|-V] -G -u|-U node -r resource

	   crm_standby [-?|-V] -v string -u|-U node -r resource [-l string]

DESCRIPTION

       The crm_standby command manipulates a node's standby attribute. Any node in standby mode is no longer eligible to host resources and any
       resources that are there must be moved. Standby mode can be useful for performing maintenance tasks, such as kernel updates. Remove the
       standby attribute from the node when it should become a fully active member of the cluster again.

       By assigning a lifetime to the standby attribute, determine whether the standby setting should survive a reboot of the node (set lifetime
       to forever) or should be reset with reboot (set lifetime to reboot). Alternatively, remove the standby attribute and bring the node back
       from standby manually.

OPTIONS

       --help, -?
	   Print a help message.

       --verbose, -V
	   Turn on debug information.

	       Note
	       Increase the level of verbosity by providing additional instances.

       --quiet, -Q
	   When doing an attribute query using -G, print just the value to stdout. Use this option with -G.

       --get-value, -G
	   Retrieve rather than set the preference.

       --delete-attr, -D
	   Specify the attribute to delete.

       --attr-value string, -v string
	   Specify the value to use. This option is ignored when used with -G.

       --node-uuid node_uuid, -u node_uuid
	   Specify the UUID of the node to change.

       --node-uname node_uname, -U node_uname
	   Specify the uname of the node to change.

       --lifetime string, -l string
	   Determine how long this preference lasts. Possible values are reboot or forever.

	       Note
	       If a forever value exists, it is always used by the CRM instead of any reboot value.

EXAMPLES

       Have a local node go to standby:

	       crm_standby -v true

       Have a node (node1) go to standby:

	       crm_standby -v true -U node1

       Query the standby status of a node:

	       crm_standby -G -U node1

       Remove the standby property from a node:

	       crm_standby -D -U node1

       Have a node go to standby for an indefinite period of time:

	       crm_standby -v true -l forever -U node1

       Have a node go to standby until the next reboot of this node:

	       crm_standby -v true -l reboot -U node1

FILES

       /var/lib/heartbeat/crm/cib.xml--the CIB (minus status section) on disk. Editing this file directly is strongly discouraged.

SEE ALSO

       ???, ???

AUTHOR

       crm_standby was written by Andrew Beekhof.

[FIXME: source] 						    07/05/2010							    CRM_STANDBY(8)

PACEMAKER(8)						  System Administration Utilities					      PACEMAKER(8)

NAME

       Pacemaker - Part of the Pacemaker cluster resource manager

SYNOPSIS

       crm_ticket (query|command) [options]

DESCRIPTION

       crm_ticket - Perform tasks related to cluster tickets.  Allows ticket attributes to be queried, modified and deleted.

OPTIONS

       -?, --help
	      This text

       -$, --version
	      Version information

       -V, --verbose
	      Increase debug output

       -Q, --quiet
	      Print only the value on stdout

       -t, --ticket=value
	      Ticket ID

   Queries:
       -l, --info
	      Display the information of ticket(s)

       -L, --details
	      Display the details of ticket(s)

       -w, --raw
	      Display the IDs of ticket(s)

       -q, --query-xml
	      Query the XML of ticket(s)

       -c, --constraints
	      Display the rsc_ticket constraints that apply to ticket(s)

   Commands:
       -g, --grant
	      Grant a ticket to this cluster site

       -r, --revoke
	      Revoke a ticket from this cluster site

       -s, --standby
	      Tell this cluster site this ticket is standby

       -a, --activate
	      Tell this cluster site this ticket is active

   Advanced Commands:
       -G, --get-attr=value
	      Display the named attribute for a ticket

       -S, --set-attr=value
	      Set the named attribtue for a ticket

       -D, --delete-attr=value
	      Delete the named attribute for a ticket

       -C, --cleanup
	      Delete all state of a ticket at this cluster site

   Additional Options:
       -v, --attr-value=value
	      Attribute value to use with -S

       -d, --default=value
	      (Advanced) The default attribute value to display if none is found. For use with -G

       -f, --force
	      (Advanced) Force the action to be performed

       -n, --set-name=value
	      (Advanced) ID of the instance_attributes object to change

       -i, --nvpair=value
	      (Advanced) ID of the nvpair object to change/delete

EXAMPLES

       Display the info of tickets:

	      # crm_ticket --info

       Display the detailed info of tickets:

	      # crm_ticket --details

       Display the XML of 'ticketA':

	      # crm_ticket --ticket ticketA --query-xml

       Display the rsc_ticket constraints that apply to 'ticketA':

	      # crm_ticket --ticket ticketA --constraints

       Grant 'ticketA' to this cluster site:

	      # crm_ticket --ticket ticketA --grant

       Revoke 'ticketA' from this cluster site:

	      # crm_ticket --ticket ticketA --revoke

       Make 'ticketA' standby:

       The  cluster site will treat a granted 'ticketA' as 'standby'.  The dependent resources will be stopped or demoted gracefully without trig-
       gering loss-policies

	      # crm_ticket --ticket ticketA --standby

       Activate 'ticketA' from being standby:

	      # crm_ticket --ticket ticketA --activate

       Get the value of the 'granted' attribute for 'ticketA':

	      # crm_ticket --ticket ticketA --get-attr granted

       Set the value of the 'standby' attribute for 'ticketA':

	      # crm_ticket --ticket ticketA --set-attr standby --attr-value true

       Delete the 'granted' attribute for 'ticketA':

	      # crm_ticket --ticket ticketA --delete-attr granted

       Erase the operation history of 'ticketA' at this cluster site:

       The cluster site will 'forget' the existing ticket state.

	      # crm_ticket --ticket ticketA --cleanup

AUTHOR

       Written by Andrew Beekhof

REPORTING BUGS

       Report bugs to pacemaker@oss.clusterlabs.org

Pacemaker 1.1.7 						    April 2012							      PACEMAKER(8)