Wednesday, 2021-05-12

*** enriquetaso has quit IRC00:02
*** dave-mccowan has quit IRC00:30
*** dave-mccowan has joined #openstack-meeting-alt00:32
*** jinyuanliu has quit IRC00:55
*** jinyuanliu has joined #openstack-meeting-alt00:55
*** LinPeiWen has joined #openstack-meeting-alt01:09
*** whoami-rajat has quit IRC01:23
*** freerunner has quit IRC02:06
*** freerunner has joined #openstack-meeting-alt02:06
*** gyee has quit IRC02:20
*** rcernin has quit IRC02:23
*** carloss has quit IRC02:34
*** rcernin has joined #openstack-meeting-alt03:09
*** rcernin has quit IRC03:16
*** rcernin has joined #openstack-meeting-alt03:25
*** reddy1 has quit IRC03:25
*** rcernin has quit IRC03:26
*** rcernin has joined #openstack-meeting-alt03:27
*** whoami-rajat_ has joined #openstack-meeting-alt04:44
*** lpetrut has joined #openstack-meeting-alt05:27
*** macz_ has joined #openstack-meeting-alt05:37
*** macz_ has quit IRC05:43
*** ralonsoh has joined #openstack-meeting-alt06:07
*** slaweq has joined #openstack-meeting-alt06:16
*** lpetrut has quit IRC06:21
*** sfernand has quit IRC06:21
*** ralonsoh has quit IRC06:48
*** ralonsoh has joined #openstack-meeting-alt06:49
*** jhesketh has quit IRC07:08
*** tosky has joined #openstack-meeting-alt07:09
*** jinyuanliu has quit IRC07:10
*** jinyuanliu has joined #openstack-meeting-alt07:10
*** macz_ has joined #openstack-meeting-alt07:17
*** macz_ has quit IRC07:21
*** macz_ has joined #openstack-meeting-alt08:09
*** macz_ has quit IRC08:13
*** jhesketh has joined #openstack-meeting-alt08:23
*** dave-mccowan has quit IRC08:23
*** dave-mccowan has joined #openstack-meeting-alt08:32
*** rdopiera has joined #openstack-meeting-alt08:38
*** macz_ has joined #openstack-meeting-alt10:09
*** macz_ has quit IRC10:14
*** macz_ has joined #openstack-meeting-alt10:30
*** macz_ has quit IRC10:34
*** carloss has joined #openstack-meeting-alt10:58
*** rcernin has quit IRC11:23
*** rcernin has joined #openstack-meeting-alt11:24
*** rcernin has quit IRC11:35
*** fabiooliveira has joined #openstack-meeting-alt11:39
*** jinyuanliu has quit IRC12:04
*** jinyuanliu has joined #openstack-meeting-alt12:05
*** sangeet has quit IRC12:21
*** macz_ has joined #openstack-meeting-alt12:28
*** macz_ has quit IRC12:33
*** tmazur has joined #openstack-meeting-alt12:47
*** macz_ has joined #openstack-meeting-alt13:05
*** enriquetaso has joined #openstack-meeting-alt13:09
*** macz_ has quit IRC13:09
*** e0ne has joined #openstack-meeting-alt13:12
*** whoami-rajat_ is now known as whoami-rajat13:17
*** dave-mccowan has quit IRC13:24
*** dave-mccowan has joined #openstack-meeting-alt13:26
*** reddy has joined #openstack-meeting-alt13:29
*** jinyuanliu has quit IRC13:40
*** jinyuanliu has joined #openstack-meeting-alt13:40
*** miniroy has joined #openstack-meeting-alt13:44
*** SpamapS has quit IRC13:47
*** reddy1 has joined #openstack-meeting-alt13:48
*** SpamapS has joined #openstack-meeting-alt13:49
*** reddy has quit IRC13:49
*** gshippey has joined #openstack-meeting-alt13:53
*** rosmaita has joined #openstack-meeting-alt13:58
rosmaita#startmeeting cinder14:00
openstackMeeting started Wed May 12 14:00:31 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
whoami-rajatHi14:00
jungleboyjo/14:00
enriquetasohi14:00
walshh_hi14:00
*** geguileo has joined #openstack-meeting-alt14:01
e0nehi14:01
*** felipe_rodrigues has joined #openstack-meeting-alt14:01
fabiooliveirahi14:02
felipe_rodrigueshi14:02
geguileohi! o/14:02
toskyhi14:02
eharneyhi14:03
rosmaitagood turnout, let's get started14:03
rosmaita#link https://etherpad.opendev.org/p/cinder-xena-meetings14:03
rosmaita#topic announcements - upcoming deadlines14:04
*** openstack changes topic to "announcements - upcoming deadlines (Meeting topic: cinder)"14:04
rosmaitahere's my weekly reminder of what's coming up14:04
rosmaitathis week: R-2114:04
rosmaitaxena milestone 1: R-19 (week of 24 May)14:04
rosmaitayep, 2 weeks away14:04
rosmaitacinder spec freeze: R-15 (week of 21 June)14:04
rosmaitacinderlib wallaby release: R-14 (week of 28 July, though we can release earlier)14:05
rosmaita#topic announcements - train goes to EM14:05
*** openstack changes topic to "announcements - train goes to EM (Meeting topic: cinder)"14:05
rosmaitatrain goes to Extended Maintenance mode soon ... like this week14:05
rosmaitathanks to whoami-rajat for organizing getting the final train releases out14:06
rosmaitarelease patch: https://review.opendev.org/c/openstack/releases/+/79047314:06
rosmaitaEM tag patch: https://review.opendev.org/c/openstack/releases/+/79073714:06
whoami-rajatthanks everyone for the stable branch reviews!14:06
rosmaita#topic announcements - xena midcycles14:06
*** openstack changes topic to "announcements - xena midcycles (Meeting topic: cinder)"14:06
rosmaitasave the dates for the R-18 and R-9 midcycles14:07
rosmaita#link http://lists.openstack.org/pipermail/openstack-discuss/2021-May/022306.html14:07
rosmaitaand, start thinking about what should be discussed14:07
rosmaita#link https://etherpad.opendev.org/p/cinder-xena-mid-cycles14:07
rosmaita#topic announcements - cycle priorities14:08
*** openstack changes topic to "announcements - cycle priorities (Meeting topic: cinder)"14:08
rosmaitawe had kind of a light turnout last week14:08
rosmaitaso I just want to mention this again14:08
rosmaita#link https://wiki.openstack.org/wiki/CinderXenaPTGSummary#Xena_Cycle_Priorities14:08
rosmaitakey thing to pay attention to are the priorities throughout the cycle14:08
rosmaitaplease use the topics stated there on any patches, it will help us prioritize reviews14:09
rosmaita#topic announcements - SQLAlchemy 1.4 in upper-constraints14:09
*** openstack changes topic to "announcements - SQLAlchemy 1.4 in upper-constraints (Meeting topic: cinder)"14:09
rosmaitarajat mentioned this a few weeks ago14:09
rosmaitathere are some non-backward-compat changes in 1.4 to get people ready to move to 2.014:10
rosmaitathanks to geguileo for fixing some bugs yesterday14:10
rosmaitaso it looks like cinder is ready14:10
whoami-rajatgreat!14:10
rosmaitai just want to mention this because not all projects that use sqlalchemy run cross-project tests on the u-c change patches14:11
rosmaita#link https://review.opendev.org/c/openstack/requirements/+/788339/14:11
rosmaitaso if you are working on such a project, you might want to run your tests with sqlalchemy 1.4.13 to make sure nothing breaks14:11
rosmaitathere were some regressions between 1.4.0 and 1.4.12 that were fixed14:12
rosmaitaso don't test against older 1.4.x versions14:12
rosmaitaok, that's all the announcements from me14:13
rosmaitaanyone else?14:13
rosmaitalooks like no14:14
rosmaita#topic interop guidelines review part 214:14
*** openstack changes topic to "interop guidelines review part 2 (Meeting topic: cinder)"14:14
rosmaitawe were asked at the PTG to review the current guidelines and see if anything should be added14:14
rosmaitaas a reminder, what we are looking for is14:15
rosmaitaBlock Storage API calls that should be supported in all clouds14:15
rosmaitaright now, there are only 3.0 calls in the required section14:15
rosmaitathe idea is that we want to promote workload portability14:16
rosmaitaso that users can move their workloads to any openstack cloud and expect them to work14:16
rosmaita(within reason)14:16
rosmaitaat this point, we would introduce any new calls as "advisory"14:17
rosmaitaand then after a while, the interop group will make them required (or, i guess, reject them)14:17
rosmaitalast week I mentioned 3 capabilities as advisory candidates14:18
rosmaita1 - user messages14:18
rosmaita2 - new transfer API14:18
rosmaita3 - attachments API14:18
rosmaitawhat we need for each is that (1) there exist tempest tests for the capability, and (2) we propose a patch to the interop group making the tests advisory14:19
rosmaitai like the user messages from the standpoint of encouraging people to pay attention to them14:19
rosmaitabut i'm not so sure about their relevance for workload portablity14:19
jungleboyj++14:19
rosmaitathough they might contain sufficient info for you to recover from a failure scenario?14:19
rosmaitaanyway, we can think about those because there's another problem14:20
rosmaitathe existing tempest tests are admin tests14:20
rosmaitai think they'd have to be moved to non-admin before they'd be accepted14:21
rosmaitai think they're in the admin section of tempest so that a failure scenario can be caused, something like that14:21
rosmaitai should be more specific.  there are 2 tests14:22
rosmaitaidempotent_id('50f29e6e-f363-42e1-8ad1-f67ae7fd4d5a') - tempest.api.volume.admin.test_user_messages.UserMessagesTest.test_list_show_messages14:22
rosmaitaidempotent_id('c6eb6901-cdcc-490f-b735-4fe251842aed') - tempest.api.volume.admin.test_user_messages.UserMessagesTest.test_delete_message14:22
rosmaitadoes anyone have an opinion on this, or is everyone reading their email?14:23
jungleboyj:-)14:23
eharneythe user message tests shouldn't be admin-oriented14:24
jungleboyjRight.  Otherwise they aren't user messages.  :-)14:24
rosmaitayeah, i think they're in there because you need an admin cred to cause the failure scenario to prompt a user message14:24
rosmaitain any case, we can talk about this later in the cycle, maybe at R-9 midcycle14:25
rosmaitaneed to decide: (a) should they be included, and (b) how to restructure the tempest tests14:25
rosmaitaok, #2 - new transfers api14:25
rosmaitathis is microversion 3.55 (and 3.57)14:26
rosmaitaso all it does is change the REST resource from 'os-volume-transfer' to 'volume-transfers'14:26
rosmaitathis is before my time, it think the idea is the os- one was needed for 3.0 to be compatible with 2.014:27
rosmaitaand i guess eventually we want to stop supporting os-volume-transfer in the URL?14:27
* jungleboyj can't remember why that was.14:27
eharneyjust for clarity... does a cloud meet interop guidelines if it chooses to disable volume transfer via policy configuration?14:27
rosmaitathat's a good question14:28
eharneyyes, the os-volume-methods are generally named that way because they were extensions, and it is now "volume-transfers" because it's a proper part of the API14:28
jungleboyjeharney:  Oh, that is right.  Thank you.14:28
rosmaitato answer Eric's question, as long as it's exposed for some users, i believe it's ok14:29
rosmaitaof course, on that interpretation, a cloud could expose it only to the test user and nobody else14:29
rosmaitanot sure there's anything we can do about that14:30
rosmaitai guess the important question is whether we think volume-transfer should be a required capability14:30
eharneyi don't know, i would assume that since some clouds surely don't have any users that would need it, some admins would prefer to turn it off14:31
rosmaitai looked into this a bit last week ... there are tempest tests for the "old" api, so i put up a patch to include tests for the "new" api14:31
rosmaita#link https://review.opendev.org/c/openstack/tempest/+/79020114:32
eharneyit only makes sense on clouds where users would have a reason to share volumes between each other in some way14:32
*** jbernard has joined #openstack-meeting-alt14:32
rosmaitawell, i'm thinking of a 3rd party thing, where you could set up volumes with DBs and stuff as a service, and transfer the prepared volume to your customers14:32
jungleboyjMaybe I am missing something here.14:33
jungleboyjThe interop test it to validate the things that should work in all clouds.  Not testing what the administrator has decided to enable or not.14:33
eharneyit's an API-only feature14:34
jungleboyjWhat am I missing?14:34
eharneythe only way for it to not work is if the admin doesn't allow it14:34
eharneyi think we just need more clarity (or i do) on what it means to test for interop of a feature like this14:34
rosmaitayeah, i am a bit unclear on this too14:35
jungleboyjYeah, me too.  So, if we say that it is something that should work and an admin has disabled it by policy then that cloud would fail the interop tests?14:35
eharneythat's the part i'm not clear on14:35
rosmaitawell, it depends on how much it's disabled, i think14:35
toskyshouldn't that apply to all interop tests?14:36
eharneythe flip side of that is -- why test it at all14:36
rosmaitaright, because if you have the software, you have all the stuff you need to run the full API14:36
eharneyyou are really just testing if they are running a new enough version of cinder if you're ignoring the part where admins don't allow it via policy14:36
rosmaitaok, maybe we need to invite the interop-WG to the R-9 midcycle so we can discuss this in person14:37
rosmaitamy hidden agenda with the transfers api is:14:37
rosmaitaif we are ever going to remove the "old" api, it would be good to know that people are using the "new" one14:37
rosmaitabecause that would be the required capability14:38
jungleboyj++ to further discussion.14:38
*** sfernand has joined #openstack-meeting-alt14:38
rosmaitaok, that makes sense ... real quickly, though14:39
rosmaitaitem #3 ... the attachments API14:39
rosmaitathere aren't any tempest tests14:39
whoami-rajatisn't it tested with nova tests?14:39
rosmaitathere's a patch from February 2018 to add an "attachments client"14:39
rosmaitabut it's still sitting there14:39
rosmaita#link https://review.opendev.org/c/openstack/tempest/+/48788414:40
eharneyit would be tested via nova tests, but maybe there aren't tests that validate anything about the API itself14:40
rosmaitaright14:40
eharneyi.e. from tempest manipulating attachments directly instead of just by attaching volumes to nova14:40
whoami-rajatok14:41
rosmaitayes, it's tested indirectly, but might be worth testing directly14:41
rosmaitajust wanted to mention that14:41
whoami-rajatyeah nova might not be testing attachment_get at all (not sure though)14:41
rosmaitaok, so the conclusion now is:14:42
rosmaita1 - we don't have anything to add to next.json at this time14:42
rosmaita2 - we want to meet with the interop-WG to get a better handle on the whole thing14:42
rosmaitathat's all14:42
rosmaita#topic Minor version bump for config option added in drivers14:43
*** openstack changes topic to "Minor version bump for config option added in drivers (Meeting topic: cinder)"14:43
jungleboyj++14:43
rosmaitathis is prompted by the train release patch14:43
rosmaita#link https://review.opendev.org/c/openstack/releases/+/79047314:43
whoami-rajatwith reference to config option added in this patch14:44
whoami-rajat#link https://review.opendev.org/c/openstack/cinder/+/78386614:44
rosmaitawe proposed cinder 15.5.2 or something14:44
rosmaitathe release team asked us to make it 15.6.014:44
eharneyminor version bumps are generally not a big deal, so, seems fine14:45
jungleboyjeharney:  ++14:45
rosmaitathe guidelines are here:14:45
jungleboyjI don't have a strong opinion.  If that is what they want, then we can do that.14:45
rosmaita#link https://releases.openstack.org/reference/reviewer_guide.html#release-x-y-z-will-include14:45
whoami-rajatmy main concern here is that we haven't done similar things before and if do we want to standardize it for the next releases, just to be consistent14:45
rosmaitai think it's going to be difficult to maintain consistency on this14:46
rosmaitawe've also had the situation where we were asked to downgrade a minor bump to a patch bump14:46
rosmaitaa lot of times, it's a judgement call14:47
eharneyi suspect that most people are deciding to upgrade based on "this is still stable/train" and not minor vs patch version numbers, and if the minor bump tells them to scan the release notes, maybe that's good14:48
jungleboyjeharney:  ++14:48
whoami-rajatbut we can easily monitor if a config option is added or not, it can be similar to when we bump dependencies14:49
rosmaitawe also have a weird situation because the release team wants us to do an early release of libraries in a cycle, you have wallaby brick 5.0, say, and then first early xena is 5.1, so all the rest of wallaby bricks can only be patch increments14:50
rosmaitai think what it comes down to is basically what eric said14:50
rosmaitayou have to look at the series and not so much the version number14:50
whoami-rajatin that case we do patch bumps for even dependency updates14:51
rosmaitaright14:51
whoami-rajati just wanted to be consistent with the later releases and not specifically regarding stable/train but if consistency is not a major concern here then I'm good14:51
rosmaitait's a good thing to bring up14:52
rosmaitai think we should try to be consistent, but not get too worried about it14:52
whoami-rajat+114:53
tosky(not for the last release of train which should go out yesterday - and I'm the one who usually likes to nags for consistency)14:53
rosmaita:)14:53
rosmaita#topic open discussion14:54
*** openstack changes topic to "open discussion (Meeting topic: cinder)"14:54
rosmaitai think Eric asked last week or at the festival of mypy about what happened to the "Toggle CI" button in gerrit14:56
rosmaitai put an item on the opendev meeting agenda to ask them about that14:56
eharneywell, i was definitely noting that it was missed :)14:56
rosmaitai just need to remember to go to the meeting14:56
rosmaitai thought it was on the feature gap list for the gerrit web UI update, but it's not14:57
rosmaitaanyway, it would be nice to get that back14:58
*** pongboom2 has quit IRC14:58
whoami-rajat++14:58
whoami-rajatreally hard to find reviewer comments in between those CI comments14:58
rosmaitai agree14:59
enriquetaso++14:59
rosmaitathe comment thread tab is nice, but it only shows inline comments14:59
rosmaitaok, we need to make way for horizon14:59
rosmaitahave a good week everyone, and thanks for attending15:00
rosmaita#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Wed May 12 15:00:09 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2021/cinder.2021-05-12-14.00.html15:00
e0nerosmaita: horizon canceled the meeting15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2021/cinder.2021-05-12-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2021/cinder.2021-05-12-14.00.log.html15:00
jungleboyjThanks!15:00
rosmaitae0ne: welcome back! hope you had a good vacation15:00
e0nerosmaita: I did, thanks!15:00
*** macz_ has joined #openstack-meeting-alt15:06
*** macz_ has quit IRC15:10
*** jbernard has left #openstack-meeting-alt15:11
*** geguileo has left #openstack-meeting-alt15:22
*** macz_ has joined #openstack-meeting-alt15:26
*** gyee has joined #openstack-meeting-alt15:26
*** e0ne has quit IRC15:30
*** e0ne has joined #openstack-meeting-alt16:03
*** slaweq has quit IRC16:11
*** carloss has quit IRC16:16
*** carloss has joined #openstack-meeting-alt16:18
*** e0ne has quit IRC16:39
*** e0ne has joined #openstack-meeting-alt17:02
*** ralonsoh has quit IRC17:02
*** rdopiera has quit IRC17:20
*** jinyuanliu has quit IRC18:13
*** jinyuanliu has joined #openstack-meeting-alt18:14
*** vhari has quit IRC18:34
*** vhari has joined #openstack-meeting-alt18:35
*** e0ne has quit IRC18:45
*** macz_ has quit IRC19:16
*** e0ne has joined #openstack-meeting-alt19:23
*** macz_ has joined #openstack-meeting-alt19:32
*** dviroel is now known as dviroel|away19:48
*** slaweq has joined #openstack-meeting-alt19:48
*** macz_ has quit IRC20:08
*** macz_ has joined #openstack-meeting-alt20:08
*** dansmith has quit IRC20:29
*** slaweq has quit IRC21:04
*** dansmith has joined #openstack-meeting-alt21:06
*** miniroy has quit IRC22:22
*** fabiooliveira has quit IRC22:29
*** e0ne has quit IRC22:51
*** sfernand has quit IRC22:57
*** dviroel|away has quit IRC23:01
*** tosky has quit IRC23:01
*** rcernin has joined #openstack-meeting-alt23:07
*** macz_ has quit IRC23:08
*** tmazur has quit IRC23:22
*** enriquetaso has quit IRC23:26
*** vhari has quit IRC23:39

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