If the Octavia/Amphora management network is created by Kolla, support
setting the IP address family and IPv6 address/RA mode.
Closes-Bug: 1913409
Change-Id: I9f2ef2196654c91596cb5c4b3c157bcee267226a
This change enables the use of Docker healthchecks for manila services.
Implements: blueprint container-health-check
Change-Id: I3a2239764b7e3d6db51e535404388a512aba7629
Need to consider Negative seqno to compare in some cases,
but the task does not support to do that, we need to make it work.
1.we use mariabackup to restore datas on control1, delete the
mariadb data on control2 and control3, and then use cluster recovery,
as a result that the seqno of the other two nodes will be '-1'.
2. add one more control node into our existing mariadb cluster,
and then use cluster recovery, the seqno of the new node will be '-1'.
Change-Id: Ic1ac8656f28c3835e091637014f075ac5479d390
There are inconsitencies across the documentation and the source code files
when it comes to project's name (Kolla Ansible vs. Kolla-Ansible). This
commit aims at unifying it so that the naming becomes consistent everywhere.
Change-Id: I903b2e08f5458b1a1abc4af3abefe20b66c23a54
There are a few issues fixed here:
- The Barbican API service doesn't set a log file, so all the Barbican API
service logs go to loadwsgi.py.log by default.
- The logs in loadwsgi.py.log are not ingested properly by Fluentd.
- uWSGI logs go to barbican-api.log. This would normally be used as the log
file for the Barbican API service logs.
This patch makes the following changes to address the above issues:
- All uWSGI logs (from the Emperor and Vassals) go to barbican_api_uwsgi_access.log
Although these logs aren't strictly all access logs, this follows the existing
pattern for WSGI logs.
- The Barbican API service logs are written to barbican-api.log instead of
loadwsgi.py.log. This follows the pattern used by other OpenStack services.
- Fluentd is configured to parse the Barbican API service logs as it would with
other OpenStack Python services.
Change-Id: I6d03fa8c81c52b6f061514a836bbd15bb6639aaf
Closes-Bug: #1891343
--db-sock JSON-RPC socket name
--db-nb-sock OVN_Northbound db socket
--db-sb-sock OVN_Southbound db socket [1]
so should use db-nb-sock and db-sb-sock
Closes-bug: #1913031
[1] https://github.com/ovn-org/ovn/blob/master/utilities/ovn-ctl
Change-Id: Ife38237a308c87465d5ac3faf7d8de93fd49de4e
Libvirt may reasonably expect that its secrets directory
(/etc/libvirt/secrets) is persistent. However, the nova_libvirt
container does not map the secrets directory to a volume, so it will not
survive a recreation of the container. Furthermore, if Cinder or Nova
Ceph RBD integration is enabled, nova_libvirt's config.json includes an
entry for /etc/libvirt/secrets which will wipe out the directory on a
restart of the container.
Previously, this appeared to cause an issue with encrypted volumes,
which could fail to attach in certain situations as described in bug
1821696. Nova has since made a related change, and the issue can no
longer be reproduced. However, making the secret store persistent seems
like a sensible thing to do, and may prevent hitting other corner cases.
This change maps /etc/libvirt/secrets to a Docker volume in the
nova_libvirt container. We also modify config.json for the nova_libvirt
container to merge the /etc/libvirt/secrets directory, to ensure that
secrets added in the container during runtime are not overwritten when
the container restarts.
Change-Id: Ia7e923dddb77ff6db3c9160af931354a2b305e8d
Related-Bug: #1821696
The handler was firing even when we were only generating config.
This is an issue because the services may not have been deployed.
TrivialFix
Change-Id: I2f832d73138b4c9f29e3c71e2463293eab71483a
Adds the following new Zuul job for testing deployment of Monasca and
associated services:
* kolla-ansible-centos8-source-monasca
All core OpenStack services except for Keystone are disabled to ensure
enough memory is available.
A follow up patch will replace the basic tests here with Tempest.
Co-Authored-By: Doug Szumski <doug@stackhpc.com>
Change-Id: I5d33fd3d7b69798ba0aa23509f7b809065f61c19
Prior to this change it was not possible to generate the config
before deploying the services as you'd hit:
RUNNING HANDLER [Waiting for grafana to start on first node] *************************
Monday 18 January 2021 15:06:35 +0000 (0:00:00.182) 0:04:39.213 ********
skipping: [sv-h22a8-u19]
skipping: [sv-h22a5-u36]
FAILED - RETRYING: Waiting for grafana to start on first node (10 retries left).
This would never succeed as the service has not yet been deployed.
TrivialFix
Change-Id: I9437a049b24e5e613a7e66add481a8983b84867a
It is now possible to deploy either 1.x or 2.x version of Prometheus.
The new 2.x version introduces breaking changes in terms of storage
format and command line options.
Change-Id: I80cc6f1947f3740ef04b29839bfa655b14fae146
Co-Authored-By: Radosław Piliszek <radoslaw.piliszek@gmail.com>
With this patch, Monasca no longer relies on automatic topic creation
in Kafka, and instead pre-creates all topics before bringing up the
containers. If the topic already exists then it will not be
changed, therefore existing users are not affected.
This patch allows per topic customisations, such as increasing the
number of partitions on particular topics and also works around
a race condition in automatic topic creation where multiple instances
of the same service could race to create a topic causing some of the
services to restart and throw an error before resuming normal
operation.
Change-Id: Ib15c95bb72cf79e9e55945d757b248e06f5f4065
This change enables the use of Docker healthchecks for blazar
services.
Implements: blueprint container-health-check
Change-Id: I3eaa0906b66ae6afe4d5f23048e5cadb3f984845
This change enables the use of Docker healthchecks for barbican
services.
Implements: blueprint container-health-check
Change-Id: Iffda6569103f95733bd7fb80aef31c6a608a55b7
This change enables the use of Docker healthchecks for cinder
services.
Change-Id: I9bef02a66aae2024052078d8354059ab28a71e1e
Implements: blueprint container-health-check
kolla-ansible upgrade failed when octavia_auto_configure set
to true. because upgrade action don't register the resources
info.
this change adds some tasks to query the resources info
for upgrade action in octavia role.
Change-Id: I4b0ac001b38bee81d983dd68534b9d0e78b4f6d7
The bootstrap process tries to removes existing apparmor profiles but
doesn't consider the case where those are disabled. This change fixes
the scenario where the libvirt profile exists but is disabled.
Closes-Bug: 1909874
Change-Id: Ied0f2acc420bd5cf1e092c8aee358cba35bd8d5d
This change enables the use of Docker healthchecks for cloudkitty
services.
Implements: blueprint container-health-check
Change-Id: I19892035382ffff5200e88da53408a19e72c9d68
Adding docker apt gpg key requires gpupg to be installed.
Task will fail on minimal Debian 10 install as gnupg absent.
Change-Id: I979f88162ad8a206e413b37ac7fb09bcc912e016
The default kolla-ansible deployment of solum_api do not provide a value for 'host' variable in
[api] section of the solum.conf
This causes the solum_api service to fallback to default host 127.0.0.1, making haproxy unable to
provide services.
This fix adds value for 'host' variable, so the solum_api service able to listen on provided ip,
making it available to services like haproxy accessing the service remotely
Closes-Bug: 1909986
Change-Id: I38a4ecab071306143952c8036830318c476797f2
