16:01:50 #startmeeting Cinder 16:01:51 Meeting started Wed Aug 14 16:01:50 2019 UTC and is due to finish in 60 minutes. The chair is jungleboyj. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:52 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:54 The meeting name has been set to 'cinder' 16:01:56 I am here. 16:02:03 hi 16:02:06 o/ :) 16:02:10 hi 16:02:15 hello 16:02:17 @!j 16:02:17 <_pewp_> jungleboyj (._.) ~ ︵ ┻━┻ 16:02:28 courtesy ping: jungleboyj whoami-rajat rajinir lseki carloss pots woojay erlon geguileo eharney rosmaita enriquetaso e0ne smcginnis davidsha walshh_ xyang hemna _hemna tosky 16:02:39 o/ 16:02:44 o/ 16:02:46 hi 16:02:48 hi 16:02:51 o/ 16:02:58 Hi 16:03:39 @! 16:03:39 <_pewp_> jungleboyj (*´・д・)ノ 16:03:39 o/ 16:04:29 Ok. Lets get started. 16:04:48 #topic announcements: 16:05:10 Hopefully everyone knows by now that we have the mid-cycle next week. 16:05:21 #link https://etherpad.openstack.org/p/cinder-train-mid-cycle-planning 16:05:36 Please add topics to the etherpad so that this is a productive time for us all. 16:05:48 * jungleboyj glares at smcginnis for abandoning us 16:05:51 ;-) 16:05:52 :P 16:06:37 We have a good start in there. I am going to go through our PTG and last mid-cycle notes I know there are to-dos in there that haven't been addressed. 16:06:49 I will cover more details later in the meeting. 16:07:02 That was all I had for announcements. 16:07:23 #topic cinderclient CLI version negotiation needs a look 16:07:39 #link https://review.opendev.org/#/c/664430/ 16:07:47 well, mostly asking for reviews here, Sean gave some feedback that i added more information around 16:07:55 also wanted to check in on the whole major version bump plan in general 16:08:34 eharney: I thought this was what we were already doing. 16:08:34 Just added this to the midcycle etherpad - https://review.opendev.org/#/q/status:open+project:openstack/python-cinderclient+branch:master+topic:major_bump 16:08:54 We need to coordinate that work and make sure we get everything we want in. 16:09:26 smcginnis: ++ Sounds good. 16:10:03 I don't really like that there is now error for using a version that is newer than what you requested but if that is what Nova does we should be consistent. 16:10:30 I suppose you are going to get some sort of error anyway because what you are trying to do isn't supported yet. 16:11:34 I guess I would feel better if we had documentation and a release note indicating that behavior to go with the patch. 16:11:47 that makes sense 16:12:24 so we're going to aim to land all of the major bump patches somewhere close to the client freeze deadline? 16:13:23 eharney: Yeah, we should put group review of the patches early in the mid-cycle so we can try to shepherd things through. 16:14:01 ok 16:14:04 do we show a msg to user regarding the set version is higher than maximum and the max api version is used instead? 16:14:33 whoami-rajat: That would be consistent and create a better UX. 16:15:20 not sure i follow 16:15:46 At least put out a 'WARNING' type message that it is falling back. 16:16:05 If they try, it doesn't work, they run with debug on or whatever they at least get more info. 16:16:14 if a user sets OS_VOLUME_API_VERSION = 3.90 and max version supported is 3.56, the user should know 3.90 doesn't exist or isn't supported and their max version supported is 3.56 16:16:56 i just modeled the behavior here after how things already work in nova and manila 16:17:15 jungleboyj: ++ 16:17:21 printing warnings gets interesting with the "i have a script that parses CLI output" user base 16:17:33 eharney: Right. 16:17:56 I think the concensus I've seen lately has been that CLI output is not an API. 16:18:24 smcginnis: That is a good consensus. 16:18:25 except for the CLIs that output json/csv? 16:18:34 well you can emit warnings and such to stderr 16:18:40 true 16:18:46 clarkb: ++ 16:18:47 and output regular content that scripts might care about to stdout 16:19:01 That makes sense to me. 16:19:27 clarkb: +1 16:19:50 clarkb: ++ 16:20:04 eharney: Are you ok with that approach? 16:20:17 adding a warning message if the requested version is downgraded? yes 16:20:39 MVs are confusing and a PITA as it is. Anything we can do to make them less confusing is good. 16:20:50 eharney: Right, but don't change functionality. 16:22:08 i'll try to get some doc and examples together for next week 16:22:55 eharney: Sounds good. 16:22:58 Thank you! 16:23:12 That is a good change to get in. I thought we already had that done. :-) 16:23:33 Anything else on that topic? 16:23:40 nope 16:23:45 Okie Dokie. 16:23:53 So, details for next week. 16:24:05 #topic Details for Next Week's Mid-cycle 16:24:29 I have put my Cell phone in the etherpad. 16:24:42 I have also added my arrival/departure times. 16:25:15 For those of you that didn't see I am timezone challenged. So, we won't be meeting until 10 am because that is all the earlier I reserved the room and I couldn't get anything else. 16:25:25 So, we will have kind-of lazy mornings. 16:25:46 I am bringing the usual recording equipment and the room should be much the same as last time. 16:26:40 Rather than dealing with food service figured we would just make trips to the cafe downstairs for coffee and snacks when people want. Lenovo will cover. It is cheaper and easier that way. 16:26:54 * jungleboyj should find my badge. 16:27:02 i think we should all bring headsets so we can all get into zoom or whatever if necessary 16:27:15 make it easier on the remote attendees 16:27:31 Sure. Can do. I am hoping I might have Zoom working but I am not sure. 16:27:35 rosmaita: ++ 16:27:48 rosmaita: That is a good idea. Hadn't thought of that before. 16:28:19 Supposedly my trial Zoom account ends this week but I haven't seen any indication of that. 16:28:40 i think we could use my bluejeans account if necessary 16:28:52 rosmaita++ 16:28:54 rosmaita: ++ Oh, that would be so much better. 16:29:26 Assume we can record those. 16:29:33 i think i can even record in bluejeans, but need to check 16:29:40 maybe eharney knows? 16:29:43 Sweet. 16:29:48 it records, but may have some time limit 16:30:05 ok, i will take an action item to get that info today 16:30:30 I will still record to YouTube to be safe and to keep that record. 16:30:50 rosmaita: Check out what is possible and we can coordinate to be ready for next week. 16:30:56 ack 16:31:24 Using some sort of official meeting platform would be good though. 16:32:30 Any other questions/concerns? 16:32:50 Assume we will do the usual lunch together and grab dinner afterwards one night. 16:33:03 or both nights. 16:33:05 :-) 16:34:17 I am planning that we should be able to wrap up by mid-day Friday. If not I do have one conflicting meeting that I will need to step out for at 1:30. 16:34:50 Then we have the big party at eharney 's house on Friday night. 16:34:57 :-) 16:35:01 sweet 16:35:06 :) 16:35:12 Wondered if IRC was still working. Had to check. 16:35:30 Ok. Any question/concerns on that topic? 16:35:37 nope 16:36:23 nope 16:36:27 Ok. That was all I had on the agenda. 16:36:34 #topic Open Discussion 16:36:52 As usual, if you are a remote attendee watch the Etherpad and IRC for details. 16:37:37 Anyone have other topics for today? 16:37:52 Hi team, looking forward to reviewing https://review.opendev.org/#/c/668825/ 16:38:51 zhengMa: Sure. Will make sure to take a look through that. 16:39:38 And more, there's a similar patch https://review.opendev.org/#/c/674758/ , do we have to do some changes because of this? 16:39:50 jungleboyj: thank you! 16:40:05 i don't think you have to change anything because of that patch 16:40:25 eharney: ++ 16:41:47 eharney: thank you, but will the compression configuration be confusing? 16:42:36 your feature only does anything if you choose to upload as a new format to glance, right? 16:43:06 that's right 16:43:19 the other one only applies compression transparently inside of the qcow2 format 16:43:32 and doesn't require any particular configuration etc 16:43:42 so i think it's ok 16:43:57 eharney: ok, got it, thank you 16:44:41 Anything else for today? 16:44:48 So i've the base frame of the bp ready, i still need to optimize the tests but would appreciate reviews on the functional code 16:44:49 cinder : https://review.opendev.org/#/c/639180/ 16:44:49 cinderlib : https://review.opendev.org/#/c/674826/ 16:46:41 Wheee, that is a big patch. 16:46:50 Ok. Will find some time to look at that. 16:46:53 whoami-rajat: Thanks for working on that. 16:47:45 jungleboyj: np, the existing tests needed to include the volume type that made the patch big 16:47:48 That would be good to get reviewed and agreed upon before the end of the mid-cycle as well since there was some controversy over it in the past. 16:48:00 jungleboyj: i will try to minimize it more 16:48:24 jungleboyj: thanks! 16:48:43 Anything else? 16:49:03 Nothing from my side 16:49:12 Ok good. 16:49:34 Just a note that we won't have this meeting next week as it will be during the mid-cycle. So we will just be having one big meeting. :-) 16:50:19 I think that is it for today then. 16:50:29 Thank you everyone and I look forward to seeing some of you next week. 16:50:43 bye! 16:50:45 #endmeeting