Added storage policy so that deployers can override how to store the logs.
"per_host" stores logs in a sub-directory per host. "per_program" stores logs
in a single file per application which facilitates troubleshooting easy.
Change-Id: I5f71d61549f911ba8ead19e17ea481a4e0fc0262
This fix separates the remote log streams from the local
by binding the remote ruleset to the UDP and TCP input modules.
Additionally new overrides are provided to allow for better customization:
``rsyslog_server_logrotation_window`` defaults to 14 days
``rsyslog_server_ratelimit_interval`` defaults to 0 seconds
``rsyslog_server_ratelimit_burst`` defaults to 10000
The rsyslog.conf is also now using v7+ style configuration settings
Change-Id: I5759ea8fb7eaad79d857a335a4aede558aa0067d
Closes-Bug: #1621559
The current method of installing the distribution packages required is
set in the tasks and cannot be changed by a deployer.
Currently the apt task always installs the latest package. This results
in unexpected binary changes when a deployer may simply be trying to
execute a configuration change.
This patch adds the ability for a deployer to change the desired state
so that the results are predictable.
Change-Id: If54f50bed876970c626e67f8501d581f68476c2f
This is an implementation of a pattern for multi-distro support by
including logic to deploy packages via either apt-get or yum.
This change has been tested with CentOS 7 and Ubuntu 14.04. Package
names and other distro/family specific variables are supplied via one
of the files in vars/ utilizing the following precedence:
"{{ ansible_distribution | lower }}-{{ ansible_distribution_version | lower }}.yml"
"{{ ansible_distribution | lower }}.yml"
"{{ ansible_os_family | lower }}.yml"
In this change, only the files corresponding to 'ansible_os_family'
have been provided. The included 'families' are 'debian' and 'redhat'
This allows for support of distros other than Ubuntu and CentOS, such
as Debian and Fedora, more easily in the future.
Change-Id: I78c8c3be9d00fc505fabc83de36dfd43b8e85848
Workarounding the upstream ansible apt module bug
documented here:
https://github.com/ansible/ansible-modules-core/pull/1517
For the next versions of ansible we'll be using, we should
check if the apt bug is fixed. When it's fixed, we could
abandon this change and use the standard apt module
with correct cache handling.
Change-Id: I00d6d0704e77bc3f8f19fb36933ac518b3372e8d
Dmitriy Rabotyagov