Tuesday, 2018-10-02

*** dtrainor_ has quit IRC00:04
*** macza has quit IRC00:04
*** jcoufal has joined #openstack-meeting-alt00:05
*** jcoufal has quit IRC00:11
*** slaweq has joined #openstack-meeting-alt00:11
*** slaweq has quit IRC00:15
*** rossella_s has quit IRC00:18
*** rossella_s has joined #openstack-meeting-alt00:19
*** tetsuro has joined #openstack-meeting-alt00:21
*** rossella_s has quit IRC00:36
*** rossella_s has joined #openstack-meeting-alt00:37
*** dpawlik has joined #openstack-meeting-alt00:45
*** dpawlik has quit IRC00:50
*** rossella_s has quit IRC00:54
*** rossella_s has joined #openstack-meeting-alt00:54
*** dpawlik has joined #openstack-meeting-alt01:01
*** rossella_s has quit IRC01:03
*** rossella_s has joined #openstack-meeting-alt01:04
*** dpawlik has quit IRC01:05
*** efried has joined #openstack-meeting-alt01:15
*** ijw has joined #openstack-meeting-alt01:16
*** ijw has quit IRC01:21
*** cloudrancher has quit IRC01:22
*** hongbin has joined #openstack-meeting-alt01:23
*** cloudrancher has joined #openstack-meeting-alt01:23
*** Leo_m has joined #openstack-meeting-alt01:29
*** Leo_m has quit IRC01:29
*** rossella_s has quit IRC01:30
*** rossella_s has joined #openstack-meeting-alt01:30
*** yamahata has quit IRC01:39
*** iyamahat has quit IRC01:39
*** efried has quit IRC02:10
*** efried1 has joined #openstack-meeting-alt02:10
*** efried1 is now known as efried02:12
*** rossella_s has quit IRC02:14
*** rossella_s has joined #openstack-meeting-alt02:14
*** rossella_s has quit IRC02:25
*** rossella_s has joined #openstack-meeting-alt02:26
*** yamamoto has quit IRC02:32
*** yamamoto has joined #openstack-meeting-alt02:33
*** yamamoto has quit IRC02:37
*** rossella_s has quit IRC02:52
*** rossella_s has joined #openstack-meeting-alt02:52
*** dpawlik has joined #openstack-meeting-alt03:02
*** yamamoto has joined #openstack-meeting-alt03:05
*** dpawlik has quit IRC03:06
*** dave-mccowan has quit IRC03:07
*** yamamoto has quit IRC03:12
*** hongbin has quit IRC03:15
*** dpawlik has joined #openstack-meeting-alt03:17
*** dpawlik has quit IRC03:22
*** rossella_s has quit IRC03:22
*** rossella_s has joined #openstack-meeting-alt03:23
*** diablo_rojo has quit IRC03:27
*** rossella_s has quit IRC03:28
*** rossella_s has joined #openstack-meeting-alt03:28
*** ijw has joined #openstack-meeting-alt03:36
*** yamamoto has joined #openstack-meeting-alt03:47
*** rossella_s has quit IRC04:02
*** rossella_s has joined #openstack-meeting-alt04:02
*** rossella_s has quit IRC04:12
*** rossella_s has joined #openstack-meeting-alt04:14
*** rossella_s has quit IRC04:26
*** rossella_s has joined #openstack-meeting-alt04:28
*** rossella_s has quit IRC04:44
*** rossella_s has joined #openstack-meeting-alt04:44
*** rossella_s has quit IRC05:02
*** rossella_s has joined #openstack-meeting-alt05:02
*** e0ne has joined #openstack-meeting-alt05:06
*** e0ne has quit IRC05:06
*** rossella_s has quit IRC05:16
*** rossella_s has joined #openstack-meeting-alt05:16
*** mtreinish has quit IRC05:17
*** dpawlik has joined #openstack-meeting-alt05:18
*** mtreinish has joined #openstack-meeting-alt05:21
*** rossella_s has quit IRC05:22
*** dpawlik has quit IRC05:23
*** rossella_s has joined #openstack-meeting-alt05:24
*** rossella_s has quit IRC05:34
*** rossella_s has joined #openstack-meeting-alt05:34
*** dpawlik has joined #openstack-meeting-alt05:34
*** dpawlik has quit IRC05:39
*** rossella_s has quit IRC05:44
*** rossella_s has joined #openstack-meeting-alt05:49
*** dpawlik has joined #openstack-meeting-alt06:00
*** rossella_s has quit IRC06:01
*** rossella_s has joined #openstack-meeting-alt06:01
*** rossella_s has quit IRC06:03
*** rossella_s has joined #openstack-meeting-alt06:04
*** slaweq has joined #openstack-meeting-alt06:11
*** slaweq has quit IRC06:16
*** yamamoto has quit IRC06:27
*** yamamoto has joined #openstack-meeting-alt06:27
*** d0ugal has joined #openstack-meeting-alt06:32
*** dims has quit IRC06:38
*** dims has joined #openstack-meeting-alt06:44
*** dims has quit IRC06:48
*** dims has joined #openstack-meeting-alt06:51
*** tetsuro has quit IRC06:53
*** e0ne has joined #openstack-meeting-alt07:00
*** rcernin has quit IRC07:01
*** dpawlik has quit IRC07:04
*** slaweq has joined #openstack-meeting-alt07:07
*** kopecmartin|off is now known as kopecmartin|ruck07:17
*** dpawlik has joined #openstack-meeting-alt07:24
*** mpiwowarczy has quit IRC07:32
*** tetsuro has joined #openstack-meeting-alt07:38
*** slaweq has quit IRC07:39
*** slaweq has joined #openstack-meeting-alt07:49
*** iyamahat has joined #openstack-meeting-alt07:51
*** priteau has joined #openstack-meeting-alt07:51
*** d0ugal has quit IRC07:53
*** jtomasek has joined #openstack-meeting-alt08:04
*** alexchadin has joined #openstack-meeting-alt08:11
*** derekh has joined #openstack-meeting-alt08:37
*** alexchadin has quit IRC08:45
*** ttsiouts has joined #openstack-meeting-alt08:51
*** masahito has joined #openstack-meeting-alt08:58
*** bertys has joined #openstack-meeting-alt08:59
*** alexchadin has joined #openstack-meeting-alt08:59
priteau#startmeeting blazar09:00
openstackMeeting started Tue Oct  2 09:00:17 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
*** ttsiouts has quit IRC09:00
priteau#topic Roll call09:00
*** openstack changes topic to "Roll call (Meeting topic: blazar)"09:00
masahitoo/09:00
tetsuroo/09:00
bertyso/09:00
priteauHello everyone09:01
priteauI don't have a big agenda today09:01
priteau1. Project Update @ Berlin Summit09:01
priteau2. OpenStack-wide Goals09:01
priteau3. AOB09:01
priteau#topic Project Update @ Berlin Summit09:01
*** openstack changes topic to "Project Update @ Berlin Summit (Meeting topic: blazar)"09:01
priteauI have registered for the summit and sent the proof to confirm our project update slot09:02
*** ttsiouts has joined #openstack-meeting-alt09:02
priteauWe are on the official schedule now09:03
priteau#link https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22775/blazar-project-update09:03
priteauTuesday, November 13, 11:25am-11:45am09:03
bertyspriteau: Thanks, I have registered as well.09:03
masahitoThanks09:04
priteauDoes this time work for you masahito and bertys?09:04
priteauThis is at the beginning of the summit09:04
masahitoNo problem.09:04
priteauAlmost right after the keynotes09:04
bertysworks for me as well09:04
priteaubertys: Could you please update your speaker profile which shows up on the page?09:05
priteauYou can put a picture and a little bio09:05
priteauIt's manage within your OpenStack profile09:06
priteau*managed*09:06
bertyspriteau: ok, will do, no problem09:06
priteauUnless you want to remain incognito ;-)09:06
priteauI am going to ask whether there is a specific slide deck template to follow, and if not use the previous one09:07
priteauThen I will circulate the slides so we can start contributing09:08
priteauI haven't yet looked closely at the summit schedule, anything interesting?09:09
masahitome neither.09:09
priteauWe should see a draft forum schedule next week (October 10)09:11
priteauMoving on to the next topic09:11
priteau#topic OpenStack-wide Goals09:11
*** openstack changes topic to "OpenStack-wide Goals (Meeting topic: blazar)"09:11
priteauOn the ML there is already a discussion of goals for the T release09:12
priteau#link http://lists.openstack.org/pipermail/openstack-dev/2018-September/135097.html09:13
priteauInterestingly the discussion has focused around openstackclient support09:13
priteauWe are planning to make progress on our own OSC plugin this cycle so it should give us a head start for the T cycle!09:14
masahitoNice09:14
priteauAnd for Stein, we need to start working on our upgrade checker09:15
priteau#link https://governance.openstack.org/tc/goals/stein/upgrade-checkers.html09:15
masahitoWe have less CLI commands. It's easy to migrate to OSC.09:15
priteaumasahito: It's not hard work but we still need to take the time to do it :-)09:16
bertyspriteau: I guess you already saw the feedback from Matt @ https://storyboard.openstack.org/#!/story/2003657, right ?09:17
priteaubertys: I had not, thanks for letting me know.09:17
priteauI see that there is now a oslo.upgradecheck library09:18
*** slaweq has quit IRC09:19
*** yamamoto has quit IRC09:19
bertysright, has been accepted https://github.com/openstack/oslo.upgradecheck & https://review.openstack.org/#/c/602483/09:19
priteauSeems like the agreement is to have a noop checker if there is nothing to watch out for upgrade09:20
*** yamamoto has joined #openstack-meeting-alt09:20
priteauThat's from the Week R-29 Update09:20
*** slaweq has joined #openstack-meeting-alt09:21
priteau#link https://review.openstack.org/#/c/603465/09:21
priteauMonasca's noop upgrade checker09:21
masahitopriteau: do you have a list of issues you hit while you upgrade the Chameleon Cloud?09:21
masahitoIf there is, backporting from the list is nice.09:22
priteaumasahito: Most issues were linked to all our local changes, including DB schema changes. I don't recall if there was an issue with upstream code.09:22
priteauBut I will check.09:22
masahitoOf course, noop checker is nice, too. because Blazar is operator friendly project :-)09:22
priteauIt may be required for all projects to have a checker, even if noop, by the end of the cycle09:24
*** yamamoto has quit IRC09:24
priteauIf I can find some time during the week I can try to push an initial patch09:25
*** rdopiera has joined #openstack-meeting-alt09:26
priteauAnything else to discuss on this topic?09:26
masahitonothing from my side09:26
priteau#topic AOB09:27
*** openstack changes topic to "AOB (Meeting topic: blazar)"09:27
priteauI see there's been some discussion on the approach to use for placement client in https://review.openstack.org/#/c/584625/09:27
masahitopriteau: Thanks for putting it on the table09:28
priteauFor what it's worth, my opinion is that we should move forward with tetsuro's code. We can always change it to use a common library if one is created09:28
tetsuroAgreed.09:29
masahito+109:29
priteaubertys: ?09:30
bertyspriteau: My original intention was to review tetsuro's patches once https://review.openstack.org/#/c/527728/ is merged09:31
priteauBut do you agree with the approach of writing our own client code for now, so we can make rapid progress?09:32
priteauCreating a common library that can be used by multiple projects is going to require time09:34
bertysI do not want to block making progress on blazar side so I will provide some feedback this week09:34
priteauThanks09:35
tetsurobertys: Thanks09:35
priteauAny other AOB topics?09:36
masahitoI have few updates.09:36
masahito1. pushed scenario tests for the instance reservations. The scenario comes basically from host reservation's one.09:36
masahitohttps://review.openstack.org/#/q/topic:bug/1714438+(status:open+OR+status:merged)09:37
masahito2. Updated patches for resource-availability-api09:37
masahitoThat's from my side.09:37
priteauThank you masahito. I started to review the instance reservation patches earlier this morning :-)09:38
masahitothanks09:39
tetsuroAh, great work on instance scenario tests, thank you so much.09:39
priteautetsuro: Anything new on your side?09:40
tetsuroSince I was a bit worried about moving on Placement related changes without instance scenario tests09:40
tetsuroNot really new from me this week, sorry.09:41
masahitotetsuro: I'm planning to add more scenario once we've added a new tag to the tempest plugin for stable/queens.09:42
priteauMy AOB is that Chameleon needs network resource reservation, so I am going to work on prototyping an approach09:42
*** yamamoto has joined #openstack-meeting-alt09:42
masahitopriteau: I'm testing our ideas of floating IP reservation in the PTG in my local to find out pros/cons.09:43
masahitopriteau: Which are you working on floatingIP or VLAN?09:44
priteauThat's great. I am going to focus more on the VLAN side of things.09:44
masahitoGreat. We can work for it in parallel :-)09:45
priteauPlease keep me updated as you make progress09:46
masahitosure09:46
priteauAnything else for AOB? If not we can end the meeting early and go back to work!09:47
masahitoah, just fyi09:49
masahitoI noticed tetsuro became officially placement-core.09:49
masahitocongrats!!09:49
tetsuroYes, that happened last Thursday. Thanks.09:50
priteauCongratulations tetsuro!09:50
bertystetsuro: congrats and keep up the good work!09:50
tetsuroYup, thanks. Never let you down.09:51
priteauI don't hear anything else. Let's end early.09:53
priteauHave a good week everyone, thanks for joining.09:53
priteau#endmeeting09:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:53
openstackMeeting ended Tue Oct  2 09:53:13 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/blazar/2018/blazar.2018-10-02-09.00.html09:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/blazar/2018/blazar.2018-10-02-09.00.txt09:53
openstackLog:            http://eavesdrop.openstack.org/meetings/blazar/2018/blazar.2018-10-02-09.00.log.html09:53
masahitoThanks. bye09:53
tetsurothanks!09:53
*** bertys has quit IRC09:55
*** ttsiouts has quit IRC10:01
*** ttsiouts has joined #openstack-meeting-alt10:03
*** masahito has quit IRC10:13
*** dpawlik has quit IRC10:16
*** dpawlik has joined #openstack-meeting-alt10:17
*** yamamoto has quit IRC10:40
*** yamamoto has joined #openstack-meeting-alt10:40
*** d0ugal has joined #openstack-meeting-alt11:01
*** dave-mccowan has joined #openstack-meeting-alt11:02
*** ttsiouts has quit IRC11:03
*** ttsiouts has joined #openstack-meeting-alt11:03
*** ttsiouts has quit IRC11:08
*** e0ne has quit IRC11:10
*** ttsiouts has joined #openstack-meeting-alt11:13
*** jtomasek has quit IRC11:16
*** jtomasek has joined #openstack-meeting-alt11:16
*** tetsuro has quit IRC11:18
*** jtomasek has joined #openstack-meeting-alt11:18
*** alexchadin has quit IRC11:21
*** ganso has joined #openstack-meeting-alt11:24
*** ttsiouts has quit IRC11:25
*** tbarron has joined #openstack-meeting-alt11:25
*** ganso has left #openstack-meeting-alt11:25
*** e0ne has joined #openstack-meeting-alt11:50
*** dtrainor has joined #openstack-meeting-alt11:54
*** yamamoto has quit IRC12:07
*** yamamoto has joined #openstack-meeting-alt12:08
*** ttsiouts has joined #openstack-meeting-alt12:10
*** yamamoto has quit IRC12:12
*** beagle is now known as beagles12:16
*** haleyb has quit IRC12:23
*** haleyb has joined #openstack-meeting-alt12:27
*** _pewp_ has quit IRC12:30
*** _pewp_ has joined #openstack-meeting-alt12:31
*** rossella_s has quit IRC12:32
*** raildo has joined #openstack-meeting-alt12:32
*** jcoufal has joined #openstack-meeting-alt12:32
*** markvoelker has joined #openstack-meeting-alt12:32
*** rossella_s has joined #openstack-meeting-alt12:33
*** raildo_ has joined #openstack-meeting-alt12:34
*** raildo has quit IRC12:37
*** yamamoto has joined #openstack-meeting-alt12:51
*** tssurya has joined #openstack-meeting-alt12:53
*** d0ugal has quit IRC13:00
*** d0ugal has joined #openstack-meeting-alt13:21
*** ttsiouts has quit IRC13:23
*** dustins has joined #openstack-meeting-alt13:27
*** rossella_s has quit IRC13:30
*** e0ne has quit IRC13:32
*** ttsiouts has joined #openstack-meeting-alt13:33
*** rossella_s has joined #openstack-meeting-alt13:33
*** dangtrinhnt_x has joined #openstack-meeting-alt13:34
*** d0ugal has quit IRC13:36
*** tpsilva has joined #openstack-meeting-alt13:39
*** raildo_ is now known as raildo13:39
*** d0ugal has joined #openstack-meeting-alt13:54
*** hongbin has joined #openstack-meeting-alt13:57
*** dustins has quit IRC13:58
*** ttsiouts has quit IRC13:58
*** dustins has joined #openstack-meeting-alt14:01
*** e0ne has joined #openstack-meeting-alt14:02
*** amotoki_ is now known as amotoki14:04
*** cloudrancher has quit IRC14:07
*** cloudrancher has joined #openstack-meeting-alt14:08
*** ttsiouts has joined #openstack-meeting-alt14:12
*** munimeha1 has joined #openstack-meeting-alt14:24
*** liuyulong has joined #openstack-meeting-alt14:29
*** liuyulong has quit IRC14:42
*** ttsiouts has quit IRC14:46
*** dangtrinhnt_x has quit IRC14:56
*** ttsiouts has joined #openstack-meeting-alt15:00
*** toabctl has joined #openstack-meeting-alt15:03
*** gagehugo has joined #openstack-meeting-alt15:04
*** yamamoto has quit IRC15:10
*** yamamoto has joined #openstack-meeting-alt15:10
*** d0ugal has quit IRC15:12
*** d0ugal has joined #openstack-meeting-alt15:12
*** Leo_m has joined #openstack-meeting-alt15:15
*** e0ne has quit IRC15:19
*** dpawlik has quit IRC15:22
*** ircuser-1 has joined #openstack-meeting-alt15:25
*** dave-mccowan has quit IRC15:27
*** ttsiouts has quit IRC15:42
*** macza has joined #openstack-meeting-alt15:43
*** macza_ has joined #openstack-meeting-alt15:47
*** gyee has joined #openstack-meeting-alt15:49
*** macza has quit IRC15:51
*** jcoufal has quit IRC15:59
*** jgrassler has joined #openstack-meeting-alt15:59
cmurphy#startmeeting keystone16:00
openstackMeeting started Tue Oct  2 16:00:11 2018 UTC and is due to finish in 60 minutes.  The chair is cmurphy. 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
gagehugoo/16:00
jgrasslero/16:00
cmurphy#link https://etherpad.openstack.org/p/keystone-weekly-meeting agenda16:00
cmurphylbragstad is starting his 18-year indentured servitute so i am standing in16:00
cmurphyplease add things to the agenda16:01
knikollao/16:01
cmurphy#topic Outreachy project submissions16:02
*** openstack changes topic to "Outreachy project submissions (Meeting topic: keystone)"16:02
cmurphy#link https://etherpad.openstack.org/p/keystone-outreachy-proposals keystone outreachy proposals16:02
cmurphyI started an etherpad to draft outreachy project submissions, it's a little more structured than the brainstorming etherpad16:03
hrybackio/16:03
*** jcoufal has joined #openstack-meeting-alt16:03
cmurphythere's one draft there, feel free to give me feedback on it16:03
cmurphyand placeholders for kmalloc's ideas16:04
cmurphyand if you plan to propose other projects feel free to add them there16:04
cmurphyany thoughts on that topic?16:04
*** ayoung has joined #openstack-meeting-alt16:05
ayoungWhat is the time frame for submissions?16:05
cmurphyayoung: deadline is Oct 16 I think16:06
cmurphybut they start accepting them and letting applicants apply for them before that iirc so it's good to get them in asap16:06
knikollai like the tasks in there16:06
cmurphyayoung: interesting, would be good to have a spec for that idea before submitting it as a project i think16:07
gagehugoheh "REALLY motivated"16:07
ayoungcmurphy, I'll work on it16:08
cmurphyokay thanks ayoung16:08
ayoungwe've discussed it a bunch, so I think we should be able to come up with something clear fairly quickly on the keystone side16:08
ayoungclient might take more work, but that would probably be follow on16:09
cmurphyokay, let's move on, we can come back to this in open discussion if we like16:10
cmurphy#topic Application credentials fine grained access control spec16:10
*** openstack changes topic to "Application credentials fine grained access control spec (Meeting topic: keystone)"16:10
cmurphy#link http://specs.openstack.org/openstack/keystone-specs/specs/keystone/stein/capabilities-app-creds.html spec16:10
jgrasslerYeah, that one...16:10
cmurphyso jgrassler has let me know that he has a bit too much on his plate to make this feasible for him to accomplish16:11
ayoungOutreachy!16:11
cmurphy:) i worry this is a little too involved for an outreachy project16:11
ayoungHeh.  You Think?16:11
jgrasslerI wouldn't have phrased it quite so diplomatically ("I fear I have to flake out on this"), but yes, that's the gist of it.16:11
cmurphyi wanted to ask if anyone was clamoring for a new project or would want to split up the work with me16:11
ayoungcmurphy, I'll help16:12
jgrasslerayoung: yeah...the thought had crossed my mind, too during the previous agenda item :-)16:12
cmurphyayoung: awesome, thanks16:12
ayoungthe fine grained stuff was kindof something I wanted16:12
cmurphyalso i wanted to thanks jgrassler for getting the spec in shape, that was no small effort16:12
ayoungcmurphy, should I update this spec to support it: https://review.openstack.org/#/c/456974/16:13
ayoungRole check on body key16:13
jgrasslerThanks :-) I'd meant to write the code at some stage, though...16:13
ayoungthat was originally for the policy-in-rbac,16:13
cmurphyayoung: i'd rather we stick to the spec we agreed to on this iteration16:13
ayoungcmurphy, agreed.  I meant as a mitigation for things that spec couldn't cover, I could rewrite this spec to be "here's how we do that in the future"16:14
ayoungthings like the actions api in nova that might not map perfectly to URL+Verb along16:14
ayoungalone16:14
ayoungOr are we confident we can get away without the body checks.  I'm ok deferring it16:15
cmurphyi think this iteration doesn't drastically need it because we're still doing the policy checks as well which cover the different policies for different bodies16:16
ayoung++16:16
cmurphyanyways, thanks jgrassler and ayoung16:17
ayoungI'll keep it in mind.  Anyway, I can tackley the SQL and API changes16:17
cmurphy++16:17
cmurphy#topic Shared-Nothing Keystone for Multisite16:17
*** openstack changes topic to "Shared-Nothing Keystone for Multisite (Meeting topic: keystone)"16:17
cmurphyayoung: i'm guessing this is you16:17
ayoungIs App Creds Flaskified yet?16:17
cmurphynot yet16:17
ayoungOK, so SHared nothing is another way to say "different databases"16:18
ayoungi.e.  we put a keystone server at a region, and it handles only requests for that reqion16:18
ayoungand I have a couple reviews outstanding in support of this approach.  I'd really appreciate getting any battles about them out of the way soonish16:18
ayoungI have a spec, too, that I am resurrecting, based on the Federated ID changes, that should help multis-site16:19
*** toabctl has quit IRC16:19
ayoungbasically, the Fed Query APIs let  a user ask "what would Keystone do about this REMOTE_USER/REMOTE_GROUPS set of variables16:19
ayoungit will support pre-population of values, and it will support using the Keystone data from an Application as well16:20
ayoungi.e. Identity as a Service?16:20
ayoungor something like that16:20
ayoungSo, please look at them, and tell me what you don't like16:20
cmurphyayoung: we have pushed back really hard on allowing user-set IDs and I don't fully understand the reasoning this is needed now, why was the predictable ID not sufficient?16:20
cmurphyi think kmalloc had strong objections too16:21
ayoungcmurphy, user-set IDs for Domain is to give us a top-level division between regions16:21
ayoungit is expected that only the domain_id will be user-set,16:21
ayoungnot the userids, or project ids16:21
ayoungso, I am kindof sticking with kmalloc 's reasoning on the majority16:21
ayoungdomains are a little different, in that the domain_id is used to generate the user-id in LDAP and, with the other path, Federation16:22
ayoungit also lets us say "this domain is at this regions, that domain is at that region" in a central server, and have the rest of the data be local to the regional keystone servers16:23
ayoungkmalloc, has since given his approval, at least in IRC, to this approach16:23
ayoungIdPs are also (iirc) allowed to have user-set Identifiers, which will let us have a unified approach to identity across the multi-sites16:24
ayoungcmurphy, any real objection, or just wondering "why now?"16:24
cmurphyayoung: mostly wondering why16:24
ayoungcmurphy, cool.16:25
cmurphyayoung: i will read the spec and ask you more questions16:25
ayoung++16:25
ayoungcmurphy, we have at least 2 customers that are tackling this problem and I would like to set them up for success16:26
ayoungI'm willing to listen to any and all wisdom on how to handle multi-site when you can't scale galera to all of the nodes16:26
ayoungaccording to what I've heard, galera will cover ~ 9 nodes, which, if you HA at a site with 3 msql instances, lets you get up to a 3 site cluster16:27
ayoungbut, if galera goes down, you've lost the the whole cluster16:27
ayoungand that is a non-rare occurrence16:27
ayoungSo the thought experiement is:  what if we have a hub-and-spoke model, and try to minimize the amount of data to keep in sync between them16:28
ayoungat the hub, we would have keystone and the minimal service catalog with the regional keystone only16:28
ayounghub would also have a domain-to-region mapping...16:29
ayoungand I don;'t have a good answer on how to do that today16:29
cmurphyi think i'm missing why you need a domain to region mapping, one domain per region doesn't fit most use cases16:30
ayoungAnyway, that is the goal, and I am looking for input on how to acheive it, or smart alternatives that are not just "completely separate openstack deployments"16:30
ayoungcmurphy, so, the domain-to-region does not need to be one-to-one16:31
cmurphyah16:31
ayounginstead, it is a way of saying "if this domain is linked to this region, this regional keystone owns the data in it"16:31
cmurphyso kind of like a catalog for your regions16:32
ayoungI think the Federated domain, where the users are mapped, would still be owned by the central16:32
ayoungcmurphy, exactly, yes16:32
ayoungcmurphy, I would only put the identity servers into the central catalog, though16:32
ayoungif you want to see what is really supported there (nova, sahara, whatever) go to that Keystone server and look at the catalog16:33
ayoungSo...I'm done16:35
cmurphyanyone have questions for ayoung ?16:36
cmurphy#topic open discussion16:36
*** openstack changes topic to "open discussion (Meeting topic: keystone)"16:36
cmurphyfyi i won't be at office hours16:36
kmallocO/16:37
cmurphykmalloc we were talking about ayoung's explicit_domain_id plan16:37
kmallocReading backlog16:38
kmallocGimme a sec16:38
kmalloci fall back to the oath model16:39
ayoungOaf?16:39
kmallocand predictable ids, meaning it's not "supplied" but it is something we predictably generate16:39
kmallocdomains being the separate case16:40
kmallocmeaning we need to allow some level of autoprovisioning or mechanism to supply a known domain id.16:40
kmallocoath - yahoo folks doing the federation16:40
kmallocthe domain-to-region mapping is the key that way16:40
kmalloci don't see an issue with ayoung's approach architecturally within keystone16:41
kmallocand i am willing to cede a minimal level of keystone-auto-id-owning to make the model work16:42
ayoung#link http://superuser.openstack.org/articles/massive-hyperscale-insfrastructure-openstack/16:42
kmallocit is a real concern in the direction everything is taking16:42
cmurphycool, i'll look closer at it soon16:42
ayounglooking for design docs16:43
kmalloci am also ok if a local keystone generates a local "id" that is combined with a specific local domain to generate the ultimate user-id.16:43
kmallocand the "generated local-id" then is transmitted to the remote keystones, meaning the id, pending the domain-id being in sync, would be consistent between deployments16:44
ayoungso...sync is a problem16:44
kmallocthat is assuming a single keystone is the sole owner of a user resource though... so no a->b->a->c->a16:44
ayoungright now, what we could do is have a listener16:44
kmallocjust a->c, a->b....16:44
ayoungthat would try and talk to a remote server, but if that server is down, we need to hold on to the changes16:45
kmalloci am ok with a "domains must be made and configured when a federated source of id is configured"16:45
ayoungor, have some way to "requery all since X" when the remote site comes back up16:45
kmallocthere is work to do to trust a source of id, one step may be making a domain.16:45
ayoungso, I am really trying to avoid data sync.  THus, limiting it to domains, and the rest be "provisioned on demand with predicatble IDS"16:45
ayoungkeeping Federated configuration (IDP etc) in sync is a low risk16:46
ayoungusers and project assignements are much more likely to be dropped16:46
kmallocthe goal is to avoid needing to sync everything. i don't want to sync domains, i am inclined to say operationally, make domain X, and configure IDP as trusted and linked to domain x16:46
kmallocit is part of the setup.16:46
ayoungso, the other part is "if we need info from Region X to work with Region Y, use K2K"16:47
ayoungand now we have some modicum of a framework to keep the assignements we need in sync16:48
kmallocthat is largely what we've been driving at. or "central IDP" and locally assignments are derived from IDP info (on demand) or concretely set.16:48
ayounglike, DomainXY maps to Domain Y16:48
kmallocthe central idp may be keystone, may be something else with advanced mapping in the region-local keystones16:48
ayoungI'm thinking specifically of knikolla 's use cases where the Cinder Server is owned by one Keystone, and the Nova server by another16:49
kmallocnothing says you still can't have a central source of ID16:49
kmallocwhich in knikolla's case, right now is a keycloak.16:50
kmallocthe proxy/k2k bits for service federation is separate from strict id federation16:50
kmallocdon't try to over engineer a single solution16:50
ayoungcmurphy, does this make sense?16:50
kmallocit is likely they are related (lean on similar tech) but are setup with some separation.16:51
kmallocsince the concerns are slightly different16:51
kmallocautoprovision, consistent/predictable ids is part of it16:51
cmurphyayoung: so far yes, though I'm still not 100% on why plain k2k isn't sufficient16:51
kmallocbut you have to look at user->service interaction and service->service interactions16:51
kmallocso, k2k can fill s->s (on behalf of the user)16:52
kmallocbut typically users will go idp->[auth through keystone]->Nova (or similar) and not have to bounce through k2k16:52
ayoungOne thing we can't do today is tell a user "you can only use this region's servers"16:53
kmallocrealistically, we're talking about changing k2k to more of "it isn't specifically a keystone you're talking to, it is any form of ID"16:53
ayounghowever, if the regional keystone is the only thing that can supply tokens for those servers, you now have an auth-point for limiting access16:53
ayoungcan't do that solely with K2k16:53
ayoungbut K2K would be useful for then saying "OK, now allow user U2 to use this nova as well"16:54
cmurphyayoung: we could give them a mapping that only maps to the domains in one region16:54
cmurphybut i guess you're saying the user can't discover that16:54
kmalloccmurphy: correct.16:54
ayoungService catalog is not used to enforce, either16:55
kmallocand should not be used to enforce*16:56
ayoungso a user can use an endpoint not in their catalog if the token is still valid16:56
ayoungSo,  say we have 3 tiers (Gold, Silvern Bronze)16:56
cmurphy3 minutes left16:57
ayoungdo it as 3 regions, each with their own keystone, each with a distinct service catalog16:57
kmallocthe enforcement should not be predicated on the SC, the SC may communicate what is really enforced (I worry about shipping the SC around as auth[z] data)16:57
ayoungthe only time you need to do K2K is to set up an arraingement that cuts horizontally, and that should be owned by one of the regions16:57
kmallocall of this is enhancements to how keystone does federation and how sources of IDentity are handled.16:58
cmurphytimes up17:00
kmallocthe end goal is: source of identity -> keystone, and keystone is locally independant/not synchronized.17:00
cmurphy#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:00
openstackMeeting ended Tue Oct  2 17:00:09 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-10-02-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-10-02-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-10-02-16.00.log.html17:00
kmallocthanks for chairing the meeting cmurphy17:00
cmurphyyw17:00
*** iyamahat has quit IRC17:01
*** gagehugo has left #openstack-meeting-alt17:02
*** derekh has quit IRC17:03
*** rossella_s has quit IRC17:12
*** rossella_s has joined #openstack-meeting-alt17:12
*** cloudrancher has quit IRC17:24
*** cloudrancher has joined #openstack-meeting-alt17:25
*** iyamahat has joined #openstack-meeting-alt17:26
*** rdopiera has quit IRC17:29
*** rossella_s has quit IRC17:30
*** rossella_s has joined #openstack-meeting-alt17:34
*** munimeha1 has quit IRC17:47
*** priteau has quit IRC17:47
*** dpawlik has joined #openstack-meeting-alt17:48
*** diablo_rojo has joined #openstack-meeting-alt17:48
*** tssurya has quit IRC17:52
*** dpawlik has quit IRC17:53
*** dpawlik has joined #openstack-meeting-alt18:09
*** dpawlik has quit IRC18:14
*** smyers has quit IRC18:41
*** smyers has joined #openstack-meeting-alt18:49
*** Swami has joined #openstack-meeting-alt19:03
*** e0ne has joined #openstack-meeting-alt19:32
*** diablo_rojo has quit IRC20:00
*** dave-mccowan has joined #openstack-meeting-alt20:09
*** dustins has quit IRC20:16
*** dave-mccowan has quit IRC20:30
*** dave-mccowan has joined #openstack-meeting-alt20:31
*** dave-mccowan has quit IRC20:36
*** cloudrancher has quit IRC20:41
*** ttsiouts has joined #openstack-meeting-alt20:55
*** raildo has quit IRC20:58
*** cloudrancher has joined #openstack-meeting-alt20:59
*** e0ne has quit IRC21:02
*** ttsiouts has quit IRC21:10
*** ttsiouts has joined #openstack-meeting-alt21:11
*** cloudrancher has quit IRC21:12
*** diablo_rojo has joined #openstack-meeting-alt21:22
*** ttsiouts has quit IRC21:27
*** ttsiouts has joined #openstack-meeting-alt21:28
*** Leo_m has quit IRC21:40
*** ijw has quit IRC21:57
*** ttsiouts has quit IRC22:04
*** jesusaur has quit IRC22:06
*** jesusaur has joined #openstack-meeting-alt22:11
*** jcoufal has quit IRC22:36
*** tpsilva has quit IRC22:55
*** pbourke has quit IRC23:02
*** pbourke has joined #openstack-meeting-alt23:02
*** hongbin has quit IRC23:02
*** yamamoto has quit IRC23:21
*** yamamoto has joined #openstack-meeting-alt23:22
*** yamamoto has quit IRC23:24
*** yamamoto has joined #openstack-meeting-alt23:24
*** yamamoto has quit IRC23:29
*** yamamoto has joined #openstack-meeting-alt23:30
*** yamamoto has quit IRC23:34
*** erlon has joined #openstack-meeting-alt23:36
*** macza_ has quit IRC23:37
*** macza has joined #openstack-meeting-alt23:37
*** macza has quit IRC23:42
*** Swami has quit IRC23:42
*** rcernin has joined #openstack-meeting-alt23:59

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