On Thu, Apr 27, 2017 at 09:19:55AM +0200, Jehan-Guillaume de Rorthais wrote: > > > > 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
> > > > # crm node status-attr ava set standby off > > Well, you want the "persistent" setting "on", > > and override it with a "transient" setting "off". > Quick questions: > > * is it what happen in the CIB when you call crm_standby? crm_standby --node emma --lifetime reboot --update off crm_standby --node emma --lifetime forever --update on (or -n -l -v, default node is current node, default lifetime is forever) > * is it possible to do the opposite? persistent setting "off" and override > it > with the transient setting? see above, also man crm_standby, which again is only a wrapper around crm_attribute. -- : 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 _______________________________________________ Users mailing list: Users@clusterlabs.org http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org