| Age | Commit message (Collapse) | Author | Files | Lines |
|
[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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
Needed-By: https://review.opendev.org/c/openstack/kolla-ansible/+/961614
Change-Id: I9011f9a6d065b85ff76852950e4537070a12b437
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
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
|
|
It has been deprecated in Antelope cycle.
Change-Id: Ie9cc529d186b74ea3d07b0082f9c965d4aa054e9
|
|
Change-Id: Id64c04ef38bd3084dec05bf58ec10b93344f68ec
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
Change-Id: Idbb16f373260735e9650be57042952258a2ee3f9
|
|
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
|
|
We no longer need to check for them so one MANAGE_PY is enough.
Change-Id: Iee2f3bb1c0444f414cad2617dea225192ab8dc81
|
|
Big patch drops all mentions of binary images support. Suggestions are
welcome how to split it into parts or handle better.
Change-Id: I5d5a46c6ce7734ceb8b844e17b43e359d7cac6e3
|
|
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
|
|
|
|
|
|
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
|
|
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
|
|
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
|
|
Signed-off-by: Christian Berendt <berendt@betacloud-solutions.de>
Change-Id: Id3187b2b95e9b9bd3d9233a498f7c45e66c604c7
|
|
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
|
|
|
|
As announced on the openstack-discuss ML[1], Karbor is retiring
this cycle (Wallaby).
Needed-By: https://review.opendev.org/c/openstack/karbor/+/767032
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018643.html
Change-Id: I0b8b1782874282636552f3ffe924a8d512d48959
|
|
Searchlight project is retiring in Wallaby cycle[1].
This commit removes the images and support of Searchlight
project before its code is removed.
Needed-By: https://review.opendev.org/c/openstack/searchlight/+/764526
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018637.html
Change-Id: Ibcae8d0af13fd1d242912b8703c1d1253e2a1326
|
|
Qinling project is retiring in Wallaby cycle[1].
This commit removes the usages of Qinling project
before its code is removed.
Needed-By: https://review.opendev.org/c/openstack/qinling/+/764521
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018638.html
Change-Id: I5bb79f08b76830981be95df19f3a33f5fda6893d
|
|
Signed-off-by: Christian Berendt <berendt@betacloud-solutions.de>
Change-Id: I303ee5367aba0ae114e52b7b559faf06133f2304
|
|
Make start.sh run with pipefail and nounset to avoid common errors
in the start scripts and detect them early.
Httpd code had to be patched to allow it to pass on Debuntu.
Also fix the two missed applications of httpd to make sure all
its path are covered.
And also fix Horizon's ENABLE_ZAQAR - K-A does not use Zaqar.
Yet another - Horizon's settings_bundle. :-)
Finally, fix Neutron for Debuntu (KOLLA_LEGACY_IPTABLES).
Change-Id: I39b8d78f6758df1f92b8b0d2c06ea99b038b843b
Depends-On: https://review.opendev.org/711923
|
|
The horizon image copies the masakari dashboard's policy file to Python
site packages, but it should go to /etc/openstack-dashboard. This allows
the dashboard to be seen by non-admins, although it fails to load.
We get an error like the following in horizon.log:
No policy rules for service 'instance-ha' in
/etc/openstack-dashboard/masakari_policy.json
This change fixes the issue.
Change-Id: I8ede183c76a830de06ce6524dc3f6f6944b182c1
Closes-Bug: #1894240
|
|
|
|
more info: https://review.opendev.org/#/c/721733/
Depends-On: I12d74b53b64268d0358220af35f7fd719d82b397
Depends-On: I21c9ab9820f78cf76adf11c5f0591c60f76372a8
Change-Id: I7bd03b4f70ddfb15c96ed68e659cb6dccb0c36a3
Co-Authored-By: jacky06 <zhang.min@99cloud.net>
|
|
FWaaS is being retired upstream [1][2] in V cycle.
[1] https://review.opendev.org/#/c/735838/
Change-Id: I45679c8596844780565644e52034bd3de0915ff4
|
|
'config_monasca_dashboard' method added and called so if
'ENABLE_MONASCA' is set this merhod will add monasca-ui to horizon.
Change-Id: If46d0d629a678f9878f36f1cfbe31153ab5ebf9b
Implements: blueprint monasca-ui
Signed-off-by: Hamed Bahadorzadeh <h.bahadorzadeh@gmail.com>
|
|
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
|
|
Stein/Buster packages are enabling plugins by default at its
installation time, but we actually know what plugins should be enabled
just only at the deploy time.
Therefore we need to install all available plugins and disble them right
at the image build time.
Plugins will be enabled according to deployment (kolla-ansible)
configuration at deploy time.
Change-Id: I9604ebb4f2a5081fd1209b9841aa997a70a90a11
|
|
Masakari provides Instances High Availability Service for
OpenStack clouds by automatically recovering failed Instances.
Change-Id: I279d6b43f8e4d4e30b39deb607823ceca272a4b8
Implements: blueprint masakari-support
|
|
|
|
The project has been retired and there will be no Train release [1].
This patch removes Neutron LBaaS support in Kolla.
[1] https://review.opendev.org/#/c/658494/
Depends-On: https://review.opendev.org/#/c/663875/
Change-Id: I99484c48ed09f7e015e134bdff1f298c359c6905
|
|
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
|
|
|
|
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
|
|
Add Qinling Dockerfile , Qinling is an OpenStack project
to provide "Function as a service". This project aims to
provide a platform to support serverless functions.
Change-Id: Idebf5c8756a0d0225adcce29b45a399120bb5eb6
Implements: blueprint qinling-support
|
|
If you run the horizon container with a restart policy of never, and the
static asset compression fails, the container fails to start, e.g. (seen
in CI)
++ /usr/bin/manage.py collectstatic --noinput --clear
Traceback (most recent call last):
File "/usr/bin/manage.py", line 18, in <module>
from django.core.management import execute_from_command_line
ImportError: No module named django.core.management
However, with a restart policy of unless-stopped (the default). the
horizon container will fail the first time but will succeed after a
restart. This is because the settings bundle hash is updated before the
compression is attempted.
To fix this, update the hash after compression completes successfully.
Change-Id: I3f1682ed55e7d45c1e97a1b34c7993aa839f0bb2
Closes-Bug: #1824137
|
|
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
|
|
RHEL7 derived distros use Python 2.7
RHEL8 uses Python 3.6
Ubuntu 18.04 uses Python 3.6, but we haven't enabled it yet.
Debian:buster uses Python 3.7, but we haven't enabled it yet.
We have several places in code where "/lib/pythonX.Y/site-packages"
is used so we need to know value of X.Y rather than py2/py3 switch.
How to check for Python 2:
{% if distro_python_version == '2.7' %}
Breaks: Iad6b70b433a0dd1b0f8ae6790fd280594517661a
Change-Id: Ie24f109af19ae0438c21e0d43cb3cc947812b4ce
|
|
Change-Id: Ic90821f1a9ebfcea67183bb91aebca00c046133e
|