aboutsummaryrefslogtreecommitdiff
path: root/ansible/roles/haproxy/templates/keepalived.conf.j2
AgeCommit message (Collapse)AuthorFilesLines
2016-11-15Remove Ansible from KollaSteven Dake1-33/+0
Change-Id: I5396e4b9927d3e65b6aa4185238a43a4765a996b
2016-04-01Make keepalived virtual_router_id param configurableCarlos Cesario1-2/+2
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
2016-04-01When two interfaces are used for two VIPs, tie them togetherDave McCowan1-21/+8
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
2016-03-14Use nopreempt for keepalivedSamYaple1-2/+4
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
2016-03-04Add authentication for keepalivedJeffrey Zhang1-0/+8
TrivialFix Closes-Bug: #1551314 Change-Id: Id85859500aec283703b6b6714abf213a42286182
2016-02-26Change kolla_internal_address variableSamYaple1-1/+1
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
2016-02-24Implement Option for Two VIPs to separate API trafficDave McCowan1-1/+17
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
2015-09-10First keepalived container is started with wrong priorityVladislav Belogrudov1-1/+1
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
2015-08-08Fixes group name for keepalived.confSam Yaple1-1/+1
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
2015-08-05Add check_script for haproxy in keepalivedSam Yaple1-1/+2
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
2015-07-30Rename role name to service nameSam Yaple1-1/+1
The original purpose for having an abstract like 'database' rather than the service name of 'mariadb' has been change. Our direction is different and this patch reflects consistent naming throughout Change-Id: I704896191cc5243f9dab2a4cca9120e9dc2ceb2c Closes-Bug: #1478328
2015-07-30Add keepalived to ansibleSam Yaple1-0/+19
Adds the needed ansible bits to support keepalived Closes-Bug: #1479934 Change-Id: Iace29b23a0e923b1f5dc9a4f5bc0f88afce3ae62 Partially-Implements: blueprint ansible-service