Comment 2 for bug 1628521

So the reason why we cannot to this right away for galera is the following:
When we pass wsrep_cluster_address=gcomm://overcloud-controller-0.internalapi.localdomain,overcloud-controller-1.internalapi.localdomain,overcloud-controller-2.internalapi.localdomain
the galera resource agent is unable to map those names to the cluster node names and the galera setup will fail.

So we first need to extend the galera RA to support some mapping between cluster node name and hostnames of ip addresses belonging to the node.