Pacemaker default configurations are unreasonable

[Dan Xu]

Tripleo uses pacemaker's default configurations of virtual ip monitor interval and haproxy monitor interval, which is
sudo pcs resource show ip-192.168.36.17
Resource: ip-192.168.36.17 (class=ocf provider=heartbeat type=IPaddr2)
    Attributes: ip=192.168.36.17 cidr_netmask=32
    Operations: start interval=0s timeout=20s (ip-192.168.36.17-start-interval-0s)
                stop interval=0s timeout=20s (ip-192.168.36.17-stop-interval-0s)
                monitor interval=10s timeout=20s (ip-192.168.36.17-monitor-interval-10s)

sudo pcs resource show haproxy
Resource: haproxy (class=systemd type=haproxy)
    Operations: start interval=0s timeout=200s (haproxy-start-interval-0s)
                stop interval=0s timeout=200s (haproxy-stop-interval-0s)
                monitor interval=60s (haproxy-monitor-interval-60s)

The first configuration will make the outage time of openstack service to be more than 20s.
The second configuration may make the outage time of haproxy processes to be 60s (the worst case).

All these make the HA not very effective (outage time is too long).