[RFE] Expose a config option to declare a network to bind corosync instead of a specific interface.
Bug #1631490 reported by
Jorge Niedbalski
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack HA Cluster Charm |
In Progress
|
Wishlist
|
Unassigned | ||
Bug Description
[Environment]
Xenial
Juju 2.0
[Description]
Currently the charm exposes the corosync_bindiface directive for defining on which network interface corosync will bind.
This config option works for most of the cases, but when the network configuration is composed with multiple interfaces with a non-predictable ordering (such as MAAS) it would be a nice to have feature to specify a network instead and identify the right interface from there.
| tags: | added: sts |
| Changed in hacluster (Juju Charms Collection): | |
| status: | New → In Progress |
| assignee: | nobody → Jorge Niedbalski (niedbalski) |
| Changed in hacluster (Juju Charms Collection): | |
| importance: | Undecided → Wishlist |
| Changed in charm-hacluster: | |
| assignee: | nobody → Jorge Niedbalski (niedbalski) |
| importance: | Undecided → Wishlist |
| status: | New → In Progress |
| Changed in hacluster (Juju Charms Collection): | |
| status: | In Progress → Invalid |
| no longer affects: | hacluster (Juju Charms Collection) |
| Changed in charm-hacluster: | |
| assignee: | Jorge Niedbalski (niedbalski) → nobody |
To post a comment you must log in.
