Tuesday, 2018-10-30

*** gyee has quit IRC00:04
*** hongbin has joined #openstack-meeting-alt01:23
*** bhavikdbavishi has joined #openstack-meeting-alt01:36
*** cloudrancher has quit IRC01:41
*** cloudrancher has joined #openstack-meeting-alt01:42
*** diablo_rojo has quit IRC01:56
*** lei-zh has joined #openstack-meeting-alt02:06
*** bhavikdbavishi has quit IRC02:08
*** fanzhang has left #openstack-meeting-alt02:18
*** lei-zh has quit IRC02:31
*** lei-zh has joined #openstack-meeting-alt02:32
*** yamahata has quit IRC02:48
*** iyamahat has quit IRC02:49
*** bhavikdbavishi has joined #openstack-meeting-alt03:11
*** diablo_rojo has joined #openstack-meeting-alt03:32
*** tetsuro has joined #openstack-meeting-alt04:10
*** lei-zh has quit IRC04:10
*** bswartz has quit IRC04:11
*** janki has joined #openstack-meeting-alt04:14
*** bswartz has joined #openstack-meeting-alt04:19
*** diablo_rojo has quit IRC04:21
*** diablo_rojo_ has joined #openstack-meeting-alt04:21
*** vishalmanchanda has joined #openstack-meeting-alt04:22
*** hongbin has quit IRC04:23
*** ccamacho has quit IRC04:26
*** diablo_rojo_ has quit IRC04:42
*** diablo_rojo has joined #openstack-meeting-alt04:50
*** lpetrut has joined #openstack-meeting-alt04:52
*** diablo_rojo has quit IRC05:00
*** tetsuro has quit IRC05:03
*** tetsuro has joined #openstack-meeting-alt05:03
*** tetsuro_ has joined #openstack-meeting-alt05:04
*** tetsuro has quit IRC05:08
*** iyamahat has joined #openstack-meeting-alt05:10
*** lei-zh has joined #openstack-meeting-alt05:11
*** lei-zh has quit IRC05:18
*** yamahata has joined #openstack-meeting-alt05:28
*** lpetrut has quit IRC05:28
*** tetsuro_ has quit IRC05:29
*** tetsuro has joined #openstack-meeting-alt05:34
*** tetsuro has quit IRC05:38
*** lei-zh has joined #openstack-meeting-alt05:42
*** tetsuro has joined #openstack-meeting-alt06:05
*** tetsuro has quit IRC06:09
*** tetsuro has joined #openstack-meeting-alt06:10
*** jbadiapa has quit IRC06:10
*** vishalmanchanda has quit IRC06:16
*** vishalmanchanda has joined #openstack-meeting-alt06:16
*** smyers_ has joined #openstack-meeting-alt06:17
*** smyers has quit IRC06:18
*** smyers_ is now known as smyers06:18
*** vishalmanchanda has quit IRC06:26
*** vishalmanchanda has joined #openstack-meeting-alt06:26
*** dkrol has quit IRC06:28
*** slaweq has quit IRC06:40
*** tonyb has quit IRC06:50
*** dpawlik has joined #openstack-meeting-alt07:26
*** dpawlik has quit IRC07:27
*** dpawlik has joined #openstack-meeting-alt07:27
*** jbadiapa has joined #openstack-meeting-alt07:36
*** rdopiera has joined #openstack-meeting-alt07:42
*** slaweq has joined #openstack-meeting-alt07:50
*** tetsuro has quit IRC07:50
*** alexchadin has joined #openstack-meeting-alt08:02
*** ccamacho has joined #openstack-meeting-alt08:04
*** kopecmartin|off is now known as kopecmartin08:08
*** e0ne has joined #openstack-meeting-alt08:41
*** lpetrut has joined #openstack-meeting-alt08:48
*** rossella_s has joined #openstack-meeting-alt08:48
*** priteau has joined #openstack-meeting-alt08:52
*** slaweq has quit IRC08:53
*** masahito has joined #openstack-meeting-alt08:58
priteau#startmeeting blazar09:00
openstackMeeting started Tue Oct 30 09:00:22 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
priteauHello Blazar folks09:00
masahitoo/09:00
*** ccamacho has quit IRC09:01
priteauHi masahito09:01
priteauClocks in Europe have changed to winter time on Sunday, hopefully Bertrand will have noticed that the meeting is one hour earlier :-)09:02
priteaumasahito: Do you know if tetsuro is joining today?09:02
masahitopriteau: He didn't say anything.09:03
masahitoI'll ping him.09:03
priteauThank you09:05
priteauLet's start, he might join later09:07
priteauAgenda for today:09:07
*** tetsuro has joined #openstack-meeting-alt09:07
priteau1. Project Update @ Berlin Summit09:07
priteau2. Forum @ Berlin Summit09:07
masahitoHe still doesn't replay me. We can start :-)09:07
priteau3. Blazar specifications09:07
priteau4. stein-2 milestone09:07
priteau5. AOB09:07
priteauHi tetsuro09:07
tetsuroHi sorry to be late09:07
priteauNo problem09:08
priteau#topic Project Update @ Berlin Summit09:08
*** openstack changes topic to "Project Update @ Berlin Summit (Meeting topic: blazar)"09:08
priteauOur talk is getting close to its final state now09:08
priteau#link https://docs.google.com/presentation/d/1nsuiQe72E0cYELSI8qLmNwVm4SOXzuf01akzqKEZ1TE/edit09:09
masahitoI updated Rocky features page.09:09
priteauThank you masahito for adding content about Rocky09:09
priteauI added content for Beyond Stein too09:09
masahitoNice09:10
priteaumasahito: could you add a bit more details about the use cases for NFV on slide 2?09:10
masahitogot it09:11
priteauThere's a TODO09:11
priteauI'll add another slide after slide 2 to describe the current kind of reservations available (instance and host)09:12
priteauAnd how users create them09:12
priteauThis was a suggestion from tetsuro last week09:12
priteauMaybe a screenshot of blazar-dashboard too?09:13
masahitoThat's nice idea.09:14
priteauAny other suggestion to improve the talk?09:14
priteauWe've got just two weeks left before the summit, so we should make the final changes by next meeting09:15
masahitoIf time is allowed, the interest from Scientifc-WG is good contents for the session.09:16
masahitoI don't know who has an interest to Blazar project except us, but the showing common interest makes sense.09:18
priteauI think a main blocker for scientific clouds to adopt Blazar could be the lack of quotas09:18
priteauAt the moment one user could reserve the entire OpenStack cloud09:19
priteauSo we need to make progress on integration with Nova quotas09:19
priteauIt's on the "Beyond Stein" slide09:20
priteauShould we move to the next topics?09:20
masahitoyup09:21
tetsuroyes09:21
priteau#topic Forum @ Berlin Summit09:21
*** openstack changes topic to "Forum @ Berlin Summit (Meeting topic: blazar)"09:21
priteauJust a reminder that we've got two forum sessions, both of them have Etherpads now09:21
priteau#link https://etherpad.openstack.org/p/Berlin2018-Forum-Extending-Blazar-reservations09:21
priteau#link https://etherpad.openstack.org/p/BER-python-bindings-for-the-placement-api09:22
priteauHopefully we'll have a good turnout09:23
priteau#topic Blazar specifications09:23
*** openstack changes topic to "Blazar specifications (Meeting topic: blazar)"09:23
priteauOur blazar-specs repo is now live09:23
priteau#link http://git.openstack.org/cgit/openstack/blazar-specs09:23
priteauIt's empty for now but I will populate it later09:24
priteauI propose that we finish working on the floating IP spec in the blazar repo, so that comments are all in the same place09:24
priteauNew specs will go to blazar-specs09:25
*** derekh has joined #openstack-meeting-alt09:25
priteauWhat do you think of this approach?09:26
tetsuroTHat sounds a right way to go.09:26
masahitoIt makes sense.09:26
priteauGreat, I will go ahead with this plan.09:27
priteau#topic stein-2 milestone09:28
*** openstack changes topic to "stein-2 milestone (Meeting topic: blazar)"09:28
priteauI moved most bugs and blueprints that we couldn't tackle for stein-1 to the stein-2 milestone09:29
priteau#link https://launchpad.net/blazar/+milestone/stein-209:29
priteauI'd like to do more reviews but I keep finding more bugs to fix!09:29
priteauLast one: https://bugs.launchpad.net/blazar/+bug/180046309:29
openstackLaunchpad bug 1800463 in Blazar "Hosts are not added to aggregate when updating an active reservation" [Critical,In progress] - Assigned to Pierre Riteau (priteau)09:29
priteauAfter the summit we could have a review meeting to go through the backlog09:32
masahitookay09:33
priteauAny comment about stein-2?09:33
*** lei-zh has quit IRC09:33
priteaumasahito: Are you planning to push a new version of the floating IP spec as per your last comment on https://review.openstack.org/#/c/609302/09:36
masahitooops, yes.09:36
masahitoI forgot pushing the spec, sorry. I'll do that tomorrow.09:36
priteauThank you!09:37
priteau#topic AOB09:38
*** openstack changes topic to "AOB (Meeting topic: blazar)"09:38
priteauAnything else to discuss?09:38
masahitoI have one item09:39
*** tetsuro has quit IRC09:39
masahitoThe place of the document for blazar-status command.09:39
masahitohttps://review.openstack.org/#/c/611811/09:39
masahitoThis patch adds its CLI document to CLI section. IMHO, it's a section for user's CLI.09:40
priteauRight. In Nova it is located at https://docs.openstack.org/nova/latest/user/upgrade.html09:42
masahitoSo my suggestion is adding an admin section or upgrade section.09:42
priteauThis is because their user guide is split in several sections, one is for end users and one for maintenance09:43
priteauAlthough they also have a separate admin guide at https://docs.openstack.org/nova/latest/admin/index.html09:43
masahitoOkay, I'll push another follow-up patch to move its section.09:43
priteauI think the simplest approach for us is to create an upgrade section in the user guide09:44
priteauAt the same time we should document blazar-db-manage09:44
masahitoRight.09:44
priteauThanks for volunteering to improve the patch masahito09:44
priteauAnything else?09:46
*** tetsuro has joined #openstack-meeting-alt09:48
priteautetsuro is back. tetsuro, any AOB?09:48
priteauIf not we can finish early09:48
tetsuroNo, sorry09:48
priteauOK, thanks for joining everyone!09:49
priteau#endmeeting09:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:49
openstackMeeting ended Tue Oct 30 09:49:45 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/blazar/2018/blazar.2018-10-30-09.00.html09:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/blazar/2018/blazar.2018-10-30-09.00.txt09:49
openstackLog:            http://eavesdrop.openstack.org/meetings/blazar/2018/blazar.2018-10-30-09.00.log.html09:49
masahitobye09:49
*** tetsuro has quit IRC09:51
*** masahito has quit IRC09:56
*** slaweq has joined #openstack-meeting-alt10:08
*** priteau has quit IRC10:11
*** ccamacho has joined #openstack-meeting-alt10:11
*** bhavikdbavishi has quit IRC10:20
*** ttsiouts has joined #openstack-meeting-alt10:22
*** jtomasek has quit IRC10:30
*** e0ne has quit IRC10:32
*** dpawlik has quit IRC10:37
*** dpawlik has joined #openstack-meeting-alt10:37
*** pbourke has quit IRC10:49
*** pbourke has joined #openstack-meeting-alt10:49
*** e0ne has joined #openstack-meeting-alt10:54
*** jbadiapa has quit IRC11:04
*** erlon has joined #openstack-meeting-alt11:04
*** priteau has joined #openstack-meeting-alt11:04
*** bhavikdbavishi has joined #openstack-meeting-alt11:14
*** janki has quit IRC11:25
*** bhavikdbavishi has quit IRC11:35
*** alexchadin has quit IRC11:36
*** bhavikdbavishi has joined #openstack-meeting-alt11:41
*** yamamoto has quit IRC11:51
*** yamamoto has joined #openstack-meeting-alt11:53
*** jesusaur has quit IRC11:56
*** yamamoto has quit IRC11:58
*** pbourke has quit IRC12:01
*** jtomasek has joined #openstack-meeting-alt12:01
*** dtrainor has joined #openstack-meeting-alt12:01
*** jesusaur has joined #openstack-meeting-alt12:01
*** pbourke has joined #openstack-meeting-alt12:06
*** bhavikdbavishi has quit IRC12:07
*** pbourke has quit IRC12:09
*** pbourke has joined #openstack-meeting-alt12:09
*** jesusaur has quit IRC12:13
*** ttsiouts has quit IRC12:16
*** raildo has joined #openstack-meeting-alt12:16
*** tssurya has joined #openstack-meeting-alt12:20
*** e0ne has quit IRC12:21
*** janki has joined #openstack-meeting-alt12:31
*** ttsiouts has joined #openstack-meeting-alt12:32
*** yamamoto has joined #openstack-meeting-alt12:33
*** bhavikdbavishi has joined #openstack-meeting-alt12:39
*** jesusaur has joined #openstack-meeting-alt12:41
*** jbadiapa has joined #openstack-meeting-alt13:02
*** lpetrut has quit IRC13:05
*** dustins has joined #openstack-meeting-alt13:07
*** e0ne has joined #openstack-meeting-alt13:08
*** lpetrut has joined #openstack-meeting-alt13:11
*** yamamoto has quit IRC13:12
*** bhavikdbavishi has quit IRC13:12
*** jtomasek_ has joined #openstack-meeting-alt13:13
*** tpsilva has joined #openstack-meeting-alt13:15
*** jtomasek has quit IRC13:17
*** dklyle has quit IRC13:37
*** dklyle has joined #openstack-meeting-alt13:37
*** ttsiouts has quit IRC13:40
*** redrobot has joined #openstack-meeting-alt13:41
*** ttsiouts has joined #openstack-meeting-alt13:42
*** jcoufal has joined #openstack-meeting-alt13:49
*** hongbin has joined #openstack-meeting-alt13:52
*** rdopiera has quit IRC13:58
*** dklyle has quit IRC14:02
*** david-lyle has joined #openstack-meeting-alt14:02
*** GeraldK has joined #openstack-meeting-alt14:05
*** yamamoto has joined #openstack-meeting-alt14:21
*** wxy| has joined #openstack-meeting-alt14:23
*** yamamoto has quit IRC14:26
*** jgrosso has joined #openstack-meeting-alt14:31
*** e0ne has quit IRC14:33
*** janki has quit IRC14:35
*** e0ne has joined #openstack-meeting-alt14:37
*** munimeha1 has joined #openstack-meeting-alt14:38
*** raildo has quit IRC14:43
*** raildo has joined #openstack-meeting-alt14:50
*** yamamoto has joined #openstack-meeting-alt14:59
*** gagehugo has joined #openstack-meeting-alt15:06
*** caboucha has joined #openstack-meeting-alt15:06
*** ianychoi_ is now known as ianychoi15:07
*** markstur has joined #openstack-meeting-alt15:08
*** yamamoto has quit IRC15:20
*** yamamoto has joined #openstack-meeting-alt15:23
*** e0ne has quit IRC15:25
*** Leo_m has joined #openstack-meeting-alt15:27
*** yamamoto has quit IRC15:28
*** gyee has joined #openstack-meeting-alt15:29
*** e0ne has joined #openstack-meeting-alt15:35
*** dpawlik has quit IRC15:43
*** dpawlik has joined #openstack-meeting-alt15:44
*** ccamacho has quit IRC15:48
*** dpawlik has quit IRC15:49
*** Leo_m has quit IRC15:49
*** Leo_m has joined #openstack-meeting-alt15:51
*** yamamoto has joined #openstack-meeting-alt15:57
lbragstad#startmeeting keystone16:00
openstackMeeting started Tue Oct 30 16:00:39 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
*** openstack changes topic to " (Meeting topic: keystone)"16:00
openstackThe meeting name has been set to 'keystone'16:00
hrybackio/16:00
lbragstad#link https://etherpad.openstack.org/p/keystone-weekly-meeting16:00
cmurphyo/16:00
lbragstadagenda ^16:00
knikollao/16:01
kmalloco/16:01
gagehugoo/16:02
lbragstadgive folks another 30 seconds16:02
* kmalloc drinks more coffee while waiting16:02
*** cloudrancher has quit IRC16:02
wxy|o/16:02
lbragstad#topic TC Vision Feedback16:03
*** openstack changes topic to "TC Vision Feedback (Meeting topic: keystone)"16:03
lbragstadin case you haven't seen it16:03
lbragstad#link http://lists.openstack.org/pipermail/openstack-dev/2018-October/136034.html16:03
lbragstadapplies to us16:03
lbragstadif you have opinions, comments, questions, or concerns, feel free to weigh in16:03
lbragstad#topic Athenz and Auto Provisioning16:04
*** openstack changes topic to "Athenz and Auto Provisioning (Meeting topic: keystone)"16:04
lbragstad#link https://etherpad.openstack.org/p/keystone-shadow-mapping-athenz-delta16:04
*** cloudrancher has joined #openstack-meeting-alt16:04
lbragstadpenick posted responses to questions in there16:04
kmallocnice16:04
lbragstaddepending on his availability, we might see if we can get him in our meeting next week if we have more questions16:04
lbragstadhe did offer to participate in a hangout/vc if people find that useful16:05
lbragstadfeel free to weigh in on the approach, or leave comments about what might be feasible to upstream into keystone's auto-provisioning implementation16:05
lbragstaddoes anyone have immediate questions on this topic?16:06
lbragstadok - moving on16:07
lbragstad#topic Dead Code/Doc Cleanup16:07
*** openstack changes topic to "Dead Code/Doc Cleanup (Meeting topic: keystone)"16:07
lbragstadkmalloc o/16:07
kmalloctake a look at the links on the agenda16:07
kmalloca few of us have been on a "clean up the dead code" kick16:07
kmalloc(notably wxy| cmurphy and myself)16:07
kmallocthis is removing a lot of ancient stuff we don't need anymore16:08
lbragstad#link https://review.openstack.org/#/q/status:open+project:openstack/keystonemiddleware+branch:master+topic:bug/164973516:08
lbragstad#link https://review.openstack.org/#/c/614172/16:08
hrybackiinfinite++16:08
lbragstad#link https://review.openstack.org/#/c/612625/416:08
kmallocthere will be more16:08
lbragstad#link https://review.openstack.org/#/c/613218/116:08
lbragstad#link https://review.openstack.org/#/c/613513/316:08
lbragstadthanks kmalloc cmurphy wxy|16:08
kmallocbut this is very much something we need to keep our eyes on16:08
kmallocold code causes weird problems16:08
knikollaawesome!16:08
kmalloclike spamming the keystone server for the revocation list that is a 410 now16:09
kmalloc(KSM)16:09
kmallocso, if you see code that needs to go16:10
kmallocspin a quick pack16:10
kmallocpatch*16:10
kmallocwhile i like these as low-hanging fruit, clearly we have to still do the cleanup even if we don't have someone picking them up16:10
kmallocso, my opinion is we should just clean some stuff up ever now and again16:10
kmallocespeically the big ones like PKI[z] support in KSM16:11
*** dustins has quit IRC16:11
lbragstadmakes sense - i'll review those patches today16:11
kmallocbecause it removes a lot of bitrot code16:11
kmallocand less to maintain is good for us(tm)16:11
*** jtomasek_ has quit IRC16:12
lbragstadany other patches to note regarding dead code?16:13
kmallocnothing yet16:13
lbragstad#topic Bug Smash16:13
*** openstack changes topic to "Bug Smash (Meeting topic: keystone)"16:13
lbragstadkmalloc?16:14
knikollawondering how a "dead code" halloween costume would look like16:14
gagehugo(un)dead code16:14
kmallocI went through and triaged/smashed/closed/etc a TON of bugs across our projects16:14
cmurphyI reopened a couple of those btw16:14
kmallocif i mis-closed a bug, please don't hesitate to open it back up (cmurphy caught a few)16:14
cmurphy:)16:14
kmalloccmurphy: :)16:14
kmallocalso don't hesitate to be aggressive about closing/marking bugs as incomplete if they need more info16:15
kmallocI'd like to see us down under 100 bugs for keystone by end of stien16:15
kmallocwe're at ~130ish16:15
lbragstadyeah - we've been trending higher over the last 180ish days...16:15
kmallocmost of them are small amounts of code to fix, e.g. https://review.openstack.org/#/c/613633/16:15
*** GeraldK has quit IRC16:15
kmallocbut it's not exactly "easy" to figure out what needs to be done16:15
kmallocanother example:16:16
kmalloc#link https://review.openstack.org/#/c/613455/16:16
*** lpetrut has quit IRC16:16
kmallocjust long running bugs we should bubble to the top of our lists16:16
kmallocmost of the other projects are in the single digit or sub 30 bugs16:17
kmallocother = our other, aka not-server16:17
kmallocsome are really in depth, i expect those to take longer16:17
lbragstadit would be nice to have keystone server under 100 by the time we release stein16:17
gagehugowe did finally fix that one doc issue about the port # that would be re-opened as a new bug at least once a week16:17
kmallocbut we have mostly been letting bugs sit, and either they are not relevant (we aren't going to fix) or we should fix them16:17
kmallocgagehugo: we have a lot of doc bugs16:18
kmallocthose are really unfun to fix16:18
kmalloc:(16:18
lbragstadwe have a lot of documentation work in general16:18
kmalloci'd like to get us to really consider a bug-zero target16:18
lbragstadespecially the duplication from the Great Doc Migration in Pike16:18
kmallocmeaning, all bugs are actively worked on (longer bugs) or have fixes proposed16:19
kmallocor are in an incomplete/need more data state16:19
kmalloce.g. the awful admin-ness bug wont be closed until scope_type work is done16:19
kmalloci don't expect bug-zero in stien16:20
lbragstadwhich we're planning to get done in stein16:20
kmallocbut we should aim to knock down to sub 100, if we are sub 100 this cycle we can aim for sub 50 next16:20
kmallocand if we are 50 or under, i think bug-zero is a real target16:20
lbragstadhalf of the scope_types bugs are in progress16:20
lbragstad#link https://bugs.launchpad.net/keystone/+bugs?field.tag=policy16:20
kmalloc++16:20
lbragstadthanks to vishakha for helping out there16:21
kmallocvishakha has been working on a bunch of bugs16:22
kmallocit's fantastic16:22
cmurphyI've been looking for interesting low-hanging-fruit tasks for all the outreachy applicants, if any of these bugs are easy fixes but missing the low-hanging-fruit tag please add it, or if any of them could maybe be broken down into smaller tasks that a newbie could do please let me know16:22
kmallocwe also have had some wonderful outreachy-potential folks stepping in on the low hanging ones16:22
kmalloccmurphy: ++16:22
cmurphyi had to remove the low-hanging-fruit from a couple of troll bugs16:23
lbragstadthanks for helping with that kmalloc and cmurphy16:23
*** dave-mccowan has joined #openstack-meeting-alt16:23
lbragstadcmurphy do you remember which ones?16:23
cmurphyhttps://bugs.launchpad.net/keystone/+bug/1570463 https://bugs.launchpad.net/keystone/+bug/157965916:24
openstackLaunchpad bug 1570463 in OpenStack Identity (keystone) "RFE: keystone-manage CLI to allow using syslog & specific log files" [Medium,Incomplete] - Assigned to Maram El-Salamouny (maramelsalamouny)16:24
openstackLaunchpad bug 1579659 in OpenStack Identity (keystone) "oauth login silently ignores scope" [Medium,Triaged] - Assigned to omkar_telee (omkar-telee)16:24
*** jgrosso has quit IRC16:24
* kmalloc would close that first bug as "wont fix" tbh16:24
kmallocyou can totally pipe output to the syslog injector binary16:25
cmurphyi was trying to figure out if it's already fixed16:25
*** cloudrancher has quit IRC16:25
kmallocit might be with keystone's log.conf16:25
kmallocbut i would just say pipe to logger16:25
kmallocthat would be the way i'd do it in any environment i manage16:26
*** cloudrancher has joined #openstack-meeting-alt16:26
kmallocbecause configuring keystone-manage sounds like a TON of work16:26
cmurphytriaging the bug isn't the topic ;)16:26
kmallocanyway16:26
lbragstadanything else we want to cover on bugs16:26
lbragstad?16:26
kmallocwe should re-visit friday-bug-day16:26
kmallocjust make sure all bugs are triaged16:27
*** ayoung has joined #openstack-meeting-alt16:27
kmallocpost summit*16:27
kmallocnot pre-summit16:27
kmalloc:P16:27
lbragstadmm16:27
lbragstadwe moved away from friday's because of $reasons16:27
kmallocthe weekly bug smash did keep bugs at least with eyes.16:27
kmalloccould be any day16:27
lbragstadbut i wouldn't be opposed to focusing on bugs during office hours16:27
kmallocjust a weekly "hey folks, triage bugs"16:27
lbragstadif question queues are down16:27
hrybacki++ pragmatic16:28
kmallocjust once a week make sure new bugs haven't lingered for months.16:28
kmallocor weeks16:28
lbragstadsure16:28
kmallocor well longer :P16:28
kmallocobviously more triaging is good16:28
lbragstadi notice several other projects use their weekly meetings to do group triage16:28
kmalloc1st hour of office hours == quick triage?16:29
lbragstadthat's not something we've typically done, but i wouldn't mind spreading the triage knowledge around a bit16:29
hrybackidumb question -- is there anything like an sla between cores and community wrt bug responses?16:29
kmallochrybacki: typically no16:29
cmurphyhrybacki: it's not just "cores" who are responsible for bugs16:29
kmallocanyone may triage bugs.16:29
lbragstadhrybacki sla as in the community must respond to bugs within X days or something like that?16:30
cmurphykmalloc: or fix them16:30
kmallocand sometimes reporter needs to supply more info16:30
kmalloccmurphy: ++16:30
hrybackinot what I meant -- but if there was something they'd have to pin it to /a/ group16:30
hrybackilbragstad: aye16:30
*** e0ne has quit IRC16:30
kmallocthere is no set SLA in that regard16:30
hrybackiack16:30
lbragstadpart of the Apache2 license covers part of that16:30
* kmalloc is done harping on bugs.16:31
kmalloc:)16:31
kmallocthanks all!16:31
ayoungThere is only one bug I care about16:31
hrybackiinteresting /me notes a review16:31
hrybackilol ayoung16:31
hrybackiwhich one?16:31
cmurphylol16:31
* hrybacki ducks16:31
ayoungI'm a man with a one track mind.  So much to do in one lifetime....16:31
lbragstadhrybacki you're playing with fire16:31
knikollahaha16:31
* hrybacki runs and hides16:32
ayoungNot a man for compromise and where's and why's and living lies16:32
* lbragstad braces himself for an ayoung rant 16:32
lbragstad;)16:32
ayounghttps://www.youtube.com/watch?v=hFDcoX7s6rE16:32
ayoungJust excited for Bohemian Rhapsody this weekend, actually.16:32
kmallochrybacki: don't encourage it :P16:32
ayoung:)16:33
kmallocayoung: i've heard VERY good things, but lets talk about that outside of the meeting16:33
lbragstadoh - i know16:33
hrybackiI'll stop poking the ants nest16:33
lbragstadi want to see that movie so bad16:33
lbragstadalrighty - moving16:33
lbragstadon16:33
lbragstad#topic KSA Rate Limiting16:33
*** openstack changes topic to "KSA Rate Limiting (Meeting topic: keystone)"16:33
lbragstadkmalloc o/ again?16:33
kmallocThis needs tests.16:33
kmallocBUT16:33
kmallocI want eyes on this to see if this belongs in ksa16:33
kmallocI think it is worthwhile16:34
kmallocbut it could go up in SDK instead16:34
kmallocthis implements ratelimiting mechanisms in KSA itself16:34
ayoungKSA?16:34
kmallockeystoneauth16:34
ayoungWhy on the client side?16:34
kmallocso the client can say "i don't want to overload X server"16:34
ayoungKSA2?16:34
ayounghmmm16:34
kmallocor "we might get locked out if we ask too many times, so please don't ask too many times"16:34
ayoungLIke LDAP?16:34
kmallocthis is allowing the client to limit their requests to <any> service16:35
kmallocnot just assuming the server will be pleasant about it16:35
kmallocnodepool specifically needs this kind of functionality, but if nodepool does it is likely someone else does too16:35
ayoungWhen you say it that way, it sounds like SDK16:35
kmallocand the lower the level it is supported the easier it is to maintain16:36
cmurphyI sort of grimaced at it but mordred made the point that there is already retry logic in ksa16:36
kmallocnot everything uses SDK.16:36
kmallocand KSA does have.. yes what cmurphy said16:36
cmurphyso rate limiting sort of goes with that16:36
mordredI didn't do it16:36
* mordred reads16:36
lbragstadmakes sense16:36
kmallocso, please +1/+2/-1 (please do not -2, we're not at that point yet)16:36
ayoungnot everything uses KSA either.  CloudForms goes with Fog16:36
kmalloci'd like eyes and comments.16:36
mordredso - the reason I think it needs to be in ksa and not sdk (where it is now)16:37
kmallocayoung: aye, but most things python use KSA16:37
mordredis that automatic retries are handled at the ksa layer16:37
mordredand so are invisible as requests to the sdk layer16:37
ayoungOk.16:37
* knikolla pokes mordred: we should talk about the summit talk at some point soon16:38
mordredknikolla: yeah. :)16:38
kmallocmordred: and i largely agree, but want the other keystone folks to have eyes on it16:38
kmallocand it will have tests before it lands16:38
* lbragstad makes a note to review16:38
ayoungWhat will it break to have it in KSA?16:38
mordredalso - fwiw - the code allows two things - client-side rate limiting, as well as concurrency limiting - we have found that both are essential in real-world use like nodepool16:39
kmallocbut, right now just looking at "is this a good idea and a good impl" is what we wanty16:39
kmallocayoung: should break nothing, it's opt-in use only16:39
mordredayoung: nothing. it should be completely no-op if you don't opt-in16:39
kmallocayoung: as it should be16:39
*** chhagarw has joined #openstack-meeting-alt16:39
ayoungJust to complete the thought...if this is so important, should it be OPT in, or is that only due to paranoia?16:39
kmallocit must be opt in, because you want the client to specify how limited things should be16:40
kmallocmany times a couple simple retries isn't bad16:40
kmallocthe client/consumer is the only thing that can know how limited the rate of requests should be16:40
mordredyeah - it's extra overhead that many people don't need - but if you're at scale, you will need it16:40
kmallocif it's a "this might break the server" case, the server should protect itself16:40
kmalloc(different story)16:40
mordred'should'16:40
kmallocyeah, so not opening THAT can of worms right now16:41
* mordred flexes arms and remembers crashing public clouds before having implemented client-side rate limiting :)16:41
lbragstadanything else on this topic?16:42
ayoungOK...we'll look with appropriate understaning now.  Anything else on that?16:42
kmallocnope.16:42
lbragstad#topic open discussion16:42
*** openstack changes topic to "open discussion (Meeting topic: keystone)"16:42
kmallocexcept please do not -2 ;)16:42
lbragstadfloor is open16:42
cmurphyLike I mentioned before I'm looking for good low hanging fruit tasks for newbies to get their hands dirty without having a lot of keystone context16:43
cmurphyso if you can think of any or run across any let me know16:43
lbragstadi'll keep my eyes open16:43
ayoungcmurphy, so, my advice to people lately has been to start with code reviews, not bug fixes16:43
ayoungfind some thing they understand, and ask questions.16:43
ayoungNo +1-1 required16:43
cmurphyayoung: that's a good point16:44
kmallocayoung: that has always been my recommendation16:44
*** Leo_m has quit IRC16:44
ayoungand those questions usually lead to a discussion, which leads to the original poster sometimes saying "hey that is a good idea."16:44
kmallochowever, a lot of recent code reviews have been ... a little dense :)16:44
kmalloci think we're through the worst of that for now.16:44
cmurphyyeah, it would be a little flood-gate-y16:44
*** Leo_m has joined #openstack-meeting-alt16:45
*** iyamahat has quit IRC16:45
ayoungIf they want, and the author agrees, they can make that change for the original poster by updating the patch, and there there they go...16:45
ayoungGreat for Typos, and doc changes esp16:45
kmallocalso followup patches for nits/typos are good16:46
kmalloc100% would support someone wanting to submit their own patch to fix the things if they so desired like that16:46
ayoungkmalloc, I wish that had always been the norm here....sometimes I miss Brant,  sometimes I don't16:46
*** yamahata has quit IRC16:47
lbragstadslightly unrelated - but i have a couple patches up to oslo.context and oslo.policy that will make the scope_types work in keystone easier16:47
lbragstad#link https://review.openstack.org/#/c/611443/16:48
cmurphyso I'll definitely keep this in mind but also being able to see your code land is really motivating especially since a lot of these people are students16:48
ayounglbragstad, oooh, so does ozz16:48
lbragstad#link https://review.openstack.org/#/c/613635/16:48
lbragstadand #link https://review.openstack.org/#/c/614195/16:48
lbragstadthose things should make it easier for us to do complete user management with scope-types16:48
lbragstad(like the demo i did a week or two ago)16:49
ayoungI like, in general16:49
ayounghttps://review.openstack.org/#/c/613313/16:49
ayoungThat allows a much wider set of testing.  One thing  we can't do now:  check if the right project ID was set16:50
lbragstadnice - i'm on that review16:50
kmallocyeah that one has been on my list for a couple days16:50
ayounglike, we only cjheck the ID from the token, and assume a match.  That one thos, goes much further and allows a lot of target stuff16:50
ayoungthe one things we don't do is test via oslo-context.16:50
ayoungI'm working on a unit test for the checker code, so we can build it out for this one16:51
ayoungcoding features so you can talk about them during presentation in the summit is an interesting dynamic.  Its like "How should we do this right...oh, we need that..."16:52
kmallocwe should also expose the flatten mechanism as part of the policy check, like "flatten_target" inherent to olso.policy16:53
kmallocopt-in so we don't break anyone16:53
kmallocbut it would be a nice-to-have16:53
ayoungkmalloc, yeah, we need to move some of the mechanisms we build for the CLI into toolijng for others to use.  That one is the obvious one, aloth, for servicees, they tend to use context, which does that for you...sort of16:54
ayoungaloth.>altho16:54
lbragstadunrelated: does simo work at red hat?16:54
kmallocyes.16:54
ayounglbragstad, yep16:55
ayounglbragstad, still in my old group, that does IdM etc16:55
kmallocayoung: if you can get another pass by simo on the jwt thing16:55
ayounghappy to do so16:55
kmallocthnx16:55
lbragstadtiming isn't ideally, but i agree with cmurphy that it would be nice to get their eyes on the jwt thing one more time16:55
*** Leo_m has quit IRC16:55
kmalloci have one more review that i want to raise up as a potential thing16:55
lbragstadthanks ayoung and kmalloc16:55
kmallocfor folks to look at16:55
kmalloc#link https://review.openstack.org/#/c/613681/16:56
*** Leo_m has joined #openstack-meeting-alt16:56
ayoungSo... will JWT give us a way to do PKI type signing?16:56
kmallocthat requires some work, but i want some extra eyes to determine if a None header is within WSGI spec16:56
kmallocthe rest of the code should be "ok" otherwise.16:56
ayoungspecifically, I want one keystone to be able to sign a token, and for other services to be able to validate without forging them16:56
kmallocayoung: eventually. JOSE with asym encryption/validation16:56
kmallocbut that is a few steps outside of JWT addition16:57
cmurphyerm that's for other keystones to validate them, not other non-keystone services16:57
kmallocto keystone16:57
cmurphyright?16:57
kmallocit could be possible16:57
lbragstadyeah - that is noted specifically as an advantage of jwt16:57
ayoungcmurphy, anyojne should be able to validate....16:57
kmalloc3 minutes, time check16:57
ayoungthe only reason we send them back to keystone is because of the Fernet spec.  PKI tokens were validated in the services16:57
* kmalloc ducks out, food.16:58
lbragstadthe major hurdle is that services need roles16:58
kmallocbe back in -keystone post meeting.16:58
lbragstadin order to do rbac16:58
lbragstadand we don't include unbound things in the token payload16:58
ayoungcmurphy, and, one Keystone may not be a peer to the other keystone.  I was brainstorming some of this for the edge talk16:58
* ayoung needs to go find the slip of paper he was scribbling on with all these ideas16:59
lbragstadwe can take this to -keystone later, too16:59
lbragstadthanks for coming, all16:59
*** rossella_s has quit IRC16:59
lbragstad#endmeeting16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:59
openstackMeeting ended Tue Oct 30 16:59:55 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-10-30-16.00.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-10-30-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-10-30-16.00.log.html17:00
*** rossella_s has joined #openstack-meeting-alt17:01
*** rossella_s has quit IRC17:01
*** iyamahat has joined #openstack-meeting-alt17:01
*** rossella_s has joined #openstack-meeting-alt17:03
*** wxy| has quit IRC17:04
*** rossella_s has quit IRC17:11
*** tssurya has quit IRC17:19
*** yamahata has joined #openstack-meeting-alt17:19
*** lpetrut has joined #openstack-meeting-alt17:23
*** ccamacho has joined #openstack-meeting-alt17:23
*** yamamoto has quit IRC17:24
*** ttsiouts has quit IRC17:28
*** ttsiouts has joined #openstack-meeting-alt17:29
*** chhagarw has quit IRC17:29
*** kopecmartin is now known as kopecmartin|off17:30
*** derekh has quit IRC17:30
*** ttsiouts has quit IRC17:33
*** panda is now known as panda|off17:37
*** ayoung has quit IRC17:46
*** jcoufal has quit IRC17:53
*** cloudrancher has quit IRC18:01
*** cloudrancher has joined #openstack-meeting-alt18:02
*** yamamoto has joined #openstack-meeting-alt18:03
*** dpawlik has joined #openstack-meeting-alt18:03
*** e0ne has joined #openstack-meeting-alt18:10
*** yamamoto has quit IRC18:12
*** dustins has joined #openstack-meeting-alt18:13
*** dpawlik has quit IRC18:20
*** diablo_rojo has joined #openstack-meeting-alt18:24
*** e0ne has quit IRC18:25
*** lpetrut has quit IRC18:29
*** jcoufal has joined #openstack-meeting-alt18:34
*** dpawlik has joined #openstack-meeting-alt18:36
*** dpawlik has quit IRC18:40
*** e0ne has joined #openstack-meeting-alt19:13
*** rnoriega has quit IRC20:13
*** rnoriega has joined #openstack-meeting-alt20:14
*** gagehugo has left #openstack-meeting-alt20:24
*** priteau has quit IRC20:33
*** caboucha has quit IRC20:43
*** Leo_m has quit IRC20:51
*** tssurya has joined #openstack-meeting-alt20:58
*** cloudrancher has quit IRC20:59
*** cloudrancher has joined #openstack-meeting-alt21:00
*** erlon has quit IRC21:02
*** jcoufal has quit IRC21:06
*** raildo has quit IRC21:13
*** dustins has quit IRC21:16
*** e0ne has quit IRC21:18
*** munimeha1 has quit IRC21:55
*** ttsiouts has joined #openstack-meeting-alt21:55
*** ttsiouts has quit IRC22:04
*** ttsiouts has joined #openstack-meeting-alt22:05
*** david-lyle has quit IRC22:08
*** ttsiouts has quit IRC22:10
*** yamamoto has joined #openstack-meeting-alt22:10
*** yamamoto has quit IRC22:15
*** dklyle has joined #openstack-meeting-alt22:28
*** erlon has joined #openstack-meeting-alt22:35
*** e0ne has joined #openstack-meeting-alt22:49
*** tssurya has quit IRC22:51
*** tonyb has joined #openstack-meeting-alt23:03
*** e0ne has quit IRC23:13
*** tpsilva has quit IRC23:18
*** yamamoto has joined #openstack-meeting-alt23:23
*** chhagarw has joined #openstack-meeting-alt23:25
*** chhagarw has quit IRC23:30
*** erlon has quit IRC23:35
*** erlon has joined #openstack-meeting-alt23:48
*** hongbin has quit IRC23:57

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