Wednesday, 2020-01-22

*** k_mouza has quit IRC00:45
*** yamamoto has joined #openstack-meeting-401:42
*** yamamoto has quit IRC01:53
*** Liang__ has quit IRC02:06
*** yamamoto has joined #openstack-meeting-402:23
*** diablo_rojo has quit IRC03:06
*** yamamoto has quit IRC03:27
*** k_mouza has joined #openstack-meeting-403:46
*** k_mouza has quit IRC03:52
*** yamamoto has joined #openstack-meeting-404:56
*** links has joined #openstack-meeting-405:16
*** evrardjp has quit IRC05:34
*** evrardjp has joined #openstack-meeting-405:34
*** Jeffrey4l has quit IRC05:45
*** Jeffrey4l has joined #openstack-meeting-405:46
*** k_mouza has joined #openstack-meeting-405:47
*** k_mouza has quit IRC05:52
*** vishalmanchanda has quit IRC07:24
*** lpetrut has joined #openstack-meeting-407:47
*** gcheresh has joined #openstack-meeting-407:59
*** slaweq_ has joined #openstack-meeting-407:59
*** e0ne has joined #openstack-meeting-408:00
*** bnemec has joined #openstack-meeting-408:09
*** davee_ has quit IRC08:14
*** davee_ has joined #openstack-meeting-408:14
*** e0ne has quit IRC08:22
*** e0ne_ has joined #openstack-meeting-408:23
*** e0ne_ has quit IRC08:23
*** e0ne has joined #openstack-meeting-408:23
*** slaweq_ has quit IRC08:33
*** e0ne has quit IRC08:42
*** ralonsoh has joined #openstack-meeting-408:51
*** yamamoto has quit IRC09:02
*** gcheresh has quit IRC09:15
*** gcheresh has joined #openstack-meeting-409:17
*** k_mouza has joined #openstack-meeting-409:22
*** k_mouza has quit IRC09:29
*** k_mouza has joined #openstack-meeting-409:32
*** e0ne has joined #openstack-meeting-410:13
*** k_mouza has quit IRC10:38
*** pcaruana has joined #openstack-meeting-411:02
*** dviroel has joined #openstack-meeting-411:03
*** lkoranda has joined #openstack-meeting-411:17
*** lkoranda has quit IRC11:53
*** k_mouza has joined #openstack-meeting-412:01
*** lkoranda has joined #openstack-meeting-412:22
*** dmellado has quit IRC12:24
*** dmellado has joined #openstack-meeting-412:26
*** k_mouza has quit IRC12:32
*** k_mouza has joined #openstack-meeting-412:40
*** yamamoto has joined #openstack-meeting-413:08
*** k_mouza has quit IRC13:41
*** lkoranda has quit IRC13:44
*** lkoranda has joined #openstack-meeting-413:45
*** lkoranda_ has joined #openstack-meeting-413:47
*** rosmaita has joined #openstack-meeting-413:48
*** lkoranda has quit IRC13:50
*** lkoranda_ has quit IRC13:52
*** lkoranda has joined #openstack-meeting-413:53
rosmaitaCourtesy reminder: Cinder meeting in #openstack-meeting-4 at 1400 UTC13:56
rosmaitajungleboyj rosmaita smcginnis tosky whoami-rajat m5z e0ne geguileo eharney walshh_ jbernard ^^13:56
*** tosky has joined #openstack-meeting-413:57
*** whoami-rajat has joined #openstack-meeting-413:59
rosmaita#startmeeting cinder14:00
openstackMeeting started Wed Jan 22 14:00:14 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
smcginniso/14:00
e0nehi14:00
rosmaita#link https://etherpad.openstack.org/p/cinder-ussuri-meetings14:00
whoami-rajathi14:00
rosmaita#topic roll call14:00
*** openstack changes topic to "roll call (Meeting topic: cinder)"14:00
geguileohi! o/14:00
m5zhi14:01
*** yamamoto has quit IRC14:01
toskyo/14:02
*** enriquetaso has joined #openstack-meeting-414:02
enriquetasoo/14:02
rosmaitalooks like a good turnout14:02
rosmaita#topic announcements14:02
*** openstack changes topic to "announcements (Meeting topic: cinder)"14:02
rosmaitaspec freeze is next week14:02
rosmaitathanks to everyone who attended the virtual mid-cycle yesterday, i think it was productive14:03
rosmaita#link https://wiki.openstack.org/wiki/CinderUssuriMidCycleSummary14:03
rosmaita^^ that's a quick writeup of what we talked about14:03
enriquetasorosmaita++ thanks to you!14:03
* rosmaita blushes14:03
rosmaitai put together a survey for participants but also people who did NOT attend14:04
rosmaita#link https://forms.gle/muR2vMArZ7Eu1iV4614:04
rosmaitawill help in planning for part 2, which will be week of 16 March14:04
enriquetaso\o/14:04
rosmaitaand, i have been a busy boy, here's the result of one of my action items:14:05
rosmaita#link https://review.opendev.org/70370914:05
e0nerosmaita: awesome! I like such format with several short calls14:05
rosmaitae0ne: that's good feedback14:05
rosmaitathe above link is an attempt to be explicit about how we want to write/review code that uses py3-only features, and also code that still uses py2 compatibility14:06
rosmaitaplease be brutal in your comments!14:06
rosmaitait will be helpful if we can get some good guidelines together14:06
e0nerosmaita: thanks for this patch! I didn't get a time to review it but it's great to have such guides14:06
rosmaitathank you14:07
rosmaitaok, that's all for announcements, on to the main program14:07
rosmaita#topic really quick spec review14:07
*** openstack changes topic to "really quick spec review (Meeting topic: cinder)"14:07
rosmaita#link https://review.opendev.org/#/q/status:open+project:openstack/cinder-specs14:07
rosmaitai just want to take a quick look at these, mainly asking people if we are still interested14:08
rosmaitaor, if they are still interested in proposing them14:08
smcginnisI don't think the backup-id one needs to be a spec. We should just add the code.14:08
rosmaitayeah, i have a question about it later on the agenda14:08
rosmaitai was going to say, we could leave it as a spec for when this comes up again about adding something to the volumes table14:09
rosmaitabut14:09
rosmaitawe can point people to this review, it doesn't have to be a spec14:09
whoami-rajati think we can merge 'copy image to multiple stores' patch if everyone is ok with it (looks like it from the +2 list)14:09
rosmaitayes, i had a question about that14:09
rosmaitais it cinder policy for the PTL to merge specs?14:09
rosmaitaguess that's for smcginnis and jungleboyj14:09
rosmaitathe question, i mean14:10
*** yamamoto has joined #openstack-meeting-414:10
*** yamamoto has quit IRC14:10
smcginnisrosmaita: I don't think we ever made it a formal policy.14:10
jungleboyjo/14:10
jungleboyjSorry.  Late.14:10
*** yamamoto has joined #openstack-meeting-414:10
rosmaitai definitely like the idea of as many cores reading each spec as possible14:10
whoami-rajatrosmaita, ++14:11
rosmaitaso it's probably good to leave them open even with multiple +2s14:11
rosmaitabut i agree with whoami-rajat that this particular spec is ready for merging14:11
rosmaitai didn't see eharney come in14:11
e0neI didn'14:11
*** k_mouza has joined #openstack-meeting-414:11
e0neI didn't approve this spec because it was added to the agenda14:12
rosmaitae0ne: you mean the multiple stores of glance spec?14:12
rosmaitadid you still want to look it over?14:12
e0nerosmaita: I was talking about https://review.opendev.org/#/c/70097714:13
rosmaitae0ne: ok14:13
*** k_mouza has quit IRC14:13
rosmaitai was going to ask eharney if he plans to revise https://review.opendev.org/682456 , i can ask offline14:14
rosmaitait looks like everything else has been sitting for over a month14:14
rosmaitaso it looks like we are pretty much on schedule for specs14:14
rosmaitaalthough, Liang did have a question about the volume-local-cache spec14:15
*** yamamoto has quit IRC14:15
rosmaitafrom yesterday's discussion, it looked like maybe cinder needs to know about what cache-mode is available so we can reject unsafe modes?14:15
rosmaitaor did I misunderstand what we wanted there?14:15
rosmaitaLiang's question was how we would get this info to cinder14:16
rosmaitai guess the issue is:14:16
rosmaitaif we want to disallow unsafe modes completely, we can have os-brick reject the attachment14:17
rosmaitaif we want to disallow unsafe operations, we would need cinder to have some info14:17
rosmaitamy request is that if you have an interest in this spec, and especially in this part of it, please leave a comment on the spec14:18
rosmaitai think i may have gone over my 5 minutes14:18
rosmaita#topic 3rd-party CI update14:19
*** openstack changes topic to "3rd-party CI update (Meeting topic: cinder)"14:19
rosmaitae0ne: that's you14:19
e0nerosmaita: thanks14:19
e0neI'm trying to figure out how many 3rd-party CIs have cinder tempest plugin running14:19
e0neI tried to check on existing patches to cinder but a lot of logs are not available now14:20
e0nethat's why I created a dummy patch14:20
e0ne#link https://review.opendev.org/#/c/703772/14:20
rosmaitagood idea14:20
jungleboyje0ne:  :-)  Yeah, that is part of the reason I haven't had a chance to look at all of that.14:20
e0neand I tried ti run all CIs from https://docs.openstack.org/cinder/latest/drivers.html14:21
e0ne#link https://docs.openstack.org/cinder/latest/drivers.html14:21
e0nethere are a lot of failures14:21
e0neand I'm waiting for more results14:21
jungleboyj:-(14:21
e0neprobably, I'll to it on a daily basis to run rechecks14:21
e0nehttps://docs.google.com/spreadsheets/d/1id4FY7Ywv8vWp01cTw_Km_YpN98U7vYvFgn8wy_o9vU/edit#gid=014:21
e0neI'm sorry for google docs14:21
e0neI can convert it to some more open format if needed14:22
rosmaitai think that's fine for now14:22
e0neI'm worried a lot about Dell EMC CI14:22
smcginnisI did get copied on a message that the log server is down.14:22
e0neI was not able to open any logs from it both from Europe and US14:22
jungleboyjThat is fine.  Ugh, what is up with the Dell CI not having logs accessible?14:22
smcginnisThere is an IT ticket open to resolve that.14:22
toskyso, to summarize, and without considering the Dell CI ...14:23
jungleboyjsmcginnis:  Ah, ok.  Thanks for being on that.14:23
e0nesmcginnis: thanks for the information14:23
toskyjust one 3rd party CI is running cinder-tempest-plugin (!)14:23
e0neFujitsu ETERNUS CI logs are not accessible too:(14:23
rosmaitawow14:23
jungleboyjAre we really down to this few drivers?14:23
rosmaitae0ne: yes thanks for putting this all in one place14:23
e0neit reports SUCCESS14:23
e0nebut there are no logs http://openstackci.jp.fujitsu.com/Eternusci/72/703772/1/check/fujitsu-eternus-dx-iscsi/6d794b614:23
*** links has quit IRC14:23
jungleboyjrosmaita: ++14:23
e0ne^^ this job reported to gerrit 25 minutes ago14:24
*** lkoranda has quit IRC14:24
e0nemy google spreadsheet is open for comments for everybody14:24
e0neI can give add write permissions per request14:25
e0neaccording tempest plugin, only NetApp SolidFire CI is using it:(14:25
e0neDatara CI should use it too but I don't have a confirmation14:26
rosmaitawell, i guess we should say "Hooray for NetApp!"14:26
e0neI14:26
rosmaitabut otherwise, this is a depressing spreadsheet14:26
jungleboyj:-)14:26
e0neI'll keep this doc updated once I'll have more results14:26
toskythanks; so what are the next steps?14:26
e0nePure Storage CI has own tempest plugin with few tests14:26
toskye0ne: do you know if that plugins is published somewhere?14:27
toskyI wonder if those tests are really pure-specific14:27
e0netosky: I don'd know yet14:27
toskyanyway, do we have direct contacts for all CI maintainers?14:27
e0neunfortunately, that's all I've got for today:(14:27
smcginnisThey *should* all be listed on14:27
rosmaitae0ne: that's plenty! thanks for putting this together14:28
smcginnishttps://wiki.openstack.org/wiki/ThirdPartySystems14:28
e0nehttps://wiki.openstack.org/wiki/ThirdPartySystems/Dell_EMC_SC_Series_CI14:28
e0neyou can find CI wiki with contacts on the https://docs.openstack.org/cinder/latest/drivers.html page14:28
e0netosky: ^^14:28
jungleboyjtosky: In the past I have used the infor smcginnis shared.14:28
jungleboyjI get some responses.  Sometimes I don't.14:28
rosmaitai think we may need to have an emergency virtual mid-cycle focusing only on 3rd party CI14:28
e0ne+114:29
jungleboyjYeah.  :-(14:29
e0nebtw, I didn't check if 3rd-party CI uses python314:29
rosmaitajungleboyj: i think you took an action item yesterday to contact some people who's CIs are not responding?14:29
jungleboyjrosmaita:  Yes I did.  Will try to follow up on that today.14:30
rosmaitaok, great14:30
jungleboyjAs well as making a blanket statement to the ML to see if we get more discussion.14:30
rosmaitalet's discuss this again at next week's meeting14:31
jungleboyjrosmaita: ++14:31
whoami-rajate0ne, i think the CI's not using python3 were marked unsupported in Train14:31
e0newhoami-rajat: sounds reasonable14:31
rosmaitayes, hopefully no one snuck back to using py2!14:31
*** davidsha has joined #openstack-meeting-414:32
jungleboyjwhoami-rajat: Right.  I went through that process.14:32
rosmaitaok, let's revisit this next week and in the meantime I'll follow up with something more concrete14:33
rosmaita(not sure what, though)14:33
e0ne:)14:33
*** Liang__ has joined #openstack-meeting-414:33
rosmaitain the meantime, please look at this from yesterday: https://wiki.openstack.org/wiki/CinderUssuriMidCycleSummary#The_current_state_of_3rd_Party_CIs14:33
rosmaita#link https://wiki.openstack.org/wiki/CinderUssuriMidCycleSummary#The_current_state_of_3rd_Party_CIs14:33
jungleboyjWell, we have been going back and forth on this forever.  Who knows, you might have a new insight rosmaita14:34
rosmaitaone never knows14:34
rosmaitayeah, smcginnis posted some info from 2017 on this same topic yesterday!14:34
rosmaitathanks for following up on this e0ne14:35
rosmaitaany more comments?14:35
e0nerosmaita: you're welcome14:35
e0nenothing from my side for now14:35
smcginnisThat definitely wasn't the first time it was discussed either. ;)14:35
rosmaitaright!14:35
jungleboyjAnd won't be the last.14:36
rosmaita#topic is 'backup_id' in volume metadata ambiguous?14:36
*** openstack changes topic to "is 'backup_id' in volume metadata ambiguous? (Meeting topic: cinder)"14:36
rosmaitaactually, before i pose that question14:36
rosmaitai think smcginnis has a good point that the spec should be a bug instead14:36
rosmaita#link https://review.opendev.org/#/c/70097714:37
rosmaita^^ so you know what i'm talking about14:37
*** roman_g has joined #openstack-meeting-414:37
smcginnisIt's metadata. We have a field for metadata. It's not captured in there yet. Just add it (my take on things)14:37
rosmaitathat makes sense to me14:37
smcginnisThere's no real API change, no need to modify the DB, so not really anything that needs to be captured in a spec to make sure everyone understands the change and impact.14:38
rosmaitaand there's the backport potential you mentioned on the review14:38
smcginnisYeah, I think there's a good case for that.14:38
rosmaitawe can leave it up to the spec proposers about how they want to follow up14:39
rosmaitai'll leave a comment14:39
rosmaitain the meantime14:39
rosmaitamy question is whether 'backup_id' in the volume metadata could be ambiguous14:39
rosmaitais it obvious that it means "This volume was created from a backup" vs. "This volume was backed up"?14:39
smcginnisMaybe "src_backup_id"?14:39
rosmaitai'm kind of new around here, that's why i'm asking14:39
rosmaitasmcginnis: yes, that's what i was thinking14:40
smcginnisI like that it is more explicit then.14:40
rosmaitaok, i will suggest that on the spec14:40
smcginnisThe spec also focuses on volume creation directly from backup, but that was just a convenience API added. I think the change should also handle adding that metadata when a volume is independently created, then restored to from a backup.14:41
enriquetasosmcginnis++14:41
rosmaitai agree, might as well make it as useful as possible14:41
rosmaitaany other comments?14:41
smcginnisNope14:42
rosmaitaok, moving on14:42
rosmaita#topic py3.6 *and* py3.7 testing in the gate 14:42
*** openstack changes topic to "py3.6 *and* py3.7 testing in the gate  (Meeting topic: cinder)"14:43
rosmaitathis is another follow-up from yesterday14:43
rosmaitasince we don't have to test py2 any more, and we are claiming py3.6 and py3.7 support, i figure we should be testing both of those14:43
rosmaita(it won't consume any extra resources)14:43
e0ne+114:43
rosmaitaanyway, i went back and looked at our recent change to tox.ini and .zuul.yaml14:44
rosmaitaresults are here:14:44
rosmaita#link https://etherpad.openstack.org/p/cinder-ussuri-community-goal-drop-py27-support14:44
rosmaitadown at the bottom, under "Review"14:44
smcginnis3.8 may be added in Victoria. There is some discussion on that that just testing 3.6 and 3.8 should be sufficient to make sure 3.7 is safe.14:45
smcginnisJust a data point for the future.14:45
rosmaitaok, good to know14:45
rosmaitaour current setup will be easy to add 3.8 testing to both tox and zuul14:45
rosmaitain any case, i think cinderlib and os-brick are running gate tests with just the system python3 for wherever the test lands14:46
rosmaitawhich may be ok14:46
rosmaitabut i wanted to point it out14:46
rosmaitaas far as cinder-tempest-plugin ...14:47
rosmaitalooks like it's running the normal tests plugins are supposed to run14:47
rosmaita(although I guess I should verify that)14:47
rosmaitaso i'm inclined not to mess with it14:47
whoami-rajatwith python3 right?14:48
rosmaitawhoami-rajat: yes14:48
whoami-rajatok14:48
smcginnisI think I saw some work going on with tempest itself about how to handle things since tempest is branchless.14:48
rosmaitawhich is most likely py 3.6, i think14:48
rosmaitayes, smcginnis you have a good point, we should let that shake out before making changes ourselves14:49
smcginnisI think it may have just required some devstack changes to allow stable branches to run services with py2.7 but run tempest under py3.14:49
rosmaitaso, to summarize, it looks like our testing is in pretty good shape14:50
rosmaitacould be some room to look at cinderlib and os-brick if anyone is so inclined14:50
rosmaitabut those gate jobs are pretty complicated, i personally do not want to touch them with a 10-foot pole14:51
smcginnis;)14:51
jungleboyj /me hands rosmaita  an 11 foot pole14:51
rosmaitajungleboyj: i thought maybe you would go metric!14:52
jungleboyj:-)14:52
rosmaitai guess it's a 3 metre poll for our non-USA constituents14:52
rosmaitaok, enough of that14:52
rosmaita#topic open discussion14:52
*** openstack changes topic to "open discussion (Meeting topic: cinder)"14:52
lsekisorry I'm late14:53
lsekie0ne: netapp ontap drivers {nfs, iscsi, fcp} are running cinder-tempest-plugin as well14:53
lsekiwe're having some troubles with our CI right now, though14:53
lsekiI'll let you know when it's fixed and having plugin tests passing14:53
e0nelseki: thanks14:53
rosmaitalseki: ty14:53
jungleboyjlseki:  ++  Great.14:53
rosmaitalseki: you missed our shout-out to netapp for using cinder-tempest-plugin14:53
lseki\o/14:54
jungleboyjwhoop whoop!14:54
rosmaita(09:26:05 AM) rosmaita: well, i guess we should say "Hooray for NetApp!"14:54
lsekihooray 🎉14:54
dviroel\o/14:54
enriquetasohooray :P14:54
sfernand:)14:54
smcginnisOh, since it's open floor, just pointing out the naming for W - https://wiki.openstack.org/wiki/Release_Naming/W_Proposals14:55
rosmaitaso anything goes nowadays, naming wise?14:56
jungleboyjThis will be interesting.14:56
smcginnisYep.14:56
smcginnisUp to 10 letters long in the ISO basic Latin alphabet.14:56
rosmaitawell, i am all out of ideas after "Vaiveahtoish"14:57
smcginnis:)14:57
rosmaita(which obviously didn't win)14:57
rosmaitadown to 2 minutes -- anyone?14:58
*** Liang__ is now known as LiangFang14:59
whoami-rajata review request for the patch - https://review.opendev.org/#/c/700176/14:59
*** vishalmanchanda has joined #openstack-meeting-414:59
LiangFango/14:59
rosmaitaLiangFang: noted15:00
rosmaitaok, thanks to e0ne for his 3rd party CI spreadsheet15:00
rosmaitaand see everyone next week!15:00
rosmaita#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Wed Jan 22 15:00:44 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
e0nesee you next week15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-01-22-14.00.html15:00
enriquetasobye15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-01-22-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-01-22-14.00.log.html15:00
jungleboyjThanks!15:00
enriquetaso6+89+615:01
smcginnis10115:01
enriquetasosorry about that haha15:02
enriquetasosmcginnis, haha15:02
*** LiangFang has quit IRC15:05
*** tosky has left #openstack-meeting-415:06
*** k_mouza has joined #openstack-meeting-415:06
*** k_mouza has quit IRC15:11
*** k_mouza has joined #openstack-meeting-415:34
*** k_mouza has quit IRC15:38
*** gcheresh has quit IRC15:57
*** rosmaita has left #openstack-meeting-416:04
*** diablo_rojo has joined #openstack-meeting-416:34
*** gcheresh has joined #openstack-meeting-416:34
*** bnemec has quit IRC16:51
*** gcheresh has quit IRC16:53
*** k_mouza has joined #openstack-meeting-417:15
*** k_mouza has quit IRC17:19
*** k_mouza has joined #openstack-meeting-417:23
*** evrardjp has quit IRC17:34
*** evrardjp has joined #openstack-meeting-417:34
*** diablo_rojo has quit IRC17:42
*** davidsha has quit IRC18:00
*** vishalmanchanda has quit IRC18:17
*** e0ne has quit IRC18:19
*** diablo_rojo has joined #openstack-meeting-418:19
*** yamamoto has joined #openstack-meeting-418:59
*** k_mouza has quit IRC18:59
*** yamamoto has quit IRC19:04
*** ralonsoh has quit IRC19:06
*** e0ne has joined #openstack-meeting-419:38
*** gmann is now known as gmann_afk19:38
*** e0ne has quit IRC19:47
*** gmann_afk is now known as gmann20:18
*** k_mouza has joined #openstack-meeting-420:33
*** diablo_rojo has quit IRC20:38
*** enriquetaso has quit IRC20:46
*** gcheresh has joined #openstack-meeting-420:51
*** sfernand has quit IRC21:07
*** slaweq_ has joined #openstack-meeting-421:07
*** pcaruana has quit IRC21:07
*** anastzhyr has joined #openstack-meeting-421:10
*** diablo_rojo has joined #openstack-meeting-421:34
*** enriquetaso has joined #openstack-meeting-421:39
*** gcheresh has quit IRC21:51
*** slaweq_ has quit IRC22:25
*** dviroel has quit IRC22:25
*** diablo_rojo has quit IRC23:51

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!