16:00:18 #startmeeting Cinder 16:00:19 Meeting started Wed Jul 31 16:00:18 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:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:23 The meeting name has been set to 'cinder' 16:00:37 courtesy ping: jungleboyj whoami-rajat rajinir lseki carloss pots woojay erlon geguileo eharney rosmaita enriquetaso e0ne smcginnis davidsha walshh_ xyang hemna _hemna tosky 16:00:46 Hi 16:00:49 hi 16:00:52 o/ 16:00:53 o/ 16:00:54 @! 16:00:54 <_pewp_> jungleboyj \( ・_・) 16:00:56 o/ 16:00:56 \o 16:01:02 o/ 16:01:04 hi 16:01:42 hi 16:01:43 hi 16:01:59 ji 16:02:01 hi 16:02:24 Cinderers Assemble! 16:03:23 Give people one more minute here. 16:04:19 i don't see how anyone would dare to be late after hearing "Cinderers Assemble!" 16:04:44 rosmaita: :-) 16:04:57 Secretly I needed more coffee. I am the late one. 16:04:59 ;-) 16:05:00 Ok. 16:05:05 #topic announcements 16:05:26 I have submitted a request to be part of the Shanghai PTG. 16:05:36 I know that rosmaita and I are going to be there. 16:05:44 :) 16:06:02 Well, I don't have travel approved yet, but the Lenovo offices are hosting OUI, so they better get me there. 16:06:41 * e0ne didn't get approval yet 16:06:50 Anyway, I estimated our attendance at 20 people, half what we have had in the past, and asked for 2 days for technical discussion and .25 days for onboarding. 16:07:02 Haven't heard any confirmation on the request yet. 16:07:09 o/ 16:07:24 So, that is the plan there. 16:07:57 We have the mid-cycle coming up in Raleigh in less than a month now: https://etherpad.openstack.org/p/cinder-train-mid-cycle-planning 16:08:03 #link https://etherpad.openstack.org/p/cinder-train-mid-cycle-planning 16:08:21 We have 4 people confirmed. 16:08:23 o/ 16:08:31 4 or 5 remote attendees. 16:08:44 I am hoping to have zoom to use to host the meeting this time. 16:08:49 *fingers crossed* 16:09:11 Please add topics to the etherpad. 16:09:23 I will work on getting topics organized before the meeting. 16:09:24 jungleboyj: hangout was good last time :) 16:10:11 We will have hangouts if nothing else. :-) 16:10:45 That is all I had for announcements 16:10:57 #topic Milestone-2 follow-up 16:11:11 I think we got the possible drivers and specs merged. 16:11:19 Thank you to all who helped make that happen. 16:11:37 hemna_: and rosmaita The last minute help was greatly appreciated. 16:12:05 Thanks rosmaita 16:12:11 de nada 16:12:38 So, I wanted to ask about the spec for updating the scheduler to use the DB. 16:12:56 e0ne: Wants to delay that to the Unicorn release so he can focus on the generic backup work. 16:13:03 That sounds like a good plan to me. 16:13:15 jungleboyj: thanks for mentioning this 16:13:22 more time for design thought on that sounds like it would be beneficial anyway, so, cool 16:13:45 Yeah ... I am fine with that. 16:13:59 e0ne: Thanks for being realistic about what you can get done. 16:14:21 jungleboyj: thanks for supporting me. I appreciate your help 16:14:31 e0ne: Any time. 16:14:58 So, was there anything else that people wanted to bring up about Milestone-2? 16:15:32 Ok. 16:15:46 #topic Leverage hw accelerator in image compression 16:15:50 zhengMa: 16:16:34 hi 16:16:38 zhengMa: Hey. 16:16:51 #link https://review.opendev.org/#/c/668825/ 16:17:04 Happy for spec merged 16:17:14 Yes. Good news. 16:17:21 And we have implemented according to the spec 16:17:59 Good. Looks like you patch is currently failing the check. 16:18:10 #spec link https://review.opendev.org/#/c/652275/ 16:18:23 yes, because of the unit test.. 16:18:52 You are also missing an update to cinder/opts.py 16:18:56 we have not implemented yet :( 16:19:15 tox right? 16:19:29 tox -e genopts 16:19:42 sorry, my mistake 16:19:44 Check the pep8 check for details. 16:20:02 Ok, got it 16:20:29 Otherwise, it does appear that you have a UT issue. 16:21:07 zhengMa: Is this just a request for reviews? 16:21:11 yes, the newly added container_format property DOES impact some unit test 16:21:57 If so, noted. If you can get the items I have noted fixed we will take a look. 16:22:02 jungleboyj: yes, we want some comments so we can quickly fix our code:) 16:22:24 Ok. Will do. Start by getting the check passing please. 16:22:24 Ok, thank you! 16:22:26 does it implement the non-hardware compression path? 16:23:03 eharney: yes, we implemented a gzip class for software compression 16:23:11 ok 16:23:40 jungleboyj: got it, thank you! 16:23:43 Cool. Any other questions? 16:23:44 flerm 16:23:57 * jungleboyj marks hemna_ tardy 16:24:02 :P 16:24:06 zhengMa: those failures look like a test fixture problem 16:24:12 @!h 16:24:12 <_pewp_> jungleboyj (/ .□.) ︵╰(゜Д゜)╯︵ /(.□. ) 16:24:22 rosmaita: ++ 16:25:11 #topic question about the cross-project GPG encryption effort 16:25:14 rosmaita: yes, I have just read the log. And we're going to fix it 16:25:14 rosmaita: 16:25:20 we have an approved spec for train, "image encryption and decryption" 16:25:25 #link http://specs.openstack.org/openstack/cinder-specs/specs/train/image-encryption.html 16:25:35 it says that "This spec requires the implementation of appropriate encryption/decryption functionality in a global library shared between the components involved in image encryption workflows (Nova, Cinder, OSC), like os-brick" 16:25:42 i was reviewing the glance spec for this, and that one says about the global library, "We determined to use os-brick". 16:25:48 #link https://review.opendev.org/#/c/609667/6 16:25:54 which is a bit stronger statement 16:26:00 so this is partly an awareness notice 16:26:06 but also, i'd think we'd want a spec outlining the proposed changes in os-brick? 16:26:55 how do we usually handle that? 16:27:25 rosmaita:do we have a cinder spec? 16:27:28 I don't think we have required a separate spec for os-brick in the past. 16:27:36 I could be wrong though. 16:27:52 hemna_: we have just the general spec 16:28:56 i just want to make sure everyone is on board with using os-brick for this 16:29:21 Yes, we did a lot of discussion around this and everyone reached agreement on os-brick rather than trying to create some other library. 16:29:45 It would be good if the spec detailed what changes are needed in os-brick to support this since cinder and glance are going to both dependent on those changes. 16:30:06 i've been attending the encryption team pop-up meeting and can put it on the agenda 16:30:13 can ask for a revision to the spec 16:30:24 #link http://eavesdrop.openstack.org/#Image_Encryption_Popup-Team_Meeting 16:30:25 rosmaita: ++ 16:30:33 Sounds like a good way to proceed. 16:30:38 ok, that's all from me, then 16:31:28 rosmaita: Thank you! 16:31:45 #topic py3.7 review underway 16:31:55 So, for awareness I have started the py37 review: 16:32:06 #link https://etherpad.openstack.org/p/cinder-py3-ci-review 16:32:26 Since I am going through all the CIs I am taking general notes in the etherpad as well. 16:32:43 Have a fear that the results of my investigation will become a long mid-cycle discussion. 16:33:28 good thing we have an otherwise light agenda 16:33:33 Regardless, I am going to keep working through the review and will present the results here next week before starting to push up 'unsupported' patches. 16:33:52 rosmaita: Yeah. For better or worse. 16:34:46 Anyway, that was all I had on that. Was for awareness more than anything and you can watch the results develop in that etherpad. 16:34:54 Do we need to restate the motivation and importance of this effort for anyone? 16:35:11 i'm pretty sure a few drivers have dependencies that don't state py3.7 support, that might be something to scan while looking through the drivers 16:35:34 rosmaita:brick seems like the right place for shared code for stuff related to volumes 16:35:50 eharney: Guidance on how to stop that if they are running py37? 16:36:10 jungleboyj: not sure what you mean 16:36:21 Not sure what you are saying maybe. 16:36:58 Do you mean there are a few drivers that don't support 3.7 because of dependencies that aren't ready? 16:37:16 i mean we can probably identify some drivers that are likely to have issues with this, if we want to 16:37:45 if we identify drivers that can't py3.7, we can just mark them unsupported for the release and let them fix their stuffs 16:37:46 Ok. If you know of ones that are going to have issues putting them into the etherpad would be helpful. 16:38:05 hemna_: Based on the stance we have made, that would seem to be waht we need to do. 16:38:44 Anything else on that discussion. 16:39:14 #topic open discussion 16:40:24 Any other topics for discussion today? 16:42:10 Going once. 16:42:15 Going twice .. 16:43:31 Ok. I guess that is all we have for today. 16:43:41 Thanks jungleboyj 16:43:53 jungleboyj: Thanks! 16:43:54 Thanks everyone for joining. Talk to you all next week! 16:44:00 #endmeeting