14:00:26 #startmeeting glance 14:00:27 Meeting started Thu Feb 13 14:00:26 2020 UTC and is due to finish in 60 minutes. The chair is abhishekk. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:28 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:30 The meeting name has been set to 'glance' 14:00:31 :) 14:00:37 #topic roll call 14:00:39 o/ 14:00:43 #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 14:00:46 o/ 14:00:53 jokke_, thank you :P 14:01:05 lets wait for 2-3 minutes 14:01:17 mhm 14:02:47 looks like only two of us 14:02:59 Lets start 14:03:37 #topic release/periodic jobs update 14:04:04 So we are planning to release milestone 2 today 14:04:40 and yes most importantly all targeted patches are in gate and will be merged in next couple of minutes 14:04:49 cool, I think everything needed should be gating 14:05:06 yep, gr8 14:05:08 Thank you jokke_ smcginnis and Brian for your support and efforts 14:06:16 2 patches, copying image and example config got merged 14:06:26 looks like we got one more to go :) 14:06:33 One patch is in gate which will merge within 15 minutes 14:06:44 for once not needing to wait for the release patch until silly hours 14:07:00 \o/ 14:07:23 So I will update the release hash in release patch submitted by smcginnis 14:07:41 will add jokke_ as a reviewer for hash confirmation 14:07:50 now when the import changes has been merged, I will revisit my client patches and have them ready hopefully by tomorrow 14:08:03 cool 14:08:25 If we able to release today, I am planning to take a day off tomorrow 14:08:38 that sounds like well deserved 14:08:57 jokke_, regarding client changes in which command you will make changes for copying patch? 14:09:06 i guess import command only like? 14:09:17 yup, that was the plan 14:09:38 just need to provide a way for the cielt to provide the new key/value pairs and booleans into the json 14:09:45 should be really straight forward 14:09:51 cool, then do we need to handle create_image_via_import as well? 14:10:12 Fingers crossed.. 14:10:24 yeah, I'll add the switches there for the multi store imports 14:10:41 Only problem is it should not messed with image-schema (for --stores option) 14:10:45 will keep them in 2 separate patches 14:10:50 awesome 14:11:22 rosmaita, o/ 14:11:33 o/ 14:11:35 so we are discussing regarding milestone 2 14:11:45 will need to double chck but I don't think we have schema for the import body 14:11:52 rosmaita: o/ 14:11:55 hello 14:12:10 and all patches which were required are merged and one is in gate 14:12:19 very nice 14:12:21 So we are good to release M2 today 14:12:25 i am way behind on reviews 14:12:45 jokke_: i'm not sure either... was going to say no schema, but now i'm not sure 14:12:47 the one gating is really good catch from Vlad Gusev. Good to get in 14:12:59 i may be confusing it with the task schema 14:13:07 I am talking about create_via_import_command 14:13:15 for that we are using schema i guess 14:13:32 abhishekk: it's not gonna touch anything but the final import call anyways 14:13:38 jokke_, ++ 14:14:06 All right then, we are covered in all aspects 14:14:07 the image-create-via-import is just wrapper that call image create api, if needed, stage and finally import in one cli command 14:14:24 ack 14:14:38 Let me know if you need help in tests :D 14:15:00 Regarding periodic job, I guess 2-3 timeouts are there 14:15:25 The patch to unblock oslo.config 7.0 is merged 14:15:35 I think the patches I have has pretty decent test coverage (I know surprised myself too!!!) they just have wrong keys there as the thing chnges few times during reviews 14:16:12 rosmaita, is there anyway to trigger the periodic job manually to trigger that periodic job? 14:16:18 jokke_, great 14:16:39 rosmaita, I am talking about this job openstack-tox-py36-with-oslo-master 14:17:10 abhishekk: ref manually triggering periodic jobs, not that I know of. I think we just need to wait until tonight for it to run or infra might have a way to execute them if you ask very nicely 14:17:14 abhishekk: what you can do is put up a patch with a change to .zuul.yaml making that job experimental 14:17:29 or maybe not 14:17:47 make it the only job that's there 14:17:54 i am being vague 14:18:03 gimme a sec to pull up zuul.yaml 14:18:14 I will try that once I will be back after 2-3 hours 14:18:21 didn't think of that, rosmaita's hax might actually work 14:18:42 No worries we don't have anything to discuss today 14:18:43 i think that's what i had to do when testing these out 14:19:55 I have changed requirements.txt locally and ran tests it was working in local environment but I guess better it should be confirmed by periodic job 14:19:59 yeah, i think you can just hack .zuul.yaml, change 'periodic' to 'check' after first removing the current stuff above periodic 14:20:27 so remove 'templates:', "check:", "gate", "experimental:' 14:20:44 and then change periodic to check and submit the patch 14:20:57 will do that afterwards (hopefully I know how to do that) 14:21:06 i will be online all day, ping me 14:21:13 cool 14:21:17 abhishekk: is there a particular job you want to see? 14:21:25 yes 14:21:26 or all of them? 14:21:27 openstack-tox-py36-with-oslo-master 14:21:30 openstack-tox-py36-with-oslo-master 14:21:40 abhishekk: is on fire today :D 14:21:51 :D 14:21:53 ok, i have a few min now, i will submit a patch and you can check later and see if it worked 14:22:14 rosmaita, awesome, thank you 14:22:21 np 14:22:32 Moving to open discussion 14:22:44 #topic Open Discussion 14:23:03 I will update the release patch in next 5-10 minutes 14:23:07 btw, I patch up for removing all the registry conf/configgen stuff, forgot that we have doc generation there as well. Just wanted to ask if you agree getting rid of those as well before I fiddle more with it? 14:23:55 jokke_, If you submit the patch now, depending on gate I can wait for next 3 hours for it to merged 14:24:28 But I am not sure how gate will behave (timeouts, parser error etc) which might delay the M2 release 14:24:31 I think we got rid of the registry tests already and the config are just massive change hog on every time we update the examples 14:24:49 I agree on that 14:24:58 abhishekk: I think we should try to get the tag in and leave that for next milestone/rc 14:25:10 +2 14:25:19 just cam to my mind to push it up to review when I saw your update configs patch :P 14:25:45 While you are working on client patch, I will work on removing registry code 14:25:57 :D 14:26:00 I'll fix it but don't hold the m2 for it 14:26:17 cool 14:26:28 so last patch we were waiting has just merged 14:26:33 we are good for release 14:26:37 \o/ 14:26:47 well you are going to beat cinder! 14:27:04 there was an update to reno that has borked our ability to release 14:27:14 ohh 14:27:22 something about the kilo-eol tag freaking it out 14:27:24 rosmaita: sounds fun 14:27:28 smcginnis is on the case 14:27:40 hope it will be fixed soon 14:27:49 Do we have anything else to discuss? 14:28:17 I had something else in my mind but totally forgot what it was, so can't be that important 14:28:26 We can wrap this up 30 minutes early 14:28:52 If you happened to remember, I will be around after 2-3 hours, we can discuss then 14:28:53 I hopefully have the decompressor plugin ready for next week 14:29:00 but that was not it 14:29:06 ok, cool, i will use that time to put up the test patch 14:29:07 cool 14:29:14 great 14:29:14 Oh! and another thing (which wasn't it either) 14:29:37 shoot 14:30:14 I will be in Barcelona next week for OSP16 hackfest. So might be poking you guys if there is any questions I cannot answer and otherwise bit less reachable than usuaa 14:30:16 l 14:31:09 also don't expect feature work from me next week, but I might throw some bugfixes up 14:31:48 So for the record this is our (RH) field team testing Train based release 14:32:18 great 14:32:30 All the best and enjoy the hackfest 14:32:48 jokke_, should I hold python-glanceclient release? 14:33:15 smcginnis, has submitted a patch for it, and I have hold it so that we can get our client changes in 14:33:33 #link https://review.opendev.org/#/c/707007/1 14:33:35 abhishekk: yeah, I'll try to have the client patches up today or tomorrow, if you don't mind lets get those reviewed quick and you can tag client early next week 14:33:50 jokke_, ack 14:33:52 sounds good to me 14:33:53 It can wait a bit. 14:33:54 o/ 14:34:09 that way we have the features to utilize the m2 features in the client 14:34:10 smcginnis, I will put a glance release patch shortly 14:34:22 will add you all as a reviewer there 14:34:23 that's all from me 14:34:32 Great, I'll take a look later after I get out of this meeting hell. :) 14:34:33 sounds good 14:34:38 still can't remember what I wanted to talk about 14:34:41 (not this meeting, other meetings) 14:34:48 smcginnis, cool, thank you for reviews 14:34:56 I need to get better putting stuff into agenda as soon as I think of something like that 14:35:16 lets wrap this up 14:35:16 jokke_: If it was really important, it will come back and remind you. ;) 14:35:26 Thank you all 14:35:27 :D 14:35:41 smcginnis: yep, can't be that important as I haven't been able to recall it for past 20min 14:35:45 thanks all! 14:36:10 #endmeeting