Tuesday, 2019-07-02

*** gyee has quit IRC00:37
*** jamesmcarthur has joined #openstack-keystone00:40
*** jamesmcarthur has quit IRC00:51
*** jamesmcarthur has joined #openstack-keystone00:53
*** lbragstad has quit IRC01:08
*** jamesmcarthur has quit IRC01:10
*** imacdonn has quit IRC01:10
*** jamesmcarthur has joined #openstack-keystone01:10
*** imacdonn has joined #openstack-keystone01:11
*** jamesmcarthur has quit IRC01:15
*** redrobot has quit IRC01:17
*** jamesmcarthur has joined #openstack-keystone01:37
*** jamesmcarthur has quit IRC01:41
*** vishalmanchanda has joined #openstack-keystone02:06
openstackgerritMerged openstack/keystone master: Add Python 3 Train unit tests  https://review.opendev.org/66774602:30
*** jamesmcarthur has joined #openstack-keystone02:37
*** vishakha has joined #openstack-keystone03:04
openstackgerritpengyuesheng proposed openstack/keystone master: Blacklist sphinx 2.1.0 (autodoc bug)  https://review.opendev.org/66858103:20
*** whoami-rajat has joined #openstack-keystone03:42
*** jamesmcarthur has quit IRC03:49
*** jamesmcarthur has joined #openstack-keystone03:50
*** jamesmcarthur has quit IRC03:57
*** jamesmcarthur has joined #openstack-keystone04:29
*** vishalmanchanda has quit IRC04:33
*** jamesmcarthur has quit IRC04:36
*** vishalmanchanda has joined #openstack-keystone04:42
*** dansmith has quit IRC05:04
*** jamesmcarthur has joined #openstack-keystone05:05
*** jamesmcarthur has quit IRC05:10
*** dansmith has joined #openstack-keystone05:22
*** jamesmcarthur has joined #openstack-keystone05:42
*** jamesmcarthur has quit IRC05:47
*** dancn has joined #openstack-keystone06:19
*** Emine has joined #openstack-keystone06:36
*** Emine has quit IRC06:37
*** xek has joined #openstack-keystone07:12
*** tesseract has joined #openstack-keystone07:15
*** evrardjp is now known as evrardjp_on_holi07:40
*** evrardjp_on_holi is now known as evrardjp_away07:40
*** jamesmcarthur has joined #openstack-keystone07:44
*** jamesmcarthur has quit IRC07:48
*** jamesmcarthur has joined #openstack-keystone07:51
*** jamesmcarthur has quit IRC07:55
*** pcaruana has joined #openstack-keystone08:01
*** trident has quit IRC08:10
*** trident has joined #openstack-keystone08:13
*** jamesmcarthur has joined #openstack-keystone08:22
*** tkajinam has quit IRC08:26
*** jamesmcarthur has quit IRC08:28
*** jamesmcarthur has joined #openstack-keystone09:00
*** jaosorior has joined #openstack-keystone09:13
*** whoami-rajat has quit IRC09:42
*** jamesmcarthur has quit IRC10:04
openstackgerritVishakha Agarwal proposed openstack/keystone master: Remove [signing] config  https://review.opendev.org/65943410:38
*** raildo has joined #openstack-keystone10:53
openstackgerritVishakha Agarwal proposed openstack/keystone master: Update test cases for os-pki revoke API  https://review.opendev.org/66865411:21
*** kimamisa has joined #openstack-keystone11:27
kimamisaHi all !11:27
kimamisaI was prototyping the stein release locally, and faced a mystery with the new policy file, and especially with the : "identity:get_user": "rule:identity:get_user" line.11:27
kimamisaIs it a way to keep the legacy behaviour of a rule given in another policy file ? I tried to find online documentation, but I'm not sure to really get what it does.11:27
*** jaosorior has quit IRC11:42
*** jamesmcarthur has joined #openstack-keystone12:01
*** jamesmcarthur has quit IRC12:05
*** jamesmcarthur has joined #openstack-keystone12:34
*** jamesmcarthur has quit IRC12:39
*** jaosorior has joined #openstack-keystone12:39
*** jamesmcarthur has joined #openstack-keystone12:42
*** dancn has quit IRC12:47
*** dancn has joined #openstack-keystone12:59
*** jamesmcarthur has quit IRC13:05
*** dancn has quit IRC13:21
*** dancn has joined #openstack-keystone13:22
*** lbragstad has joined #openstack-keystone13:24
*** jamesmcarthur has joined #openstack-keystone13:32
*** vishakha has quit IRC13:36
*** dancn has quit IRC13:55
ayoungkimamisa, policy in code14:01
ayounghttps://opendev.org/openstack/keystone/src/branch/master/keystone/common/policies/user.py#L6114:02
lbragstadkimamisa yeah - it's a way to maintain backwards compatibility when policies changes (go through a deprecation cycle)14:05
kimamisaayoung lbragstad thx ! I'll dig deeper with this !14:12
*** redrobot has joined #openstack-keystone14:33
openstackgerritColleen Murphy proposed openstack/keystone-specs master: Add Python 3 Train unit tests  https://review.opendev.org/66775514:40
*** evrardjp_away has quit IRC14:58
*** evrardjp has joined #openstack-keystone14:59
openstackgerritMerged openstack/keystone master: Bump openstackdocstheme to 1.20.0  https://review.opendev.org/66324314:59
openstackgerritLance Bragstad proposed openstack/keystone master: Allow domain users to access the limit API  https://review.opendev.org/62102315:03
openstackgerritLance Bragstad proposed openstack/keystone master: Add tests for project users interacting with limits  https://review.opendev.org/62102415:03
openstackgerritLance Bragstad proposed openstack/keystone master: Remove limit policies from policy.v3cloudsample.json  https://review.opendev.org/62102515:03
*** edmondsw_ has joined #openstack-keystone15:04
*** gyee has joined #openstack-keystone15:04
openstackgerritVishakha Agarwal proposed openstack/keystone master: Update test cases for os-pki revoke API  https://review.opendev.org/66865415:43
cmurphykeystone meeting in 15 minutes in #openstack-meeting-alt15:45
*** vishakha has joined #openstack-keystone15:45
cmurphyagenda https://etherpad.openstack.org/p/keystone-weekly-meeting15:46
cmurphymeeting now in #openstack-meeting-alt16:01
*** jamesmcarthur has quit IRC16:03
*** gyee has quit IRC16:12
*** jamesmcarthur has joined #openstack-keystone16:17
*** gyee has joined #openstack-keystone16:25
cmurphylbragstad: want to go over oslo.limit over irc or would a call be better?16:32
lbragstadi can do either - i figured a call would let us get through things quicker16:33
lbragstadi'm flexible though16:33
kmallocI don't have the ability to jump on a call atm.16:34
kmalloc=/16:34
cmurphykmalloc: irc okay though?16:35
kmallocyeah IRC16:35
cmurphyokay let's try that16:35
cmurphy#startmeeting keystone-office-hours16:35
openstackMeeting started Tue Jul  2 16:35:32 2019 UTC and is due to finish in 60 minutes.  The chair is cmurphy. Information about MeetBot at http://wiki.debian.org/MeetBot.16:35
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:35
*** openstack changes topic to " (Meeting topic: keystone-office-hours)"16:35
*** ChanServ changes topic to "Stein release schedule: https://releases.openstack.org/stein/schedule.html | Meeting agenda: https://etherpad.openstack.org/p/keystone-weekly-meeting | Bugs that need triaging: http://bit.ly/2iJuN1h | Trello: https://trello.com/b/rj0ECz2c/keystone-stein-roadmap !!NOTE!! This Channel is Logged ( https://tinyurl.com/OpenStackKeystone )"16:35
openstackThe meeting name has been set to 'keystone_office_hours'16:35
kmalloci just have to be able to transit between locations and airport/etc16:35
kmallocso, can't do video atm16:35
cmurphyirc makes it easier for others to catch up anyways16:36
bnemeco/16:36
lbragstadoh - good call16:38
lbragstadi suppose we should start here https://review.opendev.org/#/c/668523/216:39
lbragstadi should ask - is everyone ready?16:39
* cmurphy ready16:39
lbragstadalright - 668523 is trivial16:40
bnemecWell, that one's easy. It's approved. :-)16:40
lbragstadsweet16:40
lbragstadnext one is https://review.opendev.org/#/c/666085/916:40
lbragstadi wanted to keep the ksa logic separate from everything else16:40
lbragstadnothing in this patch actually uses it, it's just laying the ground work16:41
lbragstadone area of improvement i can think of though, is additional testing16:41
lbragstadbut it would likely have to be mocked pretty heavy in order to work16:41
bnemecYou mean unit testing?16:43
lbragstadright - if we wanted to unit test the functionality of that patch16:43
lbragstadi was going to bring this up in a subsequent review, since it's related to that, too16:43
bnemecI'm a little inclined not to worry too much about it since we're expecting to iterate on the implementation quite a bit.16:43
bnemecWhich I realize violates every principle of TDD.16:43
lbragstadyeah - i was also thinking about setting up a function test suite for this stuff, too16:44
bnemecBut I also don't want someone to spend a ton of time writing tests for code that we end up not using.16:44
lbragstad(the last patch in the series touches on that a bit)16:44
bnemecYeah, that seems good too.16:44
bnemecFor now, maybe look at it as a prototype and just write the tests we absolutely need?16:45
* bnemec feels so dirty for suggesting we not test code16:45
lbragstadoutside of testing, does anyone have questions about the connection logic itself?16:45
cmurphyi've been wondering if there's a way around making the connection a global16:47
cmurphyno specific suggestion though16:48
lbragstadcmurphy do you want it to be a property of the Enforcer object instead?16:48
lbragstador something along those lines?16:48
cmurphymaybe, but i suppose you might instantiate multiple enforcers and you wouldn't want to have that many live connections?16:49
lbragstadprobably not16:49
lbragstadI could document it as an optimization16:50
cmurphyi think it's probably fine as is16:52
kmallocpass in a connection, if none is passed in, attribute.16:52
kmallocs/attribute/property that is on-demand built16:53
kmallocit allows for the same mechanism as global without explicitly expecting global(s)16:53
kmalloccan be iterated on down the line16:53
kmallocno reason to fix that now.16:54
*** nickthetait has joined #openstack-keystone16:54
* lbragstad nodes16:54
* lbragstad nods*16:54
lbragstadalright - anything else on 66608516:55
bnemecI left a comment about the endpoint id.16:55
lbragstadpsh - working ahead16:55
cmurphybnemec: good point about it not being the keystone service16:55
lbragstad++16:56
bnemecI completely agree that region+service would be easier to handle in a deployment tool though.16:57
cmurphymaybe worth optimizing in the future16:57
bnemecI'd be curious to know what percentage of deployers are actually writing their own configurations vs. using Puppet/Ansible/Chef/etc.16:58
bnemecThat would inform which use case we should optimize for.16:58
cmurphyi am reasonably sure almost no one deploys openstack without some kind of deployment tool16:58
lbragstadyeah16:59
bnemecI don't disagree, but I've been surprised before. ;-)16:59
lbragstadmy home lab is built using osa - and i don't even have customers16:59
cmurphylol16:59
bnemecMy home lab is built using devstack. Yes, I'm that guy. :-P16:59
lbragstadtangent: it would be nice to have a baremetal box to pxe boot with a base image for baremetal devstack deployments17:00
*** kimamisa has quit IRC17:01
lbragstadalrighty - anything else on 666085 ?17:01
*** tesseract has quit IRC17:01
cmurphylgtm17:01
lbragstadcool17:02
lbragstadhttps://review.opendev.org/#/c/666444/7 is where things start to get interesting17:02
bnemecFWIW, user survey says "Other Tool" is only 15% of the deployment tooling ecosystem.17:02
*** jamesmcarthur has quit IRC17:02
*** jamesmcarthur has joined #openstack-keystone17:02
lbragstadthe main goal of 666444 is to just get the basic laid down and wait for actual implementation details of the models for another patch17:02
lbragstadwhat i think would be really helpful in looking at this patch, is the relationship between the Enforcer and the models17:03
lbragstadi want to keep the models separate (as their own objects that inherit an interface)17:03
lbragstadbut i found that there is a lot information you have to share between the enforcer and the models17:04
lbragstadEnforcer.enforce() essentially passes a bunch of stuff through or needs to use composition to set various attributes on the model to limit method signatures with lots of arguments17:05
lbragstadi tried to capture some of that information in Enforcer's doc strings17:07
bnemecAt first glance that semes to make sense. They are enforcement models, so it makes sense that they would be pretty tightly tied to the enforcer.17:07
lbragstadyeah17:08
cmurphyi wonder if there's a way we could reuse the keystoneauth plugin model for this, where it has a plugin class with a method class as an attribute https://opendev.org/openstack/keystoneauth/src/branch/master/keystoneauth1/identity/v3/password.py17:08
lbragstadat the same time, i want people to be able to extend an interface if they want to add a new model (as opposed to extending Enforcer)17:08
lbragstadcmurphy that's a good idea17:08
lbragstadthis is all internal stuff at this point17:09
lbragstadso we can evolve it17:10
cmurphymaybe Enforcer has self.enforcer = _FlatEnforcer and Enforcer.enforce() calls self.enforcer.enforce()17:10
cmurphyand then project_id etc wouldn't need to be duplicated?17:10
cmurphyi don't think the current way is bad though17:10
lbragstadhow would _FlatEnforces implementation get the project id in question?17:10
lbragstad_FlatEnforcer's*17:11
cmurphyhm i guess that doesn't really solve that problem17:11
* lbragstad can document this, too17:13
bnemecLike lbragstad said, this is all private stuff right now anyway. If people want to extend it to other enforcement models then maybe we can have a discussion over the best way to expose this then?17:14
cmurphy++17:14
lbragstadtrue17:14
bnemecHaving a specific use case in mind would probably help with the design too.17:14
cmurphyi can't really think of a better way to handle it at the moment17:14
lbragstadat the same time - it works17:15
cmurphy++17:15
bnemecShip it!17:15
lbragstadFILGTM!17:15
lbragstadalright - moving on17:15
lbragstadhttps://review.opendev.org/#/c/667452/317:15
cmurphywould probably be good to have tests for this one somehow17:16
*** Horrorcat has quit IRC17:16
lbragstadyeah - so this is what i was kinda talking about ealier17:16
lbragstadearlier*17:16
lbragstadmaybe what we can do is add a super *super* basic functional testing frame work in the ksa patch17:17
lbragstadthat only tests to make sure we can instantiate an Enforcer without the connection to keystone (in a devstack) deployment without it blowing up17:17
lbragstadhaving that in place would make it a little easier to introduce functional tests here17:18
cmurphy++17:18
lbragstad(i tested this logic, but i was using the script in the next patch set)17:18
bnemecIf a functional test framework could replace the test script that would be good.17:19
lbragstad++17:19
lbragstadi feel like the natural evolution of that script is to just make it an official functional test17:19
bnemecYep17:20
lbragstadcool17:20
lbragstadanything else on this patch, outside of testing?17:20
*** Horrorcat has joined #openstack-keystone17:21
cmurphyit seems like a good first iteration to me, i'm sure down the road we can find ways to improve the enforce logic17:22
* lbragstad nods17:22
bnemecI probably just need to take a closer look. I got nothing useful done last week because downstream, so I haven't been through this part of the series yet. :-/17:22
lbragstadok - well it sounds like having functional testing there is useful so we can do that part in the meantime17:23
lbragstadfinally we have https://review.opendev.org/#/c/667242/717:23
lbragstadwhich is just documentation and a usage example17:23
bnemecBut like I've said before, I'm pretty much ready to +2 anything that gets us _an_ implementation. If it's horribly broken, we'll fix it. :-)17:23
lbragstadsome of that example is going to get pulled into a formal functional test thought17:23
lbragstadthough*17:23
bnemecSo to try that I would stand up a basic devstack, pull the series and install it, then run the example.py script?17:25
lbragstadyeah17:25
bnemecTweaking the example.conf for my devstack, of course.17:25
cmurphyyou'd probably need to edit the project ids in the script17:25
lbragstadyou'll need to create a few limits and the registered limits17:25
lbragstadand do what cmurphy said, update the project ids in the script17:26
bnemecMakes sense.17:26
lbragstadbut yeah - it should work17:26
lbragstadok - so to summarize17:26
lbragstad666085 needs a functional testing framework and a bug open to investigate reusable ksa connections17:27
lbragstad666444 needs an open bug to investigate pluggable architectures for enforcement models17:27
lbragstad667452 needs functional testing (built on the action from 666085)17:28
lbragstadanything else?17:28
cmurphyi think this script will need to be tweaked for the two-level model?17:28
bnemecMaybe a bug for 666085 to look at how to configure the endpoint?17:28
knikollacmurphy: sorry for missing the meeting. we're transitioning to the new adjutant based registration system and i've been swamped with work the past few weeks.17:29
lbragstadyeah - i developed it to help me write the flat enforcement stuff, i wasn't really thinking about any of the strict-two level properties17:29
lbragstadbnemec ++17:29
cmurphyno worries knikolla17:29
lbragstadoutside of those actions, does anyone have anything else to add?17:30
cmurphylbragstad: and i guess next steps after all that would be implementing enforce() for the two-level model17:30
lbragstadcmurphy correct17:31
cmurphyfun :)17:31
lbragstadi was thinking it would be easier to implement that once the functional testing is in place17:31
cmurphyfor sure17:31
lbragstadthen we could actually use TTD to get it done17:31
lbragstadopposed to a hacktastic script17:31
bnemecYeah, right now we're mostly trying to define the public interface so other projects can start looking at how it would integrate with them.17:32
lbragstadtrue17:32
bnemecAdditional enforcement models can be done in parallel.17:32
lbragstada lot of this actually came from johnthetubaguy17:32
lbragstadi might have to poke someone to help with setting up zuul for the functional testing bits17:33
lbragstad(we'll need a basic devstack in order to do that)17:33
bnemecWe have some functional tests in other oslo projects, so we might be able to help with that.17:34
lbragstadsweet17:35
lbragstadanything else to touch on for this?17:35
cmurphynot from me17:35
lbragstadotherwise - that's about all i had17:36
bnemecI'm good too. Thanks again for driving this!17:36
cmurphy++ thanks lbragstad17:36
lbragstadno problem - thanks for taking the time to go through the patches17:36
lbragstadi'll write up a recap and send it to the ML17:36
cmurphysweet17:37
bnemecdude17:37
cmurphy:'D17:37
lbragstaddude!17:37
cmurphy#endmeeting17:37
*** openstack changes topic to "Stein release schedule: https://releases.openstack.org/stein/schedule.html | Meeting agenda: https://etherpad.openstack.org/p/keystone-weekly-meeting | Bugs that need triaging: http://bit.ly/2iJuN1h | Trello: https://trello.com/b/rj0ECz2c/keystone-stein-roadmap !!NOTE!! This Channel is Logged ( https://tinyurl.com/OpenStackKeystone )"17:37
openstackMeeting ended Tue Jul  2 17:37:43 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone_office_hours/2019/keystone_office_hours.2019-07-02-16.35.html17:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone_office_hours/2019/keystone_office_hours.2019-07-02-16.35.txt17:37
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone_office_hours/2019/keystone_office_hours.2019-07-02-16.35.log.html17:37
bnemecOn an unrelated note, I just sent in my laptop refresh request for an X1C.17:38
bnemecIf I hate it I'm blaming all of you. :-P17:38
openstackgerritMerged openstack/keystone-specs master: Update access rules spec with decisions from PTG  https://review.opendev.org/66178417:38
cmurphyyou're gonna love it17:38
gagehugonice17:39
bnemecYeah, my bigger fear is that it's going to make me want to upgrade my personal laptop. :-)17:39
*** cmurphy changes topic to "Train release schedule: https://releases.openstack.org/train/schedule.html | Meeting agenda: https://etherpad.openstack.org/p/keystone-weekly-meeting | Bugs that need triaging: http://bit.ly/2iJuN1h | Trello: https://trello.com/b/rj0ECz2c/keystone-stein-roadmap !!NOTE!! This Channel is Logged ( https://tinyurl.com/OpenStackKeystone )"17:40
*** ChanServ changes topic to "Stein release schedule: https://releases.openstack.org/stein/schedule.html | Meeting agenda: https://etherpad.openstack.org/p/keystone-weekly-meeting | Bugs that need triaging: http://bit.ly/2iJuN1h | Trello: https://trello.com/b/rj0ECz2c/keystone-stein-roadmap !!NOTE!! This Channel is Logged ( https://tinyurl.com/OpenStackKeystone )"17:40
cmurphykmalloc: chanserv says you have +Aefortv and can probably do ^17:44
kmallochm?17:44
kmallocwaht do you need?17:44
cmurphyi noticed the topic is pointing to the Stein release schedule17:44
kmallocoh yeah, all cores should have topic setting rights (through chanserv)17:44
kmalloca few of us can op and direct set the topic17:44
cmurphyChanServ: You are not authorized to perform this operation.17:45
kmallocbnemec: i don't like the X1C corporate set.17:45
kmalloccmurphy: doing it w/ msg to chanserv?17:45
cmurphykmalloc: yes17:45
kmallocweird.17:46
kmallocsec.17:46
kmallocwhat is the trello link?17:46
kmallocgot it17:46
*** nickthetait has quit IRC17:46
bnemecI think I had to do it through the openstack bot, but then nobody in the oslo channel has +o either.17:46
cmurphyhttps://trello.com/b/ClKW9C8x/keystone-train-roadmap17:46
bnemeckmalloc: Now you tell me. :-P17:46
cmurphyopenstack: help17:46
*** ChanServ changes topic to "Train release schedule: https://releases.openstack.org/train/schedule.html | Meeting agenda: https://etherpad.openstack.org/p/keystone-weekly-meeting | Bugs that need triaging: http://bit.ly/2iJuN1h | Trello: https://trello.com/b/rj0ECz2c/keystone-stein-roadmap !!NOTE!! This Channel is Logged ( https://tinyurl.com/OpenStackKeystone )"17:47
cmurphythanks kmalloc17:47
kmalloccmurphy try: /msg chanserv topic #openstack-keystone Train release schedule: https://releases.openstack.org/train/schedule.html | Meeting agenda: https://etherpad.openstack.org/p/keystone-weekly-meeting | Bugs that need triaging: http://bit.ly/2iJuN1h | Trello: https://trello.com/b/rj0ECz2c/keystone-stein-roadmap !!NOTE!! This Channel is Logged ( https://tinyurl.com/OpenStackKeystone )17:47
cmurphykmalloc: that's what i did17:47
kmallocweird.17:47
kmalloclet me fix your perms17:47
kmallocoh wow, looks like someone stripped all the extra perms you had down to +oO =/17:48
kmalloccmurphy: try now17:49
kmallocshould be fixed17:49
*** ChanServ changes topic to "Train release schedule: https://releases.openstack.org/train/schedule.html | Meeting agenda: https://etherpad.openstack.org/p/keystone-weekly-meeting | Bugs that need triaging: http://bit.ly/2iJuN1h | Trello: https://trello.com/b/ClKW9C8x/keystone-train-roadmap !!NOTE!! This Channel is Logged ( https://tinyurl.com/OpenStackKeystone )"17:51
kmallocbnemec: it's screen resolution issues.17:51
cmurphyyay17:51
cmurphyty17:51
kmallocbnemec: 1080p sucks :(.17:51
kmallocsure thing17:52
kmallocgagehugo: you are not registered with nickserv (apparantly) I can't give you perms to change topic (+tv) on the channel17:52
*** gyee has quit IRC17:52
*** ChanServ sets mode: +o kmalloc17:52
gagehugohmm17:52
*** kmalloc sets mode: -o kmalloc17:52
kmallocnvm17:53
kmallocfixed it17:53
kmallocwas a typo on my end17:53
bnemecOh, well I'm not too concerned about that. Almost all of my displays are still 1080P.17:53
kmallocbnemec: i can't work on 1080p, 1440p on a laptop, 4k on desktop17:53
gagehugoah ok17:54
kmallocalso OMG, I'm so sick of construction... it's making my whole house vibrate because they're redoing gas lines 3 blocks away17:54
kmalloci can't concentrate.....17:54
kmalloccan't wait to move out of this house...17:54
bnemecIt's always nice when the place you're leaving gives you the proverbial finger on the way out so you don't feel bad about it. :-)17:56
*** jamesmcarthur has quit IRC17:56
cmurphystepping out for a couple of hours18:01
lbragstadspeaking on x1c - has anyone upgraded theirs?18:02
kmallocbnemec: yeah but before we move out, they'll be doing the gas lines in front of our house....soooooo it's going to be 10x as bad18:02
kmalloclbragstad: can't custom configure the x1c7 yet18:02
kmallocso, nope.18:02
kmallocor couldn't recently18:02
kmalloclbragstad: ah they have a 1440p+i7 now18:03
kmallocuntil recently that didn't exist18:03
kmalloc4k*18:03
gagehugonot yet18:03
kmallocnot 1440p18:04
gagehugono ice lake in x1c7 :(18:04
lbragstadis it possible to send lenovo a laptop and stay "put this in it"18:04
*** gyee has joined #openstack-keystone18:06
kmalloclol18:07
*** jdennis has quit IRC18:20
openstackgerritBrian Haley proposed openstack/keystone master: DNM: test patch to use f29 nodeset from devstack  https://review.opendev.org/66872918:24
*** jdennis has joined #openstack-keystone18:29
openstackgerritMerged openstack/oslo.limit master: Rename filter_resource resource_filters  https://review.opendev.org/66852318:42
*** dancn has joined #openstack-keystone19:02
*** xek has quit IRC19:08
*** jamesmcarthur has joined #openstack-keystone19:21
*** jamesmcarthur has quit IRC19:28
lbragstadhttp://lists.openstack.org/pipermail/openstack-discuss/2019-July/007487.html19:38
*** jamesmcarthur has joined #openstack-keystone19:47
*** jamesmcarthur has quit IRC19:50
*** raildo has quit IRC19:52
*** bnemec has quit IRC19:54
*** vishakha has quit IRC19:56
*** raildo has joined #openstack-keystone20:01
*** bnemec has joined #openstack-keystone20:07
*** vishalmanchanda has quit IRC20:33
*** brett-soric has joined #openstack-keystone20:37
*** evrardjp has quit IRC20:51
*** evrardjp has joined #openstack-keystone20:52
*** pcaruana has quit IRC20:58
*** raildo has quit IRC21:11
*** jamesmcarthur has joined #openstack-keystone21:22
*** bnemec has quit IRC21:25
*** jamesmcarthur has quit IRC21:27
*** brett-soric has left #openstack-keystone21:27
*** bnemec has joined #openstack-keystone21:27
openstackgerritColleen Murphy proposed openstack/python-keystoneclient master: Blacklist bandit 1.6.0 & cap sphinx for 2.7  https://review.opendev.org/66060922:59
*** tkajinam has joined #openstack-keystone23:02
openstackgerritColleen Murphy proposed openstack/keystone-specs master: Add Python 3 Train unit tests  https://review.opendev.org/66775523:16
*** dancn has quit IRC23:41

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