Wednesday, 2020-07-01

*** andrebeltrami has quit IRC00:38
*** yamamoto has joined #openstack-meeting-alt00:46
*** yamamoto has quit IRC00:49
*** yamamoto has joined #openstack-meeting-alt00:58
*** Liang__ has joined #openstack-meeting-alt01:17
*** markvoelker has joined #openstack-meeting-alt01:20
*** markvoelker has quit IRC01:24
*** gyee has quit IRC01:35
*** yaawang has quit IRC01:42
*** ricolin_ has joined #openstack-meeting-alt01:43
*** yaawang has joined #openstack-meeting-alt01:43
*** Liang__ has quit IRC01:46
*** yaawang has quit IRC02:45
*** yaawang has joined #openstack-meeting-alt02:46
*** rfolco has quit IRC03:20
*** ricolin_ is now known as ricolin03:30
*** Liang__ has joined #openstack-meeting-alt03:58
*** markvoelker has joined #openstack-meeting-alt04:03
*** markvoelker has quit IRC04:08
*** apetrich has quit IRC04:43
*** mugsie has quit IRC04:53
*** mugsie has joined #openstack-meeting-alt04:57
*** markvoelker has joined #openstack-meeting-alt05:03
*** strigazi has quit IRC05:04
*** strigazi has joined #openstack-meeting-alt05:06
*** markvoelker has quit IRC05:07
*** vishalmanchanda has joined #openstack-meeting-alt05:23
*** links has joined #openstack-meeting-alt05:34
*** yaawang has quit IRC05:45
*** yaawang has joined #openstack-meeting-alt05:45
*** strigazi has quit IRC05:46
*** ccamacho has quit IRC05:58
*** ccamacho has joined #openstack-meeting-alt06:31
*** tetsuro has joined #openstack-meeting-alt06:33
*** tetsuro has quit IRC06:43
*** tetsuro has joined #openstack-meeting-alt06:43
*** tetsuro has quit IRC06:43
*** yaawang has quit IRC06:43
*** yaawang has joined #openstack-meeting-alt06:51
*** tetsuro has joined #openstack-meeting-alt06:55
*** yaawang has quit IRC06:55
*** yaawang has joined #openstack-meeting-alt06:55
*** tetsuro has quit IRC06:56
*** rcernin has quit IRC07:02
*** markvoelker has joined #openstack-meeting-alt07:04
*** rcernin has joined #openstack-meeting-alt07:05
*** markvoelker has quit IRC07:09
*** ivanvtimofeev has quit IRC07:09
*** slaweq has quit IRC07:12
*** slaweq has joined #openstack-meeting-alt07:13
*** markvoelker has joined #openstack-meeting-alt07:18
*** markvoelker has quit IRC07:23
*** rcernin has quit IRC07:30
*** Liang__ has quit IRC07:30
*** Liang__ has joined #openstack-meeting-alt07:31
*** ralonsoh has joined #openstack-meeting-alt07:33
*** jtomasek has quit IRC07:36
*** jtomasek has joined #openstack-meeting-alt07:40
*** rcernin has joined #openstack-meeting-alt07:50
*** ttsiouts has joined #openstack-meeting-alt07:53
*** ttsiouts has quit IRC07:53
*** ttsiouts has joined #openstack-meeting-alt07:54
*** e0ne has joined #openstack-meeting-alt07:58
*** rcernin has quit IRC08:06
*** rdopiera has joined #openstack-meeting-alt08:09
*** ttsiouts has quit IRC08:37
*** ttsiouts has joined #openstack-meeting-alt08:38
*** ttsiouts has quit IRC08:42
*** derekh has joined #openstack-meeting-alt08:45
*** yaawang has quit IRC08:46
*** yaawang has joined #openstack-meeting-alt08:46
*** apetrich has joined #openstack-meeting-alt08:48
*** jtomasek_ has joined #openstack-meeting-alt09:05
*** jtomasek has quit IRC09:07
*** ttsiouts has joined #openstack-meeting-alt09:27
*** yaawang has quit IRC09:30
*** yaawang has joined #openstack-meeting-alt09:31
*** yamamoto has quit IRC09:37
*** ricolin has quit IRC09:52
*** yamamoto has joined #openstack-meeting-alt09:55
*** yamamoto has quit IRC10:06
*** yamamoto has joined #openstack-meeting-alt10:07
*** apetrich has quit IRC10:12
*** Liang__ has quit IRC10:40
*** priteau has joined #openstack-meeting-alt11:02
*** markvoelker has joined #openstack-meeting-alt11:15
*** markvoelker has quit IRC11:19
*** raildo has joined #openstack-meeting-alt11:28
*** apetrich has joined #openstack-meeting-alt11:45
*** rnoriega_ has quit IRC11:58
*** rnoriega- has joined #openstack-meeting-alt11:58
*** andrebeltrami has joined #openstack-meeting-alt12:06
*** irclogbot_2 has quit IRC12:16
*** irclogbot_1 has joined #openstack-meeting-alt12:17
*** derekh has quit IRC12:28
*** trident has quit IRC12:46
*** derekh has joined #openstack-meeting-alt12:48
*** trident has joined #openstack-meeting-alt12:49
*** ricolin has joined #openstack-meeting-alt12:54
*** rfolco has joined #openstack-meeting-alt13:00
*** jhesketh has quit IRC13:22
*** jhesketh has joined #openstack-meeting-alt13:24
*** liuyulong has joined #openstack-meeting-alt13:50
*** yamamoto has quit IRC13:50
*** rosmaita has joined #openstack-meeting-alt13:52
*** tosky has joined #openstack-meeting-alt13:57
rosmaita#startmeeting cinder14:00
rosmaita#link https://etherpad.openstack.org/p/cinder-victoria-meetings14:00
rosmaita#topic roll call14:00
openstackMeeting started Wed Jul  1 14:00:03 2020 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
*** openstack changes topic to "roll call (Meeting topic: cinder)"14:00
toskyo/14:00
walshh_hi14:00
jungleboyjo/14:00
whoami-rajatHi14:00
e0nehi14:00
rosmaitahello everyone14:01
rosmaita#link https://etherpad.openstack.org/p/cinder-victoria-meetings14:01
geguileohi! o/14:01
jungleboyjHappy Wednesday!14:02
rosmaitaspecs freeze in a few hours, so that's what we'll be discussing mostly today14:02
rosmaitabut first some announcements14:02
rajiniro/14:02
rosmaita#topic updates - mid-cycle14:02
*** openstack changes topic to "updates - mid-cycle (Meeting topic: cinder)"14:02
*** sfernand has joined #openstack-meeting-alt14:02
rosmaitathanks to everyone who participated last week14:02
rosmaitaif you missed it, you can catch up on youtube14:02
*** Liang__ has joined #openstack-meeting-alt14:02
*** Liang__ is now known as LiangFang14:02
rosmaitathough abishop said he was going to wait until after part 2 and then binge watch14:03
rosmaitaso, whatever works for you14:03
LiangFango/14:03
rosmaita#link https://wiki.openstack.org/wiki/CinderVictoriaMidCycleSummary14:03
lsekio/14:03
rosmaitayou can find a link to the recording ^^14:03
jungleboyj:-)14:03
rosmaita#topic updates - monthly video meeting poll14:03
smcginniso/14:03
*** openstack changes topic to "updates - monthly video meeting poll (Meeting topic: cinder)"14:03
rosmaita#link https://rosmaita.wufoo.com/forms/monthly-video-meeting-proposal/14:04
rosmaitai noticed that there were some communication difficulties at the mid-cycle, so the poll includes an option about whether we should really do one meeting a month in video or not14:04
rosmaitabut if we commit to taking good notes in irc, i think it's worth a try14:05
rosmaitaanyway, the proposed first video meeting would be 29 July14:05
rosmaitaso we have a bit of time to think about this14:05
rosmaitaanyway, the poll closes 1200 UTC on Thursday 9 July14:05
rosmaita#updates - brocade FCZM driver14:06
rosmaitaoops14:06
rosmaita#topic updates - brocade FCZM driver14:06
*** openstack changes topic to "updates - brocade FCZM driver (Meeting topic: cinder)"14:06
rosmaitai sent out an email summarizing what we discussed at the mid-cycle14:07
rosmaita#link http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015692.html14:07
rosmaitaso, we'll see if anyone cares14:07
rosmaita#topic updates - need to keep an eye on the cinder-plugin-ceph-tempest job14:07
*** openstack changes topic to "updates - need to keep an eye on the cinder-plugin-ceph-tempest job (Meeting topic: cinder)"14:07
rosmaitathis was really bugging me yesterday, but maybe it's a fluke14:07
toskyrosmaita: master or previous branches?14:07
rosmaitawe made the job voting on 11 march this year14:07
rosmaitatosky: both14:07
toskythere is an open review that should fix the issues14:07
rosmaita#link https://zuul.opendev.org/t/openstack/builds?job_name=cinder-plugin-ceph-tempest14:08
rosmaitatosky: that's good news14:08
rosmaita#topic updates - code coverage job14:09
*** openstack changes topic to "updates - code coverage job (Meeting topic: cinder)"14:09
rosmaitai finally followed up on my PTG action to put up a job so you can have the code coverage report in groovy html on each patch14:09
rosmaita#link https://review.opendev.org/#/c/738687/14:09
rosmaita(it still needs reviews)14:10
rosmaitaright now, all it does is post the coverage output for you to look at14:10
rosmaitawe could add something that would pass/fail based on coverage falling past a threshhold14:10
rosmaitae0ne is in favor of that14:11
whoami-rajat#link https://6d4b1c17bd5712b1da1e-24da3718548989a700aa54b9db0ff79c.ssl.cf2.rackcdn.com/738687/8/check/cinder-code-coverage/7bb5c35/cover/14:11
whoami-rajatlooks great14:11
*** yamamoto has joined #openstack-meeting-alt14:11
*** yamamoto has quit IRC14:11
e0neI know that not everybody agrees with me, so I put +1 on that patch14:11
*** yamamoto has joined #openstack-meeting-alt14:12
smcginnisPutting a pass/fail on coverage is a hard thing to do right.14:12
smcginnisI've been in endless debates about what the right amount of coverage should be.14:12
jungleboyjThis is cool.  Good info at least.14:12
rosmaitayeah, it's a start14:12
rosmaitai'll think about how we could track the coverage to address e0ne's concern14:12
rosmaitamy worry is that i don't want it to be non-voting and turn into the pylint job14:13
rosmaitathat's always red and so you don't notice anymore14:13
e0nerosmaita: +114:13
*** eharney has joined #openstack-meeting-alt14:13
smcginnisAlternatively, we could just add coverage as part of the base commands that are run so it's always available for the normal UT runs.14:14
e0nerosmaita, smcginnis: we can use --fault-unnder (https://coverage.readthedocs.io/en/coverage-5.1/cmd.html) option14:14
rosmaitalet's discuss on the patch, or in a few meetings14:15
rosmaitai think for now just having the info available is good14:15
e0neAgree. it's good for the beginning14:16
rosmaitathat's it for updates, unless anyone else has an announcement14:16
jungleboyj++ Starting by having it out there is a good step.14:16
*** pots has joined #openstack-meeting-alt14:16
*** yamamoto has quit IRC14:16
jungleboyjDon't want the voting question to stop that.14:16
rosmaitayeah, let's make it a separate discussion14:16
rosmaita#topic minor driver refactoring14:17
*** openstack changes topic to "minor driver refactoring (Meeting topic: cinder)"14:17
e0nerosmaita: thanks for raising this up!14:17
rosmaita#link https://review.opendev.org/#/c/656888/14:17
rosmaitae0ne: thanks for doing it!14:17
toskye0ne: --fault-under is not good IMHO, it should be a delta14:17
e0nea minor change with a huge diff14:17
rosmaitaok, what's going on is that e0ne did some refactoring14:17
rosmaitaand, it turns out that he didn't have to modify a lot of unit tests14:18
rosmaitabecause they weren't there14:18
*** TusharTgite has joined #openstack-meeting-alt14:18
rosmaitaso my point in bringing this up is ...14:18
rosmaitaif you are a driver maintainer, look at that patch ^^ and check your driver14:18
rosmaitaand you might want to think about a follow up patch adding a test or two14:18
rosmaitathere are some sample tests on that patch14:19
e0nejust for the note: I'm not going to add unit-tests for drivers for this patch or as a follow up patch14:19
rosmaitathe main thing is, we will review the patch by hand, but it's easy to miss something14:19
rosmaitae0ne: good note14:19
rosmaitayeah, this is a driver maintainer's responsibility14:19
rosmaitaso please take a look14:20
smcginnis++14:20
rosmaitabut do it soon, like within the next few hours14:20
rosmaitabecause it looks good, and we will merge it soon so e0ne isn't in merge conflict hell14:20
e0ne:)14:21
rosmaita#topic victoria spec review14:21
*** openstack changes topic to "victoria spec review (Meeting topic: cinder)"14:21
rosmaitaok, i got sidetracked on some stuff, so my knowledge of the state of specs is from last night14:22
rosmaitabut here we go14:22
*** dave-mccowan has quit IRC14:22
rosmaita#topic spec - Remove quota usage cache14:22
*** openstack changes topic to "spec - Remove quota usage cache (Meeting topic: cinder)"14:22
rosmaita#link https://review.opendev.org/#/c/730701/14:22
rosmaitaSam left some performance info on the spec, i think14:22
rosmaitalooks like Lucio's objection is formatting14:23
rosmaita(which is fine, we want to be able to read the thing)14:23
rosmaitaso, at a glance, it looks like getting the usage dynamically isn't too big a hit14:24
jungleboyjLooks like the performance impact is sufficiently minimal though.14:24
rosmaitai suspect there will be some weird things that we won't know about until someone actually tries to implement this14:25
rosmaitaso probably no point trying to work them out in advance14:25
eharneyIMO we should look at our db schema and see if we have indexes etc. there that would make this perform as well as possible14:25
rosmaitaeharney: that is a good point, please add it as a comment to the spec14:26
*** dave-mccowan has joined #openstack-meeting-alt14:26
rosmaitayeah, good indices are key14:26
rosmaitaso, the author is in australia, and i think today is almost over there14:27
rosmaitai think it would be ok to stretch the deadline for him to attend to some changes14:27
rosmaitai think the mood here is mostly positive toward this spec?14:28
e0nerosmaita: +114:28
jungleboyj+114:28
rosmaitai guess this spec-freeze is a bit early relative to the ptg, but we can at least weed out the no-chance specs14:29
rosmaitaok, i'll put a note that he can revise and it will still be acceptable until the next cinder meeting14:29
rosmaita#topic specs - Support modern compression algorithms in cinder backup14:30
*** openstack changes topic to "specs - Support modern compression algorithms in cinder backup (Meeting topic: cinder)"14:30
rosmaita#link https://review.opendev.org/#/c/726307/14:30
rosmaitathis one is kind of in the same boat, revision wise14:30
rosmaitamy feeling is that we should update our compression algo options14:31
rosmaitabut to what ... i think i agree with eric that we should just pick 1 of the 2 options14:31
rosmaitaas to which one ...14:31
eharneyyeah14:31
rosmaitawe're going to have to get this past the requirements team14:31
eharneyi haven't done much looking into which would be a better choice14:31
rosmaitaso i think in preparing the info for the patch for global-requirements, we can decide which is best14:32
eharneyi assume any would pass the requirements concerns14:32
e0newhat about make these things plugable?14:32
eharneythey are14:32
eharneybut we don't want to give people a bunch of extra options just because we can, and have to maintain that forever14:33
rosmaitai like zstandard better, but i'm not sure it's packaged as widely as the other option14:33
rosmaitai think packaging is an issue for inclusion in global-requirements14:34
rosmaitaanyway, the author already has a patch up adding the algos to cinder14:34
rosmaitaso either one will be an easy code change14:34
rosmaitait's really a matter of working out which is best14:34
rosmaitaso i think give him another week to get an argument together, and onto the spec?14:35
rosmaitaany objection?14:35
e0neeharney: actually, all algorithms and compressors are hard-coded14:36
e0newe can make it extendable like we did for db provider14:36
eharneywhy?14:36
e0neso end-users will be able to add out-of-tree compressing algos to use it with cinder14:37
eharneyand then end up with backups that can only be consumed by certain versions of cinder on certain clouds on certain platforms..14:37
smcginnis^14:37
eharneyi don't see a benefit to justify that mess14:37
e0negoor point14:37
rosmaitayeah, let's keep these as 2 separate issues14:38
jungleboyj++14:38
rosmaitaso for now, we can say let's add a modern compression algo14:38
rosmaitaand we can discuss later whether the plugin approach makes sense14:38
geguileowould it make sense to update the default compressor?14:38
geguileoif we are going to add it to the requirements already and it won't be optional14:39
rosmaitano, i think gzip is a venerable compression algo and we can honor it by keeping it the default14:39
geguileolol14:39
rosmaitaalso, it's a standard library algo14:40
e0negeguileo: we should not break current deployments with rolling upgrades14:40
jungleboyjIt seems like this is a new feature that people can use if they wish.14:40
rosmaita#topic specs - Reset state robustification14:40
*** openstack changes topic to "specs - Reset state robustification (Meeting topic: cinder)"14:40
geguileoe0ne: that's a very good reason14:41
rosmaita#link https://review.opendev.org/#/c/682456/14:41
jungleboyjMmmm robustification14:41
e0negeguileo: that's why we still have tgt as a default option :(14:41
rosmaitai think this is good, the open question is how to handle the --force option14:41
geguileoe0ne: ouch14:41
eharneyi prefer just making the API safe and leaving the --force cases to cinder-manage14:41
rosmaitai am ok with that14:42
rosmaitaeharney: why don't you revise the spec and people can comment, you can have a 1 week extension too14:42
eharneyok14:43
rosmaita#topic specs - Default volume type overrides14:43
*** openstack changes topic to "specs - Default volume type overrides (Meeting topic: cinder)"14:43
rosmaita#link https://review.opendev.org/#/c/733555/14:43
rosmaitathis one had 2 +2s, i just left it open so people could still comment14:43
whoami-rajatit looks perfect now14:43
whoami-rajatthanks geguileo for the quick update14:44
geguileonp14:44
rosmaitaok, i will re-read and we can get this one approved before the deadline14:44
rosmaitayay!14:44
rosmaitatopic specs - Backup Backends Configuration14:45
rosmaita#link https://review.opendev.org/#/c/712301/14:45
rosmaitathis one looks good too14:45
e0nethanks everybody for your feedback on this!14:45
rosmaitalooks like e0ne has revised, i think we can get this approved in the next hour or so14:46
rosmaita#topic specs - Support revert any snapshot to the volume14:46
*** openstack changes topic to "specs - Support revert any snapshot to the volume (Meeting topic: cinder)"14:46
e0ne:)14:46
rosmaita#link https://review.opendev.org/#/c/736111/14:46
rosmaitasmcginnis: thanks for your comment on there, i think you explained clearly why we want this to have a generic implementation14:47
rosmaitathat can be overriden by backends that can do better14:47
eharneyi think this spec needs more thought on the implications of doing this... it seems like a minefield of usability and perf problems14:47
smcginnisI hate to be negative about it, because I do think it would be very useful. But there are many issues with trying to do this for all backends.14:47
eharneyit also doesn't explain how it actually works14:48
smcginnisVery light on details.14:48
*** LiangFang has quit IRC14:48
smcginnisThe work item list of "change restriction" is a little vague. :)14:48
rosmaitaok, i think this one we ask them to continue working on for W14:48
rosmaitasmcginnis: i think W has a name?14:48
smcginnisWombat IIRC.14:48
rosmaitaglad i asked, i was thinking Wallaby14:49
rosmaitaok, i will leave an encouraging comment on the spec14:49
smcginnisOh, maybe you're right.14:49
jungleboyjI thought it was Wallaby.14:49
smcginnisI really should know since I ran it, but now I forget.14:49
jungleboyjI am pretty sure it is.14:49
smcginnisYeah, you're all right. Don't listen to me. :)14:49
eharneythis needs some details on what actually happens on a typical backend that can do this in the "ideal" way14:49
jungleboyjBecause that was the one I liked.14:49
smcginniseharney: ++14:49
rosmaitai was so devastated by my V name defeat, that i can't remember anything anymore14:49
eharneybecause it's very unclear to the newer snapshots if you revert to an old snap14:50
eharneyunclear what happens to*14:50
jungleboyjYou weren't Victoriaous ?14:50
rosmaitajungleboyj: :P14:50
smcginniseharney: I know at least for some it's an internal update of a pointer, but that's definitely not how all storage works.14:51
jungleboyjThis feels like one of those proposals that is a good idea but ends up being a dangerous minefield upon implementation.14:51
rosmaitaeharney: keep your thoughts coming, i will pull them out of the meeting log and put them on the spec14:51
rosmaitaok, one final spec14:51
rosmaita#topic specs - volume list query optimization14:51
*** openstack changes topic to "specs - volume list query optimization (Meeting topic: cinder)"14:51
*** Liang__ has joined #openstack-meeting-alt14:51
rosmaita#link https://review.opendev.org/#/c/726070/14:51
rosmaitai think you may have seen my note to the ML14:52
rosmaitai think this is really a bug14:52
rosmaitaor actually a set of 3 or so bugs14:52
rosmaitabut, it may still be worth a spec14:52
eharneyi think rosmaita teased out some good details on this that i wasn't able to quite grasp when we last discussed this14:52
rosmaitabecuase the fix will have to be in 2 places14:53
eharneybut i haven't followed up enough on picking through this yetr14:53
eharneyyet*14:53
rosmaitarest api layer and also the db layer14:53
rosmaitabut i don't think it's going to require a mv change14:53
eharneyi would suggest not calling this an "optimization"14:54
rosmaitayes, the title needs to change14:55
rosmaitait's basically "correct the volume-list filtering"14:55
rosmaitaand maybe "correct the volume list"14:55
*** links has quit IRC14:55
rosmaitaand maybe "never, ever do this kind of change again where we hijack the volume status to have internal states that aren't displayable in the rest api"14:56
eharneylol14:56
rosmaitai think maybe i will write this up as a bug, and tell the author to feel free to pick up the bug?14:57
jungleboyjTwo Minute warning.14:58
eharneysensible enough14:58
rosmaitaok, works for me14:58
jungleboyj++14:58
rosmaitaok, cool, we got through all the non-WIP specs14:58
rosmaita#topic open discussion for 60 seconds14:59
*** openstack changes topic to "open discussion for 60 seconds (Meeting topic: cinder)"14:59
jungleboyj*celebration*14:59
toskyregarding the cinder-plugin-ceph-tempest test, this patch may help on train and older branches, but it needs to go through master and ussuri first: https://review.opendev.org/#/c/738273/14:59
* tosky was ready14:59
rosmaitaty tosky14:59
rosmaitaalready has a +2!15:00
rosmaitaok, gotta go15:00
rosmaita#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Wed Jul  1 15:00:19 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-07-01-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-07-01-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-07-01-14.00.log.html15:00
whoami-rajatthanks15:00
jungleboyjThanks!15:00
rosmaitaapologies to horizon team for running over15:00
e0nerosmaita: np15:00
e0ne#startmeeting horizon15:00
openstackMeeting started Wed Jul  1 15:00:54 2020 UTC and is due to finish in 60 minutes.  The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: horizon)"15:00
openstackThe meeting name has been set to 'horizon'15:00
vishalmanchandahi15:01
*** tosky has left #openstack-meeting-alt15:01
e0nevishalmanchanda: hi15:01
e0nelet's wait until more people will join us15:01
-amotoki- lurks here :)15:02
rdopierao/15:02
e0nevishalmanchanda: before we start. I was AFK whilte you were discussing cinder messages with amotoki15:02
e0ne#topic Notices15:03
*** openstack changes topic to "Notices (Meeting topic: horizon)"15:03
e0neactually, I don't have any updates this week15:03
e0neI'm going to setup a poll for our virtual mid-cycle later tonight to clarify what date and time work for us15:04
vishalmanchanda+1.15:05
e0nein cinder we did it instead of a regular weekly meeting but it could be pretty late for vishalmanchanda and amotoki15:05
e0neit's supposed to be later this month around Victoria-2 milestone15:06
vishalmanchandae0ne: hmm.. I can manage if it work for everyone.15:06
amotokiI missed meeting last two weeks as I was sleepy. I am trying to move my life rhythm earlier, but I got sleepy too early :-(15:07
amotokino intention to skip the meeting15:07
*** dave-mccowan has quit IRC15:08
e0neamotokiL that's why I asked at PTG  if a current time works good for everybody15:09
e0ne#topic Stable maintenance and EOL15:10
*** openstack changes topic to "Stable maintenance and EOL (Meeting topic: horizon)"15:10
e0neamotoki: you added this topic for PTG but we had no time to discuss it15:10
e0ne#linke https://etherpad.opendev.org/p/horizon-v-ptg15:10
e0neI was waiting for all stable cores to discuss it15:11
*** dave-mccowan has joined #openstack-meeting-alt15:11
e0ne#link https://etherpad.opendev.org/p/horizon-v-ptg (line #105)15:12
amotokiI just wonder who are stakeholders for older branches and whether we have bandwidth to check which stable branches including gate healthiness15:12
e0nepersonally, I'm not interested in ocata anymore15:12
e0nebut I still have customers with pike and queens15:13
rdopierawe use queens, stein and train15:13
e0neso I'm OK to mark ocata as EOL (end of life)15:13
amotokiocata is already under discussion for EOL15:13
amotokias it is not easy to maintain its gate related to py27 drop15:14
e0nethat's true15:14
amotokias you know ocata will be EOL soon as a whole15:14
amotokiit is a different story outside of horizon15:15
e0ne+115:15
e0ne#link http://lists.openstack.org/pipermail/openstack-discuss/2020-May/015112.html15:16
amotokirocky and older are now in EM phase. which branches are you interested in?15:16
amotokiaccording to the above comment from e0ne and rdopiera, pike is oldest15:17
amotokiand queens has common interest at least from RH and mirantis15:17
e0neunfortunately, I have to support pike(15:17
amotokihehe, it is not so surprising15:18
amotokiI think what we need to do are (1) to check gate healthiness in stable branches and then (2) fix gate failures if any15:19
e0neamotoki: I can do it15:19
amotokiI believe periodic jobs help us for (1) as it is not easy to check it regularly15:20
amotoki(2) is totally up to who can work on it.15:20
*** TusharTgite has quit IRC15:21
e0ne#action e0ne to check health of gates fro EM branches15:21
e0neat least, I'll check the current situation and will do the best to fix if gages are broken15:22
amotokiI plan to backport https://review.opendev.org/#/c/737686/ to stable branches and then prepare the grafana dashboard at grafana.o.o.15:23
amotokiwe can check the healiness (for example) in the team meeting.15:23
e0neamotoki: awesome!15:23
vishalmanchandacool.15:23
e0nelet's start with this and see how it works during the next meeting15:26
e0ne#topic stable review policy15:27
*** openstack changes topic to "stable review policy (Meeting topic: horizon)"15:27
e0nehere is general guideline: https://docs.openstack.org/project-team-guide/stable-branches.html#review-guidelines15:29
e0newe follow it15:29
e0nebut it seam reasonable to fit them a bit with a current situation in horizon team15:29
e0nefrom the etherpad: we previously had a policy to allow a single +2 if a backport is proposed by a stable core to handle the situation with only a couple of stable cores.15:30
e0neI didn't know about this rule before, but lt sounds absolutely reasonable for me15:30
e0neat least for a simple fixes15:31
amotokithe comment is from me. It was true when Rob was the PTL15:31
e0neit seams it was introduced before I started contribution to horizon15:32
amotokithis rule assumes that stable reviewers are familiar with the stable policy, so stable reviewers are assumed to consider the stable policy when they propose backports.15:33
*** Liang__ has quit IRC15:33
amotokiI beleve the current stable reviewers are familiar with the policy15:34
e0neamotoki: sure. in any case, stable core and put -1 or -2 for any proposed patch15:34
amotokiyes, and if a stable core is not sure we can ping another stable core :)15:35
e0ne+215:35
e0neor we can ping openstack stable team15:35
amotokiyeah15:36
e0nerdopiera: are you agree with this proposal?15:36
amotokiin such case we discuss it in the mailing list. it works in most cases I believe.15:36
rdopierae0ne: I don't like it, but I guess we don't have much choice15:39
e0nerdopiera: It's not ideal solution15:40
amotokior we can always ping second core. we have three active stable cores now, so it can work too.15:41
amotoki(as we do now)15:42
amotokiI am just afraid what happens if my activity slows down.15:43
amotokiI want not be a bottleneck :)15:44
rdopieralet's try it, and we can always get back to the old way15:47
e0newe can try to do stable reviews on a weekly basis15:47
e0newhat is our agreement on this?15:49
* rdopiera agrees15:50
amotokithe original proposal is from me, so I have no objection. If you are okay, we can try a single +2 from bakcports from stable cores.15:51
amotokilooks like we agree15:51
e0ne#agreed to allow a single +2 if a backport is proposed by a stable core to handle the situation with only a couple of stable cores15:51
e0newe can re-visit our decision in the future if any objection will be15:52
e0ne#topic Open Discussion15:53
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"15:53
amotokilet's raise if you see any question or issue in IRC or meeting :)15:53
vishalmanchandaI want to discuss this cinder messages bp.15:53
e0newe've got seven minutes left15:53
vishalmanchandaI have already discuss some points with amotoki and I am almost agrees with him.15:53
vishalmanchandae0ne: I also need your opinion on this as you draft this bp for horizon.15:54
e0netwo cores agreed, I don't want to argue :)15:54
vishalmanchanda#link https://specs.openstack.org/openstack/cinder-specs/specs/newton/summarymessage.html15:54
e0nevishalmanchanda: FYI, I'm going to add some backup-related messages this cycle15:55
vishalmanchandae0ne: nice.15:55
vishalmanchandae0ne: What's you think how Can we show it in horizon?15:56
amotokias summary, I pointed that messages related to snapshots need to be covered in the volume detail page and whether it fits normal user scenarios.15:56
amotokiand if a user have some problem(s) on a snapshot they need to check the volume detail instead of the snapshot detail in the current proposal.15:57
amotokihonestly I am not sure we need to cover all messages related to a specific volume including snapshots (and potentially backups) in the volume detail.15:58
amotokiso it leads to my question on user scenarios.15:59
e0neit's a good question16:00
e0neI need to think a bit16:00
e0newe're out of time16:00
e0nelet's continue discussion in the  #openstack-horizon channel16:01
e0ne#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:01
openstackMeeting ended Wed Jul  1 16:01:20 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-07-01-15.00.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-07-01-15.00.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-07-01-15.00.log.html16:01
amotokio/16:01
*** ricolin has quit IRC16:01
*** liuyulong has quit IRC16:05
*** ttsiouts has quit IRC16:06
*** ttsiouts has joined #openstack-meeting-alt16:07
*** ttsiouts has quit IRC16:11
*** derekh has quit IRC16:15
*** sfernand has quit IRC17:02
*** ralonsoh has quit IRC17:10
*** ralonsoh has joined #openstack-meeting-alt17:10
*** bnemec has quit IRC17:15
*** ganso has quit IRC17:15
*** ganso has joined #openstack-meeting-alt17:18
*** bnemec has joined #openstack-meeting-alt17:21
*** rnoriega- has quit IRC17:26
*** jtomasek_ has quit IRC17:26
*** megheisler has quit IRC17:26
*** tsmith2 has quit IRC17:26
*** zzzeek has quit IRC17:26
*** freerunner has quit IRC17:26
*** hongbin has joined #openstack-meeting-alt17:28
*** irclogbot_1 has quit IRC17:28
*** gyee has joined #openstack-meeting-alt17:29
*** rnoriega- has joined #openstack-meeting-alt17:29
*** jtomasek_ has joined #openstack-meeting-alt17:29
*** megheisler has joined #openstack-meeting-alt17:29
*** tsmith2 has joined #openstack-meeting-alt17:29
*** zzzeek has joined #openstack-meeting-alt17:29
*** freerunner has joined #openstack-meeting-alt17:29
*** irclogbot_3 has joined #openstack-meeting-alt17:30
*** yamamoto has joined #openstack-meeting-alt17:44
*** yamamoto has quit IRC17:53
*** e0ne has quit IRC17:59
*** eharney has quit IRC18:16
*** slaweq has quit IRC18:25
*** hongbin has quit IRC18:44
*** rosmaita has left #openstack-meeting-alt18:46
*** hongbin has joined #openstack-meeting-alt19:18
*** rdopiera has quit IRC19:41
*** vishalmanchanda has quit IRC19:47
*** ralonsoh has quit IRC19:50
*** eharney has joined #openstack-meeting-alt19:59
*** hongbin has quit IRC20:06
*** e0ne has joined #openstack-meeting-alt20:20
*** slaweq has joined #openstack-meeting-alt20:25
*** hongbin has joined #openstack-meeting-alt20:54
*** ircuser-1 has quit IRC21:03
*** e0ne has quit IRC21:07
*** slaweq has quit IRC21:19
*** priteau has quit IRC21:21
*** rcernin has joined #openstack-meeting-alt22:37
*** rcernin has quit IRC22:47
*** rcernin has joined #openstack-meeting-alt22:47
*** hongbin has quit IRC23:11
*** hongbin has joined #openstack-meeting-alt23:16
*** rfolco has quit IRC23:48
*** yamamoto has joined #openstack-meeting-alt23:52
*** yamamoto has quit IRC23:57

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