16:00:49 #startmeeting Cinder 16:00:50 Meeting started Wed Sep 18 16:00:49 2019 UTC and is due to finish in 60 minutes. The chair is jungleboyj. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:51 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:53 The meeting name has been set to 'cinder' 16:01:17 courtesy ping: jungleboyj whoami-rajat rajinir lseki carloss pots woojay erlon geguileo eharney rosmaita enriquetaso e0ne smcginnis davidsha walshh_ xyang hemna _hemna tosky sfernand 16:01:24 hi 16:01:26 hi! o/ 16:01:26 o/ 16:01:28 hi 16:01:29 ho 16:01:30 hi 16:01:46 o/ 16:01:50 hi everyone 16:02:07 hi 16:02:11 o/ 16:02:14 @! 16:02:15 <_pewp_> jungleboyj ( ^_^)/ 16:02:59 Looks like we have the usual suspects here. 16:03:27 o/ 16:03:47 hi 16:04:00 Lets get started 16:04:06 #topic announcements 16:04:30 I didn't have anything in the etherpad but as I look I should announce that next week is RC-1 Target week. 16:04:45 #link https://releases.openstack.org/train/schedule.html 16:05:24 I am also noticing that I didn't get Feature Freeze for us into the schedule. 16:05:32 o/ 16:05:33 So, I guess it is the wild west out there! 16:05:56 🔫 16:06:19 (what is that?) 16:06:24 Anyway, any features that need to go in the release need to be reviewed this week. 16:06:34 Squirt Gun? 16:06:47 Closest thing I could find to represent wild west. :-) 16:07:12 Anyway, Otherwise hopefully people have been testing Cinder and looking for bugs. 16:07:14 works for me, just didn't render very well in my client 16:07:24 * jungleboyj looks at the Red Hat team. 16:07:59 well i think i found one in my own feature, if that counts 16:08:14 driver bug fix should also be merged until next week? 16:08:17 :-( I guess that is good. 16:08:27 sfernand: yes 16:08:29 sfernand: Yes, driver bug fixes can be merged . 16:08:36 Until we cut the RC. 16:09:13 jungleboyj: RC1 or final RC? 16:09:21 lseki: RC 16:09:22 RC1, 16:09:27 with the RC, the stable branch for train will be cut, and from then on, only backports are allowed 16:09:30 Unless it is a critical bug. 16:09:33 We are in overall feature freeze, so any features we want to land yet should have a FFE on the ML. 16:09:41 lseki: after RC1 only critical bugfixes are allowed 16:09:51 e0ne_: got it, thanks! 16:10:00 We only need to add a Cinder specific feature freeze to the schedule if we want something earlier than the overall one. 16:10:01 ack 16:10:03 jungleboyj, e0ne_: got it, thanks! 16:10:18 smcginnis: Ok. Glad I didn't mess that up. 16:10:32 So any new features for drives need an FFE right now. 16:10:39 *drivers 16:11:01 And we also have the hardware acceleration patches that should get an FFE now. 16:11:12 smcginnis: ++ 16:11:56 this is regarding adding Peer Persistence support feature in HPE 3PAR driver: https://review.opendev.org/#/c/677945 16:12:00 walshh_: So I think you need to submit one for this: https://review.opendev.org/#/c/673013 16:12:14 Same for yours raghavendrat 16:12:58 for the hw accel patch, https://review.opendev.org/#/c/668825/ , does it require an email to the ML, or can we declare it OK here? 16:14:11 I am fine with getting it in but I think, officially, we need to have an e-mail. 16:14:16 I defer to smcginnis though. 16:14:37 I can't find it documented anywhere. 16:15:04 I think the preference is to have it on the ML so there's a record, but if we just want to approve it here, at least this is recorded to reference later if need be. 16:15:15 I like to keep things low overhead when we can. 16:15:31 i'm just asking because of the time zone, not sure zheng or liang are here 16:15:45 Ok. So, I am ok with approving it here. I will review it after the meeting. 16:15:59 ok, cool 16:16:12 Any objections? 16:17:11 I will take that as a no. 16:17:28 can anyone please share email id of ML. i will send a mail requesting for review 16:17:53 openstack-discuss@lists.openstack.org 16:18:01 Yeah ... that. :-) 16:18:01 Please don't send posts to the ML asking for reviews. Or do you mean asking for a feature freeze exception? I think that's covered here now. 16:18:10 thanks rosmaita: 16:18:21 jungleboyj: May want to post something listing the features that have been given approval in this meeting though. 16:18:23 what smcginnis said, though 16:18:34 smcginnis: True. 16:19:34 Hmmm, looking at raghavendrat his change is related to a bug. 16:19:47 So, I think we are ok there. 16:20:13 Any objections? 16:20:44 The last one would be this one from walshh_ That she just pinged me about: https://review.opendev.org/#/c/673013 16:20:53 actually its new feature in HPE 3PAR; other drivers already have Peer Persistence 16:21:05 What is peer persistence? Replciation? 16:21:10 Sean already gave it a +2, so I think that is ok for an FFE? 16:21:11 *replication 16:21:28 yes. Active Active replication 16:23:06 It is limited to their driver. 16:23:40 CI is passing. 16:24:13 Have I lost everyone here? 16:24:34 💣 💥 16:24:39 jungleboyj: sounds good to me to be merged 16:24:42 right. its specific to HPE driver 16:24:56 no objection from me 16:24:57 * e0ne_ is bombed 16:25:02 :) 16:25:07 * jungleboyj laughs 16:26:06 Ok. So, I will send a note saying that the following patches are approved for FFEs: https://review.opendev.org/#/c/677945/ https://review.opendev.org/#/c/673013 and https://review.opendev.org/#/c/668825 16:26:22 Team. Please review those to get them merged ASAP. 16:26:33 pardon me. FFE means ? 16:26:33 No further FFEs after that. 16:26:40 Feature Freeze Exception 16:26:47 thanks 16:27:02 Welcome 16:27:26 Ok, so that kind of covers the one topic in the agenda. 16:27:32 raghavendrat: Further context, we are past this and now need explicit approval to merge anything that can be considered a feature - https://releases.openstack.org/train/schedule.html#t-ff 16:27:53 ok 16:28:08 Trying to not destabilize the release at the last minute. 16:28:46 So, the other topic for today. 16:28:57 #topic Ranking the Forum Submissions 16:29:08 #link https://etherpad.openstack.org/p/cinder-shanghai-forum-proposals 16:29:18 thaks 16:29:23 or, thanks 16:29:36 we've got 3 topics proposed 16:29:53 jungleboyj: are you willing to moderate your 2 topics? 16:30:23 Sure, if you come help. :-) 16:30:23 great 16:31:07 jungleboyj: those are good topics :-) 16:31:32 ok, i will propose those 3 -- the upgrade check could easily be cross project, i will say that we would be happy to have it combined with other proposals on that topic 16:31:35 geguileo: Thank you. Hopefully we get some participation. 16:31:46 yeah, fingers crossed 16:31:47 rosmaita: ++ 16:32:23 does anyone have an objection to any of the topics? 16:32:34 (otherwise, i will assume approval) 16:32:39 Looks like we have decent support for them in the etherpad. 16:32:48 Ship it 16:32:53 great 16:32:59 🚢 16:33:14 i think we have some room, if the volume types gets rejected, we can combine it with the "crazy about cinder" session 16:33:26 rosmaita: ++ 16:33:33 and i can't imagine we're the only people interested in the upgrade checker 16:33:51 I don't know that I have ever had a Forum session rejected. 16:33:57 With this Summit, though, who knows! 16:34:16 hmmm ... you must be better connected than me, i have had a session rejected! 16:34:25 and have also been asked to combine sessions 16:34:27 :) 16:34:43 anyway, i'll get those proposed before the deadline 16:34:52 Ok. Well, we will see how it goes. :-) 16:35:16 reminder: 16:35:20 #link https://etherpad.openstack.org/p/cinder-ussuri-ptg-planning 16:35:40 please add topics if there are things you'd like to see discussed 16:35:55 rosmaita: ++ 16:36:09 Nice to see we have 10 people planning to attend. 16:36:17 yes, that is cool 16:36:19 adding a topic there right now 16:36:25 great! 16:37:19 Side note related to one of those topics - I think the TC is waiting for finalization of the CentOS 8 release date to see if we can use that as the official distro for Red Hat based platforms. If we need to stick with 7, that may throw a wrench (or spanner if you're one of those people) into the py3-only plan. 16:37:52 interesting 16:38:02 lseki: Would be great to know which options. 16:38:16 We only every identified logging to start, but never went anywhere from there. 16:38:26 Partly because of an oslo bug that would just restart the service anyway. 16:38:48 smcginnis: yep, I'm gonna ask the customer about which options besides credentials 16:38:53 ++ 16:39:45 smcginnis: Do we need to do anything more to fix that or is it all in Oslo? 16:39:58 Note that that bug is now fixed. 16:40:05 ^ 16:40:23 I haven't tested it, but with current upper-constraints theoretically it should all work now. 16:40:34 bnemec: Cool. Thanks for pitching in. 16:40:48 I should try that at some point. 16:41:02 Yeah, it's only been tested on Nova. Would be interested to know if it works for Cinder too. 16:41:14 bnemec: ++ 16:42:05 ok, that's all from me ... we can move to open discussion 16:42:14 #topic Open Discussion 16:44:35 Does anyone have anything else they would like to discuss? 16:46:04 Looks like no? 16:47:04 nope 16:47:18 nothing from me 16:47:21 https://review.opendev.org/#/c/677945/ 16:47:33 Wrong link 16:47:34 https://gph.is/2c7tlDw 16:47:38 Wake up people! 16:47:56 lol 16:48:34 Ok. I guess we will wrap things up for today then. 16:48:58 Thanks for attending. Please try to review the remaining features that need to get in. 16:49:01 Thanks! 16:49:07 see you next week! 16:49:07 #endmeeting