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
This fixes a bug in newest_dhcp_lease.py where the get_mac_address
function currently searches for a "bridge" interface instead of
searching for the interface whose source network is
"vagrant-private-dhcp".
Change-Id: Iea0b25f893b959b5e319b117e7a1c4c63a00dd23
Closes-Bug: #1548742
Currently Heka fails to parse the RabbitMQ logs. There are two
problems:
1. The rabbit-sasl.log file is ignored but the file_match expression
does not match.
2. The delimiter used in the RegexSplitter makes Heka stop on the
very first log entry. '\n\n(=[^=]+====' (with two \n's) is
a better delimiter. deliver_incomplete_final is used to get the
final log entry.
TrivialFix
Change-Id: I94720340d5b2d6fd5d7641b9ff58733f6cd882ee
Made changes in section Managing Ceph to correct the grammatical mistake.
Signed-off-by: Richa Yadav <ricyadav@cisco.com>
Change-Id: I2ed13f766dd39a7ac816af86664986b8d2700d80
This is single task to upgrade both haproxy and keepalived. It stops
slave nodes of keepalived and upgrades them separately to avoid
VIP migration and allow nearly no-downtime upgrade
Change-Id: I06124635a3f3553a4e8e91013cefbf897dd7179f
Implements: blueprint upgrade-haproxy
Implements: blueprint upgrade-keepalived
Partially-implements: blueprint upgrade-kolla
The permissions fix was not applied due to a recent patch.
Related-Id: I37d737509bc7cf3dc74bb13ecb0a6ae68080556e
TrivialFix
Change-Id: Ica737a8e51cdb66b06a09b5484a4915d6e26ee06
- Provided info on installing ansible via yum from EPEL and pointed
readers to the EPEL docs to learn how to install/enable the repo
Change-Id: I4bf87fbf90779be85293eb65fe7cd2ffe548d6ae
In Deploying Kolla section of the quickstart.rst IP addr needed to
be changed IP address.
Change-Id: I4f3895d6f05340a0608b2b66170a769bd1454fb7
Signed-off-by: Asha Saravanamohan <assarava@cisco.com>
Since docker 1.10.1 is required, and docker 1.8.2 does not work with Kolla,
Remove the downgrade instructions
TrivialFix
Change-Id: I461572a40b6fc96f73593cf989967449e4bc8e0a
Signed-off-by: Jason Myers <jason@jasonamyers.com>
The operators aren't mindreaders. Lets throw them a bone about
how to properly evaluate Kolla. This can probably be expanded
on.
TrivialFix
Change-Id: I70d0f6a63417dc9f361d8c14bbb512e1dcc44ed0
All manila rootwrap calls are failing in
source build because lack of sudoer setting
Change-Id: I301fd7b6ff3721328828c2e0384f7e320146731b
Partially-Implements: blueprint enable-manila-containers