17:06:08 #startmeeting quotas-wg 17:06:10 Meeting started Tue May 31 17:06:08 2016 UTC and is due to finish in 60 minutes. The chair is nikhil. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:06:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:06:14 The meeting name has been set to 'quotas_wg' 17:06:17 #topic agenda 17:06:24 There's no formal agenda for today 17:06:43 I will just jot down the plan for 3 weeks proposed by Vilobh earlier. 17:06:50 and we can have the open discussion 17:06:58 #topic plan for next 2-3 weeks 17:07:00 * DuncanT waves 17:07:08 ohai DuncanT 17:07:23 #1. Mysql driver (vilobh working on a prototype) 17:07:46 #2. Tests (unit, functional) (need volunteers) 17:08:21 #3.1 Docs (info from spec will go here when approved 17:08:43 #3.2 generation-id documentation - how consuming projects should use/consume it; what changes the consuming project need to do to use delimiter 17:09:36 #4 Design (objects to be added to the lib, like resrouce and usage objects) (those that are missing) 17:10:16 itisha may have some cycles and I want here to help with testing. But the rest of the work is open floor if people wanted to pick and contribute. 17:10:22 3.2 would be useful ASAP - without that it's really tricky to get an idea of impact 17:10:30 ++ 17:10:40 nikhil, I have an initial doc up on generation id here: https://review.openstack.org/323415 even though it's completely a WIP - that i added today and would have some more material tomorrow. 17:10:43 Thanks to sudipto, it's now a WIP. 17:11:06 #info gen_id documentation work in progress: https://review.openstack.org/323415 17:11:17 I've not got any free cycles really, though I've got an experimental tree that cuts reservations out of the current cinder code as prep 17:11:27 sudipto: Awesome, thanks! 17:12:34 DuncanT: that's interesting, any link for us to see? 17:12:34 DuncanT, nikhil i plan to write 2-3 docs this week - 1. Gen id stuff. 2. about delimiter's data model 3. How other projects could consume it. Would love to hear about comments/reviews - to ensure I have the right idea about it :) 17:12:55 nikhil: Not yet, but I'll github it this week and post a link 17:13:06 ah nice, thanks DuncanT 17:13:13 any other comments/questions before we move to open discussion? 17:13:23 sudipto: that's pretty awesome! 17:13:24 Time is not my friend at the moment :-( 17:13:29 :) 17:13:37 sudipto:thanks... 17:14:10 #topic open discussion 17:14:29 sudipto: do you mind giving us a tl;dr; of what's there for docs? 17:14:56 (just to get some discussions started) 17:15:39 you mean the review above or in general? 17:15:46 nikhil, ^ 17:15:52 sudipto: I meant in general 17:16:04 (based on your research so far) 17:16:54 nikhil, ok - basically - i think the docs should have those 3 citations i mentioned above. and most likely a project specific implementation detail... 17:17:06 (ofcourse left to open discussions) 17:17:17 We need to add some scale tests to the plan fairly early on I think... what does the performance look like with 1k, 5k, 10k, 100k, 1M entities being tracked for quota 17:18:02 Need to find out if the cache-free approach actually scales... the cache was added for scaling reasons though I can't see any benchmarks done at the time 17:18:22 It's also important for people to know - what the impact of this project will be... 17:18:36 +1 DuncanT 17:19:26 DuncanT: good point... I guess we need some dev testing env for this. I think we could so a bit of testing for glance but 1M entries might be a stretch .. 17:19:42 Can we write a fake service for testing? Just use delimiter to track widgets 17:20:11 I do cinder tests with 1M fake db entries now, it's trivial to just insert things into the DB 17:20:34 DuncanT: I think a simplistic patch to glance #images in queued status (only DB record) would do exactly that. 17:20:50 sudipto: ^ what do you think? 17:20:58 nikhil, yeah that could be achieved. 17:21:23 (also, we can test it on devstack) 17:21:54 nikhil, i would not necessarily commit on doing that this week, since i would like to spend sometime on the docs, but definitely add it to the to-do list. 17:21:55 It's just to make the count queries hit some big record counts - we should be testing at least 10x the biggest record count we expect to see in the wild 17:23:00 nikhil, DuncanT based on Jay's mail - is that how we would eventually expect delimiter to be consumed? 17:23:18 referring to this NOVA example. 17:24:46 sudipto: That's the current plan, yes. I'd like some confidence that it fly ASAP, so that we know if we need to think again (and go have a long debate with Jay no doubt) 17:24:47 referring to http://lists.openstack.org/pipermail/openstack-dev/2016-May/095035.html 17:25:21 DuncanT: right on 17:25:57 DuncanT, sounds good. 17:25:58 sudipto: no worries, I think the lib mysql support may take this week. but this can be put in our glance bucket and work with itisha too. 17:26:49 Having figures and demo code is a good way to deal with any nay-sayers, and to give us confidence before investing too much 17:27:12 * sudipto smells DuncanT is referring to a PoC 17:27:15 DuncanT +1 17:27:39 sudipto: A PoC plus an honest attempt to break it / benchmark it 17:27:54 sudipto: A friendly PoC is a different thing entirely 17:28:03 DuncanT, heh gotcha! 17:28:13 any volunteers for that? 17:28:36 I might have cinder in some shape to do it, maybe. Got a lot else on at the moment though :-( 17:28:51 DuncanT, I will work with you - will that be alright? 17:29:02 certainly 17:29:09 I too have some other commitments, but i will make sure that i keep coming back to you about it. 17:29:39 I'll get a github tree up this week with what I've got - I find them easier than gerrit reviews for messing with 17:30:04 DuncanT, great! That could be our starting point I guess. 17:30:16 DuncanT, I will try to prototype Nova. 17:31:49 Sounds good 17:31:57 any other topic for open discussion? 17:32:20 going 1 17:32:22 going 2 17:32:29 Thanks all! 17:32:37 Let's reconvene next week. 17:32:46 #endmeeting