| Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I954106dc32b4c08604d5c40e00fe53e5bb18b266
|
|
Change-Id: I6c15cf0fd7b8f1cc3339936c58ad8a8581cfc570
|
|
|
|
(Dalmatian)""
|
|
Python3-pip installs the dependent package tzdata
and blocks the mount of the /etc/localtime file in docker.
After deleting the symbolic link docker correctly mounts
the external localtime file.
Applies only to ubuntu 24.04, in previous versions
of ubuntu there was no such problem
Closes-Bug: #2091161
Change-Id: I733a50b5ca455cfa4b248dc324500d78c17c817b
|
|
So far, the certificates were not part of config.json
files for containers. With future patches that will remove
container restarts based on triggers from config and
service-copy-cert, it is important that all files that change
during config are specified in config.json so that
kolla-set-configs --check can detect those changes and based
on that restart the container. This patch provides prerequisite
for future patch in kolla-ansible.
Comments from kevko:
The script also takes into account whether review [1] is
merged or not, ensuring that it will function correctly in
both cases thanks to review [2], because using the state
file, we can effectively verify whether the config.json that
copies CA certs to /var/lib/kolla/share is being used or not.
If we didn’t handle it this way, we would have to rely on
checking whether the directory /var/lib/kolla/share exists or
some another magic, which is insufficient because various
states and combinations of Kolla image and Kolla-Ansible
versions could result in certificates always being copied.
This method provides a clear and definitive distinction.
[1] https://review.opendev.org/c/openstack/kolla-ansible/+/924651
[2] https://review.opendev.org/c/openstack/kolla/+/915440
Change-Id: I5120f1874f25a9ca8326e6db8b12dee4c81feb56
Signed-off-by: Roman Krček <roman.krcek@tietoevry.com>
Co-Authored-By: Michal Arbet <michal.arbet@ultimum.io>
Needed-By: https://review.opendev.org/c/openstack/kolla-ansible/+/924651
|
|
This reverts commit db0f87d3c8e1e7eccdeb1ea46216d530711680d3.
Reason for revert: Epoxy cycle is on
Change-Id: Ie2a747223b33039684650bede8863af0c8906d2f
|
|
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 restructures the handling of configuration
files in set_configs.py, introducing functions for managing
default configuration files first.
Closes-Bug: #2060855
Change-Id: If91e0330dc149143c82d2183b8ddf6fa9f68d80e
|
|
Added timestamp with milliseconds, log level, and custom
date format to improve clarity and make logs more useful
for debugging.
Change-Id: Ice2d601eddb54bbb0e7e3be6f03ba6db58256c1f
|
|
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/933312
Change-Id: I0ce9e907594fd160a08ad7929d5bc4bca9abf536
|
|
|
|
it should be the same as in repos.yaml
Change-Id: Ieb413f7a4bd1989d7f29309368b6b218d1395e0b
|
|
|
|
Change-Id: I219418411470bdeae9af84277f5150a623c05e69
|
|
This patch bump proxysql 2.6.x to 2.7.x
Change-Id: I6e726d8ebf9dbc6d019dd72d6d0be9d9957a3f22
|
|
Add setuptools because Python3.12 dropped distutils
Needed-By: https://review.opendev.org/c/openstack/kolla-ansible/+/925581
Change-Id: Ie12c43dc1de122c203edc28181366457ccd67834
|
|
This package provides a standalone sysusers binary with
minimal dependencies, designed for use in non-systemd
environments.
This package simply ensures that all packages that want
to install systemd as dependency will have to settle for
this one because the systemd package breaks
systemd-standalone-sysusers, as it is an alternative.
[1] https://packages.debian.org/bookworm/systemd-standalone-sysusers
[2] https://packages.ubuntu.com/noble/systemd-standalone-sysusers
Change-Id: I3ba85069c265844bd2f8b5e6d2b14f32e4898cfd
|
|
Since packages are installed using root during image build - we
need to use sudo when updating those packages when using dev-mode.
Change-Id: Idf14e334d50abeb1719563b1733af0b8425b3b55
|
|
|
|
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
|
|
Kolla checks the status of its configurations
using kolla_set_configs --check. However, this
doesn't work for the command block in the config.json
file. This means that if only the command value changes,
but not the config_files block, which is common practice
in Kolla-Ansible btw, the container will not report the
changes.
This is undesirable and important to fix, especially
considering the planned rework of notifiers in
Kolla-Ansible [1].
[1] https://review.opendev.org/c/openstack/kolla-ansible/+/773243/14
Closes-Bug: #2080861
Change-Id: I2a290da38ea34b05ce3da8fb8b39b6252bf2da47
|
|
PackageCloud is discontinued as of August 18th [1].
Also corrects the versions docs for RabbitMQ and Erlang.
Use new RMQ Cloudsmith repo URLs, these now use
*.rabbitmq.com domains [2].
1. https://www.rabbitmq.com/blog/2024/08/11/package-repository-updates#packagecloud-will-be-discontinued-on-aug-18th-2024
2. https://www.rabbitmq.com/blog/2024/08/11/package-repository-updates#mirrors-now-use-rabbitmqcom-domains
Change-Id: I2cce3dd2540c878878ff0aae80ee5a7e0f455da7
|
|
Provides mechanism for future work to fix bug where when package file
manifest changes, the changes were not reflected in to devmode-enabled
container.
It changes the strategy of installing projects in dev mode in containers.
Instead of bind mounting the project's git repository to the venv
of the container, the repository is bind mounted to
/dev-mode/<project_name> from which the it is installed using pip
on every startup of the container using kolla_install_projects script.
Related-bug: #1814515
Change-Id: Ia1bdff87cba73587a03124ab78a56b21c6176373
Signed-off-by: Roman Krček <roman.krcek@tietoevry.com>
|
|
|
|
When using recursive mode to set permissions for a directory as
defined in kolla config.json, all the subdirectories and files will
receive the same permissions. This change adds the option to exclude
specific files or directories - either a name or a regular expression
can be used.
Closes-Bug: #1931294
Closes-Bug: #1972168
Co-Authored-By: Jakub Darmach <jakub@stackhpc.com>
Change-Id: If2f39736e2af34cd91d0976051ff66f06e96ab42
|
|
Closes-Bug: #2076453
Change-Id: I6af9baf09a19a7dbcaf98585870aa44ff79398d3
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
|
|
Change-Id: Id1c028e0650c1fd3aa4c0a7b311a61b26057179c
|
|
Change-Id: I9eb51e079fee1322bcaaf9d481cd7890aeb77696
|
|
This reverts commit 19a004e0a500ea4839fa1e089e1c50c953cec3b3.
Reason for revert: Fixed
Change-Id: I5491adef46fe0cec013a597cb05018d8d7e862f0
|
|
pin opensearch and opensearch-dashboards to 2.12. for now
Closes-Bug: #2060668
Related-Bug: #2060306
Change-Id: I3df4823d78474d94e138ff73f0f577bd247bdad0
Signed-off-by: Sven Kieske <kieske@osism.tech>
|
|
|
|
Change-Id: Ib0e78581e6c34be650e59d8a044fe21b06ab45a9
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
|
|
This patch bump proxysql 2.5.x to 2.6.x
Change-Id: I26e6c04ad0ba15ad4aa90f95259dc41cad439e73
|
|
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
|
|
Change-Id: I736fcfd766a378783dbfe06ab8ac58858e84aba7
|
|
(Bobcat)""
|
|
This reverts commit 2ed66effa6e4a102919cb53a4b0737f852eb8674.
Reason for revert: Let's use RDO trunk
Change-Id: I3945fe5fd0aef2e12a7f6c60d714e69ea496083b
|
|
notice that the td-agent command got renamed to fluentd.
see also the upgrade notes at[0].
for more details, refer to the changelog[1].
[0]: https://web.archive.org/web/20231006084137/https://www.fluentd.org/blog/upgrade-td-agent-v4-to-v5
[1]: https://github.com/fluent/fluent-package-builder/blob/b4b7017c09d78f2c404db62612733b40f69668a6/CHANGELOG.md#release-v500---20230729
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/901509
Change-Id: I5e95363c6c180e330945fe3d98e97c7049bbd6f7
Signed-off-by: Sven Kieske <kieske@osism.tech>
|
|
Since change I1bc19f8198da3f9ab2ae2a8864c3349b21b0249e we install the
centos-release-ceph-reef package as a dependency, but some code was
still expecting the quincy package.
Change-Id: I8ebcf815d80f3bead25e0078d69b34e17ad013bd
|
|
|
|
Change-Id: If0ab5696af19d2865b475d37d96cb0cbc3a619b2
|
|
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/900536
Change-Id: I1bc19f8198da3f9ab2ae2a8864c3349b21b0249e
|
|
|
|
Change-Id: Ife390597433fcededf15ecc09db626983e1b8cfd
|
|
This reverts commit 881e3925c7aa8c3bbe6897ea8790f109dc0a7fb8.
Reason for revert: switch back to master, to be followed by switch to bobcat when available
Change-Id: Ib8fdad41a669fc8404b8de2de5361db9547c4ea2
|
|
Launchpad is not traffic constrained, so let's better use that,
instead of the community mirror.
Change-Id: Ie9e0f574c8e3a61e67736caa3faedb8602a5adde
|
|
CloudSmith is over budget, see [1].
As mentionedin in [2] - we're using amd64 packages on aarch64,
since the community mirror does not mirror aarch64 - and the packages
should be really marked as noarch.
[1]: https://github.com/rabbitmq/rabbitmq-server/discussions/9526
[2]: https://github.com/rabbitmq/rabbitmq-server/discussions/9553
Closes-Bug: #2037469
Change-Id: I83179ce5d53fed6cfe7f5fcbf6fdecd7199baa36
|
|
Change-Id: I1967202e23405ad713fd0d54337754d46566156d
Signed-off-by: Sven Kieske <kieske@osism.tech>
|
|
|