Wednesday, 2021-05-05

*** dave-mccowan has joined #openstack-meeting-alt00:10
*** jinyuanliu has quit IRC01:05
*** jinyuanliu has joined #openstack-meeting-alt01:05
*** jamesmcarthur has joined #openstack-meeting-alt01:05
*** tmazur has quit IRC01:21
*** jamesmcarthur has quit IRC01:28
*** jamesmcarthur has joined #openstack-meeting-alt01:46
*** jamesmcarthur has quit IRC01:50
*** jamesmcarthur has joined #openstack-meeting-alt02:00
*** reddy has quit IRC02:16
*** jamesmcarthur has quit IRC02:26
*** jamesmcarthur has joined #openstack-meeting-alt02:27
*** carloss has quit IRC02:30
*** rcernin has quit IRC03:05
*** rcernin has joined #openstack-meeting-alt03:16
*** jamesmcarthur has quit IRC03:25
*** enriquetaso has quit IRC03:26
*** vishalmanchanda has joined #openstack-meeting-alt04:51
*** ralonsoh has joined #openstack-meeting-alt06:11
*** whoami-rajat has joined #openstack-meeting-alt06:18
*** slaweq has joined #openstack-meeting-alt06:26
*** gyee has quit IRC06:32
*** e0ne has joined #openstack-meeting-alt07:07
*** sangeet has joined #openstack-meeting-alt07:17
*** rcernin has quit IRC07:21
*** rcernin has joined #openstack-meeting-alt07:25
*** rdopiera has joined #openstack-meeting-alt07:30
*** tosky has joined #openstack-meeting-alt07:30
*** LinPeiWen has joined #openstack-meeting-alt07:57
*** rcernin has quit IRC07:59
*** ianychoi_ has quit IRC08:13
*** rcernin has joined #openstack-meeting-alt08:23
*** rcernin has quit IRC08:29
*** rcernin has joined #openstack-meeting-alt08:38
*** rcernin has quit IRC08:42
*** rcernin has joined #openstack-meeting-alt08:46
*** rcernin has quit IRC09:30
*** rcernin has joined #openstack-meeting-alt09:54
*** rcernin has quit IRC10:05
*** LinPeiWen has quit IRC10:20
*** tosky has quit IRC10:38
*** tosky has joined #openstack-meeting-alt10:38
*** carloss has joined #openstack-meeting-alt10:41
*** e0ne has quit IRC10:42
*** tosky_ has joined #openstack-meeting-alt10:45
*** tosky has quit IRC10:47
*** tosky_ is now known as tosky10:49
*** rcernin has joined #openstack-meeting-alt10:52
*** rcernin has quit IRC10:58
*** rcernin has joined #openstack-meeting-alt11:02
*** rcernin has quit IRC11:06
*** rcernin has joined #openstack-meeting-alt11:24
*** rcernin has quit IRC11:28
*** rcernin has joined #openstack-meeting-alt11:45
*** rcernin has quit IRC11:55
*** Luzi has joined #openstack-meeting-alt12:00
*** dviroel is now known as dviroel|nho12:01
*** jinyuanliu has quit IRC12:03
*** jinyuanliu has joined #openstack-meeting-alt12:03
*** sangeet has quit IRC12:10
*** jamesmcarthur has joined #openstack-meeting-alt12:16
*** rcernin has joined #openstack-meeting-alt12:18
*** eharney has joined #openstack-meeting-alt12:22
*** rcernin has quit IRC12:23
*** jamesmcarthur has quit IRC12:31
*** jamesmcarthur has joined #openstack-meeting-alt12:33
*** eharney has quit IRC12:37
*** eharney has joined #openstack-meeting-alt12:52
*** enriquetaso has joined #openstack-meeting-alt12:52
*** jinyuanliu has quit IRC13:05
*** jinyuanliu has joined #openstack-meeting-alt13:05
*** rdopiera has quit IRC13:28
*** rdopiera has joined #openstack-meeting-alt13:28
*** tmazur has joined #openstack-meeting-alt13:28
*** miniroy has joined #openstack-meeting-alt13:33
*** jamesmcarthur has quit IRC13:36
*** reddy has joined #openstack-meeting-alt13:48
*** rosmaita has joined #openstack-meeting-alt13:51
*** jamesmcarthur has joined #openstack-meeting-alt13:52
*** Luzi has quit IRC13:59
rosmaita#startmeeting cinder14:00
openstackMeeting started Wed May  5 14:00:06 2021 UTC and is due to finish in 60 minutes.  The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: cinder)"14:00
openstackThe meeting name has been set to 'cinder'14:00
rosmaita#topic roll call14:00
*** openstack changes topic to "roll call (Meeting topic: cinder)"14:00
eharneyhi14:00
toskyhi (around a bit, I may have to drop)14:00
whoami-rajatHi14:01
*** e0ne has joined #openstack-meeting-alt14:02
jungleboyjHello.14:02
rosmaitahello everyone14:02
rosmaita#link https://etherpad.opendev.org/p/cinder-xena-meetings14:02
walshh_hi14:02
rosmaita#topic announcements14:02
*** openstack changes topic to "announcements (Meeting topic: cinder)"14:02
rosmaitai posted a summary of our discussions at the PTG14:03
rosmaita#link https://wiki.openstack.org/wiki/CinderXenaPTGSummary14:03
jungleboyj👍14:03
rosmaitayou should take a look at your discussion and check it for accuracy14:03
enriquetasohi14:03
rosmaitait's a wiki, so you should be able to make correctinos14:03
rosmaita(that's a typo, i'm not trying to be cute)14:03
enriquetaso:P14:04
jungleboyjLOL14:04
rosmaitai was a bit consistent about using irc nicks and real first names throughout the doc14:04
rosmaitaone thing i do want to point out are the cycle priorities14:04
rosmaita#link https://wiki.openstack.org/wiki/CinderXenaPTGSummary#Xena_Cycle_Priorities14:04
rosmaitathere are some priorities addressing stability that don't really have a deadline14:05
rosmaitaand those tend to get lost14:05
*** macz_ has joined #openstack-meeting-alt14:05
rosmaitabut they can be done in small pieces14:05
rosmaitawhat i'd like you to do is to use the gerrit topic listed so we can keep visibility on them14:06
rosmaitathat is, so you can get quick review of your patches14:06
rosmaitathat's all from me, anyone else have an announcement?14:07
rosmaitaguess not14:08
rosmaita#topic midcycle meeting times14:08
*** openstack changes topic to "midcycle meeting times (Meeting topic: cinder)"14:08
*** LinPeiWen has joined #openstack-meeting-alt14:08
rosmaitalast week i asked you to check on whether the dates are ok14:08
rosmaitai haven't heard anything14:09
jungleboyjOops.  :-(14:09
rosmaitaso i am assuming that wednesday 2 june and wednesday 4 august are unobjectionable?14:09
enriquetasosorry about that..14:09
rosmaitawell, it won't hurt to wait one more week to schedule these14:09
rosmaitaso14:09
*** macz_ has quit IRC14:09
jungleboyjAt the usual cinder meeting time plus an hour?14:10
whoami-rajatthe timing and dates work for me14:10
rosmaitaor minus an hour14:10
whoami-rajatrosmaita: was there a poll for this?14:10
rosmaitano we were going to vote in the meeting14:10
jungleboyjYeah.  That is as good a time as any for me.14:10
rosmaitathat is, this meeting14:10
whoami-rajatok cool14:11
rosmaitaso, to summarize, the midcycle will be on a wednesday and will overlap with the normal cinder meeting time14:11
rosmaitaso the only question is whether people are planning to be on vacation those weeks, or if there is a major opensource/python event those weeks14:12
rosmaitai don't know of any major events14:12
rosmaitaso my question right now is, are people ready to vote to pick the times for those days?14:13
rosmaitamaybe we need to vote on that!14:13
rosmaitaAre you ready to vote on the time for the midcycles today?14:14
rosmaita#startvote yes, no14:14
openstackUnable to parse vote topic and options.14:14
rosmaita:D14:14
rosmaita#startvote Are you ready to vote on the time for the midcycles today? yes, no14:15
openstackBegin voting on: Are you ready to vote on the time for the midcycles today? Valid vote options are yes, no.14:15
openstackVote using '#vote OPTION'. Only your last vote counts.14:15
rosmaita#vote yes14:15
whoami-rajat#vote yes14:15
enriquetaso#vote yes14:15
eharney#vote maybe14:15
openstackeharney: maybe is not a valid option. Valid options are yes, no.14:15
eharney#vote yes14:15
walshh_#vote yes14:15
jungleboyj#vote yes14:15
rosmaitai thought i was committed to democracy, so it's kind of disconcerting to see that i don't know how to use the voting feature of the meetbot14:16
jungleboyj#fail14:16
jungleboyj;-)14:16
rosmaitathat seems to be everyone, will close the vote in 20 seconds14:17
rosmaita#endvote14:17
openstackVoted on "Are you ready to vote on the time for the midcycles today?" Results are14:17
openstackyes (6): enriquetaso, walshh_, whoami-rajat, jungleboyj, rosmaita, eharney14:17
rosmaitaok, guess we are ready14:18
rosmaitathe R-18 midcycle will be held on Wednesday 2 June 202114:18
rosmaitawe need to pick a time14:18
rosmaitaoptions are:14:18
rosmaitaA 1300-1500 UTC14:18
rosmaitaB 1400-1600 UTC14:18
rosmaitaC need more options14:18
rosmaita#startvote time for the 2 June midcycle? A, B, C14:18
openstackBegin voting on: time for the 2 June midcycle? Valid vote options are A, B, C.14:18
openstackVote using '#vote OPTION'. Only your last vote counts.14:18
jungleboyj#vote B14:19
whoami-rajat#vote A, B14:19
openstackwhoami-rajat: A, B is not a valid option. Valid options are A, B, C.14:19
rosmaita#vote B14:19
whoami-rajat#vote A14:19
walshh_#vote B14:19
eharney#vote B14:19
enriquetaso#vote B14:20
rosmaitai think that's everyone ... will wait 20 sec14:21
tosky(I always vote "it will conflict with something anyway")14:21
rosmaita#endvote14:22
openstackVoted on "time for the 2 June midcycle?" Results are14:22
openstackA (1): whoami-rajat14:22
openstackB (5): jungleboyj, enriquetaso, eharney, rosmaita, walshh_14:22
rosmaitaok 1400-1600 it is14:22
rosmaitanext one14:22
rosmaitathe R-9 midcycle will be held on Wednesday 4 August 202114:22
rosmaitalet's pick a time14:22
rosmaitaoptions are:14:22
rosmaitaA 1300-1500 UTC14:22
rosmaitaB 1400-1600 UTC14:22
rosmaitaC either one of the above14:22
rosmaitaD need more options14:22
rosmaita#startvote time for the 4 August midcycle? A, B, C, D14:22
openstackBegin voting on: time for the 4 August midcycle? Valid vote options are A, B, C, D.14:22
openstackVote using '#vote OPTION'. Only your last vote counts.14:22
eharney#vote C14:23
tosky#vote C14:23
rosmaita#vote C14:23
jungleboyj#vote B14:23
whoami-rajat#vote C14:23
enriquetaso#vote C14:23
walshh_#vote C14:23
rosmaitai think that's everyone .... will close the vote in 20 sec14:24
rosmaita#endvote14:25
openstackVoted on "time for the 4 August midcycle?" Results are14:25
openstackC (6): tosky, eharney, walshh_, whoami-rajat, rosmaita, enriquetaso14:25
openstackB (1): jungleboyj14:25
rosmaitaOK, that makes 1400-1600 the winner14:25
rosmaitaok, thanks everyone, i will send out an email for the benefit of people who weren't here14:25
rosmaita#action rosmaita announce midcycle date/times14:26
rosmaita#topic final train release status14:26
*** openstack changes topic to "final train release status (Meeting topic: cinder)"14:26
rosmaitawhoami-rajat: you have the floor14:26
rosmaita#link https://etherpad.opendev.org/p/train-final-release14:26
whoami-rajatSo rosmaita updated the tracker with patches to be included in final train release (thanks!)14:27
whoami-rajatWe currently only have open patches in cinder train14:27
whoami-rajatos-brick patches merged14:27
whoami-rajatand other branch doesn't have new patches, we did a release recently so no need to release them this time14:28
rosmaitasomeone (tosky?) put a question about the stabilization fix14:28
rosmaitathat is, backport https://review.opendev.org/c/openstack/cinder/+/785970 to train14:28
eharneywe should do that, i'll propose it14:28
whoami-rajatrosmaita: there's one patch from SVF failing because of other patch dependency, I've backported the other one so we can review it and fix the gate on first one?14:29
rosmaitai have no objection14:29
whoami-rajatsounds good14:29
rosmaitawhoami-rajat: sure, i was hoping that the SVF team would do it14:29
rosmaitamy "no objection" was in response to eharney14:29
whoami-rajatrosmaita: they haven't responded to my comment since a long time so i wasn't sure they're going to do it14:30
toskythat was me, yes, thanks14:30
rosmaitawhoami-rajat: i agree about your proposal, though, it is probably better to have both fixes together14:30
toskydo we have any contact for that team? Maybe a direct email?14:31
rosmaitawell, they are usually making pests of themselves asking for reviews :P14:31
whoami-rajatrosmaita: i didn't understand, the second one needs to be merged to pass gate on first one? then we can merge first one14:31
rosmaitaso i'm kind of surprised that they've gone silent14:31
*** ikanias has joined #openstack-meeting-alt14:31
rosmaitawhoami-rajat: i meant it is better to have both those fixes in train14:32
whoami-rajatrosmaita: yes, agree14:32
rosmaitaso what you said .... we merge the patch you just proposed first, which will allow us to rebase the current failing patch14:33
whoami-rajatyes14:33
whoami-rajatatleast that's what we did in other branches14:33
eharneyIMO we should also get https://review.opendev.org/c/openstack/cinder/+/783204 in which is currently languishing on stable/ussuri review14:34
*** sangeet has joined #openstack-meeting-alt14:34
*** sangeet has left #openstack-meeting-alt14:34
jungleboyjeharney:  ++ Have a few things languishing.14:34
whoami-rajatcan anyone propose the backports (or i can do) and we can add them to the etherpad14:35
eharneyi'll propose that one14:35
whoami-rajatok thanks14:35
rosmaitaok, i just approved https://review.opendev.org/c/openstack/cinder/+/78320414:36
rosmaitai think it makes sense to get it into train, too14:36
rosmaitaanything else anyone is aware of?14:37
whoami-rajatthat's all from me14:37
rosmaitaok, thanks14:38
rosmaitatosky: are you available now?14:38
enriquetasoshould we backport to train this https://review.opendev.org/c/openstack/cinder/+/785223 too?14:39
toskyrosmaita: zep14:39
eharneyenriquetaso: we could, but i don't know that it's too crucial since it seems to mostly only hit CI jobs and not users14:40
rosmaitajust moved you up in the agenda14:40
enriquetasosure, thanks14:40
whoami-rajateharney:  but we've faced consistent lvm-lio job failures on train gate before14:41
toskywhoami-rajat: iirc that fix is for the LVM version in focal, which is only supported in victoria and newer releases14:41
eharneywill there still be lvm-lio train jobs..?14:41
toskyuntil we support train, yes (but based on bionic)14:42
enriquetaso++14:42
toskystein, train and ussuri (maybe also rocky, don't remember) are bionic14:42
eharneyok, well, i'm not opposed to backporting it, for sure14:42
rosmaitaok, we can always backport it later if necessary, doesn't really affect the release14:43
rosmaita(unless we're seeing gate failures that prevent other stuff from merging)14:43
rosmaita#topic some gate-related issues14:43
*** openstack changes topic to "some gate-related issues (Meeting topic: cinder)"14:43
toskyvery quick, two fixes for jobs:14:44
rosmaita#link https://review.opendev.org/c/openstack/cinder/+/78971714:44
rosmaitai think that one looks fine14:44
rosmaita#link https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/78675514:44
rosmaitai wasn't sure where to see this one is affecting stein?14:45
toskyiirc because we haven't submitted new stein patch recently14:45
*** LinPeiWen has quit IRC14:46
toskyI've noticed while working on https://review.opendev.org/c/openstack/os-brick/+/786737 (which is worth considering too, low prio as it's stein)14:46
toskythe first revision of the patch failed because of that; the current revision works because it depends on the cinder-tempest-plugin fix14:47
rosmaitaok, i was looking at a brick patch, not cinder14:47
rosmaitaall stable cores: give ^^ some attention14:48
rosmaitathanks, Luigi14:48
rosmaita#topic interop guidelines review14:48
*** openstack changes topic to "interop guidelines review (Meeting topic: cinder)"14:48
rosmaitahopefully we can get through this really quick14:48
rosmaitathis is what we are talking about:14:49
rosmaita#link https://wiki.openstack.org/wiki/CinderXenaPTGSummary#The_Interoperability_Working_Group14:49
rosmaita"Cinder team: will review mv changes between 3.0 and 3.64 to see if any "advisory" tests should be added"14:49
rosmaitajust so you know where to look14:49
rosmaitathis is the next set of capabilities:14:49
rosmaita#link https://opendev.org/osf/interop/src/branch/master/next.json#L151-L16314:50
whoami-rajatrosmaita: IIRC these are only related to third party CI ?14:50
rosmaitano, kind of a separate issue14:50
rosmaitathis is the specification of what we think must be included for a cloud to be running OpenStack14:50
toskywhoami-rajat: guidelines/testing for interoperability of (vendored) openstack implementation14:50
rosmaitawe also get indirectly included in this nova capability:14:51
whoami-rajatok14:51
rosmaita#link https://opendev.org/osf/interop/src/branch/master/next.json#L13314:51
rosmaitaand here's where you can see what that capability "means", in terms of what tempest tests it matches to:14:51
rosmaita#link https://opendev.org/osf/interop/src/branch/master/next.json#L1103-L113014:52
rosmaitathe volumes-* capability definitions start here (and go on and on):14:52
eharneyi'm curious to know what tests exist for "volumes-v3-readonly"14:52
rosmaita#link https://opendev.org/osf/interop/src/branch/master/next.json#L237814:52
eharneyah, https://opendev.org/osf/interop/src/branch/master/next.json#L283014:53
eharneyyeah that test doesn't validate that readonly actually works14:53
rosmaitayeah, these will only be API tests14:54
rosmaitaby the way, that stuff you can't read in the description of all these tests says:14:54
rosmaita"This is being added as advisory to highlight the transitition from  v2 to v3."14:54
rosmaitai will put up a patch to remove that sentence14:54
rosmaita#action rosmaita interop patch removing transition v2->v3 language14:55
rosmaitaok, so i looked over our microversions14:55
rosmaita#link https://docs.openstack.org/cinder/latest/contributor/api_microversion_history.html14:55
rosmaitai only found two candidates14:55
rosmaitawell, actually 314:55
rosmaitamv 3.3, User Messages14:55
rosmaitai forgot to check whether there are existing tempest tests for ^^14:56
rosmaitabecause if they aren't we will need to write them14:56
rosmaitathe second is mv 5.55, 3.57, "New Transfer API"14:56
eharneyi don't recall any user message tests existing14:56
whoami-rajatfrom the quick find, i can't find anything saying message there14:56
rosmaitause /volume-transfers instead of /os-volume-transfer in the URL14:56
*** macz_ has joined #openstack-meeting-alt14:57
rosmaitai started looking into this one, but got lost in the tempest clients and couldn't figure out whether they are using the os- version or not when making the calls14:57
rosmaitabecause transfers actually are tested14:57
toskythe tests can set the specific microversion used by the tempest client (if that's the question)14:58
eharneya quick grep says that tempest is probably only testing the old one14:58
rosmaitaok, thanks14:58
rosmaitaso if we care about this, we can update the tempest tests first14:58
rosmaitaprobably worth doing anyway?14:59
eharneyyes14:59
rosmaitaso this is only an issue if we intend on removing the os-volume-transfer urls14:59
whoami-rajatrosmaita: what about default volume types? (I'm trying to write tests for it but lacking the endpoint support for the unique url)15:00
rosmaitawell, i don't know if we want to require that people make those accessible to end users15:00
rosmaitaactually , i guess we don't15:00
rosmaitaok, we are out of time, i will pick this up next week15:01
whoami-rajatthanks!15:01
rosmaitasorry about no open discussion, we spent all our time voting15:01
rosmaita#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:01
openstackMeeting ended Wed May  5 15:01:47 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2021/cinder.2021-05-05-14.00.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2021/cinder.2021-05-05-14.00.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2021/cinder.2021-05-05-14.00.log.html15:01
vishalmanchanda#startmeeting horizon15:01
openstackMeeting started Wed May  5 15:01:59 2021 UTC and is due to finish in 60 minutes.  The chair is vishalmanchanda. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: horizon)"15:02
openstackThe meeting name has been set to 'horizon'15:02
vishalmanchandahi anyone around for horizon meeting?15:03
tmazuro/15:04
rdopierao/15:04
vishalmanchandaLet's start the meeting.15:05
vishalmanchanda#topic Notices15:06
*** openstack changes topic to "Notices (Meeting topic: horizon)"15:06
vishalmanchandaI have no notices for this week.15:06
vishalmanchandatmazur: rdopiera : Do you have notice to announce or we can move to next topic?15:07
tmazurI have something for bug triage. Shall I wait or we can do it now?15:07
vishalmanchandawe can discuss it during open-discussion.15:08
tmazurOk15:08
vishalmanchanda#topic nodjs migration15:08
*** openstack changes topic to "nodjs migration (Meeting topic: horizon)"15:08
vishalmanchanda#link https://review.opendev.org/q/topic:%22migrate-to-nodejs14%22+(status:open%20OR%20status:merged)15:08
vishalmanchandaMost of the patches already have one +2,  Please review them so that we can move to next step i.e. drop nodejs10 jobs.15:09
vishalmanchandaI have also purposed a patch to governance to change runtime of nodejs to nodejs14 last week and it is already merged.15:10
vishalmanchanda#link https://review.opendev.org/c/openstack/governance/+/78830615:10
vishalmanchandaNote: horizon cores can also give +2 on plugins patches and approve them if it is already have +2 from plugin team.15:11
amotokinote that it is true for most plugins (not all)15:11
vishalmanchandayeah.15:12
vishalmanchandaok moving on to next topic15:13
vishalmanchanda#topic django migration15:13
*** openstack changes topic to "django migration (Meeting topic: horizon)"15:13
vishalmanchandano update on this topic.15:13
vishalmanchandadjango-pyscss owner didn't responded yet to my email.15:13
vishalmanchandaI will send a reminder after the meeting.15:14
vishalmanchandaamotoki: I have a question regarding this topic?15:14
amotokivishalmanchanda: I am confused with your question mark15:15
vishalmanchandaCan't we purpose patches to django-pyscss fork which is created by ivan to make it work with django3.x15:16
amotokivishalmanchanda: which fork do you mean?15:16
vishalmanchandaI wonder what we do if django-pyscss owner didn't respond15:17
amotokido you mean a github fork by Ivan?15:17
vishalmanchandahttps://github.com/e0ne/django-pyscss15:17
vishalmanchandaamotoki: yes15:17
amotokiI am not sure Ivan would like to be a new owner for the fork or not.15:18
rdopierait or switch to the django-sass-processor15:18
rdopierafork it or *15:18
vishalmanchandardopiera: have you tried django-sass-processor?15:18
rdopieravishalmanchanda: I started on it today, but didn't get it working yet15:19
vishalmanchandardopiera: ok.15:19
rdopieraone nice thing that it has is that you can add python functions to it15:19
amotokiIMHO at least we should not depend on a personal effort.15:19
amotokiif we fork the upstream as horizon team, we should do it as a team (not depending on a private github repo)15:20
amotokiunless someone would like to maintain it15:20
rdopierathat's why moving it under opendev might make sense15:20
amotokirdopiera: =115:21
amotoki+115:21
vishalmanchandardopiera: +1.15:21
amotokion the other hand, perhaps we don't want to maintain it for general purposes (even if we fork it under opendev) so it might be a transient solution15:23
rdopierawe would have to rename the fork anyways15:24
rdopierawe could as well rename it to something horizon-specific15:24
rdopierato discourage use by other projects15:24
amotokiyeah, that's true15:25
vishalmanchandaOk let's wait for one more week if django-pyscss owner responds otherwise we have to move forward either with horizon-specific django-pyscss fork or django-sass-processor.15:26
vishalmanchandamoving to next topic.15:27
vishalmanchanda#Support for Angular 1.8.x in Horizon15:28
vishalmanchanda#topic Support for Angular 1.8.x in Horizon15:28
*** openstack changes topic to "Support for Angular 1.8.x in Horizon (Meeting topic: horizon)"15:28
vishalmanchandaSome of the horizon angular panels (keypair and glance) are broken in Debian Bullseye distribution.15:28
vishalmanchandathere is mail about it on open-discuss15:29
vishalmanchanda#link http://lists.openstack.org/pipermail/openstack-discuss/2021-May/022243.html15:29
vishalmanchandaI have never used Debian so far.15:30
vishalmanchandaAs of now we use angular 1.5.8.0 https://github.com/openstack/horizon/blob/master/requirements.txt#L4415:30
rdopierashould we add <1.8 to our requirements for Angular?15:30
vishalmanchandardopiera: what if we update angular to 1.8.2?15:31
rdopierathat would be great, however, I have no idea how to do it and how much work it would be15:33
tmazurI can see some breaking changes but not sure yet if we are affected or not15:34
vishalmanchandardopiera: if we add <1.8 to our requirements for Angular does that fix the issue?15:35
rdopieravishalmanchanda: it moves the problem from us to the Debian maintainers ;-)15:36
rdopierabut no, it does not fix it15:37
vishalmanchandardopiera: I have no idea about that.15:37
vishalmanchandaUpdating angular to 1.8.2 requires a lot of code changes.15:38
rdopierajust ignore my suggestion, we are in the best position to fix it15:39
vishalmanchandaI have started doing that in the morning but I am able to do it only for 2 files taking reference from old patches.15:39
vishalmanchandardopiera: what if I pushed an initial patch to upgrade angular-js to 1.8.215:43
vishalmanchandardopiera: Could you help me with reviews?15:43
rdopieravishalmanchanda: I still haven't learned Angular15:44
tmazurI definitely can :)15:44
vishalmanchandatmazur: thanks.15:45
vishalmanchandaI am also not an expert on angular but I will push some code for the upgrade taking reference from old patches.15:46
tmazurYeah, let's see how it breaks everything15:47
tmazur(I hope not though)15:47
vishalmanchandatmazur: 🙂15:47
vishalmanchandaI am sure it will break many panels15:48
vishalmanchandaBut Let's see.15:48
vishalmanchandameanwhile, I will report a new bug for this upgarde so it's easy to track.15:50
vishalmanchanda#topic open-discussion15:50
*** openstack changes topic to "open-discussion (Meeting topic: horizon)"15:50
tmazurSo, speaking of bugs15:51
tmazurHere's an etherpad page for triage. https://etherpad.opendev.org/p/horizon-bug-triage15:51
tmazurTo not overwhelm us, I took a look at the first 1015:52
vishalmanchandatmazur: great work:)15:53
tmazurTwo of the newest bugs seemed pretty simple so I've commited patches. Also the one about release notes needs reviews.15:53
amotokiwhich order? latest ones first?15:54
tmazurOne appeared to be a duplicate, two are about system scope, so I've marked them as high priority and triaged15:54
tmazurYes, latest ones first.15:54
rdopierathe one about novaclient logs is fixed and merged, not sure if we want backports15:54
tmazurSince we have a lot of them, I've decided to start from the top now. Later I am planning to look through the oldest15:55
tmazurActually, I've closed some old ones too, just not added them here, again, to not overwhelm us.15:55
ikaniasregarding automation, are we considering moving from Selenium to Cypress.io in the future?15:55
amotokiapart from bug triage, I have another topic on stable branch EOL. Discussion on otaca and pike EOL started. Who would like to maintain these in horizon?15:55
amotokitmazur: you can assign bugs on system scope to me.15:56
tmazuramotoki: ok, thanks!15:57
amotokirdopiera: tmazur: do you still need to have ocata and pike branches?15:57
tmazurSo essentially: please review the ones that are on review, please take a look at ones that need confirmation. Feel free to add your notes!15:57
rdopieraamotoki: we will drop support for osp13 later this year, and only support osp16+ since, so we don't need anything older than Train15:58
amotokirdopiera: which stable branch corresponds to osp13?15:59
rdopieraQueens15:59
amotokiso, you don't see a block for ocata and pike EOL?16:00
amotokiat least from osp perspective?16:00
rdopieracorrect16:00
amotokivishalmanchanda is our PTL and release liaison, so perhaps it is in his radar.16:00
vishalmanchandaguys we are out of time.16:00
vishalmanchandalet's discuss it in horizon channel.16:01
vishalmanchandaThanks everyone for your contribution.16:01
tmazurThanks everyone!16:01
vishalmanchanda#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:01
openstackMeeting ended Wed May  5 16:01:44 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2021/horizon.2021-05-05-15.01.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2021/horizon.2021-05-05-15.01.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2021/horizon.2021-05-05-15.01.log.html16:01
*** rosmaita has left #openstack-meeting-alt16:02
*** rdopiera has quit IRC16:32
*** gyee has joined #openstack-meeting-alt16:33
*** dviroel|nho is now known as dviroel16:38
*** zzzeek has joined #openstack-meeting-alt16:45
*** zzzeek has quit IRC16:50
*** zzzeek has joined #openstack-meeting-alt16:52
*** enriquetaso has quit IRC17:02
*** enriquetaso has joined #openstack-meeting-alt17:02
*** zzzeek has quit IRC17:04
*** jamesmcarthur_ has joined #openstack-meeting-alt17:08
*** zzzeek has joined #openstack-meeting-alt17:08
*** jamesmcarthur has quit IRC17:11
*** jamesmcarthur_ has quit IRC17:23
*** ralonsoh has quit IRC17:36
*** knikolla has joined #openstack-meeting-alt18:10
*** e0ne has quit IRC18:20
*** vishalmanchanda has quit IRC18:46
*** Dantalion has quit IRC18:47
*** Dantalion has joined #openstack-meeting-alt18:48
*** Adri2000 has joined #openstack-meeting-alt18:52
*** e0ne has joined #openstack-meeting-alt19:01
*** e0ne has quit IRC19:22
*** jamesmcarthur has joined #openstack-meeting-alt19:24
*** jamesmcarthur has quit IRC19:29
*** e0ne has joined #openstack-meeting-alt19:38
*** slaweq has quit IRC20:10
*** e0ne has quit IRC20:26
*** e0ne has joined #openstack-meeting-alt20:38
*** jamesmcarthur has joined #openstack-meeting-alt20:41
*** jamesmcarthur has quit IRC20:54
*** jamesmcarthur has joined #openstack-meeting-alt20:54
*** jamesmcarthur has quit IRC21:12
*** jamesmcarthur has joined #openstack-meeting-alt21:13
*** e0ne has quit IRC21:31
*** jamesmcarthur has quit IRC21:52
*** jamesmcarthur has joined #openstack-meeting-alt22:06
*** jamesmcarthur has quit IRC22:10
*** jamesmcarthur has joined #openstack-meeting-alt22:14
*** reddy has quit IRC22:21
*** jamesmcarthur has quit IRC22:29
*** jamesmcarthur has joined #openstack-meeting-alt22:30
*** miniroy has quit IRC22:32
*** gyee has quit IRC22:41
*** tosky has quit IRC23:03
*** rcernin has joined #openstack-meeting-alt23:04
*** macz_ has quit IRC23:06
*** jamesmcarthur has quit IRC23:16
*** tmazur has quit IRC23:18
*** jamesmcarthur has joined #openstack-meeting-alt23:36
*** jamesmcarthur has quit IRC23:45
*** jamesmcarthur has joined #openstack-meeting-alt23:47

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