| Age | Commit message (Collapse) | Author | Files | Lines |
|
There are several images installing 'python3-libvirt' package. Which for
Debian reside in 'libvirt' repo. So let's enable it where needed.
Change-Id: I1c91d27f2578f5ca7c83c4747725b1d9371880b0
|
|
We moved to CentOS Stream 8. Just no one noticed that binary target was
failing to build.
This change sorts out all failing images.
Change-Id: Ia7768caabfe214a629339d50973d0d9873fc65d5
|
|
|
|
Change-Id: I2125001586c6ee999e171716d83ddf29bf398e8a
|
|
We use official CentOS 8 Stream image as a base.
So far Stream does not have own SIG repos
RDO Wallaby packages will be built against Stream
Kolla CI jobs are renamed to centos8s. Kolla-Ansible ones will follow
in later patch.
Change-Id: Ibb23c9d0caf115fcbba7bd322ecebe8d80b6821a
|
|
|
|
|
|
Upgrade to the latest ELK OSS release. Due to the licensing change, this
effectively pins us to 7.10.x which is supported until 2022-05-11 [1].
This patch also takes advantage of the ARM artifacts which have
been kindly provided since the 7.8.0 release [2].
[1] https://www.elastic.co/support/eol
[2] https://www.elastic.co/blog/elasticsearch-on-arm
Change-Id: Icfa3db5788b25f70ee75411dbaf20d8d4a6a734b
|
|
|
|
This reverts commit 61def281d077f88051d1b1a14dfdbfabac036c8c.
Reason for revert: --location was already in curlrc and it was unified in change I46b77978926fc2b578a68d1aaa944b2198af0685
Change-Id: I066d747400ede30037ff324ad55430af7c35dc18
|
|
|
|
Change-Id: I63f6491919eba913bfd35a294b4cc17cc4c68603
|
|
Deprecates support for Prometheus v1.x.
In Xena support for this image will be removed from Kolla.
Change-Id: I31a8c675323f367a2d59bfb31644ee5b4b44e3f2
|
|
-L for curl: If the server reports that the requested page has moved to a different location (indicated with a Location: header and a 3XX response code), this option will make curl redo the request on the new place
It fixes build error for me:
INFO:kolla.common.utils.prometheus-v2-server: ---> Running in 693fd4095c77
INFO:kolla.common.utils.prometheus-v2-server:curl (https://github.com/prometheus/prometheus/releases/download/v2.23.0/prometheus-2.23.0.linux-amd64.tar.gz): response: 302, time: 0.166583, size: 640
INFO:kolla.common.utils.prometheus-v2-server:
INFO:kolla.common.utils.prometheus-v2-server:gzip: stdin: not in gzip format
INFO:kolla.common.utils.prometheus-v2-server:
INFO:kolla.common.utils.prometheus-v2-server:tar: Child returned status 1
INFO:kolla.common.utils.prometheus-v2-server:tar: Error is not recoverable: exiting now
Change-Id: I095ca6f34cc7c7bca485e9ec019cc52aeb8e3ff4
|
|
1. stop pinning networking-hyperv
Pike release was long time ago so maybe it is time to unpin it?
commit 6dc8e978462fd08122133e273ae956721997d3af
Author: Dan Ardelean <dardelean@cloudbasesolutions.com>
Date: Mon Aug 28 12:56:25 2017 +0300
Change networking-hyperv version for Pike
2. stop install vmware-nsxlib as a plugin
vmware-nsx is a plugin and we install it already
vmware-nsxlib can be fetched from Pypi
Solves:
INFO:kolla.common.utils.neutron-server:The conflict is caused by:
INFO:kolla.common.utils.neutron-server: The user requested vmware-nsxlib 15.0.8.dev129 (from /plugins/vmware-nsxlib-15.0.8.dev129)
INFO:kolla.common.utils.neutron-server: vmware-nsx 15.0.1.dev424 depends on vmware-nsxlib>=17.0.0
Change-Id: I6ef344d463333e5cdc3a0850c8e068218779fdbd
|
|
|
|
|
|
|
|
To better utilise caches during the working week, we decided to publish
only weekly (as opposed to daily). This is due to DockerHub-imposed
limits.
If published images are broken, or need to be refreshed, then this patch
can be temporarily reverted.
Change-Id: I3916b703e40f0b80c47501ff7faa958b903be05c
|
|
kolla-ansible runs ovs-dpdkctl.sh inside container, and ovs-dpdkctl.sh
requires crudini.
Change-Id: Iad84dd12432befe9250c50d4094b1e5e2e0cf8ee
|
|
|
|
|
|
Change-Id: Ia32e44a13c0280767082f11f730c8a54f9bb25c5
|
|
|
|
|
|
This fixes comparisons when files are not Unicode-encoded.
A relevant unit test is included.
It can be used as a base for other _cmp_file method unit tests
if the need arises.
Change-Id: Ic638516eb92d24ad247a7866fd1b5e2ac0400388
Closes-Bug: #1913952
|
|
Change-Id: I6055deeb3b2ae5e856dc23f69da1525874c59409
|
|
Change-Id: Ib61768465a58e70af5ca43de80fbfb5099f51cac
|
|
|
|
Change-Id: Idfec98f5dee6419dabbd0824b60af60eb0ecd3f2
|
|
Nova requires libvirt 6.0.0 or newer in Wallaby. So I backported 7.0.0
from Debian 'testing'.
AArch64 and x86-64 are covered.
Change-Id: Ia678cd43b5ce53aee528674280f674c596a278ff
|
|
Change-Id: I4d20f23a9b26364943bf967908255d82c8f6621b
|
|
With tips and clarifications.
Adapted from Kolla Ansible's patch. [1]
[1] https://review.opendev.org/c/openstack/kolla-ansible/+/759254
Change-Id: I07490bc3a7809415fe1734aee255143c205d9573
|
|
Change-Id: Iea2c02d59d2906141ca37ce9b48a0f7f4fc14421
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Debian still needs it but it is enabled for all architectures.
Change-Id: I6a3ba599af3deedd450b4ffff6b86a0c04628340
|
|
|
|
We install pip in base image so why repeat?
Change-Id: Id903880b121d87d75b7b14084b0961b9ce99deba
|
|
Change-Id: I448793566202e672348733b8bbbd6665dc251dfe
|
|
Signed-off-by: Christian Berendt <berendt@betacloud-solutions.de>
Change-Id: Id3187b2b95e9b9bd3d9233a498f7c45e66c604c7
|
|
When running with `-o nounset` since [1], the Horizon became quite
fragile to run as it started requiring all ENABLE_* environment
variables to be set upfront. Normally they are - via kolla-ansible.
However, when working with it outside of kolla-ansible or removing
services (like it was the case 3 times during the Wallaby cycle),
it creates needless issues (like having to wait for images to get
published for kolla-ansible gate or users bumping into irrelevant
incompatibilities [2]).
This patch makes sure all ENABLE_* environment variables default
to 'no' and are no longer required to be set when there is no
need to set them to 'yes'.
[1] 032804e5a0ddf89f7726880d1b57dd492d7d5c07
[2] https://bugs.launchpad.net/kolla/+bug/1911141
Change-Id: I644e072a699dccd8f32a24e484ff6dab7b9b449d
|