13:59:44 #startmeeting glance 13:59:45 Meeting started Thu Apr 25 13:59:44 2019 UTC and is due to finish in 60 minutes. The chair is jokke_. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:59:46 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:59:49 The meeting name has been set to 'glance' 13:59:50 #topic roll-call 14:00:04 #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 14:00:07 o/ 14:00:10 o/ 14:00:16 o/ 14:01:18 ok, lets get started 14:01:28 #topic release updates/periodic jobs 14:01:54 only 3 failures last week of which 1 is for master and other 2 for stable branches 14:02:10 also failures are related to translation 14:02:24 no subunit parser error or timeout issue in last week 14:02:45 have you looked into those translation failures? Did we screw up something or what's breaking there? 14:03:05 'propose-translation-update' this is the job which failed for master and stable branch 14:03:32 ++ ssh -p 29418 proposal-bot@review.openstack.org gerrit query --current-patch-set status:open project:openstack/glance owner:proposal-bot branch:master topic:zanata/translations 14:03:32 Host key verification failed. 14:03:37 this was the error 14:03:55 I don't think we messed up with something 14:04:05 this may be a known thing, i think sean and fungi were talking about something like that 14:04:16 has to do with hostname changes i think 14:04:20 also those jobs are passing now 14:04:30 ok, so nothing from our end, sounds like infra needs to fix the job (my best guess is related to the namespace change) 14:04:30 cool 14:04:42 nice :) 14:04:53 so nothing to worry about then 14:04:57 that sounds great 14:05:35 yes 14:05:44 anything else on this abhishekk? 14:05:48 nope 14:05:59 cool cool 14:06:09 #topic summit ptg planning 14:07:08 I'm bit delayed on my skeleton schedule but by the looks of it we get majority of out topics dealt with over Thu and Friday 14:07:09 rosmaita: yes, there were rogue virtual machines nova had lost track of in inap-mtl01 and the ops there had to find and delete them 14:07:17 fungi: thanks! 14:07:22 So Friday will be our glance_store day 14:07:27 they were getting into arp overwrite battles with addresses assigned to our instances 14:07:51 sounds like fun 14:07:52 fungi: thanks, and good that you guys got those figured out 14:07:57 indeed 14:09:06 rosmaita: did jay post the cinder schedule somewhere already? 14:09:06 tl;dr: openstack has bugs, and we get to experience them first hand 14:09:17 jokke_: yes, looking now 14:09:50 fungi: and that's good thing. Always good to find the nasty ones ourselves ;) 14:10:03 #link https://etherpad.openstack.org/p/cinder-train-ptg-planning 14:10:29 fungi: it's very sad to develop sw that you don't/can't run yourself 14:12:29 so back to ptg planning, Thu morn looks like we want to be spending pretty much with cinder :D 14:12:58 we also need one session with nova as well 14:13:50 one small session will be enough to share the idea 14:13:56 about? 14:14:04 I don't see anything in the etherpad 14:14:14 uploading snapshot to dedicated backend 14:14:32 "dedicated store" 14:14:45 Ohh, looks like I forget, could you please add it? 14:14:52 rosmaita, yes dedicated store 14:14:58 :) 14:15:07 :D 14:15:11 ok, lets see what we can do about that 14:15:39 thank you 14:16:12 I have PoC ready as per current design proposed for cinder and nova 14:19:02 rosmaita: anything in the cinder schedule you definitely do not want conflicting with our topics? 14:19:31 looking 14:20:02 rosmaita: I assume you will be spending most of your time in the cinder room, but if there is something you specifically want to take part of (apart those glance/cinder cross projects) and you have slot what would suite you, let us know 14:20:23 ++ 14:20:27 yeah, i am kind of unorganized ATM 14:20:47 by the looks of it, we have lots of flexibility and we definitely want to accommodate you as much as possible 14:21:01 thanks, appreciate it 14:22:00 'cause we can use the time we're just two of us with abhishekk hacking and going through ptl stuff etc. 14:22:19 so gaps here and there won't get wasted anyways 14:22:19 ++ 14:22:26 ok, cool 14:23:28 _and_ I need to look the other teams schedules though a bit 'cause I think there might be some stuff outside of our schedule I should try to squeeze into mine as well 14:25:01 Also how do you guys feel trying to timebox an hour somewhere on those 3 days under "Come and talk to Glance", just for anything people can kind of bring up to us we have possibly missed? 14:26:04 ls 14:26:11 could be useful 14:26:15 agree 14:26:20 sorry guys :( 14:26:30 erolg: np ;) 14:26:40 I assume wrong window in focus :D 14:28:58 rosmaita: do you have time today to look into those schedules and flag any topics on our planning? I'll definitely try to get the skeleton together tonight (might be late) 14:29:27 i will do that 14:29:58 before 16:00 utc 14:30:07 gr8, I think only things that you're marked as driver are the cinder ones so they should be easy 14:30:19 yeah 14:30:58 also like said we have room, so anything else we have forgotten from our topic list, poke them in today and we can see what we can do about them 14:31:14 ack 14:31:43 Otherwise I'll utilize that extra time to sit down with abhishekk and/or attending sessions outside of glance planning 14:32:00 ok 14:32:25 ack 14:32:37 moving on 14:32:40 #topic Reopen bug "glance-image-import.conf not parsed when running under wsgi" 14:32:59 rosmaita: so our unsupported wsgi deployments keeps popping up 14:32:59 yeah, i ran into this again 14:33:14 well, it's our supported wsgi deployment 14:33:25 happens when you run the official glance wsgi server 14:33:48 i put some notes at the bottom of the bug 14:33:55 ohh ... you mean when you run under pastedeploy? 14:34:00 #link https://bugs.launchpad.net/glance/+bug/1775782 14:34:01 Launchpad bug 1775782 in Glance "glance-image-import.conf not parsed when running under wsgi" [Critical,Triaged] 14:34:23 it's when you run /usr/bin/glance-api 14:34:28 rosmaita, I will have a look tomorrow, I am pretty much sure whatever workarounds I have added I have tested those 14:34:43 it could be that something changed in oslo.config 14:35:03 all i know is that when i only use --config_dir=/etc/glance , it doesn't start 14:35:10 well it does 14:35:19 it's just running on the same port as the registry 14:35:27 and tls-proxy cannot find it 14:35:42 so it's ignoring the bind_port in the config file 14:36:12 luckily, no one runs devstack in that configuration, so there haven't been complaints 14:37:03 but yeah, abhishekk if you can take a look and see how you think we should proceed on that 14:37:14 rosmaita, ack 14:37:32 i was using a fresh devstack from master (train) over the weekend when i saw this, btw 14:37:58 ok just read through the bug again 14:38:13 we need to figure out way to test this 14:38:23 yes 14:38:26 so this doesn't keep surprising us time after time 14:38:42 i know, it's an enormous pain 14:38:46 and any idea how far back this is broken again, I guess Stain is fecked? 14:39:01 but that's why i think having our code explicilty look for the image-import-conf is the best solution 14:39:15 we do it in uwsgi, should do it in "normal" configuration too 14:40:35 sorry my network is slow, so I am getting replies very late 14:40:45 rosmaita: makes sense, perhaps have test under integration or functional that literally just spins up the process and checks that a config option from that file is available, if not we know something is fishy again 14:40:53 jokke_: don't know, possibly back to queens 14:41:02 ffs 14:41:21 when was the image-import conf introduced? 14:41:51 during queens I guess 14:42:03 anyway, my problem in testing this has been having my own config lying around 14:42:11 likely, that bug was opened at mid Rocky 14:42:44 this bug was reported during early rocky phase i guess 14:43:01 so one problem is that we all know the workarounds (more or less), this api coming up on the registry port is fairly recent 14:43:44 anyway, it's still connected with the freaking uwsgi stuff 14:43:56 that, should be solved this cycle unless tempest decides to screw us over with registry removal as well 14:44:09 who knows!!! 14:44:18 do you have a session with QE team scheduled? 14:44:29 i would def like to be present for that one 14:44:43 or instead of making changes in devstack can we follow this option paste.openstack.org/show/722963/ 14:44:48 mhm ... I do have solution for those issues, 'though ... won't get me any new friends but we can deal with that when the time comes :P 14:45:02 we have default viz, running glance not in uwsgi, and registry removal 14:45:18 abhishekk: that's what i am talking about, i think we should do that on our side 14:45:27 and probably revert my chanage to use config-dir 14:45:40 ack 14:45:42 rosmaita: one of those "other project topics" I was referring to ... looking for QA office hour again 14:45:44 i think we need to tell systemd to use the config-file 14:46:01 and then we look for the import file ourselves, basically like on that paste iirc 14:46:29 i think there's a way to give oslo config a file and have it tell you the directory it's in 14:46:44 i think sean used it in an upgrade check for cinder 14:47:01 also he figured out how to do a unit test 14:47:08 gimme a min to find the patch 14:47:15 ack 14:48:27 rosmaita: sounds good 14:49:24 we just need to figure out something which keeps us working and not having this issue popping up every now and then. If that means that we hardcode the config files we expect to see, so be it 14:49:51 sounds good 14:50:38 anything else about this? 14:50:41 abhishekk: i think this is the patch i'm thinking of 14:50:49 #link https://review.opendev.org/#/c/647937 14:50:54 looking 14:51:01 #metoo 14:51:29 in cmd/status.py, he looks for the policy.json by finding the cinder.conf 14:51:53 anyway, may or may not be helpful 14:52:06 can be useful 14:52:33 that is indeed interesting approach ... I like it 14:52:48 yeah, especially the unit test, able to use oslo.config and also a mock 14:53:17 yup 14:54:50 5 min 14:54:55 anything else on this? 14:55:35 no, as long as we address soon 14:55:41 we can talk at ptg 14:55:51 i have puppy madness going on here, brb 14:56:02 nothing from me 14:56:14 kk 14:56:20 #topic open discussion 14:56:34 2 things, I sent the mail about coming meetings 14:56:47 collect swags for me as well :p 14:57:05 yes, I saw it 14:57:05 and I have not forgotten that I promised to take care of the spec housekeeping 14:57:29 that will happen this week so we are clean for the summit/ptg 14:57:39 cool! 14:57:56 just wanted you to know that I did not forget 14:58:21 anything else from you guys in general? 14:58:32 nope, safe journey 14:58:40 yes, safe travels, all! 14:58:43 Safe travels everyone! 14:58:55 when are people arriving? i get in like 2am monday morning 14:58:57 So exited to see you guys f2f again next week 14:58:58 next week we will be together \./ 14:59:17 I'll be there at Sun evening ... landing 17:30 or something like that 14:59:19 yes, will be on telegram, will be good to see you both 14:59:29 Wednesday evening 14:59:38 yes same Telegram or WhatsApp reaches 15:00:07 #metoo 15:00:08 ok, cool, will look forward to seeing everyone 15:00:11 #endmeeting