Friday, 2017-03-03

*** jathan has quit IRC00:00
*** cwolferh has quit IRC00:00
*** jdandrea has quit IRC00:02
*** kornica has quit IRC00:03
*** jwcroppe has quit IRC00:03
*** gfidente|afk has quit IRC00:05
*** baoli has quit IRC00:06
*** baoli has joined #openstack-dev00:07
*** baoli has quit IRC00:12
*** sdague has quit IRC00:12
*** yassine has joined #openstack-dev00:14
*** dimtruck is now known as zz_dimtruck00:18
*** sdake has joined #openstack-dev00:20
*** thorst has joined #openstack-dev00:20
*** hongbin has quit IRC00:25
*** thorst has quit IRC00:25
*** jwcroppe has joined #openstack-dev00:25
*** salv-orlando has quit IRC00:26
*** xarses_ has quit IRC00:27
*** jwcroppe has quit IRC00:29
*** _cjones_ has quit IRC00:29
*** jwcroppe has joined #openstack-dev00:30
*** _cjones_ has joined #openstack-dev00:30
*** limao has joined #openstack-dev00:30
*** ijw has quit IRC00:31
*** mkoderer__ has quit IRC00:31
*** limao has quit IRC00:32
*** limao has joined #openstack-dev00:32
*** nplanel has joined #openstack-dev00:34
*** _cjones_ has quit IRC00:34
*** markvoelker has quit IRC00:35
*** jmckind has quit IRC00:35
*** markvoelker has joined #openstack-dev00:35
*** furlongm has quit IRC00:36
*** DFFlanders has quit IRC00:40
*** markvoelker has quit IRC00:40
*** yuntongjin has joined #openstack-dev00:40
*** adu has joined #openstack-dev00:41
*** zz_dimtruck is now known as dimtruck00:41
*** jamielennox|away is now known as jamielennox00:43
*** adu has left #openstack-dev00:45
*** iyamahat has quit IRC00:45
*** iyamahat has joined #openstack-dev00:46
*** bkudryavtsev has quit IRC00:46
*** sdake_ has joined #openstack-dev00:48
*** sdake has quit IRC00:48
*** tovin07 has joined #openstack-dev00:50
*** ijw has joined #openstack-dev00:52
*** ijw has quit IRC00:53
*** ijw has joined #openstack-dev00:54
*** retr0h has quit IRC01:02
*** csmart has quit IRC01:03
*** retr0h has joined #openstack-dev01:07
*** yamamoto_ has joined #openstack-dev01:09
*** priteau has joined #openstack-dev01:10
*** csmart has joined #openstack-dev01:11
*** priteau has quit IRC01:14
*** SumitNaiksatam has quit IRC01:18
*** dimtruck is now known as zz_dimtruck01:19
*** zz_dimtruck is now known as dimtruck01:20
*** thorst has joined #openstack-dev01:21
*** yanyanhu has joined #openstack-dev01:23
*** thorst has quit IRC01:25
*** gongysh has joined #openstack-dev01:27
*** jamielennox is now known as jamielennox|away01:29
*** jmckind has joined #openstack-dev01:31
*** sdake has joined #openstack-dev01:32
*** sdake_ has quit IRC01:34
*** jmckind has quit IRC01:35
*** Santhosh_ has quit IRC01:35
*** markvoelker has joined #openstack-dev01:36
*** jamielennox|away is now known as jamielennox01:36
*** thorst has joined #openstack-dev01:37
*** markvoelker has quit IRC01:40
*** thorst has quit IRC01:41
*** markvoelker has joined #openstack-dev01:43
*** bobmel has joined #openstack-dev01:52
*** radhikam has quit IRC01:56
*** bobmel has quit IRC01:57
*** thorst has joined #openstack-dev01:58
*** thorst has quit IRC01:59
*** kbyrne has quit IRC02:00
*** kbyrne has joined #openstack-dev02:02
*** xarses has joined #openstack-dev02:02
*** raunak has quit IRC02:14
EmilienMlbragstad: I'm back online but maybe late for you02:16
lbragstadEmilienM o/02:16
EmilienMlbragstad: how can I help?02:16
lbragstadEmilienM i saw your note about updating the pike goals02:17
lbragstadEmilienM i submitted a patch - https://review.openstack.org/#/c/440840/02:17
* EmilienM clocks02:17
EmilienMclicks*02:17
lbragstadEmilienM i can't seem to find the exact blueprint we used for tracking that work in keystone - i believe it happened sometime between 2012 and 2013 though02:17
EmilienMlbragstad: well, that's good to me02:18
EmilienMkeystone is the best example here, where everything was done already for long time :D02:18
lbragstadEmilienM process wise I'm not sure how much detail you want for completion documents02:18
lbragstad;)02:18
EmilienMlbragstad: no worries, this patch is enough imho02:18
lbragstadEmilienM awesome - that was my question :)02:18
EmilienMlbragstad: cool! thanks for asking02:21
*** gongysh has quit IRC02:22
*** thorst has joined #openstack-dev02:23
*** thorst has quit IRC02:24
*** SumitNaiksatam has joined #openstack-dev02:25
*** yuntongjin1 has joined #openstack-dev02:28
*** yuntongjin has quit IRC02:28
*** radhikam has joined #openstack-dev02:29
*** ijw has quit IRC02:30
*** vnogin has quit IRC02:32
*** kirotawa has joined #openstack-dev02:39
*** fragatin_ has joined #openstack-dev02:47
*** thorst has joined #openstack-dev02:48
*** thorst has quit IRC02:48
*** galstrom_zzz is now known as galstrom02:50
*** amotoki has quit IRC02:50
*** mriedem has quit IRC02:51
*** fragatina has quit IRC02:51
*** fragatin_ has quit IRC02:52
*** raunak has joined #openstack-dev02:56
*** aasthad has quit IRC03:02
*** lucasxu has joined #openstack-dev03:03
*** amotoki has joined #openstack-dev03:06
*** macjack has joined #openstack-dev03:07
*** macjack has quit IRC03:08
*** lucasxu has quit IRC03:10
*** priteau has joined #openstack-dev03:10
*** bkudryavtsev has joined #openstack-dev03:11
*** bkudryavtsev has quit IRC03:12
*** priteau has quit IRC03:15
*** amotoki has quit IRC03:16
*** tuanluong has joined #openstack-dev03:16
*** fragatina has joined #openstack-dev03:19
*** fragatina has quit IRC03:24
*** amotoki has joined #openstack-dev03:28
*** diablo_rojo has quit IRC03:28
*** vnogin has joined #openstack-dev03:32
*** ihrachys has joined #openstack-dev03:34
*** radhikam has quit IRC03:35
*** bswartz has joined #openstack-dev03:36
*** vnogin has quit IRC03:37
*** amotoki has quit IRC03:38
*** galstrom is now known as galstrom_zzz03:41
*** ihrachys has quit IRC03:44
*** achampion has joined #openstack-dev03:50
*** bobmel has joined #openstack-dev03:53
*** thorst has joined #openstack-dev03:54
*** iyamahat has quit IRC03:54
*** yamahata has quit IRC03:54
*** kirotawa has quit IRC03:57
*** bobmel has quit IRC03:58
*** furlongm has joined #openstack-dev03:58
*** thorst has quit IRC03:59
*** nicolasbock has quit IRC03:59
*** lucasxu has joined #openstack-dev03:59
*** nmathew has joined #openstack-dev04:01
*** halprin has quit IRC04:04
*** ShaneDavidson has quit IRC04:08
*** aasthad has joined #openstack-dev04:09
*** SumitNaiksatam has quit IRC04:14
*** diablo_rojo has joined #openstack-dev04:18
*** amotoki has joined #openstack-dev04:20
*** radhikam has joined #openstack-dev04:20
*** yuntongjin1 has quit IRC04:20
*** yuntongjin has joined #openstack-dev04:21
*** bks has joined #openstack-dev04:25
*** psachin has joined #openstack-dev04:34
*** yuntongjin1 has joined #openstack-dev04:37
*** yuntongjin has quit IRC04:37
*** sree has joined #openstack-dev04:40
*** amotoki_ has joined #openstack-dev04:45
*** amotoki has quit IRC04:48
*** sdake_ has joined #openstack-dev04:48
*** karthiks has joined #openstack-dev04:49
*** sdake has quit IRC04:50
*** lucasxu has quit IRC04:52
*** sdake has joined #openstack-dev04:53
*** karthiks has quit IRC04:54
*** thorst has joined #openstack-dev04:55
*** sdake_ has quit IRC04:55
*** spartacloud has quit IRC04:56
*** sridharg has joined #openstack-dev04:58
*** halprin has joined #openstack-dev04:59
*** thorst has quit IRC05:00
*** ihrachys has joined #openstack-dev05:04
*** sdake has quit IRC05:04
*** markvoelker has quit IRC05:07
*** rderose has quit IRC05:07
*** karthiks has joined #openstack-dev05:10
*** Rockyg has quit IRC05:10
*** priteau has joined #openstack-dev05:11
*** ayogi has joined #openstack-dev05:12
*** baoli has joined #openstack-dev05:13
*** sdake has joined #openstack-dev05:14
*** priteau has quit IRC05:16
*** baoli has quit IRC05:17
*** fragatina has joined #openstack-dev05:19
*** sdake has quit IRC05:24
*** fragatin_ has joined #openstack-dev05:24
*** fragatina has quit IRC05:24
*** sdake has joined #openstack-dev05:27
*** fragatin_ has quit IRC05:28
*** eroux has joined #openstack-dev05:29
*** vnogin has joined #openstack-dev05:34
*** vnogin has quit IRC05:39
*** ihrachys has quit IRC05:45
*** SumitNaiksatam has joined #openstack-dev05:47
*** iyamahat has joined #openstack-dev05:47
*** ksobkowiak has quit IRC05:48
*** sdake_ has joined #openstack-dev05:51
*** yamahata has joined #openstack-dev05:52
*** sdake has quit IRC05:53
*** SumitNaiksatam has quit IRC05:53
*** bobmel has joined #openstack-dev05:54
*** thorst has joined #openstack-dev05:56
*** halprin has quit IRC05:56
*** bobmel has quit IRC05:58
*** dimtruck is now known as zz_dimtruck05:58
*** sridhargaddam has joined #openstack-dev05:59
*** sridharg has quit IRC05:59
*** thorst has quit IRC06:01
*** yuntongjin1 has quit IRC06:01
*** yuntongjin has joined #openstack-dev06:02
*** sdake_ has quit IRC06:05
*** markvoelker has joined #openstack-dev06:07
*** raunak has quit IRC06:07
*** dhajare has joined #openstack-dev06:09
*** nmathew- has joined #openstack-dev06:10
*** nmathew has quit IRC06:10
*** nmathew has joined #openstack-dev06:11
*** AnilV4 has joined #openstack-dev06:12
*** markvoelker has quit IRC06:12
*** nmathew- has quit IRC06:14
*** yuntongjin1 has joined #openstack-dev06:16
*** yuntongjin has quit IRC06:16
*** iyamahat has quit IRC06:22
*** tovin07 has quit IRC06:23
*** tovin07 has joined #openstack-dev06:24
*** ltomasbo|away is now known as ltomasbo06:24
*** yuntongjin1 has quit IRC06:26
*** yuntongjin has joined #openstack-dev06:27
*** tovin07 has quit IRC06:27
*** tovin07 has joined #openstack-dev06:28
*** salv-orlando has joined #openstack-dev06:29
*** svinota has joined #openstack-dev06:30
*** fragatina has joined #openstack-dev06:30
*** fragatina has quit IRC06:32
*** fragatina has joined #openstack-dev06:32
*** eroux has quit IRC06:35
*** SumitNaiksatam has joined #openstack-dev06:41
*** adriant has quit IRC06:42
*** treiz has quit IRC06:47
*** limao has quit IRC06:50
*** treiz has joined #openstack-dev06:51
*** diablo_rojo has quit IRC06:51
*** yuntongjin has quit IRC06:51
*** yuntongjin has joined #openstack-dev06:52
*** AnilV_ has joined #openstack-dev06:52
*** salv-orl_ has joined #openstack-dev06:52
*** salv-orlando has quit IRC06:55
*** thorst has joined #openstack-dev06:57
*** Poornima_K has joined #openstack-dev07:01
*** thorst has quit IRC07:01
*** salv-orl_ has quit IRC07:03
*** diablo_rojo has joined #openstack-dev07:04
*** k4n0 has joined #openstack-dev07:04
openstackgerritAnusha Ramineni proposed openstack/governance master: Add congress-dashboard to governance  https://review.openstack.org/44095207:05
*** charcol has quit IRC07:05
*** e0ne has joined #openstack-dev07:07
*** priteau has joined #openstack-dev07:12
*** tesseract has joined #openstack-dev07:12
*** limao has joined #openstack-dev07:14
*** tuanluong has quit IRC07:15
*** david-lyle has quit IRC07:16
*** jrist has quit IRC07:16
*** david-lyle has joined #openstack-dev07:16
*** priteau has quit IRC07:17
*** jrist has joined #openstack-dev07:17
*** gpj89 has joined #openstack-dev07:18
*** ShaneDavidson has joined #openstack-dev07:18
*** limao_ has joined #openstack-dev07:18
*** limao has quit IRC07:19
*** karthiks is now known as karthiks|lunch07:21
*** yuntongjin has quit IRC07:21
*** tesseract-RH has joined #openstack-dev07:29
*** tesseract has quit IRC07:30
*** athomas has joined #openstack-dev07:31
*** takamatsu has joined #openstack-dev07:35
*** vnogin has joined #openstack-dev07:36
*** diablo_rojo has quit IRC07:40
*** tovin07_ has joined #openstack-dev07:41
*** pcaruana has joined #openstack-dev07:41
*** vnogin has quit IRC07:41
*** rcernin has joined #openstack-dev07:44
*** ShaneDavidson has quit IRC07:48
*** saibarspeis has joined #openstack-dev07:54
*** bobmel has joined #openstack-dev07:54
*** gpj89 has quit IRC07:55
*** gpj89 has joined #openstack-dev07:55
*** matrohon has joined #openstack-dev07:56
*** thorst has joined #openstack-dev07:58
*** salv-orlando has joined #openstack-dev07:59
*** bobmel has quit IRC07:59
*** lpetrut has joined #openstack-dev07:59
*** tovin07_ has quit IRC07:59
*** karthiks|lunch is now known as karthiks07:59
*** hseipp has joined #openstack-dev08:00
*** SumitNaiksatam has left #openstack-dev08:02
*** thorst has quit IRC08:02
*** gpj89 has quit IRC08:04
*** lpetrut has quit IRC08:05
*** rarcea has joined #openstack-dev08:06
*** markvoelker has joined #openstack-dev08:08
*** markvoelker has quit IRC08:14
*** yamahata has quit IRC08:14
*** retr0h has quit IRC08:14
*** csmart has quit IRC08:14
*** eezhova has joined #openstack-dev08:17
*** matrohon_ has joined #openstack-dev08:17
*** matrohon_ has quit IRC08:18
*** diablo_rojo has joined #openstack-dev08:18
*** retr0h has joined #openstack-dev08:24
*** bauzas is now known as bauwser08:29
*** vnogin has joined #openstack-dev08:35
*** jdurgin has quit IRC08:43
*** ygbo has joined #openstack-dev08:44
*** snica_away is now known as snica08:48
*** k4n0 has quit IRC08:51
*** shardy has joined #openstack-dev08:51
*** bobmel has joined #openstack-dev08:53
*** jpich has joined #openstack-dev08:54
*** thorst has joined #openstack-dev08:58
*** zzzeek has quit IRC09:00
*** zzzeek has joined #openstack-dev09:00
*** radhikam has quit IRC09:02
*** egallen has joined #openstack-dev09:03
*** priteau has joined #openstack-dev09:06
*** diablo_rojo has quit IRC09:06
*** gszasz has joined #openstack-dev09:06
*** k4n0 has joined #openstack-dev09:08
*** thorst has quit IRC09:09
*** vsaienk0 has joined #openstack-dev09:09
*** e0ne has quit IRC09:10
*** matrohon has quit IRC09:10
*** eezhova has quit IRC09:10
*** sridhargaddam has quit IRC09:11
*** david-lyle has quit IRC09:13
*** david-lyle has joined #openstack-dev09:13
*** jrist has quit IRC09:14
*** jrist has joined #openstack-dev09:14
*** csmart has joined #openstack-dev09:19
*** gszasz has quit IRC09:20
*** jdurgin has joined #openstack-dev09:20
*** paramite has joined #openstack-dev09:24
*** gfidente has joined #openstack-dev09:26
*** sridhargaddam has joined #openstack-dev09:26
*** owalsh has joined #openstack-dev09:28
*** akrivoka has joined #openstack-dev09:29
*** sridhargaddam has quit IRC09:29
*** sridharg has joined #openstack-dev09:29
*** david-lyle_ has joined #openstack-dev09:30
*** owalsh-afk has quit IRC09:31
*** david-lyle has quit IRC09:31
*** mhickey has joined #openstack-dev09:36
*** yanyanhu has quit IRC09:39
*** lucas-afk is now known as lucasagomes09:47
*** eezhova has joined #openstack-dev09:48
*** dsariel has quit IRC09:51
*** yamamoto_ has quit IRC09:54
*** yamamoto has joined #openstack-dev09:55
*** yamamoto has quit IRC10:00
*** MattMan has quit IRC10:01
*** MattMan has joined #openstack-dev10:01
*** dsariel has joined #openstack-dev10:04
*** nijaba has quit IRC10:05
*** nijaba has joined #openstack-dev10:06
*** nijaba has quit IRC10:06
*** nijaba has joined #openstack-dev10:06
*** thorst has joined #openstack-dev10:06
*** owalsh has quit IRC10:07
*** owalsh has joined #openstack-dev10:07
*** e0ne has joined #openstack-dev10:08
*** k4n0 has quit IRC10:08
*** thorst has quit IRC10:10
*** markvoelker has joined #openstack-dev10:10
*** vnogin has quit IRC10:10
*** electrofelix has joined #openstack-dev10:11
*** tovin07 has quit IRC10:12
*** ShaneDavidson has joined #openstack-dev10:13
*** markvoelker has quit IRC10:15
*** ddellav_ has quit IRC10:18
*** k4n0 has joined #openstack-dev10:20
*** karthiks has quit IRC10:23
*** matrohon has joined #openstack-dev10:23
openstackgerritMerged openstack/governance master: Add os-traits project under nova governance  https://review.openstack.org/43716710:23
openstackgerritMerged openstack/governance master: Add planning artifacts for goal-python35  https://review.openstack.org/43734910:24
openstackgerritMerged openstack/governance master: Add planning artifact for goal-deploy-api-in-wsgi  https://review.openstack.org/43735410:25
openstackgerritThierry Carrez proposed openstack/governance master: Add congress-dashboard to governance  https://review.openstack.org/44095210:27
*** lpetrut has joined #openstack-dev10:32
*** gongysh has joined #openstack-dev10:34
*** amotoki_ has quit IRC10:37
*** gongysh has quit IRC10:37
*** saibarspeis has quit IRC10:41
*** halves has joined #openstack-dev10:47
*** ShaneDavidson has quit IRC10:47
*** dalgaaf has quit IRC10:47
*** baoli has joined #openstack-dev10:48
*** dalgaaf has joined #openstack-dev10:49
*** vnogin has joined #openstack-dev10:52
*** baoli has quit IRC10:53
*** limao_ has quit IRC10:54
*** limao has joined #openstack-dev10:55
*** vnogin has quit IRC10:56
*** yamamoto has joined #openstack-dev10:57
*** limao has quit IRC10:59
*** vnogin has joined #openstack-dev11:00
*** dtantsur|afk is now known as dtantsur11:00
*** yamamoto has quit IRC11:01
*** john-davidge has joined #openstack-dev11:02
*** nicolasbock has joined #openstack-dev11:06
*** yamamoto has joined #openstack-dev11:12
*** aasthad has quit IRC11:12
*** yamamoto has quit IRC11:16
*** yamamoto has joined #openstack-dev11:17
*** yamamoto has quit IRC11:17
*** athomas has quit IRC11:17
*** bogdando has joined #openstack-dev11:17
*** yamamoto has joined #openstack-dev11:17
*** zz_dimtruck is now known as dimtruck11:21
*** dizquierdo has joined #openstack-dev11:22
*** yamamoto has quit IRC11:22
*** athomas has joined #openstack-dev11:24
*** matrohon has quit IRC11:25
*** nmathew has quit IRC11:31
*** luizbag has joined #openstack-dev11:36
*** yamamoto has joined #openstack-dev11:36
*** sree has quit IRC11:36
*** gszasz has joined #openstack-dev11:37
*** jkilpatr has quit IRC11:38
*** snica is now known as snica_away11:39
*** yamamoto has quit IRC11:39
*** luizbag has quit IRC11:42
*** sdague has joined #openstack-dev11:48
*** aysyd has joined #openstack-dev11:50
*** nplanel has quit IRC11:53
*** yamamoto has joined #openstack-dev11:58
*** jkilpatr has joined #openstack-dev11:59
*** rfolco has joined #openstack-dev12:01
*** ansmith has joined #openstack-dev12:04
*** jkilpatr has quit IRC12:07
*** thorst has joined #openstack-dev12:07
*** matrohon has joined #openstack-dev12:08
*** amotoki has joined #openstack-dev12:08
*** markvoelker has joined #openstack-dev12:11
*** thorst has quit IRC12:11
*** cdent has joined #openstack-dev12:14
*** luizbag has joined #openstack-dev12:15
*** markvoelker has quit IRC12:16
*** luizbag has quit IRC12:17
*** luizbag has joined #openstack-dev12:17
*** jkilpatr has joined #openstack-dev12:21
*** saibarspeis has joined #openstack-dev12:21
*** shardy is now known as shardy_lunch12:25
*** snica_away is now known as snica12:27
*** matrohon has quit IRC12:28
*** salv-orlando has quit IRC12:28
*** thorst has joined #openstack-dev12:44
*** k4n0 has quit IRC12:46
*** steveg_afk has quit IRC12:49
*** yuntongjin has joined #openstack-dev12:51
*** yamamoto has quit IRC12:52
*** pabelanger has quit IRC12:55
*** kashyap has quit IRC12:57
*** pabelanger has joined #openstack-dev12:57
*** kashyap has joined #openstack-dev12:57
*** yuntongjin has quit IRC12:59
*** yuntongjin has joined #openstack-dev13:01
*** morazi has joined #openstack-dev13:01
johnthetubaguysdague: just reading though, I like the inclusion of delete orphaned resources13:04
*** owalsh is now known as owalsh-lunch13:04
sdaguejohnthetubaguy: once you catch up on the high level limits proposed spec - https://review.openstack.org/#/c/440815/ - let me know, because in intersection of your specs and the keystone ones, I'm starting to see things I think we need to take off the table to move forward13:04
*** AnilV4 has quit IRC13:05
*** sdake has joined #openstack-dev13:07
*** psachin has quit IRC13:07
*** donghao has joined #openstack-dev13:08
*** denisra has joined #openstack-dev13:10
*** denisra has quit IRC13:11
*** nplanel has joined #openstack-dev13:11
*** ansmith has quit IRC13:12
*** bks has quit IRC13:12
openstackgerritTelles Mota Vidal Nóbrega proposed openstack/governance master: Sahara Artifacts to deploy through WSGI  https://review.openstack.org/44111713:13
*** darvon has quit IRC13:13
sdaguejohnthetubaguy: ok, how is the reading going, I've got a fresh cup of coffee, and wanted to discuss a few things I think we have to do to ever move this forward13:15
*** darvon has joined #openstack-dev13:16
johnthetubaguysdague: almost there, just looking at your proposed stages13:16
johnthetubaguysdague: cool, I am done13:21
*** alexismonville has joined #openstack-dev13:21
johnthetubaguysdague: I added a few comments, but nothing that changes things much13:21
sdagueok, cool. Let me just dump some thoughts here which aren't in that spec.13:23
*** markvoelker has joined #openstack-dev13:23
sdaguestuff that we might need to just take off the table entirely, so that there is a path forward13:23
johnthetubaguysure13:23
sdague1) I think we need to dump user quota as a concept, only Nova seems to really implement this, and it's done largely to create 2 tier hierarchy with projects13:24
johnthetubaguysdague: I think that was from the per user policy folks13:24
sdagueright13:24
johnthetubaguysdague: so, +113:24
sdaguehierarchy should solve that13:25
johnthetubaguyyeah13:25
*** dtantsur is now known as dtantsur|bbl13:25
sdague2) I think we need to take overbooking off the table for the next 2 cycles (though assume it might come back later)13:25
*** ansmith has joined #openstack-dev13:25
*** salv-orlando has joined #openstack-dev13:25
sdaguebecause what I have found is every discussion in this space turns into everyone thinking about how the math works in overbooking, and missing all the first steps13:26
johnthetubaguyI was thinking of talking hierarchy off the table, but I think taking all kinds of overbooking off the take is easier13:26
sdagueand it's an interesting math problem, but it's so premature13:26
*** kylek3h has quit IRC13:26
johnthetubaguyso it depends what you think the no overbooking case is, I think I subscribe to the cinder model, which is different to what most folks were assuming13:27
sdague3) quota classes need to be taken off the table. All they are is a macro for setting a bunch of limits at once13:27
johnthetubaguyyeah, will need that, but its a keystone problem now, and probably should match thier implied roles stuff anyways13:27
*** cdent has quit IRC13:27
sdagueand quota classes get to be inside baseball pretty quick for folks that haven't thought about it13:27
johnthetubaguyyeah, its complexity we can punt on13:28
sdagueI honestly think that with keystone primatives, you just implement that in ansible playbooks pretty easily13:28
johnthetubaguyit doesn't change the service <-> keystone interface I have in my head anyways13:28
sdagueright13:28
johnthetubaguyyeah, most folks have scripted that on top right now13:28
johnthetubaguy(FWIW, that includes the people who added that code, AFAIK)13:29
*** heroux has joined #openstack-dev13:29
sdaguealso, while you gave a o_O to the common library having both the limits checks and quota checks in it, I would argue that this thing is really important to have the logic of sane limits match the logic of quota checking in that limits mode13:30
dstaneksdague: this is the first i've heard of quota classes13:30
sdagueand while keystone will be the only consumer of limits interfaces, if they aren't all tested together, it's going to be buggy as well13:30
sdagueas hell13:30
johnthetubaguysdague: so what I imagine the common lib to do I noted in a comment in your spec just now13:31
johnthetubaguyI think its not far away from what you where thinking, if I read your spec correctly13:31
dstanekthe "assume it might come back later" is important to me. i was just advocating this yesterday. don't implement, but take into account during design so we don't end up in another corner13:32
johnthetubaguydstanek: its a crazy nova bit of basically dead code, but the idea is interesting, longer term, best to ignore it for now13:32
sdagueyeh, honestly though, I would make this thing something that knows nothing about context, and litterally is just a prologish "given this structure and this delta, are we good"13:32
sdaguehave as few requirements as possible, so it doesn't need branches, and should be safe to upgrade on all your projects whenever this is a bug fix13:33
sdaguebecause that bug fix might be needed on both the setting side as well as the enforce side13:33
johnthetubaguysdague: yeah, we can do that glue on the Nova side like we do for policy, thats probably better13:33
sdagueyeh, or some other oslo lib that has convenience functions13:33
johnthetubaguysdague: the bit I was meaning really is the register callback for the count functions13:33
*** dizquierdo has quit IRC13:34
sdaguebut the actual core math feels like if we don't keep it pretty abstract, again things are going to get too complicated to manage13:34
johnthetubaguysdague: like call this method, with the scope defined, to get answers for vcpu, ram and disk13:34
sdaguejohnthetubaguy: yeh, sure13:34
sdagueI think that's kind of why that's going to take a whole cycle to figure out13:35
johnthetubaguyso the Nova code is almost written like that already, it needs to be different, but yeah, something a bit like that13:35
johnthetubaguysdague: +113:35
johnthetubaguythis is very much something we should take to the forum to ask operators (and users) if it looks correct13:36
sdagueyeh13:36
sdaguewell, the important thing though is moving the sets into keystone can move forward even if we don't have all the enforcement models figured out13:36
johnthetubaguydeprecation wise, maybe we deprecate user quotas this cycle, although thats a bit rude if we haven't replace it yet, but good for early feedback13:36
sdagueit's good signaling13:37
johnthetubaguyyeah13:37
johnthetubaguyI am all for good signaling13:37
sdaguethey won't go away until you can have hierarchy13:37
johnthetubaguyyeah, it feels a bit like nova-network (well hopfully not too like that)13:37
*** spartacloud has joined #openstack-dev13:38
johnthetubaguythis is crazy, please don't use this13:38
johnthetubaguymessage13:38
sdagueyep13:38
*** shardy_lunch is now known as shardy13:39
sdaguejohnthetubaguy: ok, in looking at the comments13:40
sdagueI don't actually think that coherent limits in keystone is just UX, I think that if we can't trust the limit hierarchy to be clean, the enforcement code gets an order of magnitude more complicated13:40
*** aspiers has quit IRC13:41
sdagueI'm also really tempted to build out an entirely separate document with blockdiag of all the limit possibilities in the hiearchy I see so far13:42
johnthetubaguyso there is a case I was thinking about13:43
sdagueI don't want it to distract from this, but I think we are often reusing words that mean different things13:43
*** cwolferh has joined #openstack-dev13:43
johnthetubaguyyeah, I think we need to describe what we mean by no overbooking13:43
dstaneksdague: i would like that. the rules for validating limits could be super simple or very complicated.13:43
johnthetubaguyin my head...13:43
sdagueI also am not sure how the cinder model works here, because don't they decrement parent limits when they allocate child quota13:43
johnthetubaguyits basically a subtree is given exclusive quota13:43
*** achampion has quit IRC13:44
johnthetubaguysdague: they have a reservation thing, which tells you what is left for the parent13:44
johnthetubaguysdague: at least I thoughts that what they intended13:44
dstaneki'm also curious to know if you guys have thought about the CRUD API for limits - lots of different ways to do it and i've not starting thinking about the trade offs yet13:44
johnthetubaguydstanek: something tells me we should do the service <-> keystone interface first, I am not sure why13:44
sdaguedstanek: honestly, I haven't really yet, because I wanted to get concept buy in, and I'd be happy for keystone folks to weigh in on what they think it should be13:45
sdaguejohnthetubaguy: ??13:45
ZZelle_zzzeek, hi13:45
zzzeekZZelle_: hey13:45
*** edleafe is now known as figleaf13:46
dstanekjohnthetubaguy: i don't see that one being too difficult. the hardest part is figuring out what parts of the hierarchy to return based on how enforcement will work13:46
sdaguejohnthetubaguy: I don't understand how you do this without doing the admin setting of the information first13:46
johnthetubaguysdague: the thing in my head? or something else?13:46
dstaneksdague: happy to weigh in :-)13:46
johnthetubaguysdague: oh, I see what you mean13:47
johnthetubaguyI guess in my head I see how we do the quota check13:47
johnthetubaguyif we can agree that info, and the logical space13:47
ZZelle_zzzeek, when you define a relationship, sqlalchemy is able to expose a 1-n relationship into a list13:47
johnthetubaguywe then work out how admins have to set that up13:47
sdaguejohnthetubaguy: right, so I think you have to go the other way, do the admin putting information into the system13:48
*** mhayden has quit IRC13:48
sdaguethen you have the constraints on what the data can look like, and you pull it onto the other side and do enforce on it13:48
johnthetubaguysdague: you are right, maybe I did that in my head without realising actually13:48
ZZelle_zzzeek, is it possible to have the same behavior without defining a relationship?13:48
zzzeekZZelle_: a relationship has lots of behaviors.  are you referring to an instance level, "obj.things" is a list of related objects?13:49
sdagueI think if you don't start from how you create the limit structure, you can get into a "well, if I had this data" that is nice to operate on, but completely impossible to describe the operator steps to create13:49
ZZelle_zzzeek, exactly ... typically defined with a backref13:49
*** vladikr has joined #openstack-dev13:49
zzzeekZZelle_: taking your qeustion literally, you would say, "obj.things = session.query(RelatedThing).with_parent(obj).all()"13:49
*** mhayden has joined #openstack-dev13:50
sdaguedstanek / johnthetubaguy well my goal right now is to figure out how we get agreement on the broad strokes, then I think we can dive into the keystone setting interfaces13:50
zzzeekZZelle_: if you'd like that to be "auto", then you'd use @property to run that code internally13:50
johnthetubaguyyeah13:50
johnthetubaguysdague: so that bit about definding what we mean by no overbook, I think that was actually me thinking about this operator API, my bad13:50
zzzeekZZelle_: http://docs.sqlalchemy.org/en/latest/orm/join_conditions.html#building-query-enabled-properties13:51
sdagueok, so how about in anther document (maybe still in keystone?) I put together some of the quota trees and what may or may not happen there. I'll use blockdiag so hopefully the pictures become a little clearer. I definitely get lost on the ascii art13:51
ZZelle_ zzzeek, great so it allows to remove the dirty formatting in get_all_firewall_routers in https://review.openstack.org/#/c/440976/1/neutron_fwaas/db/firewall/firewall_router_insertion_db.py13:52
johnthetubaguysdague: I keep thinking of operators defining a limit on a sub tree, then the parent of the subtree handing out quota to their children13:52
sdaguejohnthetubaguy: that assumes that you can't allocate a resource in the parent13:52
*** gabor_antal_km has joined #openstack-dev13:53
*** yamamoto has joined #openstack-dev13:53
sdaguehonestly, that's a scenario that I'll list, but I'm going to call it "Make Chet Sad" quotas13:53
zzzeekZZelle_: im not seeing the connection w/ whatever that code is doing but if you say so :)13:53
johnthetubaguysdague: no, no I assume you can allocate resources there, thats fine13:53
sdaguejohnthetubaguy: ok, but then you have to always go up the hierachy to check quota13:54
sdaguelet me draw things, you can yell at me after pictures13:54
sdagueplus, need breakfast13:54
dstaneksdague: the other doc sounds great13:54
johnthetubaguysdague: I think its easier than that though13:54
johnthetubaguysdague: consider A with children B and C13:55
sdaguejohnthetubaguy: if you don't have pictures, I'm going to ignore you :)13:55
sdagueother doc, other doc13:55
johnthetubaguysdague: yeah, I think the pictures are in my spec for this13:55
johnthetubaguybut I over complicated it, obviously13:55
dstanekjohnthetubaguy: my thought is for your A -> B/C example that keystone would have to return limits for all three13:57
*** cdent has joined #openstack-dev13:57
*** spartacloud has quit IRC13:57
*** Poornima_K has quit IRC13:57
johnthetubaguyso there is one limit, and you always have to count resources for A, B and C, if you create anything in A, B or C13:57
dstanekin the general case it would have to return limits (if any) for the project and all siblings - plus the nearest parent with a limit as long as it doesn't cross a reseller boundary13:57
johnthetubaguymaybe thats the same thing13:57
*** ayogi has quit IRC13:58
dstanektechnically you don't need to siblings to make the go/no go decision, but i was thinking in terms of better messaging and/or the ability to over promise13:59
dstanekother systems i've used have had ranking and related features.14:00
*** radhikam has joined #openstack-dev14:00
*** gordc has joined #openstack-dev14:00
dstanekso as a first pass we probably won't need siblings14:00
*** yamamoto has quit IRC14:00
*** sdake_ has joined #openstack-dev14:01
*** sdake has quit IRC14:03
*** bogdando has quit IRC14:03
*** owalsh-lunch is now known as owalsh14:07
ZZelle_zzzeek, thx14:07
*** radhikam has quit IRC14:07
*** dtantsur|bbl is now known as dtantsur14:09
*** mriedem has joined #openstack-dev14:09
*** kylek3h has joined #openstack-dev14:09
*** sree has joined #openstack-dev14:11
*** krtaylor has quit IRC14:12
*** krtaylor has joined #openstack-dev14:13
*** jed56_ has joined #openstack-dev14:15
*** sree has quit IRC14:16
*** kgiusti has joined #openstack-dev14:17
*** e0ne has quit IRC14:17
johnthetubaguysdague: dstanek: tried to draw out my idea here: https://github.com/JohnGarbutt/quota_ideas/blob/master/idea.py14:18
johnthetubaguynaturally its more complicated than it seemed in my head14:18
dstanekjohnthetubaguy: not sure i understand the datastructure used there14:21
dstanekjohnthetubaguy: also how does endpoint play a part in this?14:21
johnthetubaguydstanek: this is per endpoint, so I am thinking Nova side, we just get the limits that apply to that Nova endpoint14:21
*** ihrachys has joined #openstack-dev14:24
openstackgerritLance Bragstad proposed openstack/governance master: Update keystone goals for running in apache  https://review.openstack.org/44084014:24
*** pcaruana has quit IRC14:24
johnthetubaguydstanek: the idea is you have to count the resources in a particular scope, when checking the limit14:24
*** baoli has joined #openstack-dev14:26
*** jcoufal has joined #openstack-dev14:27
*** eharney has joined #openstack-dev14:28
*** lucasagomes is now known as lucas-hungry14:29
*** yamahata has joined #openstack-dev14:33
*** dansmith is now known as superdan14:34
*** steveg_afk has joined #openstack-dev14:34
dstanekjohnthetubaguy: so give 3 different limts set by nova i'm assuming that we'll always want to return all of them for a project and not just one in particular. is that true?14:35
*** galstrom_zzz is now known as galstrom14:36
johnthetubaguydstanek: I think we already return all, each one has a default14:36
johnthetubaguydstanek: I have more ideas cooking, will push in a sec14:36
dstanekand each endpoint would have values set for all defined limits?14:36
*** dtardivel has joined #openstack-dev14:36
*** AnilV4 has joined #openstack-dev14:37
dstanekso if you add a new region you would have to supply limits at that point14:37
*** e0ne has joined #openstack-dev14:39
*** faizy has joined #openstack-dev14:42
*** e0ne has quit IRC14:42
*** gabor_antal_km is now known as gabor_antal14:43
dstanekor would you have limits at the service level (nova says 10 vCPU per project) and have endpoints override (this endpoint only allows 8 since it have less hardware) and then override at the project level14:44
*** sdake_ has quit IRC14:44
*** e0ne has joined #openstack-dev14:44
dstaneki'm not familiar with the existing usecases14:44
*** sdake has joined #openstack-dev14:44
*** saibarspeis has quit IRC14:45
*** halprin has joined #openstack-dev14:45
openstackgerritFelipe Reyes proposed openstack/governance master: Add ceph-proxy charm  https://review.openstack.org/44115514:46
*** owalsh has quit IRC14:47
*** achampion has joined #openstack-dev14:48
*** yuntongjin has quit IRC14:50
*** yamahata has quit IRC14:51
*** rderose has joined #openstack-dev14:52
*** owalsh has joined #openstack-dev14:57
*** dimtruck is now known as zz_dimtruck14:58
johnthetubaguydstanek: today its always per nova-api service that you set limits14:59
johnthetubaguydstanek: thats a fine starting point really14:59
dstanekso nova limits with project overrides?15:00
*** slashme has joined #openstack-dev15:01
*** dizquierdo has joined #openstack-dev15:01
johnthetubaguydstanek: does this help? https://github.com/JohnGarbutt/quota_ideas/blob/master/idea.py15:05
*** paramite has quit IRC15:07
*** jdandrea has joined #openstack-dev15:08
*** rcrit has quit IRC15:08
johnthetubaguydstanek: I am adding more comments, its a bit opaque15:10
*** lucas-hungry is now known as lucasagomes15:12
*** salv-orlando has quit IRC15:12
*** ociuhandu has joined #openstack-dev15:12
*** aspiers has joined #openstack-dev15:14
*** jcoufal_ has joined #openstack-dev15:15
*** hongbin has joined #openstack-dev15:16
*** lucasxu has joined #openstack-dev15:17
*** xemdetia has joined #openstack-dev15:17
*** jcoufal has quit IRC15:18
*** kriskend has joined #openstack-dev15:19
*** diablo_rojo has joined #openstack-dev15:19
dstanekjamesmcarthur: here is what i was thinking https://gist.github.com/dstanek/a8a343a3ab5ad4ad0862e3e1be33217315:20
*** rcrit has joined #openstack-dev15:25
johnthetubaguydstanek: sdague: this script attempts to print out the idea in my brain: https://github.com/JohnGarbutt/quota_ideas/blob/master/idea.py15:25
johnthetubaguyits always twice as complicated as it first seems15:26
sdaguejohnthetubaguy: honestly, I have a hard time not stack overflowing with these things in code15:26
johnthetubaguysdague: if you run the script it gives text, let me get that somewhere15:27
*** ociuhandu has quit IRC15:27
johnthetubaguysdague: dstanek: https://gist.github.com/JohnGarbutt/677154f6cad51f5f2a948b3aefa0621f15:28
johnthetubaguyhang out, thats un readable15:28
johnthetubaguyone sec15:28
*** vnogin has quit IRC15:29
*** mriedem1 has joined #openstack-dev15:30
johnthetubaguysdague: not sure if this makes any sense, but the idea is a flow where operator sets default quota, then sets overrides, and nova does boot instance check: https://gist.github.com/JohnGarbutt/677154f6cad51f5f2a948b3aefa0621f15:31
*** mriedem has quit IRC15:31
*** achampion has quit IRC15:33
*** jaypipes has joined #openstack-dev15:34
*** bnemec is now known as beekneemech15:35
*** marst has quit IRC15:38
*** Leo_ has joined #openstack-dev15:39
*** zz_dimtruck is now known as dimtruck15:39
*** vills_ has joined #openstack-dev15:40
*** kbringard has joined #openstack-dev15:41
*** mriedem1 is now known as mriedem15:42
*** kbringard has quit IRC15:44
*** kbringard has joined #openstack-dev15:44
*** sridharg has quit IRC15:45
*** eharney has quit IRC15:48
*** marst has joined #openstack-dev15:48
*** eezhova has quit IRC15:49
*** salv-orlando has joined #openstack-dev15:52
*** dhellmann has quit IRC15:54
*** dhellmann has joined #openstack-dev15:54
*** ksobkowiak has joined #openstack-dev15:54
*** jaypipes is now known as leakypipes15:55
*** xarses_ has joined #openstack-dev15:55
*** ihrachys has quit IRC15:56
*** ayogi has joined #openstack-dev15:57
*** andreww has joined #openstack-dev15:57
*** iyamahat has joined #openstack-dev15:59
*** xarses_ has quit IRC15:59
*** AnilV4 has quit IRC16:00
*** xarses_ has joined #openstack-dev16:01
*** lucasxu has quit IRC16:01
*** andreww has quit IRC16:01
*** rcernin has quit IRC16:02
*** eezhova has joined #openstack-dev16:03
*** radhikam has joined #openstack-dev16:05
*** eharney has joined #openstack-dev16:05
*** DennyZhang has joined #openstack-dev16:06
*** ltomasbo is now known as ltomasbo|away16:08
openstackgerritSean McGinnis proposed openstack/governance master: Update email for Cinder PTL  https://review.openstack.org/44120016:11
*** lucasxu has joined #openstack-dev16:11
*** dizquierdo has quit IRC16:12
dimssmcginnis : i was just thinking that folks should have non-work alternate email address(es) :)16:12
*** eezhova has quit IRC16:12
*** eezhova has joined #openstack-dev16:12
*** eezhova has quit IRC16:13
*** tesseract-RH has quit IRC16:14
smcginnisdims: ;)16:15
*** mhickey has quit IRC16:16
sdaguejohnthetubaguy: https://review.openstack.org/441203 is starting to do the block diag thing16:16
*** eroux has joined #openstack-dev16:21
*** ihrachys has joined #openstack-dev16:24
*** nplanel has quit IRC16:25
*** iyamahat has quit IRC16:25
*** matrohon has joined #openstack-dev16:25
*** eroux has quit IRC16:26
*** jkilpatr_ has joined #openstack-dev16:28
*** ansmith has quit IRC16:30
*** jkilpatr has quit IRC16:31
*** cdub has joined #openstack-dev16:34
*** e0ne has quit IRC16:35
*** aasthad has joined #openstack-dev16:37
*** e0ne has joined #openstack-dev16:38
sdaguejohnthetubaguy: it makes a ton more sense once you do the tox on it, once there is a draft build, I'll point you at it16:39
*** e0ne has quit IRC16:41
*** ansmith has joined #openstack-dev16:41
*** rarcea has quit IRC16:42
*** wootehfoot has joined #openstack-dev16:45
*** DennyZhang has quit IRC16:46
*** jathan has joined #openstack-dev16:48
*** raunak has joined #openstack-dev16:51
*** eezhova has joined #openstack-dev16:51
*** owalsh has quit IRC16:53
*** iyamahat has joined #openstack-dev16:57
*** kjw3 has quit IRC16:58
*** radhikam has joined #openstack-dev16:58
*** leakypipes has quit IRC17:00
*** owalsh has joined #openstack-dev17:00
*** owalsh is now known as owalsh-afk17:00
*** mriedem1 has joined #openstack-dev17:01
*** aarefiev is now known as aarefiev_afk17:04
*** mriedem has quit IRC17:04
sdaguejohnthetubaguy: http://docs-draft.openstack.org/03/441203/2/check/gate-keystone-specs-docs-ubuntu-xenial/f4c0f1f//doc/build/html/specs/keystone/backlog/hierarchical-quota-scenarios.html17:08
*** morazi_ has joined #openstack-dev17:08
*** lucasagomes is now known as lucas-afk17:08
*** eantyshev has joined #openstack-dev17:10
dstaneksdague: i did a real quick brain dump earlier about what i first thought when quotes came up at PTG https://gist.github.com/dstanek/a8a343a3ab5ad4ad0862e3e1be33217317:10
*** morazi has quit IRC17:11
sdaguedstanek: cool17:12
*** _cjones_ has joined #openstack-dev17:12
*** faizy has quit IRC17:13
*** mriedem1 is now known as mriedem17:13
*** vhosakot has joined #openstack-dev17:15
*** morazi_ has quit IRC17:16
*** annegentle has joined #openstack-dev17:17
johnthetubaguysdague: sweet17:19
*** kjw3 has joined #openstack-dev17:20
johnthetubaguydstanek: does this one make any sense: https://gist.github.com/JohnGarbutt/677154f6cad51f5f2a948b3aefa0621f17:20
johnthetubaguydstanek: basically I flattened the checks, I think17:20
*** akrivoka has quit IRC17:21
*** cdent has quit IRC17:22
*** rabel_b1 has quit IRC17:23
*** jpich has quit IRC17:24
*** eezhova has quit IRC17:25
*** matrohon has quit IRC17:26
sdaguejohnthetubaguy: I'm having a hard time understanding count scope17:27
dstanekjohnthetubaguy: don't you need to keep the hierarchy?17:27
johnthetubaguydstanek: I don't think we need it, when you flatten it17:28
johnthetubaguysdague: ah, yeah17:28
dstaneksdague: i think that's just the list of things that have the same limits17:28
johnthetubaguyno...17:28
johnthetubaguyits different17:28
dstanekok, then i don't get it either :-)17:28
johnthetubaguyso you need to count the resources17:28
johnthetubaguythe resources are assocaited with a project_id17:28
*** ZZelle has joined #openstack-dev17:29
johnthetubaguyso when counting resources I pass in a list of project_ids17:29
*** morazi_ has joined #openstack-dev17:29
johnthetubaguyso I filter the list of all resources in the system by the given list of project_ids17:29
johnthetubaguyto do the count17:29
johnthetubaguyso that limit applies to the sum of all resource usage, across the list of "scopes"17:29
johnthetubaguysdague: now I forgot removing the user, scope can get flattened to just project_ids, oops17:30
johnthetubaguydoes that make more or less sense now?17:30
johnthetubaguyprobably less17:30
dstanekwhat project ids are you passing it?17:31
sdaguejohnthetubaguy: also, I do not understand at all why count scope would be different between resources17:31
sdaguejohnthetubaguy: it's not clicking for me honestly, this is why I went to the block diag model.17:31
johnthetubaguysdague: that bit was a bit odd, it just came out of the use case I chose, which is probably bogus17:32
*** gpj89 has joined #openstack-dev17:32
johnthetubaguysdague: I think where you have 0, I was having -117:32
dstaneki was thinking that when a services is asked for a resource in a given project that it would just ask keystone for limits related to that project17:32
sdaguejohnthetubaguy: I don't understand how -1 is consistent17:33
johnthetubaguysdague: but thats too much along the no-over commit spectrum I think17:33
*** slaweq_ has quit IRC17:33
sdaguebecause it means you allow overbooking17:33
johnthetubaguysdague: so lets look at your diagram for A, with B, C and D17:33
sdagueyep17:33
johnthetubaguylets say 10, and all -117:34
sdagueok17:34
johnthetubaguyfor me that gives us a limit check for 10, but we always have to count all resources in A, B, C and D17:34
johnthetubaguyso a single check, no matter if you create something in A, B, C or D17:34
sdaguethat means to compute quota violations you have to count all siblings at every level17:34
johnthetubaguysdague: yes17:34
*** ayogi has quit IRC17:35
*** hseipp has quit IRC17:35
johnthetubaguythats what my scope thing was trying to represent17:35
*** slaweq_ has joined #openstack-dev17:35
sdagueso, when a division is represented17:35
*** vills_ has left #openstack-dev17:35
sdagueso A has 20 children, and each child there has 20 children17:35
sdaguethen you need 400 values for every quota check17:36
*** dtantsur is now known as dtantsur|afk17:36
johnthetubaguywell, we would check resources for 400 projects, yes17:36
*** jbryce_ has joined #openstack-dev17:36
*** darrenc_ has joined #openstack-dev17:36
*** gmann_ has joined #openstack-dev17:37
*** eezhova has joined #openstack-dev17:37
*** ionelmc_ has joined #openstack-dev17:37
sdaguethat seems like it's going to send you down a really wonky path17:37
*** Dmitrii-Sh_ has joined #openstack-dev17:37
*** wolsen_ has joined #openstack-dev17:37
*** ggherdov-___ has joined #openstack-dev17:37
*** rmcadams_ has joined #openstack-dev17:37
johnthetubaguymaybe thats a computationally stupid default, but as an operator its the behaviour I think I want17:37
johnthetubaguyso, lets take this one level on, it gets a bit less wonky...17:38
*** lathiat_ has joined #openstack-dev17:38
johnthetubaguyso I have A=10, but I set B=517:38
*** ansiwen_ has joined #openstack-dev17:38
johnthetubaguythat means when I do anything in B, C or D, I have to check if we are over 517:38
johnthetubaguyif I do anything in A, I just check project A to see if there is more than 517:39
sdaguejohnthetubaguy: this is why the limits set behavior and the quotas enforce behavior need to be in the same library17:39
*** mdbooth_ has joined #openstack-dev17:39
*** djinni_ has joined #openstack-dev17:39
*** cswang_ has joined #openstack-dev17:39
sdaguejohnthetubaguy: does it?17:39
johnthetubaguysdague: it does the way I was seeing the world, which is maybe wonkey17:40
*** guitarzan has joined #openstack-dev17:40
sdaguejohnthetubaguy: so you are saying that A=10, B=10, no allocation of resources17:40
*** raorn_ has joined #openstack-dev17:40
sdaguetrying to allocate a resource in A is an overquota error?17:40
johnthetubaguyyes17:40
*** Trident has joined #openstack-dev17:40
*** athmane_ has joined #openstack-dev17:40
*** dosaboy_ has joined #openstack-dev17:41
*** jhesketh_ has joined #openstack-dev17:41
johnthetubaguythe use case here is that...17:41
johnthetubaguythe limit on A is set by the global operator17:41
johnthetubaguyA choses to delegate what it was given for its sub tree to some of its children17:41
*** greghayn1 has joined #openstack-dev17:42
sdagueand is only allowed to work with what's left?17:42
*** andreykurilin_ has joined #openstack-dev17:42
*** pwnall138 has joined #openstack-dev17:42
*** adam_g_ has joined #openstack-dev17:42
*** jmccrory_ has joined #openstack-dev17:42
johnthetubaguysdague: yes17:42
*** afazekas_ has joined #openstack-dev17:42
*** dtroyer_zz has joined #openstack-dev17:42
*** mgagne_ has joined #openstack-dev17:42
*** rods_ has joined #openstack-dev17:42
lbragstadso A can *only* give out a max of 10 things to it's children17:42
*** mdorman_ has joined #openstack-dev17:42
*** andyjone1 has joined #openstack-dev17:42
johnthetubaguythe operator only gave it 10, for it, and all its children17:42
*** hamzy_ has joined #openstack-dev17:42
johnthetubaguy(in my head)17:42
sdagueok, so assuming that A gets to carve out it's own quota and limits how do you you deal with the following situation17:42
*** robputt_ has joined #openstack-dev17:42
*** cloudkiller has joined #openstack-dev17:42
*** dimtruck_ has joined #openstack-dev17:42
*** natorious_ has joined #openstack-dev17:43
sdaguesite admin allocates A, quota 1017:43
*** vkmc- has joined #openstack-dev17:43
*** dutsmoc has joined #openstack-dev17:43
sdagueA is self admin17:43
*** zz_pwnall1337 has quit IRC17:43
*** leifz has quit IRC17:43
*** dtroyer has quit IRC17:43
*** gmann has quit IRC17:43
*** McNinja has quit IRC17:43
*** natorious has quit IRC17:43
*** dstanek has quit IRC17:43
*** darrenc has quit IRC17:43
*** wolsen has quit IRC17:43
*** comstud has quit IRC17:43
*** robputt has quit IRC17:43
*** jmccrory has quit IRC17:43
*** dimtruck has quit IRC17:43
*** mdbooth has quit IRC17:43
*** ansiwen has quit IRC17:43
*** mgagne has quit IRC17:43
*** rods has quit IRC17:43
*** Dmitrii-Sh has quit IRC17:43
*** jbryce has quit IRC17:43
*** aweeks has quit IRC17:43
*** raorn has quit IRC17:43
*** lathiat has quit IRC17:43
*** afazekas has quit IRC17:43
*** figleaf has quit IRC17:43
*** rmcadams has quit IRC17:43
*** athmane has quit IRC17:43
*** dims has quit IRC17:43
*** andreykurilin has quit IRC17:43
*** cloudnull has quit IRC17:43
*** hamzy has quit IRC17:43
*** Tridde has quit IRC17:43
*** ionelmc has quit IRC17:43
*** ggherdov-__ has quit IRC17:43
*** MikeG451 has quit IRC17:43
*** djinni has quit IRC17:43
*** mdorman has quit IRC17:43
*** nitesh has quit IRC17:43
*** cswang has quit IRC17:43
*** andyjones2001 has quit IRC17:43
*** skazi has quit IRC17:43
*** jd_ has quit IRC17:43
*** ryotagami has quit IRC17:43
*** jhesketh has quit IRC17:43
*** adam_g has quit IRC17:43
*** greghaynes has quit IRC17:43
*** vkmc has quit IRC17:43
*** kragniz has quit IRC17:43
*** pumaranikar has quit IRC17:43
*** guitarza1 has quit IRC17:43
*** dosaboy has quit IRC17:43
*** dimtruck_ is now known as dimtruck17:43
*** adam_g_ is now known as adam_g17:43
lbragstadugh17:43
*** McNinja_ has joined #openstack-dev17:43
* johnthetubaguy uh, oh17:43
*** natorious_ is now known as natorious17:43
*** cloudkiller is now known as cloudnull17:43
*** leifz- has joined #openstack-dev17:43
sdagueA spins up 5 things17:43
*** nitesh` has joined #openstack-dev17:43
*** pumaranikar has joined #openstack-dev17:43
*** leifz- is now known as leifz17:43
sdagueA creates child project B17:43
*** skazi has joined #openstack-dev17:43
*** edleafe has joined #openstack-dev17:43
*** McNinja_ is now known as McNinja17:43
sdagueA gives B limit 1017:43
*** vkmc- is now known as vkmc17:43
*** vkmc has quit IRC17:43
*** vkmc has joined #openstack-dev17:43
*** dstanek has joined #openstack-dev17:43
sdaguewhich is can do, because limit changes don't check allocations17:43
*** jbryce_ is now known as jbryce17:43
johnthetubaguyso that limit application would require --force in Nova today17:44
*** MikeG451 has joined #openstack-dev17:44
*** Dmitrii-Sh_ is now known as Dmitrii-Sh17:44
*** gmann_ is now known as gmann17:44
sdaguejohnthetubaguy: sure, but we're moving limits out17:44
*** jmccrory_ is now known as jmccrory17:44
*** wolsen_ is now known as wolsen17:44
lbragstadso that would technically allow for overbooking, right?17:44
sdagueand you definitely can't go check allocations when adjusting limits17:44
sdaguelbragstad: well, that's the question17:44
*** dims has joined #openstack-dev17:44
*** shardy has quit IRC17:44
lbragstadhmm17:44
sdaguethat's why overbooking isn't really a useful word here, because there are tons of subtle behaviors that you might call overbooking17:45
johnthetubaguyyeah, you would be overquota until the resources are delete I guess, yeah17:45
*** ryotagami has joined #openstack-dev17:45
johnthetubaguysdague : +1 for overbooking not really describing the situation properly here17:45
johnthetubaguybut for me, the delegated quota control is the use case that matters, but I could be getting the wrong end of the stick17:45
*** jd_ has joined #openstack-dev17:45
lbragstadso - this might be a crazy bad idea17:45
johnthetubaguysdague: its a good point though, thats nasty, I hadn't thought about that one17:46
sdaguethis is why I want the blockdiags of the different things, because I think that there are lots of edges here17:46
*** snica is now known as snica_away17:46
johnthetubaguysdague: in my world, I would be allowing B to build its 10, and A would be erroring with overquota, but thats maybe what we want...17:46
lbragstadbut what if we kept limit updates in keystone, but only make it something that the service can do? then we have the limit update go through the service since it can calculate and apply usage to the limit update?17:46
sdaguelet me start writing up Garbut Model17:47
*** cdent has joined #openstack-dev17:47
johnthetubaguylbragstad: but we loose the operator gain of setting it centrally17:47
lbragstadjohnthetubaguy what we we setting?17:48
johnthetubaguylbragstad: operator configuring the limits centrally I mean17:48
*** ionelmc_ is now known as ionelmc17:48
*** rmcadams_ is now known as rmcadams17:48
lbragstadjohnthetubaguy as an operator don't I want to say "I'm going to give project A a limit of 20 'things'"17:48
lbragstadif those 'things' are owned by nova - would it make sense for the operator to talk to nova about that then?17:49
sdaguelbragstad: well, the point was not to do that17:49
*** kbringard1 has joined #openstack-dev17:49
lbragstadsdague ah17:49
johnthetubaguysdague: +117:49
sdaguelbragstad: that's what we have today17:49
lbragstadsdague johnthetubaguy sorry - i must have missed those bits17:49
johnthetubaguyif you look at horizon, thats the model people want really17:49
sdagueand the net of it is we get all kinds of different modeling and behavior here17:50
johnthetubaguylbragstad: I was totally originally thinking the same as you though, until I did that certified administror thingy17:50
lbragstadright17:50
*** dtardivel has quit IRC17:50
lbragstadyeah - i totally thought that would help in figuring out the usage versus limit problem17:50
johnthetubaguythere do appear to be almost infinite ways of slicing this one17:51
*** kbringard has quit IRC17:51
johnthetubaguysdague: FWIW, I think why you are describing in the diagrams the current cinder model (at least I think thats how I understood it)17:51
dstanekjohnthetubaguy: if your example the data that is coming back from keystone?17:51
sdaguejohnthetubaguy: I thought the cinder model is kind of the garbutt model17:52
johnthetubaguydstanek: yeah, for the context with project_id keystone gives me that dict back17:52
johnthetubaguysdague: oh... its possible17:52
johnthetubaguysdague: I think they default to 0 rather than -1, at least thats how I remembered it17:52
sdaguejohnthetubaguy: maybe, I don't know17:52
johnthetubaguyanyways, its probably good to have both options down, so we can discard one of them, based on the use cases / crazy behaviours17:53
dstanekjohnthetubaguy: does that mean that keystone figures our the hierarchy values?17:53
*** dizquierdo has joined #openstack-dev17:53
*** dtroyer_zz has left #openstack-dev17:53
*** dtroyer_zz has joined #openstack-dev17:53
johnthetubaguydstanek: yeah, based on whats set, keystone figures out what limit checks the service needs17:53
johnthetubaguydstanek: I guess I skipped that step there, I included example REST calls the operator makes to keystone in the code sample17:54
dstanekso that works if you must have explicit values set for each project in the hierarchy, but not if you want roll-up17:54
*** jdandrea has quit IRC17:55
johnthetubaguydstanek: that is with the default of -1 set on all children, and the operator default project being set on all parent projects17:55
johnthetubaguydstanek: -1 means no need to count at that level17:55
*** jcoufal_ is now known as jcoufal17:55
johnthetubaguyif -1 is a leaf node...17:55
johnthetubaguyoh man, this stuff gets so messy, in every corner17:56
* lbragstad nods17:56
lbragstadi think that's why this problem has been avoided for so long :-/17:56
johnthetubaguysdague: so I had another idea, with drop hierarch, and just do flat limits in the first version17:56
johnthetubaguyheh, can't even spell it properly17:56
sdaguejohnthetubaguy: right, so it is a reason I put flatland in my document17:56
lbragstadyeah - i'd be good with doing that in the initial version17:57
sdagueok, so, I pushed another rev to ask the question there17:57
johnthetubaguysdague: ah, cool17:57
johnthetubaguylbragstad: I attempted a POC of the quota lib: https://github.com/JohnGarbutt/quota_ideas but its messy in there17:57
sdaguejohnthetubaguy: it will be easier to see if you run the block diag locally, but in the garbutt scenario at the end17:57
sdagueI actually have no idea what you'd define the world to be in the default -1 scenario17:58
lbragstadjohnthetubaguy aha - yeah I was digging through that a little bit earlier17:58
dstanekjohnthetubaguy: but if you say -1 i'm assuming you want the parent's value. without returning the hierarchy all children with -1 will return the parent's value and that would be more than they should use17:58
*** amotoki has quit IRC17:59
*** donghao has quit IRC17:59
johnthetubaguydstanek: no, I return please check the whole sub tree doesn't exceed the parent's value, i.e. do your count across all the children that are marked as -117:59
sdaguejohnthetubaguy: ok, fixed the syntax issue18:00
johnthetubaguysdague: yeah, I have parent projects defaulting to some value, and all children defaulting to -1 (instead of 0)18:00
sdaguebut look at that final example question18:00
dstanekjohnthetubaguy: the counting happens on the service side though right?18:01
sdaguein the A B C D tree18:01
dstanekfor example, line 58 in https://gist.github.com/dstanek/a8a343a3ab5ad4ad0862e3e1be332173 - how does that get implemented in a flat way?18:01
johnthetubaguydstanek: yes, the count functions are registered with the library18:01
johnthetubaguysdague: which line should I be looking at?18:01
sdague21218:01
*** breitz has quit IRC18:02
sdaguewhat is the impact on D and B with that command18:02
johnthetubaguysdague: so thats given all the resources to C, I think18:03
johnthetubaguysdague: so that means A, B, D are not allowed anything18:03
*** iyamahat has quit IRC18:03
sdaguejohnthetubaguy: so D would have limits = -118:04
sdagueand be told "over quota" on all actions?18:04
johnthetubaguysdague: .... yes, I guess so18:04
*** athomas has quit IRC18:05
sdagueand junior admin gets the ticket, and logs into the system, and does what to resolve it?18:05
sdagueor even understand the state of the world18:06
*** lpetrut has quit IRC18:06
johnthetubaguysdague: yeah, thats a good reason why its broken18:06
*** slaweq_ has quit IRC18:06
sdaguebecause, I am quite concerned with "you are over quota" without a clear way to increase the quota18:06
johnthetubaguyyeah, thats hard to debug18:06
johnthetubaguyand reason about18:07
*** e0ne has joined #openstack-dev18:07
johnthetubaguydstanek: not sure I understand the case on your line 58, just thinking it though18:08
*** TxGirlGeek has joined #openstack-dev18:08
*** slaweq_ has joined #openstack-dev18:08
sdaguejohnthetubaguy: ok, I'm just going to stop exploring the Garbutt Model then, and leave the open question18:09
johnthetubaguysdague: yeah, I think you convinced me on defaulting to 018:09
*** rcernin has joined #openstack-dev18:09
dstanekjohnthetubaguy: it A (limit 10) -> B (nothing set) -> C (limit 4)18:10
johnthetubaguydstanek: is this the overcommit case?18:10
dstanekyou have to know both 10 and 4 on the usage side to calculate correct18:10
sdaguealso, this is really really why I wanted us to write all these models down and ask questions. Because I think that in working memory everyone had an idea and some happy path behavior, but hadn't thought through18:10
*** bobmel has quit IRC18:10
johnthetubaguysdague: +1 getting this written down18:10
sdaguedstanek: you need to express more rules18:10
*** ygbo has quit IRC18:10
*** jdandrea has joined #openstack-dev18:10
*** gyee has joined #openstack-dev18:11
johnthetubaguyyeah, I am missing some rules18:11
johnthetubaguyB = 0 or B= -1?18:11
sdaguedstanek: because the Garbutt model is the only ruleset we wrote down so far that would let us get there18:11
*** ccneill has joined #openstack-dev18:11
*** gszasz has quit IRC18:11
johnthetubaguyyeah18:11
dstanekjohnthetubaguy: not exactly. simple example is A (limit 10) has two children B and C with B and C not having explicit limits18:11
sdagueand I think we just crossed it off the list18:11
johnthetubaguydstanek: we are saying the children have 0 quota by default here18:11
sdaguedstanek: right, so the thing i was calling Strict Hierarchy Default Closed18:12
sdaguewouldn't let you set that18:12
sdagueUpdate C limit 4 would fail, because unset is effective 018:12
*** bobmel has joined #openstack-dev18:12
dstaneksdague: that's what i was asking earlier. will everything have to have an explicit limit for every project?18:12
johnthetubaguyah... so there is another rule set here18:12
johnthetubaguydang it18:13
sdaguedstanek: I think we are too early to ask that question18:13
*** gfidente has quit IRC18:13
sdaguedstanek: we need to write out what the possible models here that we are considering18:13
sdagueand walk through their implications18:13
dstanekthat's why i brought the case of not setting it.18:13
*** slaweq_ has quit IRC18:14
dstaneksdague: when you say models what are you refering to?18:14
*** jdurgin has quit IRC18:14
sdaguedstanek: right, so in SHDC, once you set a limit on a parent (including defaults being set) you have to give every child specific grants, in descending order18:14
sdaguedstanek: https://review.openstack.org/#/c/44120318:14
*** fragatina has quit IRC18:15
johnthetubaguyI guess its the outcome of line 76 in here: https://review.openstack.org/#/c/441203/4/specs/keystone/backlog/hierarchical-quota-scenarios.rst18:15
sdaguesorry, I linked that earlier18:15
sdaguejohnthetubaguy: right18:15
dstaneki probably missed it while in a meeting18:15
*** slaweq_ has joined #openstack-dev18:15
sdaguedstanek: this is the follow on document of different quota models18:16
johnthetubaguyI think you remove the rule of the child needing more quota than its parent18:16
johnthetubaguywhich is interesting18:16
johnthetubaguysdague: so where I failed, I think, was only one one layer of hierarchy deep, mine falls apart when you got more than two deep really18:17
sdaguejohnthetubaguy: yeh, you definitely need to model with 2+ layers18:17
johnthetubaguyI kept thinking they are all sub trees, but thats nonsense18:17
*** e0ne has quit IRC18:18
alexismonvillethe openstack team survey for FY17Q4 is ready to collect your inputs https://goo.gl/forms/S4SmLxq9hpzCbkpn118:18
alexismonvilleooopppps... bad channel18:18
alexismonvillesorry for that18:18
*** lucasxu has quit IRC18:19
*** aysyd has quit IRC18:19
sdaguejohnthetubaguy: yeh, especially as one of the key use cases is to make a project for a division, and let them self manage creating new projects to their hearts content.18:19
*** aysyd has joined #openstack-dev18:20
*** jmckind has joined #openstack-dev18:20
sdagueI guess we could just mandate that all organizations get rid of management hierarchies18:20
johnthetubaguysdague: that works for me :)18:20
* johnthetubaguy giggles18:20
sdaguesmcginnis: http://docs-draft.openstack.org/03/441203/5/check/gate-keystone-specs-docs-ubuntu-xenial/7a38237//doc/build/html/specs/keystone/backlog/hierarchical-quota-scenarios.html is the document we're currently just trying to flesh out18:20
johnthetubaguyyeah, I was thinking consider each sub tree one layer deep recursively, but that broke down really badly18:21
smcginnisIf I rememeber right (big if) child projects get -1 and any can consume up to the parent quota in Cinder.18:21
smcginnisOoh, pictures.18:21
lbragstadsmcginnis that's how it works today18:21
johnthetubaguyah, so I totally missed that18:21
lbragstad?18:21
johnthetubaguyI thought it defaulted to 018:21
dstaneksdague: so i think i was describing my take on the Garbutt model18:21
sdaguesmcginnis: so... it's the Garbutt Model?18:22
sdaguein which case, how do you handle the open question listed in there?18:22
* smcginnis is reading through18:22
*** jmckind has quit IRC18:23
sdaguesmcginnis: just for reference, these are just trying to express rulesets and see where their edge conditions are18:23
smcginnisack18:23
sdaguetowards eventually figuring out which ruleset(s) would be supported18:23
smcginnisGood exercise18:23
smcginnisI'm not sure we've captured this elsewhere.18:23
smcginnisWhich would have really helped now to go back through and evaluate where we are at.18:24
lbragstadso in the Garbutt Model, if I set the limit of C to something that effectively takes the local limit from A, B is showing a local limit of 0?18:24
dstaneksdague: does -1 mean us up as much as a parent allows?18:24
sdaguesmcginnis: yeh, during the PTG I basically realized "If I don't have pictures and labels, I'm lost"18:24
sdaguedstanek: yes18:25
*** eezhova has quit IRC18:25
lbragstadif we didn't have a common diagram we'd all be whiteboarding this individually anyway18:25
sdagueit means fail open vs. fail closed18:25
*** lucasxu has joined #openstack-dev18:25
johnthetubaguysmcginnis: is the current behaviour different to this one: http://specs.openstack.org/openstack/cinder-specs/specs/liberty/cinder-nested-quota-driver.html18:25
johnthetubaguythat said it defaults to 0, but I guess it maybe allows -1 as an override?18:26
smcginnisSo I think what cinder has now is the Strict Hierarchy Default Closed model, with the exception of the default being -1 instead of 0.18:26
smcginnisjohnthetubaguy: I thought it was -1.18:26
*** luizbag has left #openstack-dev18:27
*** jdurgin has joined #openstack-dev18:27
smcginnisjohnthetubaguy: The 'allocated' amount defaults to 0.18:28
sdagueok, need lunch, will be back in a bit18:28
dstaneki'm not completely grokking the idea of local limits.18:28
johnthetubaguyit could be, its just the spec is different18:28
johnthetubaguyyeah, I should go now really18:28
lbragstadi think local limit is dedicated to that specific node18:28
smcginnisjohnthetubaguy: Wouldn't be the first time our spec doesn't match what went in. :/18:28
sdaguedstanek: the local limit thing is that by giving a child limit allocation, it removes from yours18:28
johnthetubaguysdague: thanks for your doc though, thats a big help18:28
johnthetubaguysmcginnis: true18:28
lbragstadso it should be used as a tool to not have *all* children consume everything18:28
*** breitz has joined #openstack-dev18:28
lbragstadaha - right... so if the local limit of A is 10 and limit for C is updated to 10, the local limits for both A and B are set to 018:29
johnthetubaguyyeah18:29
johnthetubaguyso I guess that is the model I was thinking about18:29
sdaguelbragstad: right, but it does put D in a weird place18:30
sdagueto figure out how to get out of it18:30
lbragstadright18:30
dstaneksdague: ok, then my model is similar to Garbutt, but less strict18:30
lbragstadi think we're making progress understand the parent child relationship, but siblings is totally new18:30
lbragstadunderstanding*18:30
sdaguedstanek: ok, how about you add a stanek model to the doc. Just let me know if you do so I don't accidentally overwrite18:31
sdaguethe blockdiag is pretty easy markup18:31
dstaneksdague: cool will do18:31
lbragstadalright - breaking for lunch and going to take care of a couple errands18:33
dstaneklbragstad: you're not supposed to be working anymore today :P18:33
* johnthetubaguy runs away18:34
*** fragatina has joined #openstack-dev18:37
*** jdurgin has quit IRC18:37
*** ijw has joined #openstack-dev18:38
*** iyamahat has joined #openstack-dev18:39
*** dharinic is now known as dharinic|lunch18:42
*** spartacloud has joined #openstack-dev18:43
*** valw has joined #openstack-dev18:43
*** jdurgin has joined #openstack-dev18:44
*** sdake has quit IRC18:47
*** ericyoung has quit IRC18:48
*** electrofelix has quit IRC18:50
*** radhikam has quit IRC18:51
*** radhikam has joined #openstack-dev18:51
lbragstaddstanek neither are you!18:52
*** salv-orl_ has joined #openstack-dev18:52
*** sdake has joined #openstack-dev18:53
dstaneklbragstad: sick kid here so i can't really leave the house anyway18:55
*** salv-orlando has quit IRC18:56
*** jkilpatr has joined #openstack-dev18:56
*** robputt_ is now known as robputt18:57
*** lpetrut has joined #openstack-dev18:59
*** donghao has joined #openstack-dev18:59
*** TxGirlGeek has quit IRC19:00
*** jkilpatr_ has quit IRC19:00
*** TxGirlGeek has joined #openstack-dev19:00
*** jed56_ has quit IRC19:00
*** jcoufal_ has joined #openstack-dev19:02
*** jcoufal has quit IRC19:05
*** dizquierdo has quit IRC19:05
*** kjw3 has quit IRC19:07
*** hseipp has joined #openstack-dev19:07
*** kjw3 has joined #openstack-dev19:07
*** donghao has quit IRC19:07
*** baoli has quit IRC19:09
*** ddellav has joined #openstack-dev19:09
*** baoli has joined #openstack-dev19:10
*** bobmel has quit IRC19:11
*** valw_ has joined #openstack-dev19:13
*** valw has quit IRC19:13
*** john-davidge has quit IRC19:15
dstaneksdague: i think i accurately captured my thoughts. is it safe to push the spec?19:18
sdaguedstanek: go for it19:19
sdagueI'll make sure to update my local copy to not clobber19:19
*** jungleboyj has joined #openstack-dev19:20
dstaneki've added the 'Freedom Model' because nobody hates freedom19:22
*** jdandrea has quit IRC19:23
*** rcrit has quit IRC19:23
*** hseipp has quit IRC19:24
*** ansmith has quit IRC19:24
sdagueoh dear :)19:25
*** kbringard1 has quit IRC19:25
*** kbringard has joined #openstack-dev19:25
dstaneksdague: feel free to rename19:26
*** rockyg has joined #openstack-dev19:29
*** jcoufal has joined #openstack-dev19:32
*** greghayn1 is now known as greghaynes19:33
*** rcrit has joined #openstack-dev19:33
*** jcoufal_ has quit IRC19:34
*** aweeks has joined #openstack-dev19:34
*** TxGirlGeek has quit IRC19:35
*** TxGirlGeek has joined #openstack-dev19:36
sdaguedstanek: ok, looking at your example19:37
*** rockyg has quit IRC19:38
*** rockyg has joined #openstack-dev19:38
sdagueso, here is the follow on question about how would we resolve this19:38
sdagueC allocates 519:38
sdagueE allocates 519:38
sdagueF tries to allocate 1, is told they are over quota, even though they've not allocated anything19:39
sdaguefiles a ticket to get quota19:39
*** ShaneDavidson has joined #openstack-dev19:39
sdaguewhat does the admin do?19:40
*** salv-orl_ has quit IRC19:40
*** matrohon has joined #openstack-dev19:41
sdaguemaybe I'll just put the questions into the document19:41
dstanekthe admin would need to up the limit somewhere since the quotes19:41
dstanekanother option would be to say that quotas that are explicitly set are independent from thier parent, but that seems like it would be harder to understand19:42
dstaneksdague: that's the same issue you'd have in the Garbutt model's first example right?19:43
jungleboyjdstanek: You don't want to make the quotas that are explicitly set independent from the parent.  Then it isn't hierarchical.19:43
dstanekjungleboyj: yep, another reason not to do that19:43
sdaguedstanek: yeh, so when computing usage, if we put unlimited in anywhere then we need to basically query and count everything in the tree19:43
jungleboyj:-)  I was team lead for the guy who tired to get this in place so I know a little.19:44
*** kbringard1 has joined #openstack-dev19:44
*** dharinic|lunch is now known as dharinic19:44
sdaguedstanek: the other concern I have with ever defaulting to unlimitted, is you bring a new service/resource into play, and you need to go make a limit update to every project19:44
*** eezhova has joined #openstack-dev19:45
sdaguebut maybe, that shouldn't be a huge concern19:45
*** kbringard has quit IRC19:46
dstaneksdague: that where that additional global rules thought came in19:46
dstanekit would be used in the absence of finding any explicit limit upwards in teh tree19:47
sdaguedstanek: ok, right, so this really continues to follow the resource default limit from the unified limits spec19:47
sdaguethe terminology shifted a little be there in your section, so that wasn't clear to me19:48
*** TxGirlGeek has quit IRC19:49
*** annegentle has quit IRC19:51
* dstanek is sometimes shifty19:51
*** achampion has joined #openstack-dev19:52
*** TxGirlGeek has joined #openstack-dev19:52
*** ryotagami has quit IRC19:54
sdagueheh19:55
*** dhajare has quit IRC19:55
*** TxGirlGeek has quit IRC19:55
*** baoli_ has joined #openstack-dev19:55
*** baoli has quit IRC19:55
*** amotoki has joined #openstack-dev19:55
sdagueok, well my brain is fully burnt on all of this today, but at least I think we're making some progress in writing ideas down.19:55
*** mjbrender has joined #openstack-dev19:56
*** salv-orlando has joined #openstack-dev19:57
*** ryotagami has joined #openstack-dev19:58
*** valw_ has quit IRC19:58
*** galstrom is now known as galstrom_zzz19:59
*** amotoki has quit IRC20:00
*** ShaneDavidson has quit IRC20:00
*** pwnall138 is now known as zz_pwnall13820:00
*** jdandrea has joined #openstack-dev20:01
*** vladikr has quit IRC20:04
*** xarses_ has quit IRC20:09
*** bobmel has joined #openstack-dev20:12
*** matrohon has quit IRC20:13
*** john-davidge has joined #openstack-dev20:16
*** kbringard1 has quit IRC20:16
*** mjbrender has quit IRC20:17
*** xarses_ has joined #openstack-dev20:17
*** bobmel has quit IRC20:18
*** andreww has joined #openstack-dev20:18
*** andreww has quit IRC20:18
*** andreww has joined #openstack-dev20:18
*** galstrom_zzz is now known as galstrom20:19
*** john-davidge has quit IRC20:21
*** xarses_ has quit IRC20:21
*** ansmith has joined #openstack-dev20:21
*** eezhova has quit IRC20:23
*** rockyg has quit IRC20:23
*** rockyg has joined #openstack-dev20:29
*** TxGirlGeek has joined #openstack-dev20:30
*** ansmith has quit IRC20:31
*** achampion has quit IRC20:31
*** jcoufal has quit IRC20:34
jungleboyjsdague: If you need help on the Hiearchical Quota stuff in the future, let me know and I will see if I can dig up some knowledge.20:35
*** jcoufal has joined #openstack-dev20:36
sdaguejungleboyj: well, right now, just trying to write down stuff that came from the PTG20:36
sdagueand make sure we're all talking about the same things20:37
jungleboyjsdague: Ok.  Sounds good.20:37
sdaguebecause things like overbooking got used a lot20:37
sdaguebut people were having it mean different things20:37
jungleboyjsdague: That is a common problem for OpenStack.  We have that problem in Cinder frequently as each  company seems to have slightly different terminology for things.20:38
*** sree has joined #openstack-dev20:38
jungleboyjAnd then we have the same challenge across OpenStack projects.  :-(20:38
*** sree has quit IRC20:43
*** rockyg has quit IRC20:44
*** egallen has quit IRC20:45
*** halves has quit IRC20:52
*** yassine has quit IRC21:00
*** heroux has quit IRC21:10
*** andreww has quit IRC21:11
*** andreww has joined #openstack-dev21:12
*** ccneill has quit IRC21:12
*** sdake_ has joined #openstack-dev21:13
*** xarses_ has joined #openstack-dev21:13
*** baoli_ has quit IRC21:14
*** andreww has quit IRC21:16
*** sdake has quit IRC21:16
*** kjw3 has quit IRC21:19
*** iyamahat has quit IRC21:19
*** rfolco has quit IRC21:19
*** ijw has quit IRC21:21
*** ijw has joined #openstack-dev21:21
*** rfolco has joined #openstack-dev21:23
*** morazi_ has quit IRC21:23
*** rfolco has quit IRC21:23
*** eezhova has joined #openstack-dev21:24
*** bobmel has joined #openstack-dev21:25
*** jdandrea has quit IRC21:25
*** diablo_rojo has quit IRC21:28
sdaguejungleboyj: yep, that's why I started making blockdiag diagrams21:28
*** diablo_rojo has joined #openstack-dev21:29
*** jamielennox is now known as jamielennox|away21:29
*** amrith has quit IRC21:29
*** bobmel has quit IRC21:30
*** aysyd has quit IRC21:35
*** diablo_rojo has quit IRC21:35
*** egallen has joined #openstack-dev21:37
*** kjw3 has joined #openstack-dev21:40
openstackgerritArmando Migliaccio proposed openstack/governance master: Retire networking-ofagent  https://review.openstack.org/44148821:42
jungleboyjsdague: cool.  Getting stuff like that easier to understand is a good thing.21:43
sdaguejungleboyj: ++21:44
*** achampion has joined #openstack-dev21:46
jungleboyjThanks for working on it.21:47
*** thorst has quit IRC21:48
*** egallen_ has joined #openstack-dev21:48
*** baoli has joined #openstack-dev21:48
*** egallen has quit IRC21:50
*** thorst has joined #openstack-dev21:50
*** rcernin has quit IRC21:51
*** egallen_ has quit IRC21:52
*** achampion has quit IRC21:52
*** thorst has quit IRC21:55
*** amotoki has joined #openstack-dev21:56
*** gpj89 has quit IRC21:57
*** xyang1 has joined #openstack-dev22:00
*** lucasxu has quit IRC22:00
*** baoli has quit IRC22:02
*** amotoki has quit IRC22:03
*** saibarspeis has joined #openstack-dev22:03
*** kriskend has quit IRC22:06
*** jaypipes has joined #openstack-dev22:07
*** xemdetia has quit IRC22:09
*** sdake_ has quit IRC22:09
*** vipuls has quit IRC22:13
*** eharney has quit IRC22:15
*** athmane_ has quit IRC22:15
*** athmane has joined #openstack-dev22:15
*** jaypipes is now known as leakypipes22:15
*** galstrom is now known as galstrom_zzz22:17
*** john-davidge has joined #openstack-dev22:17
*** ihrachys has quit IRC22:18
*** vipuls has joined #openstack-dev22:20
*** john-davidge has quit IRC22:21
*** ShaneDavidson has joined #openstack-dev22:22
*** ihrachys has joined #openstack-dev22:22
*** ihrachys has quit IRC22:22
*** ihrachys has joined #openstack-dev22:23
*** priteau has quit IRC22:25
*** dimtruck is now known as zz_dimtruck22:26
*** slaweq_ has quit IRC22:28
*** slaweq_ has joined #openstack-dev22:30
*** jcoufal has quit IRC22:30
*** vnogin has joined #openstack-dev22:30
*** Leo_ has quit IRC22:31
*** ShaneDavidson has quit IRC22:32
*** sdake has joined #openstack-dev22:35
*** vnogin has quit IRC22:35
*** alexismonville has quit IRC22:36
*** donghao has joined #openstack-dev22:37
*** gordc has quit IRC22:42
*** donghao has quit IRC22:43
*** zz_dimtruck is now known as dimtruck22:44
*** achampion has joined #openstack-dev22:48
*** salv-orlando has quit IRC22:51
*** salv-orlando has joined #openstack-dev22:52
*** mriedem has quit IRC22:53
*** steveg_afk has quit IRC22:56
*** baoli has joined #openstack-dev23:00
*** radhikam has quit IRC23:02
*** baoli has quit IRC23:02
*** saibarspeis has quit IRC23:07
*** jkilpatr has quit IRC23:08
*** egallen has joined #openstack-dev23:08
*** cdent has quit IRC23:10
*** xyang1 has quit IRC23:11
*** sdake has quit IRC23:11
*** andreww has joined #openstack-dev23:13
*** xarses_ has quit IRC23:17
*** xarses_ has joined #openstack-dev23:17
*** john-davidge has joined #openstack-dev23:18
*** andreww has quit IRC23:18
*** jathan has quit IRC23:20
*** takamatsu has quit IRC23:21
*** john-davidge has quit IRC23:23
*** bobmel has joined #openstack-dev23:26
*** kirotawa has joined #openstack-dev23:27
*** david-lyle_ is now known as david-lyle23:29
*** bobmel has quit IRC23:31
*** vhosakot has quit IRC23:37
*** sree has joined #openstack-dev23:38
*** svinota has quit IRC23:39
*** jkilpatr has joined #openstack-dev23:41
*** sree has quit IRC23:42
*** marst has quit IRC23:44
*** david-lyle has quit IRC23:47
*** kgiusti has left #openstack-dev23:51
*** kobis1 has joined #openstack-dev23:52
*** kobis has quit IRC23:53
*** rfolco has joined #openstack-dev23:55
*** rfolco has quit IRC23:55
*** iyamahat has joined #openstack-dev23:56
*** gongysh has joined #openstack-dev23:57

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