14:00:15 #startmeeting glance 14:00:16 Meeting started Thu Jan 12 14:00:15 2017 UTC and is due to finish in 60 minutes. The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:19 The meeting name has been set to 'glance' 14:00:26 #topic roll call 14:00:40 o/ 14:00:57 o/ 14:01:03 #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 14:01:15 o/ 14:01:18 o/ 14:01:38 \o 14:02:16 sigmavirus should be around too, just saw that he sent something to the ML a few minutes ago 14:02:23 Hey all, I am 14:02:28 Was filing bugs against bandit 14:02:34 Sorry for being late :) 14:02:44 well, you are usually early! 14:02:52 ok, let's get started 14:03:00 #topic updates 14:03:14 Reminder: gerrit downtime today 20:00-20:30 utc 14:03:33 i don't know how to do sub-topice 14:03:36 *topics 14:03:39 (There is no way) 14:03:44 (There is only zuul) 14:03:45 anyway, #2: New experimental grenade gate job 14:03:58 just want you to be aware it exists 14:04:01 I guess you could do #info but *shrug* 14:04:10 #link https://review.openstack.org/#/c/414326/ 14:04:32 only impact could be slower overall gate 14:04:58 which could be a problem, so just a heads-up for awareness 14:05:10 #info item 3 - community images 14:05:26 here's the latest installment in the saga: 14:05:30 #link http://lists.openstack.org/pipermail/openstack-dev/2017-January/110018.html 14:05:56 i missed the QA meeting due to a time confusion 14:06:03 =( 14:06:18 there seems to be a slight misunderstanding about what we are asking for 14:06:28 so i tried to address that explicitly in the above email 14:06:56 but the issue seems to be coming down to: who decides what is an acceptable API change? 14:07:12 cdent has put us on the agenda for today's API-WG meeting 14:07:15 Yay. That discussion again 14:07:21 /sarcasm 14:07:46 yeah, looks like that might be what it's coming down to 14:07:57 anyway, api-wg meeting is at 16:00 utc today 14:08:04 (that time i'm sure about!) 14:08:19 i'll be there, anyone else who's interested please attend 14:09:21 that's all i've got to say about this ATM 14:09:29 ok, moving on 14:09:40 #info Review of progress on priority items from last week 14:09:50 #link http://lists.openstack.org/pipermail/openstack-dev/2017-January/109772.html 14:10:18 priority 1 was the request-id stuff; abhishekk has a new patch up addressing issues; please review 14:10:30 maybe we can get that knocked out today and drop it from the priority list 14:10:40 yes, thank you 14:11:45 priority 2: alembic stuff 14:12:04 https://review.openstack.org/#/c/392993/ has a -1 from dolph 14:12:06 rosmaita: this needs to be included too https://review.openstack.org/#/c/397409/ 14:12:16 rosmaita: I'll look into that 14:12:21 hemanthm: ty 14:12:59 not sure everyone knows, alex_bash is on paternity leave for the next 2 weeks or so, so he'll only be around sporadically 14:13:47 rosmaita: unacceptable 14:13:51 he shouldn't be around *at all* 14:13:53 :) 14:14:38 ok, the alembic stuff remains a priority ... that means core reviewers need to look at it before doing other stuff this week (unless you are working on a security bug) 14:15:03 so mark down these reviews: 14:15:10 Yeah, if you're a core working with the VMT, that takes priority 14:15:27 #link https://review.openstack.org/#/c/392993/ (after hemanthm updates) 14:15:58 #link https://review.openstack.org/#/c/397409/ 14:16:12 #link https://review.openstack.org/#/c/382958/ 14:16:33 #info priority 3: community images 14:16:51 i will have to update over the ML 14:17:15 i am confusing myself with the #topic and #info 14:17:30 lol 14:17:53 dharinic had a request for some stuff to be put on the priority list for this coming week 14:18:19 Yeah. I was hoping we can add Buffered Reader to our priority 14:18:33 hearing no objections, consider it added 14:18:38 Here is the link to the patch under review: https://review.openstack.org/#/c/120866/ 14:18:53 Awesome, Thanks. 14:18:58 i'm not inclined to add new stuff because we have an upcoming glance_store release 14:19:02 (more on that later) 14:19:15 so there will probably be soem glance_store related stuff that we'll need to address 14:19:30 ok, last update item 14:19:40 #info PTL self-nominations opens soon (week of Jan 23) 14:20:00 if you're thinking of running for PTL, keep the deadline in mind 14:20:24 also, you can talk to me or flavio about what it's like to be ptl to gather data 14:20:45 also, i think mfedosin and flwang have some experience in that regard 14:20:59 i am planning to run again, but don't let that stop you 14:21:43 that's all for updates 14:21:56 #topic PTG planning 14:22:14 #link https://etherpad.openstack.org/p/glance-pike-ptg-planning 14:22:45 oh yeah, when i said above that i was planning to run, i meant "run for glance ptl", not "run away" 14:22:58 ok, we need to start thinking about The Future 14:23:09 some general info is on the etherpad linked above 14:23:37 if you have some ideas of where glance needs to go in Pike and Queens, please propose sessions 14:23:47 we will have all day wed, thurs, and friday morning 14:24:05 won't be distractions like at previous summits, so we should be able to get a lot done 14:24:49 i know stevelle and jokke are interested in multiple backend support 14:25:10 anyway, if you have ideas, please add them to the etherpad 14:25:28 # topic upcoming glance_store release 14:25:38 sigmavirus: that's you, i believe 14:25:45 Sorry got side tracked 14:25:55 #topic upcoming glance_store release 14:25:59 dang doesn't update it 14:26:01 anyway 14:26:10 The non-client library release freeze is coming up next week 14:26:25 #topic upcoming glance_store release 14:26:29 As such, I'd like us to find the *top* priority (non-bug fix) reviews for the glance-store and prioritize their reviews 14:26:50 Anything that's a bug fix I would like to prioritize for *after* the release because we can work on backporting those to stable/ocata and creating a release 14:27:17 This is especially important if there are any reviews that are supporting the existing priorities (request-id, etc.) 14:27:43 If we don't have any feature related work, I'm going to submit the release request sooner rather than later to get it off my plate 14:27:51 off the top of my head, we had a multi-tenant swift support fix that i believe has been merged 14:27:52 14:28:09 we have a security bug that needs to get in 14:28:21 but that's all i'm aware of right now 14:28:23 anyone else? 14:29:23 sigmavirus: you said Jan 18 for the release? 14:29:30 and possibly try getting Buffered Reader in? 14:29:45 dharinic: you are correct 14:30:55 rosmaita: the dates are in the agenda 14:30:56 jan 18 is before our next meeting, so if anyone thinks of something, please communicate to the ML 14:31:10 sigmavirus: ty, i knew i saw them somewhere 14:31:17 :) 14:31:27 #action sigmavirus to propose glance_store release on 18 Jan 2017 14:31:49 ok, so right now, we have still open for glance_store: 14:32:00 - buffered reader for swift 14:32:18 - security bug that i can't give details on 14:32:30 ok, moving along 14:32:55 #topic glance_store and glance coresec 14:33:12 as you may have noticed, there's a security bug open related to glance_store 14:33:28 i've got some concerns about the proposed fix 14:33:45 need coresec people to look at the bug and weigh in 14:34:01 we absolutely need to get this fixed before jan 18 14:34:15 if you are on coresec and don't know what i am talking about, please pm me 14:34:56 #topic glance_store patch needs thought about testing 14:35:16 #link https://review.openstack.org/#/c/378460/ 14:35:48 this is a follow-up patch for a ceph driver bug 14:36:02 the bug had to do with how the size of an image was being determined 14:36:30 it was fixed in one place earlier 14:36:48 but this patch fixes it in the get_size() function 14:37:06 which was a pretty bad place to miss it 14:37:37 sigmavirus had put a note on an earlier patch that it would be good to have a test 14:38:10 and since one of the instances of using a problematic ceph call was missed, i have to agree 14:38:23 but, it's not entirely clear how this could be tested 14:38:53 so my request is for people to take a look and see if you can suggest something 14:39:29 i think the fix is ok, but with no tests, it's hard to avoid a regression 14:39:33 ^ 14:39:35 ++ 14:40:06 ok, that's all for our regularly scheduled program 14:40:11 #topic open discussion 14:40:22 maybe stubout the method in question and barf if it is invoked? 14:41:29 hemanthm: barf is such a ... sticky word 14:41:33 ;P 14:42:09 :P 14:42:11 hemanthm: i think you may have hit on the solution there 14:43:37 i've received some feedback that i haven't allowed for sufficient open discussion at meetings 14:43:51 rosmaita: I haven't looked at the patch yet, will take a look at it today 14:43:52 so, just want to point out that we have 16+ min 14:44:18 so ... please discuss! 14:44:27 ok ... what's happening with our logo? 14:44:47 hemanthm: good question, i never heard back about the redesign 14:45:01 #action rosmaita follow up about the glance logo situation 14:45:42 i haven't heard about any fabulous swag that's supposed to be available at the PTG, either 14:46:01 I was so hoping for chipmunk shirts 14:46:19 hemanthm: you may very well get one, but it may look like a squirrel! 14:46:26 haha 14:48:25 rosmaita: send swag 14:48:31 :) 14:48:34 * sigmavirus has a darth of OS swag 14:48:51 sigmavirus: if anyone needs OS swag, it's you 14:49:09 anyone have any interesting new year's resolutions? 14:49:32 Be a better release CPL 14:50:04 Be better at everything. 14:50:12 question: Is every session at the PTG like a presentation that one person presents/talks about? Or is it more like a team discussion and brainstorming? 14:50:26 dharinic: sort of a combination 14:50:29 Be better at writing email filters :/ 14:50:30 not a presentation, really 14:50:44 more that someone leads the discussion in a productive manner 14:50:59 so as the discussion leader, you set the stage 14:51:09 Cool. Thanks rosmaita 14:51:14 and then most of the session is discussion and brainstorming 14:51:29 np, good question 14:51:47 whats the approx count of ppl who will be attending it? 14:51:53 dharinic: it may involve boo-ing the speaker too :P 14:51:57 another good question 14:52:07 Will keep that in mind hemanthm :P 14:52:11 let's take a quick poll of who expects to attend the PTG 14:52:23 i will attend 14:52:28 o/ 14:52:29 I will too 14:52:29 o/ 14:52:43 o/ 14:52:52 mfedosin: will you be able to attend? 14:52:53 I'm all booked 14:52:55 alex_bash too 14:53:14 I'll be there from Sun evening to Sat 14:53:47 i haven't set travel plans yet, but will be similar, but maybe leave friday afternoon 14:54:10 so ... finally, hemanthm and jokke_ will get to meet! 14:54:20 yay 14:55:31 rosmaita: unfortunately no 14:55:38 mfedosin: bummer 14:55:44 I know 14:56:19 but if its possible to organize it online I'll be happy to join 14:56:30 mfedosin: i was just going to say that 14:56:46 :) 14:56:51 #action rosmaita find out what online arrangements will be available at PTG 14:57:28 if you have a laptop with webcam we may organize skype call 14:57:29 i'll try to find out right away, and hten maybe you could organize a glance_store session 14:58:00 great! 14:58:05 mfedosin: could you put an item on next week's agenda to give us a glare update? 14:58:32 sure! will be done 14:58:36 excellent 14:58:47 btw, sorry for offtopic, but I prepared several demos for glare 14:59:52 i'm mainly interested in glance/glare areas of cooperation that we should be thinking about/aware of 15:00:00 ok, we're out of time 15:00:04 #endmeeting