Tuesday, 2016-05-03

*** markvoelker has joined #openstack-meeting-cp00:09
*** sigmavirus24 is now known as sigmavirus24_awa00:45
*** david-lyle has joined #openstack-meeting-cp01:09
*** _amrith_ is now known as amrith02:19
*** sdake has joined #openstack-meeting-cp02:20
*** amrith is now known as _amrith_03:04
*** markvoelker has quit IRC04:19
*** markvoelker has joined #openstack-meeting-cp05:19
*** markvoelker has quit IRC05:24
*** sdake has quit IRC05:37
*** sdake has joined #openstack-meeting-cp05:38
*** markvoelker has joined #openstack-meeting-cp06:20
*** markvoelker has quit IRC06:25
-openstackstatus- NOTICE: Filesystem on logs.openstack.org is broken, we are on the process of repairing it. Please stop checking your jobs until further notice06:44
*** ChanServ changes topic to "Filesystem on logs.openstack.org is broken, we are on the process of repairing it. Please stop checking your jobs until further notice"06:44
*** ebalduf has quit IRC06:57
*** beekhof has quit IRC07:07
*** markvoelker has joined #openstack-meeting-cp07:21
*** markvoelker has quit IRC07:26
*** beekhof has joined #openstack-meeting-cp07:27
*** sdake has quit IRC07:56
*** DuncanT_ has joined #openstack-meeting-cp07:58
*** scottda has quit IRC07:58
*** DuncanT has quit IRC07:58
*** scottda has joined #openstack-meeting-cp07:58
*** scottda has quit IRC07:58
*** scottda has joined #openstack-meeting-cp07:58
*** docaedo has quit IRC07:58
*** lbragstad has quit IRC07:58
*** lbragstad has joined #openstack-meeting-cp07:59
*** docaedo has joined #openstack-meeting-cp08:00
*** DuncanT_ is now known as DuncanT08:02
*** markvoelker has joined #openstack-meeting-cp08:22
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:24
-openstackstatus- NOTICE: Logs filesystem has been successfully restored, please recheck your jobs08:25
*** markvoelker has quit IRC08:27
-openstackstatus- NOTICE: Filesystem on docs-draft.openstack.org is broken, we are on the process of repairing it. Please stop checking jobs using this filesystem until further notice08:35
*** vgridnev has quit IRC09:05
-openstackstatus- NOTICE: Docs-draft filesystem has been restored. Please check your affected jobs again09:22
*** belmoreira has joined #openstack-meeting-cp09:23
*** markvoelker has joined #openstack-meeting-cp09:23
*** sheeprine_ is now known as sheeprine09:23
*** sheeprine has joined #openstack-meeting-cp09:23
*** markvoelker has quit IRC09:28
*** _amrith_ is now known as amrith10:14
*** markvoelker has joined #openstack-meeting-cp10:24
*** sdague has joined #openstack-meeting-cp10:25
*** markvoelker has quit IRC10:28
*** amrith is now known as _amrith_11:02
*** markvoelker has joined #openstack-meeting-cp11:24
*** markvoelker has quit IRC11:29
*** markvoelker has joined #openstack-meeting-cp12:22
*** xyang1 has joined #openstack-meeting-cp12:53
*** raildo-afk is now known as raildo12:58
*** sheel has joined #openstack-meeting-cp13:42
*** ebalduf has joined #openstack-meeting-cp13:51
*** sigmavirus24_awa is now known as sigmavirus2413:56
*** mageshgv has joined #openstack-meeting-cp14:06
*** mageshgv has quit IRC14:46
*** ebalduf has quit IRC14:48
*** ebalduf has joined #openstack-meeting-cp14:49
*** mageshgv has joined #openstack-meeting-cp14:57
*** hemnafk is now known as hemna15:09
*** sdake has joined #openstack-meeting-cp15:23
*** sdake_ has joined #openstack-meeting-cp15:26
*** belmoreira has quit IRC15:26
*** sdake has quit IRC15:28
*** diablo_rojo has joined #openstack-meeting-cp15:46
*** diablo_rojo1 has joined #openstack-meeting-cp16:18
*** diablo_rojo has quit IRC16:21
*** diablo_rojo has joined #openstack-meeting-cp16:22
*** diablo_rojo1 has quit IRC16:23
*** vilobhmm111 has joined #openstack-meeting-cp16:59
vilobhmm111#startmeeting quotas-wg16:59
openstackMeeting started Tue May  3 16:59:30 2016 UTC and is due to finish in 60 minutes.  The chair is vilobhmm111. Information about MeetBot at http://wiki.debian.org/MeetBot.16:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:59
*** openstack changes topic to " (Meeting topic: quotas-wg)"16:59
openstackThe meeting name has been set to 'quotas_wg'16:59
vilobhmm111hi everyone16:59
nikhilo/16:59
vilobhmm111welcome back after the summit !16:59
nikhil:)16:59
vilobhmm111hi nikhil17:00
nikhilhi vilobhmm11117:00
nikhilguess just two of us :)17:00
vilobhmm111nikhil : :)17:00
vilobhmm111seems like it17:01
vilobhmm111thanks for reviewing the spec17:01
*** Qijing has joined #openstack-meeting-cp17:01
vilobhmm111also please include the glance use case in the review17:01
nikhilyw!17:01
nikhilI think we are deferring to the way delimiter evolution for now17:01
nikhilthe glance use case described during the summit may or may not be implemented17:01
nikhilbasically there are two school of thoughts there17:02
nikhilone that says we need reservation like model and other that doesn't care17:02
vilobhmm111nikhil : ok..please explain so that all of us are aware of it17:02
vilobhmm111hi Qijing17:02
Qijinghi17:02
vilobhmm111welcome17:02
vilobhmm111Qijing17:02
Qijingthx17:03
nikhilvilobhmm111: want the description now?17:03
nikhilI can add comments to the spec as well17:03
vilobhmm111nikhil : not right now17:03
vilobhmm111in the spec17:03
nikhilcool17:03
vilobhmm111you can comment there17:03
vilobhmm111i will see if we can have the glance cases covered17:04
vilobhmm111#agenda delimiter design summit talk17:04
vilobhmm111irc://irc.freenode.net:6667/#agenda delimiter-design-summit-talk17:05
vilobhmm111for anyone who missed the summit talk17:05
vilobhmm111here is the etherpad https://etherpad.openstack.org/p/newton-quota-library which captures the discussion17:05
vilobhmm111slides for the library proposal : http://www.slideshare.net/vilobh/delimiter-openstack-cross-project-quota-library-proposal17:05
vilobhmm111feel free to update your thoughts on the spec https://review.openstack.org/#/c/284454/17:06
vilobhmm111so the conclusion is :17:06
vilobhmm111#1. Delimiter will get inputs from the respective projects about (usage_count, resources, generation_id)17:07
vilobhmm111#2. generation_id will be used to take into consideration the point in time view of the resource usage17:08
vilobhmm111#3. right now only nova has the concept of generation_id17:08
vilobhmm111we as a team need to evaluate the benefits of generation id and does it make sense to purse that route as it adds an additonal dependency on any project consuming deleimiter to add the generation id concept17:09
nikhil++17:09
vilobhmm111#topic things-to-do17:11
*** openstack changes topic to "things-to-do (Meeting topic: quotas-wg)"17:11
Qijingwhat about the reserve17:11
Qijingwill still use reserver to ensure the sequence of operations?17:11
vilobhmm111Qijing : Delimiter won't have the concept of quotas..but for specific use-cases that glance needs and which nikhil will update on the spec we need to think more on what can be done17:11
vilobhmm111*concept of reservations*17:12
nikhilyeah..17:12
Qijingok17:12
nikhilI am inclining towards defining more of each of those terms more17:12
vilobhmm111Qijing : Delimiter won't have the concept of reservations17:12
nikhilI was told that industry standard is to use only two terms for quota experience -- limits and reservations17:13
vilobhmm111nikhil : sure i saw your feedback will discuss with you before i make an update today..will send you an e-mail or post it on etherpad before we finalize17:13
nikhilsounds good. thanks.17:13
vilobhmm111nikhil : ok17:13
vilobhmm111ok back to things-to-do17:13
nikhilvilobhmm111: I have a couple items to discuss today after you are done with the agenda17:14
vilobhmm111nikhil : sure17:14
vilobhmm111just give me 10 more min17:14
nikhilnp17:14
vilobhmm111#1. setup launchpad page for the library so that we can keep track of features and bugs17:14
*** _amrith_ is now known as amrith17:14
vilobhmm111what does everyone think about it ?17:15
nikhilmakes sense17:15
vilobhmm111link to generation-id spec/blueprint which nova is/plan to use : https://review.openstack.org/#/c/283253/17:15
vilobhmm111nikhil, _amrith_, Qijing : ^^17:15
Qijing+117:15
vilobhmm111#2. get an agreement on the spec with the design proposed here https://etherpad.openstack.org/p/newton-quota-library17:17
vilobhmm111nikhil all upto you17:17
nikhil:)17:18
nikhilI need a bit more time but I think we can start the groundwork until then?17:18
nikhilit will take a bit of effort to bootstrap things and we can know more on where things are heading then17:19
Qijingthx nikhil17:19
nikhilvilobhmm111: oh, did you mean that you are done with agenda for today?17:19
nikhilQijing: yw :-)17:20
nikhilif so, can we change the topic to "setting quota limits"?17:20
vilobhmm111nikhil : yes17:21
vilobhmm111nikhil : for sure we need to start with the ground work17:21
nikhilok17:22
nikhilvilobhmm111 are we discussing anything more on this topic?17:22
nikhil!ping17:22
openstackpong17:22
vilobhmm111nikhil : sorry getting network issue17:23
nikhilvilobhmm111: you still here?17:23
nikhilah17:24
vilobhmm111ya lets discuss17:24
vilobhmm111you have anything specific about getting started17:24
vilobhmm111i thought wills setup17:24
vilobhmm111#1. repo17:24
nikhilnothing much17:24
nikhilok17:24
vilobhmm111#2. launchpad page17:24
vilobhmm111#3. drop e-mail to ML asking interested people to contribute17:25
nikhilhm17:25
vilobhmm111i think that can be initial set of steps.17:25
nikhilmay be a #0. send email to ML giving a summary of the discussion at the summit, approach, spec plan & scope17:26
vilobhmm111nikhil : yep17:26
nikhilalthough, spec plan and scope can be merely copy paste of the first para17:26
vilobhmm111definately17:26
nikhilvilobhmm111: I think there's a great doc page on setting up projects. dims had given the link to us before the summit.17:26
vilobhmm111but ya since not everyone could make it to the design summit session it would be nice to give an overview and the next step planned17:27
nikhilwe may need to setup stuff in gerrit like groups giving +W access etc17:27
vilobhmm111nikhil : sure17:27
nikhilvilobhmm111: yeah, I think a few people missed the summit session as well during the summit but were interested in it17:28
nikhilduring the summit == although they were at the summit17:28
vilobhmm111ha17:28
nikhil:)17:28
vilobhmm111sounds like a good plan17:28
nikhil++17:29
vilobhmm111let me rephrase17:29
vilobhmm111#1. Drop ML about mission, scope, next steps based on what was discussed in the design summit session17:29
vilobhmm111#2. Setup repo, gerrit stuff, launchpad17:29
vilobhmm111#3. Spec needs update move quickly with spec - vilobhmm17:30
Qijingwhat is the name of the repo?17:31
vilobhmm111Qijing : we have to setup new17:31
vilobhmm111it will be mostly "delimiter"17:31
nikhil!ping17:32
openstackpong17:32
Qijingit will be under github.com/ or github.com/openstack17:32
nikhilgithub.com/openstack17:32
vilobhmm111Qijing : will need to check what is the prescribed policy17:32
vilobhmm111but imho it should be github.com/openstack17:32
nikhilactually, the official page is git.openstack.org/openstack17:33
vilobhmm111nikhil : ok17:33
vilobhmm111nikhil, Qijing : does the above mentioned plan seem ok to you ?17:34
nikhil!ping17:34
openstackpong17:34
nikhilvilobhmm111: yeah, makes sense17:34
Qijingvery good to me17:34
vilobhmm111ok17:34
*** sheel has quit IRC17:34
nikhilI have a couple of technical questions for today17:34
vilobhmm111nikhil : sure please go ahead17:35
nikhilthat may be worth addressing in the spec17:35
vilobhmm111sure17:35
nikhil#topic setting quota limits17:35
nikhil!ping17:35
openstackpong17:35
* nikhil is getting newtwork lag17:35
nikhilvilobhmm111: you may need to switch the topic (only chairs are allowed afaik)17:36
vilobhmm111nikhil : what specifically about setting quota limits ?17:36
nikhilbut the questions are:17:36
vilobhmm111irc://irc.freenode.net:6667/#topic setting quota limits17:36
vilobhmm111#topic setting-quota-limits17:36
*** openstack changes topic to "setting-quota-limits (Meeting topic: quotas-wg)"17:36
nikhil1. who can set the quota limits?17:36
nikhil2. where are the quota limits set?17:36
*** sheel has joined #openstack-meeting-cp17:37
vilobhmm111lets do one at a time17:37
*** patrickeast has quit IRC17:37
vilobhmm111#1. who can set the quota limits?17:37
vilobhmm111depends on what project model we are using17:37
Qijingcloud-admin?17:37
nikhiloh I've 4 😃17:37
vilobhmm111nikhil : oops thats a lot :P17:37
nikhilvilobhmm111: right17:37
vilobhmm111please go ahead17:37
vilobhmm111sorry to interrupt17:38
nikhilok, let me jot them down17:38
vilobhmm111ok17:38
nikhilthen we can go over them one by one17:38
*** patrickeast has joined #openstack-meeting-cp17:38
vilobhmm111sure17:38
nikhil3. in case of hierarchical namespaces how do individual services figure out the changes in the tree and consider quota limits accordingly?17:39
nikhil4. do we need to have upgrade story for going from non-nested to nested quota limits? (see 4 types of quota limits described in the spec and the comment)17:39
* nikhil done17:39
nikhil!ping17:39
openstackpong17:39
vilobhmm111nikhil17:40
vilobhmm111irc://irc.freenode.net:6667/#1. who can set the quota limits?17:40
vilobhmm111#1. who can set the quota limits17:40
vilobhmm111depends on what project model we are using17:40
vilobhmm111if we are using flat ; only admin can update for all the projects …this admin will be the cloud-admin17:40
vilobhmm111if we are using hierarchical ; admin or parent of the subtree can update the project quotas17:41
nikhilcloud admin or service admin?17:41
vilobhmm111service-admin17:41
nikhilok17:41
vilobhmm111the cloud -admin also has the priviledge to do so if needed17:41
vilobhmm111since cloud-admin is kinda superuser17:42
nikhilsure, but not recommended17:42
nikhil?17:42
vilobhmm111not recommended yes17:42
nikhilcool17:42
vilobhmm111cloud-admin interfaces or interacts with service-admin17:42
vilobhmm111to update/delegate quota17:42
Qijingservice admin is just generic user?17:42
vilobhmm111and then its upto the service-admin to manage respective projects in the hierarchy17:43
vilobhmm111Qijing : service admin is a user with more permissions than normal user..as the name suggest he/she is an admin17:43
Qijingok17:44
vilobhmm111nikhil : if this answer is clear we can move to next one17:44
nikhilvilobhmm111: yes, thanks. clear for me17:44
vilobhmm111nikhil : cool17:44
vilobhmm111#2. where are the quota limits set?17:44
Qijingservice admin can update the limits of its parent project?17:44
vilobhmm111right now there is a table in every project which maintains details about project/resouce limits17:45
vilobhmm111usually its called quotas17:45
vilobhmm111"quotas"17:45
vilobhmm111by default the values are picked up from .conf files17:45
vilobhmm111#3. in case of hierarchical namespaces how do individual services figure out the changes in the tree and consider quota limits accordingly?17:46
nikhilok17:46
nikhil!ping17:47
openstackpong17:47
vilobhmm111nikhil : just to clarify did you mean that if resource get over consumed how will the parent know about it ?17:48
nikhilvilobhmm111: correct and if there is some weirdness between what admin set, value picked from conf file and type  of quota supported17:49
nikhilbasically ensuring that when a quota limit is set, it is set correctly17:49
vilobhmm111code will rely on one source of truth the value set in db17:50
Qijingneed to check the correctness when read from conf file17:50
nikhilok17:50
nikhilso when a admin tried to set_quota, delimiter will figure it out for them if they are setting correctly?17:50
nikhiltries*17:51
Qijingyes17:51
vilobhmm111nikhil : there can be 3 cases17:52
nikhilok?17:52
vilobhmm111#1. project->delimiter->set_quotas->(resource available)->"yes" grant it"17:52
vilobhmm111#2.project->delimiter->set_quotas->(resource available)->"no" not enough resource available exception"17:53
vilobhmm111with this exception service-admin can talk to cloud-admin to increase quota17:54
vilobhmm111so short answer17:54
nikhilok, I am assuming they will have to physically talk to :)17:54
vilobhmm111not necessarily17:55
vilobhmm111we can have a logic to17:55
vilobhmm111#1. figure out parent of service-admin which is the cloud-admin17:55
vilobhmm111#2. send an rpc or something and get the quota extended17:55
vilobhmm111but for this the cloud-admin needs to be aware of the inventory details17:56
vilobhmm111which is kind of tricky17:56
nikhil:)17:56
vilobhmm111so for simplicity17:56
vilobhmm111lets for now raise an exception17:56
nikhilyes17:56
nikhilthat works17:56
vilobhmm111and let them talk physically :)17:56
nikhilperfect17:56
vilobhmm111we can enhance it further if needed17:56
Qijingsounds good17:56
nikhilwhat happens if the hierarchy of the projects17:56
nikhildoesn't allow the default conf value to be set17:57
nikhilwe set min(conf, available_resource_limit)?17:57
vilobhmm111yup17:57
nikhilk, so that's done by delimiter17:57
vilobhmm111yes17:57
nikhilso, we keep talking to keystone during this process17:57
vilobhmm111rigght now keystone is not ok to store info there17:58
vilobhmm111so will query respective projects for the default values17:58
vilobhmm111keystone -> project hierarchy17:58
nikhilhow do individual projects know hierarchy?17:58
vilobhmm111from keystone17:58
Qijingthere is parent_id in keystone, right?17:58
nikhilso, for hierarchy talk to keystone and then compute stuff from projects?17:58
vilobhmm111i will answer #4 later i have to join a meeting now @ work17:59
nikhilk np.17:59
nikhilthanks for your answers17:59
vilobhmm111nikhil : np17:59
nikhilwe can catch up on #4 next week too17:59
vilobhmm111sure17:59
vilobhmm111Qijing, nikhil : thanks for joining17:59
nikhilwill update agenda17:59
nikhilthanks!17:59
vilobhmm111lets keep the conversation up and live17:59
Qijingthx!17:59
vilobhmm111nikhil : sure17:59
vilobhmm111#endmeeting17:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:59
openstackMeeting ended Tue May  3 17:59:50 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/quotas_wg/2016/quotas_wg.2016-05-03-16.59.html17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/quotas_wg/2016/quotas_wg.2016-05-03-16.59.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/quotas_wg/2016/quotas_wg.2016-05-03-16.59.log.html17:59
*** markvoelker has quit IRC18:04
*** tyr_ has joined #openstack-meeting-cp18:05
*** markvoelker has joined #openstack-meeting-cp18:05
*** diablo_rojo has quit IRC18:05
*** diablo_rojo has joined #openstack-meeting-cp18:06
*** markvoelker_ has joined #openstack-meeting-cp18:07
*** markvoelker has quit IRC18:08
*** amrith is now known as _amrith_18:11
*** Qijing has quit IRC18:12
*** _amrith_ is now known as amrith18:16
*** vilobhmm111 has quit IRC18:23
*** vilobhmm11 has joined #openstack-meeting-cp19:31
*** tyr_ has quit IRC19:42
*** david-lyle has quit IRC19:42
*** kfox1111 has quit IRC19:42
*** Kiall has quit IRC19:42
*** fungi has quit IRC19:42
*** persia has quit IRC19:42
*** jgriffith has quit IRC19:42
*** david-lyle has joined #openstack-meeting-cp19:51
*** fungi has joined #openstack-meeting-cp19:51
*** persia has joined #openstack-meeting-cp19:51
*** jgriffith has joined #openstack-meeting-cp19:51
*** tyr_ has joined #openstack-meeting-cp19:51
*** kfox1111 has joined #openstack-meeting-cp19:51
*** Kiall has joined #openstack-meeting-cp19:51
*** rockyg has joined #openstack-meeting-cp20:05
*** amrith is now known as _amrith_20:12
-openstackstatus- NOTICE: restarting apache on review.openstack.org to pick up security patches. Gerrit web ui may disappear for a short time.20:27
*** diablo_rojo has quit IRC20:32
*** vgridnev has joined #openstack-meeting-cp20:51
*** rockyg has quit IRC21:01
*** xarses has joined #openstack-meeting-cp21:08
*** raildo is now known as raildo-afk21:15
*** vgridnev has quit IRC21:17
*** vilobhmm11 has quit IRC21:24
*** vilobhmm11 has joined #openstack-meeting-cp21:25
*** vilobhmm11 has quit IRC21:25
*** vilobhmm11 has joined #openstack-meeting-cp21:26
*** vilobhmm11 has quit IRC21:26
*** vilobhmm11 has joined #openstack-meeting-cp21:27
*** vilobhmm11 has quit IRC21:30
*** vilobhmm11 has joined #openstack-meeting-cp21:30
*** sdake_ is now known as sdake21:33
*** vilobhmm11 has quit IRC21:59
*** vilobhmm11 has joined #openstack-meeting-cp22:02
*** vilobhmm11 has quit IRC22:02
*** vilobhmm11 has joined #openstack-meeting-cp22:03
*** vilobhmm11 has quit IRC22:04
*** mageshgv has quit IRC22:07
*** sigmavirus24 is now known as sigmavirus24_awa22:10
*** xyang1 has quit IRC22:23
*** diablo_rojo has joined #openstack-meeting-cp22:32
*** _amrith_ is now known as amrith22:49
*** sdague has quit IRC22:50
*** sdake has quit IRC22:55
*** sdake has joined #openstack-meeting-cp22:55
*** markvoelker_ has quit IRC23:16

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