Tuesday, 2026-09-08

opendevreviewDmitry Krasovskyi proposed openstack/horizon stable/2025.1: Fix compatibility with openstackSDK for PortForwardingManager  https://review.opendev.org/c/openstack/horizon/+/100457609:49
opendevreviewDmitry Krasovskyi proposed openstack/horizon stable/2025.2: Fix compatibility with openstackSDK for PortForwardingManager  https://review.opendev.org/c/openstack/horizon/+/100457709:50
opendevreviewDmitry Krasovskyi proposed openstack/horizon stable/2026.1: Fix compatibility with openstackSDK for PortForwardingManager  https://review.opendev.org/c/openstack/horizon/+/100457809:51
opendevreviewsean mooney proposed openstack/horizon master: xstatic is not a runtime dep of horizon  https://review.opendev.org/c/openstack/horizon/+/100457911:29
sean-k-mooneyhi folks i just want to bring https://review.opendev.org/c/openstack/horizon/+/1004579 to your attention11:50
sean-k-mooneyhorizon currently list xstatic as a depency even though it is never imported in the horizon repo11:50
sean-k-mooneyxstatic is not buildable form sdist with setuptools >=82 because pkg_resouces was removed11:51
sean-k-mooneyso if you use moderne setuptools with horizons requirements.txt you cant install it from sdist11:51
sean-k-mooneyim fixing our downstream builds to work around it11:52
sean-k-mooneybut it woudl be good if we could remove xstatic form the requireemnt.txt11:52
sean-k-mooneydevstack is only passing today because its pulling the prebuilt wheel same for tox11:52
sean-k-mooneyci is sitll in flight but its looking good sofar https://zuul.openstack.org/status?change=100457911:53
sean-k-mooneyif horizon has not cut rc1 yet it woudl be good to include that chagne11:53
sean-k-mooneyrdopiera: ^ fyi11:54
sean-k-mooneyjjasek: ^11:55
jjaseksean-k-mooney, thanks for the info and the patch! Will take a look at it.12:28
rdopierasean-k-mooney: why not just install pkg_resources, it's now a separate package12:35
sean-k-mooneywell for one even if it is xstatic is not a runtime dep12:35
sean-k-mooneyso listing it in requirements.txt is incorrect12:35
sean-k-mooneyyou could portially do that as well but that increase the security surface12:36
sean-k-mooneyif horizon used pkg_resouces direcly it woudl be fien but if its not a direct dependcy of horizon or the openstack dash board it shoudl not be in requirements.txt12:37
rdopierabut it is a runtime dependency, without xstatic installed, we can't import any of the xstatic-* modules12:38
rdopierabecause they are submodules of the xstatic module12:39
sean-k-mooneythey are not submoutle sof that12:39
sean-k-mooneythey are seperate namespaces pakcages12:40
rdopierasorry, it's very hard for me to read what you are typing, I'm not a native English speaker12:41
rdopierawhat is submoutle?12:41
sean-k-mooneysorry they are not sub moudles12:42
sean-k-mooneyeach xstatic package is an independet namespaces package12:42
sean-k-mooneyhttps://zuul.opendev.org/t/openstack/buildset/0ec321e7c75f488183238c772b3f9d9e12:42
sean-k-mooneythe last job has not completed yet but the majority fo the check jobs have already run and passed12:43
sean-k-mooneythe xstatic python package is entirly optional none of the xstatic-* packages we use in horizon depend on it eitehr. https://zuul.opendev.org/t/openstack/build/1ac79c911dcb4ec1af81d2a2097fe38b/log/controller/logs/devstacklog.txt#1205212:45
rdopieraI guess it changed somewhere along the way12:46
sean-k-mooneynot recently, but maybe as part of the work stephen did last cycle to remove the pkg_resocues deps 12:47
rdopieraif it works, I'm sure it's fine and if it changes again we can always bring it back12:47
rdopierasean-k-mooney: no, it must have been earlier than that, where the namespace packages changed in python12:48
rdopieraxstatic started when they were the new hot thing12:48
rdopierasean-k-mooney: are you also going to be removing it from global requirements?12:50
sean-k-mooneywe could but i was not planning too12:50
sean-k-mooneyif we have no deps anywayer on it we could12:50
sean-k-mooneyi was not sure if anything else might use it?12:50
rdopieraI don't see what they would be using it for?12:50
rdopieraif it's not needed to import the xstatic-* packages12:51
sean-k-mooneyit looks like https://opendev.org/openstack/xstatic-angular/src/branch/master/setup.py#L2 is usign xstatic directly12:52
sean-k-mooneybut i dont knwo if xstatic-angular is still used12:54
sean-k-mooneyit missing a pyproject.toml12:54
sean-k-mooneyso it can be released with our current tooling since that is now requried i belive12:54
rdopierait is https://github.com/openstack/horizon/blob/master/openstack_dashboard/utils/settings.py#L23412:56
sean-k-mooneyso i coudl be wrong but that is not importign xstatic its importhing the namespacesed moduels12:57
rdopierasean-k-mooney: that `from xstatic.pkg import angular` is how every program that uses xstatic-* packages imports them12:57
rdopieraso if that breaks, it will also break everywhere else12:57
sean-k-mooneyhttps://github.com/openstack/horizon/blob/master/openstack_dashboard/utils/settings.py#L28812:58
sean-k-mooneyso you are using importlib to do the import12:58
sean-k-mooneynot xstatic12:58
sean-k-mooneyhttps://github.com/openstack/horizon/blob/master/openstack_dashboard/utils/settings.py#L1412:59
rdopierayes, but it does the equivalent of that line of code12:59
rdopierait does `import xstatic.pkg.angular` basically13:01
sean-k-mooneyyes but again its an namespace package which may or may not actully need xstatic13:01
sean-k-mooneybtu you have other problems with the xstatic packaging as well13:01
sean-k-mooneyye have not added pyproject.toml files to all the xstatic repos13:02
rdopierathen what's wrong with that line in xstatic-angular's setup.py?13:02
sean-k-mooneyno13:02
sean-k-mooneyso there are two things13:02
sean-k-mooneyhttps://opendev.org/openstack/xstatic-angular13:02
sean-k-mooneydoes not have a pyproject.toml which si now requried by the pti for python packages13:03
sean-k-mooneysetup.py and setup.cfg can be kept for backward compatiblty13:03
rdopieraI really find it hard to understand you, sorry, I need a break13:03
sean-k-mooneybut the release tooling requries a pyproject.toml now13:03
sean-k-mooneyhttps://opendev.org/openstack/xstatic-angular/src/branch/master/setup.py#L2 is importing from the current package13:04
sean-k-mooneyso while that looks like its importing an xstatic subpackage i dont think it actully is13:04
sean-k-mooneythere are no requiremets expressed in https://opendev.org/openstack/xstatic-angular/src/branch/master/setup.py#L2313:05
sean-k-mooneyso the current setup.py is basiclly declaring that it has no dependencies13:05
rdopieramaybe you could come tomorrow to the team meeting, there will be native English speakers present then who can handle it better13:05
rdopierait has no dependencies, it only holds data files13:07
rdopierathat's the entire idea of xstatic-* packages13:07
sean-k-mooneyyep13:07
sean-k-mooneyand if you look at the package layout https://opendev.org/openstack/xstatic-angular/src/branch/master/xstatic/pkg/angular13:08
sean-k-mooneyyou can see its declaring itself as xstatic.pkg.angular  so it will be placed in xstatic/pkg/angular under sitepackages13:08
sean-k-mooneyanyway ci passes, https://review.opendev.org/c/openstack/horizon/+/1004579  i can see if i can attend the meetign tomorrow, from an outsdie perspective it does not look like xstatic is a runtime requirement but i may have missed something13:11
rdopieraI mean it looks like it works, as I said, in the worst case we will put it back. I meant the other problems for the meeting.13:12
rdopieraif they require pyproject.toml now, I expect they are going to have a lot of problems with a lot of packages13:12
sean-k-mooneywe haveen been adding pyproject.toml to all python repos for the last 2 release13:13
sean-k-mooneyand updated the pti to reflect that earlier in the year13:13
sean-k-mooneyhttps://github.com/openstack/governance/commit/42f6cf0fb2923d7c4fadea1547d80b7287d537d513:13
sean-k-mooneythis cycle we are not requiring all metadata to move to pyproject.toml but the minium stub is expected to be in place13:14
sean-k-mooneywithout a pyproject.toml pip will not use pbr, perhaps xstatic is not using pbr today and it may work without it but it would not be complient with the pti13:16
rdopieraI guess we need to add a topic to the PTG to plan this as a release priority next cycle13:17
rdopieraas I said, it's just data files and a python file with metadata, there is really nothing we would need pbr for13:18
sean-k-mooneyall it gives you is automatic generation of package metadata such as the git sha it was buitl from13:19
rdopierayeah, not needed here13:19
sean-k-mooneybut its more a case of that is the specifed packaging tool for all python deliverables13:19
rdopieraparhaps we should move those xstatic-* packages out of the openstack repos then13:20
rdopieraI think opendev had some place for projects that are not officially part of openstack?13:21
sean-k-mooneymaybe or just add the file its pretty trivial. but that kind of up to ye13:21
sean-k-mooneyyou can create seperate namespaces via a patch to project-cofnig13:21
rdopieraif we add pbr in there, all other projects that use those modules (moinmoin wiki) will suddenly depend on pbr13:21
sean-k-mooneybut you cannot use the release repo for reelase if you do that13:21
rdopieraanyways, I think it's something for the ptg13:22
rdopierathank you for letting us know13:22
sean-k-mooneyyou could proably create horizon-extra/xtatic ...13:22
sean-k-mooneybut you could also just propose an update to the pti13:22
sean-k-mooneyand specificly call out xstatic as not requireing pbr13:23
sean-k-mooneyits an evolving document so you can just propsos an update as the xstatic packages are really javascript/html/css asset packages that hapen to use python packaging rahter then python packges in the normal sense13:24
opendevreviewMerged openstack/horizon master: tox: Drop redundant passenv  https://review.opendev.org/c/openstack/horizon/+/100422115:17
opendevreviewMerged openstack/horizon master: Stop using deprecated SDK attribute names in tests  https://review.opendev.org/c/openstack/horizon/+/100434315:17
zigoHi team! The current requirements.txt of Horizon 26.0.0 claims Horizon is compatible with openstacksdk 4.5.0. Reality check of unit tests: it didn't even pass unit tests with sdk 4.10, I had to increase the version in debian/control so it would take 4.19 from Debian Experimental.19:20
zigoI would strongly suggest fixing this during the RC period.19:21
opendevreviewTatiana Ovchinnikova proposed openstack/horizon master: SDK for Nova hypervisors  https://review.opendev.org/c/openstack/horizon/+/100361620:37
tmazurThank you zigo, we will update the requirements21:15
opendevreviewKevin Allioli proposed openstack/horizon master: Fix flaky test_image_filtration_admin test  https://review.opendev.org/c/openstack/horizon/+/99302322:09

Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!