15:00:18 #startmeeting Glance 15:00:18 Meeting started Thu Jan 22 15:00:18 2015 UTC and is due to finish in 60 minutes. The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:23 The meeting name has been set to 'glance' 15:00:32 o/ 15:00:34 o/ 15:00:37 o/ 15:00:45 f/goto bops 15:00:49 o/ 15:01:21 Let's get started! 15:01:24 #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 15:01:41 #topic Updates 15:01:46 o/ 15:01:50 The updates this week are about 15:01:58 1. Mid-cycle meetup schedule .. 15:02:02 2. K-2 15:02:10 3. K3 15:02:22 #topic Mid-cycle meetup schedule 15:02:31 #link https://etherpad.openstack.org/p/kilo-glance-mid-cycle-meetup 15:03:08 if you have responded, you must have received an email. 15:03:49 If anyone has any questions on the venue, directions, topics, schedule, food etc 15:04:04 Please bring it up now or send an email to me 15:04:12 How do remote participants request food? /kidding 15:05:29 #action everyone: please respond to the long lunch proposal either way soon 15:05:36 Next. 15:05:39 #topic K-2 15:05:46 https://launchpad.net/glance/+milestone/kilo-2 15:06:07 We've a long list of reviews 15:06:19 Please take a look at them on priority. 15:06:58 If the code has not major objections, and the spec is consistent with the code proposed it would be merged soon 15:07:14 You must already have received some feedback 15:07:33 * sigmavirus24 hasn't on the Policy blueprint 15:08:05 #action: everyone, the k2 bugs (if not necessary) can moved to k3 as long as corresponding code does not look in a good shape. 15:08:23 sigmavirus24: that one is dicey 15:08:39 let's see how things go on others in next couple of days 15:08:56 we need reviewers focused on small set of patches so that at least some get in 15:09:42 Yeah, I figured mine would be okay for k-3 so I targetted there. Someone moved it to k-2 apparently 15:09:52 If anyone is worried about a patch not getting in soon, this might be a good time to speak up (or about something getting in that shouldn't be) 15:10:29 sigmavirus24: it was me :P (optimistically prioritizing) 15:10:41 Next. 15:10:44 #topic K3 15:11:10 The following features/additions/changes have been deferred to k3 15:11:13 1. Catalog Service 15:11:18 2. Artifacts 15:12:39 The deactivation of an image and policy changes *may* get in k2 . (due to some recent developments) 15:13:07 Other specs that have not received any significant reviews yet 15:13:27 They are just hard to focus on given other major changes that we are planning to adopt this cycle. 15:14:20 That was the updated part. We can leave some time here for feedback. 15:14:28 *update* 15:15:36 So, FYI, with catalog service, one of the tasks was to add notifications for metadefs. You and Brian thought we should break that out. So, I'll be putting up a spec on that. 15:15:51 That review is already written, yes? 15:16:02 TravT_: Sounds like a good idea. 15:16:04 (The actual metadef notification code) 15:16:14 yes, kamil has a good start on it 15:16:16 Yup, the implementation is ready (almost?) 15:16:43 It's fine to start off sluggish and keep a watch on the bugs. 15:17:10 Seems like metadef team has been actively resolving some as well as has been great with specs. 15:17:52 (Basically, we would be short of reviewers) 15:18:12 #topic Reviews/Bugs/Releases 15:18:23 1. Glance client 15:18:24 https://launchpad.net/python-glanceclient/+milestone/v0.16.0 15:18:28 2. glance_store 15:18:33 https://launchpad.net/glance-store/+milestone/v0.1.11 15:18:51 Those are the planned ones 15:19:15 kragniz: brought a good point that we should probably release SemVer style 15:19:16 what about sorting features for v2 in the client? 15:19:44 So, yeah. Things like that - please mark it on the lp and 15:20:05 leave a message to sigmavirus24 kragniz jokke_ zhiyan or me to add it to the trello board 15:20:12 flapper87 too 15:20:50 sigmavirus24: I kinda stole your topic, did you have anything more important to point out? 15:20:59 (sorry about that) 15:21:06 Nope. Just wanted to discuss it's progress :) 15:21:26 Cool. Looks like reviews for the most part. 15:21:28 I'm planning on writing release notes for client and store when some of the reviews are merged 15:21:37 kragniz: +1 15:21:52 I thought PBR did that for us or something 15:22:04 sigmavirus24: not release notes 15:22:31 personal touch is always welcoming ;) 15:22:36 sigmavirus24: we went over this with dhellmann :P 15:22:47 PBR confuses me 15:22:47 * nikhil_k means that in the modest possible way 15:24:18 Who's next? 15:24:28 is this a point where i can hop in? i need to find core reviewer(s) for https://review.openstack.org/#/c/145223/ 15:24:28 Feature request:- 15:24:29 https://bugs.launchpad.net/glance/+bug/1411215 15:25:31 Yeah I added that and wanted to bring attention to it. It seems useful but I'm not sure if it is really desirable 15:25:51 Also I wanted to make sure no one things that anything other than a glob-like syntax is necessary 15:26:02 sigmavirus24: we've planning to work on the cloning feature for that 15:26:03 Compiling regular expressions provided by the user seems like a badidea 15:26:55 +1 15:27:06 we want to push that stuff to the metadata indexing service 15:27:28 stpierre: I'm not a core but I'll look at that today 15:28:21 stpierre: can we wait just a bit? would like to give some feedback in the open discussion 15:28:25 sure 15:28:32 Next. 15:28:48 https://bugs.launchpad.net/glance/+bug/1188532 nominated for juno and icehouse 15:29:10 The OSSA requested someone nominate it for those but we haven't accepted the nominations 15:29:17 (Or we hadn't as of last night) 15:29:57 So I wanted feedback as to whether we do want to backport and someone to accept those. I'll backport them today since teh juno branch freeze starts on 30 Jan 15:30:01 sigmavirus24: the duplicate one has more info unfortunately https://bugs.launchpad.net/glance/+bug/1383973 15:30:40 sigmavirus24: I'd started work on it yday and could get to it only partially. It's tricky due to the glance_store changes. We can discuss more offline. 15:31:27 That looks like a good one to backport to me 15:31:46 Okay 15:32:00 I just wanted to bring it up since the next juno release is not far off 15:32:15 May I for some attention on https://bugs.launchpad.net/glance/+bug/1412802 ? Quite a nasty bug, and also worths backporting to I-J 15:32:56 sigmavirus24: this is the most active duplicate https://bugs.launchpad.net/glance/+bug/1398830 15:33:23 Oh that's already nominated. Nevermind :) 15:33:59 yeah, lp needs a cleanup there ;) 15:35:03 ativelkov: can we get to you review after sigmavirus24's next one? 15:35:19 ativelkov: nikhil_k: I'm kind of surprised that is only a medium. since it is data corruption \ loss. 15:35:24 Sure, sorry for interrupting 15:36:01 Next one is just the spec for passing real targets to the policy enforcer (which is now targetted for k-2) 15:36:05 TravT_: be back on that, sorry 15:36:09 * TravT_ shuts mouth too ;) 15:36:25 https://review.openstack.org/#/c/149112/ 15:36:31 so I'd love feedback on that and early review on the associated review is appreciated. I have ideas for tests as detailed in the spec but haven't added them 15:36:34 yes, thanks nikhil 15:37:10 awesome, thanks for that pointer sigmavirus24 ! 15:37:22 * sigmavirus24 hands torch to ativelkov 15:37:42 Thanks sigmavirus24 :) 15:38:01 Well, that's a data corruption issue I recently found 15:38:17 The fix is here: https://review.openstack.org/#/c/148574/ 15:39:00 As it happens in Icehouse and Juno, I proposed to backport it (which is quite simple: the changed code haven't been modified for a long time) 15:40:02 * sigmavirus24 is reviewing 15:40:12 ativelkov: TravT_ : yeah, I think we can mark it critical. 15:40:42 Our initial discussion with ativelkov lead me to believe this was specific to stores, with the values associated to them 15:41:09 Thanks for the pointer TravT_ , much appreciated! 15:41:42 Should we target that to k-2? 15:41:50 just did :) 15:42:08 Thanks 15:42:08 If more reviews come, we may definetly release it in k2 15:42:38 might be a good idea to focus on critical bug sooner 15:42:48 ;) 15:43:01 Need to sync openstack/common from oslo-incubator: 15:43:10 Need to sync openstack/common from oslo-incubator for service module - catalog index service requires it for notifications listener 15:43:14 lakshmiS: ^ (seems like you) 15:43:15 Should i open a bug to import it? 15:43:34 that would be great 15:43:47 We are also looking at the service module to use as a framework for notification refactoring - similar to how ceilometer uses it for notifications. 15:44:15 are there any other ideas on refactoring notifications? 15:45:24 * sigmavirus24 hasn't looked at notifications in depth yet so I can't give useful feedback, yet 15:45:55 according to current work at notifications for metadata objects https://review.openstack.org/#/c/148546/ which is based on implementation from images 15:46:09 We are thinking about some notification refactoring in glance, this might come up in Nova-Glance common session at the mini-summit 15:46:35 is there a agenda for nova-glance common session? 15:46:39 Please free to float this idea on the summit etherpad, we can try to sneak it in >.> 15:46:47 ok 15:47:18 #topic Open Discussion 15:47:48 stpierre: about your spec 15:48:41 Looks like a good improvement. I'm just worried about it clashing with https://review.openstack.org/#/c/125156/ and (possibly) https://review.openstack.org/141331 15:49:16 Just with the code proposal path. 15:49:51 stpierre: if you've a draft ready, we can try to merge it faster than those two. 15:50:10 (unlikely for k2) 15:50:23 i don't have anything ready yet unfortunately 15:51:04 stpierre: no issues, not a possibility in next 2 weeks. So, anything after than is welcome :) 15:51:22 okay, i can definitely have something by then 15:51:41 sigmavirus24: would you like to be assigned to https://bugs.launchpad.net/glance/+bug/1398830 backports? (I can help as needed and in review too ;) ) 15:51:47 the only potentially serious point of contention i see is with the "in-memory cache" in the first spec there; it doesn't describe how the in-memory cache will be populated. but even that should be fairly trivial since my change will just replace the current read/write operations with something consistent and easy :) 15:52:04 so all i need is a core reviewer to sign on and i can be off and writing code 15:52:23 stpierre: feel free to assign and bug me on this 15:52:26 nikhil_k: go for it 15:52:31 i'll assign myself 15:52:35 sigmavirus24: awesome! 15:52:46 I'm going to prioritize juno though 15:52:47 because deadlines 15:52:51 nikhil_k: tyvm 15:52:52 +1 15:53:01 stpierre: :) 15:54:54 If nothing else ... 15:55:37 looking forward to seeing many of you next week! 15:55:49 TravT_: ;_; 15:55:54 TravT_: ;_; 15:56:03 Also TravT_ sorry I misunderstood your spec. I read it totally wrong :) 15:56:10 yeah, wish you guys could be there. 15:56:39 sigmavirus24: no worries 15:56:39 Thanks all! 15:56:56 #endmeeting