14:03:14 #startmeeting glance 14:03:15 Meeting started Thu May 17 14:03:14 2018 UTC and is due to finish in 60 minutes. The chair is jokke_. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:03:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:03:17 o/ 14:03:18 The meeting name has been set to 'glance' 14:03:20 #topic roll-call 14:03:22 o/ 14:03:28 o/ 14:03:29 o/ 14:03:30 o/ 14:03:36 #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 14:04:37 sorry about all the stuff i added to the agenda, but i am working remotely and may lose connectivity 14:04:46 ok, lets get started, we have a lot on our plate 14:04:54 #topic updates 14:05:20 #info no meeting during the Summit week 14:05:41 So next week we will not have a glance meeting, I'll send mail out after this one 14:05:52 ok 14:06:27 second thing, our specs are still lacking reviews/acs 14:06:42 #action all review pending glance-specs 14:07:08 Are there any in particular that we should prioritize? 14:07:57 probably abhishekk 's multistore? 14:08:13 I have some feedback queued up for that still 14:08:14 we're approaching spec freeze, If it's your -2..+2 I just want to have ack specially from all the cores (appreciated from rest) to the specs we have open and are in the glance-rocky-priorities 14:08:22 I reviewed it twice so far I believe 14:08:35 will grateful to have reviews 14:08:47 #link https://etherpad.openstack.org/p/glance-rocky-priorities 14:09:27 and please if there is concerns on your spec, do revisit them asap so we get to an agreement and can merge them and work on the features 14:10:00 OK 14:10:21 ok 14:11:48 last update from me is, in case someone missed the memo, I'll be off the week after summit. I'll be in the West-Coast of US so anything urgent that needs my attention will be reacted on late hours 14:12:14 ack 14:12:22 Telegram, WhatsApp etc. reaches and I'll try to have a peak on my work mail at least daily 14:12:34 ack 14:12:54 cool I reorder the agenda bit as I wasn't sure if there was release updates 14:13:00 #topic release updates 14:13:10 just a few reminders 14:13:22 rocky-2 milestone is week of june 4 14:13:29 that is also spec freeze date 14:13:45 and, we have a bug scrub scheduled for friday june 8 14:14:25 We probably won't be processing releases next week, but if anything comes up that is important let me know and we can get it out. 14:14:26 jokke_ you will be back for week of june 4, right? 14:14:41 yes 14:14:55 I'll be coming home over the weekend 14:15:31 oh yeah, last thing since no glance meeting next week 14:15:46 next bug squad meeting is monday may 28 14:16:02 that is all from me 14:16:15 still at some super early time eastern rosmaita? 14:16:31 rosmaita: will you take chair on the Thu 31st of May meeting so we do not miss 2 of them? 14:16:31 yeah, 10:00 utc i think? 14:16:36 Thats not as bad 14:16:42 jokke_ will do 14:16:49 ty 14:17:23 anything else on the updates? 14:17:25 McClymontS that's UTC time 14:17:32 right so 6 am east 14:17:41 yeah 14:18:04 Cool, I will try to make one 14:18:48 ok, moving on 14:18:58 #topic Tip tests 14:19:47 So, the glanceclient test issues (which rosmaita is going to talk next)revealead one lacking thing in our testing 14:20:12 we test only released dependencies, meaning these failures will come to us most of the time as surprise 14:20:24 :) 14:20:36 Zuul allows us to test the tips of the repo if we so choose 14:20:57 and I would like us to do so for the openstack repos we depend on 14:21:36 but I do not want to block us as soon as something merges that breaks us, as it might be that such thing will not end up to the release at all 14:22:36 we have basically 3 options. Either we get periodical test job ran, which runs our tests against the tips, problem with this is, that no-one really follows those periodical tests 14:23:55 the second option is to have non-voting -tips test ran on every patch we upload, this obviously increses the load on infra, might make the tests even longer what they are now and the problem is the same. Pleople tends to ignore non-voting tests 14:24:14 i think maybe periodical, and make it the release manager' 14:24:24 s duty to check each week 14:24:38 +1 14:24:40 or, we make them run wendesday night so that they are always done before glance meeting 14:24:51 3rd option would be to make the -tips test to experimental pipeline, which would need someone manually triggering the tests ... again not happening often enough 14:24:53 then we could make it part of glance meeting to look 14:25:38 does anyone know how to set up periodical jobs? 14:25:48 i guess they have them set up on the stable branches 14:26:19 yeah, it's same as setting any other jobs into zuul, just need to set the pipeline to periodical 14:26:33 oh, then that's not a big deal 14:26:50 i will do an experimental patch later today 14:27:11 I think the periodical tests runs every night during the quiet hours 14:28:04 so are everyone ok with the idea of it being periodical test and release managers duty to keep eye on them weekly? 14:28:06 may be day time at my end then 14:28:27 ok for me 14:28:36 sounds good, just something to report on at the weekly glance meeting 14:28:51 yeah 14:29:45 #agreed -tips tests to be setup as periodical and release liaison keeping eye out for them and reporting status on the teem meeting updates 14:30:21 rosmaita: you'll put the patch up? Can you also add it to the docs on the rel liaison duties? 14:30:32 yes, will do both 14:30:55 #action rosmaita to setup the job and update rel liaison duties into the dev documentation 14:30:58 ty 14:31:02 i'll put keystoneauth as library to test, we can add others as we think of them 14:31:59 rosmaita: just walk through the requirements.txt keystoneauth is obvious, swift client, cinder client and brick; and probably the oslo. stuff 14:32:29 ok, that's a good list to start with 14:32:31 those should cover majority 14:32:37 gr8 14:32:48 #topic pthon-glanceclient gate status 14:32:51 rosmaita: floor is yours 14:33:09 ok, so the glanceclient py35 gate is currently broken 14:33:23 details on the agenda 14:33:31 i will go directly to status 14:33:44 we need keystoneauth 3.6.2 to be released 14:33:57 then we need u-c to be changed to allow 3.6.2 14:34:16 then i have a patch that we need to merge for glanceclient 14:34:24 and then we should be back to normal 14:34:29 (more or less) 14:34:51 my patch is https://review.openstack.org/#/c/568698/ 14:35:09 ok, any indication if keystone is gonna release that before the summit? 14:35:21 do we have workaround if not? 14:35:28 release patch is up 14:35:34 ok, brilliant 14:35:48 i don;'t know if the u-c change is proposed by bot, or if we have to do a manual one 14:35:51 which just got approved 14:35:56 cool 14:36:03 I guess it is proposed by bot 14:36:40 ok, then hopefully it will be proposed soon, i will keep a lookout and push it in release channel where most of the requirements people hang out 14:37:03 so, i do want people to read the "fallout" section on the agenda 14:37:22 as far as i can tell, my fix does not break any tests 14:37:41 but ... whether it doesn't break *anything* depends on how good our test coverage is 14:38:13 we'll see 14:38:40 yeah, i am a little worried about glance's use of keystoneauth1 14:38:43 so expectation is that the gate is unblocked today still 14:39:43 possibly 14:40:01 depends on the u-c patch and then my https://review.openstack.org/#/c/568698/ merging 14:40:22 yeah, lets keep eye on those while reviewing the specs ;) 14:40:24 could use some eyes on that patch to make sure the fix makes sense 14:41:01 i tried to explain clearly in commit msg and comments in the code 14:41:11 #link https://review.openstack.org/#/c/568698/ 14:41:42 yeah comment you have written helps to understand the code 14:41:43 #action all eyes on the rosmaita's client patch 568698 to unblock gate 14:42:03 and please read the "fallout" on the agenda 14:42:39 that's all from me unless people have questions 14:43:37 nothing for now 14:43:49 Im good 14:43:56 #topic Open Discussion 14:44:04 anything else? 14:44:26 Nothing from me 14:44:33 I'll see some of you in Canada 14:44:46 yes, let's plan to meet up at the glance update session 14:44:46 all who are attending the summit, safe journey and enjoy the summit 14:44:51 abhishekk thanks! 14:44:59 Thank you abhishekk 14:45:00 yeah def for those of you coming to Vancouver, safe travels, can wait seeing ye all 14:45:07 :D 14:45:24 I will look through the agenda out there and lets grab a team dinner again 14:45:25 glance update is monday, and we can plan meetings to discuss specs, etc. 14:45:34 jokke_ ++ 14:45:50 don't think there is a distillery tour in vancouver :( 14:45:55 share photos ;) 14:46:05 bummer that jameson's got snowed out in dublin 14:46:10 so if you have corp team nights out or something else blocking specific nights, please let me know asap 14:46:27 jokke_ I am pretty booked most nights but will try to make time for sure 14:46:35 Can skip something I am sure 14:47:39 McClymontS: it's pretty normal on summit week that every night has something going on. These thing quite often end up being dinner + roaming for drinks and socializing with the groups whose dinner was missed 14:47:47 Just keep me posted on plans 14:48:02 oh absolutely jokke_, but I'd like to meet up with out a doubt 14:48:06 so get used to the idea of rough week and long nights :P 14:48:13 So let me know when and where, rosmaita has my number 14:48:24 ++ 14:48:34 that would be great, I'll put up dinner etherpad and send that to the mailing list as well today 14:49:05 Awesome sounds great all 14:49:10 #action jokke_ to put up Glance Summit Dinner etherpad for planning 14:49:12 I look forward to seeing you guys 14:49:16 likewise! 14:49:19 likewise 14:49:27 rosmaita: there is a distilery in gastown fyi :P 14:49:32 ok mates if nothing else, see you in week after summit 14:49:35 if nothing else, lets free up the 12min for something productive! 14:49:39 thank you all :D 14:49:42 Awesome 14:49:48 ok! have a good day everyone 14:49:51 thanks all 14:49:58 and a good evening to abhishekk 14:50:00 #endmeeting