Wednesday, 2025-05-28

opendevreviewTakashi Kajinami proposed openstack/horizon master: Remove retired projects from plugin list  https://review.opendev.org/c/openstack/horizon/+/95105601:37
opendevreviewTakashi Kajinami proposed openstack/horizon master: Update bug tracker for ironic UI  https://review.opendev.org/c/openstack/horizon/+/95105701:39
opendevreviewDmitriy Chubinidze proposed openstack/horizon master: Adds changing instance password support  https://review.opendev.org/c/openstack/horizon/+/95108907:42
opendevreviewDmitriy Chubinidze proposed openstack/horizon master: Adds changing instance password support  https://review.opendev.org/c/openstack/horizon/+/95108907:54
opendevreviewIvan Anfimov proposed openstack/horizon master: Instances replaced to Servers | Part 1  https://review.opendev.org/c/openstack/horizon/+/95096608:38
opendevreviewTakashi Kajinami proposed openstack/horizon master: Update bug tracker for ironic UI  https://review.opendev.org/c/openstack/horizon/+/95105708:56
opendevreviewIvan Anfimov proposed openstack/horizon master: Instances replaced to Servers | Part 1  https://review.opendev.org/c/openstack/horizon/+/95096610:02
opendevreviewDmitriy Chubinidze proposed openstack/horizon master: Adds changing instance password support  https://review.opendev.org/c/openstack/horizon/+/95108910:06
opendevreviewDmitriy Chubinidze proposed openstack/horizon master: Adds changing instance password support  https://review.opendev.org/c/openstack/horizon/+/95108910:07
opendevreviewTakashi Kajinami proposed openstack/horizon master: Skip tests for plugin-registry.csv update  https://review.opendev.org/c/openstack/horizon/+/95110910:12
opendevreviewDmitriy Chubinidze proposed openstack/horizon master: Adds changing instance password support  https://review.opendev.org/c/openstack/horizon/+/95108910:27
opendevreviewIvan Anfimov proposed openstack/horizon master: Instances replaced to Servers | Part 1  https://review.opendev.org/c/openstack/horizon/+/95096610:38
opendevreviewDmitriy Chubinidze proposed openstack/horizon master: Adds changing instance password support  https://review.opendev.org/c/openstack/horizon/+/95108911:14
opendevreviewDmitriy Chubinidze proposed openstack/horizon master: Adds changing instance password support  https://review.opendev.org/c/openstack/horizon/+/95108911:39
opendevreviewDmitriy Chubinidze proposed openstack/horizon master: Adds changing instance password support  https://review.opendev.org/c/openstack/horizon/+/95108912:20
anfimovirhello 14:58
jjasekHello everyone :-)14:59
rdopierao/15:02
omcgonago/15:02
tmazur#startmeeting horizon15:03
opendevmeetMeeting started Wed May 28 15:03:13 2025 UTC and is due to finish in 60 minutes.  The chair is tmazur. Information about MeetBot at http://wiki.debian.org/MeetBot.15:03
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:03
opendevmeetThe meeting name has been set to 'horizon'15:03
tmazurHello everyone and welcome to the weekly meeting!15:03
chubinidzedrHi ;)15:03
tmazurToday's agenda is here: https://etherpad.opendev.org/p/horizon-release-priorities#L4015:04
tmazurThanks anfimovir :)15:04
anfimovirnp ;))15:04
anfimovirWe can start from one open question 15:05
anfimovir950966: Instances replaced to Servers | Part 1 | https://review.opendev.org/c/openstack/horizon/+/95096615:06
anfimovirWhat do your think about?15:06
tmazurWe can talk about it right after we follow the order :)15:07
tmazur#topic Notices15:07
anfimovirsorry 15:07
tmazurSchedule reminder: this week is R-18 week. Flamingo Schedule: https://releases.openstack.org/flamingo/schedule.html 15:08
tmazurNothing urgent is happening right now, Flamingo-2 is in the beginning of July15:09
tmazurI missed last week since I was on PTO, so we cut Flamingo-1 just yesterday15:10
tmazurSo all the recent changes are included as well15:11
tmazurMoving forward15:12
tmazur#topic Release priorities15:12
tmazurhttps://etherpad.opendev.org/p/horizon-release-priorities#L4415:13
tmazurjjasek thanks for your reviews15:13
chubinidzedrI'd like to discuss moving to Font Awesome 6:)15:13
chubinidzedrotherwise it will be stuck for a long time15:13
rdopierawhen did that become a release priority?15:13
anfimovirthis create problems with source installation, no problem, moved to open reviews ;)15:14
tmazurrdopiera you're right. anfimovir, chubinidzedr we try to keep release priorities clean and clear. If it's anything urgent, we can put it in open reviews on the top15:15
anfimovirsorry, ok15:16
tmazurhttps://review.opendev.org/c/openstack/horizon/+/949141   <--- rdopiera, jjasek what do you think about this one?15:16
rdopierathe instance password and volume type are also not priorities for this cycle?15:17
anfimovirRadomir, done, moved too.15:17
tmazuryes15:17
rdopierawe can make things priorities, but it requires some agreement15:18
rdopieratmazur: what's the process for this, shouldn't we have a warning first?15:18
tmazurPriorities usually are being discussed on PTG15:18
jjasektmazur, sorry I did not review/test this Drop support patch yet.15:18
rdopierawhen we deprecate settings and such, we usually have a warning one release in advance, I think dropping support for a python version is even more important?15:19
tmazurSo we don't just add new priorities without discussion 15:19
tmazurrdopiera, sure15:20
tmazurI was asking do we want to prioritize a warning for this cycle?15:20
rdopieraanfimovir: is there an urgent need to drop python 3.9?15:20
tmazuranfimovir also please add more information into the commit message. Usually we add links to the agreements and reasons we deprecate things15:21
anfimovirPython 3.9 already dropped from nova side, we can do it  until flamingo release.15:22
anfimovir[2]https://governance.openstack.org/tc/reference/runtimes/2025.2.html#python15:23
anfimovir@tmazur, ok, no problem15:23
tmazuranfimovir thanks15:23
opendevreviewIvan Anfimov proposed openstack/horizon master: Drop support for Python 3.9  https://review.opendev.org/c/openstack/horizon/+/94914115:24
anfimovircommit message updated15:24
rdopierabut other than "others are doing it", is there a technical reason for it? do we need to use some feature that doesn't work on 3.9?15:27
anfimovirfrom this side, you right.15:27
noonedeadpunkI think djhango 5.0 does not support py39 anyway?15:28
noonedeadpunkat least according to their docs15:29
noonedeadpunk#link https://docs.djangoproject.com/en/5.2/faq/install/#what-python-version-can-i-use-with-django15:29
noonedeadpunkand seemingly there's no support for 3.13 otherwise15:29
rdopieraare we switching to django 5.0 this cycle?15:29
noonedeadpunkI guess it depends if you want to add py3.13 support15:30
rdopieraI think it's useful to have the 3.9 tests running, if only to see when they start to fail because something we depend on doesn't support 3.915:30
rdopierawe will need to add py3.13 tests anyways15:30
noonedeadpunkbut Django 4.2 has no 3.13 15:31
noonedeadpunkso it looks like either 3.9 or 3.1315:31
noonedeadpunkbasically EL9 or Debian 13 choice :)15:31
rdopiera"This is not mandatory testing in the 2025.2 cycle, and there is no guarantee that the OpenStack 2025.2 release will support Python 3.13."15:32
noonedeadpunkyeah, right, it's optional15:32
noonedeadpunkit's up to project to decide15:32
rdopieraso looks like we have one more cycle, we should probably make django 5.0 a release priority for G15:32
noonedeadpunkjust highlighting that there's unlikely a possibility to have both 15:32
noonedeadpunkand also it's Django>=5.1.315:33
rdopierathanks, that's valuable information15:33
noonedeadpunk5.0 have neither of them15:33
rdopierawe will have to take it into account when planning the next cycle15:33
noonedeadpunk++15:33
tmazurThanks noonedeadpunk15:34
noonedeadpunkbtw. Django 4.2 seems to EOL before 2025.2 will EOL15:35
tmazurSo if we prioritize Django 5.1.3 for G, we can for now do a warning about 3.915:35
noonedeadpunkso in case of discovered CVE in Django, it would be not a pleasent situation15:36
rdopieratmazur: a release not would be sufficient, I guess?15:36
noonedeadpunk`Django 4.2 LTS security support ends in April 2026`15:36
rdopieranoonedeadpunk: personally it's nothing new for me, I keep backporting cve patches for the older versions of horizon that we still support all the time15:37
noonedeadpunkyeah, you probably can monkey patch some things in horizon...15:38
rdopieraabsolutely not15:38
noonedeadpunkbut how are you covering Django vulnarabilities i nHorizon then?15:39
noonedeadpunkanyway, this is probably a different discussion for a different time :)15:39
rdopieranoonedeadpunk: I backport django patches to older versions of django that we package with the open stack distribution15:39
tmazurcve patches very rarely have conflicts actually15:40
tmazurso we just backport15:40
noonedeadpunkum. so you sugest all horizon users to maintain own forks of Django and backport on their own?15:40
rdopieranoonedeadpunk: or they could pay us to do it for them ;-)15:40
noonedeadpunkright15:41
rdopierabut no, I'm not15:41
rdopierabut there is no good solution here, is there?15:41
tmazurAnyway, we will prioritize 5.1.3 for G15:41
noonedeadpunkexcept prioritizing 5.1.3 - no, there's not15:41
noonedeadpunkand yeah15:41
rdopierawe are not going to be able to swtich to django 5.1 this cycle, it's too late for such large changes15:41
tmazurAnd try to release it in G-115:41
noonedeadpunkI agree that non-SLURP will go EOL very fast15:41
tmazurIt's before EOL15:42
tmazurOk, let's move to the next topic.15:45
tmazur#topic Bug deputy report15:46
tmazurhttps://etherpad.opendev.org/p/horizon-release-priorities#L5215:46
tmazurrdopiera thanks for your review, I'll need to take a look as well15:49
tmazuranfimovir do you want to discuss your open question now?15:49
anfimovirYes15:50
anfimovirIt seems to me that the decision on swift looks strange, we support one option, but the other one is the same (the difference is not big) - no.15:51
tmazur#topic Open discussion15:51
tmazurCould you please elaborate?15:51
anfimovirPlease find time read both case in bug deputy15:52
anfimovirWe can back to this question in next week.15:52
tmazurOk15:52
anfimovirI have talk about15:52
anfimovirOpen questions 950966: Instances replaced to Servers | Part 1 | https://review.opendev.org/c/openstack/horizon/+/95096615:52
noonedeadpunkI think I tried to raise my confusion/proposal regarding Instances naming back in e0ne PTL days, but there was some argument against that, alike to term being well established in Horizon.15:55
tmazurSame with project/tenants15:56
noonedeadpunkBut this still does not dissolve the fact, that it's a very unique in the platform as a whole, as the term is not used anywhere 15:56
noonedeadpunkwell, project/tenants is a bit different15:56
anfimovirTenants already complete replaced to Projects15:56
anfimovirWe finish it in 2025.215:56
noonedeadpunkIt's incomplete migration between terms15:56
noonedeadpunkas in keystonev2 api they were named as tenants iirc15:57
noonedeadpunkBut I can't recall nova calling servers as instances... 15:57
anfimovirInstance/Server really create problems for users.15:57
noonedeadpunkCould be I joined openstack too late to remember that ofc15:57
tmazurI wasn't there either when the decision was made15:58
tmazurIs there any documentation for reference? Probably not?15:58
noonedeadpunkmeaning, we can have another round of discussion about it :D15:58
tmazurI would suggest the ext PTG15:58
anfimovirRadomir, what do you think about?15:58
tmazurDiscussions "in person" are always way more productive15:58
noonedeadpunkabout previous round of this topic which was years ago? Even if it was documented, I will never-ever find it15:59
noonedeadpunkIt was somewhere around 2017 or 2016...15:59
tmazurI was not much with Horizon at this interval, so I was not there15:59
rdopieraanfimovir: personally I think we have more important things to fix, but I won't reject such changes if someomne else wants to do the work16:00
anfimovirOk, I do it in next week..16:00
noonedeadpunkthe only concerns here, is that the change will invalidate docs, some guides with screenshots, etc16:00
noonedeadpunktranslations16:00
rdopieraanfimovir: I'm on pto next month16:01
tmazuranfimovir it will be also helpful to write it to mailing list16:01
noonedeadpunknothing too terrible, but amount might be big16:01
noonedeadpunkgreat point tmazur16:01
tmazurAnyway, let's talk next time, I have another meeting to join16:01
tmazurThanks everyone for joining and good discussions!16:01
noonedeadpunkthanks for handling the meeting!16:01
tmazurSee you next week!16:02
jjasekThank you, bye bye!16:02
anfimovirSee you.16:02
rdopierao/16:02
tmazur#endmeeting16:02
opendevmeetMeeting ended Wed May 28 16:02:13 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:02
opendevmeetMinutes:        https://meetings.opendev.org/meetings/horizon/2025/horizon.2025-05-28-15.03.html16:02
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/horizon/2025/horizon.2025-05-28-15.03.txt16:02
opendevmeetLog:            https://meetings.opendev.org/meetings/horizon/2025/horizon.2025-05-28-15.03.log.html16:02
gboutryThank you!16:02
chubinidzedrgoodbye!16:02
opendevreviewDmitriy Chubinidze proposed openstack/horizon master: Adds changing instance password support  https://review.opendev.org/c/openstack/horizon/+/95108920:28
-opendevstatus- NOTICE: The Gerrit service on review.opendev.org is temporarily unreachable due to an ongoing issue in the hosting provider where it resides22:07

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