Tuesday, 2018-12-18

*** PagliaccisCloud has quit IRC00:09
*** dave-mccowan has joined #openstack-meeting-alt00:12
*** macza has quit IRC00:13
*** macza has joined #openstack-meeting-alt00:15
*** PagliaccisCloud has joined #openstack-meeting-alt00:15
*** dave-mccowan has quit IRC00:18
*** macza has quit IRC00:20
*** absubram has quit IRC00:38
*** erlon_ has joined #openstack-meeting-alt00:48
*** iyamahat has joined #openstack-meeting-alt00:48
*** iyamahat has quit IRC00:50
*** iyamahat has joined #openstack-meeting-alt00:56
*** stevebaker has joined #openstack-meeting-alt01:03
*** masahito has joined #openstack-meeting-alt01:10
*** masahito has quit IRC01:15
*** gyee has quit IRC01:18
*** yikun has joined #openstack-meeting-alt01:27
*** iyamahat_ has joined #openstack-meeting-alt01:39
*** iyamahat has quit IRC01:42
*** hongbin has joined #openstack-meeting-alt01:42
*** hongbin_ has joined #openstack-meeting-alt02:28
*** hongbin has quit IRC02:29
*** iyamahat_ has quit IRC02:52
*** yamahata has quit IRC02:52
*** erlon_ has quit IRC02:57
*** dpawlik has joined #openstack-meeting-alt03:06
*** dpawlik has quit IRC03:10
*** apetrich has quit IRC03:15
*** hongbin has joined #openstack-meeting-alt03:20
*** hongbin_ has quit IRC03:21
*** rcernin has quit IRC03:25
*** rcernin has joined #openstack-meeting-alt03:27
*** rcernin has quit IRC03:28
*** rcernin has joined #openstack-meeting-alt03:28
*** bhavikdbavishi has joined #openstack-meeting-alt03:34
*** bhavikdbavishi has quit IRC03:35
*** bhavikdbavishi has joined #openstack-meeting-alt03:35
*** hongbin has quit IRC03:43
*** dtrainor_ has joined #openstack-meeting-alt03:57
*** dtrainor_ has quit IRC03:57
*** rf0lc0 has joined #openstack-meeting-alt04:28
*** rfolco has quit IRC04:29
*** PagliaccisCloud has quit IRC04:31
*** bhavikdbavishi has quit IRC04:33
*** PagliaccisCloud has joined #openstack-meeting-alt04:36
*** janki has joined #openstack-meeting-alt04:50
*** PagliaccisCloud has quit IRC05:01
*** sridharg has joined #openstack-meeting-alt05:08
*** kmalloc has quit IRC05:14
*** iyamahat has joined #openstack-meeting-alt05:24
*** diablo_rojo has quit IRC05:25
*** bhavikdbavishi has joined #openstack-meeting-alt05:44
*** PagliaccisCloud has joined #openstack-meeting-alt06:06
*** bhavikdbavishi has quit IRC06:06
*** PagliaccisCloud has quit IRC06:27
*** ccamacho has quit IRC06:31
*** mgagne_ has quit IRC06:35
*** mgagne has joined #openstack-meeting-alt06:39
*** gouthamr has quit IRC06:55
*** bhavikdbavishi has joined #openstack-meeting-alt07:01
*** iyamahat has quit IRC07:01
*** iyamahat has joined #openstack-meeting-alt07:09
*** e0ne has joined #openstack-meeting-alt07:11
*** ccamacho has joined #openstack-meeting-alt07:14
*** bhavikdbavishi has quit IRC07:18
*** apetrich has joined #openstack-meeting-alt07:18
*** ccamacho has quit IRC07:21
*** bhavikdbavishi has joined #openstack-meeting-alt07:22
*** jtomasek has joined #openstack-meeting-alt07:26
*** dpawlik has joined #openstack-meeting-alt07:35
*** dpawlik has quit IRC07:42
*** yamahata has joined #openstack-meeting-alt07:52
*** slaweq has joined #openstack-meeting-alt07:53
*** dpawlik has joined #openstack-meeting-alt07:56
*** kopecmartin|off is now known as kopecmartin07:59
*** apetrich has quit IRC08:06
*** ccamacho has joined #openstack-meeting-alt08:22
*** liuyulong has quit IRC08:23
*** bhavikdbavishi has quit IRC08:35
*** lhinds has quit IRC08:36
*** lhinds has joined #openstack-meeting-alt08:37
*** apetrich has joined #openstack-meeting-alt08:38
*** tetsuro has joined #openstack-meeting-alt08:42
*** priteau has joined #openstack-meeting-alt08:47
*** tetsuro has quit IRC08:47
*** tetsuro has joined #openstack-meeting-alt08:48
*** masahito has joined #openstack-meeting-alt08:58
priteau#startmeeting blazar09:00
openstackMeeting started Tue Dec 18 09:00:03 2018 UTC and is due to finish in 60 minutes.  The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: blazar)"09:00
openstackThe meeting name has been set to 'blazar'09:00
priteau#topic Roll call09:00
*** openstack changes topic to "Roll call (Meeting topic: blazar)"09:00
masahitoo/09:00
priteauHello masahito09:00
priteauI spot tetsuro as well09:02
tetsuro0/09:03
priteauNo bertys however09:04
priteauWell, let's start09:04
priteauAgenda for today is code review and next meetings09:05
priteau#topic Code review09:05
*** openstack changes topic to "Code review (Meeting topic: blazar)"09:05
priteauI see tetsuro's placement patch was just approved09:06
masahitoYes, I added W+1 just now.09:07
tetsuroThanks a lot. I will begin another series to enable affinity.09:07
priteaumasahito: I see you pushed an update to the resource allocation series. I haven't had time to review them this morning but will try to do so today. If I recall correctly it was the unit tests that needed an update.09:08
*** bhavikdbavishi has joined #openstack-meeting-alt09:08
masahitoRight. The gate job failure is just I forgot to update unit tests when I changed the response body schema.09:09
masahitoI fixed it.09:09
priteauThank you09:10
priteauFinally we can have this functionality for stein-2 :)09:10
priteauSmall patches that are easy to review:09:11
priteauNew version of Asmita's patch for min/max IntOpt values: https://review.openstack.org/#/c/625514/09:11
priteauMailing list address update… https://review.openstack.org/#/c/625244/09:12
priteauAnother one: https://review.openstack.org/#/c/621925/09:13
priteauSmall typo fix from me: https://review.openstack.org/#/c/625607/09:14
*** jesusaur has quit IRC09:15
priteauI would like to discuss what to do for the mutable config patch09:16
priteauhttps://review.openstack.org/#/c/585847/09:16
priteauThere is nothing wrong with the patch itself, it is implemented as it should be09:17
priteauHowever, it is not possible to use the functionality because blazar-manager doesn't like receiving a SIGHUP09:17
masahitoLooks like meaning less patch for current blazar.09:18
masahitoI'm okay to go the patch.09:18
priteauI am proposing that we merge the patch but, if we cannot resolve the SIGHUP issue at the time of the Stein release, we create a release note containing an "issues" block09:18
*** rcernin has quit IRC09:18
tetsuro+1. reasonable09:20
*** iyamahat has quit IRC09:21
masahito+109:21
priteauI will change the commit message to reflect the fact that it doesn't yet work though09:21
*** jesusaur has joined #openstack-meeting-alt09:22
priteauUpdated commit message: https://review.openstack.org/#/c/585847/09:25
priteauPlease review09:25
masahitoDone09:26
priteauGreat09:26
priteaumasahito: Will you push an update to your floating IP spec? There are some comments from Akihiro Motoki. https://review.openstack.org/#/c/609302/09:28
masahitoyes. I'm checking and replying the comment now.09:28
masahitoI want to talk Akihiro's comment that Blazar should have a config which declares a set of floating IP address.09:29
priteauWhat about this approach:09:31
masahitoHis suggestion is Blazar has a config option to declare 1. a set of IP addresses blazar can assign for floating IPs or 2. a set of IP address ranges blazar cannot assign for floating IPs.09:31
priteauWhen we create a floating IP in Blazar, Blazar fetches the subnet info from Neutron and verifies that the IP is *not* inside the allocation range09:31
priteauAnd it checks that the IP *is* within the CIDR network09:32
priteauThis way, the admin doesn't have to manually keep the blazar config in sync with the Neutron state09:32
priteauWhat do you think?09:32
masahitoThat's what I was thinking for the spec. Of course, it makes sense.09:34
priteauLet's propose this then09:35
masahitoAhh, I didn't mention any validation in the spec.09:35
masahitoIt would be that's why he commented.09:35
masahitookay, I reply it.09:35
priteauDo you have only the spec or have you started writing some code as well?09:37
masahitonothing09:38
priteauOK. I am in the opposite situation: I have an implementation of network segment reservation (VLAN, VXLAN, etc.) but no spec yet ;-)09:39
priteauThe spec for network segments will follow broadly the same approach as floating IP: Blazar can allocate networks outside of the tenant range.09:40
priteauWe needed the implementation for internal use, but I think I will be able to write a spec and share it early next year09:42
masahitoNice09:43
priteauI think we've covered most of the patches. Over the next few weeks I hope to make some progress with pushing Chameleon bug fixes upstream, so there will be more to review.09:44
*** bhavikdbavishi has quit IRC09:45
masahitoIt looks like some bug reports for s-2 are assigned to you now.  Do you have time to hit these? If I have time, I can take over some patches.09:45
priteauMany of these already have a fix in Chameleon, it often just needs a test case and a release note09:45
*** vishalmanchanda has joined #openstack-meeting-alt09:46
priteauI will let you know if any don't have anything started that you could work on09:46
masahitogot it.09:47
*** derekh has joined #openstack-meeting-alt09:48
priteau11 minutes left, let's talk about the next meetings.09:48
priteau#topic Next meetings09:49
*** openstack changes topic to "Next meetings (Meeting topic: blazar)"09:49
priteauAs you probably know, next Tuesday is Christmas and the Tuesday after is New Year's Day09:49
priteauSo I propose that we cancel both meetings09:49
masahito+109:49
priteauNext meeting would be on January 809:49
priteauThat's just after the stein-2 milestone. Will you have some time for code review until then?09:51
priteau(via Gerrit, not IRC meeting)09:51
*** erlon_ has joined #openstack-meeting-alt09:51
masahitoI'll work until on 28th Dec and start on 7th Jan.09:51
masahitoSo I have some days to review the codes.09:52
priteauGreat. I will work the rest of this week and maybe some between 26 and 31. Then back on the 7th of Jan09:53
priteau#topic AOB09:54
*** openstack changes topic to "AOB (Meeting topic: blazar)"09:54
priteauAnything else to discuss?09:55
masahitoThe next Summit and PTG is announced. http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000961.html09:56
*** frickler has joined #openstack-meeting-alt09:57
masahitoI'm not sure I can attend it now.09:57
priteauThanks for sharing. I am not sure I will be there, it's not a great timing for me.09:58
priteauWe can discuss closer to the date. Early bird registration is open until February 1st.09:59
priteauThat's all for today. Thanks for joining09:59
priteauHave a great holiday season.10:00
priteau#endmeeting10:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"10:00
openstackMeeting ended Tue Dec 18 10:00:05 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/blazar/2018/blazar.2018-12-18-09.00.html10:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/blazar/2018/blazar.2018-12-18-09.00.txt10:00
openstackLog:            http://eavesdrop.openstack.org/meetings/blazar/2018/blazar.2018-12-18-09.00.log.html10:00
masahitoHave a great holiday!10:00
masahitobye10:00
*** masahito has quit IRC10:06
*** erlon_ has quit IRC10:08
*** ttsiouts has joined #openstack-meeting-alt10:10
*** dpawlik has quit IRC10:30
*** dpawlik_ has joined #openstack-meeting-alt10:30
*** pbourke has quit IRC10:36
*** pbourke has joined #openstack-meeting-alt10:37
*** yamamoto has quit IRC11:01
*** ttsiouts has quit IRC11:17
*** ttsiouts has joined #openstack-meeting-alt11:18
*** ttsiouts has quit IRC11:22
*** erlon_ has joined #openstack-meeting-alt11:32
*** yamamoto has joined #openstack-meeting-alt11:38
*** EmilienM|off is now known as EmilienM11:41
*** ttsiouts has joined #openstack-meeting-alt11:47
*** baojg has joined #openstack-meeting-alt11:52
*** bhavikdbavishi has joined #openstack-meeting-alt11:52
*** yamamoto has quit IRC11:54
*** yamamoto has joined #openstack-meeting-alt11:54
*** bhavikdbavishi has quit IRC11:56
*** bhavikdbavishi has joined #openstack-meeting-alt11:56
*** raildo has joined #openstack-meeting-alt12:01
*** tpsilva has joined #openstack-meeting-alt12:06
*** PagliaccisCloud has joined #openstack-meeting-alt12:07
*** janki has quit IRC12:17
*** liuyulong has joined #openstack-meeting-alt12:40
*** e0ne has quit IRC12:53
*** bhavikdbavishi1 has joined #openstack-meeting-alt12:59
*** bhavikdbavishi has quit IRC13:00
*** bhavikdbavishi1 is now known as bhavikdbavishi13:00
*** yamamoto has quit IRC13:37
*** yamamoto has joined #openstack-meeting-alt13:38
*** yamamoto has quit IRC13:43
*** rf0lc0 is now known as rfolco13:48
*** e0ne has joined #openstack-meeting-alt13:57
*** bhavikdbavishi has quit IRC13:57
*** pgodek has joined #openstack-meeting-alt14:06
*** e0ne has quit IRC14:07
*** PagliaccisCloud has quit IRC14:20
*** yamamoto has joined #openstack-meeting-alt14:22
*** e0ne has joined #openstack-meeting-alt14:43
*** ttsiouts has quit IRC14:45
*** ttsiouts has joined #openstack-meeting-alt14:46
*** jgrosso has joined #openstack-meeting-alt14:46
*** dpawlik_ has quit IRC14:47
*** ttsiouts has quit IRC14:50
*** jgrosso has quit IRC14:52
*** bhavikdbavishi has joined #openstack-meeting-alt14:57
*** ttsiouts has joined #openstack-meeting-alt14:58
*** Chenjie_ has joined #openstack-meeting-alt15:01
*** Chenjie_ has quit IRC15:02
*** xyang has joined #openstack-meeting-alt15:04
*** munimeha1 has joined #openstack-meeting-alt15:05
*** wxy| has joined #openstack-meeting-alt15:07
*** Chenjie_ has joined #openstack-meeting-alt15:08
*** hongbin has joined #openstack-meeting-alt15:14
*** Chenjie_ has quit IRC15:14
*** dpawlik has joined #openstack-meeting-alt15:16
*** dpawlik has quit IRC15:21
*** bhavikdbavishi has quit IRC15:21
*** jtomasek has quit IRC15:29
*** vishalmanchanda has quit IRC15:35
*** liuyulong has quit IRC15:38
*** ileixe_ has joined #openstack-meeting-alt15:51
*** ileixe_ is now known as ileixe15:54
*** gagehugo has joined #openstack-meeting-alt15:57
*** ccamacho has quit IRC15:59
lbragstad#startmeeting keystone16:00
openstackMeeting started Tue Dec 18 16:00:09 2018 UTC and is due to finish in 60 minutes.  The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
lbragstad#link https://etherpad.openstack.org/p/keystone-weekly-meeting16:00
*** openstack changes topic to " (Meeting topic: keystone)"16:00
lbragstadagenda ^16:00
openstackThe meeting name has been set to 'keystone'16:00
lbragstado/16:00
hrybackio/16:00
ileixeo/16:00
vishakhao/16:00
gagehugoo/16:00
lbragstadwow - better attendance than i was expecting :)16:00
*** diablo_rojo has joined #openstack-meeting-alt16:01
cmurphyo/16:01
wxy|o/16:02
lbragstadok - cool16:02
lbragstadwe have quite a bit on the agenda today - so we'll go ahead and get started16:02
lbragstad#topic Upcoming Meetings/Holidays16:02
*** openstack changes topic to "Upcoming Meetings/Holidays (Meeting topic: keystone)"16:02
lbragstadthe next two tuesdays fall on holidays16:02
lbragstadso i'm not expecting to hold meetings unless folks *really* want to have one while celebrating16:03
lbragstadotherwise - we'll just pick things back up on January 8th16:03
lbragstadi'll send a note after the meeting with a reminder to the openstack-discuss mailing list16:04
lbragstad#topic Oslo Releases16:04
*** openstack changes topic to "Oslo Releases (Meeting topic: keystone)"16:04
lbragstadkind of related to the holiday schedule16:04
lbragstadbnemec sent a note yesterday about oslo releases16:04
lbragstad#link http://lists.openstack.org/pipermail/openstack-discuss/2018-December/001047.html16:04
*** iyamahat has joined #openstack-meeting-alt16:05
bnemecI'm just about to propose the releases for this week.16:05
lbragstadthis is just a reminder that if anyone needs anything from an oslo library for the next few weeks, we'll have to do it soon16:05
knikollao/16:05
lbragstadthere isn't anything on my radar16:05
bnemecHolding off on privsep because it makes a significant change and I don't want to deal with it over the holidays, but I don't think that will affect keystone.16:05
lbragstadack16:06
* knikolla having a headache, but i'll lurk around. 16:06
lbragstadyeah - we don't use privsep i don't think16:06
wxy|bnemec: does oslo has something like feature freeze time? I wonder if we can have oslo.limit 1.0 release in Stein.16:06
bnemecwxy|: We do have feature freeze, and it's a bit earlier than the OpenStack-wide feature freeze.16:07
bnemecLet me find the details.16:07
lbragstadrelated to ^ - i pinged jaypipes and johnthetubaguy a few days ago about syncing up on that work16:07
wxy|bnemec: Thanks, I'll pay attention for the deadline.16:08
wxy|lbragstad: ++16:08
lbragstadprior to berlin, there was a bunch of good discussion on the interface between nova and oslo.limit, but i don't think it has moved since then16:08
bnemecFor Rocky, Oslo's feature freeze actually coincided with Keystone's: https://releases.openstack.org/rocky/schedule.html16:08
bnemecWhich reminds me I probably need to get that on the Stein schedule.16:09
bnemecFull details are here: http://specs.openstack.org/openstack/oslo-specs/specs/policy/feature-freeze.html16:09
lbragstadif we ask again, we might not get a response this close to the holidays, but it might be worth putting together an action item for the beginning of January to follow up with the nova team on that stuff16:09
wxy|lbragstad: it's good to have.16:09
lbragstadwxy| want to take that one with me?16:10
wxy|lbragstad: sure.16:10
lbragstad#action lbragstad and wxy| to follow up with nova after the holidays about movement on oslo.limit + nova integration16:10
lbragstadcool16:10
lbragstadanything else oslo library related?16:10
wxy|no, thanks16:11
lbragstadthanks wxy|16:11
lbragstad#topic Previous Action Items16:11
*** openstack changes topic to "Previous Action Items (Meeting topic: keystone)"16:11
lbragstadi think the only previous action item we had was to get a spec up for protecting the admin role from being deleted16:11
lbragstadwhich cmurphy has done16:11
lbragstad#link https://review.openstack.org/#/c/624692/16:11
lbragstadup for review if you're interested in taking a look ^16:11
lbragstad#topic Reviews16:12
*** openstack changes topic to "Reviews (Meeting topic: keystone)"16:12
lbragstaddoes anyone have reviews that need eyes?16:12
lbragstador anything in review they want to call attention to specifically?16:12
cmurphyhttps://review.openstack.org/62497216:12
lbragstadthat's the last bit of all the docs work, right?16:13
cmurphyall of the admin guide consolidation/reorg yes16:13
cmurphyi'm still working on the federation guide16:13
cmurphyalso interested in people's thoughts on https://review.openstack.org/623928 and the related bug report16:13
lbragstadawesome - thanks for picking up the remaining consolidation bits cmurphy16:13
lbragstadi'll take a look at 623928 today16:14
lbragstadany other reviews people want to bring up?16:15
lbragstadok - moving on16:16
lbragstad#topic System scope upgrade cases16:16
*** openstack changes topic to "System scope upgrade cases (Meeting topic: keystone)"16:16
lbragstadcmurphy and i have been going through the system scope changes for the projects API16:16
lbragstadand it got me thinking about another case16:16
lbragstad#link https://review.openstack.org/#/c/625732/16:16
lbragstadi wanted to bring this to the rest of the group to walk through the upgrade, just so we're all on the same page16:17
lbragstad^ that review is specific to groups (not projects), but it's applicable16:17
lbragstadif you look at #link https://review.openstack.org/#/c/625732/1/keystone/common/policies/group.py16:17
lbragstadyou can see that I'm deprecating the previous policies and implementing the system reader role as the default16:18
lbragstadbut... that only happens if a deployment sets ``keystone.conf [oslo_policy] enforce_scope=True`` and it's False by default16:18
lbragstadfor example the policy for get_group would be '(rule:admin_required or role:reader)'16:20
lbragstadsince deprecated policies are handled gracefully by oslo.policy in order to help with upgrade16:20
lbragstadso - if enforce_scope=False (the default), the get_group policy would be accessible by something with the `reader` role on a project16:21
cmurphywhat exactly happens when a policy is deprecated? if the operator hasn't changed any defaults and policy is in code, does the new check string take effect or the old check string?16:22
lbragstadgood question16:22
lbragstadthey are OR'd16:22
lbragstadfor example, the current policy for get_group is rule:admin_required16:23
lbragstadand if the new policy ends up being `role:reader`, it will be OR'd with the deprecated policy.16:23
lbragstadthis allows operators a window of time to assign users roles for the new default, or make adjustments so that they can either 1. consume the new default or 2. copy/paste the old policy and maintain it as an override16:24
cmurphyso both policies will be allowed - so it's essentially more permissive while it's being deprecated?16:25
*** dave-mccowan has joined #openstack-meeting-alt16:25
lbragstadwith that specific example, it is16:26
lbragstadbut... the new policy could be something like `role:reader AND system_scope:all`16:26
lbragstadwhich wouldn't allow someone with the reader role on a project to access the get_group API16:27
lbragstadi'm not a huge fan of encoding scope checks into check strings...16:28
lbragstadand it's redundant with scope_types... but after thinking about this for a week or so.. i'm not sure there is another way to roll out new policies in a backwards compatible way?16:28
lbragstadat least while we have enforce_scope=False by default16:28
lbragstadif enforce_scope=True, then `role:reader` alone would be a bit safer16:29
cmurphyi'm not sure either16:29
lbragstadso far, the best answer i have (which may not be the best) is...16:30
lbragstad1. deprecate the old policies 2. the new policies have the scope check in the check string :( 3. when we go to remove the old deprecated policies in Train we can clean up the policies to remove the scope checks from the check string16:31
bnemecDo they need to be OR'd? In general I would expect the new rule to just take effect if the operator hasn't overridden the old one.16:31
lbragstadstep 3 would also include a change for keystone to set ``keystone.conf [oslo_policy] enforce_scope=True``16:32
lbragstadbnemec good question16:32
lbragstadthe reason why we OR'd them is because if the new rule is less permissive, then we want to make sure operators have time to adjust assignment accordingly so that users can continue to access that API16:33
lbragstadotherwise, it would be possible for operators to break users on upgrade if the new, more restrictive rule, is used exclusively16:34
bnemecHow will they know they need to change it though? Is there a warning if it only passes the old, less restrictive rule?16:34
* lbragstad grabs a link 16:34
lbragstadhttp://git.openstack.org/cgit/openstack/oslo.policy/tree/oslo_policy/policy.py#n67816:36
lbragstadwe run that code when we load rules in oslo.policy16:36
bnemecYeah, I guess that tells them it will change, but it doesn't necessarily tell them whether that's a problem.16:37
lbragstadyeah - that gets tough since it depends on how they have roles setup?16:38
bnemecI guess they would test by explicitly setting the new policy so the deprecated one isn't OR'd in and see if anything breaks.16:38
lbragstadyes - exactly...16:38
lbragstadwhich is how i've hard to write some of the new keystone protection tests16:38
lbragstadhad*16:38
bnemecYeah, it would be nice if we could be smarter with the warnings, but that would make the logic even more complicated and I already have a hard enough time following it. :-)16:39
lbragstad=/16:39
lbragstadthere certainly isn't a shortage of edge cases here16:40
lbragstadif people want to discuss this though, we can take it to office hours, too16:40
lbragstadmy other question was about the organization of #link https://review.openstack.org/#/q/status:open+project:openstack/keystone+branch:master+topic:implement-default-roles16:41
bnemecSounds good. I don't want to hold up the meeting any more than I already have.16:41
vishakhalbragstad: I will soon update my patches for system scope too.16:41
lbragstadvishakha awesome - that's another reason why i wanted to talk about this as team, since we have multiple people doing the work16:42
wxy|vishakha: ah, good to know, I'll review yours as well.16:43
vishakhalbragstad: Yes will ping you for any doubts related to scopes. Thanks for the updates.16:43
lbragstadi know we have bugs open for the majority of this owrk16:43
vishakhawxy|: thanks :)16:43
lbragstad#link https://bugs.launchpad.net/keystone/+bugs?field.tag=policy16:43
lbragstadbut - as the people who have to review this stuff... is there anything I (we) can do organizationally to maintain the chaos/review queue16:44
lbragstador make it easier for people to review in general16:47
cmurphynot sure there's much that can be done about sheer volume16:47
lbragstadyeah - that's the answer i was afraid of16:47
bnemecMaybe talk to dhellmann. He does a lot of high volume review submission.16:48
lbragstadi wasn't sure if people wanted to team up on specific resources, or have a priority queue of some kind that applied focus to certain areas16:48
lbragstadbnemec oh - good call16:48
cmurphyhe does but it's usually distributed across projects16:48
cmurphyso not so much review load on one team16:49
lbragstadi just sympathize with people looking at this and not knowing where to start - so if there is anything i can do to make that easier, i'm all ears16:49
bnemecYeah, but maybe he has some tricks for distributing it. I know they had a team split up the work for the python3-first stuff.16:50
*** e0ne has quit IRC16:50
lbragstadsomething we can talk about after the meeting, too16:52
lbragstadfew minutes left and there are two more topics, so we can move on for now16:53
lbragstad#topic Tokens with tag attributes16:53
*** openstack changes topic to "Tokens with tag attributes (Meeting topic: keystone)"16:53
lbragstadileixe o/16:53
ileixeo/16:53
ileixeIt's about the RFE which returns token with 'tag' attribute.16:54
ileixetag with project16:54
ileixewe are using the tag for oslo.policy16:55
ileixefor example get_network only for matching tag16:55
lbragstadso - do you have custom policy check strings that are written to check the token directly?16:56
ileixein credential - yes16:56
*** macza has joined #openstack-meeting-alt16:56
lbragstade.g., %(target.token.project.tag)16:56
ileixeyes similar16:56
ileixeI heard of system_scope first time in this place.. and this can be used for our purpose though. I'm not sure16:57
lbragstaddo you have a more detailed example of why you need to override get_network?16:58
ileixeWe have two general scope16:58
ileixe'dev' 'prod'16:58
ileixeevery project include in one of them16:58
ileixeand we have also two network dev_net prod_net16:58
ileixeprovider_network they are16:59
lbragstadso 'dev' and 'prod' are not projects or domains?16:59
ileixeyes16:59
ileixeit just16:59
ileixescheme for our inhouse16:59
ileixecodebase16:59
ileixewe want to make some general scope to restrict resource16:59
ileixeand for now I found 'tag'16:59
lbragstadsure -  are you available to discuss this after the meeting in -keystone?17:00
ileixeyes sure17:00
lbragstadok - cool, meet you over there17:00
lbragstadthanks for the time everyone17:00
lbragstad#endmeeting17:00
ileixeThanks17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:00
openstackMeeting ended Tue Dec 18 17:00:55 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-12-18-16.00.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-12-18-16.00.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-12-18-16.00.log.html17:01
*** wxy| has quit IRC17:03
*** kopecmartin is now known as kopecmartin|off17:05
*** e0ne has joined #openstack-meeting-alt17:13
*** ttsiouts has quit IRC17:14
*** ttsiouts has joined #openstack-meeting-alt17:15
*** e0ne has quit IRC17:19
*** ttsiouts has quit IRC17:19
*** ileixe has quit IRC17:54
*** gouthamr_ has joined #openstack-meeting-alt17:54
*** cloudrancher has quit IRC17:55
*** iyamahat has quit IRC17:57
*** cloudrancher has joined #openstack-meeting-alt17:57
*** yamahata has quit IRC17:57
*** derekh has quit IRC18:01
*** iyamahat has joined #openstack-meeting-alt18:11
*** PagliaccisCloud has joined #openstack-meeting-alt18:20
*** yamahata has joined #openstack-meeting-alt18:31
*** e0ne has joined #openstack-meeting-alt18:34
*** e0ne has quit IRC18:40
*** gyee has joined #openstack-meeting-alt18:48
*** priteau has quit IRC18:58
*** sridharg has quit IRC19:05
*** e0ne has joined #openstack-meeting-alt19:05
*** erlon_ has quit IRC20:04
*** jtomasek has joined #openstack-meeting-alt20:29
*** erlon has joined #openstack-meeting-alt20:32
*** jtomasek has quit IRC20:34
*** gagehugo has left #openstack-meeting-alt20:37
*** PagliaccisCloud has quit IRC21:04
*** hongbin has quit IRC21:09
*** hongbin has joined #openstack-meeting-alt21:09
*** dpawlik has joined #openstack-meeting-alt21:12
*** dpawlik has quit IRC21:22
*** rcernin has joined #openstack-meeting-alt21:22
*** tpsilva has quit IRC21:31
*** raildo has quit IRC21:36
*** rcernin has quit IRC21:37
*** dpawlik has joined #openstack-meeting-alt21:37
*** dpawlik has quit IRC21:42
*** e0ne has quit IRC21:51
*** rcernin has joined #openstack-meeting-alt22:04
*** munimeha1 has quit IRC22:05
*** rcernin has quit IRC22:37
*** rcernin has joined #openstack-meeting-alt22:41
*** rcernin has quit IRC22:43
*** rcernin has joined #openstack-meeting-alt22:45
*** masahito has joined #openstack-meeting-alt23:03
*** efried has joined #openstack-meeting-alt23:29
*** efried has quit IRC23:34
*** dave-mccowan has quit IRC23:56

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