| Age | Commit message (Collapse) | Author | Files | Lines |
|
This is not required anymore since we have switched to Rocky Linux 10.
Change-Id: I10b68c2d3afa91cabf9341df75d8cf9f626c0f9b
Signed-off-by: Pierre Riteau <pierre@stackhpc.com>
(cherry picked from commit 64475a0b1b4dccbc3b817c78453e1d027b3f0d68)
|
|
Change-Id: I37f4515587cb040296612e35d4c643f0c2bea6f6
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.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>
|
|
RDO has staffing problems and has decided to only
support SLURP releases - let's drop reliance on that
repository.
Change-Id: I56f86a1c5262e3ee2bcbb52cae53c3b2655ed87f
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
Known missing packages:
- mod_auth_mellon - missing SAML support in Keystone/Horizon - built in Kolla COPR
- glusterfs-fuse in manila-share - built in Kolla COPR
- collectd/telegraf - no opstools repository
- redis - needs a switch to valkey
- python3-ethtool - not required for neutron-mlnx-agent since 6 years [1]
Building packages in Kolla COPR is a temporary solution until these show up
in EPEL10.
[1]: Id2cae3ac9ff049e9fc8225551f99e1e99a87fc65
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/951751
Change-Id: I7074fabcf95184fcfd2561648ae1e05acfb0bc11
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
Change-Id: I4f852176918531ea19210961fd1b4fa63bc0ecca
|
|
Change-Id: I1f9bc50b71f55dd5f579d1536a7ab63d5d554d1e
|
|
|
|
Change-Id: If15ba52acfd305aa9bbae382fe7429c11041e93f
|
|
|
|
|
|
Change-Id: I05a96f27b47a0f87bcf435872dd08ec0927232e3
|
|
Change-Id: I0bdef4252d4f2850d2b1a40feac3c373e5c453e7
|
|
Users can override the upper-constraints.txt by setting the source of
openstack-base in kolla-build.conf.
However, bifrost-base Dockerfile so far doesn't pass overridden
upper-constraints file to Bifrost install playbook resulting the
playbook not acknowledging it and just use upstream one.
This change sets the source of Bifrost upper-constraints to use
upper-constraints of openstack-base for consistency among all Kolla
images
With this, change the environment variable UPPER_CONSTRAINTS_FILE is
only affecting kolla-toolbox image.
Therefore, moved UPPER_CONSTRATINS_FILE variable example to the
``kolla_toolbox_pip_conf`` block of kolla-toolbox Dockerfile.
Additionally, updated 'Python packages build options' section of
documentation to represent latest method of changing Python package
related options (including this change).
Change-Id: I0a9c782ca1177ef84e4323cb1e5bfac0fb3f383c
|
|
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 commit removes the hardcoded KOLLA_DISTRO_PYTHON_VERSION
and replaces it with dynamic Python version detection during
container images build. Dockerfiles and scripts now use general
python3 references, simplifying maintenance and ensuring
compatibility with future Python versions.
Test cases relying on distro_python_version were also cleaned up.
Change-Id: I891749598247a5e951ed4a873b16acfd0566f59c
|
|
And also python3.11 to python3.12 on rpm distro side
Change-Id: I000e2f2aacb011618a0b3c7b41fe286b3680614f
|
|
If the latest and targeted rabbitmq-server dependencies mismatch,
kolla-toolbox will fail to build.
Closes-Bug: #2066171
Change-Id: I64e9442545d98364585e3c632ae9142cd6b4f9bf
|
|
ansible-core 2.16 requires py3.10+ on the host running
ansible-playbook - let's use Python 3.11 on RPM distros
to have the same version of ansible-core used on all
distributions.
Change-Id: I2caf2c972cd0283889fadde01bdd6a53e5f66ed9
|
|
|
|
2.15 patch was 2023.2 only - because we missed it last cycle [1]
ansible-core 2.16 requires python3.10 which is not the default
python in Rocky Linux 9 - therefore we use 2.15 there for now
[1]: https://review.opendev.org/c/openstack/kolla/+/910148
Change-Id: Ic8cc29230d82f4d1f07a3c97c3dcbcd14ac76074
|
|
Fix existing spell checking
Change-Id: Ief7b8f2d427b2557c84fda9b3774ed85ceb105f4
|
|
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 if it somehow fails for 5 times - we get exit code 0.
Closes-Bug: #2052293
Change-Id: I2bdeb77e3133123053b05adcbde3a426c60f3304
|
|
|
|
|
|
Closes-Bug: #2031692
Change-Id: I8b69869cca98d83d3b1be3f4add88ff83b22b4a1
|
|
Erlang has been bumped to 26 as well.
Change-Id: I5a6e90790d9c3c148e118fdf2ce6089e0a6a343e
|
|
* Use structure that allow for custom package version and base URL.
Change-Id: I169e51c0f5c691518ada1837990b5bdd2a3d1481
Closes-bug: #2020761
|
|
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
|
|
|
|
Change-Id: Id20394d06747b7f56e8745f129149c3f1c492ca7
|
|
This reverts commit d965b1b3da9b8c2780a91781834a46f5886bd9c2.
Reason for revert: Not required in master?
Change-Id: I03b8ed63687ed854a50d521043b04deaf76f7067
|
|
ansible.posix 1.5.4 has been released and it broke the way
we use JSON callback plugin (it requires play.path) - see [1] and [2].
[1]: https://github.com/ansible-collections/ansible.posix/commit/3bbf2e3cd56775096fc8ce69e281142472b73cac
[2]: https://github.com/ansible-collections/ansible.posix/issues/461
Change-Id: I2f879e59a64b9039a8a27c40bd462fde4df73f43
|
|
upper_constraints_remove() macro allows to remove line
upper_constraints_version_change() allows to change versions
This way we have cleaner way to alter u-c in those images which need it.
Change-Id: I8fc354b8aa4d03fcd3ecfb9cbfe75de67492a0e3
|
|
Debian 'bookworm' does not like when someone installs Python packages
into system directories. So instead of installing 'virtualenv' from pip
we move to use 'python3 -m venv' which we install from distribution
repositories (on Debian/Ubuntu as EL9 has it in base 'python3').
Change-Id: I7092b561d81c362ca24f84a3d753e777e5625ab3
|
|
Change-Id: I6e66aea5dc0af61fbc074b4c8ed3910435c98dbd
|
|
Change-Id: I6564886f68a997b82b49b6f975283a6d95831ce6
|
|
|
|
Change-Id: I4836806c0434caaff1e6fd1646aa5566b0c3d7e1
|
|
Change-Id: I17045980b6f73a0395b1bdfd3b1b6b63679284c9
|
|
We switched repo to provide Erlang 25 but not switched to it.
Change-Id: I8b0a2f27ccb3db61a38d8fe89676f99eed1e3d75
|
|
Swift deployment is broken since CVE-2022-38060 fixed sudoers file in
the I66476a2b396e2cbe41e68ac51f57aae1806b2ed8. The kolla-toolbox
container have their own virtualenv path differs from all other
containers. This change adds the correct sudoers secure_path
configuration needed only for kolla-toolbox conainer.
Related-Bug: #1985784
Change-Id: I3651576ee354364d639c187ff750491667ecab56
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
|
|
Change-Id: I13e3cf5a02dadcedd1ebbd54d56f7f633e6e3d68
|
|
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
|
|
Cap openstacksdk in kolla-toolbox to avoid ansible-openstack-collection
from failing.
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/844905
Change-Id: I4d7dcc413cd9ab0b9db550e1aed7d2229b04c5d1
|
|
As we have one type of images now some RUN calls could be merged so we
will have less layers in resulting images.
Change-Id: I5178c58fbd8c65efe825dc249c0f1368ef0fe8e0
|
|
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
|