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
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
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
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
With RDO use we did not disabled some repositories. This patch disable
them and enable where needed.
Change-Id: Ia9d537fe9c1ad54789d2bfb4027254fbb3defe7e
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
* 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
This allows us to use the new simpler style conf format, as well as drop
the dependency on the deprecated clusterer plugin.
Depends-On: I921459f3e40b9e0d4af9497384e49aabf0abe79b
Change-Id: I75e00312b36e1678b90a42cf58d24652323eff27
Obtain binaries from encrypted source when we're unable to check for
their signatures. This should provide better security than downloading
the files over HTTP but does not replace signature verification or file
integrity check.
Related-Bug: #1791674
Change-Id: I7d6eed9ab14ceb130ea4f5f03d893ddaaa0a7acd
Debian 'stretch' has rabbitmq-server 3.6.10 in backports repository so
we will use it instead of external version.
Also take care of 'erlang-base-hipe' (or rather lack of it) on AArch64
architecture.
Depends-on: I72d1d1c10cbc4c5fe0907e395b6d7c969353dff8
Change-Id: Id332215b1e05e6edf18efd85c4463993bb7b321f
set_configs.py has logic to handle chown of directories. Simplify
the codebase by removing these unnessary chowns. Further the chowns
cause some forms of NFS backed storage to not work properly.
Change-Id: I8df95d06b1010778deb3e2a3065aaab26ed2eb6a
Closes-Bug: #1693973
centos based images have wrong label info,
these changes fix own image's name and build-date.
Change-Id: I1d13f8f386c8db12b5fbe5f8ecbbf9e3fbb4ba1c
Closes-Bug: #1680341
Use LABEL instruction instead of MAINTAINER (deprecated) instruc-
tion as suggested by Docker's official dockerfile guide.
docs.docker.com/engine/reference/builder/#maintainer-deprecated
Closes-Bug: #1683652
Change-Id: Ie87a1ddf31aefcd0b623fd2837d78de420e76898
Debian support is not maintained in Kolla so it got a bit behind Ubuntu
one. This changeset enables Debian for all images. Jessie (even with
backports) may be too old for some images though.
Also unify distro check to ['debian', 'ubuntu'] to keep alphabetical order
like it is done for RPM distributions.
Partially-Implements: blueprint multiarch-and-arm64-containers
Change-Id: I056233fbfa277e0e2360c07c3f80d9558c554357
Some images have packages sorted alphabetically and some not.
Unify common style between all images.
Change-Id: I906ed89c10b12886665618752f525ba71d83d991