- Jul 06, 2020
-
-
Zuul authored
-
wu.chunyang authored
Change-Id: I51054561af93f03e09fa86eeec7c579aca103cdf
-
Zuul authored
-
- Jul 05, 2020
- Jul 03, 2020
-
-
Pierre Riteau authored
Change I810aad7d49db3f5a7fd9a2f0f746fd912fe03917 for supporting multiple Nova cells updated the list of containers that require a policy file to only include nova-api, nova-compute, and nova-compute-ironic. The nova-conductor config.json template was left unchanged and fails to copy the nova policy file into its container. This can be seen on a fresh deployment, but might be missed on an upgrade if an older policy file is still available in /etc/kolla/nova-conductor. This commit removes the nova_policy_file block from the nova-conductor config.json template, as it shouldn't be required. Backport: ussuri, train Change-Id: I17256b182d207aeba3f92c65a6d7cf3611180558 Closes-Bug: #1886170
-
- Jul 02, 2020
-
-
Zuul authored
-
wu.chunyang authored
barbican alway use default notification driver (defalt '') so we should change this value according to whether enable notification Change-Id: Ia17a64fe9bf31042369dec19f1f76b1ab8592288
-
Zuul authored
-
Justinas Balciunas authored
Time format in Ruby Time.strptime is not accepting padding flags, therefore we need to remove them for the Fluentd to be able to parse MariaDB xinetd logs properly. Change-Id: Iabfa9afdcad505106a5580eb2d058273ee5f7c1f Closes-Bug: #1886002
-
Stig Telfer authored
In Fluentd v0.12, both the in memory and file buffer chunk size default to 8MB. In v1.0 the file buffer defaults to 256MB. This can exceed the Monasca Log or Unified API maximum chunk size which is set to 10MB. This can result in logs being rejected and filling the local buffer on disk. Change-Id: I9c495773db726a3c5cd94b819dff4141737a1d6e Closes-Bug: #1885885 Co-Authored-By:
Sebastian Luna Valero <sebastian.luna.valero@gmail.com>
-
- Jul 01, 2020
-
-
Zuul authored
-
Zuul authored
-
Zuul authored
-
Radosław Piliszek authored
In the spirit of Kolla-Ansible, we generally try to provide workable defaults. The default for Elasticsearch curator schedule was fine except for multinode deploys where it would cause all nodes to run at the same time producing broken runs (race condition in the get-delete cycle). It is easy to improve this situation by embracing poor-man's reimplementation of keystone's fernet key rotation schedule. ES Curator does not need all the complexity of the former so it can be handled very well by shifting by as many hours as the instance's index dictates. It should rarely if ever need more time (most likely still in minutes range rather than hours). Change-Id: I9d6758c8550308d13d936de1a14afbe4124e593b
-
Stig Telfer authored
Resolve trivial syntax error in Fluentd output config for Monasca. Change-Id: I20b37bb83a76bfabb1126925a1b4f1f59767b7a3 Co-Authored-By:
Sebastian Luna Valero <sebastian.luna.valero@gmail.com> Closes-Bug: #1885873
-
Bharat Kunwar authored
While all other clients should use internalURL, the Magnum client itself and Keystone interface for trustee credentials should be publicly accessible (upstream default when no config is specified) since instances need to be able to reach them. Closes-Bug: #1885420 Change-Id: I74359cec7147a80db24eb4aa4156c35d31a026bf
-
- Jun 30, 2020
-
-
Radosław Piliszek authored
There were two issues with it. Lack of /usr/local/bin in PATH for CentOS and wrong crontab path for Ubuntu/Debian. This patch mirrors how it is handled in keystone. Change-Id: Ib54b261e12c409d66b792648807646015826e83c Closes-Bug: #1885732
-
Zuul authored
-
Zuul authored
-
Zuul authored
-
Radosław Piliszek authored
Mostly due to move to Python3-only. Also fix the other venv docs to avoid virtualenv. :-) Change-Id: Id89c4ec6ff8b80feace01a3dee7dd30dd4cc5ec5
-
- Jun 29, 2020
-
-
James Kirsch authored
The Zun configuration file does not set the CA for the clients the Zun service uses: zun_client, glance_client, neutron_client, cinder_client, and placement_client. This will cause the Zun service to fail when TLS is enabled in the OpenStack deployment. Depends-On: https://review.opendev.org/#/c/736809 Change-Id: Ieed843c890210608699c1a63deed66c9bb63986c
-
Mark Goddard authored
Recently a feature was merged to support pulling in multiple configuration files from a globals.d directory. However, if this directory does not exist, we get the following error when executing kolla-ansible: find: '/etc/kolla/globals.d': No such file or directory This change addresses this by redirecting find command stderr to /dev/null. TrivialFix Change-Id: Ie5aa511a5ebf3355817a7c3bb65b09ac5dcf2b67
-
Zuul authored
-
Zuul authored
-
Christian Berendt authored
Change-Id: Ia22f286e85be90983ca79291b3a54596bba30d6c
-
- Jun 27, 2020
-
-
James Kirsch authored
The etcd service protocol is currently configured with internal_protocol. The etcd service is not load balanced by a HAProxy container, so there is no proxy layer to do TLS termination when internal_protocol is configured to be "https". Until the etcd service is configured to deploy with native TLS termination, the etcd uses should be independent of internal_protocol, and "http" by default. Change-Id: I730c02331514244e44004aa06e9399c01264c65d Closes-Bug: 1884137
-
- Jun 26, 2020
- Jun 25, 2020
-
-
Zuul authored
-
Michal Nasiadka authored
Currently openvswitch sets system-id based on inventory_hostname, but when Ansible inventory contains ip addresses - then it will only take first ip octet - resulting in multiple OVN chassis being named i.e. "10". Then Neutron and OVN have problems functioning, because a chassis named "10" will be created and deleted multiple times per second - this ends up in ovsdb and neutron-server processes using up to 100% CPU. Adding openvswitch role to ovn CI job triggers. Change-Id: Id22eb3e74867230da02543abd93234a5fb12b31d Closes-Bug: #1884734
-