horizon now supports Django 4.2 version. So
this patch make ""horizon-tox-python3-django42" job
as voting.
Change-Id: I09e50fdede1003fe9a94d129dffe03d224e52e50
As nodejs v20 job is passing in horizon and all horizon
plugins [1]. So we didn't require the nodejs v18 job.
This patch removes the nodejs v18 job definition from
``.zuul.d/nodejs-jobs.yaml`` and other nodejs v18 job
references.
[1] https://review.opendev.org/c/openstack/horizon/+/904934
Change-Id: I3a27799b4864c572a2ef7bf7477ea2b21eb8f395
This patch adds a non-voting job 'horizon-integration-pytest'.
It is failing as of now but we are planning to fix it asap.
Change-Id: I3130314be0dfa04fbb5245d0e15e0ab299f2b543
Django 4.2 is our primary version in 2023.2 (Caracal),
so we need to start testing with Django 4.2.
Once all unit tests work, let's switch it to voting.
PYTHONWARNINGS in tox.ini is also simplified. We had three similar
variants of PYTHONWARNINGS in tox.ini. There is no need to use a
different value for py3 and py39 as we already use py39 by default.
PendingDeprecationWarning was added to hide Django deprecation
warnings, so I keep it now. On the other hand I think we should
handle Django deprecation warnings much earlier to sync Django
releases more promptly, so TODO comment is added.
Change-Id: I530be8fde637a912968b4ce7dbc94a4108dc50df
This patch makes "horizon-integration-tests" job voting
again. It was changed to non-voting so that patch that
update Xstatic-jQuery upper bound, update cirros version
for the horizon-integration job and a few other changes
which are required to fix the horizon-integration can get merged.
The patch [1] is already merged and the upper bound in
openStack/requirement also got updated[2]. So let's make
horizon-integration job voting again.
[1] https://review.opendev.org/c/openstack/horizon/+/887548
[2] https://review.opendev.org/c/openstack/requirements/+/887933
Change-Id: I0059c2cd47e6b540306337caa3e0f826f3b755a9
The jquery-migrate 3 requires newer jquery than we have.
Also added all the other fixes for integration tests to see
if that resolves our problems.
This needs to be merge first so that patch which update the
upper bump of XStatic-JQuery in openstack/requiremensts [1]
can be merged.
Note: This patch also make horizon-integration job to non-voting
so that we can merge this patch and once openstack/requirements
[1] patch is merged, we will make horizon-integartion job voting
again
[1] https://review.opendev.org/c/openstack/requirements/+/887933
Co-Author-By: manchandavishal <manchandavishal143@gmail.com>
Change-Id: I9b8a5e8abe734e7fd99aa0066ede0377e34fbf44
xstatic-angular-fileupload pypi moved under openstack namespace.
It is already renamed in openstack/project-config [1].
This patch do the same in ``.zuul.d/xstatic-master.yaml`` file.
[1] https://review.opendev.org/c/openstack/project-config/+/873843
Change-Id: I41cf26f7586908796e339bb78f81c93cf5911ce2
The repository has been retired and will be maintained in an external
organization[1]. Because we install the library from Pypi, we no longer
need to clone it from opendev repository.
[1] https://github.com/xstatic-py/xstatic-font-awesome
Change-Id: I9c75b084705dfdc6df52aca1659f89444c8a1728
horizon and ironic-ui already migrated to nodejs18 but parent
job of 'horizon-cross-ironic-ui-npm' still uses nodejs16.
So this patch updates nodejs16->nodejs18 version in parent job
of "horizon-cross-ironic-ui-npm".
Note: It also updates the python version to py39->py310
in parent jobs of "horizon-cross-manila-ui-python" and
"horizon-cross-heat-dashboard-python" as per the antelope runtime.
Change-Id: I4b34661e91cb307df49f7282196cca8961d7eac1
As nodejs v18 job is passing in horizon and all horizon
plugins [1]. So we didn't require the nodejs v16 job.
This patch removes the nodejs v16 job definition from
``.zuul.d/nodejs-jobs.yaml`` and other nodejs v16 job
references.
[1] https://review.opendev.org/c/openstack/horizon/+/865293
Change-Id: I9e791c24944f228a27813eb860080d3ea3e1449d
As openstack-tox jobs migrated from ubuntu focal to ubuntu
jammy[1]. So horizon integration and selenium-headless jobs
start failing. This patch changes the nodeset for both
these jobs to ubuntu focal as a workaround to unblock
the CI.
[1] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/861116
Related-Bug: #1996638
Change-Id: I674d7d3a8e1b34229fd5ef0285153e13324d3417
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for antelope. Also,
updating the template name to generic one.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: I57d369e1e1a84a2685e3eb157699e1262c996400
horizon and ironic-ui already migrated to nodejs16 but parent
job of 'horizon-cross-ironic-ui-npm' still uses nodejs10.
So this patch updates nodejs10->nodejs16 version in parent job
of "horizon-cross-ironic-ui-npm".
Change-Id: Iff8b60f79de26fb22f014ebc9f15d12dcb89f822
Python runtimes for Zed are 3.8, 3.9 and optionally 3.10 [1][2],
so tox envs in tox.ini are updated accordingly.
Declare python_requires >=3.8 in setup.cfg
python_requires are declared in many projects during dropping
python 2.7 support. It is good to follow the convention and
it also clarifies our python interpreter requirement.
This commit also cleans up python2.7 related stuffs in setup.py.
Both are related to the supported versions of python,
so I made both changes in a single commit.
[1] https://governance.openstack.org/tc/reference/runtimes/zed.html
[2] b740b42fb1/zuul.d/project-templates.yaml (L542)
Change-Id: I4161816fd1fec19a3834cc7d994b3f761e1ab2ce
Closes-Bug: #1960887
This patch defines a project template "horizon-nodejs-jobs"
for nodejs v16 jobs which is the next LTS version of nodejs[1]
and also, the runtime for the Zed cycle[2]. Next step is to
the horizon plugins use this template to run nodejs v16 jobs
and once it's pass in all horizon plugins we can remove
nodejs v14 jobs completely.
This patch also do few cleaups:
• remove nodejs v14 job to run on horizon gate because we don't
need to run both nodejs v14 and nodejs v16 jobs for horizon.
• replace nodejs v14 experimental xstatic job with nodejs v16 job.
• replace horizon-nodejs14-run-test periodic job with nodejs v16.
[1] https://nodejs.org/en/about/releases/
[2] https://governance.openstack.org/tc/reference/runtimes/zed.html#node-js-runtime-for-zed
Depends-On: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/831912
Change-Id: Ic11f2c3bd7a6a09c8fa6fb7a457e83e889deed6b
keystone does not distinguish public and admin endpoints since
Train [1], so there is no need to use a separate endpoint for
keystone admin operations. admin endpoint still can be configured
but there is no functional difference anymore from other endpoints.
We do not need to require admin endpoint and can use an endpoint
specified by OPENSTACK_ENDPOINT_TYPE for all API operations.
This commit reverts commit f9bab3fe195eb13635aa70cb910d94df98d66cf3
as we no longer need the workaround.
[1] https://review.opendev.org/c/openstack/keystone/+/664246
Closes-Bug: #1950659
Change-Id: I2660fd2df8081e1d2d9c84626037f94bd9d137a5
Django 2.2 support was dropped. Django 2.2 ends its extended support
in April 2022[1]. Considering this, horizon dropped Django 2.2 support
and use Django 3.2 as default version of Django.
It also updates the python version from py38 to py39 for
"horizon-non-primary-django-jobs" and
"horizon-tox-python3-django" project template because py36
and py39 are now runtime for the Yoga cycle[2]. So I have updated it to
py39.
[1] https://www.djangoproject.com/download/
[2] https://review.opendev.org/c/openstack/governance/+/820195
Change-Id: I8886f12f7e51b721ac5123070086d5dcfefe4e72
CI job "horizon-integration-tests" needs an admin endpoint. Since
[1] devstack does not create it by default. This patch enables it
in this job now.
[1] https://review.opendev.org/c/openstack/devstack/+/777345
Related-Bug: #1950659
Change-Id: I5a81344ea3aaa182d8b4d6a15a6240d3c99557cf
I believe we need the following steps and it is what I did in past
when we bump the Django minimum version.
1. (already done) update global-requirements.txt to allow horizon to
update requirements.txt to include Django 3.2.
2. specify the required Django version which includes both 2.2 and 3.2
(at this point upper-constraints uses 2.2)
3. update upper-constraints.txt in the requirements repo to use Django 3.2
4. bump the min version of Django in horizon
(optionally) update non-primary-django tests to include non-primary versions of
Django. It seems you drops 2.2 support together when we support 3.2, so perhaps
this step is not the case though.
https://review.opendev.org/c/openstack/horizon/+/811412 directly updated
the min version to Django 3.2 which is incompatible with the global
upper-constraints.txt.
To avoid this, https://review.opendev.org/c/openstack/horizon/+/815206 made
almost all tests non-voting. I am not a fan of such approach and believe
there is a way to make the transition of Django version more smoothly.
---
This commit reverts the zuul configuration changes in
https://review.opendev.org/c/openstack/horizon/+/815206 and
https://review.opendev.org/c/openstack/horizon/+/811412.
horizon-tox-python3-django32 is voting now as we are making it
the default version.
Change-Id: I60bb672ef1b197e657a8b3bd86d07464bcb1759f
This patch update Django version to the current LTS version i.e. 3.2.
Django 2.2 is going to end its extended support by April 2022[1].
horizon and all its plugins already support Django3.2 version, So
let's make this the default version. It also bump few other packages
version in lower-constraints.txt to make it work with Django 3.2.
Note: It also change 'openstack-tox-py38' job to non-voting
which I will revert in follow-up patch once this patch is merged.
[1] https://www.djangoproject.com/download/
Change-Id: I49e323b76ad2c2e680c3f133d0f219d850f7908c
This commit adds a non-voting unit test job with Django 3.2.
Jobs with Django 3.0 and 3.1 are dropped now.
They were introduced before Django 3.2 was released.
Django 3.0 reached EOL and Django 3.1 will reach EOL this December.
Django 3.2 is an LTS version so testing with Django 3.2 is enough.
Change-Id: Ic6ba0ea281b287b7f4762f92e2e81a6fd654da8f
As we added nodejs14 support in
I423e8bbec21ab1d52a0a840d779723aa92678735 change.
We can now drop nodejs10 or related job as it is EOL.
Change-Id: I54e909d2ba0c6d751247809373166c37f8baeb77
Nodejs10 is going to EOL by April 2021 [1].
So this patch defines a template for nodejs14 jobs
which is next LTS vesrion of nodejs. Once we migrate
to nodejs14 version we can drop nodejs10 support.
[1] https://nodejs.org/en/about/releases/
Change-Id: I423e8bbec21ab1d52a0a840d779723aa92678735