Multicast Address isn't randomized
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack HA Cluster Charm |
Triaged
|
Wishlist
|
Unassigned | ||
hacluster (Juju Charms Collection) |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
When deploying a hacluster, the multicast address defaults to a fixed address of 226.94.1.1.
This means having two haclusters on the same network segment will cause no end of conflicts and other unexpected behaviour.
The recommended address range (to simplify) for private address space is 239.[192-
When a hacluster is deployed without a mulitcast address it should be randomly allocated from that pool.
This only gives 24 bits of randomness, and does have potential to cause a conflict. The mcastport may additionally be randomized to add more entropy.
Changed in charm-hacluster: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
Changed in hacluster (Juju Charms Collection): | |
status: | Triaged → Invalid |
Additonally, looking at the charm: mcastaddr:
corosync_
description: 'Multicast IP address to use for exchanging messages over the network.
If multiple clusters are on the same bindnetaddr network, this value
can be changed.
That should be 'must be unique per cluster' or something like that.