Wednesday, 2021-03-10

*** vishalmanchanda has quit IRC00:05
*** jamesmcarthur has quit IRC00:21
*** jamesmcarthur has joined #openstack-meeting-alt00:22
*** jamesmcarthur has quit IRC00:30
*** jamesmcarthur has joined #openstack-meeting-alt00:35
*** jamesmcarthur has quit IRC00:35
*** tosky has quit IRC00:36
*** jinyuanliu has quit IRC01:03
*** macz_ has joined #openstack-meeting-alt01:04
*** jinyuanliu has joined #openstack-meeting-alt01:04
*** jamesmcarthur has joined #openstack-meeting-alt01:08
*** macz_ has quit IRC01:09
*** subbareddy has quit IRC01:11
*** jamesmcarthur has quit IRC01:17
*** jamesmcarthur has joined #openstack-meeting-alt01:19
*** jamesmcarthur has quit IRC01:23
*** jamesmcarthur has joined #openstack-meeting-alt01:23
*** jamesmcarthur has quit IRC01:26
*** jamesmcarthur has joined #openstack-meeting-alt01:27
*** dviroel_ has joined #openstack-meeting-alt01:31
*** jamesmcarthur has quit IRC01:32
*** jamesmcarthur has joined #openstack-meeting-alt01:33
*** dviroel has quit IRC01:38
*** ttx has quit IRC01:38
*** Adri2000 has quit IRC01:39
*** dviroel_ is now known as dviroel01:39
*** jamesmcarthur has quit IRC01:39
*** jamesmcarthur has joined #openstack-meeting-alt01:39
*** macz_ has joined #openstack-meeting-alt01:40
*** macz_ has quit IRC01:45
*** jamesmcarthur has quit IRC01:47
*** ttx has joined #openstack-meeting-alt01:47
*** macz_ has joined #openstack-meeting-alt02:22
*** macz_ has quit IRC02:27
*** jamesmcarthur has joined #openstack-meeting-alt03:12
*** jamesmcarthur has quit IRC03:13
*** jamesmcarthur has joined #openstack-meeting-alt03:13
*** jamesmcarthur has quit IRC03:13
*** sangeet has quit IRC03:20
*** sangeet has joined #openstack-meeting-alt03:20
*** jamesmcarthur has joined #openstack-meeting-alt03:27
*** jamesmcarthur has quit IRC03:33
*** jinyuanliu has quit IRC03:34
*** jamesmcarthur has joined #openstack-meeting-alt03:34
*** jinyuanliu has joined #openstack-meeting-alt03:34
*** jamesmcarthur has quit IRC03:38
*** jamesmcarthur has joined #openstack-meeting-alt03:52
*** jamesmcarthur has quit IRC03:57
*** jamesmcarthur has joined #openstack-meeting-alt03:58
*** gyee has quit IRC03:58
*** jamesmcarthur has quit IRC04:05
*** jamesmcarthur has joined #openstack-meeting-alt04:07
*** macz_ has joined #openstack-meeting-alt04:23
*** knomura has joined #openstack-meeting-alt04:27
*** macz_ has quit IRC04:27
*** carloss has quit IRC04:29
*** jamesmcarthur has quit IRC04:44
*** sangeet has quit IRC04:50
*** knomura has quit IRC04:53
*** vishalmanchanda has joined #openstack-meeting-alt04:59
*** ajitha has joined #openstack-meeting-alt05:11
*** sangeet has joined #openstack-meeting-alt05:22
*** jamesmcarthur has joined #openstack-meeting-alt05:27
*** jamesmcarthur has quit IRC05:31
*** macz_ has joined #openstack-meeting-alt05:50
*** macz_ has quit IRC05:55
*** whoami-rajat has joined #openstack-meeting-alt06:23
*** e0ne has joined #openstack-meeting-alt06:31
*** e0ne has quit IRC06:31
*** enriquetaso has quit IRC06:43
*** jamesmcarthur has joined #openstack-meeting-alt06:49
*** jamesmcarthur has quit IRC06:50
*** knomura has joined #openstack-meeting-alt07:05
*** knomura has quit IRC07:09
*** LinPeiWen has quit IRC07:13
*** ralonsoh has joined #openstack-meeting-alt07:21
*** ajitha has quit IRC07:21
*** e0ne has joined #openstack-meeting-alt07:22
*** e0ne has quit IRC07:27
*** LinPeiWen has joined #openstack-meeting-alt07:32
*** slaweq has quit IRC07:42
*** slaweq has joined #openstack-meeting-alt07:46
*** slaweq has quit IRC07:52
*** slaweq has joined #openstack-meeting-alt07:54
*** rdopiera has joined #openstack-meeting-alt07:56
*** lpetrut has joined #openstack-meeting-alt08:06
*** sfernand has quit IRC08:36
*** tosky has joined #openstack-meeting-alt08:46
*** jamesmcarthur has joined #openstack-meeting-alt08:50
*** jamesmcarthur has quit IRC08:55
*** LinPeiWen has quit IRC09:26
*** rcernin has quit IRC09:54
*** knomura has joined #openstack-meeting-alt10:10
*** knomura has quit IRC10:14
*** e0ne has joined #openstack-meeting-alt10:35
*** carloss has joined #openstack-meeting-alt10:39
*** LinPeiWen has joined #openstack-meeting-alt10:44
*** macz_ has joined #openstack-meeting-alt11:19
*** macz_ has quit IRC11:24
*** sangeet has quit IRC11:47
*** macz_ has joined #openstack-meeting-alt12:00
*** macz_ has quit IRC12:06
*** sangeet has joined #openstack-meeting-alt13:12
*** sangeet has quit IRC13:23
*** ajitha has joined #openstack-meeting-alt13:24
*** enriquetaso has joined #openstack-meeting-alt13:46
*** rosmaita has joined #openstack-meeting-alt14:00
rosmaita#startmeeting cinder14:01
openstackMeeting started Wed Mar 10 14:01:13 2021 UTC and is due to finish in 60 minutes.  The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: cinder)"14:01
openstackThe meeting name has been set to 'cinder'14:01
jungleboyjo/14:01
almir-okatoo/14:01
whoami-rajatHi14:02
e0nehi14:02
eharneyhi14:02
*** TusharTgite has joined #openstack-meeting-alt14:02
toskyhi14:03
TusharTgitehi14:03
enriquetasohi14:03
rosmaitahello everyone14:05
geguileohi!14:05
rosmaita#link https://etherpad.openstack.org/p/cinder-wallaby-meetings14:05
rosmaita#topic announcements14:05
*** openstack changes topic to "announcements (Meeting topic: cinder)"14:05
*** sfernand has joined #openstack-meeting-alt14:05
rosmaitathe Xena PTG has been scheduled14:06
rosmaita19-23 April14:06
rosmaitait's free to attend but you need to register14:06
rosmaita#link http://lists.openstack.org/pipermail/openstack-discuss/2021-March/020778.html14:06
rosmaitainfo ^^14:06
rosmaitawe need to start planning14:06
rosmaita#link https://etherpad.opendev.org/p/xena-ptg-cinder-planning14:07
*** tmazur has joined #openstack-meeting-alt14:07
rosmaitafirst thing is to decide what times we will meet14:07
rosmaitaand for how long14:07
rosmaitai think we should stick with what we've done for the past virtual PTGs14:07
e0ne+114:07
enriquetaso+114:07
jungleboyjrosmaita:  ++14:07
rosmaitabut, i am open to ideas to accommodate people who those times don't work for14:08
rosmaitaso if the stated times are bad for you, let me know either on the etherpad or in irc14:08
rosmaitathe other question is about how long to meet each day14:08
rosmaitawe've been doing 3 hour blocks, but could do 414:09
rosmaitai think 3 hours has been working ok14:09
e0ne3 hours sounds better to me. It's easier to dedicate a time14:10
jungleboyjrosmaita:  ++14:10
geguileo3 hours sounds good14:10
whoami-rajat3 hour works for me14:11
rosmaitaok, guess there's a consensus, we will stick with 3 hours14:11
rosmaitathat was easy!14:11
rosmaitanext item14:11
jungleboyj:-)14:11
rosmaitaos-brick 4.3.0 has been released and the stable/wallaby branch has been cut14:11
rosmaitayou may have seen a complaint on the ML about the aggressive update to requirements14:12
rosmaitanot sure there's anything we can do about that now14:12
rosmaitaor if i want to, anyway14:12
rosmaitakey point for this meeting is that if you find a bug in os-brick 4.3.014:12
rosmaitabugfixes must be proposed to master and backported to stable/wallaby14:13
whoami-rajatadding to it, we've similar bumps in all stable releases14:13
*** jrollen is now known as jroll14:13
rosmaitaso os-brick master is now xena development14:13
rosmaitawelcome to the future14:13
jungleboyj:-)14:14
*** felipe_rodrigues has joined #openstack-meeting-alt14:14
rosmaitaok, this week is cinderclient release and the feature freeze14:14
e0ne:)14:14
rosmaitaalso requirements freeze14:14
jungleboyjWhere does the time go?14:14
rosmaitano kidding14:14
rosmaitaok, as far as feature freeze goes14:15
rosmaitawe are working from the blueprints in launchpad for wallaby14:15
rosmaita#link https://blueprints.launchpad.net/cinder/wallaby14:15
rosmaitaso, if you have a feature listed in there, it will be really helpful if you make sure links to your patches are in the "Whiteboard" section of you BP14:16
rosmaita*your BP14:16
rosmaitaexcept for the cinderclient patches we are about to discuss, those are the review top priority for the next few days14:17
rosmaita#topic cinderclient release14:18
*** openstack changes topic to "cinderclient release (Meeting topic: cinder)"14:18
rosmaitai have made a handy etherpad14:18
rosmaita#link https://etherpad.opendev.org/p/wallaby-cinderclient14:18
rosmaitathe brick extension just has one open easy maintenance patch14:18
rosmaitacinderclient has a bunch of maintenance patches14:19
rosmaitashould be quick reviews14:19
rosmaitaimportant patch is the version bump14:20
rosmaitai will reach out to cores personally once the release notes and requirements patches are ready14:21
rosmaitalooking at the open reviews14:21
rosmaita#link https://review.opendev.org/q/project:openstack/python-cinderclient+status:open14:21
rosmaitai don't see anything else other than maybe the client cert patch14:21
rosmaitabut i haven't looked at/thought about it14:22
rosmaitaany opinions?14:22
eharneyit seems kind of risky to slip in at the last minute to me14:22
*** lyarwood has joined #openstack-meeting-alt14:23
rosmaitathat is my thought14:23
rosmaitawe will push that one to xena14:24
eharneypresumably work would be happening in other clients/services for mtls too if this is of interest, we should see what14:24
jungleboyjrosmaita: ++ Good call.14:24
rosmaitaif it turns out to be important, we can do a very early xena release that will be compatible with wallaby14:24
jungleboyjI started looking at it yesterday and had the same thought.14:24
rosmaitaok, thanks14:25
rosmaitayou will notice the absence of a v2-support-removal patch14:25
rosmaitai am in the middle of one, but i am not going to try to rush it in14:25
rosmaitai don't think we'll be removing v2 from cinder this cycle either14:26
rosmaitabut, i think it should be top priority for xena14:26
rosmaitaboth client and cinder14:26
rosmaitawe will organize it at the PTG14:26
rosmaitalast item14:27
rosmaitalooks like i need to put together an etherpad of the cinder feature reviews14:27
rosmaitai will do that after the meeting14:27
rosmaitaasking people to go to launchpad and then find the reviews doesn't seem to be working14:28
*** jinyuanliu has quit IRC14:28
rosmaitai will send the link to the ML and #openstack-cinder when it's ready14:28
*** jinyuanliu has joined #openstack-meeting-alt14:28
rosmaitaonly items on that list will be eligible for feature freeze14:28
rosmaitaso watch for it and check to make sure your reviews are on it14:28
whoami-rajatrosmaita: one ques, are driver features also included in the BPs?14:29
rosmaitawhoami-rajat: yes, they are supposed to be14:29
rosmaitathat's the "driver features declaration" deadline on the release schedule14:29
whoami-rajatthen i think zadara has one feature that they haven't created a bp for14:29
whoami-rajathttps://review.opendev.org/c/openstack/cinder/+/77446314:29
rosmaitai will have to check, i thought there was a bp for that14:30
whoami-rajatthen i might've missed it, my bad14:30
rosmaitaor i did14:30
rosmaitabut we've discussed that patch at a previous meeting, so i think it should be included as a wallaby feature14:31
whoami-rajati don't find anything with zadara here https://blueprints.launchpad.net/cinder/wallaby14:31
rosmaitaok, i will fix that14:32
whoami-rajatthanks14:33
rosmaitaone note to people with driver patches14:33
rosmaitasome of the CIs are not responding automatically14:33
rosmaitaso please check (a) your CI, and (b) run it on your patch if you have to14:34
rosmaitaa lot of people prioritize reviews by whether the patch is passing its own CI14:34
rosmaitaso make sure the info is on the review for everyone to see14:34
rosmaitaalso14:34
rosmaitaplease follow the release note format so we don't waste cycles re-submitting14:35
rosmaita#link https://docs.openstack.org/cinder/latest/contributor/releasenotes.html14:35
sfernandack14:35
rosmaitathanks!14:35
rosmaitaok, that's all from me14:35
rosmaita#topic Cinder backup - upload chunk in parallel (ThreadPoolExecutor)?14:36
*** openstack changes topic to "Cinder backup - upload chunk in parallel (ThreadPoolExecutor)? (Meeting topic: cinder)"14:36
hemnaheh14:36
rosmaitai think this was left over from last week, not sure who's item it is14:36
hemnais there a review for it?14:36
rosmaitanot sure, but i have one for you hemna: https://review.opendev.org/c/openstack/rbd-iscsi-client/+/77474814:37
rosmaitaok, we will postpone this topic14:37
hemnaok cool thanks.14:37
eharneyhttps://review.opendev.org/c/openstack/cinder/+/779233  i think14:37
hemnawe have been seeing some perf issues with chunked backup driver and are looking into parallelism as well14:37
hemna2Tb volume backups take like 20+ hours :(14:38
jungleboyj:-(14:38
eharneydoes parallelism fix that?14:38
hemnayah, I think we are cpu bound14:39
e0nethe patch looks good but we need to be careful, it could affect several drivers14:39
rosmaitaok, then i don't want to rush it in before FF14:39
eharneyif nothing else that patch needs an option added for # of threads IMO, also needs careful review14:39
rosmaitalet's push it to Xena14:39
hemnanah, better be safe14:40
rosmaitaeharney: ++14:40
jungleboyj++14:40
rosmaitaiirc, swift will throttle writes to a single container, so it can be counterproductive if you're not careful14:40
rosmaitaok, moving along14:40
rosmaita#topic random issues with tgt, breakages in some jobs, proposal to switch the default  backend to lioadm14:40
*** openstack changes topic to "random issues with tgt, breakages in some jobs, proposal to switch the default  backend to lioadm (Meeting topic: cinder)"14:40
rosmaitatosky: that's you14:40
* lyarwood is also here \o14:41
toskyI'm merely the messenger; lyarwood could't attend, but you can see the report in the etherpad14:41
toskyoh14:41
* tosky hides14:41
rosmaitaok, thanks14:41
lyarwoodhey sorry childcare means I wasn't sure if I'd make it14:41
rosmaitaeveryone look at the etherpad14:41
rosmaitaoh, wait14:41
rosmaitaok lyarwood you have the floor14:41
toskyI was going to say "the proposal is to switch the default to lioadm in ubuntu too"14:41
lyarwoodthanks, so yeah lots of detail in the pad14:42
lyarwoodbut tosky is correct that's my current proposal given the failures I've seen with encrypted volume tests14:42
lyarwoodI'm still unable to reproduce issues we've seen in the nova-live-migration job when detaching volumes that I think is related to this14:42
lyarwoodusing lioadm on Bionic doesn't appear possible so we will need to pin the grenade jobs to tgtadm14:43
lyarwoodtosky: to reply to your point in the pad AFAICT the grenade job that failed was using Bionic14:44
eharneyi think lio should work on bionic14:45
eharneyat least, not sure why it wouldn't14:45
lyarwoodI assumed so but python3-rtslib-fb fails to install with `Failed to start rtslib-fb-targetctl.service: Unit rtslib-fb-targetctl.service is not loaded`14:45
eharneyhuh, i'll leave figuring out that for later14:46
lyarwoodanyway appreciate there's lots of context to load here so I'm just looking for any reason not to do this after M314:47
toskylyarwood: uhm, that's strange, as victoria is focal already (it was one of the goals), so the starting point for victoria should be focal14:47
toskylyarwood: I will ask gmann14:47
jungleboyjtosky:  Yeah, I thought we had moved to focal.14:48
eharneywell, lio should in general be a better solution, but i am concerned that our lio-barbican gate job fails a lot, possibly due to a bug in the target code14:48
rosmaitai am worried about doing this as we approach RC time14:48
hemnarosmaita+114:48
eharneyso if we start running it more places we may have to get a lot more engaged on figuring out what is going on there than we have been14:48
lyarwoodso the flip side is that we have a huge uptick in volume detach failures across the gate14:48
rosmaitayes, if our lio-barbican job is a guide, lio is not going to increase stability14:48
lyarwoodkk I wasn't aware of the lioadm job being unstable14:49
lyarwoodbut to finish my point14:49
lyarwoodif I can reproduce the detach issue and show it's related to the use of tgtadm then I think the move to lioadm would still be valid ahead of rc14:49
lyarwoodthe encrypted volume failure I've reproduced thus far hasn't caused anywhere near as many failures14:50
toskyand regardless of the decision, https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/779697 makes sense anyway on its own14:51
lyarwoodyeah correct14:51
rosmaitaok, well looking at the build history, mabye that job isn't as awful as experience indicates14:52
rosmaitahttps://zuul.opendev.org/t/openstack/builds?job_name=cinder-tempest-plugin-lvm-lio-barbican&project=openstack%2Fcinder14:52
rosmaitaok, let's revisit this next week14:52
rosmaitathanks lyarwood14:52
jungleboyjThat still looks like quite a few failures.14:52
lyarwoodack thanks rosmaita14:52
rosmaita#topic bug report future14:53
*** openstack changes topic to "bug report future (Meeting topic: cinder)"14:53
rosmaitaenriquetaso: that's you14:53
enriquetasoo/14:53
enriquetasoIn the last weekly meetings we were not able to cover all the topics proposed on the agenda. For this reason and considering the productivity of discussing the bugs of the week with the team, I would like to propose an additional mini meeting to this one. The new meeting would begin exactly after this one, it would last half an hour and it would be on the specific channel of cinder.14:53
rosmaitaenriquetaso: ++14:53
enriquetasoI have not sent an email to the mailing list yet, but if it's okay with you, I'll do it this week.14:53
enriquetaso\o/14:53
rosmaitado we want to start today?14:53
enriquetasoyes14:53
rosmaitaworks for me14:53
rosmaitaany objections?14:54
jungleboyjMakes sense.14:54
sfernandnope14:54
jungleboyjSince we often use this whole time.14:54
sfernandsounds good14:54
rosmaitagreat, let's move along then.  thanks, sofia14:54
rosmaita#topic stable branch updates14:54
*** openstack changes topic to "stable branch updates (Meeting topic: cinder)"14:54
rosmaitawhoami-rajat: you have the floor14:54
whoami-rajatHi14:54
whoami-rajatas mentioned in the etherpad, victoria is released \o/14:55
whoami-rajatussuri release patch is up14:55
tosky\o/14:55
whoami-rajatbut we still have unmerged patches in train, specifically cinder (i guess 7 patches?) and 1 in os-brick14:55
rosmaitaok, i think we will have to postpone train release until later next week14:56
whoami-rajati will update the tracker with all unmerged patches but for time being please review https://review.opendev.org/#/q/project:openstack/cinder+status:open+branch:stable/train14:56
rosmaitaneed all reviewers focused on cinderclient today and features for the rest of the week14:56
*** miniroy has joined #openstack-meeting-alt14:56
whoami-rajatrosmaita: yep, makes sense14:56
rosmaitaok, thanks for organizing this14:56
enriquetaso++14:57
whoami-rajatnp14:57
rosmaita#topic open discussion14:57
*** openstack changes topic to "open discussion (Meeting topic: cinder)"14:57
rosmaitareminder: the cinder meeting is in UTC14:57
rosmaitaso for some people in north america, the local time will be different next week14:57
rosmaitaand europe goes to summer time at the end of the month14:57
rosmaitaso if you show up next week and no one is there, check the time14:58
eharneyhttps://review.opendev.org/c/openstack/cinder/+/777470   could use another +2, have had folks waiting on this fix for a bit14:58
rosmaita:)14:58
jungleboyjOh, does DST happen this weekend?14:58
hemnayes afaik14:58
hemnadoes anyone understand the policies code?14:59
jungleboyjrosmaita:  Thanks for letting me know.14:59
rosmaitadepends on what you mean by "understand"14:59
eharneyi think some people have been doing some work on policies lately14:59
hemnaheh14:59
hemnaso, I'm looking into adding https://review.opendev.org/c/openstack/cinder/+/77954114:59
hemnawhich allows admins to see all the volume_admin_metadata15:00
*** jamesmcarthur has joined #openstack-meeting-alt15:00
rosmaitajust noticed we are out of time15:01
rosmaitabug meeting in cinder channel now15:01
hemnais there a way to add that policy but make it optionally work, so that the current default of not showing all admin_metadata can stay in place15:01
rosmaita#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:01
openstackMeeting ended Wed Mar 10 15:01:18 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-03-10-14.01.html15:01
jungleboyjThanks!15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2021/cinder.2021-03-10-14.01.txt15:01
whoami-rajatthanks!15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2021/cinder.2021-03-10-14.01.log.html15:01
*** TusharTgite has left #openstack-meeting-alt15:01
e0ne#startmeeting horizon15:01
openstackMeeting started Wed Mar 10 15:01:47 2021 UTC and is due to finish in 60 minutes.  The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: horizon)"15:01
openstackThe meeting name has been set to 'horizon'15:01
vishalmanchandahi15:02
rdopierahello15:02
tmazuro/15:02
*** knomura has joined #openstack-meeting-alt15:05
*** zzzeek has quit IRC15:05
e0nehi15:06
e0nelet's start. I hope amotoki will join us soon15:06
*** zzzeek has joined #openstack-meeting-alt15:06
* e0ne #topic Notices15:07
e0neXena PTG has been scheduled on 19-23 of April15:08
e0neregistration is free15:08
e0ne#link http://lists.openstack.org/pipermail/openstack-discuss/2021-March/020778.html15:08
*** ikanias has joined #openstack-meeting-alt15:08
e0neI hope everybody will join and we'll have a good number of conversations15:09
vishalmanchandaagain virtual ptg:(15:09
*** Adri2000 has joined #openstack-meeting-alt15:09
e0nevishalmanchanda: covid-19 situation is pretty bad still :(15:09
vishalmanchandayeah.......15:10
*** knomura has quit IRC15:10
e0necongrats vishalmanchanda as our new PTL for Xena release!15:10
e0ne#link https://governance.openstack.org/election/15:11
vishalmanchandahehe thanks:)15:11
e0nevishalmanchanda: thanks for volunteering for being a PTL15:11
vishalmanchandalooking forward to it.15:12
vishalmanchandaLet's see how it goes.15:12
e0neeverything will be good, I'm sure :)15:13
e0nevishalmanchanda: don't worry15:13
rdopieraI'm sure you will smash it15:13
vishalmanchandaI hope you guys will continue to contribute in next cycle.15:14
e0nevishalmanchanda: +115:14
tmazurSure!15:14
e0nelet's finish some Wallaby businesses before15:15
e0ne#link https://releases.openstack.org/wallaby/schedule.html15:15
e0nethis week is a feature freeze and soft string freeze15:15
e0neafter this milestone, only bugfixes are allowed15:16
amotokisorry for late. I watched two cycling races in parallel and didn't notice the time :p15:16
e0netechnically, horizon uses other release model, but it's good to follow these milestones15:17
amotokifolloing the feature freeze sounds fair.15:18
e0neamotoki: it's not fair that burton us cup cancelled but cycling championships are going :(15:20
amotokie0ne: hehe15:20
e0nedo we have any unmerged feature proposal?15:21
amotokihopefully most tnings can recover in either of new or exsiting sways :)15:22
amotokis/sways/ways/15:22
tmazurthe one about autofocus on login screen15:22
e0neI didn't find anything in the list https://review.opendev.org/q/project:openstack/horizon+status:open #link15:22
tmazurI've added the discussion of it to agenda15:23
e0netmazur: I prefer to treat it as bugfix15:23
tmazure0ne: even if we agree to add a new setting?15:23
e0neoh... I missed it15:23
rdopieraone more reason to not add a new setting ;-)15:24
tmazurhaha15:24
amotokilet's discuss it in a dedicate topic anyway15:24
tmazuryes15:24
e0neamotoki: +115:24
e0neanyway, that's all updates from my side15:24
amotokione thing from me15:25
vishalmanchandae0ne: we also have to add Wallaby Cycle Highlights by this week.15:25
vishalmanchanda#link http://lists.openstack.org/pipermail/openstack-discuss/2021-March/020900.html15:25
e0nevishalmanchanda: thanks for a reminder. I'll go via release notes and propose a patch today15:26
vishalmanchandae0ne: thanks.15:26
ikaniasI think that putting the domain field at the top is wrong15:26
ikaniasIt should be below the password15:26
vishalmanchandaamotoki: please continue.15:26
ikaniasfield15:26
ikaniasMany web sites do that that way15:26
amotokiikanias: we will discuss it later in this meeting15:26
ikaniassure15:26
amotokiikanias: we are in the "Notices" section15:27
amotokiRenaming Chinese locales landed successfully. I confirmed all translation jobs worked as expected.15:27
amotokiI hope all plugins can cut a release including it.15:27
e0neamotoki: awesome!15:27
vishalmanchandaamotoki: great.15:27
rdopierathank you for handling that15:27
amotokifreezer-web-ui is the only plugin which does not merge it.15:27
amotokibut what we can do is just to wait for them15:27
amotokimost plugins landed translation imports, so it would be no problme.15:28
amotokithat's all from me.15:28
e0neamotoki: thanks a lot for driving this effort15:28
amotokiyw15:28
e0nelet's move to the next topic15:29
e0neI don't know who added it but I like it15:30
rdopierait was me15:30
e0ne#topic Promoting Tatiana to core.15:30
*** openstack changes topic to "Promoting Tatiana to core. (Meeting topic: horizon)"15:30
rdopieraI would like to propose tmazur as a core reviewer15:30
rdopieraShe has a long history with the horizon project15:31
vishalmanchandaIt would be great to have tatina in our core-team:)15:31
e0ne#link https://www.stackalytics.io/?module=horizon-group&metric=commits&user_id=tmazur15:31
e0ne#link https://www.stackalytics.io/?module=horizon-group&user_id=tmazur15:32
e0newill it be a double-horizon-core or just a second time horizon-core?15:32
tmazurhaha15:32
tmazurI don't know :)15:33
rdopieratmazur: oof, you still count as Mirantis!15:33
rdopierain stackalytics15:33
vishalmanchanda🙂15:33
amotokisurprising....15:33
tmazurYesss, I remember there were some difficulties with affiliation changing15:33
amotokitmazur: you can push your info to the stackalytics repo15:33
e0nerdopiera: me too...15:34
tmazurI guess I even should contact someone directly15:34
rdopieranot like it's critically important15:34
vishalmanchandahttps://review.opendev.org/q/project:x%252Fstackalytics+status:open15:34
tmazurrdopiera: definitely15:35
amotokiaside from that, I am fine to add her to the core team. it would be a nice improvement to cover more areas deeply. She is familiar with angular area.15:36
e0netmazur: AFAIR, there was some json file in the repo with mapping. I'll let you know once I find it15:36
e0neI need to do the same15:36
tmazure0ne: ok, thanks!15:36
tmazurAnd thanks everyone for promoting me!15:37
amotokitmazur: I also have experience on stackalitics thing. we can help you.15:37
ikaniastmazur: Congrats!15:37
rdopierawe have the technology ;-)15:37
amotokiit looks like we have a consensus.15:37
tmazurI will proceed with doing my best for Horizon ;p15:37
e0neI think we've got an agreement and there is no need to make a voting in a mailing list15:37
tmazuramotoki: thanks!15:37
amotokido you need to nominate her officially in the mailing list or is it an apporval?15:37
amotokie0ne: you are faster than me.15:38
e0neamotoki: I'll send a mail to the ML just to make it a bit more official :)15:38
vishalmanchandaIMO It is better to announce on mail chain as well as per openstack docs.15:38
e0nebut since all cores agreed, we don't need a voting15:39
e0neof course, rdopiera can change his vote ;)15:39
amotokii think the notice would be fine15:39
e0neamotoki: +115:39
e0netmazur: welcome back to the team!15:40
tmazurWoohoo! Happy to be back! :D15:40
vishalmanchandatmazur: Congrats:)15:40
amotokitmazur: welcome :)15:40
e0ne#topic Login page autofocus discussion15:41
*** openstack changes topic to "Login page autofocus discussion (Meeting topic: horizon)"15:41
e0ne#link https://review.opendev.org/c/openstack/horizon/+/77769015:42
tmazurSo we have a few options here15:42
e0neI don't really want to introduce a new config option for it15:43
tmazurTo add a new setting to shift it wherever we want, to pick the Domain field only when it's empty and to shift the Domain field to the bottom15:43
*** lpetrut has quit IRC15:44
amotokiat the staring point, the current behavior is to focus on "domain" field even if "domain" field is filled with the value used previously.15:44
ikaniasI think that putting the domain field at the top is wrong from UX point of view15:44
tmazurI introduced the new setting solution but after a discussion we had with rdopiera and ikanias it seems not a good solution now15:44
amotokiikanias: why do you think so?15:45
rdopieraikanias: do you have any examples of other services that put the username first?15:45
amotokiikanias: username is unque inside a domain15:45
ikaniasIn all my previous apps I worked for the domain was always last to appear15:45
ikaniasI will get examples if you wish15:45
amotokia used ID can determined as a combination of username and domain name (or ID).15:46
amotokiconsidering this, putting "password" field between "user" and "domain" is a bit confusing to me15:46
amotokibut others can have other opinions.15:46
tmazuramotoki: not between, after the password15:47
tmazuramotoki: oops, please ignore15:47
amotokitmazur: np15:47
ikaniasamotoki: Username and password ahould always be one below the other IMO15:47
rdopieraamotoki: but that is the administrator's point of view, the users themselves don't think about themselves as belonging to a domain15:47
rdopieraamotoki: it's more like selecting where to log in for them15:49
rdopierawhere they want to go15:49
rdopieraespecially since often they may have logins in multiple domains15:49
ikaniasamotoki: I think we also need to be aligned to the rest of the web apps that exist15:49
e0neikanias: good point. do you have examples by the hand?15:50
amotokiI remembers that windows login page has "domain" selection at the bottom.15:50
ikaniase0ne: currently no but i will get you15:50
e0neikanias: it will be useful15:51
ikaniase0ne: sure will work on it after the meeting15:51
e0nefrom my PoV, I prefer to have such order: 1)domain 2)login 3)password15:51
tmazurWindows XP at least, yes15:51
e0nebut in anyway, I don't want to introduce a new config option for it15:51
amotokiI see less value in a new setting too15:53
rdopierahttps://duckduckgo.com/?q=login+screen+domain+-windows&t=canonical&iar=images&iax=images&ia=images15:53
rdopieraa quick search shows that it seems to be a pattern15:53
tmazurI remember seeing somewhere login - domain - password too...15:54
rdopierahttp://2.bp.blogspot.com/-hVhEQWgDVLY/ULtR1Uq3CCI/AAAAAAAAA6M/BLOoFSv0Wkw/s1600/db3fde3a98cfc4eb3b2bd264bc8caeec-761004.jpeg15:54
amotokimost examples have only user nad password fields though... :(15:54
rdopierabut the ones that have a domain field, have it last15:55
ikaniasThe oracle example has a domain below15:55
rdopieraprobably because of Windows15:55
rdopieraI would expect everyone to copy Windows15:55
ikaniashttp://2.bp.blogspot.com/-hVhEQWgDVLY/ULtR1Uq3CCI/AAAAAAAAA6M/BLOoFSv0Wkw/s1600/db3fde3a98cfc4eb3b2bd264bc8caeec-761004.jpeg15:55
*** vhari has quit IRC15:56
rdopieraoh yes, market leader ;-)15:56
ikaniasI believe that if ORACLE uses this method then it is a good one15:56
ikanias:-)15:56
amotokiWhile I still think the order of domain->user->password as natural, I have no strong opinion.15:57
amotokiIf we move the domainf field to the bottom, do you no longer need a new setting?15:57
*** macz_ has joined #openstack-meeting-alt15:57
*** macz_ has quit IRC15:57
tmazuramotoki: yes, we will just have a focus on user field15:57
tmazuras the first one15:57
rdopieraI agree that it is more logical, but habit trumps logic15:58
*** macz_ has joined #openstack-meeting-alt15:58
amotokiokay.... I always feel frustrated in the login form of Windows when switching a domain though15:58
e0newe've got one minute left15:59
e0nelet's continue in #openstack-horizon channel15:59
tmazuryes15:59
amotokiit looks better to confirm our consensus. let's contineu in #-horizon16:00
*** LinPeiWen has quit IRC16:00
e0ne#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:00
openstackMeeting ended Wed Mar 10 16:00:22 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2021/horizon.2021-03-10-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2021/horizon.2021-03-10-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2021/horizon.2021-03-10-15.01.log.html16:00
*** vhari has joined #openstack-meeting-alt16:14
*** gyee has joined #openstack-meeting-alt16:22
*** rosmaita has left #openstack-meeting-alt16:40
*** tbarron has joined #openstack-meeting-alt18:37
*** ralonsoh has quit IRC18:41
*** e0ne has quit IRC18:48
*** rdopiera has quit IRC18:49
*** jamesmcarthur has quit IRC18:50
*** jamesmcarthur has joined #openstack-meeting-alt18:50
*** jamesmcarthur has quit IRC18:51
*** jamesmcarthur has joined #openstack-meeting-alt18:52
*** jamesmcarthur has quit IRC18:52
*** jamesmcarthur has joined #openstack-meeting-alt18:52
*** jamesmcarthur has quit IRC18:57
*** macz_ has quit IRC19:35
*** macz_ has joined #openstack-meeting-alt19:36
*** mugsie__ has joined #openstack-meeting-alt19:37
*** tosky_ has joined #openstack-meeting-alt19:37
*** benj_- has joined #openstack-meeting-alt19:37
*** smyers_ has joined #openstack-meeting-alt19:37
*** dosaboy_ has joined #openstack-meeting-alt19:38
*** whoami-rajat has quit IRC19:40
*** tosky has quit IRC19:42
*** benj_ has quit IRC19:42
*** dosaboy has quit IRC19:42
*** mugsie has quit IRC19:42
*** smyers has quit IRC19:42
*** smyers_ is now known as smyers19:42
*** irclogbot_3 has quit IRC19:44
*** mugsie__ is now known as mugsie19:47
*** ajitha has quit IRC19:54
*** tosky_ is now known as tosky20:16
*** tosky has quit IRC20:49
*** tosky has joined #openstack-meeting-alt20:49
*** jamesmcarthur has joined #openstack-meeting-alt21:44
*** johnsom has quit IRC21:46
*** johnsom has joined #openstack-meeting-alt21:46
*** enriquetaso has quit IRC21:53
*** slaweq has quit IRC21:55
*** vishalmanchanda has quit IRC22:08
*** zzzeek has quit IRC22:16
*** zzzeek has joined #openstack-meeting-alt22:18
*** rcernin has joined #openstack-meeting-alt22:27
*** jamesmcarthur has quit IRC23:43
*** jamesmcarthur has joined #openstack-meeting-alt23:43
*** jamesmcarthur has quit IRC23:47
*** jamesmcarthur has joined #openstack-meeting-alt23:47
*** jamesmcarthur has quit IRC23:52
*** jamesmcarthur has joined #openstack-meeting-alt23:52

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