Ceph » Orchestrator

For context:

We are running 1 test cluster ceph with cephadm. Currently last pacific (16.2.13).
We use cephadm to deploy keepalived:2.1.5 and HAProxy:2.3.
We have 3 VIPs, 1 for each instance of HAProxy.

But, we do not use the same network for managing the cluster and for the public traffic.
We have a management network (172.X) to connect to the machines, and for cephadm to do the deployments, and a prod network (10.X) where the connections to HAproxy will be done.

This is an example of keepalived.conf file generated:

```
vrrp_instance VI_2 {
state MASTER
priority 100
interface bond0
virtual_router_id 52
advert_int 1
authentication {
auth_type PASS
auth_pass rkuldramymuvtkzmcxjh
}
unicast_src_ip 172.X
unicast_peer {
172.Y
172.Z
}
virtual_ipaddress {
10.X dev bond0
}
track_script {
check_backend
}
}
```

If the network 172.X is not in the interface specified by `interface`. For example eno1 instead of bond0, the instances of Keepalived will not properly communicate with each other.
I think we should choose to have either `interface` set, or unicast_src_ip with `unicast_peer`. Or maybe have a way to choose either one or the other.