| Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I793e35ef347c9d44b4e870cd3ca1bd459e557623
|
|
|
|
|
|
|
|
|
|
Tim Shearer started it in 1d96a2bbe1b536b7d7f4cdbf55c6dabae6d058ae.
Since all extend_start files are sourced rather than executed, the executable
bits are now cleared throughout the project.
Change-Id: Ia1797c32fc6a35f9f077c673abf4d8e16e51a760
|
|
|
|
|
|
|
|
There is proposed change in kolla-ansible below
which is changing the way how central-logging
works and adding native fluent logging.
Because of this, it's needed to add python
fluent library to openstack images.
Proposed Change:
- https://review.opendev.org/#/c/755775/
Change-Id: Iedc782a3317c93a2af0da4696fd71c05e0e4a55e
|
|
Bug mentioned in Dockerfile was fixed about 4 years ago.
Change-Id: I6d90e6673b01756e7de7c8eeb29423cee0cce6f7
|
|
Kolla supports only AArch64 and x86-64 so there is no need to check for
other architectures.
Change-Id: I44e45492bcbdd56a5c985ba84bad66202c9fde55
|
|
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
|
|
These were not available at the time we switched everything else. Venus
remains unavailable.
Change-Id: Ic9e54568a2844991b12e04ebfb1444b5cf286dbb
|
|
We can drop temporary 'use-short-names' argument and make short
(kolla/debian-nova-libvirt:master) image names default.
Kolla Ansible is using short names now.
Change-Id: I153355353cd12aa25adaa9c87438a478748dfb28
|
|
This patch is changing the way how keepalived
checks daemons liveness.
Check_alive.sh will find checks for daemons
which are copied by kolla-ansible and return 0/1
if alive/down.
This patch is required for proxysql HA.
Needed-By: https://review.opendev.org/c/openstack/kolla-ansible/+/770215
Change-Id: I68836918466beb572e42ffedce127747290ad481
|
|
--use-short-names argument drops 'install_type' from image names:
kolla/debian-openstack-base:14.1.0
This should allow to get rid of '-source' in image names without
disrupting CI jobs.
Switch publish jobs to use short names so k-a tests will have ready to
use images for both long and short names.
Change-Id: I29c9d51f4b518a4e2d3157ab5d6cc434fb83f2ef
|
|
We have 'quiet' mode where only minimal data is printed to the console.
But there were no logs at all then.
This change generates log files (if 'logs-dir' argument is used) during
quiet build.
Also enables 'quiet' mode for CI so Zuul will not have to parse 29MB
JSON file each time.
Change-Id: If7d5c2807f0947a8bbbc1ceb8531c9b9c9287c1f
|
|
This reverts commit 09c890b12463a4b2c8767231189e7016f337fbc3.
Reason for revert: That change caused all Kolla's work items to be
transferred. This includes tarballs, their extracted contents, cloned
git repositories, etc. to also be transferred to swift which takes
extra time, pollutes logs and decreases the stability of jobs slightly
(the mechanism is not designed for this kind of load).
The collection of templated Dockerfiles in CI has to be reimplemented
if it is wanted.
Change-Id: Ideaf66ce18c993802f4d20f490caa47cec0dde5e
|
|
The only place where it stays is argument parsing where it gets ignored.
Hardcoded to 'source' to make merging both kolla and kolla-ansible
changes easier.
Change-Id: I6890a7ec7baf507f8acd75b42bbd0fb17c2e4511
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/837620
|
|
A recent change to git [1] introduced a new behaviour to work around a
CVE [2] that disallows any git operations in directories not owned by
the current user.
This may seem unrelated to installation, but it plays havoc with PBR,
which calls out to git to get to get revision history. So if you are
"pip install"-ing from a source tree you don't own, the PBR git calls
in that tree now fail and the install blows up.
When using type=source, kolla clones the repository, then creates a
tarball from it, which is ADDed to the image. The ownership of the files
in the tarball is preserved, which in this case will be the user running
kolla-build. Since the Docker build runs as root, we hit the PBR issue.
Our solution is to make sure that any tarball we generate from git
sources have all files owned by root:root so that the root user is able
to use git commands when building container images.
[1] https://github.com/git/git/commit/8959555cee7ec045958f9b6dd62e541affb7e7d9
[2] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24765.
Closes-Bug: #1969096
Related-Bug: #1968877
Co-Authored-By: Mark Goddard <mark@stackhpc.com>
Change-Id: I2cbf1f539880d512aa223c3ef3a4b19ee18854ac
|
|
|
|
|
|
|
|
|
|
|
|
Change-Id: If524e45dc262efb253fc06329d4567412282926d
|
|
It is not used in k-a and has never been.
Change-Id: I600cc276ba67d88928e6c2c87810459435b92650
|
|
hacluster-pcs is already in centos, no need to be in
centos+aarch64.
TrivialFix
Change-Id: I9868f73172efedf113c3cc1567098b3439e2a205
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
*-source-upgrade kept old names as we need to add *-binary-upgrade ones
to check previous_release-binary/* -> current_release/* upgrade path
k-a jobs will go in separate patch
Change-Id: Ieba3260ffa11fa2d3982f379f95abed9f840028d
|
|
If they are unbuildable then they should be in distro or distro+arch
blocks now.
Change-Id: I9cd225d3a7fd99fdeaf4926730c95d37f8f7eac7
|
|
There is only source.
Change-Id: I0d32808c73ab3292a8f213424118dfe2313d465b
|
|
Change-Id: I33eecfa49086b01a116aa0616fd1b6815ff8894e
|
|
When everything fails assume we have Python 3.8 (should never happen).
Change-Id: I69033cc910dd8236a470fd130816f2870a9b5b3a
|
|
With binary install type dropped there is no need for this macro.
Change-Id: I7bdd29eb48a23faa04a98e785129d97258f05e64
|
|
It was marked deprecated in Yoga.
Change-Id: Iea1cf9c539a73da625e335d6c1adb6cd71ec93d4
|
|
We no longer need to check for them so one MANAGE_PY is enough.
Change-Id: Iee2f3bb1c0444f414cad2617dea225192ab8dc81
|
|
|
|
|
|
|
|
We have one install_type only now so that infra stuff is not needed
anymore.
Change-Id: I60d50ba7699d46d001eaef365fb84b0ce8e9b262
|
|
Big patch drops all mentions of binary images support. Suggestions are
welcome how to split it into parts or handle better.
Change-Id: I5d5a46c6ce7734ceb8b844e17b43e359d7cac6e3
|
|
|
|
With one type of install type there is no need for renaming infra
images.
Change-Id: I28b7563e5ce1efac0298a62fee96a9f946f3341b
|