14:01:27 #startmeeting glance 14:01:28 Meeting started Thu May 25 14:01:27 2017 UTC and is due to finish in 60 minutes. The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:29 #topic roll call 14:01:31 The meeting name has been set to 'glance' 14:01:40 o/ 14:01:50 o/ 14:01:53 o/ 14:02:06 sorry for the late start, i was catching up on the dev list 14:03:25 ok, guess we have a quorum, here we go ... 14:03:33 #topic updates - happy towel day 14:03:39 https://lemonly.com/wp-content/uploads/2012/05/Towel-day-Infographic2.jpg 14:03:47 might as well have something to be happy about! 14:03:59 #topic updates - glance personnel situation 14:04:27 guess you've seen the ML ... stevelle, dharinic, and hemanthm have all stepped down from glance-core 14:04:41 https://s-media-cache-ak0.pinimg.com/736x/f4/99/cf/f499cffdba28e5ae3854a012d8314d4e.jpg 14:04:54 yeah :( 14:05:06 mfedosin: :) 14:05:18 they all leave big holes in the project 14:05:40 especially hemanthm , who was coresec and the release CPL for pike 14:05:45 right :( 14:05:59 and P-2 is coming up in 2 weeks, i believe 14:06:07 soon 14:06:54 I quess I assume the release liaison role as I've done it before 14:07:07 jokke_: that would be very helpful 14:07:12 I've created a topic about my return to core team... 14:07:25 mfedosin: i saw, item 6 14:07:34 let's move it up and discuss now 14:07:37 we can discuss it now or postpone it to 6 14:07:39 what's your current situation? 14:08:23 I'm working on Glare :) 14:08:39 that's nice :) 14:08:48 and I think will continue for several months 14:09:14 but I talked to my manager and he approved my desire to take part in the Glance project. 14:09:24 that's good 14:09:33 especially because glare and glance have much in common 14:09:34 :) 14:10:01 I've implemented a lot of tests for glare that can be applied for glance, for example 14:10:09 So I can spend some time reviewing the code and writing small patches. 14:10:59 so yes, I want to return and help the project 14:11:01 more tests would be good 14:11:05 as much as I can 14:11:06 mfedosin: good to hear that 14:11:12 and your help would be appreciated 14:11:25 I constantly receive messages in the IRC and by mail with a request to review something. 14:11:26 i don't know whether this is an appropriate request, but here goes anyway 14:11:35 in glance or related projects 14:11:54 can we agree not to discuss anything about glance-glare project integration until the Queens PTG? 14:11:57 But unfortunately without the core status my actions are hardly useful. 14:12:10 okay :) 14:12:19 rosmaita: ^ 14:12:28 cool, we just don't need the extra distraction 14:12:36 but we definitely need the help 14:13:01 as I said - I'll try to do as much as I can 14:13:15 my feeling is that you are a high-quality engineer, and you certainly know the glance code base well 14:13:15 What do you think? 14:13:58 And I know how bad the code is :) 14:14:08 not "bad", just "special" 14:14:11 :) 14:14:25 here's my honest opinion 14:14:37 ordinarily, i'd wait a bit and let you do more reviews, etc. 14:14:43 but these are not ordinary times 14:15:03 so unless someone here has an objection 14:15:21 i will propose your reinstatement to the ML, and we can see what hte rest of the community thinks 14:15:22 should I write an email somewhere? 14:15:31 i'll do it 14:15:42 ah, okay, thank you! 14:15:56 i definitely appreciate you stepping up like this, mike 14:16:17 my pleasure 14:16:26 and there is a still-open security bug that can use your help :) 14:16:51 speaking of which ... the fix for that has become complicated enough that it needs a spec 14:17:02 :( 14:17:04 you have no idea how many people wrote me about that 14:17:10 i will get that posted soon on the bug 14:17:13 that's the one we discussed in the summit? 14:17:16 (hopefully this afternoon) 14:17:23 jokke_: yes, same one 14:17:35 The Bug 14:17:38 mfedosin: i believe you are already subscribed to the bug, you will get an email when i update it 14:17:43 yes, that one! 14:18:18 i was really hoping hemanthm could review that spec, i will still ask him, don't knwo what his time situation is, though 14:18:42 ok, next topic 14:18:52 #topic community goals report 14:19:16 i didn't have time to make the python 3.5 etherpad this week 14:19:37 but mtreinish has helpfully posted his wsgi goal patches 14:19:48 let's make those a priority for review this week 14:19:59 #link https://review.openstack.org/#/q/status:open+project:openstack/glance+branch:master+topic:goal-deploy-api-in-wsgi 14:20:08 the glance side is pretty straightforward 14:20:11 #link https://review.openstack.org/#/c/459451/ 14:20:28 the devstack is a bit more invovlved because I needed to do things a bit differently to work with chunked transfer encoding 14:20:36 but it's still not that bad 14:22:00 mtreinish: yes, in some clouds "several gigabytes" is close to a terabyte 14:22:14 so i appreciate your extra work on 459451 14:23:42 ok, there are already some +2s, so let's make an effort to get matt's stuff reviewed this week 14:24:04 #topic image import update 14:24:20 jokke_: anything to report/request? 14:24:49 yes 14:25:16 quick one ... flavio looked through the taskflow change and approved :) 14:25:28 cool 14:26:07 obviously something broke but I have high hopes that once https://review.openstack.org/#/c/467145 merges I recheck those 14:27:33 meanwhile I've been looking for next patches to complement the intial including client side 14:27:49 and those help text changes etc. 14:28:39 I just try to get the two approved patches landed as my local repo is totally mess atm. and clean base would be super nice ;) 14:29:29 also something is horribly broken on that https://review.openstack.org/#/c/443636 I haven't figured out yet 14:30:05 it passed gate multiple times before but that just might be again some rebasing issues I'm hoping to clarify once the two patches lands 14:31:26 ok, thanks ... what do you want me to say in the weekly priorities email? 14:31:45 so unblocking 391442 and 443632 are my top priorities above anything else atm. 14:32:07 feel free ... if it has some effect, even better ;) 14:32:48 well, it's probably only us people here who will read it 14:32:51 :( 14:33:26 ok, thanks erno 14:33:49 i forgot to give myself some actions 14:34:08 but that's it from me ... epect me to ping people around to for reviews once the next ones are in the pipeline/unblocked 14:34:08 #action rosmaita email nominating mfedosin to glance-core 14:34:32 #action rosmaita list mtreinish wsgi patches in priorities email 14:35:00 #action rosmaita list erno's 391442 and 443632 in priorities email 14:35:15 next topic 14:35:28 #topic glance-specs action 14:35:41 #link https://review.openstack.org/#/q/status:open+project:openstack/glance-specs+branch:master 14:36:25 there are 2 +2s on https://review.openstack.org/#/c/451560/ ... jokke_ can you +A? 14:37:11 it will go into the to-be-created "untargeted" specs directory 14:37:30 same with https://review.openstack.org/#/c/206120/ 14:37:47 (though that only has 1 +2 atm) 14:38:13 and same with https://review.openstack.org/#/c/448680/ 14:38:35 i'd just like to get those available in case someone new shows up and is interested in something to work on 14:38:45 (actually, the first one is close to implemented) 14:39:13 and, finally, i put up the pike priorities: https://review.openstack.org/#/c/468035/ 14:39:18 wil look the later two ... first one +A'd 14:39:27 ty 14:39:39 I know it was yours but I assumed we still had the agreement PTL +As specs 14:39:57 oh, i forgot about that 14:39:58 but happy to do so if we have lifted that at this point 14:40:22 yeah, i feel weird about +Aing my own stuff 14:40:32 I hear ya 14:40:58 one more spec-related item from me 14:41:33 i took the action item last week to investigate a fix for 0075, the ossn blocking people from purging the glance db 14:41:50 i remembered that jay pipes has/had a blog called join-fu about databases 14:41:59 so i asked him what he thought 14:42:30 his response was that keeping track of the retired image IDs isn't really a database problem per se ... 14:42:35 it's just a big problem 14:42:54 so my hope that there was some kind of groovy database solution already known was in vain 14:43:13 his opinion, which i think is the same as mine and hemanthm's at some point 14:43:37 is that we need a policy to restrict image_id specification at image-creation time 14:43:47 and let operators decide what to do about it 14:43:51 I'm still inclined to block that 14:43:56 why? 14:44:00 it's optional 14:44:06 #link http://www.joinfu.com/ <== that? 14:44:41 efried: yes, looks like "had a blog" is the correct way to describe it! 14:44:58 I would never believed to use this, but that will introduce interoperability issue for something that we have discussed can be fixed without 14:45:18 i don't see an interoperability issue at all 14:45:41 i mean, it's like property protections 14:45:50 specially after the summit discussion where we had exactly 1 vite for "never use it, don't need" and "absolutely necessary" 14:45:53 in some clouds, you can't create particular metadata 14:46:10 i know, so "never use it" can protect with policy 14:46:20 "absolutely need it" can leave it available 14:47:27 i know that rackspace ran into performance issues with too much soft-deleted stuff in the images table 14:47:48 they haven't exposed the ability to end users, so they were able to purge 14:47:51 that still introduces yet another place where those two coulds would behave differently on their public APIs 14:48:03 not really 14:48:11 you can just assume "can't do it" for all clouds 14:48:20 and if you can, it's a nice surprise 14:48:39 well that's the problem ... as since the beginning of the time you have been able to assume can do 14:48:43 on all clouds 14:49:05 yeah, but this is a security problem 14:49:18 well, we can fight this out on the spec 14:49:25 anyway, i was going to do a spec-lite 14:49:26 yup ;) 14:49:36 but i will do a short full-spec so we can list the alternatives 14:49:50 and then send out a message to operators for review 14:50:20 ok, thanks for the quick discussion 14:50:39 #topic python-glanceclient 14:50:58 the word on the street is that someone has been asking for a release of glanceclient in #openstack-glance ? 14:51:06 anyone present? 14:51:28 o/ 14:51:37 My interest in a new glanceclient release is to unblock https://review.openstack.org/#/c/412634/ (related to the service-tokens blueprint). 14:51:43 The fixes, which recently merged, are https://review.openstack.org/466385 and https://review.openstack.org/396816 14:51:45 I was gonna ask that after those couple of fixes that was landed to unbreak the gate 14:51:53 Yuh, ^^ 14:52:19 #link https://review.openstack.org/#/q/status:open+project:openstack/python-glanceclient+branch:master 14:52:24 those are the open patches 14:52:29 If possible can some one review my small patches so that they can be part of release? 14:52:54 abhishekk: i looked at yours this morning, did you figure out the weird https cert breakage? 14:53:06 same test failing in py27 and py35 14:53:17 (at least as of an hour ago) 14:53:22 Patch is submitted for that which has merged today only 14:53:33 I have added recheck for the same 14:53:52 I guess yessterday nikhil has apprived that patch 14:54:17 s/approvex 14:54:30 ok, it would be helpful if we make a list now of the patches that need to get into a release 14:54:46 would next wed be good to do a release? 14:55:20 * efried consults pike release schedule... 14:55:37 I don't think we're release ready today, def not want to release on Fri with skeleton crew 14:55:45 agreed 14:55:56 that's why i'm thinking day before next glance meeting 14:56:06 Agree 14:56:06 so early next week is fine by me if we're ready by that 14:56:08 efried: https://releases.openstack.org/pike/schedule.html 14:56:11 Sounds good to me. 14:56:42 That should leave enough time to resurrect the service token stuff in nova 14:56:57 jokke_: can you hit https://review.openstack.org/#/c/457974/ real quick? docs patch 14:57:19 efried: what are the patches you need in? 14:57:33 https://review.openstack.org/466385 and https://review.openstack.org/396816 (both already merged) 14:57:44 They unblock the gate, too. 14:57:52 which is a nice bonus! 14:57:56 ok, cool 14:58:06 abhishekk: which are the patches you want in? 14:58:14 and is there anything else necessary? 14:58:25 Just a min 14:58:55 efried: sorry, i didn't realize your patches had already merged 14:58:56 https://review.openstack.org/444104 14:59:07 time check 14:59:14 And Downloading image with --progress fails 14:59:30 https://review.openstack.org/445318 14:59:46 ok, i will put those in priority list, we will try to get merged over next few days 14:59:59 and aim for release on wed may 31 15:00:02 Thank you rosmaita 15:00:06 np 15:00:13 ok, thanks everyone! 15:00:16 Thanks to all 15:00:17 happy towel day 15:00:17 Thanks all 15:00:21 #endmeeting