Fix race on initial run where cluster founder is not found

On the very first time we apply a pacemaker proposal, non-founder nodes
might be running chef-client faster than the founder node (depending on
how crowbar will order them) and this might result in the founder
attribute not being indexed fast enough. So the nodes will fail not
finding the founder.

So on this very first time, we wait a bit to make sure the founder will
be returned in our search results.
Add ability to pick between multicast and unicast
Merge pull request #136 from vuntz/fix-initial-no-cluster-founder

Fix race on initial run where cluster founder is not found
Fix typo in README
Merge pull request #139 from vuntz/typo

Fix typo in README
Merge pull request #132 from vuntz/add-udpu

Add ability to pick between multicast and unicast
haproxy: Allow setting the tune.bufsize and tune.chksize options
crowbar-pacemaker: Increase tune.bufsize option of haproxy

The default value (16384) is too small for keystone: getting a PKI token
from its ID fails with a 400 Bad Request message from haproxy because
the URI path is too long.
Merge pull request #142 from vuntz/haproxy-bufsize

Fix issue with keystone/HA not working because of default haproxy setting