Switch from pacemaker standby to pacemaker stop

Currently, the "snapshots" backup is being taken after taking out one
node from the cluster using pcs node standby. The consequence of it is
that the standby property is also being backuped, so when the node is
restored, it appears as standby and it needs to be unstandby manually.

Switching to pcs cluster stop/pcs cluster start does not make the playbook take any
longer, nor it creates an impact on the time the vips take to be
migrated to a different node while provides the advantage that when the
node is restarted (during restore), pacemaker starts correctly without
any other manual step.

Change-Id: Ided482f7eaed8d5e1fac60679ef3ba07bda41c0c

tripleo_ansible/roles/backup_and_restore/defaults/main.yml

@@ -82,3 +82,6 @@ tripleo_backup_and_restore_remove_default_cronjob: true
 
 # Skip the ping test to the NFS server on rear setup
 tripleo_backup_and_restore_skip_nfs_test: false
+
+# How many seconds do we want to wait fir pcs cluster stop to finish
+tripleo_backup_and_restore_pcs_timeout: 3600

tripleo_ansible/roles/backup_and_restore/tasks/main.yml

@@ -62,7 +62,7 @@
         - not tripleo_backup_and_restore_enable_snapshots|bool
 
     - name: Pacemaker management
-      import_tasks: pacemaker_unstandby.yml
+      import_tasks: pacemaker_start.yml
       when:
         - pacemaker_enabled
         - tripleo_backup_and_restore_enable_snapshots|bool

tripleo_ansible/roles/backup_and_restore/tasks/pacemaker_start.yml

@@ -16,7 +16,7 @@
 #
 # Start again pacemaker
 - name: Add the node to the pacemaker cluster
-  command: pcs node unstandby
+  command: pcs cluster start
   tags:
     - bar_create_recover_image
 

tripleo_ansible/roles/backup_and_restore/tasks/run_backup.yml

@@ -33,7 +33,7 @@
     - always
 
 - name: Take this node out of pacemaker
-  command: pcs node standby
+  command: pcs cluster stop --request-timeout={{ tripleo_backup_and_restore_pcs_timeout }}
   when:
     - pacemaker_enabled
     - tripleo_backup_and_restore_enable_snapshots|bool