HA does not work on environments without MAAS or virtual IPs

Bug #1894971 reported by Pedro Guimarães
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack HA Cluster Charm
Triaged
Wishlist
Unassigned
vault-charm
New
Undecided
Unassigned

Bug Description

Hi,

I am currently testing hacluster + vault + mysql on top of public clouds and I am not able to set it up on HA mode.

The issue here is that both vault and mysql need ha-relation in order to move into "ready" status; however, public clouds generally do not allow for VIPs and we don't have the MAAS dns-ha option.

Revision history for this message
Pedro Guimarães (pguimaraes) wrote :

We have an ongoing deployment stuck in this issue.

Revision history for this message
David Ames (thedac) wrote :

Pedro,

I just want set expectations here. The hacluster VIP HA solution has never been supported on public clouds. So this is a feature request that will require road map placing. Field critical status is not appropriate.

Revision history for this message
Calvin Hartwell (calvinh) wrote :

Sorry @David but I disagree. Vault is used as part of Charmed Kubernetes and thus, we cannot deploy that solution on public clouds right now until the issue is addressed.

Revision history for this message
Billy Olsen (billy-olsen) wrote :

@calvinh - I understand the importance of the solution in the Charmed Kuberenetes deployment, however this does appear to be a feature request for the hacluster charm. There's generally a limitation within public clouds that they don't often allow for any arbitrary IPs to be added to nodes and receive traffic without modifying something in the cloud infrastructure.

For AWS, this requires a solution such as the aws ocf resource agent [0] and each public cloud will likely require its own as it relates to the details of interacting with the infrastructure. I agree that it does pose a limitation, but its not clear what the right solution for this is - adding ocf agents for hacluster to handle the various clouds, adding an alternative backend to vault such as etcd, or using some other solution.

As such, I don't believe this qualifies for field critical as it is a feature gap/request that needs to be handled with appropriate design work.

[0] - https://www.mankier.com/7/ocf_heartbeat_awsvip

Revision history for this message
Billy Olsen (billy-olsen) wrote :

Based on classification of new feature work here, I'm unsubscribing field-critical and we can plan this in as appropriate.

Changed in charm-hacluster:
status: New → Triaged
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.