Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=stable%2F2026.1 2026-04-28T11:22:25+00:00 2026-04-28T11:22:25+00:00 Michal Nasiadka mnasiadka@gmail.com 2026-04-28T07:28:31+00:00 urn:sha1:929df04f10273cbbdae0bd1cc75f24f49963bc83 We have dropped mod_wsgi support from services in [1]. [1]: https://review.opendev.org/c/openstack/kolla-ansible/+/982414 Change-Id: Ie5da8427706dfb74bad4e174c990355a6870114c Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com> 2024-11-15T08:04:30+00:00 Michal Arbet michal.arbet@ultimum.io 2022-02-15T12:50:59+00:00 urn:sha1:11f65c6c1d3bfd6a12f8e71d778d46d635010449 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 2022-04-09T15:44:26+00:00 Marcin Juszkiewicz marcin.juszkiewicz+kolla@linaro.org 2022-04-01T11:41:14+00:00 urn:sha1:1749da2fbf6b395b1a2cd77f349e0bea5d2f4a5e Big patch drops all mentions of binary images support. Suggestions are welcome how to split it into parts or handle better. Change-Id: I5d5a46c6ce7734ceb8b844e17b43e359d7cac6e3 2020-08-10T09:51:07+00:00 James Kirsch generalfuzz@gmail.com 2020-07-30T19:36:39+00:00 urn:sha1:5bdf514645e6ba603f813f299c68ff7fb12daa3c Refactor installing and initial setup of httpd and mod wsgi from individual services to base image. Change-Id: I651a55a9ebe258ef403d33de010a4dfb368a4021 2020-04-15T09:32:06+00:00 Marcin Juszkiewicz marcin.juszkiewicz@linaro.org 2020-03-09T16:44:54+00:00 urn:sha1:53443c5c712f4ec23b859105e94bcd90abc27762 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 2020-03-01T17:25:58+00:00 Christian Berendt berendt@betacloud-solutions.de 2020-02-19T21:39:33+00:00 urn:sha1:861f55fbfd7558d56008e6275b0c6f5993346b95 Change-Id: I9692dda817ef134d647247431565e1b58cf9da41 2019-12-11T11:38:46+00:00 Mark Goddard mark@stackhpc.com 2019-12-10T11:51:51+00:00 urn:sha1:8484190e77e4237247dac7fba128e5a111fc9918 All Apache httpd setup has been moved to a new helper script, kolla_httpd_setup. This includes the existing clean of /run/httpd, /var/run/httpd, /tmp/httpd etc. Horizon has an additional bit of Apache config for Debian/binary, which has been kept in extend_start.sh for horizon. Change-Id: Ia2af74b69c151db0bd7e452460b0babcee50b282 Related: blueprint centos-rhel-8 2019-06-06T10:59:03+00:00 Marcin Juszkiewicz marcin.juszkiewicz@linaro.org 2019-03-08T17:50:14+00:00 urn:sha1:d436001b43f0a7e3c161ac4a2c5d09d36c6f1015 Commit 43b74ccc157c0b50138c3785ed91dab504895571 enabled use of Python 3 based packages but not switched to use Python 3. Some of images still contain Python 2. There are two reasons: - Ceph (ceph-common depends on Py2) - python3-ldappool on Ubuntu 18.04 In Ceph situation Py3 packages were added. For second one we can not do anything - Py2 dependency got dropped in Ubuntu 18.10 version. Removed neutron-server-plugin-networking-infoblox due to being not maintained. Once https://review.opendev.org/#/c/657578/ get merged someone may revert that part. Implements: blueprint debian-ubuntu-python3 Depends-on: Ie2a1077f7def0743f1403341985e2109aa490026 Change-Id: Ibfe0c2b8be98db56c61f74fb0247488ab3749ef4 2019-05-23T13:44:18+00:00 Marcin Juszkiewicz marcin@juszkiewicz.com.pl 2019-05-23T11:55:51+00:00 urn:sha1:fcceb51963110e7280bf090c4194031b42e54123 Ubuntu/source deployment of horizon and placement-api failed: + exec /usr/sbin/apache2 -DFOREGROUND apache2: Syntax error on line 80 of /etc/apache2/apache2.conf: DefaultRuntimeDir must be a valid directory, absolute or relative to ServerRoot Once directory is in place it works fine. Change-Id: Icbd500e5b16deb0eafc0821a1c117794ddb8ae62 2019-04-10T14:14:21+00:00 Mark Goddard mark@stackhpc.com 2019-04-09T16:43:54+00:00 urn:sha1:6c0065185943355851308ae4df23b73918fab7be 1. Install python3-pymysql in placement-base image. 2. Remove default placement WSGI config. 3. Use python3 for manage.py in horizon Change-Id: Ibb620af2241e39fe99bc48757f90296c0d77d438 Partial-Bug: #1823989