| Age | Commit message (Collapse) | Author | Files | Lines |
|
[tool.setuptools.data-files] does not support recursive directory
installation. The old setup.cfg [files] worked because PBR's
FilesConfig.expand_globs() used os.walk() to expand docker/*, but
this hook is not triggered by the pbr.build PEP-517 backend.
Move docker/ into kolla/ and use [tool.setuptools.package-data]
instead. Update kolla_worker._get_images_dir() to check the kolla
package directory first so both editable and regular installs work.
Change-Id: I4fc452c03740ef22ebbb4e8d0d86c4f4783e2d09
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
The build-date label was rendered into a LABEL instruction on line
3 of every Dockerfile template, immediately after FROM.
Because Docker invalidates the cache for a changed instruction and
all subsequent layers, a date change caused a full rebuild of every
image on each new calendar day, even when nothing else had changed.
Fix this by removing build-date from the Dockerfile templates and
applying it as a --label argument at build time via image.labels.
Labels passed on the build command line are not part of the
Dockerfile cache key, so the date is still recorded in the image
metadata without affecting layer caching.
Change-Id: I8ef0d85bab1a999a4d09f7cbf0c088ca00fdcf77
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
Change-Id: Id6684e4356f68e4348c0f8c1c0c1e5397553397e
Signed-off-by: Piotr Milewski <vurmil@gmail.com>
Signed-off-by: Bartosz Bezak <bartosz@stackhpc.com>
|
|
Currently we are enabling repos irrespective of rpm/deb
statement blocks and not failing in the method used
if a repository is missing.
Downside is - we might be producing one more layer,
but it probably is a more logical approach.
This is required for adding rpm support in repos.yaml
that will also include failing on missing repositories.
Change-Id: I5479c5c935760f00fe4cd307366f261deee3199f
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
Previous apt preference missed the epoch and sub-packages, so no
pinning was applied.
Closes-Bug: #2115893
Change-Id: I5c765db0508a2ffec90ba149bb5ea9b90dd31bc8
Signed-off-by: Bartosz Bezak <bartosz@stackhpc.com>
|
|
We've seen multiple occassions of all these healthcheck commands
not being able to be executed in 30s after the switch to RMQ 4.1.
Let's put more information in the Docker/Podman healthcheck logs.
Change-Id: I4b1b54983144f5514a6703c255d2cb4fa052a0fb
|
|
Change-Id: I4f852176918531ea19210961fd1b4fa63bc0ecca
|
|
|
|
Change-Id: If15ba52acfd305aa9bbae382fe7429c11041e93f
|
|
This patch adds a way to patch files in a Docker
image built by Kolla. This is very useful for several
reasons, specifically:
- Custom modifications
- The stable branch of some library has a fix but no pip
package has been released
- Eliminates the need to package your own pip packages
- Eliminates the need to invent your own versioning to prevent
upstream versioning
- Eliminates the need to manage a pip server
- In other words, it eliminates the need to get a wheel into
the image and install it manually using any method not
previously mentioned
It is also highly desirable because, although Kolla can replace
the source for a service with a custom URL for a tarball or its
own Git repo, it cannot do this for dependencies pulled from pip.
I would also like to point out that this is a feature with its own
code path and works only if the user "inserts" a patch into the folder
patches/docker-image/something.patch and creates an analogous series
file for patch source code.
Simply said, this code will never interfere with the upstream build process
since this feature is not intended for use in upstream.
It is rather meant for downstream users who know what they are doing.
Now they just have an option to patch their images.
Everything works on all layers of the Docker image and stores a report
of applied patches which can then be seen in /etc.
This mechanism is similar as debian patch quilt.
Change-Id: I61d0790c5d4d070b7ea9e8c99c0a76ff5d22bf9d
|
|
This reverts commit 36a7cd053d5b13ecc9fad1866f244a733fdd58e5.
Reason for revert: feature not needed anymore, see here:
https://review.opendev.org/c/openstack/kolla-ansible/+/926146/comment/e593d721_7c48143b/
Change-Id: Ic0f9521c66240f13ff5b7fc94480dbbb76498339
|
|
Will be used to check if the current RabbitMQ version is high enough
before upgrading to the new one.
Change-Id: Ie133d6efc2e4c00002b8f0724e0183eaab35d1c5
|
|
Change-Id: I9eb51e079fee1322bcaaf9d481cd7890aeb77696
|
|
Pinning Erlang to 26.2.* (max supported version as per [1]),
so we don't break this in future when Erlang 26.3 becomes
available.
[1]: https://rabbitmq-website.pages.dev/docs/which-erlang
Change-Id: I1fd03a67914386129d7b0bb9be6aca86982f98f3
|
|
Currently we don't set timeout and the default is infinity.
Change-Id: Id1a87995a36e202fc0aaf82daf022ec10d78e37d
|
|
Erlang has been bumped to 26 as well.
Change-Id: I5a6e90790d9c3c148e118fdf2ce6089e0a6a343e
|
|
This reverts commit 600ed4f149a1cf542f54d7fc5005030f53c69a83.
Reason for revert: 3.11.18 is out with a fix
Change-Id: I4659bcd48ea32294b3ee84af9af94fae32b38bf3
|
|
Seems rabbitmq node drain got broken in 3.11.17
Related-Bug: https://github.com/rabbitmq/rabbitmq-server/issues/8414
Change-Id: I3a23670f85336344d8aebaded74dd65871837b82
|
|
This reverts commit dda3bf45b29537f4925dc3374cf96eb8ed5b652b.
Reason for revert: fixed in 3.11.13
Change-Id: Ia1288a7fecb2e4a96564bd9adb9ce9d8415c61ac
|
|
Change-Id: I040b24c294e5daa07ece9f4a0f58fcab5cdf185f
|
|
Change-Id: I4836806c0434caaff1e6fd1646aa5566b0c3d7e1
|
|
We switched repo to provide Erlang 25 but not switched to it.
Change-Id: I8b0a2f27ccb3db61a38d8fe89676f99eed1e3d75
|
|
We do not have Erlang 25 for CentOS Stream 9 on AArch64 so we revert to
use Erlang 24 from CentOS repository.
Also synced Erlang and RabbitMQ versions between images.
Change-Id: I1480de095eaea66c3a83a61ca3ff269953181e39
|
|
OpenStack 'zed' requires Python 3.8+ so RHEL 8 family has to go.
This changeset moves to CentOS Stream 9 while move to RockyLinux 9 is
planned as final solution.
CI moved to CentOS Stream 9 nodes.
Depends-on: https://review.opendev.org/c/openstack/kolla-ansible/+/839715
Change-Id: I113b9984294cf8663d3fc0c8840320e1d40ea731
|
|
There is no need to install it in other images.
Change-Id: I9fdb987533662ee532141b06fc23b64c92788429
|
|
3.10 comes with quorum queues support, Erlang 25 is the recommended series.
Change-Id: I67f8df66b4896a9b223c02ed09f68f3f43693849
|
|
Explicitly set the permissions on the kolla-toolbox kolla_extend_start
file. Also, since all extend_start files are sourced rather than
executed, the executable bits are now cleared throughout the project.
Change-Id: I5c2deb4a2e33575d57c852089f856a9acc6818d0
|
|
We have one install_type only now so that infra stuff is not needed
anymore.
Change-Id: I60d50ba7699d46d001eaef365fb84b0ce8e9b262
|
|
Also update Erlang to 24
Change-Id: Ifbaccc54896bab096a6d16dc7733941dd600cf39
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/828594
|
|
RabbitMQ requires Erlang 23+ and soon will bump to 24+.
On AArch64 we used version 22 as there was no other option. Now it is.
Change-Id: I667ccda5bb4edbfbfb97dfb0cea264837ed05cae
|
|
Change-Id: Ie5bacf5d76850e51aa5f20b34759f76f89f73a2c
|
|
RabbitMQ 3.8.14 is the last version with Erlang 22 support
Change-Id: I1d68a47f78b925af76c44c61af7da1465371e721
|
|
Now that we run without erlang pinned by the repository itself,
let's pin it on our side.
Change-Id: Ifa491b102ad0db7f6dc645ca552d83b53bcf3b46
|
|
With RDO use we did not disabled some repositories. This patch disable
them and enable where needed.
Change-Id: Ia9d537fe9c1ad54789d2bfb4027254fbb3defe7e
|
|
This script is used to check the health check of the rabbitmq container
Related patch of kolla-ansible:
https://review.opendev.org/c/openstack/kolla-ansible/+/780407
Change-Id: Icbdc9f9686ec1b6f6e1c0ca51ef557b49f32d289
|
|
Defaults to 'image_prefix' for now but shows which images gets their
names changed soon.
Change-Id: I0608e8f62f28d6667b4c8753c47553e4cbf75503
|
|
With the move to RHEL/CentOS 8 we no longer have Python 2 in our images
so there is no need for checking which Python version (2.x or 3.x) is
used inside of containers.
We also no longer have to support yum as a value for
distro_package_manager.
Partially-Implements: blueprint centos-rhel-8
Change-Id: Ie45cf3465fedddbde7856961527421883ba3d5c9
|
|
Upgrade and pin RabbitMQ to 3.8.
Upgrade Erlang to 22 to meet requirements:
https://www.rabbitmq.com/which-erlang.html
Start using bintray repository provided by RabbitMQ.
Linaro builds will be used for aarch64.
Implements: blueprint rabbitmq-version-upgrade
Closes-Bug: #1848452
Change-Id: I3d775fd832f2603181da89009cebc1370a61a023
|
|
This script is used by neither Kolla Ansible nor TripleO.
Change-Id: I4859a727b269dd13465d90dff50107e29d39956e
|
|
Change-Id: I9692dda817ef134d647247431565e1b58cf9da41
|
|
* Some further changes for python2 vs python3 packages
* Allow rabbitmq 3.7.*, since a newer erlang is available
* Switch from qemu-img-ev to qemu-img on CentOS 8
* bridge-utils no longer available on CentOS 8
* libvirt-daemon-driver-lxc no longer available on CentOS 8
* Mark some more images buildable for CentOS 8
Change-Id: Iaf5b68ff6d944ae730ca0b1d5832172c106a6c08
Partially-Implements: blueprint centos-rhel-8
Partially-Implements: blueprint centos-rhel-python-3
|
|
We want RabbitMQ 3.7.10-1 for Ubuntu. So set it in one place which is
designed for such things instead of doing it everytime we want to
install it.
Change-Id: Ib2b2d4e392aaf77bcdec24f9f5551cdf15d32d91
|
|
Disable external repositories by default and enable only when needed.
Depends-on: https://review.opendev.org/696480
Implements: blueprint repos-off-by-default
Change-Id: Icf2a8397a8349e0fe849d88d160409fd234480a9
|
|
Buster is at freeze phase so safe to update and use. Will give us
Python 3 based OpenStack packages (usually release delayed).
Change-Id: I48c2d252a834716f1bcf10b18f2d32fe541e8137
|
|
Ubuntu is also affected by the new rabbitmq server version mismatch
with erlang. Pin it to last known working version until the packaging
mess is fixed.
Change-Id: I5e3ba7762f0990718e4180ffcd3db7722edc17b4
Related-bug: #1814233
|
|
New version of rabbitmq-server in epel but not new enough version of
erlang available in epel or delorean-trunk repos.
Closes-Bug: #1814233
Change-Id: Iac3cad17ff8279a2be66ffe1366d6844f999d66f
|
|
[1] added a new block for rabbitmq plugin installation,
block rabbitmq_install_plugins already exists, it should be
utilized.
[1] https://review.openstack.org/#/c/628150
Change-Id: I900780aa22ba3a3fc19b88bdbb03b2a291ee7167
|
|
|
|
This change updates the docker files to use base_package_type instead
of doing specific distro checks for the rhel/deb generic cases. The
base_distro is still available and is used when a specific distro needs
a customization but if the differences are purely rpm vs deb, then the
base_package_type can be used.
Change-Id: I8d720bb185df65a0178061ccf20b1ab2265da2c5
|
|
Change-Id: I1b2b3d6708bfcd58864e26e6c1fc618fb421e9a2
|