Monday, 2017-03-06

*** xiaofandh12 has quit IRC00:02
*** bobmel has joined #openstack-dev00:05
*** yuntongjin has joined #openstack-dev00:09
*** yuntongjin has quit IRC00:09
*** bobmel has quit IRC00:10
*** gouthamr has joined #openstack-dev00:12
*** amotoki has joined #openstack-dev00:27
*** ssbarnea has quit IRC00:27
*** limao has joined #openstack-dev00:32
*** charcol-v2 has joined #openstack-dev00:32
*** charcol has quit IRC00:35
*** spartacloud has joined #openstack-dev00:41
*** zz_dimtruck is now known as dimtruck00:45
*** spartacloud has quit IRC00:46
*** salv-orlando has joined #openstack-dev00:53
*** salv-orlando has quit IRC00:54
*** salv-orlando has joined #openstack-dev00:54
*** salv-orl_ has quit IRC00:55
*** markvoelker has joined #openstack-dev00:56
*** dsariel has quit IRC01:02
*** donghao has joined #openstack-dev01:03
*** dimtruck is now known as zz_dimtruck01:04
*** zz_dimtruck is now known as dimtruck01:04
*** donghao has quit IRC01:08
*** tovin07 has joined #openstack-dev01:08
*** yamamoto_ has joined #openstack-dev01:10
*** gpj89 has joined #openstack-dev01:11
*** dimtruck is now known as zz_dimtruck01:13
*** erlon has quit IRC01:15
*** zz_dimtruck is now known as dimtruck01:21
*** yamamoto_ has quit IRC01:21
*** yamamoto_ has joined #openstack-dev01:25
*** yamamoto_ has quit IRC01:29
*** yamamoto_ has joined #openstack-dev01:29
*** fragatina has quit IRC01:30
*** fragatina has joined #openstack-dev01:31
*** fragatin_ has joined #openstack-dev01:32
*** fragatina has quit IRC01:36
*** yamamoto_ has quit IRC01:39
*** charcol-v2 has quit IRC01:42
*** sam_nowitzki has joined #openstack-dev01:42
*** charcol has joined #openstack-dev01:47
*** fragatin_ has quit IRC01:59
*** gongysh has joined #openstack-dev02:05
*** alexismonville has quit IRC02:09
*** yuntongjin has joined #openstack-dev02:15
*** yamamoto_ has joined #openstack-dev02:36
*** chigang has joined #openstack-dev02:42
*** yuntongjin has quit IRC03:00
*** bobmel has joined #openstack-dev03:05
*** ihrachys has joined #openstack-dev03:06
*** thorst has quit IRC03:08
*** bobmel has quit IRC03:10
*** jaypipes has joined #openstack-dev03:14
*** sree has joined #openstack-dev03:51
*** lathiat_ has quit IRC03:53
*** lathiat has joined #openstack-dev03:53
*** jaypipes has quit IRC03:54
*** nplanel has joined #openstack-dev04:09
*** adriant has quit IRC04:20
*** markvoelker has quit IRC04:23
*** thorst has joined #openstack-dev04:28
*** thorst has quit IRC04:28
*** jaypipes has joined #openstack-dev04:30
*** spartacloud has joined #openstack-dev04:43
*** spartacloud has quit IRC04:48
*** chigang has quit IRC04:49
*** psachin has joined #openstack-dev04:49
*** nmathew has joined #openstack-dev04:50
*** vnogin has joined #openstack-dev04:54
*** vnogin has quit IRC04:58
*** claudiub has joined #openstack-dev04:59
*** yuntongjin has joined #openstack-dev05:01
*** ShaneDavidson_ has quit IRC05:05
*** sreenath has joined #openstack-dev05:09
*** limao has quit IRC05:15
*** limao has joined #openstack-dev05:15
*** markvoelker has joined #openstack-dev05:24
*** markvoelker has quit IRC05:29
*** thorst has joined #openstack-dev05:29
*** bobmel has joined #openstack-dev05:32
*** thorst has quit IRC05:34
*** gpj89 has quit IRC05:34
*** timothyb89 has quit IRC05:35
*** timothyb89 has joined #openstack-dev05:35
*** bobmel has quit IRC05:37
*** amotoki_ has joined #openstack-dev05:42
*** psachin has quit IRC05:42
*** ksobkowiak has quit IRC05:44
*** amotoki has quit IRC05:46
*** saibarspeis has joined #openstack-dev05:50
*** hichihara has joined #openstack-dev05:51
*** kobis has joined #openstack-dev05:54
*** Poornima has joined #openstack-dev05:55
*** Poornima has quit IRC05:55
*** achampion has quit IRC05:56
*** Poornima has joined #openstack-dev05:56
*** Poornima has quit IRC05:57
*** achampion has joined #openstack-dev05:58
*** sridharg has joined #openstack-dev05:58
*** Poornima has joined #openstack-dev05:58
*** Poornima has joined #openstack-dev06:00
*** gouthamr has quit IRC06:02
*** kobis has quit IRC06:04
*** Poornima has joined #openstack-dev06:05
*** eroux has quit IRC06:05
*** Poornima has quit IRC06:07
*** rcernin has joined #openstack-dev06:08
*** Poornima has joined #openstack-dev06:09
*** abregman has joined #openstack-dev06:15
*** ekuris has joined #openstack-dev06:15
*** dhajare has joined #openstack-dev06:22
*** kornica is now known as kornicameiter06:30
*** kornicameiter is now known as kornicameister06:30
*** thorst has joined #openstack-dev06:30
*** thorst has quit IRC06:34
*** charcol-v2 has joined #openstack-dev06:35
*** charcol has quit IRC06:37
*** markvoelker has joined #openstack-dev06:44
*** svinota has joined #openstack-dev06:45
*** dimtruck is now known as zz_dimtruck06:49
*** zz_dimtruck is now known as dimtruck06:49
*** ayogi has joined #openstack-dev06:52
*** salv-orl_ has joined #openstack-dev06:53
*** itzikb has joined #openstack-dev06:54
*** AnilV4 has joined #openstack-dev06:55
*** brault has quit IRC06:55
*** salv-orlando has quit IRC06:56
*** pcaruana has joined #openstack-dev06:58
*** dimtruck is now known as zz_dimtruck06:59
*** charcol-v2 has quit IRC07:02
*** pcaruana has quit IRC07:05
*** pcaruana has joined #openstack-dev07:06
*** svinota has quit IRC07:12
*** tesseract has joined #openstack-dev07:13
*** saibarspeis has quit IRC07:15
*** fragatina has joined #openstack-dev07:18
*** dsariel has joined #openstack-dev07:20
*** ihrachys has quit IRC07:25
*** takamatsu has joined #openstack-dev07:25
*** ihrachys has joined #openstack-dev07:26
*** eroux has joined #openstack-dev07:27
*** kobis has joined #openstack-dev07:29
*** kobis has quit IRC07:29
*** ihrachys has quit IRC07:30
*** jprovazn has joined #openstack-dev07:30
*** ltomasbo|away is now known as ltomasbo07:31
*** ihrachys has joined #openstack-dev07:36
*** fragatina has quit IRC07:38
*** ihrachys has quit IRC07:40
*** hseipp has joined #openstack-dev07:41
*** ihrachys has joined #openstack-dev07:56
*** ihrachys has quit IRC08:00
*** slaweq_ has quit IRC08:03
*** brault has joined #openstack-dev08:08
*** slaweq_ has joined #openstack-dev08:08
*** tovin07 has quit IRC08:12
*** tovin07 has joined #openstack-dev08:12
*** karthiks has joined #openstack-dev08:16
*** ihrachys has joined #openstack-dev08:16
*** paramite has joined #openstack-dev08:17
*** eezhova has joined #openstack-dev08:18
*** yuval has joined #openstack-dev08:20
*** ihrachys has quit IRC08:20
*** eantyshev has left #openstack-dev08:26
*** ihrachys has joined #openstack-dev08:26
*** hichihara has quit IRC08:27
*** ihrachys has quit IRC08:31
*** thorst has joined #openstack-dev08:32
*** bauwser is now known as bauzas08:34
*** nmathew- has joined #openstack-dev08:35
*** thorst has quit IRC08:36
*** nmathew has quit IRC08:38
*** ciprian-barbu has quit IRC08:42
*** fragatina has joined #openstack-dev08:46
*** rwsu has quit IRC08:47
*** jpich has joined #openstack-dev08:50
*** markvoelker_ has joined #openstack-dev08:51
*** svinota has joined #openstack-dev08:51
*** markvoelker has quit IRC08:54
*** snica_away is now known as snica08:54
*** sam_nowitzki has quit IRC08:56
*** zzzeek has quit IRC09:00
*** sridharg has quit IRC09:00
*** kobis has joined #openstack-dev09:00
*** zzzeek has joined #openstack-dev09:00
*** yamamoto_ has quit IRC09:00
*** shardy has joined #openstack-dev09:00
*** rwsu has joined #openstack-dev09:01
*** sridharg has joined #openstack-dev09:03
*** eezhova has quit IRC09:04
*** kobis has quit IRC09:10
*** sshnaidm|off is now known as sshnaidm09:13
*** e0ne has joined #openstack-dev09:13
*** d0ugal has quit IRC09:14
*** nmathew- has quit IRC09:15
*** bogdando has joined #openstack-dev09:15
*** Poornima has quit IRC09:21
*** Poornima has joined #openstack-dev09:21
*** d0ugal has joined #openstack-dev09:26
*** d0ugal has quit IRC09:26
*** d0ugal has joined #openstack-dev09:26
*** eezhova has joined #openstack-dev09:28
openstackgerritYuval Brik proposed openstack/governance master: karbor: add api-ref link  https://review.openstack.org/44183309:29
*** akrivoka has joined #openstack-dev09:31
*** thorst has joined #openstack-dev09:33
*** Poornima has quit IRC09:35
*** Poornima has joined #openstack-dev09:35
*** sam_nowitzki has joined #openstack-dev09:36
*** athomas has joined #openstack-dev09:37
*** thorst has quit IRC09:37
*** abregman is now known as abregman|mtg09:42
*** abregman|mtg has quit IRC09:42
*** lucas-afk is now known as lucasagomes09:43
*** abregman has joined #openstack-dev09:44
*** sridharg has quit IRC09:47
*** ssbarnea has joined #openstack-dev09:47
*** sridharg has joined #openstack-dev09:49
*** gmoro has joined #openstack-dev09:49
*** radhikam has quit IRC09:51
*** radhikam has joined #openstack-dev09:51
*** sree has quit IRC09:52
*** radhikam has quit IRC09:52
*** radhikam has joined #openstack-dev09:52
*** ygbo has joined #openstack-dev09:52
*** radhikam has quit IRC09:53
*** sree has joined #openstack-dev09:53
*** radhikam has joined #openstack-dev09:53
*** radhikam has quit IRC09:54
*** radhikam has joined #openstack-dev09:54
*** radhikam has quit IRC09:54
*** radhikam has joined #openstack-dev09:55
*** radhikam has quit IRC09:55
*** ababich has quit IRC09:55
*** radhikam has joined #openstack-dev09:55
*** radhikam has quit IRC09:56
*** radhikam has joined #openstack-dev09:56
*** radhikam has quit IRC09:57
*** radhikam has joined #openstack-dev09:57
*** radhikam has quit IRC09:58
*** radhikam has joined #openstack-dev09:58
*** electrofelix has joined #openstack-dev09:58
*** radhikam has quit IRC09:58
*** radhikam has joined #openstack-dev09:59
*** radhikam has quit IRC09:59
*** radhikam has joined #openstack-dev09:59
*** vills_ has joined #openstack-dev10:00
*** radhikam has quit IRC10:00
*** radhikam has joined #openstack-dev10:00
*** radhikam has quit IRC10:01
*** radhikam has joined #openstack-dev10:01
*** limao has quit IRC10:01
*** radhikam has quit IRC10:02
*** yuntongjin has quit IRC10:02
*** radhikam has joined #openstack-dev10:02
*** radhikam has quit IRC10:02
*** MattMan has quit IRC10:02
*** MattMan has joined #openstack-dev10:03
*** radhikam has joined #openstack-dev10:03
*** k4n0 has joined #openstack-dev10:03
*** radhikam has quit IRC10:03
*** donghao has joined #openstack-dev10:04
*** donghao has quit IRC10:08
*** mdbooth_ is now known as mdbooth10:08
*** john-davidge has joined #openstack-dev10:09
*** vnogin has joined #openstack-dev10:10
*** athomas has quit IRC10:11
*** vnogin has quit IRC10:15
*** athomas has joined #openstack-dev10:18
*** dalees has quit IRC10:19
*** sdague has joined #openstack-dev10:25
*** Haaibo has joined #openstack-dev10:25
*** dalees has joined #openstack-dev10:25
*** Gk-1wm-su has joined #openstack-dev10:26
*** Gk-1wm-su has quit IRC10:27
*** Gk-1wm-su has joined #openstack-dev10:28
*** abregman has quit IRC10:29
openstackgerritMerged openstack/governance master: Add ovsdbapp project  https://review.openstack.org/43808610:29
openstackgerritMerged openstack/governance master: Add new pynotedb project  https://review.openstack.org/43829110:29
openstackgerritMerged openstack/governance master: Update email for Cinder PTL  https://review.openstack.org/44120010:32
*** owalsh-afk is now known as owalsh10:33
*** openstackgerrit has quit IRC10:33
*** thorst has joined #openstack-dev10:34
*** Gk-1wm-su has quit IRC10:35
*** mvk has quit IRC10:35
*** vnogin has joined #openstack-dev10:36
*** ssbarnea has quit IRC10:36
*** ssbarnea has joined #openstack-dev10:37
*** thorst has quit IRC10:38
*** egallen has joined #openstack-dev10:39
*** amotoki_ has quit IRC10:40
*** ciprian-barbu has joined #openstack-dev10:41
*** abregman has joined #openstack-dev10:43
*** dalgaaf has quit IRC10:43
*** dalgaaf has joined #openstack-dev10:45
*** dtantsur|afk is now known as dtantsur10:46
*** kobis has joined #openstack-dev10:47
*** vills_ has quit IRC10:52
*** rraja has joined #openstack-dev10:52
*** cdent has joined #openstack-dev10:52
*** lpetrut has joined #openstack-dev10:54
*** gszasz has joined #openstack-dev11:00
*** nicolasbock has joined #openstack-dev11:05
*** ciprian-barbu has quit IRC11:07
*** mvk has joined #openstack-dev11:07
*** nplanel has quit IRC11:12
*** sdague has quit IRC11:13
*** sdague_ has joined #openstack-dev11:14
*** sdague has joined #openstack-dev11:14
*** sdague has quit IRC11:16
*** sdague_ is now known as sdague11:16
*** vills has joined #openstack-dev11:17
*** sam_nowitzki has quit IRC11:20
*** Poornima has quit IRC11:21
*** sree has quit IRC11:21
*** gongysh has quit IRC11:21
*** sree has joined #openstack-dev11:21
*** fragatina has quit IRC11:22
*** fragatina has joined #openstack-dev11:23
*** vills has left #openstack-dev11:25
*** sree has quit IRC11:26
*** shardy has quit IRC11:26
*** shardy has joined #openstack-dev11:26
*** ihrachys has joined #openstack-dev11:29
*** furlongm has quit IRC11:32
*** furlongm has joined #openstack-dev11:32
*** ihrachys has quit IRC11:33
*** eglynn has joined #openstack-dev11:35
*** yassine has quit IRC11:44
*** ggherdov-___ is now known as ggherdov-11:52
*** gszasz has quit IRC11:54
*** snica is now known as snica_away12:00
*** yuntongjin has joined #openstack-dev12:01
*** amotoki has joined #openstack-dev12:01
*** gszasz has joined #openstack-dev12:03
*** gszasz has quit IRC12:03
*** Jack_I has joined #openstack-dev12:06
*** aysyd has joined #openstack-dev12:12
*** rfolco has joined #openstack-dev12:17
*** snica_away is now known as snica12:18
*** shardy is now known as shardy_lunch12:21
*** nplanel has joined #openstack-dev12:26
*** openstackgerrit has joined #openstack-dev12:32
openstackgerritJohn Garbutt proposed openstack/project-team-guide master: WIP: Addressing the challenges of a global community  https://review.openstack.org/44192312:32
*** gordc has joined #openstack-dev12:38
*** lucasagomes is now known as lucas-hungry12:41
*** sridharg has quit IRC12:43
*** thorst has joined #openstack-dev12:44
*** alexismonville has joined #openstack-dev12:47
*** ociuhandu has joined #openstack-dev12:48
*** ihrachys has joined #openstack-dev12:49
*** jamielennox is now known as jamielennox|away12:50
*** yassine has joined #openstack-dev12:52
*** rfolco has quit IRC12:52
*** alexismonville has quit IRC12:53
*** alexismonville has joined #openstack-dev12:53
*** salv-orlando has joined #openstack-dev12:53
*** rfolco has joined #openstack-dev12:54
*** ihrachys has quit IRC12:54
*** gamado has joined #openstack-dev12:55
*** salv-orl_ has quit IRC12:56
*** shardy_lunch is now known as shardy12:56
sdagueianychoi: question about https://review.openstack.org/#/c/43950012:56
*** owalsh is now known as owalsh-afk12:58
*** abregman has quit IRC12:59
*** ihrachys has joined #openstack-dev13:00
*** abregman has joined #openstack-dev13:00
*** kylek3h_ has quit IRC13:01
*** sridharg has joined #openstack-dev13:03
*** abregman is now known as abregman|mtg13:03
*** ihrachys has quit IRC13:04
*** slaweq_ has quit IRC13:09
*** slaweq_ has joined #openstack-dev13:10
*** jkilpatr has joined #openstack-dev13:12
*** AnilV4 has quit IRC13:18
*** steveg_afk has joined #openstack-dev13:18
*** ihrachys has joined #openstack-dev13:20
*** vsaienk01 has quit IRC13:23
*** ihrachys has quit IRC13:25
*** yuntongjin has quit IRC13:25
*** yuntongjin has joined #openstack-dev13:25
*** ayogi has quit IRC13:29
*** Poornima has joined #openstack-dev13:29
*** abregman|mtg has quit IRC13:31
*** sshnaidm has quit IRC13:32
*** limao has joined #openstack-dev13:35
*** vladikr has joined #openstack-dev13:36
*** bobmel has joined #openstack-dev13:37
*** kylek3h has joined #openstack-dev13:37
*** sshnaidm has joined #openstack-dev13:38
*** rcrit has joined #openstack-dev13:38
*** jkilpatr has quit IRC13:39
*** rderose has joined #openstack-dev13:40
*** skazi has quit IRC13:41
*** sridharg has quit IRC13:41
*** sridharg has joined #openstack-dev13:41
*** abregman|mtg has joined #openstack-dev13:44
*** baoli has joined #openstack-dev13:47
*** ansmith has joined #openstack-dev13:48
*** baoli has quit IRC13:48
*** baoli has joined #openstack-dev13:49
*** baoli has quit IRC13:50
*** baoli_ has joined #openstack-dev13:50
*** ihrachys has joined #openstack-dev13:50
*** lucas-hungry is now known as lucasagomes13:51
*** baoli_ has quit IRC13:51
*** kgiusti has joined #openstack-dev13:53
*** donghao has joined #openstack-dev13:53
*** skazi has joined #openstack-dev13:54
*** gszasz has joined #openstack-dev13:54
*** ihrachys has quit IRC13:55
*** ansmith has quit IRC13:55
*** morazi has joined #openstack-dev13:56
*** owalsh-afk is now known as owalsh13:57
*** donghao has quit IRC13:58
*** baoli has joined #openstack-dev13:59
*** achampion has quit IRC14:00
*** achampion has joined #openstack-dev14:01
*** Poornima has quit IRC14:01
*** eroux has quit IRC14:02
*** saibarspeis has joined #openstack-dev14:02
*** noslzzp has quit IRC14:02
*** morazi has quit IRC14:03
*** noslzzp has joined #openstack-dev14:03
*** abregman|mtg has quit IRC14:04
*** Werz44 has joined #openstack-dev14:04
*** awaugama has joined #openstack-dev14:04
*** jdandrea has joined #openstack-dev14:05
*** jprovazn has quit IRC14:05
*** amotoki has quit IRC14:06
*** amotoki has joined #openstack-dev14:06
*** xyang1 has joined #openstack-dev14:09
*** ansmith has joined #openstack-dev14:09
*** mriedem has quit IRC14:09
*** ihrachys has joined #openstack-dev14:10
*** gongysh has joined #openstack-dev14:11
*** amotoki has quit IRC14:15
*** ihrachys has quit IRC14:15
*** morazi has joined #openstack-dev14:16
*** achampion has quit IRC14:18
*** abregman|mtg has joined #openstack-dev14:19
*** ihrachys has joined #openstack-dev14:21
*** fragatin_ has joined #openstack-dev14:23
*** achampion has joined #openstack-dev14:23
*** fragatina has quit IRC14:23
*** gouthamr has joined #openstack-dev14:25
*** jcoufal has joined #openstack-dev14:25
ianychoisdague, hello I am starting to keep track of your callings on here and -infra channel..14:26
*** yuntongjin has quit IRC14:27
*** yuntongjin has joined #openstack-dev14:27
*** makowals has quit IRC14:28
sdagueianychoi: ok, cool, I posted to the openstack-dev list with a question on https://review.openstack.org/#/c/439500/14:29
*** makowals has joined #openstack-dev14:30
sdaguemostly because I'd love to get rid of all the supporting infrastructure in the nova tree if the i18n team has decided it isn't needed any more14:30
ianychoisdague, I am also reading the mailing list.. and yes, I18n team decided not to translate log-level strings. However, I have seen that some companies (e.g., IBM) translate log-level strings. For those cases, leaving _LW(), LE() would be fine I think.14:33
sdagueianychoi: those aren't submitted back upstream?14:34
ianychoisdague, no - anymore, unless the policy will be changed in future14:34
ianychoisdague, then would it be beneficial to remove _LW(), _LE() for all upstream development for developers?14:35
sdaguethe whole point of upstream infrastructure in projects is because of upstream support. The _LE stuff ends up being something that definitely confuses people submitting, and adds a bunch of friction / cruft when moving things around.14:35
sdagueianychoi: yeh, that's basically my question14:35
*** yuntongjin has quit IRC14:36
sdagueif the i18n team has declared that traslated logs are not useful, and even at times harmful, we should embrace that and simplify all the upstream code at the same time14:36
sdaguebecause the only reason that was put in was because the i18n team wanted it14:37
ianychoisdague, I have just thought that most developers agreed to follow _LE, _LW as a convention.14:37
sdagueianychoi: only because i18n team was using it14:38
sdaguemost developers hate it14:38
*** sree has joined #openstack-dev14:38
ianychoisdague, Hmm, I have not recognized such things. Question: for such convention discussion, which places would be proper? oslo-18n discussion?14:38
sdaguebut if the i18n team is not going to use it, then it's extra work for no reason14:38
sdagueianychoi: I think just the openstack-dev mailing list14:39
sdagueianychoi: http://lists.openstack.org/pipermail/openstack-dev/2017-March/113365.html I started a thread here14:39
*** yuval has quit IRC14:40
sdaguethis impacts the wider community rather significantly. I'm happy taking the lead from the i18n team, but I just want to make sure I understand that the i18n team decided that log translations are not useful, and they would no longer be supporting their translation upstream14:41
sdaguebecause, that means we should stop doing the same in the projects14:41
*** amotoki has joined #openstack-dev14:41
*** pnavarro has joined #openstack-dev14:42
ianychoisdague, I see. First of all, thanks a lot for your raising, since I thought that the policy (not to translate log-level strings) was already delivered to developers.14:42
ianychoihttps://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n14:42
sdagueianychoi: yeh, I guess that message didn't get passed on. Honestly, I approved the catalog delete, but it wasn't until the tox change that I started to understand what the i18n team was doing here14:44
*** lpetrut has quit IRC14:44
*** eharney has joined #openstack-dev14:44
*** xemdetia has joined #openstack-dev14:44
ianychoiFor I18n PTL role, I tried to more communicate with cross project liaison, but unfortunately, the participation of i18n cross-project liaison is relatively low.14:44
sdagueyeh, I'm happy to just mark that up to the message got lost. No real blame there.14:45
sdagueI just want to ensure we get to the same page now.14:45
ianychoisdague, yep.. same page in the community is so important14:46
sdagueIs the policy about not translating log-level strings written down somewhere for the i18n team? So I can reference it in starting to delete the nova infrastructure?14:46
ianychoisdague, the message I have found as a written form is http://lists.openstack.org/pipermail/openstack-i18n/2016-November/002574.html - as Andreas already shared14:48
*** donghao has joined #openstack-dev14:48
ianychoisdague, now it is better for me to specify in I18n contributor guide: https://docs.openstack.org/developer/i18n/14:49
sdagueianychoi: yeh, I think in the contributor guide would be best14:49
sdaguethat feels more official than email14:49
ianychoisdague, and.. one question: are you familiar with oslo.i18n discussion: https://docs.openstack.org/developer/oslo.i18n/policy.html ?14:49
sdagueianychoi: I was not, but the most recent stuff seems to be Juno there14:50
ianychoisdague, since _LW, _LE are written in oslo.i18n, it would be nice for me to discuss with oslo team after specifying in I18n contributor guide?14:50
sdagueianychoi: maybe.14:51
sdagueAt some level, those are just infrastructure14:51
sdagueand oslo.i18n having that infrastructure allows different policies to exist14:51
sdaguehowever, the consuming of that by projects ends up being a different thing14:51
ianychoisdague, I see. Since AJaeger is not here but in #openstack-infra channel, I would like to move on #openstack-infra channel.14:52
*** makowals has quit IRC14:52
sdagueianychoi: ok14:52
sdaguehe mostly has been sending me to you :)14:52
*** limao_ has joined #openstack-dev14:52
sdaguebut I'm fine with that14:52
ianychoisdague, I see :)14:52
*** xyang1 has quit IRC14:52
*** limao has quit IRC14:53
*** spartacloud has joined #openstack-dev14:53
*** xyang1 has joined #openstack-dev14:54
*** jprovazn has joined #openstack-dev14:54
*** makowals has joined #openstack-dev14:56
*** breitz has joined #openstack-dev14:56
*** limao_ has quit IRC14:58
*** limao has joined #openstack-dev14:59
*** itzikb_ has joined #openstack-dev15:00
*** itzikb has quit IRC15:00
dstaneksdague: ianychoi: in keystone we had lots of issues with the _L* initially. i had to write some complicated hacking rules to help us out http://git.openstack.org/cgit/openstack/keystone/tree/keystone/tests/hacking/checks.py#n14915:01
*** jaypipes_ has joined #openstack-dev15:01
ianychoidstanek, for your case, supporing _LW _LI _LE _LC is too complicated from your implementation on such hacking rules?15:03
*** nplanel has quit IRC15:05
*** mriedem has joined #openstack-dev15:05
*** kriskend has joined #openstack-dev15:07
*** saibarspeis has quit IRC15:07
*** spartacloud is now known as zackf15:08
*** limao has quit IRC15:09
sdaguedstanek: we've got it as well15:10
*** limao has joined #openstack-dev15:10
*** lpetrut has joined #openstack-dev15:10
sdaguedstanek: but, the point being, the policy on i18n seems to have changed, which means we'd drop all those15:10
*** jethro7 has quit IRC15:12
dstaneksdague: that would be great since it's always a point of confusion15:13
sdaguedstanek: agreed15:13
dstanekianychoi: the hacking rules are there because people had such a hard time remembering to do it correctly15:14
*** zz_dimtruck is now known as dimtruck15:14
*** makowals has quit IRC15:14
dstanekianychoi: for example when the same message is logged and then used for the exception15:14
*** jethro7 has joined #openstack-dev15:14
*** baoli has quit IRC15:15
*** lucasxu has joined #openstack-dev15:16
*** itzikb has joined #openstack-dev15:17
*** makowals has joined #openstack-dev15:18
*** scottynomad has quit IRC15:19
*** itzikb_ has quit IRC15:20
*** david-lyle has quit IRC15:20
*** zaitcev has joined #openstack-dev15:20
*** limao has quit IRC15:21
*** limao has joined #openstack-dev15:21
*** morazi has quit IRC15:22
*** owalsh has quit IRC15:22
*** gongysh has quit IRC15:24
*** morazi has joined #openstack-dev15:24
*** aloga has quit IRC15:25
*** aloga has joined #openstack-dev15:25
*** limao has quit IRC15:26
*** erlon has joined #openstack-dev15:26
*** ericyoung has joined #openstack-dev15:26
*** bogdando has quit IRC15:28
*** slaweq has quit IRC15:29
*** kbringard has joined #openstack-dev15:29
*** bogdando has joined #openstack-dev15:29
*** itzikb has quit IRC15:29
*** dhajare has quit IRC15:31
*** owalsh has joined #openstack-dev15:32
*** hamzy_ is now known as hamzy15:33
*** amotoki has quit IRC15:33
*** mpotdar has joined #openstack-dev15:36
*** galstrom_zzz is now known as galstrom15:39
*** sree has quit IRC15:40
*** makowals_ has joined #openstack-dev15:42
*** svinota has quit IRC15:42
*** rraja has quit IRC15:43
*** makowals has quit IRC15:43
*** e0ne has quit IRC15:44
*** Leo_ has joined #openstack-dev15:44
*** rderose has quit IRC15:44
*** dizquierdo has joined #openstack-dev15:47
*** blues-man has joined #openstack-dev15:47
*** halves has joined #openstack-dev15:50
*** mhickey has joined #openstack-dev15:50
openstackgerritAndy McCrae proposed openstack/governance master: Add os_molteniron to OpenStack-Ansible  https://review.openstack.org/44200315:51
*** annegentle has joined #openstack-dev15:52
*** morazi has quit IRC15:52
*** gamado has quit IRC15:53
*** tremble has joined #openstack-dev15:53
*** tremble has quit IRC15:53
*** tremble has joined #openstack-dev15:53
*** bobmel has quit IRC15:54
jaypipes_dstanek, sdague, cdent: so I'm still on the fence about placement vs. keystone for storing limits. sdague, you're absolutely correct in your point about needing to send notifications about changes to the project hierarchy to the placement service if we decided to store limits in placement...15:57
*** xarses_ has joined #openstack-dev15:57
sdaguejaypipes_: I have a practical concern as well, beyond the separation of concerns15:58
*** annegentle has quit IRC15:59
sdaguethe placement team has a ton on it's plate, and reviews are slow. Unified limits in keystone wouldn't be going through that same bottleneck.15:59
jaypipes_sdague: fair enough.16:00
*** vnogin has quit IRC16:00
sdagueat least any time before placement is a dedicated project with a dedicated core team. The nova core team is stretched as it is without effectively making every other project need to push changes at Nova.16:01
jaypipes_sdague: ok16:01
*** yamahata has joined #openstack-dev16:02
*** hongbin has joined #openstack-dev16:03
*** morazi has joined #openstack-dev16:06
*** eezhova has quit IRC16:07
*** mpotdar has quit IRC16:07
*** annegentle has joined #openstack-dev16:07
*** tremble has quit IRC16:08
*** rcernin has quit IRC16:08
*** eezhova has joined #openstack-dev16:09
sdaguedstanek: I updated the model document and walked through the Stanek model for logic to update limits or validate usage violations16:10
*** tremble has joined #openstack-dev16:10
*** tremble has quit IRC16:10
*** tremble has joined #openstack-dev16:10
*** bogdando has quit IRC16:11
sdaguedstanek: I also just tried to update the terminology to match some of the other examples a bit, I don't think I changed anything substantial in the process16:12
sdaguehttps://review.openstack.org/#/c/441203/16:12
*** mpotdar has joined #openstack-dev16:12
*** pt_15 has joined #openstack-dev16:12
dstaneksdague: nice, i'll take a look. thx16:12
*** dsariel has quit IRC16:13
dstanekjaypipes_: with limits you must understand the hierarchy at all times. with the usage calculation you only need to know about it at the time you make the calculation.16:13
*** gamado has joined #openstack-dev16:13
*** e0ne has joined #openstack-dev16:13
dstaneksdague: jaypipes_: what happens now when a project is deleted? do the services watch for the notification to automatically remove resources or notify owner or anything like that?16:14
sdaguedstanek: no, they don't16:15
sdaguewe just get stale data16:15
*** baoli has joined #openstack-dev16:16
*** donghao has quit IRC16:16
jaypipes_dstanek: with limits, you only need to know the the limit of the parent, whether overbooking is allowed, and the sum of sibling limits.16:16
jaypipes_dstanek: you don't need to know the entire hierarchy to determine limits violations.16:16
sdaguejaypipes_: it all depends on the model you want to express16:17
*** david-lyle has joined #openstack-dev16:17
sdaguejaypipes_: so, perhaps we need to write down the Pipes model in here - https://review.openstack.org/#/c/441203/16:17
*** achampion has quit IRC16:17
jaypipes_dstanek: on the other hand, with usages, you *do* need to know the entire set of projects that are descendants of the project in question in order to get a sum of usage across all the children.16:17
sdaguejaypipes_: one of my take aways from the limits conversation is that overbooking means something16:17
sdagueit's not sufficient to explain the constraints on the limit system16:18
jaypipes_sdague: the only thing overbooking means is that the sum of limits for children can exceed the absolute limit of the parent.16:18
*** pnavarro has quit IRC16:18
sdaguejaypipes_: that requires all limits be explicit?16:19
jaypipes_sdague: *usage* on the other hand, is always absolute with regards to the individual project's limit. it may never exceed it.16:19
jaypipes_sdague: sorry, what do you mean by explicit?16:19
*** kobis has quit IRC16:19
sdaguejaypipes_: please take a look at this - http://docs-draft.openstack.org/03/441203/7/check/gate-keystone-specs-docs-ubuntu-xenial/7e38090//doc/build/html/specs/keystone/backlog/hierarchical-quota-scenarios.html16:19
*** sridharg has quit IRC16:20
sdagueI've been trying to diagram scenarios people have expressed, and give them explicit names16:20
*** tremble has quit IRC16:20
*** baoli has quit IRC16:20
*** donghao has joined #openstack-dev16:21
dstanekjaypipes_: hmmm...i was under the impression that overbooking mean that the sum of the child limits could be greater than the parent's limit, but usage couldn't exceed the parents16:21
sdagueagain, overbooking is not specific enough of a term16:21
*** david-lyle has quit IRC16:22
jaypipes_dstanek: yes, that's what I just said, no? :)16:22
jaypipes_sdague: reading the diagram page...16:23
dstanekjaypipes_: ah, yes. i see that now16:23
sdaguejaypipes_: because there is another dimension at least, which is how do you treat a project with nothing explicitly set on it16:24
*** tlaxkit has joined #openstack-dev16:24
dstanekjaypipes_: i was thinking that you could use the hierarchy information returned as a part of the limits to not need to understand the hierarchy yourself16:24
jaypipes_dstanek: well, placement service could theoretically not need to understand the hierarchy natively. it could, for instance, just ask Keystone "hey, gimme a list of all the project UUIDs that are 'below' this other project in a tree.16:26
*** donghao has quit IRC16:27
sdaguejaypipes_: so how does the idea you have in your head for how this works compare to the 3 hierarchical scenarios there? is it one of them, or a different one?16:28
jaypipes_sdague: still reading :) gimme a few more minutes...16:28
sdagueok, no prob16:28
sdaguealso, realize it's early and rough, so not everything is fleshed out16:29
jaypipes_sdague: when you say "assume only 1 API endpoint", I'm honestly a little confused.16:29
jaypipes_sdague: I don't understand what the API endpoint has to do with quotas?16:29
sdaguejaypipes_: part of the reason that we mentioned endpoint is that if you bring on a new version of Nova, and register that into your catalog, that may very well have new limits with it. So each nova endpoint instance may needed dedicated numbers.16:30
sdaguejaypipes_: anyway, I'm trying to get rid of everything that's orthoginal so we're working on 1 resource16:31
sdagueand seeing how it plays out16:31
sdagueso, honestly, don't get hung up on that, it can either be or not be a thing and doesn't impact much16:31
*** lucasxu has quit IRC16:32
jaypipes_k16:32
*** donghao has joined #openstack-dev16:33
*** amotoki has joined #openstack-dev16:34
*** donghao has quit IRC16:35
*** ptrlv has joined #openstack-dev16:35
*** donghao has joined #openstack-dev16:35
*** bogdando has joined #openstack-dev16:36
*** jathan has joined #openstack-dev16:37
*** ativelkov has quit IRC16:38
*** amotoki has quit IRC16:39
*** gamado has quit IRC16:40
*** ativelkov has joined #openstack-dev16:40
*** donghao has quit IRC16:40
*** dsariel has joined #openstack-dev16:40
*** e0ne has quit IRC16:41
*** eezhova has quit IRC16:41
*** salv-orlando has quit IRC16:41
*** e0ne has joined #openstack-dev16:45
*** yassine has quit IRC16:46
*** rderose has joined #openstack-dev16:47
*** yassine has joined #openstack-dev16:47
*** e0ne has quit IRC16:50
*** aludwar has quit IRC16:51
*** aludwar has joined #openstack-dev16:52
openstackgerritJulie Pichon proposed openstack/project-team-guide master: Add tips for writing good release notes  https://review.openstack.org/44203916:55
*** abregman|mtg has quit IRC16:55
*** ccneill has joined #openstack-dev16:56
*** sshnaidm is now known as sshnaidm|afk16:58
*** achampion has joined #openstack-dev16:59
*** _cjones_ has joined #openstack-dev16:59
*** takamatsu_ has joined #openstack-dev17:01
*** aasthad has joined #openstack-dev17:01
*** takamatsu is now known as Guest5789317:01
*** takamatsu_ is now known as takamatsu17:02
*** ayogi has joined #openstack-dev17:02
*** Guest57893 has quit IRC17:03
*** vnogin has joined #openstack-dev17:04
*** k4n0 has quit IRC17:04
*** mgagne_ has quit IRC17:05
*** mgagne_ has joined #openstack-dev17:05
*** jaypipes has quit IRC17:05
*** jaypipes_ is now known as jaypipes17:05
*** vnogin has quit IRC17:07
*** vnogin has joined #openstack-dev17:07
*** dosaboy_ is now known as dosaboy17:09
*** tlaxkit has quit IRC17:09
*** slaweq_ has quit IRC17:09
*** tesseract has quit IRC17:10
*** slaweq has joined #openstack-dev17:10
*** ayogi has quit IRC17:11
*** ygbo has quit IRC17:11
*** ayogi has joined #openstack-dev17:13
*** vhosakot has joined #openstack-dev17:15
*** ekuris has quit IRC17:16
*** david-lyle has joined #openstack-dev17:18
*** jdandrea has quit IRC17:19
*** jathan has quit IRC17:21
*** david-lyle has quit IRC17:24
*** eroux has joined #openstack-dev17:26
*** rcernin has joined #openstack-dev17:27
*** hseipp has quit IRC17:27
*** dizquierdo has quit IRC17:28
*** david-lyle has joined #openstack-dev17:30
*** yassine has quit IRC17:32
*** lucasxu has joined #openstack-dev17:32
*** jpich has quit IRC17:33
*** vhosakot has quit IRC17:35
*** akrivoka has quit IRC17:35
*** eezhova has joined #openstack-dev17:36
*** akrivoka has joined #openstack-dev17:37
*** mhickey has quit IRC17:38
*** mpotdar has quit IRC17:38
*** jathan has joined #openstack-dev17:40
openstackgerritMichal Jastrzebski (inc0) proposed openstack/governance master: Apply for stable:follows-policy for Kolla  https://review.openstack.org/34645517:41
*** andreww has joined #openstack-dev17:43
*** armax has joined #openstack-dev17:45
*** xarses_ has quit IRC17:46
*** athomas has quit IRC17:47
*** mvk has quit IRC17:49
*** eroux has quit IRC17:50
*** ltomasbo is now known as ltomasbo|away17:52
*** bogdando has quit IRC17:52
*** annegentle has quit IRC17:52
sdaguejohnthetubaguy: I did kind of the next level drill down on the Stanek model, going to get up from the computer for a bit, if you think working through that on the Garbutt model would be useful, I can - http://docs-draft.openstack.org/03/441203/7/check/gate-keystone-specs-docs-ubuntu-xenial/7e38090//doc/build/html/specs/keystone/backlog/hierarchical-quota-scenarios.html17:52
*** snica is now known as snica_away17:52
*** mhickey has joined #openstack-dev17:53
johnthetubaguysdague: I should take a look, will be tomorrow though I think17:54
sdagueok, fair enough17:55
*** beekneemech is now known as bnemec17:56
*** halves has quit IRC17:57
*** mhickey has quit IRC17:57
*** ociuhandu has quit IRC18:01
*** iyamahat has joined #openstack-dev18:03
*** kbringard1 has joined #openstack-dev18:03
*** kbringard has quit IRC18:03
*** kbringard has joined #openstack-dev18:04
*** mhickey has joined #openstack-dev18:04
*** radhikam has joined #openstack-dev18:04
*** kbringard2 has joined #openstack-dev18:04
*** kbringard1 has quit IRC18:05
*** jdandrea has joined #openstack-dev18:06
*** kbringard has quit IRC18:09
*** blues-man has quit IRC18:09
*** shardy has quit IRC18:11
*** owalsh has quit IRC18:14
*** halves has joined #openstack-dev18:14
*** ksobkowiak has joined #openstack-dev18:16
*** owalsh has joined #openstack-dev18:17
*** sreenath has quit IRC18:18
*** wootehfoot has joined #openstack-dev18:19
*** lucasagomes is now known as lucas-afk18:20
*** kbringard2 has quit IRC18:22
*** kbringard has joined #openstack-dev18:23
*** shardy has joined #openstack-dev18:24
*** athomas has joined #openstack-dev18:27
*** jdandrea has quit IRC18:27
*** eezhova has quit IRC18:28
*** e0ne has joined #openstack-dev18:29
*** mvk has joined #openstack-dev18:31
*** ayogi has quit IRC18:33
*** baoli has joined #openstack-dev18:34
*** eroux has joined #openstack-dev18:34
*** dtantsur is now known as dtantsur|afk18:34
*** amotoki has joined #openstack-dev18:36
*** jdandrea has joined #openstack-dev18:39
*** jcoufal has quit IRC18:40
*** amotoki has quit IRC18:41
*** ijw has joined #openstack-dev18:43
*** diablo_rojo has joined #openstack-dev18:45
*** jcoufal has joined #openstack-dev18:46
*** kbringard1 has joined #openstack-dev18:47
*** vsaienko has joined #openstack-dev18:47
*** kbringard has quit IRC18:49
vsaienkodevstack core please review https://review.openstack.org/#/c/440303 need for ironic multinode grenade18:49
*** Guest64317 has joined #openstack-dev18:50
*** ayogi has joined #openstack-dev18:50
vsaienkothe patch updates enable_plugin to ignore second plugin enablement which is caused by unknown issue, event when it is added to local.conf only once18:51
sdaguevsaienko: can you show me a job where that happens?18:52
vsaienkosdague there is an example http://logs.openstack.org/57/436957/10/experimental/gate-grenade-dsvm-ironic-multinode-multitenant-ubuntu-xenial-nv/56b2faa/logs/grenade.sh.txt.gz#_2017-03-02_09_58_21_58318:54
*** akrivoka has quit IRC18:54
*** lucasxu has quit IRC18:55
vsaienkosdague the job failed on save_mysql_db() I don't understand how DEVSTACK_PLUGINS may be set when _DEVSTACK_STACKRC not http://logs.openstack.org/57/436957/10/experimental/gate-grenade-dsvm-ironic-multinode-multitenant-ubuntu-xenial-nv/56b2faa/logs/grenade.sh.txt.gz#_2017-03-02_09_58_19_68818:56
*** owalsh is now known as owalsh-brb18:56
*** Guest64317 has quit IRC18:56
*** kbringard has joined #openstack-dev18:57
*** baoli has quit IRC18:58
*** kbringard1 has quit IRC19:01
*** ociuhandu has joined #openstack-dev19:02
*** dschultz has joined #openstack-dev19:02
*** ckonstanski has joined #openstack-dev19:04
*** pcaruana has quit IRC19:04
sdaguevsaienko: so the thing that's actually dying is the trick to pull out the MYSQL pwd19:05
vsaienkosdague yes the error comes from that call but I don't understand what causes it19:06
sdaguevsaienko: I think this might fix it https://review.openstack.org/44212119:07
*** electrofelix has quit IRC19:08
sdagueI think the variable was inheriting from the parent19:08
*** akrivoka has joined #openstack-dev19:09
*** baoli has joined #openstack-dev19:09
vsaienkosdague let me check if that works I will let you know19:09
vsaienkosdague thanks!19:09
sdaguevsaienko: no prob19:09
*** shardy has quit IRC19:11
*** vsaienko has quit IRC19:14
*** halprin has quit IRC19:14
*** bobmel has joined #openstack-dev19:14
*** pcaruana has joined #openstack-dev19:15
openstackgerritMerged openstack/project-team-guide master: Add tips for writing good release notes  https://review.openstack.org/44203919:17
*** bobmel has quit IRC19:20
*** eglynn has quit IRC19:20
*** yee379 has quit IRC19:21
*** yee379 has joined #openstack-dev19:21
*** eroux has quit IRC19:21
*** egallen has quit IRC19:22
*** egallen has joined #openstack-dev19:22
*** salv-orlando has joined #openstack-dev19:24
openstackgerritJohn Garbutt proposed openstack/governance master: Describe what upstream support means  https://review.openstack.org/44060119:25
openstackgerritJohn Garbutt proposed openstack/governance master: Describe what upstream support means  https://review.openstack.org/44060119:25
*** eroux has joined #openstack-dev19:25
*** basilAB_ has joined #openstack-dev19:26
*** egallen has quit IRC19:27
*** baoli has quit IRC19:29
*** vsaienko has joined #openstack-dev19:33
*** Werz44 has quit IRC19:33
*** lpetrut has quit IRC19:34
*** lpetrut has joined #openstack-dev19:34
*** vhosakot has joined #openstack-dev19:34
*** kbringard1 has joined #openstack-dev19:34
*** ddyer has quit IRC19:36
*** kbringard has quit IRC19:37
jaypipeslbragstad: what's HMT?19:38
lbragstadjaypipes hierarchical multi tenancy19:39
jaypipesah. fancy :)19:39
lbragstadjaypipes I *always* misspell hierarchical so I just use HMT ;)19:39
*** kbringard1 has quit IRC19:39
*** kbringard has joined #openstack-dev19:39
jaypipeslbragstad: :)19:39
*** kbringard1 has joined #openstack-dev19:40
*** ddyer has joined #openstack-dev19:40
*** fragatin_ has quit IRC19:42
*** kbringard has quit IRC19:44
*** markvoelker_ has quit IRC19:47
*** vhosakot has quit IRC19:48
*** ociuhandu has quit IRC19:48
*** Rockyg has joined #openstack-dev19:50
*** baoli has joined #openstack-dev19:50
*** baoli has quit IRC19:50
*** gszasz has quit IRC19:53
*** gouthamr has quit IRC19:54
*** kbringard1 has quit IRC19:54
*** galstrom is now known as galstrom_zzz19:54
*** kbringard1 has joined #openstack-dev19:55
lbragstadsdague looking at one of the examples in this section - http://docs-draft.openstack.org/03/441203/7/check/gate-keystone-specs-docs-ubuntu-xenial/7e38090//doc/build/html/specs/keystone/backlog/hierarchical-quota-scenarios.html#strict-hierarchy-default-closed19:55
lbragstadthe `UPDATE LIMIT on B to 10 followed by UPDATE LIMIT on C to 5` should technically fail the second rule, right?19:55
*** claudiub|2 has joined #openstack-dev19:55
lbragstadalso, does the second rule need to be written as "The sum of all children is must be <= the parent."19:56
*** dsariel has quit IRC19:56
*** claudiub has quit IRC19:58
*** salv-orlando has quit IRC19:58
*** annegentle has joined #openstack-dev19:59
*** ayogi has quit IRC20:00
*** bobmel has joined #openstack-dev20:01
*** kbringard has joined #openstack-dev20:02
*** kbringard1 has quit IRC20:02
*** kbringard1 has joined #openstack-dev20:02
*** kbringard2 has joined #openstack-dev20:05
*** kbringard2 has quit IRC20:05
*** kbringard2 has joined #openstack-dev20:05
*** bobmel has quit IRC20:06
*** ijw_ has joined #openstack-dev20:06
*** kbringard1 has quit IRC20:06
*** kbringard has quit IRC20:06
*** bobmel has joined #openstack-dev20:07
*** kbringard has joined #openstack-dev20:08
*** kbringard has quit IRC20:09
*** ijw has quit IRC20:09
*** kbringard2 has quit IRC20:10
*** ijw has joined #openstack-dev20:11
*** galstrom_zzz is now known as galstrom20:11
lbragstadI'm also wondering if it makes sense to have a section dedicated to the different failure scenarios20:13
*** owalsh-brb is now known as owalsh20:13
*** gouthamr has joined #openstack-dev20:14
*** e0ne has quit IRC20:14
*** ijw_ has quit IRC20:14
*** achampion has quit IRC20:20
*** gmoro has quit IRC20:20
*** achampion has joined #openstack-dev20:21
*** Jack_I has quit IRC20:22
sdaguelbragstad: let me look20:22
sdaguelbragstad: ah, <= is what it should be20:23
sdagueyeh, assume I'm going to typo that all the time :)20:23
lbragstadsdague ok - I have a comment in draft state20:23
sdagueso, assuming that's updated, that should all be fine, right?20:24
*** markvoelker has joined #openstack-dev20:24
sdagueI didn't fully flush out either that one or the garbutt one20:24
lbragstadsdague that model?20:24
sdaguelbragstad: yeh20:24
lbragstadsdague i think it's going to really depend on how complicated these are in real deployments20:24
sdaguelbragstad: sure, however we should be able to map out their edge scenarios right?20:25
*** achampion has quit IRC20:25
lbragstadsdague right20:25
lbragstadthe `UPDATE LIMIT on B to 10 followed by UPDATE LIMIT on C to 5` would fail, too?20:25
lbragstadin that specific scenario?20:26
*** vills has joined #openstack-dev20:26
sdaguelbragstad: why?20:27
*** donghao has joined #openstack-dev20:27
lbragstadsdague the way I read the second rule of that model was if the sum of all children exceed the limit of A, then the limit update should fail20:27
*** ociuhandu has joined #openstack-dev20:27
lbragstadso limit(A) >= limit(B) + limit(C)20:28
*** mhickey has quit IRC20:28
sdaguelbragstad: I guess it should be direct children20:28
sdagueI was thinking of it as direct children20:28
sdaguebut, I think you found a brand new way we could handle that20:28
lbragstadif we did limit(A) >= limit(B) + limit(C) that would represent the most strict model possible, right?20:29
sdagueyeh, but I think the implications of that are even more confusing20:29
*** achampion has joined #openstack-dev20:30
lbragstadsdague you mean applying it to an existing hierarchy?20:30
sdaguebecause A (10), B(6), C(4), D(0)20:30
sdagueset limit D == 220:30
sdaguepasses B check, fails A check?20:30
lbragstadyeah - that would break20:30
lbragstadthinking about it in the way I interpreted the rules of that model (which could totally be wrong)20:31
*** fragatina has joined #openstack-dev20:31
sdagueright, so, I think we'll have models we reject out of hand because they make too little sense to operators for "project D is out of quota, bump it"20:32
lbragstadright20:32
lbragstadsdague and you would consider a super strict model like that to be too restrictive to be useful, right?20:32
*** slaweq has quit IRC20:33
*** donghao has quit IRC20:33
sdagueyeh, I would call that the Exit Ed Model, because I think that it's not possible for an admin to figure out how to bump a limit correctly20:33
*** halves has quit IRC20:34
lbragstadsdague yeah - that would be like trying to update the quota locally only to see if fail, then have to update the parent quota only to see it fail, then update the grandparent quota only to see it fail, etc...20:35
lbragstadall the way up the tree (in the worst case scenario where all allocations are maxed out)20:35
lbragstadwhich i would be ok filing in the poor user experience catagory20:36
lbragstadcategory*20:36
sdagueyeh, lbragstad have more things to put in, I'll update and throw a couple more of these in there20:37
*** amotoki has joined #openstack-dev20:37
*** slaweq has joined #openstack-dev20:37
*** ijw_ has joined #openstack-dev20:38
lbragstadsdague I would think that would help us filter out the models that we don't want20:38
lbragstadanother thing I was thinking about was the classification of quota errors20:40
lbragstaddo we want a dedicated place to identify what those errors look like and what they should say, or is that too implementation specific?20:40
lbragstad(i.e. updating the limit of project D failed because project C has a limit of X)20:40
*** ijw has quit IRC20:41
*** amotoki has quit IRC20:42
sdaguelbragstad: I think we want whatever collateral we need before starting to pick models that will get implemented.20:45
lbragstadsdague keystone has had discussions about doing specific error codes (independent of HTTP codes obviously) but I could see those applying here20:46
sdagueyeh, I think once we get there, being clear with errors is going to be important20:47
lbragstadsdague ++20:47
lbragstadthinking about all the different error paths from the opaque view of a user is interesting20:47
lbragstadbecause typically, I'd just copy/paste something into a ticket for support to look into right?20:47
*** dsariel has joined #openstack-dev20:49
*** bobmel has quit IRC20:50
*** bobmel has joined #openstack-dev20:50
lbragstadputting myself into a support role, getting a "unable to do X because you're over quota" isn't very helpful, but maybe if we included classes for "sibliing over quota", "child over quota", "parent over quota" that'd make things a little easier for support to track down?20:51
*** vhosakot has joined #openstack-dev20:52
*** yamahata has quit IRC20:52
*** iyamahat has quit IRC20:52
*** salv-orlando has joined #openstack-dev20:53
sdaguelbragstad: so I think the end user creating an instance (or whatever) is going to get a pretty generic, "over limit for Memory"20:54
sdaguewhich they'd put in a ticket.20:54
Rockyglbragstad, ++  Definitely need to include type of over quotq20:54
sdaguebut the operator should be able to figure out a resolution without getting eaten by a grue20:54
annegentlesdague snerk :)20:55
*** zz_pwnall138 is now known as pwnall133720:55
*** iyamahat has joined #openstack-dev20:56
sdaguelbragstad: ok, pushed with 2 more pre rejected scenarios20:56
*** jcoufal_ has joined #openstack-dev20:57
*** hichihara has joined #openstack-dev20:58
*** athomas has quit IRC20:58
*** ericyoung has quit IRC20:58
*** wootehfoot has quit IRC20:59
*** ociuhandu has quit IRC21:00
*** jamielennox|away is now known as jamielennox21:00
lbragstadsdague ok - so maybe that sounds like it can be solved by better notifications?21:00
*** jcoufal has quit IRC21:00
lbragstador logging?21:01
*** rfolco has quit IRC21:01
*** TxGirlGeek has joined #openstack-dev21:02
*** kriskend has quit IRC21:02
*** owalsh_ has joined #openstack-dev21:03
*** lucas-afk has quit IRC21:04
*** rfolco has joined #openstack-dev21:04
*** rfolco has quit IRC21:04
*** k4n0 has joined #openstack-dev21:05
*** owalsh has quit IRC21:06
*** lucasxu has joined #openstack-dev21:06
*** yamahata has joined #openstack-dev21:06
*** xarses_ has joined #openstack-dev21:06
*** lucasagomes has joined #openstack-dev21:07
*** lpetrut has quit IRC21:08
*** andreww has quit IRC21:10
*** ShaneDavidson has joined #openstack-dev21:11
sdaguemaybe, I think it's got to be over the REST api though21:12
*** jdandrea has quit IRC21:13
*** pcaruana has quit IRC21:13
*** pabelanger has quit IRC21:14
*** pabelanger has joined #openstack-dev21:14
-openstackstatus- NOTICE: restarting gerrit to address performance problems21:15
*** jprovazn has quit IRC21:16
*** ccneill has quit IRC21:16
*** iyamahat has quit IRC21:17
*** kriskend has joined #openstack-dev21:17
lbragstadsdague the cause of the quota or limit failure has to be over the REST api?21:18
*** ccneill has joined #openstack-dev21:18
*** yamahata has quit IRC21:19
*** owalsh_ is now known as owalsh21:19
sdaguea user should be told what resource they exceeded, so they can either free up enough space, or write a good ticket21:19
lbragstadoh - right21:20
sdaguebecause the person solving that is going to do that over the keystone api to update limits, the operator should get that message during their call if they can't change that21:20
*** TxGirlGeek has quit IRC21:21
lbragstadif a user can't do something in a project because of a sibling project or a parent project's limits or usage, how much of that information should be in the response to the user?21:21
sdaguelbragstad: I think by default none21:22
sdaguethere are some information leaks there that are weird21:22
*** eroux has quit IRC21:23
sdaguebut, I also think we have time to figure that out, as that won't be dealt with until Q at least21:23
lbragstadyeah - that makes sense21:24
*** kgiusti has quit IRC21:27
*** TxGirlGeek has joined #openstack-dev21:29
*** akrivoka has quit IRC21:30
*** iyamahat has joined #openstack-dev21:30
*** vsaienko has quit IRC21:32
*** baoli has joined #openstack-dev21:33
*** TxGirlGeek has quit IRC21:34
*** nplanel has joined #openstack-dev21:34
lbragstaddstanek sdague so i'm not sure I completely understand the usage of effective limits in the stanek model21:35
*** GichukiMaina[m] has quit IRC21:35
lbragstadthe effective limit seems like something that only ever matters at the very top of the hierarchy21:36
*** TxGirlGeek has joined #openstack-dev21:36
mriedemjbryce: will there be time allocated at the summit for vertical projects to have sessions like the traditional design summit, or at least meetup-style for the devs that will be there? or is it all forum all the time meaning talking about new features in the latest release, and getting feedback and requirements from users/operators/product people?21:36
lbragstadespecially if when you change the effective limit of a project, it cascades through the entire tree if there are no violations21:36
*** aysyd has quit IRC21:37
*** vsaienko has joined #openstack-dev21:39
*** TxGirlGeek has quit IRC21:39
dstaneklbragstad: in that model i think it is just showing you what is possible in that particular part of the tree without looking at usage21:39
*** TxGirlGeek has joined #openstack-dev21:40
lbragstaddstanek in the case of D, it has a limit of -1 but an el=1021:40
lbragstadthat's technically saying "D is unlimited, but only up to 10"21:40
dstaneklbragstad: in the first example, C has a limit of 5 since that was explicitly set. D has a limit of 10 because of the rule 'If a limit is not explicitly set for a project it is allowed to comsume as much as possible until the parent’s limit is reached'21:41
*** GichukiMaina[m] has joined #openstack-dev21:41
lbragstadright?21:41
dstaneklbragstad: basically21:41
jbrycemriedem: i need to check. i know we were going to have some space available, but not scheduled/managed the way the design summit used to be21:41
lbragstaddstanek is there ever a reason to not use the effective limit all the time then?21:41
dstaneki tried to keep the rules simple, but it still allows for some interesting usage21:41
dstaneklbragstad: what do you mean by that?21:42
lbragstaddstanek i would set the limit of A to 1021:42
*** jkilpatr has joined #openstack-dev21:42
lbragstaddstanek because I know everything under A doesn't equal 1021:42
dstanekthe usage check will have to do two things look to see if the project limit is exceeded and if then make sure the parent's project limit isn't exceeded either21:42
jbrycemriedem: before i go talk to the team, maybe it would be helpful too to hear what you'd like to see now that we've seen what the ptg is like and what kind of collaborative time you still could use21:42
lbragstaddstanek isn't that similar to the Exit Ed model?21:43
lbragstadhttp://docs-draft.openstack.org/03/441203/8/check/gate-keystone-specs-docs-ubuntu-xenial/923ac60//doc/build/html/specs/keystone/backlog/hierarchical-quota-scenarios.html#exit-ed-model21:43
*** TxGirlGeek has quit IRC21:43
*** TxGirlGeek has joined #openstack-dev21:43
dansmithjbryce: so where will things described on this page happen? http://superuser.openstack.org/articles/openstack-forum/21:44
mriedemjbryce: i'm mostly wondering if there will be time for the nova team to be going over progress and talking through major dev issues in person at that point in the release (like we used to have with midcycles),21:44
dansmithjbryce: things like "long term planning" and "cross-project discussions"21:44
mriedemjbryce: and if it's useful to have nova devs there who aren't necessarily cores or giving talks21:44
dstaneklbragstad: no. iiuc, that model makes you list out explicit values all along the tree. the -1 in my model does not21:44
lbragstaddstanek ah - right21:45
dstaneklbragstad: so there is less tree balancing21:45
*** ckonstan` has joined #openstack-dev21:45
dansmithjbryce: those are activities that are good to have devs in, but we kinda need to know what the format and schedule will look like to know what we can/will discuss there, and thus who needs to go21:45
*** TxGirlGeek has quit IRC21:45
lbragstaddstanek but there is tree balancing in that the limit at the top of the tree *must* encompass the useage/limits of the entire tree21:45
lbragstadotherwise it won't apply21:45
*** TxGirlGeek has joined #openstack-dev21:46
dstaneklbragstad: yep, and that will be the same in all scenarios21:46
*** ckonstanski has quit IRC21:46
dstanekif i say project X can only have 10 resources then they can't game the system by making sub-projects allowed to have more21:46
lbragstaddstanek right - but isn't that the same thing in the exit ed model because the -1 isn't really honored, right?21:47
dstaneklbragstad: there may be a bit of a race between some of the scenarios where you need 1 more thing and the admin raises the limit of a parent, but someone else gets that thing21:47
lbragstadonce the effective limit is set at the top of the tree, the rest of the tree must comply to it even if they have -1 set21:48
*** jkilpatr has quit IRC21:48
*** yamahata has joined #openstack-dev21:48
dstaneklbragstad: i take 'Because the constraints are applied at all levels in the node' to mean the issue of increasing A so that you can increase B to finally increase the limit of C21:48
dstanekin my model you increase A21:48
*** TxGirlGeek has quit IRC21:49
lbragstaddstanek and it will increase B and C automatically, but it still must be done21:49
lbragstaddstanek just trying to walk through the cases and what makes it different21:49
dstaneklbragstad: yes, but that is always the case. i think Ed was rejected because you would have to manually jigger with things21:49
*** ociuhandu has joined #openstack-dev21:49
lbragstaddstanek yeah21:50
dstaneklbragstad: in all honestly i only looked at the rejected cases today and haven't thought too much about them21:50
lbragstaddstanek they are pretty fresh21:50
*** ansmith has quit IRC21:50
lbragstaddstanek so the Stanek model is a slightly less strict version of the Exit Ed model with a few more assumptions21:50
dstaneklbragstad: my case was just me having an engineer moment and wanting to solve the problem at PTG. i wasn't really aware of any other solutions until after that model was in my head21:51
jbrycedansmith: there are rooms for those topics/categories. the schedule and specific content for it is being set through those etherpad links that have been going out to the mailing lists21:51
lbragstaddstanek yeah - that makes sense21:51
dansmithjbryce: okay21:52
*** jkilpatr has joined #openstack-dev21:52
* mriedem hasn't seen emails about scheduling sessions21:52
lbragstaddstanek for some reason I'm trying to categorize these along a spectrum of strictness21:52
dstaneklbragstad: maybe...or maybe the inverse of the Garbutt model (but i don't entirely understand that one)21:52
dansmithmriedem: jbryce: me either, I was just looking... can you help with a subject to search for?21:52
mriedemunless they aren't in the -dev list21:53
jbrycedansmith, mriedem: EmilienM sent the first one out on 3/1. Subject: "[openstack-dev] [all] Forum Brainstorming - Boston 2017"21:53
lbragstaddstanek i've spent that last hour or two going through each trying to figure out the pro/cons of each and what makes them different21:53
dansmithjbryce: ah, okay I expected that was more targeted, I see that one21:53
*** vsaienko has quit IRC21:53
dstaneklbragstad: my perspective on the solution comes from supporting a reseller model21:53
dstaneklbragstad: a variation could also be that the explicit number set is guaranteed and the -1 nodes can just take up the rest21:54
*** ociuhandu has quit IRC21:54
lbragstadright21:55
*** ijw_ has quit IRC21:55
dansmithmriedem: added one for us21:55
* mriedem is still looking21:55
lbragstaddstanek that's interesting because depending on the limits of a parent (if there is a parent) then the -1 doesn't really make much sense21:55
mriedemhttp://lists.openstack.org/pipermail/openstack-dev/2017-March/113115.html21:56
lbragstaddstanek and I'd be in favor of having each project set a local limit and an effective limit21:56
mriedemok, now why can't i find it in my mail client...21:56
EmilienMmriedem: you blocked me? :-)21:56
jbrycedansmith, mriedem: yeah the etherpads are a little thin right now, so feel free to chime in. it's the first time for this part of the event and i'm sure we'll have things to improve. i'll also check to see if we have some ad-hoc rooms that can be scheduled for projects to do mid-cycle type meetings21:56
*** kriskend has quit IRC21:57
dansmithjbryce: yeah, it's cool, it's just that we're two months out and in the prime travel-approval window, so we kinda need to know what so we know who21:57
*** wootehfoot has joined #openstack-dev21:58
*** jkilpatr has quit IRC21:58
*** hichihara has quit IRC21:59
*** vsaienko has joined #openstack-dev21:59
*** bobmel has quit IRC22:00
dstaneklbragstad: well, what about multiple siblings? that's where the -1 is powerful22:00
*** jkilpatr_ has joined #openstack-dev22:01
lbragstaddstanek aha right - because you can have two siblings with -1 and they end up flighting for limits until all parent limits are used, right?22:02
*** takamatsu has quit IRC22:02
jbrycedansmith: ok. understood22:02
mriedemEmilienM: ha it actually was in my spam folder22:03
mriedemwtf22:03
mriedemblame google22:03
dstaneklbragstad: yes22:04
*** vhosakot has quit IRC22:04
dstaneklbragstad: that gives you a lot of flexibility22:04
EmilienMmriedem: seriously?22:04
lbragstaddstanek ++22:04
mriedemEmilienM: yeah22:04
EmilienMmriedem: I use gmail (redhat)22:04
lbragstaddstanek alright - i'm working on a slightly modified Stanek model22:04
*** thorst has quit IRC22:04
EmilienMand you too, that's weird22:04
*** gouthamr has quit IRC22:05
mriedemthese emails calling me "beloved" are spam though, i think...let me click this link22:05
*** thorst has joined #openstack-dev22:05
jbrycedon't click the link unless you want to have millions transferred directly to your account22:06
mriedemi could use some millinos22:06
mriedem*millions22:06
EmilienMok that's why it takes so long22:07
dstaneklbragstad: i mentioned it here a few times so i dedicde to add a comment https://review.openstack.org/#/c/441203/822:09
dstaneklbragstad: how are you thinking it would work?22:09
*** thorst has quit IRC22:09
lbragstaddstanek i think the only thing I don't like is the fact that we reserve -1 to denote unlimited22:10
lbragstadbut in certain cases, that won't make sense22:10
*** paramite has quit IRC22:10
lbragstadlike anytime there is a child project who's parent project has a limit set that isn't -122:10
lbragstadso maybe there is a way to mix the unlimited cases we want with effective limits and local limits22:11
* lbragstad thinks there are way too many limit terms now22:11
*** owalsh is now known as owalsh-afk22:11
dstaneklbragstad: that is just for show. in implementation there would literally be no value in the database22:12
lbragstaddstanek oh22:12
lbragstaddstanek i think there are some implementations (cinder maybe) that use -1 today22:13
dstaneklbragstad: we have a tree in the keystone DB already. i was anticipating a flat table like (ID, PROJECT_ID, RESOURCE_TYPE, VALUE)22:13
dstaneklbragstad: here is my original attempt to explain https://gist.github.com/dstanek/a8a343a3ab5ad4ad0862e3e1be33217322:14
*** jcoufal_ has quit IRC22:14
dstanekthat shows more of the implementation details22:14
dstanekin the review i wrote 'not set', but i left -1 in the example because i thought it was easier to see and more pleasant than None22:14
*** kriskend has joined #openstack-dev22:16
*** kylek3h has quit IRC22:16
*** vsaienko has quit IRC22:18
*** ZZelle has joined #openstack-dev22:19
*** steveg_afk has quit IRC22:20
*** john-davidge has quit IRC22:22
*** owalsh has joined #openstack-dev22:22
*** owalsh-afk has quit IRC22:22
*** adriant has joined #openstack-dev22:22
*** vsaienko has joined #openstack-dev22:22
*** baoli has quit IRC22:23
*** ijw has joined #openstack-dev22:24
*** gouthamr has joined #openstack-dev22:24
*** jkilpatr_ has quit IRC22:24
*** morazi has quit IRC22:24
*** limao has joined #openstack-dev22:25
*** limao_ has joined #openstack-dev22:27
*** lucasxu has quit IRC22:28
*** jkilpatr_ has joined #openstack-dev22:28
*** ihrachys has quit IRC22:29
*** ijw has quit IRC22:29
*** dimtruck is now known as zz_dimtruck22:29
*** limao has quit IRC22:30
*** vsaienko has quit IRC22:31
lbragstaddstanek yeah - i'm tinkering with this locally but I think it -1 approach you have in your examples makes more sense22:33
*** jkilpatr_ has quit IRC22:34
lbragstadeven though the -1 can be misleading depending on the limits imposed by the parents, i think that is easier than orchestrating logic between local limits, effective limits, and unlimited22:34
sdaguedstanek / lbragstad so I think the thing is that's one of the dimensions about what makes the models different. Does unset mean 0 or unlimitted. Unlimitted is actually easy to reason about, but it means the usage count needs the whole tree.22:34
sdaguelbragstad: if you think there is a better way to express things, that would be cool.22:35
thingeedhellmann: wrt centralizing the support matrix work https://review.openstack.org/#/c/33002722:35
*** ijw has joined #openstack-dev22:35
lbragstadsdague the only part i was struggling with was the fact the unlimited wasn't really unlimited in all cases22:36
sdaguelbragstad: I invented effective limit there just to make it easy to see what the limit enforcing would end up being. It could be cached in the db on limit changes, or computed on the fly when queried22:36
sdaguelbragstad: right, it's only unlimitted if it's unlimitted to the top of the tree22:36
lbragstadright - in the truest sense22:36
dhellmannthingee : abandoned :-(22:36
sdaguebecause the rule about being no greater than your parent applies22:36
lbragstadyep22:36
thingeedhellmann: there is a trend with projects going with ini files http://lists.openstack.org/pipermail/openstack-dev/2017-March/113173.html22:36
lbragstadand i think that's totally valid22:36
dstaneklbragstad: in my mind unlimited is never unlimited. unlimited up to the parent limit. even at the root you have a limit because of the hardware22:37
thingeedhellmann: I'd like to pick this up. But wanted to discuss the ini part22:37
lbragstadsure22:37
*** vsaienko has joined #openstack-dev22:37
dhellmannthingee : ugh, what a horrible file format for data like this. but if that's what people are doing...22:37
*** jkilpatr_ has joined #openstack-dev22:37
*** limao_ has quit IRC22:37
sdaguethingee / dhellmann there is a reason22:37
sdagueI complained originally with the hypervisor feature matrix doing that22:37
dhellmannthingee : it will make it impossible to use something like sphinxcontrib-datatemplates and require writing custom data handling22:37
dhellmannsdague : oh?22:38
*** limao has joined #openstack-dev22:38
*** amotoki has joined #openstack-dev22:38
lbragstaddstanek sdague that's what i was trying to tinker with locally - what if we could use limits and "local limits" to give us the same freedom without having to use "unlimited"22:38
*** ijw has quit IRC22:38
sdagueand danpb did a quick prototype of what the data looked like in json or yaml22:38
dstaneklbragstad: i'm quitting working in a few so i can work on some volunteering stuff. let me know if you want to vidyo discuss at all22:38
sdagueand it honestly was worse22:38
*** ijw has joined #openstack-dev22:38
lbragstaddstanek sounds good22:38
sdagueso we went forward with least worst22:38
dhellmannsdague : ok22:39
lbragstadsdague dstanek but it is safe to assume we will always need a case where the root project requires all things (i.e. is unlimited)?22:39
sdaguelbragstad: I think that's a safe assumption22:40
lbragstadok22:40
sdagueunlimitted at the top always needs to be a supported model22:40
lbragstadok - cool, i would agree with that22:40
sdagueI mean, you could declare models where that wasn't ok, but I think we'd reject them22:40
lbragstadbut locally when i played with models for it, it turns into a weird abomination of local limit, project limit, and unlimited22:40
lbragstadyeah - i can't think of a case were we'd not want that22:41
thingeesmcginnis: not sure if you had a chance to read this http://lists.openstack.org/pipermail/openstack-dev/2017-March/113173.html22:41
thingeesmcginnis: would like to work with Karthik on this22:42
*** amotoki has quit IRC22:42
*** vhosakot has joined #openstack-dev22:43
lbragstadso - based on that, then i think it would also be safe to say that once a project flips its limit from -1 to something else, then all children in that tree have to do the same22:44
sdaguedhellmann: I think custom data handling in a case like this is fine. If you want the outputs to be similar, you kind of want to box things in to a feature declaration format and not have people writing the presentation layer like in sphinxcontrib-datatemplates.22:45
dhellmannsdague : it's possible to put a template in a theme and share it, but since I'm not actually doing the work I'll leave those sorts of decisions to thingee22:46
sdaguethe thing gets included / rendered in a single line - https://github.com/openstack/nova/blob/409f04b2185cc2da9bf4452b20b3d3d9b03beab8/doc/source/feature_classification.rst#L5522:46
sdaguelbragstad: well, flipping limits from -1 to N is a reduction in limits22:48
sdaguelbragstad: so, it just depends on ensuring the tree is still valid22:48
*** limao_ has joined #openstack-dev22:48
sdaguelbragstad: I think I walked that through on the stanek model22:48
dstaneklbragstad: well you'd have to verify that the values underneath work22:49
lbragstadsdague you probably did22:49
sdaguehttp://docs-draft.openstack.org/03/441203/8/check/gate-keystone-specs-docs-ubuntu-xenial/923ac60//doc/build/html/specs/keystone/backlog/hierarchical-quota-scenarios.html#computing-legal-limits22:49
dstaneklbragstad: that's the rub though....keystone would not know if it violated any usage22:49
sdaguedstanek: right, that's ok22:50
lbragstadso at that point, does it make sense to not use the term unlimited and specify local limits for projects?22:50
dstaneksdague: yeah, otherwise it's recursive tree algorithm of some sort22:50
*** gongysh has joined #openstack-dev22:50
sdaguedstanek: we've said before it's completely valid to set limits < current usage22:51
sdagueand that just means the user can't create any more of that22:51
dstaneklbragstad: you mean in that specific scenario or for the entire model?22:51
sdagueand they get an email and say "which of your stuff do you want deleted, or we'll pick"22:51
dstaneksdague: good to know. i don't think i've heard that before or if i did it didn't stick22:51
*** limao has quit IRC22:51
sdagueok, I'll still that in the unified limits doc, I guess I thought that was common knowledge22:52
sdaguebut... that's part of the exercise of writing out things22:52
dstanekwhile over_limits(): delete(random_thing())22:52
lbragstaddstanek i think i'm just starting with a specific scenario and trying to figure out if it's a pain to assume "unlimited" in one project by specifying local limits in sibling projects22:52
dstaneksdague: we've never really talked about limits on the keystone team until PTG.22:53
sdaguelbragstad: well, the alternative is basically default closed22:53
sdagueso unless someone sets a value, it is 022:53
lbragstadsdague what if I want a sibling to assume all available limits of the parent until the limit is hit?22:53
sdaguelbragstad: if you want that22:54
sdagueif you didn't, you could have set it22:54
*** vsaienko has quit IRC22:54
lbragstadin the stanek model that would be done with -122:55
dstaneklbragstad: as in the -1 example?22:55
lbragstadso if B and C are both children of A and A has a limit of 10, and B and C have limits of -1, they can technically fight for resources22:55
jbrycemriedem, dansmith: confirmed there are ad-hoc rooms with tables and power strips that are available for developers to meet/hack in boston. these rooms are separate from the forum rooms that are being scheduled for pre-organized discussions22:55
dstanekthe other models i don't think allow that, but i haven't fully grokked the Garbutt model yet22:55
sdaguelbragstad: anyway, got to run, feel free to throw more thoughts or updates in the doc22:55
sdaguelbragstad: right, but that's what the admin specified22:56
lbragstadsdague right - i think that's useful22:56
dstaneklbragstad: quick vidyo? i can explain what i was thinking quicker that way22:56
mriedemjbryce: can we schedule time in those rooms? or are they just a dumping ground for nerds to sit on their computers?22:56
mriedemthe nedery is the trademark name22:56
mriedem*nerdery22:56
*** kriskend has quit IRC22:56
dansmithjbryce: okay22:56
*** zz_dimtruck is now known as dimtruck22:57
lbragstaddstanek sure22:57
*** stanchan has joined #openstack-dev22:57
*** vsaienko has joined #openstack-dev22:57
lbragstadsdague would you be interesting in doing a group hangout sometime this week?22:57
lbragstadsdague dstanek if so  - i'd be happy to organize/promote one on the mailing list22:58
jbrycemriedem: i believe the idea is to do loose scheduling like we did for the projector rooms at the ptg. there are 5 of these rooms right now available mon-thurs. probably need to check with ttx on what his plans there are. let us know what you think would be most useful and we can see what we can do22:59
*** claudiub has joined #openstack-dev23:01
mriedemok. i imagine the nova dev room time will depend on what times other things are happening23:02
mriedemso we can schedule around a lull23:02
*** claudiub|2 has quit IRC23:04
*** jkilpatr_ has quit IRC23:04
*** jkilpatr_ has joined #openstack-dev23:06
*** cdent has quit IRC23:08
*** vsaienko has quit IRC23:13
*** wootehfoot has quit IRC23:14
*** charcol has joined #openstack-dev23:16
*** jkilpatr_ has quit IRC23:18
*** rcernin has quit IRC23:19
*** jkilpatr_ has joined #openstack-dev23:20
*** galstrom is now known as galstrom_zzz23:21
*** xyang1 has quit IRC23:26
*** limao_ has quit IRC23:28
smcginnisthingee: Yep. That would be great. He's close, but I do want to make sure it aligns with everything else.23:32
*** gordc has quit IRC23:35
*** annegentle has quit IRC23:35
*** xemdetia has quit IRC23:35
*** kriskend has joined #openstack-dev23:36
thingeesmcginnis: ankur is going to respin that patch tomorrow. I'll leave a comment to see if they can work together.23:38
thingeemugsie: ^ http://lists.openstack.org/pipermail/openstack-dev/2017-March/113173.html and https://review.openstack.org/#/c/330027/323:39
*** vnogin has quit IRC23:41
*** vhosakot has quit IRC23:42
*** achampion has quit IRC23:43
*** charcol has quit IRC23:45
*** gyee has joined #openstack-dev23:46
*** salv-orlando has quit IRC23:46
*** k4n0 has quit IRC23:46
*** ssbarnea has quit IRC23:46
*** jaypipes has quit IRC23:49
*** Leo_ has quit IRC23:54
*** Leo_ has joined #openstack-dev23:54
*** jkilpatr_ has quit IRC23:54
*** zaitcev has quit IRC23:56
*** gongysh has quit IRC23:57
*** jkilpatr_ has joined #openstack-dev23:58
*** ccneill has quit IRC23:59

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