14:00:31 #startmeeting glance 14:00:32 Meeting started Thu Dec 8 14:00:31 2016 UTC and is due to finish in 60 minutes. The chair is sigmavirus. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:33 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:35 #chair rosmaita 14:00:36 The meeting name has been set to 'glance' 14:00:37 Current chairs: rosmaita sigmavirus 14:00:48 sigmavirus: you are on top of things! 14:00:57 o/ 14:00:58 #topic roll call 14:01:05 * sigmavirus is a helper 14:01:06 o/ 14:01:15 o/ 14:01:19 \o 14:01:42 ok, short agenda today and light turnout 14:01:59 #topic updates 14:02:27 o/ 14:02:28 o/ 14:02:46 i'll wait another minute to see if we get a few more people 14:03:53 ok 14:04:02 o/ 14:04:07 nikhil! 14:04:24 :) 14:04:31 sorry I've been away 14:04:40 it's ok, glad to see you back 14:04:55 in fact, very glad, as you will see shortly 14:05:07 ok, back to the updates 14:05:25 last week i sent out a priorities email, let's review the items 14:05:35 #link http://lists.openstack.org/pipermail/openstack-dev/2016-December/108412.html 14:06:00 priority 1 was the rolling upgrades spec 14:06:15 it has been merged 14:06:38 priority 2 was the db strategy for rockin' and rollin' upgrades 14:07:00 that one needs some cores to review, please 14:07:26 preferably non-rackspac 14:07:40 since hemanth and rosmaita are co-authors 14:08:08 i noticed that stevelle left some comments, i will address and get a new patch up 14:08:26 also, you don't have to be a core to review it 14:08:42 anyone thinking of working on glance long-term should check it out 14:08:49 it's the strategy of The Future 14:09:08 ok, so priority (2) --> not accomplished 14:09:59 priority (3) --> not accomplished, has a +2 but needs another (or request for revision) 14:10:05 in other words, needs some action 14:10:12 moving on 14:10:23 priority (4), patch to fix a bad regression 14:10:58 was hoping to get some input from kairat on that one 14:11:50 i think it's pretty much ready, but could maybe use a few more eyes 14:12:26 ok, so (4) not accomplished 14:12:31 this is getting depressing 14:12:40 i'm afraid to look at (5) 14:12:58 looks like no action on that one 14:13:04 sorry abhishek_k 14:13:21 no issues rosmaita: 14:13:34 and (6) looks like no activity either 14:13:43 thank you for your efforts 14:13:53 well, on the plus side, that will make the list of next week's priorities easy to write 14:14:25 i'll try to attend better to 5 & 6 this week 14:14:51 spent a lot of time on the community images spec update, which i didn't list as a priority because i thought we'd reached a consensus last week 14:15:01 but we had not 14:15:13 so i guess i'm setting a bad example here 14:15:16 anywya 14:15:30 #topic Community images spec update, part 16 14:15:41 new patch up 14:15:45 #link https://review.openstack.org/#/c/396919/ 14:15:49 you mean part 601, right? :P 14:16:00 sigmavirus: thanks, that was a typo 14:16:21 ok, so this has been pretty rough going 14:16:49 it's been hard to find a solution for 'visibiliity' default & migration that satisfies everyone 14:17:01 so i've gone for a compromise that will satisfy no one 14:17:05 (just kidding) 14:17:13 actually, i think this is a good trade-off 14:17:23 even though it's not my favorite solution 14:17:35 so the new patch sticks with default visibility of shared 14:17:54 but will make non-public images that have no members 'private' in the migration 14:18:05 anyway, the full story is in the patch 14:18:22 i added some stuff to make clear what the end user impact will be 14:18:32 i don't think there's a way to have *no* impact 14:18:41 but this seems reasonable 14:18:43 correct 14:18:57 if it was a no-impact change, there'd be no need for a spec ;) 14:19:05 it's just tautological :D 14:19:10 good point 14:19:44 anyway, all the +2s have no disappeared and need to be renewed (unless you have strong reservations) 14:19:52 and again, non-cores should take a look too 14:20:06 image sharing is a bit more complicated that it should be 14:20:21 so you might as well get familiar with what's going on there 14:20:21 truths 14:21:31 ok, that's all on the agenda for today 14:21:36 #topic open discussion 14:21:52 i haven't had time to put together the next operators' survey 14:22:03 #link https://etherpad.openstack.org/p/glance-swift-multitenant-usre-survey 14:22:16 (that link is correct, misspelling and all) 14:22:48 the topic is to figure out how many operators use multi-tenant-swift backend 14:23:03 so we can prioritize work on it 14:23:32 there's a current op survey out, closes tomorrow 14:23:41 about use of multiple image locations 14:24:00 so far, looks like people are using them 14:24:19 mostly for ceph backend, but i haven't looked through all the responses yet 14:24:46 fei long is going to use the info to put together a design session for the PTG 14:24:49 * sigmavirus hates the multi location nonsense 14:24:55 me too 14:25:17 i'm hoping we get enough info to replace them with an actual feature aimed at a particular use case 14:25:39 right now, they're just sort of available for you to open security holes with 14:25:55 speaking of the PTG ... 14:26:13 my plan is that we'll do 2 1/2 days of glance 14:26:32 that will allow you to leave on Friday afternoon, don't have to wait for friday evening 14:26:43 basically, what everyone does anyway 14:27:16 but, at this point, i should shut up and let someone else have the floor 14:27:23 * rosmaita shuts up 14:27:58 I think you said all the words :) 14:28:53 guess so ... hope i didn't suck all the oxygen out of the room 14:30:18 well ... same priorities as last week except for the one that got done + community images spec update 14:30:47 ok, please have a productive next half hour! 14:30:53 #endmeeting