[ClusterLabs] Coming in Pacemaker 1.1.17: start a node in standby

[Lars Ellenberg]

On Mon, Apr 24, 2017 at 03:08:55PM -0500, Ken Gaillot wrote:
> Hi all,
> 
> Pacemaker 1.1.17 will have a feature that people have occasionally asked
> for in the past: the ability to start a node in standby mode.


I seem to remember that at some deployment,
we set the node instance attribute standby=on, always,
and took it out of standby using the node_state transient_attribute :-)

As in
# crm node standby ava
  <node id="1" uname="ava">
    <instance_attributes id="nodes-1">
      <nvpair id="nodes-1-standby" name="standby" value="on"/>
      ...
    </instance_attributes>
  </node>
  ...

# crm node status-attr ava set standby off
  <node_state id="1" uname="ava" in_ccm="true" crmd="online" crm-debug-origin="do_update_resource" join="member" expected="member">
    ...
    <transient_attributes id="1">
      <instance_attributes id="status-1">
	...
        <nvpair id="status-1-standby" name="standby" value="off"/>
      </instance_attributes>
    </transient_attributes>
  </node_state>

Seemed to work good enough at the time.

Though that may have been an un-intentional side-effect
of checking both sets of attributes?

-- 
: Lars Ellenberg
: LINBIT | Keeping the Digital World Running
: DRBD -- Heartbeat -- Corosync -- Pacemaker
: R&D, Integration, Ops, Consulting, Support

DRBD® and LINBIT® are registered trademarks of LINBIT