Wednesday, 2017-03-15

*** gyee has joined #openstack-keystone00:02
*** hoonetorg has quit IRC00:22
*** MasterOfBugs has quit IRC00:26
*** r-daneel has quit IRC00:30
*** aasthad has quit IRC00:32
*** catintheroof has joined #openstack-keystone00:32
*** hoonetorg has joined #openstack-keystone00:35
*** guoshan has joined #openstack-keystone00:39
*** zhurong has joined #openstack-keystone00:53
*** guoshan has quit IRC01:00
*** agrebennikov has quit IRC01:15
*** hoonetorg has quit IRC01:16
*** Shunli has joined #openstack-keystone01:21
*** edmondsw has joined #openstack-keystone01:21
*** liujiong_lj has joined #openstack-keystone01:23
*** catintheroof has quit IRC01:24
*** Shunli has quit IRC01:28
*** Shunli has joined #openstack-keystone01:29
*** hoonetorg has joined #openstack-keystone01:30
*** catintheroof has joined #openstack-keystone01:30
*** catintheroof has quit IRC01:32
*** liujiong_lj is now known as liujiong01:35
*** guoshan has joined #openstack-keystone01:36
*** edmondsw has quit IRC01:36
*** namnh has joined #openstack-keystone01:53
openstackgerritMerged openstack/keystonemiddleware master: Remove old comment referencing fixed bug  https://review.openstack.org/44323501:56
*** wangqun has joined #openstack-keystone02:00
lbragstadrderose you're doing a talk on PCI in Boston, right?02:11
lbragstadrderose do you know when and where it will be?02:12
*** zsli_ has joined #openstack-keystone02:14
rderoselbragstad: yeah, right02:15
rderoselbragstad: let me see02:15
lbragstadrderose no rush if you can't find it right now - but i want to promote it in my presentation02:15
lbragstadin the event mine happens before yours02:16
*** Shunli has quit IRC02:16
*** zsli__ has joined #openstack-keystone02:18
rderoselbragstad: Thu 4:10 PM02:18
rderoselbragstad: doesn't say where02:18
lbragstadsweet02:19
rderoselbragstad: what is your topic on?02:19
lbragstadrderose it's a project update on keystone02:20
rderoseI see02:20
lbragstadrecapping what we've done in Ocata, what we're doing in Pike and so on02:20
rderoselbragstad: do you want to switch?02:20
rderose:)02:20
lbragstadlol nope :)02:20
*** zsli_ has quit IRC02:20
lbragstadrderose i did throw together a slide deck if you need one02:20
rderoselbragstad: cool, yeah that would be great02:21
lbragstadrderose https://docs.google.com/presentation/d/1s9BNHI4aHs_fEcCYuekDCFwMg1VTsKCHMkSko92Gqco/edit?usp=sharing02:21
lbragstadrderose don't feel obligated to use it - i just figured it would be nice to work in that new mascot02:21
rderoselbragstad: nice02:21
rderoselbragstad: that's perfect02:21
rderosethx02:21
lbragstadrderose no problem02:22
*** aasthad has joined #openstack-keystone02:54
*** gyee has quit IRC03:01
*** markvoelker has quit IRC03:06
*** gyee has joined #openstack-keystone03:17
*** browne has quit IRC03:18
*** masterjcool has quit IRC03:20
*** knangia has quit IRC03:21
*** masterjcool has joined #openstack-keystone03:32
*** nicolasbock has quit IRC03:42
*** rderose has quit IRC03:54
*** knangia has joined #openstack-keystone03:55
*** links has joined #openstack-keystone03:56
*** namnh has quit IRC04:05
*** markvoelker has joined #openstack-keystone04:07
*** markvoelker has quit IRC04:13
openstackgerritMerged openstack/oslo.policy master: Seperate each policy rule with new line  https://review.openstack.org/44333204:18
openstackgerritOpenStack Proposal Bot proposed openstack/keystonemiddleware master: Updated from global requirements  https://review.openstack.org/43931804:20
*** dikonoor has joined #openstack-keystone04:21
openstackgerritOpenStack Proposal Bot proposed openstack/oslo.policy master: Updated from global requirements  https://review.openstack.org/44512804:26
*** dikonoor has quit IRC04:28
*** zsli_ has joined #openstack-keystone04:38
*** zsli__ has quit IRC04:40
*** zhurong has quit IRC05:00
*** david-lyle has quit IRC05:04
*** wangqun_ has joined #openstack-keystone05:07
*** wangqun has quit IRC05:07
*** josecastroleon has quit IRC05:07
openstackgerritOpenStack Proposal Bot proposed openstack/keystone master: Updated from global requirements  https://review.openstack.org/44575005:11
openstackgerritOpenStack Proposal Bot proposed openstack/keystonemiddleware master: Updated from global requirements  https://review.openstack.org/43931805:11
*** wangqun has joined #openstack-keystone05:11
*** wangqun_ has quit IRC05:13
*** wangqun has quit IRC05:18
*** wangqun has joined #openstack-keystone05:18
*** dikonoor has joined #openstack-keystone05:19
*** dikonoor has quit IRC05:28
*** dikonoor has joined #openstack-keystone05:28
*** zsli_ has quit IRC05:39
*** zsli_ has joined #openstack-keystone05:40
*** richm has quit IRC05:43
*** dikonoor has quit IRC05:48
*** gyee has quit IRC05:51
*** MasterOfBugs has joined #openstack-keystone05:58
*** adriant has quit IRC05:59
*** zsli_ has quit IRC06:08
*** markvoelker has joined #openstack-keystone06:09
*** dikonoor has joined #openstack-keystone06:11
*** markvoelker has quit IRC06:13
*** aojea has joined #openstack-keystone06:37
*** namnh has joined #openstack-keystone06:48
*** jaosorior has joined #openstack-keystone06:52
jaosoriorjamielennox: thanks for checking out the patch. still around?06:52
jamielennoxjaosorior: yea, i'mhere06:52
*** pnavarro has joined #openstack-keystone06:53
jaosoriorjamielennox: not sure if it's something valid to catch in tempest. or if there's ever a valid case where the hrefs returned by the discovery are expected to differ from the auth_url used.06:54
jaosoriorjamielennox: is you mentioned we should be using keystoneauth instead. Will discovery from keystoneclient be deprecated then?06:56
jamielennoxjaosorior: so i didn't spend a lot of time trying to understand the use case, but i don't understand why something would be valid pointing to a wrong url06:56
*** zhurong has joined #openstack-keystone06:57
jaosoriorjamielennox: ok, so the case is when keystone is behind a TLS proxy. It's a pretty common case that, since it's behind the proxy, one tries to access it via https, while discovery returns http06:58
jaosoriorso, more than the whole URL, it's an issue with the scheme or protocol06:58
jaosoriornow, while I agree this is an issue of the deployer. I wouldn't want to break users that have no control over how the openstack deployment is done.06:59
jaosoriorso, users that upgrade clients that use keystone discovery will be broken by this, and won't have much choice but to use older clients.07:00
jamielennoxjaosorior: whilst i agree i don't want to break users we've done a whole bunch of things to make this easy for deployers07:03
jamielennoxkeystoneauth will happily accept a relative url from discovery07:03
jamielennoxevery service now ships with proxy_to_wsgi by default07:04
openstackgerritMerged openstack/oslo.policy master: Updated from global requirements  https://review.openstack.org/44512807:04
jaosoriorjamielennox: these deployers use icehouse and are in the process of migrating... but it'll be a while before they get to http_proxy_to_wsgi07:04
jamielennoxand we very recently had keystoneauth called out on the ML for doing too much to hide the problems of deployments, meaning that too much knowledge is wrapped up in python client code that a golang or other language will have to copy because there is reduced pressure on the deploy to fix it07:05
jamielennoxjaosorior: then i imagine a lot more stuff that TLS termination is broken07:06
jaosorioralright07:06
jamielennoxalso, i'm probably wrong but it's just middleware why can't you use a newer version07:06
jamielennoxi guess the dependencies will conflict07:06
*** henrynash has joined #openstack-keystone07:06
jaosoriorit's not up to me dude07:06
jaosoriorI'm just trying to be nice and not break folks07:06
jamielennoxi mean the whole point of proxy_to_wsgi is so the service doesn't care07:07
jaosoriorright07:07
jamielennoxcan you just backport that to the icehouse deploy and roll it?07:07
*** josecastroleon has joined #openstack-keystone07:08
jaosoriorjamielennox: I did mention it wasn't my deployment, right?07:08
jamielennoxjaosorior: ok, i just figured you were involved somehow to be pushing the idea07:09
jaosoriorjamielennox: it's not my deployment. I'm trying to move a project to use generic interfaces instead of v2 or v3 plugins specifically (to be able to use versionless endpoints) and this issue came up from a user that tried it in production.07:10
jamielennoxjaosorior: lol, wow07:10
jamielennoxdon't suppose you can lodge a ticket? their deployment is actually broken as it is now so it's a valid request to get them to change the config to use https:// endpoints07:10
jaosorioryeah, I tried to point the dude on how to fix it even for that version of keystone.07:11
jaosorioryet, I did see several tickets for older versions of keystone on our side, and since we also had to fix it for tripleo; to figure this was a fairly common problem07:11
jaosoriorso yeah, if I had seen this before for older versions, and he had an issue with his provider, then might as well try to fix it or work around it for folks07:12
jamielennoxjaosorior: so the idea here is that you should be loading this sort of information from configuration anyway right?07:12
jamielennoxso for a broken deployment instead of using auth_type=password use auth_type=v3password and point auth_url at the versioned url07:12
jamielennoxlike the projects should not be trying to figure out how a user wants to auth07:13
jaosoriorjamielennox: or use public_endpoint and add the https there07:13
jamielennoxit's back to the x509 and kerberos problems - a project can't know all this information and ksa specifically tries to abstract it from them07:14
jaosoriorI don't really think abstraction is a bad thing07:14
jamielennoxwhat's the project code that is causing this problem?07:15
*** pnavarro has quit IRC07:16
jaosoriorjamielennox: https://review.openstack.org/#/c/44310407:16
jamielennoxergh, swiftclient07:17
jaosoriorhaha07:17
jamielennoxjaosorior: so swiftclient does this horribly and we've had various talks about how we could fix it07:18
jaosoriorjamielennox: and that one came up cause we're trynig to deploy tripleo using versionless endpoints only.07:18
jaosoriorjamielennox: I honestly just looked for the shortest path that would work. But I could rework that.07:19
jamielennoxjaosorior: so a little while ago i got a patch into swiftclient to accept a session07:19
jaosoriorright07:21
jamielennoxjaosorior: it's certainly not pretty, but it should work that if you rewrite whatever is consuming swiftclient to pass a ksa session that already has auth you should be able to bypass all the swiftclient bullshit07:22
*** henrynash has quit IRC07:23
jaosoriorjamielennox: I don't find that patch where you got to accept a session07:23
jamielennoxjaosorior: hmm, i can't remember if i got it done in my name07:24
jamielennoxhttps://review.openstack.org/#/c/298968/07:25
jamielennoxit's super limited and they were desperate to avoid a hard dependency07:25
jamielennoxbut if you do Connection(session=session) you should get the auth you want07:25
jaosoriorjamielennox: interesting, let me try that out07:27
*** knangia has quit IRC07:31
jaosoriorjamielennox: checking out glance_store. It seems to me that with the usage of a session, pretty much this chunk is not needed is it? https://github.com/openstack/glance_store/blob/master/glance_store/_drivers/swift/connection_manager.py#L83-L9507:36
jaosoriorjamielennox: if we pass a session to get_store_connection which is the one that creates the instance of swiftclient's Connection07:36
*** wxy has joined #openstack-keystone07:36
*** maciejjozefczyk has joined #openstack-keystone07:43
*** tesseract has joined #openstack-keystone07:44
*** aojea has quit IRC07:45
jaosoriorjamielennox: https://review.openstack.org/44580207:51
jamielennoxjaosorior: yea, all that part is redundant07:56
jamielennoxkeystoneauth will handle the refresh07:56
jamielennoxjaosorior: i'll owe you many beers if you can fix glance_store -> swiftclient stuff, that's the current thing i couldn't get past with deprecating the old keytoneclient.Client() interface07:57
jamielennoxit's not that it's impossible but both glance and swiftclient has built up years of redundant bullshit there and there's just not an easy deprecation path07:58
jamielennoxalso because glance_store invented their own configuration file format, so we would need a new launcher type to load the auth from .ini files07:59
*** zzzeek has quit IRC08:00
*** zzzeek has joined #openstack-keystone08:00
jaosoriorjamielennox: updated the patch08:03
jamielennoxjaosorior: see my comments?08:04
jaosoriorah08:04
jaosoriornow I got the email08:04
*** pcaruana has joined #openstack-keystone08:05
jaosoriorfixing it08:06
jaosoriorjamielennox: ok, updated the commit, what do you think? I still gotta fix the unit tests though08:09
*** markvoelker has joined #openstack-keystone08:10
jamielennoxjaosorior: why the self.client.authenticate()08:10
jamielennoxand self.client.session, where are you extracting the session from - that's a bad idea08:10
jaosoriorjamielennox: I removed that bit08:11
jaosoriorjamielennox: have you seen the latest commit?08:11
jamielennoxi think so08:11
jamielennoxyea, #3 connection_manager08:11
jaosoriorfunky08:12
jaosoriorI removed that whole part..08:12
jaosoriorduh08:13
jaosoriorhadn't saved08:13
*** markvoelker has quit IRC08:14
jamielennoxjaosorior: so i've had attemptes at refactoring this part - there's no reason for glance_store to depend on ksc, it should only need ksa08:14
jamielennoxbut the key will be to make it configurable rather that relying on V3Password directly08:15
jamielennoxhave that whole thing loaded from config somehow08:15
jaosoriorjamielennox: by the way, doesn't V3Password force one to use a v3 versioned endpoint? wouldn't it be better to use the generic auth plugins?08:17
jamielennoxjaosorior: it does force you to use unversioned08:17
jamielennoxjaosorior: what we want is for that whole bit to be configurable08:17
jamielennoxload it the way auth_token and everything eles does08:18
jaosoriorjamielennox: also, it seems that they use the trusts API, so, wouldn't they need the client for tat?08:19
jaosorior*that08:19
jamielennoxew, you'd have to ask glance why they use trusts there - they have a user/pass, why do they want a trust?08:20
jaosoriorno idea08:20
jamielennoxjaosorior: i've tried various refactors through here, i hope you have better luck08:20
jaosoriorjamielennox: well, what do you think of the latest patch set? I think it's a good first step. Then figure out why they need trusts; come up with an alternative, and iterate from there.08:23
jamielennoxjaosorior: seems like a good start, i dont know it well enough to say all the implications08:26
jamielennoxlike i'd like to avoid returning a client at all, but baby steps08:26
*** guoshan_ has joined #openstack-keystone08:27
jaosoriorjamielennox: and swiftclient should be able to use a session, and then it wouldn't try to create that keystoneclient instance, right?08:27
*** guoshan has quit IRC08:27
*** zhurong has quit IRC08:28
jamielennoxyea08:28
jamielennoxbut at least in this case you're creating the session, passing it to ksc, then using the session again08:28
*** henrynash has joined #openstack-keystone08:29
jamielennoxthings get bad when you do Client(username=x, password=y, ...) then use the session it creates internally08:29
jaosoriorI see08:29
*** d0ugal has joined #openstack-keystone08:31
*** josecastroleon has quit IRC08:33
*** Shunli has joined #openstack-keystone08:39
*** guoshan_ has quit IRC08:43
*** guoshan has joined #openstack-keystone08:44
*** aasthad has quit IRC08:52
*** Shunli has quit IRC08:53
*** Shunli has joined #openstack-keystone08:53
*** zsli_ has joined #openstack-keystone09:08
*** henrynash has quit IRC09:08
*** Shunli has quit IRC09:11
*** henrynash has joined #openstack-keystone09:20
*** henrynash has quit IRC09:21
*** henrynash has joined #openstack-keystone09:23
*** aojea has joined #openstack-keystone09:24
*** henrynash has quit IRC09:27
*** liujiong_lj has joined #openstack-keystone09:27
*** liujiong has quit IRC09:27
*** zhurong has joined #openstack-keystone09:28
*** jaosorior is now known as jaosorior_lunch09:28
*** zsli_ has quit IRC09:33
*** liujiong_lj is now known as liujiong09:36
*** zhurong has quit IRC09:38
*** zhurong has joined #openstack-keystone09:43
*** josecastroleon has joined #openstack-keystone09:50
*** zhurong has quit IRC09:53
*** dmellado has quit IRC09:54
*** dmellado has joined #openstack-keystone10:02
*** edmondsw has joined #openstack-keystone10:02
*** guoshan has quit IRC10:03
*** guoshan has joined #openstack-keystone10:06
*** wangqun has quit IRC10:06
*** edmondsw has quit IRC10:06
*** aojea has quit IRC10:08
*** markvoelker has joined #openstack-keystone10:10
*** richm has joined #openstack-keystone10:13
*** markvoelker has quit IRC10:15
*** openstackgerrit has quit IRC10:18
*** liujiong has quit IRC10:23
*** aojea has joined #openstack-keystone10:24
*** namnh has quit IRC10:41
*** guoshan has quit IRC10:41
*** henrynash has joined #openstack-keystone10:46
*** nicolasbock has joined #openstack-keystone10:50
*** aojea has quit IRC10:53
*** aojea has joined #openstack-keystone10:56
*** dikonoor has quit IRC10:58
*** raildo has joined #openstack-keystone11:01
*** raildo has quit IRC11:01
*** raildo has joined #openstack-keystone11:02
*** henrynash has quit IRC11:35
*** aojea has quit IRC11:39
*** mewald has joined #openstack-keystone11:41
mewaldWe have a cloud with separate networks für public API access and internal communication between services. The public one is a routed network, the internal is - well internal only. I need it to be possible to run e.g. "openstack project create" from the public network without SSHing or VPNing into the internal network. What is the best way to configure this?11:43
*** jdennis has joined #openstack-keystone11:51
*** jdennis1 has quit IRC11:54
*** dikonoor has joined #openstack-keystone12:00
bretonmewald: --interface option of `openstack` cli12:07
bretonoh, it's --os-interface12:09
*** markvoelker has joined #openstack-keystone12:11
*** aojea has joined #openstack-keystone12:11
*** guoshan has joined #openstack-keystone12:12
*** MasterOfBugs has quit IRC12:12
*** markvoelker has quit IRC12:16
*** jaosorior_lunch is now known as jaosorior12:21
mewaldbreton: There is no network connectivity to the admin api endpoint12:31
mewaldI would need the API calls to be available on the public network12:32
*** edmondsw has joined #openstack-keystone12:34
*** henrynash has joined #openstack-keystone12:35
*** edmondsw has quit IRC12:37
*** edmondsw has joined #openstack-keystone12:37
*** markvoelker has joined #openstack-keystone12:38
*** openstackgerrit has joined #openstack-keystone12:43
openstackgerritOpenStack Proposal Bot proposed openstack/keystone master: Updated from global requirements  https://review.openstack.org/44575012:43
*** jaosorior has quit IRC12:46
*** jaosorior has joined #openstack-keystone12:47
*** spilla has joined #openstack-keystone12:51
bretonmewald: i am not sure why you are talking about admin api endpoint12:52
*** erhudy has joined #openstack-keystone12:52
mewaldbreton: yeah me neither :D I thought that API calls like creating projects or domains etc can only be issued against the admin endpoint, is that not true?12:52
bretonmewald: projects are from API v3. There is no admin api endpoint in API v3. So, you can just pass --os-interface public to openstack cli12:52
*** guoshan has quit IRC12:53
mewaldoh ok12:53
mewaldlet me try it then :D12:53
bretonmewald: yep, that's not true for v3.12:53
*** catintheroof has joined #openstack-keystone12:59
mewaldbreton: Nice, it just works :D My lucky day!13:01
*** links has quit IRC13:02
jaosoriorrodrigods: Hey dude, can you check this out https://review.openstack.org/#/c/445802/ ?13:04
rodrigodsjaosorior, sure :)13:04
rodrigodswill take a look in a few13:05
*** aojea has quit IRC13:15
*** bauruine has quit IRC13:15
*** bauruine has joined #openstack-keystone13:16
*** lucasxu has quit IRC13:18
*** aojea has joined #openstack-keystone13:19
*** aojea has quit IRC13:19
*** aojea has joined #openstack-keystone13:19
*** bauruine has quit IRC13:20
*** bauruine has joined #openstack-keystone13:21
*** mewald has left #openstack-keystone13:43
*** markvoelker_ has joined #openstack-keystone13:54
*** markvoelker has quit IRC13:55
*** aojea has quit IRC14:00
*** zhurong_ has joined #openstack-keystone14:03
*** aojea_ has joined #openstack-keystone14:04
openstackgerritLance Bragstad proposed openstack/keystone master: Add reno conventions to developer documentation  https://review.openstack.org/44495514:05
*** links has joined #openstack-keystone14:06
*** zhurong_ has quit IRC14:06
*** knangia has joined #openstack-keystone14:07
*** henrynash has quit IRC14:10
*** lucasxu has joined #openstack-keystone14:12
*** agrebennikov has joined #openstack-keystone14:20
*** chris_hultin|AWA is now known as chris_hultin14:22
*** chris_hultin is now known as chris_hultin|AWA14:32
*** dave-mccowan has joined #openstack-keystone14:38
*** d0ugal has quit IRC14:42
*** dikonoor has quit IRC14:42
*** links has quit IRC14:42
*** d0ugal has joined #openstack-keystone14:43
*** rderose has joined #openstack-keystone14:47
*** aojea_ has quit IRC14:47
lbragstadreminder that we have the policy meeting starting in 5 minutes in #openstack-meeting-cp14:54
lbragstadcc antwash, raildo, ktychkova, dolphm, dstanek, rderose, htruta, atrmr, gagehugo, lamt, thinrichs, edmondsw, ruan, ayoung, ravelar, morgan, raj_singh, johnthetubaguy, knikolla ^14:55
johnthetubaguylbragstad: its that UTC timing correct?14:55
* lbragstad facepalm14:55
lbragstadcorrect - it should in an hour and 5 minutes ;)14:56
bretonoh, it's this time of year again14:57
johnthetubaguylbragstad: no worries, was just checking, I get a few weeks till I move15:02
*** aojea has joined #openstack-keystone15:05
knikollao/15:06
*** jaugustine has joined #openstack-keystone15:12
*** henrynash has joined #openstack-keystone15:12
*** aojea has quit IRC15:15
*** aojea has joined #openstack-keystone15:15
*** lucasxu has quit IRC15:16
*** ayoung is now known as ayoung-teeth15:22
*** voelzmo has joined #openstack-keystone15:29
*** lamt has joined #openstack-keystone15:29
*** aasthad has joined #openstack-keystone15:31
gagehugoo/15:34
*** oomichi has quit IRC15:36
*** jaugustine has quit IRC15:40
*** aojea has quit IRC15:40
*** oomichi has joined #openstack-keystone15:41
*** jaugustine has joined #openstack-keystone15:42
*** aojea has joined #openstack-keystone15:46
*** lucasxu has joined #openstack-keystone15:51
*** david-lyle has joined #openstack-keystone15:56
*** akrzos is now known as akrzos-spec16:01
lbragstadpolicy meeting starting now in #openstack-meeting-cp16:01
*** jaosorior has quit IRC16:02
*** voelzmo has quit IRC16:09
*** aojea has quit IRC16:26
*** clayton has quit IRC16:28
*** clayton has joined #openstack-keystone16:33
*** david-lyle_ has joined #openstack-keystone16:34
*** david-lyle has quit IRC16:34
*** ravelar has joined #openstack-keystone16:40
lbragstadnotmorgan want to do an oslo.policy review (it's very close to approval) https://review.openstack.org/#/c/439070/16:42
*** lucasxu has quit IRC16:47
*** lucasxu has joined #openstack-keystone16:48
lbragstadantwash one comment on the commit message here - https://review.openstack.org/#/c/439070/1616:49
*** gyee has joined #openstack-keystone16:50
*** tesseract has quit IRC16:53
antwashlbragstad: awe make sense -- I'll go ahead and remove it16:55
openstackgerritAnthony Washington proposed openstack/oslo.policy master: Add additional param to policy.RuleDefault  https://review.openstack.org/43907016:56
openstackgerritAnthony Washington proposed openstack/oslo.policy master: Add additional param to policy.RuleDefault  https://review.openstack.org/43907017:05
*** akrzos-spec is now known as akrzos17:05
lbragstadantwash ^ that's looking good17:05
antwashlbragstad : thanks lance, ready to get it merge17:05
lbragstadantwash you and me both17:06
lbragstadantwash i just reviewed the policy-in-code series, too17:06
lbragstadantwash had one minor comment on https://review.openstack.org/#/c/435754/817:06
antwashdevstack decided to stop working for me today smh, def need to create custom script with all my configs to rebuild a env17:06
lbragstadantwash and a naming suggestion on https://review.openstack.org/#/c/435755/917:06
antwashlbragstad: I'll fix them once my env rebuilds lol17:07
lbragstadantwash sweet17:07
openstackgerritRichard Avelar proposed openstack/keystone master: Policy in code (part 3)  https://review.openstack.org/43575417:12
*** lucasxu has quit IRC17:12
*** lucasxu has joined #openstack-keystone17:13
ravelarlbragstad antwash o/ got it. Had a few min to spare on vacation.17:13
* lbragstad holds door open for ravelar 17:14
lbragstadravelar go back to vacationing, sir17:14
antwash++ I need a vacation17:14
* ravelar thanks lbragstad and speeds off17:14
ravelarantwash just get up and leave ;)17:14
antwashi am a good employee sir17:15
ravelarwho has vacation days lol17:15
*** ravelar has left #openstack-keystone17:15
antwashI need to use them for my next tattoo lol17:15
openstackgerritAnthony Washington proposed openstack/keystone master: Policy in code (part 4)  https://review.openstack.org/43575517:17
*** erlon has joined #openstack-keystone17:18
openstackgerritAnthony Washington proposed openstack/keystone master: Policy in code (part 4)  https://review.openstack.org/43575517:19
openstackgerritAnthony Washington proposed openstack/keystone master: Policy in code (part 4)  https://review.openstack.org/43575517:20
*** browne has joined #openstack-keystone17:22
*** pcaruana has quit IRC17:28
lbragstadantwash you and me both ;)17:35
antwashlbragstad : you getting a new tat?17:35
antwashplacement?17:35
lbragstadantwash i have to finish mine lol17:35
antwashlbragstad : awe, I thought it was finished lol -- whole sleeve or half?17:36
lbragstadantwash right now its a half17:37
*** szaher has joined #openstack-keystone17:39
*** henrynash has quit IRC17:41
antwashlbragstad: yeah I remember, when he/she be adding to make it a full or just finishing up half?17:42
lbragstadantwash well - i'd like to turn the half into a full - but the guy who did it is in Austin17:43
*** MasterOfBugs has joined #openstack-keystone17:45
*** ayoung-teeth is now known as ayoung17:45
antwashlbragstad : aweee now I see lol man that sucks -- I got my first one an I've been addicted every since https://www.instagram.com/p/BLABMj8AF8u/?taken-by=g_gravestattoos&hl=en17:47
openstackgerritAnthony Washington proposed openstack/keystone master: Policy in code (part 4)  https://review.openstack.org/43575517:50
lbragstadantwash nice!17:56
lbragstadantwash `git review -d 435754; git review -x 435755; git review` should rebase part 4 on part 3 without pushing a new version of part 317:57
openstackgerritAnthony Washington proposed openstack/keystone master: Policy in code (part 3)  https://review.openstack.org/43575418:00
openstackgerritAnthony Washington proposed openstack/keystone master: Policy in code (part 4)  https://review.openstack.org/43575518:00
openstackgerritAnthony Washington proposed openstack/keystone master: Policy in code (part 5)  https://review.openstack.org/43575718:00
antwashlbragstad : awe shoot lol wish I would've read it before pushing up haha #badtiming18:00
antwash^ in theory it should solve all the merge conflicts18:00
* antwash praises it does solve them18:01
*** raildo has quit IRC18:10
*** lucasxu has quit IRC18:13
*** lucasxu has joined #openstack-keystone18:16
*** gyee has quit IRC18:18
*** pramodrj07 has joined #openstack-keystone18:23
*** MasterOfBugs has quit IRC18:23
*** pramodrj07 has quit IRC18:25
*** MasterOfBugs has joined #openstack-keystone18:25
*** MasterOfBugs has quit IRC18:27
*** MasterOfBugs has joined #openstack-keystone18:27
*** henrynash has joined #openstack-keystone18:38
*** voelzmo has joined #openstack-keystone18:39
*** henrynash has quit IRC18:47
*** catinthe_ has joined #openstack-keystone18:48
*** afazekas_ is now known as afazekas18:50
*** catintheroof has quit IRC18:51
*** voelzmo has quit IRC18:53
*** lamt has quit IRC19:02
*** lamt has joined #openstack-keystone19:04
*** aasthad has quit IRC19:12
openstackgerritMerged openstack/keystone master: Add reno conventions to developer documentation  https://review.openstack.org/44495519:18
*** edtubill has joined #openstack-keystone19:34
*** aasthad has joined #openstack-keystone19:42
*** voelzmo has joined #openstack-keystone19:42
*** antwash has quit IRC19:45
*** raj_singh has quit IRC19:45
*** jascott1 has quit IRC19:45
*** jlopezgu has quit IRC19:45
*** iurygregory has quit IRC19:47
*** henrynash has joined #openstack-keystone19:50
*** iurygregory has joined #openstack-keystone19:50
*** iurygregory has quit IRC19:56
*** david-lyle_ is now known as david-lyle19:57
openstackgerritMerged openstack/keystone master: Updated from global requirements  https://review.openstack.org/44575019:58
*** lamt has quit IRC19:58
*** iurygregory has joined #openstack-keystone20:00
*** voelzmo has quit IRC20:03
*** richm has quit IRC20:05
*** gus has quit IRC20:07
*** rdo has quit IRC20:09
*** gus has joined #openstack-keystone20:09
*** rdo has joined #openstack-keystone20:11
notmorganlbragstad: reviewed the oslo.policy patch20:12
notmorgan+1, jonhthetubaguy had a concern, and if his -1 is answered, i'll +2.20:12
*** henrynash has quit IRC20:12
lbragstadnotmorgan checking20:14
*** henrynash has joined #openstack-keystone20:14
EmilienMlbragstad: if we want to move forward with https://review.openstack.org/#/c/445592/ - should we propose a spec in Keystone instead?20:15
lbragstadjohnthetubaguy notmorgan the new class was added based on a comment edmondsw had20:16
EmilienMif we can 1. support key/value store backend for token storage and 2. perform rotations in a periodic task within Keystone, that's a problem solved for all deployments in OpenStack20:16
notmorganright20:16
EmilienMI would be happy to abandon my spec in TripleO and help to solve it in Keystone20:16
notmorganit's specific to description to "desc" in the new class20:16
notmorgannothing else seems to be holding it up20:16
notmorganit was odd to rename "description" to "Desc"20:16
notmorganthen store it on the new class20:17
edmondswnotmorgan yeah, that was a bit odd, but since it's no longer a kwarg I didn't know that that would matter20:18
notmorgani would pass description through and make description an @property on the new class20:18
notmorganwould be caught in the superclass set in __init__20:18
notmorganbut thats just my $0.00220:18
notmorganit's not a deal breaker20:18
notmorganit's just a "hey i'd like a clear answer and i'll +2/+A"20:18
notmorgansince it was brought up as odd20:19
EmilienMcan someone from keystone core can re-explain why we abandon https://review.openstack.org/#/c/439194 ?20:19
notmorganEmilienM: simply put 2 things, 1) the proposers were not continuing work on it/no one doing work for it20:22
EmilienMiiuc, nobody has time to do it20:22
EmilienMok it confirms what I read in the keystone meeting20:22
lbragstadnotmorgan i think the reason why it wasn't passed up was because we're being more strict with the validation20:22
EmilienMit's sad to see OSA, Kolla, Helm (and tripleo soon) doing their own things20:22
lbragstadif people use DocumentedRuleDefault, they must provide a description20:22
notmorganEmilienM: and 2) all uses of fernet needs to have the same pluggable system20:22
lbragstadif they are using RuleDefault, they don't20:22
EmilienMnotmorgan: we could make it optional20:23
EmilienMnotmorgan: provide a way to use File or a key/value store backend20:23
lbragstadso if we start requiring descriptions and roll a new version of oslo.policy, we might break people if they are using RuleDefault without providing descriptions20:23
notmorganlbragstad: right, so on the new class.. make it mandatory20:23
openstackgerritAnthony Washington proposed openstack/keystone master: Policy in code (part 3)  https://review.openstack.org/43575420:23
notmorgani just didn't see why we needed to make it a new name for the arg, not pass it through20:24
notmorganyou could make .description on the new class an @property that does what .desc does20:24
notmorganthis is all still stuff located in the new class :)20:24
notmorganthe new class is 100% the right direction20:24
lbragstadwell - it is mandatory20:24
notmorgandoesn't matter20:24
lbragstadthe new class does require it20:25
notmorganright20:25
notmorgansooooo the question was...20:25
lbragstadlooks like antwash is also doing some additonal validation when setting it though20:25
lbragstadsee line 87320:25
notmorganwhy not still keep it "description" in __init__ and then do:20:25
notmorganhttps://www.irccloud.com/pastebin/dplUGx7H/20:26
notmorganit would work with the super() call and where super sets .description20:26
notmorgansince the @settr catches it20:26
notmorganis this all because we made it mandatory?20:26
notmorganthats was the whole reason for the changE?20:26
lbragstadnotmorgan so - that should catch it i DocumentedRuleDefault before calling setter of RuleDefault?20:26
lbragstads/i/in/20:27
notmorganRuleDefault doesn't have a settr on description20:27
notmorganit is just an instance attribute20:27
notmorgan@settr is handled at the class level (think metaclass things) and is part of the class definition20:28
notmorganit's not instance-specific20:28
notmorganexcept that it references self20:28
lbragstadok20:28
notmorganbut20:28
notmorgani don't care that much20:28
notmorgani just want to have a clear "why did we change it"20:28
notmorganto answer johnthetubaguy's comment20:29
lbragstadagreed20:29
notmorgan*or* we can change it like i described20:29
lbragstadnotmorgan that'd be the best solution20:29
*** dave-mccowan has quit IRC20:29
notmorganbut it's fine either way (not trying to bike shed and hold it up here)20:29
notmorganbut i want to make sure john's comment is responded to before we merge20:29
notmorganand if we want to fix it, slate a fix here or in a followup20:29
lbragstadnotmorgan right - that's fine, we have several things we need to do in oslo.policy before we can do a new release20:30
lbragstadbut as far as documenting the need for a new class, do you think the answer that I left is sufficient?20:30
notmorganlet me check20:30
notmorganlike i said, i think that doesn't answer john's comment20:31
notmorganhe's asking why it's not being passed to super()20:31
notmorganand why the arg was renamed to desc20:31
notmorgannot why a new class20:31
notmorgani think he gets the reason for the new class.20:31
*** lamt has joined #openstack-keystone20:32
notmorganlbragstad: so.. let me respond to your comment.20:32
*** lamt has quit IRC20:33
lbragstadnotmorgan just republished some comments20:33
*** henrynash has quit IRC20:33
notmorgancool20:34
notmorgani responded to your question20:34
notmorganas well20:34
*** lamt has joined #openstack-keystone20:35
notmorgani wouldn't hold this up over that change (desc->description), just as long as it was clear why it was renamed as a response to john i'd +2/+A it, we can cleanup make it "description" again in a rollowup before release if that is the direction we go20:35
openstackgerritAnthony Washington proposed openstack/keystone master: Policy in code (part 4)  https://review.openstack.org/43575520:36
openstackgerritAnthony Washington proposed openstack/keystone master: Policy in code (part 5)  https://review.openstack.org/43575720:37
*** lamt has quit IRC20:39
*** gus has quit IRC20:40
*** gus has joined #openstack-keystone20:42
lbragstadnotmorgan ok - http://cdn.pasteraw.com/46uqzw1u9j8ubsf12i48053oq4yvcxn should fix it20:45
notmorganlooks right to me20:46
notmorganobv. need to test it.20:46
lbragstadtests pass for me locally20:47
notmorgancool20:48
*** voelzmo has joined #openstack-keystone20:51
*** voelzmo has quit IRC20:52
*** johndperkins has quit IRC21:09
openstackgerritAnthony Washington proposed openstack/oslo.policy master: Add additional param to policy.RuleDefault  https://review.openstack.org/43907021:09
*** lucasxu has quit IRC21:12
*** lucasxu has joined #openstack-keystone21:12
*** lucasxu has quit IRC21:12
*** dave-mccowan has joined #openstack-keystone21:14
*** rmascena has joined #openstack-keystone21:14
*** dave-mcc_ has joined #openstack-keystone21:18
*** dave-mccowan has quit IRC21:19
openstackgerritAnthony Washington proposed openstack/keystone master: Policy in code (part 5)  https://review.openstack.org/43575721:22
*** browne has quit IRC21:25
*** henrynash has joined #openstack-keystone21:34
*** edmondsw has quit IRC21:36
*** edmondsw has joined #openstack-keystone21:37
*** edmondsw has quit IRC21:41
openstackgerritAnthony Washington proposed openstack/keystone master: Policy in code (part 5)  https://review.openstack.org/43575721:41
*** rderose_ has joined #openstack-keystone21:42
*** rderose has quit IRC21:44
*** henrynash has quit IRC21:45
*** lamt has joined #openstack-keystone21:46
*** antwash has joined #openstack-keystone21:49
*** edtubill has quit IRC21:52
*** erlon has quit IRC21:55
*** jamielennox has quit IRC21:55
*** lamt has quit IRC21:56
*** lamt has joined #openstack-keystone22:09
*** edtubill has joined #openstack-keystone22:09
*** adriant has joined #openstack-keystone22:14
*** browne has joined #openstack-keystone22:15
*** jamielennox has joined #openstack-keystone22:15
*** aojea has joined #openstack-keystone22:20
*** lamt has quit IRC22:35
*** browne has quit IRC22:49
*** gyee has joined #openstack-keystone22:52
*** lamt has joined #openstack-keystone22:57
*** lamt has quit IRC23:02
*** catinthe_ has quit IRC23:02
*** spilla has quit IRC23:05
*** MasterOfBugs has quit IRC23:08
*** jaugustine has quit IRC23:11
*** aojea has quit IRC23:14
*** aojea has joined #openstack-keystone23:14
*** aojea has quit IRC23:18
*** rmascena has quit IRC23:36
*** agrebennikov has quit IRC23:41
*** jplopezgu_ has joined #openstack-keystone23:56

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