This commit is to apply resource-constraints only to few OpenStack services.
Commit to apply constraints to other services will be made in coming commits.
Partially-Implements: blueprint resource-constraints
Change-Id: Icafa54baca24d2de64238222a5677b9d8b90e2aa
Add become to all tasks that use the module "kolla_docker"
Change-Id: I4309c4011687b88ec31d739fd8f834fe2326ff10
Partial-Implements: blueprint ansible-specific-task-become
We still default to kolla_internal_vip_address. However, in some cases
this won't work, such as when kolla_internal_vip_address is a hostname,
not an IP. This way users can override it in globals.
Change-Id: I393a2a41ed3bf91f325042cca2310175927bdb40
- rename action and serial to kolla_ansible and kolla_serial
- use become instead of "sudo <command>" in shell
- Remove quota for failed_when and changed_when in rabbitmq tasks
Change-Id: I78cb60168aaa40bb6439198283546b7faf33917c
Implements: blueprint migrate-to-ansible-2-2-0
This patchset implements yamllint test to all *.yml
files.
Also fixes syntax errors to make jobs to pass.
Change-Id: I3186adf9835b4d0cada272d156b17d1bc9c2b799
In the old implementation, if there is no external ntp server, only one
local chrony server is supported. If multi chrony-server is configured,
chrony client can not sync with them.
In the new implementation
* use VIP to connect chrony-server, which ensure multi local chrony
servers are supported.
* chrony servers depend on VIP. So chrony-server group should be
the same with haproxy group.
* prevent chrony client sync from itself.
* Change owner to chrony:kolla for chrony log folder
* fix keysfile path
* use chrony user for centos and ubuntu image
* fix permission issue for /var/lib/chrony folder
Closes-Bug: #1705200
Change-Id: I6e85fda9824b5ddc7a96895425c5932a3566c27e
Some roles have a symlink to deploy.yml file
for reconfigure. This is causing some issues.
"included task files must contain a list of tasks"
Change-Id: Ie7ade52900a61bc1c5b867fa7a8f75fc541a6426
Closes-Bug: #1694251
Normally chronyd will cause the system to gradually correct any time offset, by slowing down or speeding up the clock as required.
In certain situations, the system clock might be so far adrift
that this slewing process would take a very long time to correct the system clock
Change-Id: I939b6aae1dbeb133203085ec68bdb9f7936ee9ef
Closes-Bug: #1696056
Many of the templates use 600, remove unnecessary permission
on these templates to bring them in line with the others.
Change-Id: I30fe1b3822b9c7bb6ab98729fc519dc1d603db27
The local keyword is used to allow chronyd to appear synchronised to
real time (from the viewpoint of clients polling it), even if it has no
current synchronisation source.
Change-Id: I27d945abb87a37d2fdf972a58c51e2f0994e3de8
Closes-Bug: #1688682
Chrony drops root to user 'chrony' on startup, so it's config file
should be owned by user this user.
Change-Id: I8ba976cc685d2e50e09211f67507487a1e0e3c5f
Add a new subcommand 'check' to kolla-ansible, used to run the
smoke/sanity checks.
Add stub files to all services that don't currently have checks.
Change-Id: I9f661c5fc51fd5b9b266f23f6c524884613dee48
Partially-implements: blueprint sanity-check-container
