14:01:46 #startmeeting glance 14:01:48 Meeting started Thu Dec 1 14:01:46 2016 UTC and is due to finish in 60 minutes. The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:50 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:52 The meeting name has been set to 'glance' 14:01:58 #topic roll call 14:02:03 hello everyone 14:02:21 Hello. o/ 14:02:45 o/ 14:02:59 o/ 14:04:05 o/ 14:04:46 ok, guess we should get started 14:04:57 #topic updates - operator surveys 14:05:10 we've got 2 operator surveys happening right now 14:05:23 one about the community images database migration 14:05:27 (more on that a bit later) 14:05:40 and one about what people use multiple image locations for 14:05:56 we're getting some good feedback 14:06:31 i'm going to send a reminder to the operators list about the multiple image locations survey, since the USA holiday happened right after the first email 14:06:40 we plan to close that survey on dec 9 14:07:10 we'll discuss another survey (still to be designed) a bit later in the meeting 14:07:39 i think these are a good way to keep touch with operators and get some good vibes going in the wider community 14:07:57 so, this was just an update that operators surveys are happening 14:08:11 but i'll be happy to answer questions if anyone has them 14:08:26 when is the CI survey overe? 14:08:50 got the last response about a week ago, so it's effectively over 14:09:01 i forgot to specify a closing date on that one 14:09:26 i'll tell you the results at agenda item 4 14:09:54 anything else? 14:10:10 (i know i'm supposed to wait quietly for questions, but i can't stand the silence!) 14:10:23 rosmaita: do we have enough feedback take a decision based on the survey? 14:10:36 *to 14:10:37 i think so, will give my recommendation in item 4 14:10:42 ok 14:11:14 all right, moving along 14:11:24 #topic unfinished business 14:11:41 hi, about 1st patch, https://review.openstack.org/#/c/319960/ - this design was rejected during cross-project discussion with reason described in the commit message 14:12:07 so I have reverted this patch after discussion with erno 14:13:53 and regarding 2nd patch, https://review.openstack.org/#/c/352892/ - I am waiting for the feedback, requesting community members to give their opinions on the same 14:14:19 i think the 2nd patch is a priority, so reviewers, please review it! 14:14:42 as far as the first patch goes ... 14:14:57 has there been a release of the glanceclient with your original patch in it? 14:15:08 because your reversion patch has been sitting since May 23 14:16:04 no that was not my patch, I have noticed that it was already merged so added a revert for that 14:16:59 ok, sorry about that 14:17:25 key thing is it looks like 2.5.0 has that undesirable code in it 14:17:32 no issues 14:17:41 yes 14:18:41 that's all from my side 14:19:23 abhishekk: what's your opinion on this now? is it important to revert right away, or instead do some kind of thread-local fix as you suggest? 14:19:52 IMO we should revert this 14:20:47 OK, can you put a comment on the patch saying that it's important to revert this to prevent incorrect info being returned to the user 14:20:48 as it has already been rejected in cross-project by many peoples 14:21:11 yes, I will add it in detail 14:21:24 thanks, that would be helpful 14:21:42 i'll put this patch in the list of things for people to pay attention to for the coming week 14:22:06 ok, and the second patch i think is pretty much ready, just needs reviews 14:22:19 yes 14:22:57 ok, great ... thanks for bringing these up (again) and hopefully we can get better action on them this time 14:23:17 any questions for abhishekk ? 14:23:44 thank you 14:23:51 ok, moving along 14:24:06 #topic Next operators survey: swift backend in multi-tenant configuration 14:24:20 this is prompted by a patch dharinic has up 14:25:02 (which i suddenly can't find) 14:25:22 https://review.openstack.org/#/c/387719/ 14:25:29 thanks! 14:25:58 that patch could use some reviews, by the way 14:26:24 And the patch that could ideally follow: https://review.openstack.org/#/c/388944/ 14:26:44 387719 corrects a bad regression in the swift multi-tenant store 14:27:11 a regression so bad, that since we haven't heard any complaints, it makes me wonder whether anyone is actually using swift in multi-tenant mode 14:27:26 or, they are using it in older distributions 14:27:38 so i'd like to do an operators survey to get some info 14:28:04 we'd take the survey after the currently open one closes on dec 9 14:28:16 so here's a etherpad to get some ideas: 14:28:27 https://etherpad.openstack.org/p/glance-swift-multitenant-usre-survey 14:28:42 and yes, i misspelled 'user' in the above 14:28:49 but that's the correct url 14:29:47 ok, that's it 14:30:07 summary: please review https://review.openstack.org/#/c/387719/ so we can release glance_store without this bad regression 14:30:17 and think about what we should ask operators 14:30:44 should we ask if operators ever switch from one store to the other? 14:30:47 or, if you know people who use swift in multi-tenant config, please add that info to the etherpad 14:31:06 hemanth: sure ... we can debate that on the etherpad 14:31:26 i suspect people don't because migration is a big pain point 14:31:32 but, who knows 14:31:54 ok, any questions about that? 14:32:09 tumbles in ... sorry for being late 14:32:18 jokke_: greetings! 14:32:50 jokke_: you can read through the meeting log later, abhishekk 's discussion earlier will interest you 14:33:00 ok, moving along 14:33:18 #topic Community Images: discuss design decision of default visibility = 'shared' 14:33:48 we talked about this at the last meeting 14:34:14 i sent out a survey to get some info from operators, here's what i told them: 14:34:27 #link http://lists.openstack.org/pipermail/openstack-operators/2016-November/012107.html 14:34:42 you haven't seen that if you don't subscribe to the operators list 14:34:55 anyway, the results 14:34:58 (drum roll) 14:35:11 #link https://review.openstack.org/#/c/396919/ 14:35:21 take a look at the last comment on that patch 14:35:57 i will give everyone a few min to read through that 14:38:03 wow 9 responses :( 14:38:23 yeah, i don't know how to interpret that 14:38:39 in one sense, great! > 5 responses 14:38:53 but on the other hand, that's a small number of deployments represented 14:40:27 rosmaita: also regarding the poll setting. What happens to the pre diablo image records? :P 14:40:57 is_public == 0 -> 'shared' 14:41:06 (or is that not what you're asking?) 14:42:03 the option A) talks only about Doablo-to-Newton images ... what is the plan on that option for pre diablo created images? 14:42:12 it was not in the poll :P 14:42:21 I think jokke_ is asking why you called out diablo-to-newton specifically 14:42:21 oh 14:42:23 so they must stay intact, right :P 14:42:59 i'm assuming there are no pre-diablo images 14:43:08 anyway, sharing was introduced in Diablo 14:43:18 but i get your point now 14:43:41 i don't think anyone ever deployed anything before essex 14:45:06 anyway ... 14:45:20 any other comments about my recommendation? 14:45:43 I'm still very much against that option A 14:45:58 purely user perspective 14:46:02 yeah, but the operators are split, and jay pipes and monty are for it 14:46:16 and that assumes that users actually look at visibility 14:46:42 rosmaita: I haven't seen either contributing to Glance for long enough that I'm willing to ignore the opinions of them :P 14:46:42 i think the (B) migration causes more problems, for example, breaking v1 14:46:56 rosmaita: I still have to catch up on the comments on that review, will comment on it in a bit 14:47:02 jokke_: i have to admit, if they disagreed with me, i'd say the same thing 14:47:05 :) 14:47:37 this is one of those things where no matter what we do, someone is going to be disappointed 14:47:47 so we just need to go with what makes the most sense 14:47:56 so my request to everyone is: 14:48:01 Talk again in Pike? :P 14:48:03 please read through and comment 14:48:06 NO!!!! 14:48:16 that's easy to achieve 14:49:18 ok, let's move along before jokke_ makes any more suggestions 14:49:26 :P 14:49:44 actually, that brings us to open discussion 14:49:49 #topic open discussion 14:50:46 so, anything to discuss? 14:50:54 I would like some insights and opinions for bug https://bugs.launchpad.net/glance/+bug/1585917. :) 14:50:54 Launchpad bug 1585917 in Glance "member-create will raise 500 error if member-id is greater than 255 characters" [Undecided,Confirmed] - Assigned to Abhishek Kekane (abhishek-kekane) 14:51:41 bhagyashris: is that still a thing? :o 14:52:21 bhagyashris: i looked into it a bit, even the 'simple' fix is not going to be easy 14:52:54 jokke_: yes 14:53:32 so bhagyashris, it seems like the metadefs fix should be straightforward 14:53:43 the problematic one is the member string 14:54:27 so maybe split the work into fixing metadefs first 14:54:29 rosmaita: yeah 14:54:50 but you are right to bring this up, because it's sitting from inertia 14:54:57 rosmaita: ref abhishekk's topic up there, my recommendation was valid when the change wasn't released yet 14:55:38 ok. 14:55:49 bhagyashris: we may have to accept 500s on bad member ids until we work out the json schema support in glance 14:56:03 but at least the metadefs can be fixed 14:56:35 jokke_: how do you feel now that the change has been released? 14:56:47 abhishekk thinks we should still revert it 14:56:59 he's going to update the patch with a comment to that effect 14:57:18 rosmaita: imo we still need to fix it. We just made ourselves clowns by releasing it, claiming it fixes the issue even we knew it doesn't 14:57:53 well, i guess it's nice that we can amuse the openstack community 14:57:59 rosmaita: metadefs fix are already merged 14:58:17 bhagyashris: that was quick work! 14:58:54 rosmaita: but I do not have strong feelings of revert vs. just patch that fixes the behavior 14:58:56 yes, IMO even we fix using thread local storage its not guaranteed to get right result 14:59:39 ok, let's continue that discussion on the patch 14:59:40 abhishekk: that's not great either ... do you have case in mind when it wouldn't? 14:59:52 for both abhishekk and bhagyashris patches 15:00:05 gotta go 15:00:12 #endmeeting