02.07.2013 15:13, Lars Marowsky-Bree wrote: > On 2013-07-02T13:14:48, Vladislav Bogdanov <[email protected]> wrote: > >>> Yes, that's exactly what you need here. >> I know, but I do not expect that to be implemented soon. > > "crm_attribute -l reboot -z" doesn't strike me as an unlikely request. > You could file an enhancement request for that. > > But with the XML diff feature, as long as you're not editing the node > section, that shouldn't be a problem - unrelated changes shouldn't > overwrite those attributes, right? That being the whole point?
I do not edit them. I my setup I generate full crm config with template-based framework. That's why nodes go there too. And I can't skip them, because I heavily use "ordinary" node attributes and they change sometimes. > > (Of course, if you remove them in the copy, that'd remove them.) > >> But tickets currently are quite limited - they have only 4 states, so >> it is impossible to put f.e. number there. > > What are you trying to do with that? That is very convenient way to f.e stop dozen of resources in one shot for some maintenance. I have special RA which creates ticket on a cluster start and deletes it on a cluster stop. And many resources may depend on that ticket. If you request resource handled by that RA to stop, ticket is revoked and all dependent resources stop. I wouldn't write that RA if I have cluster-wide attributes (which perform like node attributes but for a whole cluster). _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
