aboutsummaryrefslogtreecommitdiff
path: root/docker/horizon
AgeCommit message (Collapse)AuthorFilesLines
2026-07-06Migrate to pyproject.tomlMichal Nasiadka2-322/+0
[tool.setuptools.data-files] does not support recursive directory installation. The old setup.cfg [files] worked because PBR's FilesConfig.expand_globs() used os.walk() to expand docker/*, but this hook is not triggered by the pbr.build PEP-517 backend. Move docker/ into kolla/ and use [tool.setuptools.package-data] instead. Update kolla_worker._get_images_dir() to check the kolla package directory first so both editable and regular installs work. Change-Id: I4fc452c03740ef22ebbb4e8d0d86c4f4783e2d09 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2026-06-29Merge "kolla-build: fix build-date LABEL invalidating Docker layer cache"Zuul1-1/+1
2026-06-24kolla-build: fix build-date LABEL invalidating Docker layer cacheMichal Nasiadka1-1/+1
The build-date label was rendered into a LABEL instruction on line 3 of every Dockerfile template, immediately after FROM. Because Docker invalidates the cache for a changed instruction and all subsequent layers, a date change caused a full rebuild of every image on each new calendar day, even when nothing else had changed. Fix this by removing build-date from the Dockerfile templates and applying it as a --label argument at build time via image.labels. Labels passed on the build command line are not part of the Dockerfile cache key, so the date is still recorded in the image metadata without affecting layer caching. Change-Id: I8ef0d85bab1a999a4d09f7cbf0c088ca00fdcf77 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2026-06-19Merge "Revert "horizon: pin setuptools <82""Zuul1-5/+1
2026-06-19Revert "horizon: pin setuptools <82"Michal Nasiadka1-5/+1
This reverts commit 4cdf881631eb0a671b9f70d5afefa6ead1949118. Reason for revert: It's fixed in Horizon Change-Id: If7e6ad7114c69de2435732a45f7a86a7b9bfeca1 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2026-05-08horizon: rebuild static assets after theme changesGrzegorz Koper1-1/+2
Include the theme directory in settings_bundle so theme-only changes invalidate the cache and rebuild the static assets. Closes-Bug: #2148389 Change-Id: If4fbc24c5c339f7dee7bf67a09fc6448ede0c9fd Signed-off-by: Grzegorz Koper <grzegorzk@stackhpc.com>
2026-05-06Drop apache installation outside of httpd container22.0.0.0rc1Michal Nasiadka1-4/+0
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/986483 Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/986352 Change-Id: Ia66dde09bbbad2a5a9e67a8c642f3223ca38be43 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2026-04-28Remove httpd_setup calls from api containersMichal Nasiadka1-2/+0
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>
2026-04-24Drop zun and kuryrMichal Nasiadka1-9/+0
Zun is broken in 2026.1, it has been released broken and there are no reviews on the patch to fix it [1]. [1]: https://review.opendev.org/c/openstack/zun/+/982362 Change-Id: I770b9e62c66f8cc63475d51f80eecacc8415b91f Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2026-03-16horizon: add django-redis dependencyPiotr Milewski1-1/+2
Add django-redis to the Horizon image to support Redis/Valkey as Django cache and session backend. Closes-Bug: #2093414 Change-Id: Ib327dfb770aea5d953baba2399f97cf3ea12defd Signed-off-by: Piotr Milewski <vurmil@gmail.com>
2026-02-09horizon: pin setuptools <82Bartosz Bezak1-2/+5
setuptools 82 removed pkg_resources [1] [1] https://setuptools.pypa.io/en/stable/history.html#v82-0-0 Related-Bug: #2141293 Change-Id: Iced7662f7e58b9f094306e9a6c4f1b5a79f48b17 Signed-off-by: Bartosz Bezak <bartosz@stackhpc.com>
2025-10-27horizon: unpin pip and setuptoolsMichal Nasiadka1-1/+0
Since Venus is removed - that is not needed anymore Change-Id: I444304139dfbe451b5449a181de1129f073b7535 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2025-10-27Drop Venus imagesMichal Nasiadka1-9/+0
It has been marked as inactive and venus dashboard plugin is breaking Horizon Kolla builds. Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/964860 Change-Id: I3a04487a75c04ba989fa70f2025db33308671dfb Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2025-10-27horizon: pin pip to <25.3Michal Nasiadka1-1/+1
Closes-Bug: #2129916 Change-Id: Ib1b40a65cb2667b53c72f00d16bfe280bcf24bfe Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2025-09-18horizon: Ensure horizon owns /var/log/kolla/horizonMichal Nasiadka1-0/+4
Needed-By: https://review.opendev.org/c/openstack/kolla-ansible/+/961614 Change-Id: I9011f9a6d065b85ff76852950e4537070a12b437 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2024-12-11Remove setuptools pinMichal Nasiadka1-0/+2
Change-Id: I7d08ebb65e2de82e3edba7bd9307b2b6ac8cb7a8
2024-11-15Add mechanism for patching files in containersMichal Arbet1-0/+2
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
2024-09-19Switch to Dynamic Python Version DetectionMichal Arbet2-2/+2
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
2024-04-24Drop VitrageMichal Nasiadka1-9/+0
It has been deprecated in Antelope cycle. Change-Id: Ie9cc529d186b74ea3d07b0082f9c965d4aa054e9
2024-04-24horizon/neutron: Add FWaaS pluginhowardlee1-0/+9
Change-Id: Id64c04ef38bd3084dec05bf58ec10b93344f68ec
2024-04-16Drop FreezerMichal Nasiadka1-9/+0
It's inactive and hasn't produced a 2024.1 release [1]. There are some efforts to restore Freezer, but let's remove it for now. [1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects Change-Id: If2d034789d8c1128597c9072b4e82d14f72492e0
2024-04-16Drop SolumMichal Nasiadka1-8/+0
It's inactive and hasn't produced a 2024.1 release [1]. [1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects Change-Id: I387e5c345cd5ea45e9231b9ce5baf58a8d74caf9
2024-04-15Drop SaharaMichal Nasiadka1-9/+0
It's inactive and hasn't produced a 2024.1 release [1]. [1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects Change-Id: I7b5b032a4175c5390c9b7ff3fbd4c672adcb5325
2024-04-15Drop SenlinMichal Nasiadka1-13/+0
It's inactive and hasn't produced a 2024.1 release [1]. [1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects Change-Id: Iad4d850ba8f8b8446591cab883d2ad6243576926
2024-04-15Drop MuranoMichal Nasiadka1-16/+0
It's inactive and hasn't produced a 2024.1 release [1]. In addition to that, there's a CVE that hasn't really been patched [2]. [1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects [2]: https://lists.openstack.org/archives/list/openstack-announce@lists.openstack.org/thread/4FYM6GSIM5WZSJQIG4TT5Q3UBKQIHLWX/ Change-Id: Ie715eac24247c38b21382c735eb00a9b3b56f145
2024-02-05Rework horizon image to support local_settings.dMichal Arbet1-1/+11
The local_settings.py config is rendered by kolla-ansible orchestration, which is not a good approach because upstream local_settings.py can be changed anytime and that can be a problem, as it was shown recently with the new version of horizon. Fortunately, horizon supports local_settings overrides in local_settings.d directory and moreover it's preffered way how to configure horizon as per doc [1]. This patch just change the structure of files to support it. [1] https://docs.openstack.org/horizon/latest/configuration/settings.html Change-Id: Ib0c060adffe5287d786ba9247c6b962732cdb5e0
2023-08-22Add venus-dashboard into horizon image.howardlee1-0/+9
Change-Id: Idbb16f373260735e9650be57042952258a2ee3f9
2023-04-21docker: implement macros to alter upper-constraints.txtMarcin Juszkiewicz1-1/+1
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
2022-12-06Remove monasca, kafka, storm and zookeeper.Michal Nasiadka1-10/+0
Monasca, kafka, storm and zookeeper have been removed in kolla-ansible [1],[2]. [1]: https://review.opendev.org/c/openstack/kolla-ansible/+/861392 [2]: https://review.opendev.org/c/openstack/kolla-ansible/+/865029 Change-Id: I0958a9353bc4585c4f65a1d316328a0e80b0b8b7
2022-10-10Fix writable rootwrap/privsep configRadosław Piliszek1-1/+0
Fixes a hypothetical security issue related to privilege escalation via rootwrap/privsep. A potential vulnerable service could previously allow writes to its rootwrap/privsep config and thus allow for more commands to be run with root privileges via rootwrap/privsep. For a succesful attack, this would also require the service to allow to run arbitrary commands via rootwrap/privsep. Thus far, no such vulnerabilities have been reported and thus this fix is simply strengthening the container images against such an issue in the future. Change-Id: I92c81c77e6a16570a108cde8031f7977930fb02a Closes-Bug: #1874298
2022-09-27Move to CentOS Stream 9Marcin Juszkiewicz1-1/+0
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
2022-04-21flatten images a bitMarcin Juszkiewicz1-4/+4
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
2022-04-11Adjust permissions on _extend_start files.Tim Shearer1-1/+1
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
2022-04-11horizon: binary images are goneMarcin Juszkiewicz1-5/+1
We no longer need to check for them so one MANAGE_PY is enough. Change-Id: Iee2f3bb1c0444f414cad2617dea225192ab8dc81
2022-04-09docker: drop binary partsMarcin Juszkiewicz2-127/+13
Big patch drops all mentions of binary images support. Suggestions are welcome how to split it into parts or handle better. Change-Id: I5d5a46c6ce7734ceb8b844e17b43e359d7cac6e3
2021-11-23horizon: add various dashboard plugins for ubuntu/binaryMark Goddard1-9/+10
These were added for Debian/binary, but not Ubuntu/binary. Change-Id: I74bfa6326d8a72f9bba409e6a725fdb55b48c6b1 Closes-Bug: #1931075
2021-08-07[horizon] Copy Masakari policy in YAML formatRadosław Piliszek1-2/+2
Since commit 39f03063c0b0b22e608bbc606423e51be632be2a in masakari-dashboard (also in Depends-On), Masakari dashboard uses and distributes only the policy in YAML format. Depends-On: https://review.opendev.org/c/openstack/masakari-dashboard/+/798842 Change-Id: Id1aad2c8894331b9540bfc66177368536667f003
2021-07-29Merge "Add missing default policy files for debian-binary-horizon"Zuul1-1/+1
2021-07-03Add masakari-dashboard to debian binary horizon imageMichal Arbet1-0/+1
This patch is adding python3-masakari-dashboard to debian binary image as we added masakari-dashboard to debian in wallaby cycle. Change-Id: Ie3f357eaae5d1378ada32451dbd74f01f5cd2ba2
2021-07-01Add missing default policy files for debian-binary-horizonMichal Arbet1-1/+1
The debian-binary-horizon image is missing the default policies files which should be in /etc/openstack-dashboard/default_policies. By copying everything from /etc/openstack-dashboard/policy into /etc/openstack-dashboard, we get the default policy files, as well as commented out policy files (e.g. cinder_policy.yaml) and the nova_policy.d directory containing api-extensions.yaml. Change was merged for ubuntu in [1] but unfortunatelly not for debian, this trivial patch fixes it also for debian. [1] https://review.opendev.org/c/openstack/kolla/+/794589 Closes-Bug: #1933759 Change-Id: I822d640a251e6ed9f71c76a922513e23e4218418
2021-06-17Merge "Horizon: Install required policy files for heat-dashboard"Zuul1-2/+5
2021-06-17Merge "Horizon: Install policy files for manila-ui"Zuul1-0/+7
2021-06-11horizon: Correct location of monitoring_policy fileScott Shambarger1-1/+1
Patch to correctly copy monitoring_policy.json into /etc/openstack-dashboard. Policy was misplaced, and not being enforced. Note that by current default policy, admin doesn't not have Monitoring access. Closes-Bug: #1928408 Change-Id: I4faabdfa9c273fc61b536e6ce88b8d71ab2fc581
2021-06-07Horizon: Install policy files for manila-uiTakashi Kajinami1-0/+7
Since the commit 89a90ff9773b93062760df5e3deefb9750112633 was merged, manila-ui provides two policy files. This change ensures that these files are installed when manila-ui is enabled. Change-Id: Id92145ba74237da2fd8430b9d84413465297d3a7
2021-06-05Horizon: Install required policy files for heat-dashboardTakashi Kajinami1-2/+5
Since the commit 8e7914fce24d2c9d94a83795983aaa0fb05f020c was merged, heat-dashboard no longer use policy.json but it use two yaml files to manage policy rules. This change updates managed files for heat-dashboard accordingly. Change-Id: I0cae18c1d5169cd444a14ba3b56de24dede5919c
2021-06-03Add missing default policy files for ubuntu-binary-horizonPierre Riteau1-1/+1
The ubuntu-binary-horizon image is missing the default policies files which should be in /etc/openstack-dashboard/default_policies. By copying everything from /usr/share/openstack-dashboard/openstack_dashboard/conf into /etc/openstack-dashboard, we get the default policy files, as well as commented out policy files (e.g. cinder_policy.yaml) and the nova_policy.d directory containing api-extensions.yaml. Change-Id: I3c6fdcb9b7dd7443a7755599f7e4ee59f67e0a91 Closes-Bug: #1930586
2021-03-22centos: enable PowerTools repo in images which needs itMarcin Juszkiewicz1-0/+1
We moved to CentOS Stream 8. Just no one noticed that binary target was failing to build. This change sorts out all failing images. Change-Id: Ia7768caabfe214a629339d50973d0d9873fc65d5
2021-01-25Remove zaqar image and related pluginsChristian Berendt2-10/+0
Signed-off-by: Christian Berendt <berendt@betacloud-solutions.de> Change-Id: Id3187b2b95e9b9bd3d9233a498f7c45e66c604c7
2021-01-25Horizon: gentler `-o nounset` handlingRadosław Piliszek1-36/+31
When running with `-o nounset` since [1], the Horizon became quite fragile to run as it started requiring all ENABLE_* environment variables to be set upfront. Normally they are - via kolla-ansible. However, when working with it outside of kolla-ansible or removing services (like it was the case 3 times during the Wallaby cycle), it creates needless issues (like having to wait for images to get published for kolla-ansible gate or users bumping into irrelevant incompatibilities [2]). This patch makes sure all ENABLE_* environment variables default to 'no' and are no longer required to be set when there is no need to set them to 'yes'. [1] 032804e5a0ddf89f7726880d1b57dd492d7d5c07 [2] https://bugs.launchpad.net/kolla/+bug/1911141 Change-Id: I644e072a699dccd8f32a24e484ff6dab7b9b449d
2021-01-16Merge "horizon: set FORCE_GENERATE to no if not set"Zuul1-1/+1
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-05 20:19:40 +0000