progname is actually only fullfilled for Openstack logs and infra logs.
They are missing for program logging in RSYSLOG: HAPROXY and SWIFT.
When using Kibana, "progname" field appears empty, hence it's difficult
to know where logs come from.
Change-Id: Iae98af083cfb79d2a64fa0b70c86b0a01f7a336f
Closes-Bug: #1716051
WSGI configuration is missing the directive
"WSGIApplicationGroup %{GLOBAL}" after
WSGIProcessGroup" in the horizon template.
Of all WSGI configuration templates it is
the only one that does not have the
"WSGIApplicationGroup" line.
Change-Id: I3001901abbaae842f49179b6febf844337431afc
Closes-Bug: #1717922
New tacker has removed nova heat configure items,
but the tacker role is still using it.
In addition, the ceilometer and aodh are backend OpenStack
components, the configuration of feature in tacker does not depend
on them directly.
Change-Id: I475ff763475ed699a1e7498cc9898bd71d00ae7c
Closes-bug: 1718113
kolla designate DNSaaS makes use of containerised bind9 servers
as it's default designate_backend. These can be disabled by
setting designate_backend to "no". default: "bind9"
This commit adds two new properties:
1) designate_backend_external
which can be enabled by setting it to 'bind9'. default: "no"
and
2) designate_backend_external_bind9_nameservers, which can
accept a csv list of all the external server addresses.
(default: "")
The following attributes should either be set:
'internal' (the default)
designate_backend: "bind9"
designate_backend_external: "no"
(designate_backend_external_bind9_nameservers is ignored)
or
'external'
designate_backend: "no"
designate_backend_external: "bind9"
(designate_backend_external_bind9_nameservers must be populated)
Configuration override files to align with external bind9
dns servers must be supplied manually,
/etc/kolla/config/designate/rndc.key
/etc/kolla/config/designate/rndc.conf
Change-Id: I8dbe6fd4fe7820b9143604d89e8399b07e07c3fd
In some scenarios it may be useful to configure custom fluentd outputs
to forward logs to a logging service other than elasticsearch.
This change supports configuration of fluentd outputs by placing
output configuration files in /etc/kolla/config/fluentd/output/*.conf.
Change-Id: I3c0b271d88dbb307ba3a23546e29c72e8baeca55
Implements: blueprint fluentd-custom-outputs
HyperV Nova needs some nova.conf changes to work properly.
More precisely: 'auth_plugin' becomes 'auth_type'.
Closes-Bug: #1716956
Change-Id: Ic2342e2303b780398f81b3024fe5b11111e34a6e
Showing the CLI installed does not verify SFC is working at all.
Refer to updated link with process to create a chain.
networking-sfc is already installed in neutron,not needed to
use custom builds anymore.
Change-Id: Ib92482eba6e27ef1e856f0a54aeb4cdfc0495117
Barbican-api log is a uswsgi process and fluentd expects as
openstack service process.
This change moves log type to uswgi group.
Change-Id: Ifaf5645d0d19e133e41de0c55a55321fccfc391f
Closes-Bug: #1716513
Checking http://files.openstack.org/docs-404s/2017-09-08.txt the link
/kolla-ansible/latest/quickstart.html gives a 404 and is most wanted.
The link now is /kolla-ansible/latest/user/quickstart.html - let's
update in tree docs for this.
Fix other broken links as well - with using intra-links instead of
external links - this will make it easier to notice breakage when files
are moved.
Change-Id: I62655afd9f270fa83c07d86aa91346af6337ca32
Copy the patterns from the rabbit checks, skip some pre-checks when the
container has already been started. Without this change the pre-checks
fail when you re-run the deploy, i.e. the port is not free because
rabbit is already running on that port.
This bug was triggered because murano is enabled, and this change has
been added to add the extra rabbitmq instance by default:
d8fe3ea780c188b6e937ab6f08a8475d2330a9fa
Closes-Bug: #1715135
Change-Id: I0eb8785e7cd4eadfa792ea14a27f54a891b2bf02
1) Update doc links according to OpenStack document migration
2) Use https instead of http for docs links
Change-Id: Iedf05f9264d825ce2d4b42321fe81b93cf8f7665
