Monday, 2016-02-29

*** sdake has joined #openstack-meeting-cp00:00
*** markvoelker has joined #openstack-meeting-cp00:43
*** sdake has quit IRC00:45
*** markvoelker has quit IRC00:47
*** sdake has joined #openstack-meeting-cp00:50
*** sdake has quit IRC01:06
*** sdake has joined #openstack-meeting-cp01:08
*** sdake has quit IRC01:43
*** markvoelker has joined #openstack-meeting-cp01:44
*** markvoelker has quit IRC01:48
*** sdake has joined #openstack-meeting-cp02:31
*** markvoelker has joined #openstack-meeting-cp02:44
*** jokke_ has quit IRC02:47
*** jokke_ has joined #openstack-meeting-cp02:47
*** markvoelker has quit IRC02:49
*** sdake has quit IRC03:19
*** sdake has joined #openstack-meeting-cp03:47
*** stevemar has joined #openstack-meeting-cp03:53
*** david-lyle has joined #openstack-meeting-cp04:13
*** david-lyle has quit IRC04:36
*** markvoelker has joined #openstack-meeting-cp04:45
*** markvoelker has quit IRC04:50
*** david-lyle has joined #openstack-meeting-cp04:50
*** david-lyle has quit IRC04:56
*** nikhil has quit IRC06:32
*** sdake has quit IRC06:43
*** markvoelker has joined #openstack-meeting-cp06:46
*** markvoelker has quit IRC06:50
*** sdake has joined #openstack-meeting-cp06:59
*** sheel has joined #openstack-meeting-cp07:02
*** sdake has quit IRC07:17
*** nikhil has joined #openstack-meeting-cp07:32
*** markvoelker has joined #openstack-meeting-cp08:47
*** markvoelker has quit IRC08:51
*** sheeprine has quit IRC09:47
*** sheeprine has joined #openstack-meeting-cp09:49
*** sdake has joined #openstack-meeting-cp09:51
*** sdake has quit IRC10:06
*** sdake has joined #openstack-meeting-cp10:43
*** markvoelker has joined #openstack-meeting-cp10:47
*** markvoelker has quit IRC10:52
*** sdake has quit IRC10:53
*** sdague has joined #openstack-meeting-cp10:55
*** flaper87 has quit IRC10:56
*** flaper87 has joined #openstack-meeting-cp10:56
*** sdake has joined #openstack-meeting-cp11:06
*** sdake has quit IRC11:16
*** dims has joined #openstack-meeting-cp11:29
*** dims has quit IRC11:32
*** dims has joined #openstack-meeting-cp11:32
-openstackstatus- NOTICE: Infra currently has a long backlog. Please be patient and where possible avoid rechecks while it catches up.12:06
*** sheeprine has quit IRC12:45
*** sheeprine has joined #openstack-meeting-cp12:46
*** markvoelker has joined #openstack-meeting-cp12:48
*** markvoelker has quit IRC12:53
*** sheeprine has quit IRC13:09
*** sheeprine has joined #openstack-meeting-cp13:10
*** sheeprine has quit IRC13:30
*** sheeprine has joined #openstack-meeting-cp13:30
*** annegentle has joined #openstack-meeting-cp13:35
*** markvoelker has joined #openstack-meeting-cp13:47
*** ninag has joined #openstack-meeting-cp13:47
*** bswartz has joined #openstack-meeting-cp14:01
*** sdake has joined #openstack-meeting-cp14:35
*** diablo_rojo has joined #openstack-meeting-cp14:42
*** diablo_rojo has left #openstack-meeting-cp14:42
*** sdake has quit IRC14:58
*** annegentle has quit IRC15:12
*** mestery has quit IRC15:19
*** mestery has joined #openstack-meeting-cp15:19
*** annegentle has joined #openstack-meeting-cp15:35
*** annegentle has quit IRC15:42
*** annegentle has joined #openstack-meeting-cp15:42
*** angdraug has joined #openstack-meeting-cp15:57
*** annegentle has quit IRC16:52
*** thingee has quit IRC16:53
*** sdake has joined #openstack-meeting-cp17:06
*** sdake has quit IRC17:22
*** sdake has joined #openstack-meeting-cp17:23
*** david-lyle has joined #openstack-meeting-cp17:30
*** annegentle has joined #openstack-meeting-cp17:53
*** sdake has quit IRC17:54
*** david-lyle has quit IRC17:55
*** david-lyle_ has joined #openstack-meeting-cp17:55
*** sdake has joined #openstack-meeting-cp17:57
*** annegentle has quit IRC17:59
*** annegentle has joined #openstack-meeting-cp18:07
*** annegentle has quit IRC18:37
*** sdake has quit IRC18:43
*** angdraug has quit IRC18:45
*** dims_ has joined #openstack-meeting-cp19:11
*** dims has quit IRC19:11
*** annegentle has joined #openstack-meeting-cp19:12
*** annegentle has quit IRC19:13
*** angdraug has joined #openstack-meeting-cp19:13
*** annegentle has joined #openstack-meeting-cp19:16
*** dims_ has quit IRC19:58
*** Guest71383 is now known as redrobot20:01
*** sdake has joined #openstack-meeting-cp20:04
*** angdraug has quit IRC20:11
*** dims has joined #openstack-meeting-cp20:12
*** david-lyle_ is now known as david-lyle20:12
*** sdake has quit IRC20:22
*** dims has quit IRC20:29
*** annegentle has quit IRC20:31
*** annegentle has joined #openstack-meeting-cp20:32
*** angdraug has joined #openstack-meeting-cp20:59
*** mc_nair has joined #openstack-meeting-cp21:00
*** vilobhmm11 has joined #openstack-meeting-cp21:01
vilobhmm11hi21:01
nikhil#startmeeting quotas-wg21:01
openstackMeeting started Mon Feb 29 21:01:33 2016 UTC and is due to finish in 60 minutes.  The chair is nikhil. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: quotas-wg)"21:01
openstackThe meeting name has been set to 'quotas_wg'21:01
ninaghi21:01
mc_nairhey there21:01
nikhil#topic roll call21:01
*** openstack changes topic to "roll call (Meeting topic: quotas-wg)"21:01
vilobhmm11vilobhmm21:01
vilobhmm11o/21:02
nikhilI see vilobhmm11, ninag and mc_nair already here21:02
nikhilLet's wait a couple mins for folks to show up21:02
vilobhmm11sure21:02
nikhilLet me highlight reminder21:03
nikhilCourtesy meeting reminder: nikhil, vilobhmm, DuncanT, mc_nair, <add your nick before>21:03
vilobhmm11lets start21:04
nikhil#topic agenda21:04
*** openstack changes topic to "agenda (Meeting topic: quotas-wg)"21:04
DuncanTHi. Posting from my mobile, so a touch lagged, sorry21:04
nikhil#link https://etherpad.openstack.org/p/quotas-wg-meeting-agenda21:04
nikhilHI DuncanT21:04
nikhilthanks for adding items to the agenda21:04
nikhilgreat to see input already!21:04
vilobhmm11+121:04
nikhilThis is our first meeting21:05
nikhilso the purpose is for everyone to get introduced, express level ofinterest and define scope and objectives21:05
nikhilWe also wanted to get some early eyes on the spec and establish momentum in the freeze period21:05
nikhilso that we can have some clear, concise and productive conversations at the summit21:06
nikhilAlso, one aim is to gather input at this close-nit gathering and then share insights to the wider audience from time to time at the regular cross project meetings21:06
nikhilSo, let's start with a very brief introductions, interests etc.21:07
nikhil#topic Introductions, interests, objectives, etc.21:07
*** openstack changes topic to "Introductions, interests, objectives, etc. (Meeting topic: quotas-wg)"21:07
nikhilI can go first in people prefer..21:07
mc_nairsure :)21:08
nikhilI am Nikhil Komawar, primarily focusing on Glance and Searchlight :)21:08
nikhilI am interested in this work to get cross project input to glance for the quotas work in the coming up cycle and help prioritize it.21:09
mc_nairhey - I'm Ryan McNair - work on Cinder and have been doing a lot of work with Nested Quotas in Cinder for the past month or so21:09
DuncanTI'm DuncanT, cinder core, and my main interest is in seeing this attempt not repeat the mistakes that the cinder nested quota code made, which can be subsided quite easily in one line :-) It should be noted in terrible at actually finding time to write code, but I'm pretty good on reviews21:09
DuncanTDuncan Thomas, HPE currently21:09
nikhil++21:10
nikhilvilobhmm11: you're next21:10
nikhilvilobhmm11: I am aware that you21:10
nikhilyou've a conflicting mtg21:10
nikhilso if you want me to move please send a ack21:10
* smcginnis is lurking21:10
vilobhmm11vilobhmm I am Magnum core. I have worked in the areas of Quotas in Nova/Cinder/Magnum. Problems with quotas in normal use-case and at scale.21:10
nikhil:)21:10
vilobhmm11First to introduce and implement Nested Quota in Cinder21:11
vilobhmm11Working on Quota Flavor Classes, Quota by Flavor, Quota by Availability Zone, Quota by X21:11
vilobhmm11so have worked/focussed more on quota in general :)21:11
vilobhmm11the aim is to make a common entity21:11
vilobhmm11which will be useful for all the projects21:11
vilobhmm11and new upcoming projects who plan to use quota does nto have to re-invent the wheel21:12
vilobhmm11and spend additional cycles21:12
ninag’m Nina Goradia…interested in getting hierarchical quota support in Glance..would like it to be consistent across projects, but am open to whether or not it needs to be a common code base21:12
nikhilvilobhmm11: thanks, glad to get your insights!21:13
nikhilninag: and that sounds like a good point to discuss early on!21:13
nikhilI guess those are all  for today.21:14
nikhilThanks everyone, glad to know the interest groups.21:14
vilobhmm11nikhil : Few points we should dicsuss early on : #1. whether common code base (Y/N) #2. If common code base then should it be a library or a service21:14
vilobhmm11just to add to ninag21:15
nikhilvilobhmm11: sounds good, should we do that for open discussion today and carry it on next week?21:15
vilobhmm11nikhil : open discussion  sounds good to me;21:15
nikhilcool21:16
nikhilMoving on21:16
nikhil#topic Spec (vilobhmm)21:16
*** openstack changes topic to "Spec (vilobhmm) (Meeting topic: quotas-wg)"21:16
nikhil#link https://review.openstack.org/#/c/284454/21:16
nikhilvilobhmm11: mind giving us a tl;dr; version?21:16
vilobhmm11sure21:16
nikhil(for record keeping here in the logs)21:16
vilobhmm11so would request everyone to have a look and give there feedback21:16
*** sheel has quit IRC21:17
vilobhmm11right now i don't want to get into library vs service debate as that is the main reason why this *idea of common quota thingee* didn't made in the past21:17
vilobhmm11so calling it an entity21:17
vilobhmm11we can discuss what it should be21:17
vilobhmm11library/service21:18
vilobhmm11so goal here is to have a common *entity* which #1. minimizes or zeros down the code duplication #.2 New project and use it and enable quota #3. New features like nested quota, quota by x can be added on demand21:18
vilobhmm11#2.New project can use it and enable quota21:19
vilobhmm11that is the *WHY* part21:19
vilobhmm11now about *HOW* to do it have included details in the "Proposed change" section please have look21:20
vilobhmm11all feedbacks are welcome :)21:20
nikhil++21:20
nikhilI guess that sort of pushes the discussion around the scope of the cross-prj initiative21:21
mc_naircool, will take a look at the spec right after the meeting21:21
vilobhmm11yup21:21
nikhilTo me it seems like we really need to understand the use cases for proposing a new project21:21
vilobhmm11hence renamed the spec as well to "Delimiter - Cross Project Quota Enforcement and Management"21:21
vilobhmm11nikhil : sure21:21
nikhilIt would be a overhead for maintaining a new service for quotas if projects can't implement it internally21:22
nikhilAnd that's another part of the scope discussion comes into play21:22
nikhilI would like to know21:22
vilobhmm11nikhil : Regarding use-case for a new project/library/entiry - few details are covered here https://review.openstack.org/#/c/284454/4/specs/quota-library.rst as part of "Problem Description"21:23
*** dims has joined #openstack-meeting-cp21:23
nikhilvilobhmm11: ++21:23
vilobhmm11nikhil : three of the most common problems that were seen as part of ops meetup and previous dev meetup are jotted down here https://review.openstack.org/#/c/284454/4/specs/quota-library.rst21:24
nikhilI agree on the technical implications and the optimizations aspects of things21:24
*** thingee has joined #openstack-meeting-cp21:24
nikhilI would agree to those21:24
nikhiland have had the pleasure of experiencing the #3 of that many a times first hand ;)21:25
nikhilmy use case concerns were around:21:25
nikhil1. Are there custom glitches in projects around quotas? (one feature/resource dependent on another in subtle way)21:25
DuncanTI can't follow all those links right now, sorry, I'll have to catch up later21:25
nikhil2. Do projects need to have DB migrations that would affect quotas work and that can't be handled outside of the project scope? (May be upgrades, or quota lib adding a dependency to oslo.vo?)21:26
nikhilDuncanT: np21:26
vilobhmm11these are good points and i think we should cover it as part of spec21:27
vilobhmm11nikhil : ^^21:27
mc_nairnikhil: for 1) are you referring to quotas that are related/dependant?21:27
vilobhmm11i can update the spec with more details21:27
nikhil3. If done as a separate project, how do we take care of cross-resource transactions within the project?21:27
nikhilmc_nair: yes, quotas that are dependent21:28
nikhilvilobhmm11: the #3 is my perspective of images and image members in glance.21:29
nikhilmembers are not independent of images but21:29
nikhilimage <-> members have a many to many relationship21:29
nikhiloops, I realized that we're running over.21:30
nikhilFor some reason, forgot this was a 30 mins meeting. sorry about that.21:30
nikhilDo folks mind carrying this for another 5 mins?21:30
nikhilI do not think there's another meeting in this room.21:30
mc_nairI don't mind21:30
nikhilok great.21:31
nikhilanyone else, have objections?21:31
ninagnope, I can continue21:31
DuncanTI'm fine continuing21:32
nikhil#info meeting to be carried on till 2135 UTC21:32
mc_nairquickly running out of time on that too :)21:32
nikhilSo, to better define the scope , I think we need a wider use case feedback.21:32
nikhilAnd thanks vilobhmm11 for willing to add some initial thoughts on those in the spec.21:33
nikhilIt would be good to get them on the review or during CP meetings.21:33
vilobhmm11nikhil : sure…but this problems is only for existing projects who have quotas right now..and we need to think on migration plan before the switch happens21:33
DuncanTJust to get my 5 cent worth in, my main point was going to be that you need to specify behaviours, including corner cases, in extreme detail, from the beginning... Figuring then out as you go doesn't work out, and writing the tests first is probably a good way to proceed21:33
nikhilvilobhmm11:  and DuncanT: both are great points indeed!21:34
nikhilbut they conflict  a bit ;)21:34
nikhilI would like us to think about the migration and if that's a possibility..21:34
nikhilbut the first point to answer is:21:34
nikhil1. separate repo or not21:35
nikhil2. if yes, lib or project21:35
vilobhmm11nikhil : those are the starting points imho21:35
nikhiland that would be essential to get from other projects too I think21:35
nikhiland we're out of time again :)21:35
DuncanTSeparate repo is the only way that I can see this making progress without falling into the mess of fixing a specific project's bugs21:36
DuncanTLib or project I don't care21:36
mc_nair+121:36
nikhilok, that sounds good.21:36
vilobhmm11if we have a concensus on 1. separate repo or not 2. if yes, lib or project we have a clear path and should then think of migration, testing21:36
nikhilwhat do ppl think for adding a voting section on the spec on this topic?21:37
vilobhmm11nikhil : ^^21:37
nikhilthis == separate repo or not21:37
DuncanTWhat is the practical difference between a lib and a project?21:37
vilobhmm11DuncanT : library vs service (project)21:37
nikhilDuncanT: project would mean a API backed by DB21:37
vilobhmm11is what nikhil meant21:37
DuncanTGot you. Thanks21:38
nikhilmore like: Quotas as a Service (QaaS)21:38
DuncanTThe downsides of going through an API are a) failure modes and b) latency21:38
ninagI think a separate repo makes sense..and if the behavior is fleshed out and documented..then it will help decide whether it meets all needs from projetcs21:39
DuncanTThe upsides are debugability and consistency21:39
ninagor whether we have the cross-resource dependencies..and will help towards the library or project decision21:39
DuncanTI think the consumer entry points are pretty much the same whether we go project or lib (reserve, commit, unreserved, list, edit, etc)21:40
nikhilDuncanT: yeah, I think another downside is "concurrency issue" for intra-prj resources21:40
*** dims has quit IRC21:40
nikhilDuncanT: yes, agreed on the entry points.21:41
nikhilok, I think we'd call off on the meeting today. We can definitely continue the discussion on #openstack-dev if we like.21:41
DuncanTI think we've got plenty to think about anyway21:42
nikhilsorry for running over and we will try to be more precise from next week onwards in case people have conflicts and prior commitments.21:42
mc_nairsounds good21:42
nikhilDuncanT: agreed21:42
nikhilThanks all for joining.21:42
nikhil#endmeeting21:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:43
openstackMeeting ended Mon Feb 29 21:43:07 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/quotas_wg/2016/quotas_wg.2016-02-29-21.01.html21:43
*** mc_nair has left #openstack-meeting-cp21:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/quotas_wg/2016/quotas_wg.2016-02-29-21.01.txt21:43
openstackLog:            http://eavesdrop.openstack.org/meetings/quotas_wg/2016/quotas_wg.2016-02-29-21.01.log.html21:43
*** dims has joined #openstack-meeting-cp21:44
*** vilobhmm11 has quit IRC21:58
*** vilobhmm11 has joined #openstack-meeting-cp21:59
*** vilobhmm11 has quit IRC22:00
*** vilobhmm11 has joined #openstack-meeting-cp22:00
*** annegentle has quit IRC22:02
*** sdake has joined #openstack-meeting-cp22:05
*** dims has quit IRC22:09
*** sdake has quit IRC22:14
*** sdague has quit IRC22:18
*** sdake has joined #openstack-meeting-cp22:18
*** reed_ has joined #openstack-meeting-cp22:35
*** sdake has quit IRC22:46
*** ninag has quit IRC22:47
*** sdake has joined #openstack-meeting-cp23:03
*** dims has joined #openstack-meeting-cp23:14
*** ninag has joined #openstack-meeting-cp23:18
*** ninag has quit IRC23:22

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!