Tuesday, 2019-02-19

*** jamesmcarthur has quit IRC00:22
*** sdake has joined #openstack-meeting-alt00:26
*** tetsuro has joined #openstack-meeting-alt00:34
*** ijw has quit IRC00:35
*** ijw has joined #openstack-meeting-alt00:35
*** jamesmcarthur has joined #openstack-meeting-alt00:35
*** lbragstad has quit IRC00:39
*** jamesmcarthur has quit IRC00:40
*** slaweq has quit IRC00:41
*** erlon has joined #openstack-meeting-alt00:45
*** ijw has quit IRC00:52
*** sdake has quit IRC00:58
*** markvoelker has joined #openstack-meeting-alt01:10
*** sdake has joined #openstack-meeting-alt01:16
*** sdake has quit IRC01:16
*** sdake has joined #openstack-meeting-alt01:22
*** whoami-rajat has joined #openstack-meeting-alt01:22
*** ijw has joined #openstack-meeting-alt01:29
*** lbragstad has joined #openstack-meeting-alt01:32
*** hongbin has joined #openstack-meeting-alt01:33
*** erlon has quit IRC01:38
*** ijw has quit IRC01:41
*** ijw has joined #openstack-meeting-alt01:41
*** sdake has quit IRC01:42
*** sdake has joined #openstack-meeting-alt01:42
*** sdake has joined #openstack-meeting-alt01:43
*** markvoelker has quit IRC01:44
*** jamesmcarthur has joined #openstack-meeting-alt01:46
*** sdake has quit IRC01:54
*** jamesmcarthur has quit IRC01:56
*** jamesmcarthur has joined #openstack-meeting-alt01:58
*** sdake has joined #openstack-meeting-alt02:01
*** sdake has quit IRC02:22
*** markvoelker has joined #openstack-meeting-alt02:41
*** jamesmcarthur has quit IRC02:41
*** markvoelker has quit IRC03:13
*** apetrich has quit IRC03:14
*** dklyle has joined #openstack-meeting-alt03:23
*** rfolco has quit IRC03:36
*** andreaf has quit IRC04:08
*** andreaf has joined #openstack-meeting-alt04:09
*** janki has joined #openstack-meeting-alt04:14
*** jamesmcarthur has joined #openstack-meeting-alt04:26
*** jamesmcarthur has quit IRC04:31
*** vishakha has joined #openstack-meeting-alt04:45
*** zzzeek has quit IRC04:49
*** zzzeek has joined #openstack-meeting-alt04:52
*** irclogbot_1 has quit IRC04:57
*** jamesmcarthur has joined #openstack-meeting-alt04:58
*** bhavikdbavishi has joined #openstack-meeting-alt05:00
*** jamesmcarthur has quit IRC05:03
*** ijw has quit IRC05:27
*** ijw has joined #openstack-meeting-alt05:29
*** ijw has quit IRC05:34
*** jamesmcarthur has joined #openstack-meeting-alt05:38
*** hongbin has quit IRC05:41
*** markvoelker has joined #openstack-meeting-alt05:41
*** jamesmcarthur has quit IRC05:43
*** lbragstad has quit IRC05:53
*** sridharg has joined #openstack-meeting-alt05:53
*** jamesmcarthur has joined #openstack-meeting-alt06:10
*** markvoelker has quit IRC06:14
*** jamesmcarthur has quit IRC06:15
*** e0ne has joined #openstack-meeting-alt06:25
*** e0ne has quit IRC06:26
*** ccamacho has quit IRC06:35
*** apetrich has joined #openstack-meeting-alt06:38
*** jtomasek has joined #openstack-meeting-alt06:38
*** kopecmartin|off is now known as kopecmartin07:02
*** slaweq has joined #openstack-meeting-alt07:11
*** markvoelker has joined #openstack-meeting-alt07:11
*** jamesmcarthur has joined #openstack-meeting-alt07:11
*** jamesmcarthur has quit IRC07:15
*** e0ne has joined #openstack-meeting-alt07:23
*** rcernin has quit IRC07:25
*** cloudrancher has quit IRC07:43
*** cloudrancher has joined #openstack-meeting-alt07:43
*** markvoelker has quit IRC07:43
*** ccamacho has joined #openstack-meeting-alt07:47
*** cloudrancher has quit IRC07:47
*** jamesmcarthur has joined #openstack-meeting-alt07:48
*** jamesmcarthur has quit IRC07:53
*** masahito has quit IRC07:57
*** e0ne has quit IRC08:13
*** bhavikdbavishi has quit IRC08:23
*** sdake has joined #openstack-meeting-alt08:28
*** cloudrancher has joined #openstack-meeting-alt08:30
*** tssurya has joined #openstack-meeting-alt08:31
*** liuyulong_ has joined #openstack-meeting-alt08:33
*** jtomasek has quit IRC08:36
*** sdake has quit IRC08:37
*** markvoelker has joined #openstack-meeting-alt08:40
*** sdake has joined #openstack-meeting-alt08:46
*** jamesmcarthur has joined #openstack-meeting-alt08:50
*** liuyulong_ has quit IRC08:54
*** jamesmcarthur has quit IRC08:55
*** bhavikdbavishi has joined #openstack-meeting-alt08:57
*** ttsiouts has joined #openstack-meeting-alt08:57
*** priteau has joined #openstack-meeting-alt08:59
priteau#startmeeting blazar09:00
openstackMeeting started Tue Feb 19 09:00:10 2019 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
tetsuroO/09:01
priteauHi tetsuro09:01
priteauDo you know id masahito is planning to join?09:02
tetsuronot sure09:02
tetsuroI'll ping him on internal slack09:03
priteauThank you09:03
*** masahito has joined #openstack-meeting-alt09:03
masahitoo/09:03
priteauHi masahito09:04
tetsurohi09:04
priteauAgenda for today09:04
priteau1. Denver Summit Project Updates & Onboarding09:04
priteau2. stein-3 milestone09:04
priteau3. AOB09:04
masahitopriteau: sorry, I have to leave in 45min today.09:05
priteauNo problem, we'll try to be quick09:05
priteau#topic Denver Summit Project Updates & Onboarding09:05
*** openstack changes topic to "Denver Summit Project Updates & Onboarding (Meeting topic: blazar)"09:05
priteauThe call for Project Updates & Onboarding is open09:05
priteau"This coming Summit for project updates, we have 36 slots that are 20-min long and 6 that are 40-min long. For project onboarding, we have 24 40-min slots."09:06
priteauGiven that only tetsuro will be in Denver, I assume that we're not going to have an onboarding session this time09:06
priteauI think a 20 minute project update slot is good for us09:07
tetsuroThat decision helps me. Sounds good.09:07
priteautetsuro: Are you still happy to give the project update?09:07
*** ttsiouts has quit IRC09:08
tetsuroYes, pretty much.09:08
priteauGreat, thanks a lot09:08
priteauI will request the 20 minute slot09:08
masahitothanks, tetsuro.09:08
tetsurothanks!09:08
priteau"You (or one of the other speakers for your onboarding/update), must also confirm that at least one of you are registered to attend* the Summit by emailing knelson@openstack.org by Sunday March 17th at 7:00 UTC."09:08
*** ttsiouts has joined #openstack-meeting-alt09:08
priteauI will remind us about it closer to this date.09:09
tetsuroOkay, I remember that.09:09
priteauAre you usually able to register quite in advance?09:10
tetsuroYes, as soon as I get discount code.09:11
*** panda|off is now known as panda09:11
priteauActually, I just saw that I already received my discount code a month ago09:11
priteauAll September 2018 Denver PTG attendees receive 80% off a Summit + PTG Combo ticket. To receive the discount, you MUST register with your unique code before early bird pricing ends on February 27 at 11:59pm PST09:11
priteauDid you receive it?09:12
tetsuroI think so.09:12
tetsuroanyway I check it up09:12
*** ttsiouts has quit IRC09:13
priteau#action tetsuro register for the OpenStack Summit before early bird pricing ends on February 2709:13
priteau#action confirm registration to Kendall Nelson by Sunday March 17th09:13
*** markvoelker has quit IRC09:14
priteauWe'll start working on the slides soon.09:14
priteauAnything else about Denver?09:14
priteauLet's move to the next topic09:16
priteau#topic stein-3 milestone09:16
*** openstack changes topic to "stein-3 milestone (Meeting topic: blazar)"09:16
priteau~2 weeks to go to stein-309:17
priteautetsuro: Is https://bugs.launchpad.net/blazar/+bug/1737676 covered by your affinity patch series?09:19
openstackLaunchpad bug 1737676 in Blazar "Enable anti-affinity check for instance reservation" [Medium,New] - Assigned to Tetsuro Nakamura (tetsuro0907)09:19
tetsuroAh, that's yes09:19
priteauCan you please add a Partial-Bug or Closes-Bug to one of the commit if it is partially/completely resolved?09:20
tetsurookay.09:23
*** yamamoto has joined #openstack-meeting-alt09:23
priteauI reviewed the full patch series, I mostly had minor comments as you saw, overall it looks good09:23
priteauI haven't looked yet at your updated patches from today09:23
priteauI expect we will be able to merge soon09:23
priteaumasahito: Thanks for posting your comment on the floating IP spec: https://review.openstack.org/#/c/609302/10/doc/source/specs/stein/basic-network-plugin.rst@19209:24
masahitoyup. My comment was in the draft :-)09:24
tetsurolooks like I should check it up.09:24
priteauThe API can get complex with multiple floating IPs09:25
*** sdake has quit IRC09:25
masahitoHaving multi floating ip in one reservation makes sense to me.09:25
masahitoOne thing to discuss is its schema.09:25
*** ttsiouts has joined #openstack-meeting-alt09:25
tetsuroI see the point09:26
priteauI am ok with making floating_ip_address a list all the time, even for amount == 1. We should rename it to floatingip_addresses09:26
priteauThe main question is what to do if len(floatingip_addresses) < amount09:26
tetsuro1. invalid request, 2. complement it  a09:27
tetsuroautomatilcally09:27
priteauI would say, try and allocate from the list. Fail if any in the list is not available. Allocate from other free blazar resources for the rest.09:27
*** sdake has joined #openstack-meeting-alt09:28
priteauI think what I suggest is equivalent to tetsuro's 2.09:28
masahitoAnd when len(floatingip_address) > amount, how does the reservation pick up?09:28
priteauMaybe this one should be an error09:29
tetsuroThat should fail.09:29
tetsuroyes09:29
masahitoinvalid input?09:29
priteauyes09:29
tetsuroyes09:29
masahitoAll right. I got it.09:29
tetsuroI'm also good with priteau's strategy in len(floatingip_addresses) < amount case.09:30
priteauI can see a use case for it: user wants x of y specific floating IP addresses (x<y), but doesn't know which are free and which are used. But it probably not going to be used very often. We should keep things simple if possible.09:30
priteauProbably most of the time users will not provide any floating IP address09:31
*** slaweq has quit IRC09:31
*** ccamacho has quit IRC09:31
*** slaweq has joined #openstack-meeting-alt09:32
masahitoMake sense to me. I'll update it applying the discussion. I guess it's not a big change for the patches.09:32
priteauThanks masahito!09:32
tetsuroThank you.09:32
priteauLooks like affinity and floating IP blueprint could be merged by stein-309:33
priteauThat's good news09:34
masahitoRight. We would have big improvements.09:34
priteaumasahito: Did you see that you have a pep8 failure in https://review.openstack.org/#/c/633462/5 which is fixed in https://review.openstack.org/#/c/633669/09:35
priteauThe fix should be moved to the first of the two patches above.09:36
masahitosorry not yet09:36
masahitoAh, right.09:36
priteauI have several bug fixes to be reviewed09:37
priteauhttps://review.openstack.org/#/c/636700/09:37
priteauhttps://review.openstack.org/#/c/635005/09:37
priteauhttps://review.openstack.org/#/c/625724/09:37
*** ttsiouts has quit IRC09:38
*** ttsiouts has joined #openstack-meeting-alt09:38
priteauThanks tetsuro for the review already09:39
priteaumasahito has to go soon so let's move to AOB09:39
priteau#topic AOB09:39
tetsuroput those fixes in my list09:39
*** openstack changes topic to "AOB (Meeting topic: blazar)"09:39
masahitopriteau: thanks09:39
priteauAnything else to discuss or mention?09:40
tetsuroNot from me09:40
masahitoNothing from my side.09:40
priteauNothing special from me either.09:40
priteauWe can finish here for today.09:40
priteauThanks everyone09:41
priteau#endmeeting09:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:41
openstackMeeting ended Tue Feb 19 09:41:21 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/blazar/2019/blazar.2019-02-19-09.00.html09:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/blazar/2019/blazar.2019-02-19-09.00.txt09:41
openstackLog:            http://eavesdrop.openstack.org/meetings/blazar/2019/blazar.2019-02-19-09.00.log.html09:41
tetsurothanks!09:41
masahitothanks all. bye09:41
*** tetsuro has quit IRC09:41
*** derekh has joined #openstack-meeting-alt09:42
*** masahito has quit IRC09:45
*** sdake has quit IRC09:49
*** jamesmcarthur has joined #openstack-meeting-alt09:51
*** e0ne has joined #openstack-meeting-alt09:53
*** jamesmcarthur has quit IRC09:55
*** ttsiouts has quit IRC09:56
*** ttsiouts has joined #openstack-meeting-alt09:58
*** markvoelker has joined #openstack-meeting-alt10:11
*** jamesmcarthur has joined #openstack-meeting-alt10:27
*** jamesmcarthur has quit IRC10:32
*** ttsiouts has quit IRC10:40
*** priteau has quit IRC10:41
*** ttsiouts has joined #openstack-meeting-alt10:41
*** ttsiouts_ has joined #openstack-meeting-alt10:42
*** cloudrancher has quit IRC10:43
*** markvoelker has quit IRC10:43
*** cloudrancher has joined #openstack-meeting-alt10:43
*** cloudrancher has quit IRC10:44
*** ttsiouts has quit IRC10:45
*** cloudrancher has joined #openstack-meeting-alt10:46
*** lpetrut has joined #openstack-meeting-alt10:46
*** carlos_silva has joined #openstack-meeting-alt10:50
*** cloudrancher has quit IRC10:54
*** yamamoto has quit IRC11:00
*** yamamoto has joined #openstack-meeting-alt11:06
*** yamamoto has quit IRC11:11
*** yamamoto has joined #openstack-meeting-alt11:11
*** cloudrancher has joined #openstack-meeting-alt11:21
*** jamesmcarthur has joined #openstack-meeting-alt11:29
*** jtomasek has joined #openstack-meeting-alt11:32
*** cloudrancher has quit IRC11:32
*** cloudrancher has joined #openstack-meeting-alt11:33
*** jamesmcarthur has quit IRC11:33
*** bhavikdbavishi has quit IRC11:36
*** bhavikdbavishi has joined #openstack-meeting-alt11:37
*** markvoelker has joined #openstack-meeting-alt11:40
*** thgcorrea has joined #openstack-meeting-alt11:41
*** raildo has joined #openstack-meeting-alt11:49
*** ttsiouts_ has quit IRC11:57
*** bhavikdbavishi has quit IRC12:08
*** erlon has joined #openstack-meeting-alt12:14
*** markvoelker has quit IRC12:14
*** erlon has quit IRC12:14
*** erlon has joined #openstack-meeting-alt12:15
*** erlon has quit IRC12:16
*** erlon has joined #openstack-meeting-alt12:16
*** cloudrancher has quit IRC12:22
*** rfolco has joined #openstack-meeting-alt12:33
*** jcoufal has joined #openstack-meeting-alt12:37
*** cloudrancher has joined #openstack-meeting-alt12:39
*** janki has quit IRC12:41
*** janki has joined #openstack-meeting-alt12:44
*** janki has quit IRC12:52
*** janki has joined #openstack-meeting-alt12:53
*** janki has quit IRC12:54
*** janki has joined #openstack-meeting-alt12:54
*** bhavikdbavishi has joined #openstack-meeting-alt12:57
*** jamesmcarthur has joined #openstack-meeting-alt13:06
*** markvoelker has joined #openstack-meeting-alt13:11
*** jamesmcarthur has quit IRC13:11
*** ttsiouts has joined #openstack-meeting-alt13:11
*** cloudrancher has quit IRC13:11
*** jamesmcarthur has joined #openstack-meeting-alt13:12
*** bhavikdbavishi has quit IRC13:14
*** ttsiouts has quit IRC13:18
*** ttsiouts has joined #openstack-meeting-alt13:19
*** sdake has joined #openstack-meeting-alt13:23
*** vishakha has quit IRC13:31
*** jamesmcarthur has quit IRC13:32
*** markvoelker has quit IRC13:43
*** jamesmcarthur has joined #openstack-meeting-alt13:49
*** janki has quit IRC13:54
*** jamesmcarthur has quit IRC13:56
*** ttsiouts has quit IRC14:04
*** ttsiouts has joined #openstack-meeting-alt14:04
*** sdake has quit IRC14:05
*** ccamacho has joined #openstack-meeting-alt14:05
*** rfolco has quit IRC14:07
*** rfolco has joined #openstack-meeting-alt14:08
*** liuyulong has quit IRC14:08
*** ttsiouts has quit IRC14:09
*** ttsiouts has joined #openstack-meeting-alt14:09
*** yamamoto has quit IRC14:10
*** sdake has joined #openstack-meeting-alt14:13
*** jtomasek has quit IRC14:17
*** ccamacho has quit IRC14:18
*** sdake has quit IRC14:19
*** ccamacho has joined #openstack-meeting-alt14:22
*** yamamoto has joined #openstack-meeting-alt14:24
*** yamamoto has quit IRC14:26
*** yamamoto has joined #openstack-meeting-alt14:27
*** lbragstad has joined #openstack-meeting-alt14:34
*** sdake has joined #openstack-meeting-alt14:37
*** markvoelker has joined #openstack-meeting-alt14:41
*** munimeha1 has joined #openstack-meeting-alt14:46
*** sdake has quit IRC14:53
*** sdake has joined #openstack-meeting-alt15:00
*** whoami-rajat has quit IRC15:01
*** vishakha has joined #openstack-meeting-alt15:04
*** markvoelker has quit IRC15:14
*** whoami-rajat has joined #openstack-meeting-alt15:18
*** sdake has quit IRC15:28
*** gagehugo has joined #openstack-meeting-alt15:32
*** cloudrancher has joined #openstack-meeting-alt15:33
*** sdake has joined #openstack-meeting-alt15:35
*** lpetrut has quit IRC15:45
*** sdake has quit IRC15:52
*** sdake has joined #openstack-meeting-alt15:58
*** e0ne has quit IRC16:00
*** ianychoi has quit IRC16:00
*** ayoung has joined #openstack-meeting-alt16:01
lbragstad#startmeeting keystone16:01
openstackMeeting started Tue Feb 19 16:01:23 2019 UTC and is due to finish in 60 minutes.  The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: keystone)"16:01
openstackThe meeting name has been set to 'keystone'16:01
*** jamesmcarthur has joined #openstack-meeting-alt16:01
lbragstad#link https://etherpad.openstack.org/p/keystone-weekly-meeting16:01
lbragstadagenda ^16:01
lbragstado/16:01
cmurphyo/16:01
kmalloczzzzzz16:02
kmalloci mean o/16:02
gagehugoo/16:02
vishakhao/16:02
*** sdake has quit IRC16:03
*** e0ne has joined #openstack-meeting-alt16:03
*** hongbin has joined #openstack-meeting-alt16:03
knikollao/16:03
ayoung\m/ dOvOb  \m/16:04
lbragstadalright - let's get started16:04
lbragstad#topic previous action items16:04
*** openstack changes topic to "previous action items (Meeting topic: keystone)"16:04
lbragstadi think i was the only one that had something for last week16:04
lbragstadwhich was to send a note to the mailing list about key loading performance and my struggles attempting to recreate issues with it - or failing to realize actual performance gain16:05
lbragstad#link http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002674.html16:05
lbragstad^ which is now available for your reading pleasure16:05
lbragstadwxy-xiyuan and i did follow up with some downstream teams16:05
lbragstadand the reported issue was using an older token provider, but likely still an issue with fernet/jwt16:06
lbragstadthe problem was that the keystone process would lock the files in order to read them16:06
lbragstadso if you had a whole bunch of keystone processes on the same host, using the same key repository, you could theoretically see bottlenecks with performance if the processes start queuing up while they read keys from disk16:07
lbragstadthis gives me a bit more to go on16:07
kmallocit is likely the best bet is to run a test with low disk-cache (low ram available) and disk under io stress.16:07
lbragstadi haven't taken a stab at recreating it - but i'm going to be setting aside time to do that this week16:08
kmallocNFS might also cause similar odd issues.16:08
lbragstadyeah - that's a good point16:08
lbragstadif this piques anyone's interest, i encourage you to try it out16:08
kmallocor any other network capable filesystem (iscsi based, gluster, RADOS/RBD)16:08
lbragstadobviously, the initial jwt implementation is susceptible to this issue, as is the fernet token provider16:09
*** erus has joined #openstack-meeting-alt16:09
lbragstadi could open a bug to track this specific issue though, and we could continue with the jwt implementation if people are ok with this being something we fix after the fact16:10
ayoungIf only there were a way to avoid having to go back to Keystone to validate tokens at all...16:10
ayounglike, maybe, I don't know, sharing memcache16:10
ayoungwhy don't we stick the tokens into memcache in the first place, and then use the same memcache region between keystone and the other services?16:11
*** cloudrancher has quit IRC16:11
*** markvoelker has joined #openstack-meeting-alt16:11
ayoungIt would be especially cool if Keystone were the only service that could write to it16:11
lbragstadas i noted in my email, this is only a factor when you disable a whole bunch of caching options16:12
*** ianychoi has joined #openstack-meeting-alt16:12
ayoungyeah, but we never provided a way to do ^^16:12
ayoungIf we are dependend on caching, we should use it in a smart way16:12
lbragstadour caching implementation and usage has come a long way since ~mitaka/newton16:13
lbragstadfwiw - we still need to supply a definitive caching guide for keystone16:13
lbragstadthat describes the complexity we have in our caching implementation and how to use it effectively16:14
kmalloclbragstad: *since havana16:15
kmalloclbragstad: (yes, caching was initially implemented in havana)16:15
ayoungIs it possible to inject a new token into the cache upon creation without adding any new code?16:15
lbragstadkmalloc right - we had to overhaul a bunch of it shortly after we implemented fernet16:15
lbragstadayoung yeah - that feature already exists16:16
kmallocayoung: no. we would need to know where to inject the token cache into the memcache, the memcache clusters are not the same in all cases for distributed or centralized keystone / other services16:16
ayoungcan we share that same segment with the validation code in middleware on another server?16:16
lbragstadthough it key'd off an unnecessary configuration option16:16
kmallocand we would need to implement a cache that knows how the KSM keys are constructed16:16
kmallocwe lean on a different cache key in keystone.16:16
ayoungcould we unify them?16:17
kmallocpossibly16:17
lbragstadthat'd be a good idea16:17
kmallocbut it's a chunk of code16:17
lbragstadlooks like we might have a couple actionable things here16:19
lbragstadfor investigative purposes16:19
kmalloci would want to add this post pymemcache16:19
kmallocpython-memcache is actively causing issues for folks now (triple-o notably)16:19
*** cloudrancher has joined #openstack-meeting-alt16:20
kmalloc"only keystone being able to write" means we need to either sign the data in memcache (not likely to work easily) or use bmemcache for SASL auth16:20
ayoungsounds right to me16:20
kmallocbasically anyone who can read from memcache can write16:21
kmallocthe protocol is very ... limited.16:21
ayoungit can be a security hardening to use it.  I think hrybacki is looking into SASL auth already16:21
kmallocall KSMs need SASL auth, and ability to write to the same keys16:21
ayoungread16:21
kmallocno16:21
lbragstadas far as the time we have left for Stein - is it feasible to get any additional caching work done outside of writing a guide?16:22
kmallocKSM also must write.16:22
ayoungNah.  If you validate, it ends up back in cache on the Keystone server side16:22
kmallocif the element is LRU'd out, unless keystone is pushing a cache to every cluster on every validate, the KSM needs to write16:22
ayoungfor this it would be read only16:22
ayoungAh16:22
ayoungprobably no real benefit then, huh?16:23
kmallocyeah16:23
kmallockeystone can push on issue, but it shouldn't be push everywhere on every validate16:23
kmallocalso cache-on-issue for remote sites might cause severe performance issues16:23
kmallocleaning on the KSM to cache would be better in those cases16:23
ayoungWould be cool to have a 2 level setup, where keystone can push to a serivce, but they can't push to each other16:23
kmallocthis gets into where memcache is not the best tool16:24
ayoungistio?16:24
kmallocusing something like REDIS (don't ever use redis due to licensing) is better.16:24
hrybacki(in training but will review meeting notes this evening)16:24
kmallocif we're using the current cache infrastructure16:24
kmallocif we totally re-implement caching [tokens] to something totally different like istio, etcd, or something else, it's more doable16:25
kmallocthat is a monumental rewrite16:25
ayoungyeah,  probably tight to get that into Stein16:25
lbragstad++16:25
kmallocmight be hard to land that into Train, it's going to probably be a 2-cycle initiative16:25
kmalloc1 cycle for scaffolding, one for implementation/adoption16:26
ayoungSeriously, though, this is starting to get into Service mesh land.  We shoud investigate something for that in a future release16:26
kmallocdef. not opposed to it16:26
kmallocjust opposed to trying to wedge it into Stein :)16:26
ayoungThere are numerous, some less tied to K8S than others16:26
lbragstaddoes anyone want to take a shot at a spike and writing up their findings?16:26
kmallocunfortunately, i don't have the bandwidth at the moment.16:27
kmallocthis would be a lot of fun to work on though.16:27
ayoungOutreachy?16:27
lbragstadyeah - it is interesting16:27
kmallocprobably more than intern level of work16:27
lbragstadif not - we can table it and come back to it later16:27
kmallocthis is likely in the flask-rewrite class of effort16:27
lbragstadi would certainly like to get the guide done this release though16:28
kmallocthis touches a lot of very delicate parts.16:28
kmalloccaching is hard. very hard to do right.16:28
kmallocevery one of us here have messed it up at least once in keystone ;)16:28
kmalloc(and in my case, a lot more often)16:29
lbragstadanything else on this?16:29
lbragstadwe kinda went off on a tangent16:29
lbragstad#topic blueprint cleanup16:30
*** openstack changes topic to "blueprint cleanup (Meeting topic: keystone)"16:30
lbragstad#link https://blueprints.launchpad.net/keystone16:30
lbragstad#link https://etherpad.openstack.org/p/keystone-blueprint-cleanup16:30
lbragstad#link http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002672.html16:30
lbragstadquick status update on this16:30
*** yamamoto has quit IRC16:31
lbragstadall blueprints that weren't targeted to stein have been either marked as obsolete or superseded16:31
lbragstadall blueprints that were describing applicable ideas or work have been ported to bug reports https://bugs.launchpad.net/keystone/+bugs?field.tag=rfe16:31
lbragstadwe have patches accepted to doc that describe this now16:32
lbragstad#link https://review.openstack.org/#/c/637311/16:32
lbragstad#link https://review.openstack.org/#/c/62528216:32
lbragstad#link https://review.openstack.org/#/c/637567/ is a follow up to clean up some mistakes i made in the initial write-up16:33
lbragstaddoes anyone have questions about what was done?16:33
*** yamamoto has joined #openstack-meeting-alt16:33
*** yamamoto has quit IRC16:33
*** yamamoto has joined #openstack-meeting-alt16:33
*** yamamoto has quit IRC16:33
lbragstadmoving on16:34
lbragstad#topic reviews16:34
*** openstack changes topic to "reviews (Meeting topic: keystone)"16:34
lbragstaddoes anyone have reviews that need attention?16:34
kmallocJWS16:34
kmalloclots of JWS.16:34
kmallocwe should be landing the last bits for that asap.16:34
gagehugoI'll take a look at them16:35
lbragstad#link https://review.openstack.org/#/q/topic:bp/json-web-tokens+status:open16:35
lbragstadi still have a bunch of patches for scope checking and default roles16:35
lbragstad~50ish or so16:35
cmurphyeasy one https://review.openstack.org/63742516:35
*** jaypipes has quit IRC16:36
*** erus has quit IRC16:36
*** jaypipes has joined #openstack-meeting-alt16:36
vishakhalbragstad: Should I change this patch https://review.openstack.org/#/c/609210/ according to https://review.openstack.org/#/c/636825/16:36
*** erus has joined #openstack-meeting-alt16:37
vishakhalbragstad: and making this abandoned https://review.openstack.org/#/c/636825/16:37
lbragstadvishakha you could - if you're ok with those changes, i was just looking at ways to try and test all the permutations for role assignments16:38
lbragstadi still need to work on a couple of those bits - i'd like to write some more test cases for other types of users16:38
vishakhayes I will add some more test cases for group assignment as per the comments16:39
lbragstadcool - i'll set aside some time today to get back to that16:39
vishakhasure . Thanks for the time on it16:39
lbragstadvishakha no problem - thanks for picking that up16:39
lbragstadknikolla ildikov asked about https://review.openstack.org/#/c/484121/ today in the edge meeting16:40
lbragstadshe was curious if you plan to revisit it or if you need help?16:40
ildikovas we said we would do the max coverage with the K2K federation scenario I'm trying to put the pieces together and see how we can proceed16:41
knikollalbragstad: i hadn't checked on the comments, will do so later on today.16:41
knikollawill revise accordingly.16:41
ildikovknikolla: thanks!16:41
lbragstadthanks knikolla16:41
knikollanp :)16:41
lbragstadanyone else have anything for reviews?16:42
lbragstad#topic open discussion16:43
*** erus has quit IRC16:43
*** openstack changes topic to "open discussion (Meeting topic: keystone)"16:43
cmurphyo/16:43
lbragstad#link https://releases.openstack.org/stein/schedule.html16:43
cmurphyi un-wip'd most of the app cred capabilities patches16:43
* lbragstad just saw that 16:43
*** erus has joined #openstack-meeting-alt16:43
lbragstadready for some reviews?!16:43
cmurphythere are a few things i'd like to discuss about it16:43
cmurphybut i don't want to take up meeting time and can't stay after the meeting16:43
*** markvoelker has quit IRC16:44
cmurphymaybe thursday we could chat about it?16:44
lbragstadworks for me - unless you want to do something async (ML?)16:44
cmurphyi can do that too, might be easier16:44
*** cloudrancher has quit IRC16:44
lbragstadi don't want to hold you up16:45
lbragstaddue to time zones16:45
cmurphyi'll post something to the mailing list and following that will probably propose some small changes to the spec to align with the implementation16:45
kmalloccmurphy: cool i'll review more in depth16:45
lbragstadsounds good16:46
cmurphybut the thing is huge enough that i think it might be worth holding off pushing forward until train-116:46
ayoungcmurphy, nice16:46
lbragstadi'll start taking a look at those reviews either today or tomorrow16:46
cmurphyso that we have sufficient time for discussion and digestion16:46
gagehugook16:46
lbragstad++16:46
lbragstadspeaking of release schedules16:46
lbragstadwe are in R-716:47
kmalloccmurphy: maybe.16:47
ayoungTrain is ok for me, as that alings with the RH long term release, but if it goes any longer, it might as well not happen.16:47
kmalloccmurphy: i think we can possibly land a chunk of the code for support earlier and keep the API bits for T116:47
*** macza has joined #openstack-meeting-alt16:47
lbragstadPTL self nomination starts in two weeks - if you're planning on running please don't hesitate to reach out if you have questions16:47
kmallocso we don't allow anyone to set the values, but all supporting code is in.16:47
cmurphyayoung: at least at this point we have a complete implementation proposed which can now be tweaked, unlike last cycle where we had nothing at this time16:47
cmurphyi'm confident it will happen i just don't want to rush it and regret things16:48
cmurphyi got started on it a little late in the cycle unfortunately16:48
lbragstadthings happen - i'm just happy to see an implementation up for review16:48
kmallocand i'm more than happy to land the code so it's easier to polish and unlock for the users in T1.16:50
kmallocsaves rebase-hell16:50
lbragstadthat's always an option, too16:51
cmurphykmalloc: we might be able to do that16:51
cmurphyin any case expect an email from me in the next couple of days16:51
lbragstadanything else for open discussion?16:52
kmallocdon't forget to book hotels and get tickets to denver before it's sold-out/more-costly/etc16:52
kmallocwe are rapidly hitting the 2mo out window.16:53
lbragstadi think the summit schedule goes live tomorrow?16:53
kmallocsomething like that16:53
kmallocthis was just an early reminder so folks don't do what I've done in the past and go "oh crap...and it's way more pricy"16:53
*** hongbin has quit IRC16:54
vishakhathanks for the reminder kmalloc16:55
lbragstadlooks like we can wrap up a few minutes early16:55
lbragstadthanks for the time, everyone16:55
lbragstadreminder office hours starts in a few minutes for those available16:55
lbragstad#endmeeting16:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:55
openstackMeeting ended Tue Feb 19 16:55:39 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-02-19-16.01.html16:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-02-19-16.01.txt16:55
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-02-19-16.01.log.html16:55
*** ttsiouts has quit IRC16:56
*** ttsiouts has joined #openstack-meeting-alt16:56
*** tssurya has quit IRC17:01
*** ttsiouts has quit IRC17:01
*** raildo_ has joined #openstack-meeting-alt17:02
*** raildo has quit IRC17:03
*** raildo has joined #openstack-meeting-alt17:06
*** raildo_ has quit IRC17:07
*** raildo has quit IRC17:08
*** raildo has joined #openstack-meeting-alt17:09
*** yamamoto has joined #openstack-meeting-alt17:10
*** raildo has quit IRC17:14
*** yamamoto has quit IRC17:16
*** raildo has joined #openstack-meeting-alt17:27
*** lpetrut has joined #openstack-meeting-alt17:27
*** jcoufal has quit IRC17:30
*** raildo has quit IRC17:33
*** e0ne has quit IRC17:35
*** erus has quit IRC17:35
*** erus has joined #openstack-meeting-alt17:36
*** jcoufal has joined #openstack-meeting-alt17:36
*** lpetrut has quit IRC17:40
*** markvoelker has joined #openstack-meeting-alt17:41
*** ccamacho has quit IRC17:46
*** raildo has joined #openstack-meeting-alt17:48
*** derekh has quit IRC17:53
*** kopecmartin is now known as kopecmartin|off17:53
*** raildo_ has joined #openstack-meeting-alt18:02
*** raildo has quit IRC18:05
*** ijw has joined #openstack-meeting-alt18:08
*** raildo has joined #openstack-meeting-alt18:11
*** raildo_ has quit IRC18:12
*** raildo has quit IRC18:13
*** erus has quit IRC18:13
*** raildo_ has joined #openstack-meeting-alt18:14
*** markvoelker has quit IRC18:14
*** erus has joined #openstack-meeting-alt18:14
*** jamesmcarthur has quit IRC18:17
*** jamesmcarthur has joined #openstack-meeting-alt18:18
*** raildo has joined #openstack-meeting-alt18:20
*** raildo_ has quit IRC18:21
*** tssurya has joined #openstack-meeting-alt18:28
*** raildo_ has joined #openstack-meeting-alt18:30
*** raildo has quit IRC18:30
*** hongbin has joined #openstack-meeting-alt18:34
*** hongbin has quit IRC18:35
*** hongbin has joined #openstack-meeting-alt18:35
*** lpetrut has joined #openstack-meeting-alt18:39
*** e0ne has joined #openstack-meeting-alt18:41
*** e0ne has quit IRC18:42
*** ccamacho has joined #openstack-meeting-alt18:42
*** jtomasek has joined #openstack-meeting-alt18:45
*** jamesmcarthur has quit IRC18:53
*** e0ne has joined #openstack-meeting-alt18:54
*** markvoelker has joined #openstack-meeting-alt19:11
*** erus has quit IRC19:11
*** erus has joined #openstack-meeting-alt19:11
*** ijw has quit IRC19:15
*** panda is now known as panda|off19:17
*** lpetrut has quit IRC19:18
*** vishakha has quit IRC19:22
*** jamesmcarthur has joined #openstack-meeting-alt19:24
*** sridharg has quit IRC19:29
*** sdake has joined #openstack-meeting-alt19:34
*** e0ne has quit IRC19:39
*** e0ne has joined #openstack-meeting-alt19:39
*** diablo_rojo has joined #openstack-meeting-alt19:42
*** markvoelker has quit IRC19:44
*** e0ne has quit IRC19:45
*** gagehugo has left #openstack-meeting-alt19:50
*** sdake has quit IRC19:52
*** erus has quit IRC19:55
*** erus has joined #openstack-meeting-alt19:56
*** sdake has joined #openstack-meeting-alt19:56
*** sdake has quit IRC19:58
*** thgcorrea has quit IRC19:59
*** efried has quit IRC20:29
*** efried has joined #openstack-meeting-alt20:29
*** tssurya has quit IRC20:32
*** ttsiouts has joined #openstack-meeting-alt20:36
*** e0ne has joined #openstack-meeting-alt20:37
*** markvoelker has joined #openstack-meeting-alt20:41
*** erlon has quit IRC20:55
*** igordc has joined #openstack-meeting-alt20:58
*** ttsiouts has quit IRC21:00
*** ttsiouts has joined #openstack-meeting-alt21:01
*** ttsiouts has quit IRC21:05
*** raildo_ has quit IRC21:07
*** yamamoto has joined #openstack-meeting-alt21:13
*** markvoelker has quit IRC21:13
*** yamamoto has quit IRC21:18
*** whoami-rajat has quit IRC21:21
*** e0ne has quit IRC21:28
*** _pewp_ has quit IRC21:37
*** _pewp_ has joined #openstack-meeting-alt21:38
*** hongbin has quit IRC21:49
*** jtomasek has quit IRC21:57
*** cloudrancher has joined #openstack-meeting-alt21:57
*** sdake has joined #openstack-meeting-alt21:59
*** ttsiouts has joined #openstack-meeting-alt22:07
*** carlos_silva has quit IRC22:08
*** sdake has quit IRC22:09
*** markvoelker has joined #openstack-meeting-alt22:10
*** erus has quit IRC22:11
*** ttsiouts has quit IRC22:12
*** jcoufal has quit IRC22:14
*** aning has joined #openstack-meeting-alt22:21
*** rcernin has joined #openstack-meeting-alt22:26
*** cloudrancher has quit IRC22:39
*** markvoelker has quit IRC22:44
*** cloudrancher has joined #openstack-meeting-alt22:47
*** cloudrancher has quit IRC22:51
*** munimeha1 has quit IRC23:02
*** ccamacho has quit IRC23:13
*** ccamacho has joined #openstack-meeting-alt23:14
*** liuyulong has joined #openstack-meeting-alt23:40
*** markvoelker has joined #openstack-meeting-alt23:41

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