Tuesday, 2019-02-12

*** tetsuro has joined #openstack-meeting-alt00:25
*** TxGirlGeek has quit IRC00:25
*** macza has joined #openstack-meeting-alt00:29
*** tetsuro has quit IRC00:30
*** tetsuro has joined #openstack-meeting-alt00:32
*** macza has quit IRC00:34
*** tetsuro has quit IRC00:35
*** tetsuro_ has joined #openstack-meeting-alt00:35
*** chhagarw has joined #openstack-meeting-alt00:37
*** masahito has joined #openstack-meeting-alt00:39
*** iyamahat has joined #openstack-meeting-alt00:42
*** masahito has quit IRC00:45
*** chhagarw has quit IRC00:51
*** yamamoto has joined #openstack-meeting-alt00:51
*** gyee has quit IRC00:54
*** yamamoto has quit IRC00:56
*** hrybacki has joined #openstack-meeting-alt00:59
*** cosss_ has joined #openstack-meeting-alt00:59
*** sweston has joined #openstack-meeting-alt00:59
*** mrhillsman has joined #openstack-meeting-alt00:59
*** sdake has joined #openstack-meeting-alt01:01
*** macza has joined #openstack-meeting-alt01:08
*** ijw has joined #openstack-meeting-alt01:12
*** macza has quit IRC01:13
*** tetsuro has joined #openstack-meeting-alt01:20
*** tetsuro_ has quit IRC01:20
*** cloudrancher has joined #openstack-meeting-alt01:26
*** markvoelker has quit IRC01:30
*** markvoelker has joined #openstack-meeting-alt01:31
*** tetsuro has quit IRC01:35
*** tetsuro_ has joined #openstack-meeting-alt01:35
*** markvoelker has quit IRC01:35
*** sdake has quit IRC01:37
*** sdake has joined #openstack-meeting-alt01:40
*** sdake has quit IRC01:43
*** yamamoto has joined #openstack-meeting-alt01:53
*** tetsuro has joined #openstack-meeting-alt02:01
*** tetsuro_ has quit IRC02:01
*** TxGirlGeek has joined #openstack-meeting-alt02:04
*** lbragstad has quit IRC02:06
*** ijw has quit IRC02:07
*** macza has joined #openstack-meeting-alt02:22
*** macza has quit IRC02:27
*** macza has joined #openstack-meeting-alt02:27
*** hongbin has joined #openstack-meeting-alt02:29
*** cloudrancher has quit IRC02:29
*** macza has quit IRC02:31
*** markvoelker has joined #openstack-meeting-alt02:31
*** iyamahat has quit IRC02:35
*** TxGirlGeek has quit IRC02:36
*** yamamoto has quit IRC02:48
*** markvoelker has quit IRC03:05
*** yamamoto has joined #openstack-meeting-alt03:14
*** tetsuro has quit IRC03:22
*** tetsuro_ has joined #openstack-meeting-alt03:22
*** tetsuro has joined #openstack-meeting-alt03:26
*** tetsuro_ has quit IRC03:26
*** sdake has joined #openstack-meeting-alt03:40
*** TxGirlGeek has joined #openstack-meeting-alt03:57
*** dave-mccowan has quit IRC03:58
*** sdake has quit IRC03:59
*** markvoelker has joined #openstack-meeting-alt04:02
*** tetsuro has quit IRC04:05
*** lbragstad has joined #openstack-meeting-alt04:09
*** diablo_rojo has quit IRC04:09
*** janki has joined #openstack-meeting-alt04:30
*** markvoelker has quit IRC04:34
*** early has quit IRC05:14
*** early has joined #openstack-meeting-alt05:22
*** hongbin has quit IRC05:30
*** markvoelker has joined #openstack-meeting-alt05:32
*** TxGirlGeek has quit IRC05:56
*** early has quit IRC06:05
*** markvoelker has quit IRC06:05
*** vishakha has joined #openstack-meeting-alt06:08
*** early has joined #openstack-meeting-alt06:13
*** whoami-rajat has joined #openstack-meeting-alt06:19
*** sridharg has joined #openstack-meeting-alt06:20
*** e0ne has joined #openstack-meeting-alt06:24
*** e0ne has quit IRC06:35
*** ccamacho has quit IRC06:49
*** lbragstad has quit IRC06:50
*** markvoelker has joined #openstack-meeting-alt07:02
*** kopecmartin|off is now known as kopecmartin07:05
*** e0ne has joined #openstack-meeting-alt07:12
*** e0ne has quit IRC07:16
*** e0ne has joined #openstack-meeting-alt07:24
*** e0ne has quit IRC07:32
*** markvoelker has quit IRC07:35
*** jrbalderrama has joined #openstack-meeting-alt07:35
*** e0ne has joined #openstack-meeting-alt07:42
*** slaweq has joined #openstack-meeting-alt07:44
*** rdopiera has joined #openstack-meeting-alt07:45
*** jrbalderrama has quit IRC07:45
*** ccamacho has joined #openstack-meeting-alt07:58
*** ccamacho has quit IRC07:59
*** ccamacho has joined #openstack-meeting-alt07:59
*** masahito has joined #openstack-meeting-alt08:28
*** markvoelker has joined #openstack-meeting-alt08:32
*** e0ne has quit IRC08:35
*** e0ne has joined #openstack-meeting-alt08:37
*** e0ne has quit IRC08:38
*** e0ne has joined #openstack-meeting-alt08:46
*** e0ne has quit IRC08:48
*** e0ne has joined #openstack-meeting-alt08:54
*** iyamahat has joined #openstack-meeting-alt08:54
*** whoami-rajat has quit IRC08:54
*** e0ne has quit IRC08:56
*** priteau has joined #openstack-meeting-alt08:59
*** tetsuro has joined #openstack-meeting-alt09:00
priteau#startmeeting blazar09:00
openstackMeeting started Tue Feb 12 09:00:35 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:01
*** openstack changes topic to "Roll call (Meeting topic: blazar)"09:01
masahitoo/09:01
priteauHi masahito09:01
tetsurohi09:02
priteauHi tetsuro09:02
priteau#topic stein-3 milestone09:03
*** openstack changes topic to "stein-3 milestone (Meeting topic: blazar)"09:03
priteauWe're getting closer to the stein-3 milestone09:03
priteauI've been working on refreshing some bug fixes that were implemented for Chameleon09:04
*** panda|off is now known as panda09:04
priteauLooks like today I may be able to review the new floating IP patches and placement work09:05
*** tetsuro has quit IRC09:05
*** markvoelker has quit IRC09:05
*** tetsuro has joined #openstack-meeting-alt09:05
priteaumasahito: I suppose you won't have time to work on "reservation candidate API" in this cycle?09:06
masahitopriteau: right. sorry, no much time to work for it.09:07
priteauNo problem. Allocation API was much more important IMHO.09:07
tetsuro masahito: I left some questions on the floating IP spec. https://review.openstack.org/#/c/609302/09:08
masahitotetsuro: thanks! I'll check it later.09:09
priteauThanks tetsuro for your work on fixing https://bugs.launchpad.net/blazar/+bug/181459409:11
openstackLaunchpad bug 1814594 in Blazar "Failure to create a host" [High,In progress] - Assigned to Tetsuro Nakamura (tetsuro0907)09:11
priteauThis was a random find really. I usually deploy DevStack on CentOS7, but that day used Ubuntu16.04 which had hostnames configured differently.09:12
tetsuroGood catch, thanks a lot09:12
priteaumasahito: tetsuro's patches are at https://review.openstack.org/#/q/status:open+project:openstack/blazar+branch:master+topic:bug/181459409:12
masahitoI'll check it. thanks tetsuro09:14
priteauAnything else to discuss for stein-3?09:15
*** tetsuro has quit IRC09:16
*** tssurya has joined #openstack-meeting-alt09:17
*** tetsuro has joined #openstack-meeting-alt09:17
tetsuroThe network is unstable.. sorry.09:18
priteauNo worries09:18
priteauLet's move to AOB09:18
priteau#topic AOB09:19
*** openstack changes topic to "AOB (Meeting topic: blazar)"09:19
priteauAnything special to share today?09:19
*** iyamahat has quit IRC09:19
tetsuronop09:20
masahitoMay I ask tetsuro's patch if nothing?09:21
tetsurosure09:21
masahitoThe patch and its commit message looks good to me. Is it needed any upgrading script that changes host_name to hypervisor_name in DB?09:24
masahitoOr does the problem only happen in placement support?09:24
tetsuroAh09:24
tetsurogood question.09:25
tetsuroWait a moment plez09:25
*** e0ne has joined #openstack-meeting-alt09:25
*** e0ne has quit IRC09:26
priteaumasahito: Both values of `hypervisor_hostname` and `service_name` are already in the database for each compute host09:26
priteauWe're just getting another value to pass to placement09:26
priteauNo DB changes are required09:26
tetsuroYes, that's true09:26
tetsuropriteau is right, thanks09:26
masahitoOkay, thanks.09:27
priteauChameleon has been using a similar approach because it uses an experimental patch that allows host aggregates to be linked with hypervisor hostnames09:31
tetsuroGood to know09:32
priteauAny other questions?09:32
tetsurohttps://review.openstack.org/#/q/topic:bug/1813252 also needs more eyes.09:32
priteauThanks for the remidner09:33
tetsuroNot from me any more09:34
masahitoNothing from my side.09:35
priteauThank you for joining today.09:36
masahitoThanks09:36
priteauBye!09:36
tetsurothanks09:36
priteau#endmeeting09:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:36
openstackMeeting ended Tue Feb 12 09:36:56 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/blazar/2019/blazar.2019-02-12-09.00.html09:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/blazar/2019/blazar.2019-02-12-09.00.txt09:37
openstackLog:            http://eavesdrop.openstack.org/meetings/blazar/2019/blazar.2019-02-12-09.00.log.html09:37
*** tetsuro has quit IRC09:39
*** stephenfin_ is now known as stephenfin10:01
*** markvoelker has joined #openstack-meeting-alt10:02
*** derekh has joined #openstack-meeting-alt10:27
*** markvoelker has quit IRC10:35
*** purplerbot has joined #openstack-meeting-alt10:41
*** jtomasek has quit IRC10:46
*** obondarev has joined #openstack-meeting-alt10:52
*** jtomasek has joined #openstack-meeting-alt10:55
*** erlon has joined #openstack-meeting-alt11:07
*** lpetrut has joined #openstack-meeting-alt11:15
*** markvoelker has joined #openstack-meeting-alt11:32
*** tetsuro has joined #openstack-meeting-alt11:33
*** tetsuro has quit IRC11:46
*** erlon has quit IRC11:51
*** markvoelker has quit IRC12:05
*** raildo has joined #openstack-meeting-alt12:08
*** kaisers has quit IRC12:24
*** erlon has joined #openstack-meeting-alt12:29
*** kaisers has joined #openstack-meeting-alt12:31
*** panda is now known as panda|lunch12:32
*** masahito has quit IRC12:37
*** lpetrut has quit IRC12:38
*** lpetrut has joined #openstack-meeting-alt12:39
*** janki has quit IRC12:44
*** janki has joined #openstack-meeting-alt12:44
*** markvoelker has joined #openstack-meeting-alt13:02
*** yamamoto has quit IRC13:03
*** yamamoto has joined #openstack-meeting-alt13:08
*** panda|lunch is now known as panda13:13
*** yamamoto has quit IRC13:15
*** whoami-rajat has joined #openstack-meeting-alt13:22
*** sdake has joined #openstack-meeting-alt13:31
*** markvoelker has quit IRC13:35
*** yamamoto has joined #openstack-meeting-alt13:46
*** vishakha has quit IRC13:50
*** yamamoto has quit IRC13:56
*** e0ne has joined #openstack-meeting-alt13:56
*** vishakha has joined #openstack-meeting-alt13:58
*** gagehugo has joined #openstack-meeting-alt13:59
*** sdake has quit IRC14:03
*** dave-mccowan has joined #openstack-meeting-alt14:04
*** yamamoto has joined #openstack-meeting-alt14:06
*** yamamoto has quit IRC14:06
*** dave-mccowan has quit IRC14:09
*** liuyulong has joined #openstack-meeting-alt14:15
*** obondarev has quit IRC14:25
*** priteau has quit IRC14:26
*** erlon has quit IRC14:30
*** markvoelker has joined #openstack-meeting-alt14:32
*** lbragstad has joined #openstack-meeting-alt14:34
*** sdake_ has joined #openstack-meeting-alt14:37
*** e0ne has quit IRC14:44
*** carthaca has left #openstack-meeting-alt14:47
*** janki has quit IRC14:47
*** hongbin has joined #openstack-meeting-alt14:49
*** cloudrancher has joined #openstack-meeting-alt15:01
*** markvoelker has quit IRC15:05
*** ianychoi has quit IRC15:07
*** ianychoi has joined #openstack-meeting-alt15:07
*** e0ne has joined #openstack-meeting-alt15:09
*** hongbin has quit IRC15:09
*** hongbin has joined #openstack-meeting-alt15:12
*** yamamoto has joined #openstack-meeting-alt15:16
*** TxGirlGeek has joined #openstack-meeting-alt15:23
*** yamamoto has quit IRC15:25
*** wxy| has joined #openstack-meeting-alt15:26
*** liuyulong has quit IRC15:26
*** priteau has joined #openstack-meeting-alt15:31
*** e0ne has quit IRC15:33
*** jrbalderrama has joined #openstack-meeting-alt15:38
*** liuyulong has joined #openstack-meeting-alt15:41
*** e0ne has joined #openstack-meeting-alt15:41
*** macza has joined #openstack-meeting-alt15:42
*** diablo_rojo has joined #openstack-meeting-alt15:47
*** cloudrancher has quit IRC15:47
*** erlon has joined #openstack-meeting-alt15:52
lbragstad#startmeeting keystone16:00
openstackMeeting started Tue Feb 12 16:00:38 2019 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
*** erlon has quit IRC16:00
vishakhao/16:00
gagehugoo/16:00
cmurphyo/16:01
wxy|o/16:01
lbragstad#link https://etherpad.openstack.org/p/keystone-weekly-meeting16:01
lbragstadagenda ^16:01
lbragstadwe'll give folks a minute to join16:01
knikollao/16:02
*** markvoelker has joined #openstack-meeting-alt16:03
lbragstad#topic user survey questions16:03
*** openstack changes topic to "user survey questions (Meeting topic: keystone)"16:03
*** lpetrut has quit IRC16:03
lbragstadthe foundation emailed me asking about the upcoming user survey16:04
lbragstadthey usually check in each release and ask if we want to adjust the questions we have16:04
lbragstadi put the current questions/suggestions we have in etherpad16:06
kmalloco/16:06
lbragstadwhich - i don't think have been updated since stevemar was ptl16:06
lbragstadso about 2+ years16:06
lbragstadago16:06
lbragstadthe foundation needs to know if we want to change any of those answers by friday16:07
cmurphywould be nice if the survey could let people add specific comments, the multiple choice question is a little too generic to get really good feedback16:07
lbragstadcmurphy i agree - but i don't think that's an option16:07
cmurphyyeah16:07
knikollai would love to ask whether they're using sql backend or smth else16:08
knikollato see adoption of federation16:08
cmurphy++16:08
lbragstadfor which subsystems?16:08
lbragstadidentity?16:08
knikollayup16:08
cmurphya "what features and drivers are you using" in general would be nice16:08
lbragstadwith a text box for input?16:09
knikollaa multiple selection checkbox would work16:09
cmurphywe could probably enumerate it16:10
hrybackio/16:10
knikollaas I don't thin there'll be many with non-standard drivers.16:10
knikollathnk*16:10
lbragstadfeel free to add thoughts to the etherpad, too16:10
gagehugook16:10
lbragstadin case i'm not capturing this properly16:10
lbragstadi'm for dropping the per domain configuration question16:11
kmallocSQL, LDAP, Other (in-house developed)16:11
lbragstadthat one has been low on the survey response for a long time16:11
knikollalbragstad: ++16:11
kmallocper domain config is used some places, enough to warrant continued top level support/development but not enough to warrant an endless place on the survey16:12
knikolla++16:12
lbragstadenhancing policy is also pretty vague16:12
cmurphyheh16:12
lbragstadideas on how we can better gauge that area?16:13
kmallocassume policy is something we don't need to ask about until system scope and default roles land16:13
lbragstadoutside of "yes, make better plskthx"16:13
kmalloclike... the T cycle or so16:13
cmurphy"make policy unbad plz"16:13
hrybackilbragstad: we could ask people what areas of policy they want enhanced?16:13
hrybackilol cmurphy16:13
kmallocright now it is enough in flux to not ask folks right now16:13
knikollayup16:13
knikollai think policy is moving in the right direction16:13
kmalloccmurphy: you forgot "k thnx bye"16:13
cmurphylol16:14
lbragstadso omit it from the survey completely?16:14
kmalloclbragstad: yes16:14
knikollai'm with kmalloc on this one.16:14
kmallocadd it back in the cycle AFTER we have stabilized default roles and system scope16:14
kmallocand we can be more directed about it16:14
* lbragstad feels like we're missing an opportunity to establish a feedback loop16:15
kmalloc"does X meet your needs"... "is y sufficient" ... "enhancements for z"16:15
lbragstadbut i do see it as a turbulent area of keystone currently16:15
kmalloci don't think so, this is so much in flux you're going to get not-super-useful data16:15
kmalloci think the answers will be: "yeah, it might be better, but uhm... we aren't using it cause it's not usable yet"16:15
*** jrbalderrama has quit IRC16:16
*** ayoung has joined #openstack-meeting-alt16:16
cmurphyi disagree a little, it's still useful to compare it to past years on whether this is a top concern16:16
* hrybacki nods16:16
cmurphywhich it most likely will be but if we omit the question the data gets skewed16:16
lbragstad++16:16
kmallocI'd probably ask for a direct question about top concerns/areas needing most work16:16
hrybackithis allowed us to see Federation re-raised in priority16:16
kmallocrather than "is policy good/bad/something"16:16
lbragstadok - so what would those direct questions be?16:16
kmallocI'd go for something like: What part of keystone needs the most improvement for your deployment?16:17
lbragstadi've always been curious how many deployments roll custom policy and do what extent, but that's a tough one16:17
knikolla"Would you like to use your corporate identity provider with OpenStack but unable to do so?"16:17
kmallocif we can do a ranked choice vs multi choice and list out what we think the components are it would be good16:17
hrybackikmalloc++16:18
ayoung"Do you put a  layer in front of OpenStack to prevent users having direct access due to access control concerns."16:18
lbragstade.g., do you deploy adjutant16:18
knikollalbragstad: i think i'm the minority in asnwering yes to that.16:19
kmallocif we can't do a ranked choice, i totally get keeping policy question(s) in.16:19
ayoungI'm thinking more like in front of Nova16:19
knikollaayoung: "do you stock up on alcohol before dealing with keystone?"16:19
kmalloca multi-selection checkbox (check 3 of X) would also be fine.16:19
ayoung"do you allow end users access to Openstack directly, or do you make them go through a portal."16:19
cmurphy"do you modify default policy" might be interesting16:20
ayoungits not something people see in keystone, but rather policy across the board.  Just, we are the ones driving it.16:20
ayoungcmurphy, yeah.  Or :"Would you like to have a different policy but can't"16:21
lbragstadthis is good16:22
lbragstadwhat else?16:22
* kmalloc avoids really snarky questions.16:23
* kmalloc is pre-coffee.16:23
lbragstadfwiw - aprice and jamesmcarthur are going to be around to answer questions about the survey format in 40 minutes16:23
ayoungProbably something about "what IdM features of public clouds would you mosty like  to see in OpenStack"16:23
lbragstaddoes public cloud have to be a part of the question?16:23
*** ccamacho has quit IRC16:23
lbragstador can that apply to private/hybrid?16:23
*** ccamacho has joined #openstack-meeting-alt16:24
kmalloci would avoid asking specifically "what IdM features of other clouds" and ask more about generic Identity Management features (not cloud specific)16:24
kmallocyou can say "including public cloud providers"16:25
kmallocbut i wouldn't strictly limit in that way.16:25
lbragstadok - keep thinking of topics, i'll be visiting with the foundation about the format for questions soon if anyone is interested in helping out there16:26
lbragstadi'll revise everything and send it off before friday16:26
ayoungit should be public cloud explicitly.  Otherwise, we will never be forced to learn16:26
ayoungFor example:16:26
ayoungin Azure,. if you delete a project, you delete all of the resources of that project.16:27
kmallocayoung: ok that isn't really IdM specific16:27
kmalloci'd phrase that in another way. we've (in openstack) cross IdM with other types of management.16:27
ayoungGood point.  We put it under the Id project, but THey don't16:27
kmallocyes.16:28
kmallocit's a great question, but we need to be sure we put it in the right context16:28
lbragstadare we good to move? we can circle back to this after?16:28
ayoungsure16:28
lbragstad#topic features in flight16:28
*** openstack changes topic to "features in flight (Meeting topic: keystone)"16:28
lbragstadjust a quick check point on the things we said we were going to deliver for this release16:29
lbragstadsince we have 4 weeks until feature freeze16:29
lbragstadit's going to likely be a race with the gate16:29
lbragstadthe MFA auth receipt work is done16:29
lbragstadthe JWT provider work needs reviews - in addition to some careful eyes from wxy| about the performance concerns16:30
lbragstad(i spent a bunch of time last week trying to performance test loading keys from disk - but i might need more information)16:30
kmalloclbragstad: i can take a pass at trying to make it not-on-disk-specific as followups to your code16:31
kmallocit is fine to land as-is imo16:31
lbragstadi was going to write up a summary on the mailing list about it, too16:31
kmallocon the performance front16:31
kmallocwe can enhance past FF.16:31
kmallocor in Train.16:31
kmalloclets not spin too hard on this right now.16:31
lbragstadi'm fine with it being iterative,16:31
kmallocfernet had iterations, JWT will too16:31
wxy|kmalloc: ++, we can revisit it later.16:32
lbragstadbut if we can nail down how to recreate the issues wxy| mentioned for public cloud, i'll get something fixed before RC16:32
kmallocyes.16:32
lbragstadwxy| if i start a thread on the mailing list, would you be able to update it?16:32
lbragstador just share/double check my process for recreating the issue?16:33
kmallocit'll be easier to do that once JWT is landed. IT is not bad code nor something we should hold up. make sure we mark the release note that iterations on performance are expected to occur16:33
kmallocor something.16:33
wxy|lbragstad: Sure16:33
lbragstad#action lbragstad to summarize key loading performance notes on the openstack-discuss mailing list16:33
wxy|I can try to get more information (like performance test data) from downstream team as well.16:33
kmallocI fully expect you'll need to run some kind of io-contention running process to force it to duplicate the read-from-disk issues with low disk-cache / low ram available for disk caching16:34
lbragstadthat'd be great16:34
kmallocit's hard to replicate a real-world environment on that front.16:34
kmallocespecially with repos being deployed ${wherever} and shared with ${other_processes}16:34
lbragstadsounds good16:34
hrybackiI would like to say that we already have a big performance hit from uuid->fernet so it's worth paying close attention to for jwt (especially if we aim for it to be default)16:34
kmallocheck, i wouldn't be surprised if folks deploy keys via NFS and have performance issues that way as well.16:34
*** markvoelker has quit IRC16:35
kmallochrybacki: ++ and i think we can be better with JWT, fernet is hard to be a ton better with.,16:35
kmallocasym crypto (signing) vs symmetric crypto (encryption)16:35
* hrybacki nods16:36
lbragstadso - we have a plan for that it sounds like16:36
lbragstadexplicit domain ids16:36
lbragstadsomeone was pinging about that last week - and it sounded like they were interested in helping out with the work16:36
lbragstadi'm not sure if they got in touch with you ayoung16:37
lbragstadoptrenko i believe?16:37
ayoungNot that I remember seeing16:38
lbragstadok16:38
ayoungWith JWT validated in process, we should not need to go back to Keystone for every token, and performance should improve. It requires fetching and caching of Keystone data,though.16:39
lbragstadok - if i see them i'll try and get an update16:39
ayoungThe token body itself needs to contain all of the user specific data, not just Ids16:39
ayoungbut not service catalog16:40
lbragstadthe default roles work still needs a bunch of reviews - but we're getting there16:40
kmallocso, the concern is token body size there ayoung16:40
ayoungroles can be ID only, if the service fetches and caches them.16:40
ayoungYep.  There should be a hard limit in the vicinity of 2K I'd say on token size16:40
*** jamesmcarthur has joined #openstack-meeting-alt16:40
ayoungJust to draw a line in the sand16:41
ayoungwe know 8 K is too big, and we know we can get away with 1K16:41
hrybackilbragstad: lets sync this afternoon on the roles stuff. I've managed to sluff off enough responsibilities to aid now16:41
*** aprice has joined #openstack-meeting-alt16:41
ayoung++16:41
lbragstadwe still have a bunch to get through on the agenda - mind if we table the jwt stuff til office hours?16:41
lbragstaddomain level unified limit support is all ready for review - waiting on a patch to fix a sqlite migration16:42
lbragstadhrybacki ++16:42
lbragstadis there anything i'm missing feature wise?16:42
cmurphyi'm making good progress with app cred whitelist, but it is going to be a lot of patches and there might not be enough time to review, if that happens i think it's okay to push it to next cycle16:43
kmallocayoung: yes, we absolutely need to be less than 4k, but also note significant sizes are a deal breaker for swift on the front of "Recommended" auth methods. when your auth token is larger than the data you are sending to the user.....16:43
lbragstadoh - yes cmurphy (sorry!)16:43
cmurphynp16:43
lbragstadcmurphy those are ready for review?16:43
cmurphylbragstad: not really no16:43
lbragstadlast i saw you had them WIP'd16:43
cmurphythese two ksa patches could be reviewed https://review.openstack.org/63603016:44
cmurphythey will need to land before ksm tests will work16:44
lbragstadok16:44
lbragstadthat brings up our next topic16:45
cmurphywip ksm change if you want to see why those are needed https://review.openstack.org/63336916:45
lbragstaddoes anyone have patches they need eyes on?16:45
lbragstadcmurphy cool - i can take a look16:45
vishakhaa small change https://review.openstack.org/#/c/635444/16:46
lbragstadthanks vishakha16:46
kmallocvishakha: +2/+A16:46
cmurphyi think this ksm change is ready to go https://review.openstack.org/63369516:46
vishakhalbragstad,kmalloc: thanks16:46
lbragstadnice16:47
kmallocand we probably want to revisit https://review.openstack.org/#/c/613675/ just to cleanup / make KSM easier to work with.16:47
kmallocPKI[z] is long dead16:47
kmallocit should land *after* a rebase on the one cmurphy just linked.16:48
lbragstadyeah - so my only reason for the -1 there was because we socialize a format for deprecation16:48
kmallocso 635444 should land.16:48
kmalloclbragstad: and my response to that stands.16:48
lbragstadit's a difference of logging a warning or not i think16:49
kmallocand maintaining dead opts in the code that have zero impact.16:49
lbragstadmainly so people can see what they can clean up16:49
ayoungkmalloc, I think we should let cmurphy 's work land before we strip out all the PKI stuff.16:49
kmallocit's fine on the order of landing.16:49
ayoungor order the two patches explicitly, to keep from rebase hell16:49
kmalloci have no qualms when it lands.16:50
cmurphy10 minutes left16:50
ayoungYeah, just want to not mess up the feature work16:50
kmalloci knwo cmurphy did voice a "pki code" made some things more difficult16:50
cmurphykmalloc: not pki specifically, the whole ksm test suite is a huge mess16:50
kmalloclbragstad: it is communicated via release note that the options are removed.16:50
kmalloccmurphy: fair.16:50
kmalloccmurphy: and yes. it is.16:50
cmurphycleaning up unecessary crap is a good start but would be good to do a full reorg16:51
lbragstadi'll re-review it kmalloc16:51
kmalloclbragstad: it can land at anypoint16:51
kmalloccmurphy: i think if we can strip out (do removals) of dead code it'll make the reorg easier too.16:52
kmalloccmurphy: and yeah it def. needs to be reworked.16:52
cmurphykmalloc: ++16:52
lbragstadok - anything else for reviews?16:52
lbragstad#topic cleaning up stale blueprints16:52
*** openstack changes topic to "cleaning up stale blueprints (Meeting topic: keystone)"16:52
lbragstadthe state of blueprints in launchpad has been rough for a while16:52
lbragstadi'm going to put some time into removing cruft and updating things16:53
lbragstadif anyone is interested in learning about that process, just ping me16:53
lbragstad#topic ops meetup in berlin16:53
*** openstack changes topic to "ops meetup in berlin (Meeting topic: keystone)"16:53
kmallocfwiw, I still recommend dropping blueprints and just using RFE bugs.16:53
*** ccamacho has quit IRC16:53
* kmalloc has a change to the spec template to communicate that16:53
kmallocproposed*16:53
cmurphy#link http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002614.html call for topics16:53
hrybackiwould that be verbose enough?16:53
kmallochrybacki: we can chat more in -keystone post meeting.16:53
cmurphyI'll be at the berlin ops meetup in march16:54
cmurphythey are asking for topics that need more input from operators16:54
cmurphyso if there are deas follow up on the links in that email16:54
cmurphyand/or let me know and i can bring them up16:54
ayoungcmurphy, kmalloc we have the policy lab.  If that gets the ax, I want to move it to the official keystone topics list.  Maybe do so anyway?16:54
lbragstadthanks cmurphy16:54
kmallocsure16:55
hrybackiayoung: at the berlin meetup?16:55
lbragstad#topic open discussion16:55
*** openstack changes topic to "open discussion (Meeting topic: keystone)"16:55
kmallocfwiw, i will not be at the berlin meetup.16:55
lbragstadaprice and jamesmcarthur are here to help answer questions about the format of the user survey16:55
cmurphylbragstad: re lp blueprints count me in16:55
kmallocand i will not be at the shanghai summit.16:55
jamesmcarthuro/16:55
lbragstadaprice jamesmcarthur i think the biggest piece of information we're curious about is what format we're limited to with questions16:56
* kmalloc rolls the piano in... realizes this is not the right time, and rolls the piano back out.16:56
apriceo/16:56
lbragstadwe have some examples of the questions we'd like to ask starting at line 33 here - https://etherpad.openstack.org/p/keystone-weekly-meeting16:56
jamesmcarthurYou can select pretty much any format you see on the survey.16:56
kmallocis ranked choice for a question possible?16:57
kmallocor is it better to just do a "select 3 of X" optioins16:57
jamesmcarthurThere is a ranked choice option.16:57
*** TxGirlGeek has quit IRC16:57
kmalloccool. :)16:57
*** sridharg has quit IRC16:58
apricelbragstad: because of the volume of projects, each project is limited to two questions so we would want to select which ones out of that list that you would like to include.16:58
kmallochrybacki, lbragstad: ^ that could make the "what needs work" question more general and keep a pulse on it survey-to-survey16:58
lbragstadsure16:58
hrybackiyeah, we should think hard if we are limited to two16:58
ayounghrybacki, ah, misread.  I meant under the Denver summit/PTG umbrella.16:58
hrybackiayoung: ack, thought so but wanted to clarify16:59
apriceif you do want to do more, we could link to a survey monkey that we could facilitate that could also be shared on the ML16:59
hrybackigotta run o/ folks16:59
apricebut within the user survey specifically, there would be that limit16:59
lbragstadthat's a good idea16:59
*** hongbin has quit IRC16:59
lbragstadwe're out of time, but we can continue in -keystone if folks are still curious about the survey17:00
lbragstadi appreciate the time, everyone17:00
lbragstad#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:00
openstackMeeting ended Tue Feb 12 17:00:38 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-02-12-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-02-12-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-02-12-16.00.log.html17:00
*** sdake_ has quit IRC17:01
*** sdake has joined #openstack-meeting-alt17:03
*** wxy| has quit IRC17:06
*** liuyulong has quit IRC17:09
*** e0ne has quit IRC17:27
*** _pewp_ has quit IRC17:27
*** _pewp_ has joined #openstack-meeting-alt17:28
*** jamesmcarthur has quit IRC17:31
*** jamesmcarthur_ has joined #openstack-meeting-alt17:32
*** markvoelker has joined #openstack-meeting-alt17:32
*** gryf has quit IRC17:34
*** whoami-rajat has quit IRC17:36
*** jamesmcarthur_ has quit IRC17:42
*** e0ne has joined #openstack-meeting-alt17:43
*** yamamoto has joined #openstack-meeting-alt17:44
*** sdake has quit IRC17:44
*** dtrainor has quit IRC17:46
*** sdake has joined #openstack-meeting-alt17:47
*** gyee has joined #openstack-meeting-alt17:47
*** dtrainor has joined #openstack-meeting-alt17:48
*** yamamoto has quit IRC17:48
*** jamesmcarthur has joined #openstack-meeting-alt17:51
*** jamesmcarthur has quit IRC17:56
*** derekh has quit IRC17:56
*** jamesmcarthur has joined #openstack-meeting-alt17:58
*** jamesmcarthur has quit IRC17:58
*** kopecmartin is now known as kopecmartin|off17:58
*** jamesmcarthur has joined #openstack-meeting-alt18:01
*** markvoelker has quit IRC18:06
*** panda is now known as panda|off18:06
*** jamesmcarthur has quit IRC18:07
*** jamesmcarthur has joined #openstack-meeting-alt18:08
*** tssurya has quit IRC18:09
*** yamamoto has joined #openstack-meeting-alt18:11
*** jamesmcarthur has quit IRC18:12
*** panda|off has quit IRC18:34
*** gcerami_ has joined #openstack-meeting-alt18:37
*** sdake has quit IRC18:44
*** priteau has quit IRC18:47
*** sdake has joined #openstack-meeting-alt18:51
*** jamesmcarthur has joined #openstack-meeting-alt18:56
*** jamesmcarthur has quit IRC18:58
*** slaweq has quit IRC18:59
*** tsmith_ has joined #openstack-meeting-alt19:01
*** markvoelker has joined #openstack-meeting-alt19:03
*** vishalmanchanda_ has joined #openstack-meeting-alt19:03
*** Dantalion has quit IRC19:04
*** alex_xu has quit IRC19:04
*** stephenfin has quit IRC19:04
*** vishalmanchanda has quit IRC19:04
*** jroll has quit IRC19:04
*** number80 has quit IRC19:04
*** mugsie has quit IRC19:04
*** yamahata__ has quit IRC19:04
*** tsmith2 has quit IRC19:04
*** vishalmanchanda_ is now known as vishalmanchanda19:04
*** tsmith_ is now known as tsmith219:04
*** yamahata__ has joined #openstack-meeting-alt19:04
*** mugsie has joined #openstack-meeting-alt19:05
*** stephenfin has joined #openstack-meeting-alt19:06
*** jroll has joined #openstack-meeting-alt19:06
*** number80 has joined #openstack-meeting-alt19:06
*** jamesmcarthur has joined #openstack-meeting-alt19:07
*** gcerami_ is now known as panda19:14
*** jamesmcarthur has quit IRC19:30
*** markvoelker has quit IRC19:36
*** sdake has quit IRC19:42
*** vishakha has quit IRC19:50
*** jamesmcarthur has joined #openstack-meeting-alt19:59
*** slaweq has joined #openstack-meeting-alt20:19
*** e0ne has quit IRC20:25
*** jamesmcarthur has quit IRC20:31
*** markvoelker has joined #openstack-meeting-alt20:33
*** e0ne has joined #openstack-meeting-alt20:48
*** jamesmcarthur has joined #openstack-meeting-alt20:52
*** jamesmcarthur has quit IRC20:54
*** slaweq_ has joined #openstack-meeting-alt21:03
*** slaweq has quit IRC21:06
*** mugsie has quit IRC21:06
*** markvoelker has quit IRC21:06
*** mugsie has joined #openstack-meeting-alt21:06
*** raildo has quit IRC21:18
*** rdopiera has quit IRC21:23
*** sdake has joined #openstack-meeting-alt21:26
*** e0ne has quit IRC21:28
*** aning has quit IRC21:32
*** slaweq_ is now known as slaweq21:32
*** jtomasek has quit IRC21:35
*** sdake has quit IRC21:50
*** markvoelker has joined #openstack-meeting-alt22:03
*** jamesmcarthur has joined #openstack-meeting-alt22:27
*** slaweq has quit IRC22:34
*** markvoelker has quit IRC22:36
*** cloudrancher has joined #openstack-meeting-alt22:59
*** masahito has joined #openstack-meeting-alt23:08
*** jamesmcarthur has quit IRC23:11
*** whoami-rajat has joined #openstack-meeting-alt23:12
*** jamesmcarthur has joined #openstack-meeting-alt23:32
*** jamesmcarthur has quit IRC23:32
*** jamesmcarthur has joined #openstack-meeting-alt23:33
*** markvoelker has joined #openstack-meeting-alt23:33
*** macza has quit IRC23:42
*** macza has joined #openstack-meeting-alt23:42
*** sdake has joined #openstack-meeting-alt23:43
*** cloudrancher has quit IRC23:44
*** jamesmcarthur has quit IRC23:56

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