[Debian-ha-maintainers] Bug#717196: Acknowledgement (pacemaker: "crm configure" does not have support for rsc_ticket constraint.)

[ap at serversnab.ru]

Ok, I found that help file /usr/share/pacemaker/crm.8.txt and python 
files at /usr/share/pyshared/crm
don't have appropriate support code for rsc_ticket.
Also I found that after "pacemaker 1.7" upstream has move "crmsh" in 
standalone project. And debian has
experimental package of it 
http://packages.debian.org/experimental/crmsh
For now I build this package for debian wheezy (just changing name from 
crm to crmsh to avoid packages conflict with pacemaker) and it looks 
like issue has been resolved for me this rude way.

According https://savannah.nongnu.org/forum/forum.php?forum_id=7503
"CRM shell 1.2.5 supports all Pacemaker 1.1 versions".


# crmsh configure rsc_ticket cluster-req-t_ticket t_ticket:  
cluster_group loss-policy=fence
# crmsh configure show | grep rsc_ticket
rsc_ticket cluster-req-t_ticket t_ticket: cluster_group 
loss-policy=fence

# crmsh configure help rsc_ticket

This constraint expresses dependency of resources on cluster-wide
attributes, also known as tickets. Tickets are mainly used in
geo-clusters, which consist of multiple sites. A ticket may be
granted to a site, thus allowing resources to run there.

The `loss-policy` attribute specifies what happens to the
resource (or resources) if the ticket is revoked. The default is
either `stop` or `demote` depending on whether a resource is
multi-state.

See also the `site` set of commands.

Usage:
...............
         rsc_ticket <id> <ticket_id>: <rsc>[:<role>] [<rsc>[:<role>] 
...]
           [loss-policy=<loss_policy_action>]

         loss_policy_action :: stop | demote | fence | freeze
...............
Example:
...............
         rsc_ticket ticket-A_public-ip ticket-A: public-ip
         rsc_ticket ticket-A_bigdb ticket-A: bigdb loss-policy=fence
         rsc_ticket ticket-B_storage ticket-B: drbd-a:Master 
drbd-b:Master
...............