14:00:41 #startmeeting cinder 14:00:42 Meeting started Wed Jul 22 14:00:41 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:43 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:45 The meeting name has been set to 'cinder' 14:00:57 #topic roll call 14:01:03 hi 14:01:05 hi 14:01:11 hi 14:01:14 Hi 14:01:14 hi 14:01:17 o/ 14:01:21 hi! 14:01:25 hi 14:01:37 good turnout! it's been so quiet in the cinder channel, i thought maybe i had the wrong day 14:01:46 #link https://etherpad.openstack.org/p/cinder-victoria-meetings 14:01:52 hi 14:01:53 hi 14:02:16 hello everyone 14:02:26 #topic announcements 14:02:47 ok, next week will be our first video + IRC meeting 14:02:59 #link http://lists.openstack.org/pipermail/openstack-discuss/2020-July/015879.html 14:03:05 o/ 14:03:16 great 14:03:36 that email has "Video Meeting Rules", please review them 14:03:40 +1 14:03:45 connection info is on the etherpad 14:04:10 we'll see how it goes 14:04:17 Sounds good. 14:04:26 next announcement: PyCharm licenses for openstack contributors 14:04:34 http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016039.html 14:04:48 i think you get a license for the "professional" edition 14:05:15 Victoria Milestone-2 is next week 14:05:25 new driver: https://review.opendev.org/#/c/741158/ 14:05:30 oh, I've been using the community version 14:05:36 thanks to smcginnis for all his work reviewing that 14:05:47 it looks pretty ready to go 14:05:59 does anyone here have a burning need to review that driver? 14:06:08 (just asking, because otherwise i will do it) 14:06:28 (just don't want to duplicate effort) 14:06:30 I would like to but don't know that I will get to it. :-) 14:06:56 ok, what i wanted to make sure was that someone isn't in the middle of reviewing but hasn't published comments yet 14:07:26 ok, sounds like my afternoon is planned then 14:07:47 final announcement: Victoria mid-cycle part 2 is week of 10 August, look for poll for meeting time on the ML next week 14:07:56 actually, one more thing 14:08:19 i believe that the berlin summit is going to be virtual, but i couldn't find an actual announcement on the ML 14:08:56 rosmaita: https://www.openstack.org/summit 14:09:02 Open Infrastructure Summit 14:09:02 Virtual Event 14:09:02 Oct 19-23, 2020 14:09:09 They said it during the 10th anniversary meeting. 14:09:12 thanks! 14:09:32 i sent an email asking the foundation to update the covid-19 page 14:09:55 ok, so that's all the announcements 14:10:06 #topic final Victoria specs 14:10:24 first, thanks to geguileo and whoami-rajat__ for their patience on their spec 14:10:43 i have been a real PITA about getting the API nailed down before implementation 14:10:58 #link https://review.opendev.org/733555 14:11:12 that's the project-level default volume-types spec 14:11:37 rosmaita: do you want me to do the NITs update after the meeting or in a followup patch? 14:11:48 i think it's ready to go, but it needs another review (and of course geguileo and whoami-rajat__ can't approve it) 14:11:59 lol 14:12:01 whoami-rajat__: i don't know that they really need to be addressed 14:12:23 i just couldn't help myself 14:12:47 next up: reset state robustification 14:12:57 #link https://review.opendev.org/682456 14:13:17 so, this is a good spec, but i don't think anyone has volunteered to pick it up 14:13:40 so i propose that someone else +2 it (it has one +2) and we can merge it and then move to 'untargeted' 14:13:52 in case someone comes along looking for something to do 14:13:56 rosmaita: I like your suggestion 14:14:21 great 14:14:21 rosmaita: development has been picked up 14:14:27 rosmaita: by whoami-rajat__ 14:14:47 that's why he's the primary assignee ;-) 14:15:08 :D 14:15:40 oh, i was talking about reset-state-robustification 14:15:46 which i just noticed i have a -1 on 14:15:50 oh, my bad, sorry 14:15:52 are we still talking about the default types ? 14:15:54 np 14:16:03 sorry, i am being confusing 14:16:08 got it 14:16:09 whoami-rajat__: we are not, I'm just slow to pick up changes in the conversation XD 14:16:30 my proposal is that someone other than me, geguileo, or whoami-rajat__ needs to approve https://review.opendev.org/733555 14:16:58 that one already has whoami-rajat__ working on an implementation, so that is good for Victoria 14:17:12 everything else will have to go into wallaby or 'untargeted' 14:17:16 which reminds me 14:17:26 #link https://review.opendev.org/739487 14:17:37 creates the 'wallaby' directory 14:18:30 ok, that's all for today about specs 14:18:58 #topic finish discussion of __DEFAULT__ volume type 14:19:12 #link https://etherpad.opendev.org/p/__DEFAULT___type_discussion 14:19:32 i took a close look at the etherpad whoami-rajat__ was so nice as to put up 14:19:38 i have a proposal for how to fix this 14:19:44 and i believe it is backportable 14:20:27 so please direct your attention to the ^^ etherpad 14:21:03 and i will be quiet for a few minutes so people can read, particularly lines 33-56 14:21:14 (though it is all excellent content) 14:26:11 * rosmaita notes that 5 minutes have passed 14:26:54 any comments? 14:27:40 Everyone is stunned. 14:27:52 looks like 14:28:14 ok, i will paste that "what to do" into the bug, and whoami-rajat__ can fix it 14:28:32 so basically the last volume type surviving will always be the one set in default_volume_type 14:28:39 sounds good to me 14:28:44 if the two last conditions are applied together 14:29:00 right 14:29:34 i think this is flexible for operators and captures the original intent 14:30:24 ok, we can move on 14:30:40 #topic A/A support 14:30:45 e0ne: that's you! 14:30:49 rosmaita: thanks 14:31:13 so, technically we've got some code in cinder to get A/A HA working 14:31:40 and we've got very few drivers support it: https://github.com/openstack/cinder/blob/master/doc/source/reference/support-matrix.ini#L840 14:32:00 * jungleboyj catches up ... The Default Volume Type proposal looks good to me as well. 14:32:50 Wow, that is very few. 14:32:51 hour code says us that A/A is not supported yet: https://review.opendev.org/#/c/741412/2/cinder/cmd/volume.py and it confuses operators 14:33:05 s/hour/our 14:33:44 21 14:33:55 Oops. :) 14:34:11 so my proposal it to CI job (we discussed it during Ussuri cyccle): https://review.opendev.org/#/c/741125/ 14:34:41 I'm proposing this job as non-voting for now to get some time for bug fixes if any new bugs will be found 14:35:01 actually, I've found at least two bugs with simple tempest run in A/A mode 14:36:26 note: our gates are not very stable today, so some of my patches have -1 from CI after rebase 14:37:12 wow, so even with no special A/A tests, you're getting failures in "normal" tempest when run A/A 14:37:23 i am in favor of adding this job 14:37:28 all patches are in the same chain, so 'Mark Active-Active mode as supported' can be merged only the last 14:37:52 rosmaita: yes, I'm going to implement some real A/A related tests later this cycle 14:38:00 excellent 14:38:11 That is scary. Thanks for working on that e0ne 14:38:24 but current tempest found that volume groups are broken in A/A mode now :( 14:39:45 that's all updates about A/A from my side 14:39:58 I'm happy to get any feedback and reviews 14:40:01 ok, gives us some patches to review 14:40:08 thanks e0ne, this is good work 14:40:25 #topic The future of TSM backup driver 14:40:33 e0ne: you have the floor 14:41:16 I did some refactoring yesterday and found that some TSM code is broken :( 14:41:17 #link https://review.opendev.org/#/c/742224/ 14:41:26 smcginnis suggested to remove this driver 14:42:00 smcginnis: I'm sorry Sean, I was AFK yesterday and read your message only today's morning 14:42:29 as you may know, we don't have 3rd-party CI for backup drivers 14:42:57 and TSM driver requires some IBM software and/or hardware 14:43:07 honestly, I even didn't try to run it 14:44:06 I think, it should be OK to deprecate it in the current cycle and remove in W 14:44:46 ok, i will send something to the ML announcing our plan 14:44:58 rosmaita: thanks a lot! 14:44:59 and i will try to figure out who the TSM maintainer is 14:45:24 oh.. it could be a really complicated task :) 14:45:42 yeah 14:45:56 Let me know if there is anything I can do to help there. 14:45:57 I digged for some commit in 2013 when broken code was introduced and stopped at that point 14:46:05 I still have some contacts into IBM. 14:46:27 It is probably time to deprecate that though. 14:46:30 jungleboyj: would you like to setup 3rd-party CI for TSM? ;) 14:46:49 we should have a discussion at the midcycle about backup driver maintenance 14:46:52 * e0ne is joking 14:46:59 rosmaita: +1 14:47:07 Ha ha. I am already hosting logs for 3rd Party CI runs in my basement. 14:47:07 not having 3rd party CI on these is ... not great 14:47:22 Why not set up a CI? ;-) 14:47:31 I'm not even sure TSM is still even a product. 14:47:42 i was wondering the same thing 14:48:23 anything else on this one? 14:48:54 The last release was in 2011 14:49:17 ok, thanks e0ne 14:49:28 rosmaita: you're welcome 14:49:35 #topic Last call: stable/pike 14:49:42 He he: https://en.wikipedia.org/wiki/IBM_Tivoli_Storage_Manager#/media/File:Original_IBM_Almaden_Research_WDSF_team_from_an_IBM_technical_award.jpg 14:50:07 ok, there is widespread agreement that stable/ocata can go EOL and no one will miss it 14:50:20 however, there was one response to my proposal to EOL stable/pike 14:50:31 #link http://lists.openstack.org/pipermail/openstack-discuss/2020-July/015860.html 14:50:34 it's a party time! less code to maintain :) 14:51:12 so, the situation is that there's a patch to get the stable/pike gate going again 14:51:23 smcginnis: 's favorite thing. Removing code. 14:51:40 but, i don't see any point in merging that if the cinder team is not interested in maintaining stable/pike 14:51:46 jungleboyj: \o/ 14:51:57 i asked last week, and no one appeared interested 14:52:12 so i just wanted to verify with the people present 14:52:33 is anyone interested in keeping stable/pike alive? 14:52:53 my feeling is that just having it open is costing me too much psychic energy 14:53:05 just out of curiosity: is there an update on the nova side? Did they merge their part of pike patches? 14:53:09 and we could better spend our time fixing A/A in current branches 14:53:16 i believe they did 14:53:19 rosmaita: :_ 14:53:20 (because if we drop pike, almost everyone drops pike) 14:53:21 :) 14:53:34 but the difference is that elod volunteered to maintain nova stable/pike 14:53:44 he has not volunteered to maintain cinder stable/pike 14:54:09 and i don't want to keep it open unless at least one cinder core agrees to "adopt" stable/pike 14:54:46 Not it 14:55:24 my opinion is that the project does not need the distraction 14:55:46 and if no one even wants to review stable/pike patches, then nothing can get in there anyway 14:55:59 If eharney isn't raising a concern then I think it is safe to retire it. 14:56:12 retiring it is good 14:56:16 yay! 14:56:33 ok, will send out something on the ML and propose EOL patches 14:56:50 actually, in reverse order -- i will put up the patches and then send something to the ML 14:57:10 ok, thanks everyone for that 14:57:14 #topic open discussion 14:57:51 could anybody help to review the volume local cache patches:) 14:58:27 i think they are very close ^^ 14:58:30 I've some patches which i want to request reviews for 14:58:30 1) https://review.opendev.org/#/c/721206/ 14:58:30 2) https://review.opendev.org/#/c/735513/ 14:58:30 3) https://review.opendev.org/#/c/737035/ 14:59:44 #link https://review.opendev.org/663549 14:59:48 rosmaita: thanks 15:00:01 bugfix for generic NFS driver is waiting for reviews, too (they're small) https://review.opendev.org/#/q/topic:bug/1870367 15:00:03 #link https://review.opendev.org/700799 15:00:25 ok, please return to the meeting logs when you are looking for something to do 15:00:27 #endmeeting