| Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Needed-by: https://review.opendev.org/c/openstack/kolla-ansible/+/945611
Change-Id: I4113976db743d3c5c4ff62f2876e224888f05a36
|
|
* prometheus-alertmanager: 0.28.0 -> 0.28.1
Change-Id: Iec5b936ae77f2d8298803fbfe50f55b2ed69f4b3
|
|
|
|
Change-Id: If15ba52acfd305aa9bbae382fe7429c11041e93f
|
|
Copy aarch64 snponly.efi to /tftpboot during bootstrapping
of Centos- and Rocky-based ironic-pxe.
Don't use $KOLLA_BASE_ARCH when symlinking to
/tftpboot/ipxe.efi, because an aarch64 variant of this
binary doesn't exist, just x86_64.
Change-Id: Ie19fcb441a2e54a60762e5c8483487b713a29ddd
|
|
|
|
Depends-on: https://review.opendev.org/c/openstack/kolla-ansible/+/945498
Change-Id: I0e7ce418508f6684a20539c6b6129a134f91c71c
|
|
|
|
|
|
|
|
Support aarch64 ipxe only when using Ubuntu and Rocky
Linux base images, as the Debian ipxe package does not
provide a suitable aarch64 ipxe binary.
Change-Id: If5610148fc80acf13d4eb79fef78349764f08a17
|
|
It has long been sort of an abomination of the container world,
let's use this deprecation notice as a motivation to work out
a kolla-ansible mechanism utilising regular ironic container
images to deploy standalone ironic.
Change-Id: I6b4e6edc110eebb524396138d24b873cb4ea6726
|
|
|
|
|
|
Change-Id: I0bdef4252d4f2850d2b1a40feac3c373e5c453e7
|
|
|
|
UEFI virtual media boot requires an ESP image [1].
[1] https://docs.openstack.org/ironic/2024.2/admin/drivers/redfish.html#virtual-media-boot
Change-Id: Ie8485a7098743e1d736145e8fd9441cf13c929d7
|
|
Change-Id: I954106dc32b4c08604d5c40e00fe53e5bb18b266
|
|
In certain deployments ironic-conductor needs to create floppy images to
mount in virtual media. This needs the mtools package installed.
Change-Id: I00ccc47f7a993f13e2b2feb3f6a2565dad32b80c
|
|
When kolla is cloning a Git repository during the build
process, the `.git/config` file retains the remote
origin URL, which may expose sensitive credentials if
authentication tokens are embedded in the URL.
This fix ensures that the remote is removed after cloning
to prevent unintended exposure of credentials.
Closes-Bug: #2098904
Change-Id: Iec21fc2363e03133ec77326da7392bc25b40132a
|
|
Commit 79a234239516b94b1b79c7ddafcc4fbe4e3ba155 introduced an ability to
build 'in-house'/'not-built-in' projects with Kolla.
This commits extends this feature with an ability to use configure_user
macro for 'not-built-in' users.
The implementation is done the same way as for 'sources', i.e. engine
after registers new section structure as soon as it finds unknown
'<project>-user' section.
In addition, the documentation and CI are extended to cover
``--docker-dir`` option.
Change-Id: I690d9f3829083f2493bf286a1c45764b9699219b
|
|
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
|
|
prometheus-alertmanager: 0.27.0 -> 0.28.0
prometheus-blackbox-exporter: 0.24.0 -> 0.25.0
prometheus-cadvisor: 0.49.1 -> 0.49.2
prometheus-elasticsearch-exporter: 1.7.0 -> 1.8.0
prometheus-memcached-exporter: 0.14.2 -> 0.15.0
prometheus-mtail: 3.0.0-rc54 -> 3.0.8
prometheus-mysqld-exporter: 0.15.1 -> 0.16.0
prometheus-node-exporter: 1.7.0 -> 1.8.2
prometheus 2.50.1 -> 2.55.1
Co-authored-by: Piotr Parczewski <piotr@stackhpc.com>
Change-Id: I9359df23a41a600dd46dbc1812a54be57fd33f71
|
|
Change-Id: Ie62060b806c3d66653901bf6f2b5ea8941e7a6be
|
|
|
|
|
|
|
|
Change-Id: I979df16dea4499b470ce7a4e23df7927a5952aa7
|
|
Change-Id: Id81ce23fed7c19211aa8b15abce185d990be8389
|
|
(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
|
|
Needed-By: https://review.opendev.org/c/openstack/kolla-ansible/+/935656
Change-Id: I0b20d82a0061062f8aa9dfe179b1d02708ad610e
|
|
This reverts commit db0f87d3c8e1e7eccdeb1ea46216d530711680d3.
Reason for revert: Epoxy cycle is on
Change-Id: Ie2a747223b33039684650bede8863af0c8906d2f
|
|
Change-Id: I581ff79993d011b421d69295a6552cb14b8e2e66
|
|
|
|
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
|
|
|
|
Change-Id: I799d6bf7a381c377dee565c13b1732f7313520f4
|
|
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
|
|
|
|
|
|
Closes-Bug: #2067050
Change-Id: Ife426c073048ff27bdfd9f3af30aaaab8c2e4497
|
|
ProxySQL reports its version to MySQL clients,
causing the backup process to fail when ProxySQL is used.
This patch adds a new script that handles backups from
the replica server directly, without modifying the original
backup script. The new script retrieves the server address
via the load balancer and connects directly to the replica
server to execute the backup.
Moreover, this reduces the risk that the backup will be inconsistent
or that it will block OpenStack MySQL clients, because they are
connected to a different server, and no one is connected to the replica,
or that it will overload the load balancer (such as ProxySQL or HAProxy)
which listens on the VIP.
Closes-Bug: #2080818
Change-Id: Ibf7e40e8b059d733e114963022df06180249c650
|
|
|
|
|
|
Change-Id: I219418411470bdeae9af84277f5150a623c05e69
|
|
Change-Id: Ic7cb4e97deb04a82fd73238adbe5b4b74a6a50a0
|