Management in High Availability Guide: Galera without HAProxy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
In the "Configuration tips" section there are three different deployment strategies for Galera described, one of them states:
---cut here---
Galera can be configured using one of the following strategies:
Each instance has its own IP address:
OpenStack services are configured with the list of these IP addresses so they can select one of the addresses from those available.
---cut here---
I know this is true for memcached, but I have been searching for hours to find something that confirms this statement for database connections in the openstack config files.
Appending a second connection string to nova.conf, for example, leads to a failing service, it can't parse the string correctly.
I would be interested in the source of the information because we would like to use it, but if this is not true - as it currently seems - this bug report should be valid.
This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes:
- [x] This doc is inaccurate in this way: using Galera with a list of ip addresses instead of HAProxy (with VIP) seems to be not supported by openstack configs
- [ ] This is a doc addition request.
- [ ] I have a fix to the document that I can paste below including example: input and output.
If you have a troubleshooting or support issue, use the following resources:
- Ask OpenStack: http://
- The mailing list: http://
- IRC: 'openstack' channel on Freenode
-------
Release: on 2018-03-08 07:32
SHA: 6e4a615fe0524a3
Source: https:/
URL: https:/
Changed in openstack-manuals: | |
importance: | Undecided → Medium |
status: | New → Triaged |
page don't exists anymore. Bug track for ha-guide is now on https:/ /storyboard. openstack. org/#!/ project/ openstack/ ha-guide