openstack/kolla.git/ansible/roles/haproxy/templates/keepalived.conf.j2, branch masterUnnamed repository; edit this file 'description' to name the repository.
https://git.platform-os.org/openstack/kolla.git/atom?h=master2016-11-16T04:34:17+00:00Remove Ansible from Kolla2016-11-16T04:34:17+00:00Steven Dakestdake@cisco.com2016-11-16T02:01:25+00:00urn:sha1:3fcef82946f7053affcfb0b1b3ef4292beb9fa95
Change-Id: I5396e4b9927d3e65b6aa4185238a43a4765a996b
Make keepalived virtual_router_id param configurable2016-04-01T20:35:35+00:00Carlos Cesariocarloscesario@gmail.com2016-03-31T18:32:00+00:00urn:sha1:676998a1241f68b77d15b09d7113ae2182130c68
To be kolla deploy multiple clouds, we need to be able to configure
virtual_router_id other wise haproxy will fail setup the VIP for the
second cloud.
Partially-Implements: blueprint multiple-cloud
Closes-Bug: #1564547
Change-Id: I9eb27dd6fba61205841eadafc96601e235d2fe6d
When two interfaces are used for two VIPs, tie them together2016-04-01T16:04:22+00:00Dave McCowandmccowan@cisco.com2016-03-31T01:26:19+00:00urn:sha1:bbbe84667d49cebaa8b40366f9e3be79a47e2606
When a node uses two physical interfaces for its two VIPs, these
physical interfaces should be tied together, so both VIPs will
be taken out of scheduling if either one fails. Without this change,
if a request comes into one interface that needs access to the
second interface to process the request, the original request
unnecessarily fails. Repeating this results in a black hole where
a failing server keeps getting new requests.
Change-Id: Ic51e6584c1fbda3eb7821cb47f759c77e562cc65
Closes-Bug: #1550455
Use nopreempt for keepalived2016-03-14T01:36:33+00:00SamYaplesam@yaple.net2016-03-14T01:36:33+00:00urn:sha1:024d76534e5d69239a2a8290dab110bfa3c75306
Without this option the vip will always bounce to the highest priority
node that is up. So if you reboot the highest priority node the vip
will fail to the second highest. When the highest priority node
recovers it will claim the vip again leaving you will two fail overs
rather than one.
TrivialFix
Change-Id: I4a3c6c10eee391cdbdd80c44a71a9fafd1069944
Add authentication for keepalived2016-03-04T13:28:01+00:00Jeffrey Zhangjeffrey.zhang@99cloud.net2016-02-06T14:18:01+00:00urn:sha1:e6b230d78436dfb7b38b1c30c4a9325909ae1d20
TrivialFix
Closes-Bug: #1551314
Change-Id: Id85859500aec283703b6b6714abf213a42286182
Change kolla_internal_address variable2016-02-26T20:00:09+00:00SamYaplesam@yaple.net2016-02-26T01:02:25+00:00urn:sha1:d3cfb2052a7321606e3a46fd6846f776d28afd86
Due to poor planning on our variable names we have a situation where
we have "internal_address" which must be a VIP, but "external_address"
which should be a DNS name. Now with two vips "external_vip_address"
is a new variable.
This corrects that issue by deprecating kolla_internal_address and
replacing it with 4 nicely named variables.
kolla_internal_vip_address
kolla_internal_fqdn
kolla_external_vip_address
kolla_external_fqdn
The default behaviour will remain the same, and the way the variable
inheritance is setup the kolla_internal_address variable can still be
set in globals.yml and propogate out to these 4 new variables like it
normally would, but all reference to kolla_internal_address has been
completely removed.
Change-Id: I4556dcdbf4d91a8d2751981ef9c64bad44a719e5
Partially-Implements: blueprint ssl-kolla
Implement Option for Two VIPs to separate API traffic2016-02-24T14:18:06+00:00Dave McCowandmccowan@cisco.com2016-02-18T18:50:39+00:00urn:sha1:34c2cb8e64c4758ec9e834dc3fabc9f5835fe9ac
To improve security, operators have asked for two VIPs for
their cloud.
VIP 1 is the internal VIP that can reach internal and admin endpoints.
In addition, the internal VIP can also reach other internal services,
such as the database and message services.
VIP 2 is the external VIP that can only reach public endpoints.
With one VIP only, all services are reached at the same address.
To add a second VIP, this patch adds two new configuration parameters.
kolla_external_vip_address: is an IPv4 address to use for created VIP
kolla_external_vip_interface: is the network interface to use for VIP
In this scenario, the first VIP (the internal VIP), is defined by
the original parameters (kolla_internal address and network_interface).
When using two VIPs, the existing kolla_external_address parameter
should be/point to/resolve to the kolla_external_vip_address.
Closes-bug: 1535333
Change-Id: I5bfcefaf7899298455cdade8209c34324aebfecb
First keepalived container is started with wrong priority2015-09-10T10:22:00+00:00Vladislav Belogrudovvladislav.belogrudov@oracle.com2015-09-10T10:22:00+00:00urn:sha1:9d156eb005608fa822ff049a4cbd19890fd102f5
First keepalived container is started with priority 0 but the
latter should be in range 1-255. This gives error and keepalived
resumes with default priority 100.
Change-Id: Ib11d0072a96b818d86c81a32e78118c0c82b74d8
Closes-Bug: #1494237
Fixes group name for keepalived.conf2015-08-08T05:28:07+00:00Sam Yaplesam@yaple.net2015-08-08T05:28:07+00:00urn:sha1:1ab8bc184c7d8dc4af076ce569cf91cc79285b10
Also included is removing the executable bit on haproxy.cfg.j2 as it
should not have those permissions in the repo. It has no affect on the
templating process.
Change-Id: I9c76e528896bdf1799b8eeb62ae77bc4ad0b4449
Closes-Bug: #1482832
Add check_script for haproxy in keepalived2015-08-05T11:10:53+00:00Sam Yaplesam@yaple.net2015-08-05T11:10:53+00:00urn:sha1:8ede380f1d4d702bf29ea31e6f66dafd8518c759
This patch checks that haproxy is alive and running. It does this by
using socat to talk to the haproxy socket. That socket will only
respond successfully when haproxy is active and functional.
Change-Id: I528588d5742071103c28109a69842a6f935232c2
Closes-Bug: #1478570