Thursday, 2017-02-16

*** bswartz has quit IRC00:12
*** sdague has quit IRC00:18
*** ricolin has joined #openstack-meeting-cp00:57
*** ricolin has quit IRC01:15
*** diablo_rojo_phon has quit IRC01:20
*** diablo_rojo has quit IRC02:26
*** gouthamr has quit IRC03:44
*** ricolin has joined #openstack-meeting-cp04:08
*** ricolin has quit IRC05:33
*** ricolin has joined #openstack-meeting-cp05:46
*** MarkBaker has quit IRC06:59
*** MarkBaker has joined #openstack-meeting-cp07:44
*** MarkBaker has quit IRC08:38
*** MarkBaker has joined #openstack-meeting-cp09:43
*** MarkBaker has quit IRC09:44
*** ricolin has quit IRC09:59
*** sdague has joined #openstack-meeting-cp11:06
*** MarkBaker has joined #openstack-meeting-cp11:43
*** mars has joined #openstack-meeting-cp12:15
*** gouthamr has joined #openstack-meeting-cp13:15
*** gouthamr has quit IRC13:42
*** gouthamr has joined #openstack-meeting-cp13:43
*** kberger has quit IRC14:06
*** kberger has joined #openstack-meeting-cp14:06
*** MarkBaker has quit IRC14:23
*** MarkBaker has joined #openstack-meeting-cp15:03
*** MarkBaker has quit IRC15:13
*** edtubill has joined #openstack-meeting-cp15:28
*** MarkBaker has joined #openstack-meeting-cp15:29
*** MarkBaker has quit IRC15:36
*** rderose has quit IRC15:39
*** diablo_rojo has joined #openstack-meeting-cp15:49
*** MarkBaker has joined #openstack-meeting-cp15:56
*** lamt has joined #openstack-meeting-cp16:03
*** rdotcom has quit IRC16:09
*** MarkBaker has quit IRC16:18
*** MarkBaker has joined #openstack-meeting-cp16:31
*** mriedem has joined #openstack-meeting-cp16:53
*** MarkBaker has quit IRC16:56
ildikov#startmeeting cinder-nova-api-changes17:00
openstackMeeting started Thu Feb 16 17:00:11 2017 UTC and is due to finish in 60 minutes.  The chair is ildikov. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: cinder-nova-api-changes)"17:00
openstackThe meeting name has been set to 'cinder_nova_api_changes'17:00
ildikovscottda DuncanT ameade cFouts johnthetubaguy jaypipes takashin alaski e0ne jgriffith tbarron andrearosa hemna erlon mriedem gouthamr ebalduf patrickeast smcginnis diablo_rojo gsilvis  xyang1 raj_singh lyarwood17:00
smcginnisildikov: Sorry, gotta miss today. Will catch up on logs later today.17:00
hemnayough17:00
*** jaugustine has joined #openstack-meeting-cp17:01
breitzo/17:01
mriedemo/17:01
ildikovsmcginnis: np17:01
ildikovlet's wait a bit, although as we're so close to the PTG we might not have that many attendees today17:02
*** jungleboyj has joined #openstack-meeting-cp17:03
ildikovall right, let's start17:03
hemnaon your marks....get set.....17:04
ildikovhemna: :)17:04
* jungleboyj is lurking.17:04
ildikovso we have the spec on the Nova side to capture how to get Nova to work with the new Cinder API17:04
ildikov#link https://review.openstack.org/#/c/373203/17:05
ildikovit would be great to check on the problematic items in it and figure out the preferred way forward next week17:05
hemnalots of mriedem feedback there.17:05
ildikovwe are looking into a few cases, like breitz is working on BfV and I try to look into shelve17:06
hemnathe Cinder API is in place, so isn't it just a matter of talking about how to use it and adjusting on v2 vs v3 availability?17:06
ildikovhemna: yep, there's quite some, I hope johnthetubaguy will have some time too to check the comments17:06
* jgriffith sneaks in the back of the room17:07
* johnthetubaguy sneaks in too17:07
* scottda sneaks in, hiding behind jgriffith and johnthetubaguy17:07
ildikovhemna: switching to v3 is one thing, using the new attach/detach API is another17:07
mriedemi need johnthetubaguy to approve https://review.openstack.org/#/c/424428/17:07
hemnayou know, the kids in the back of the class always get called on first.....17:07
ildikovjgriffith: johnthetubaguy: scottda: I'm not biting ya know ;)17:07
jungleboyjI lurked at the front and haven't been bitten yet.  ;-)17:08
ildikovjohnthetubaguy: did you have a chance to look into the comments on the Nova spec?17:08
ildikovI guess that's a no :)17:10
ildikov#action homework to all kids in the room to check the spec and comments to have a common ground for discussion next week17:11
ildikovas we have multi-attach as one of the goals here we also need to look into what needs to be done on the Cinder side17:12
mriedemmy hope for the PTG session is,17:13
ildikovjgriffith: do you think we need a slot for this next week or it's less difficult than that?17:13
mriedemjohnthetubaguy can give us the high-level on th spec since a lot of nova cores won't have read it yet,17:13
mriedemand then we can dig into the sticking points that i've -1ed on the spec, which can lead to discussion about what we need out of the cinder API, if anything17:13
ildikovmriedem: +117:14
jgriffithildikov I think that's up to the Nova reps, IMHO it's not that difficult17:14
mriedemwe already have a nova/cinder slot on thursday morning17:14
ildikovmriedem: I will sync up with johnthetubaguy so we have some items on an etherpad as a starting point17:14
mriedembecause we have other tihngs than multiattach to talk about17:14
jgriffithI just need solid guidance on the whole api version thing, and I think mriedem 's plan on that may be the best way to go17:14
jgriffithmriedem yes, yes WE do :)17:14
ildikovjgriffith: I meant more how to handle detach on the Cinder side for instance with the different back ends17:14
jgriffithildikov so that's a Cinder problem only IMO17:15
jgriffithildikov and I we've pretty much got a design on how that needs to work17:15
ildikovjgriffith: sorry, I meant whether we need a slot on the Cinder agenda or not17:15
jgriffithildikov oh17:15
jgriffithsorry17:15
jgriffithYES17:15
jgriffithI want to make sure we're all on the same page, and in face2face is the best way to do that17:16
jgriffithand it means I can use a whiteboard :)17:16
ildikovjgriffith: ok, I will add it somewhere on the Cinder etherad then, tnx :)17:16
ildikovjgriffith: lol :)17:16
hemnaildikov, I have my multi-attach patch up in Cinder17:17
jungleboyjjgriffith: Bingo!17:17
jgriffithhemna wait.. what?17:17
hemnahttps://review.openstack.org/#/c/428365/17:17
hemnait makes it work :P17:17
jgriffithoh, capabilities clean-slate17:17
ildikovmriedem: my hope is that we don't need to talk that much about the multi-attach parts during the Cinder-Nova session, maybe don't need to talk about it at all17:17
jungleboyjhemna: :-p17:17
hemnajgriffith, yah I think that's what we wanted right ?17:17
hemnaat least from the last meeting17:18
jgriffithhemna indeed!17:18
jgriffiththanks!17:18
hemnacoolio17:18
mriedemildikov: we will because only like 1 other person in nova has read john's spec17:18
mriedemjohn garbutt's i mean17:18
mriedemwe have all sorts of issues to work out wrt upgrades, evacuate, live migration, etc17:18
ildikovthat's true, although that's more about how to make the new attach/detach calls work17:19
mriedemildikov: hemna: also in case you haven't noticed yet, i completely molested https://review.openstack.org/#/c/335358/ last night17:19
hemnathat sounds dirty17:19
ildikovmriedem: I need to take a few more breaths before going into that... ;)17:19
mriedemhemna: that was the idea :)17:20
ildikovmriedem: I haven't check all the comments yet, but frankly I hope I don't need to write a spec to clean up some mess in the soon to be old flow17:20
jungleboyj*smh*17:20
ildikov*checked17:20
ildikovmriedem: we can live without that patch, but I think it will make it even harder to have a clean new attach flow17:21
mriedemildikov: it's gotten much more complicated than i originally though, and it's an api behavior change, so i think a short spec just to get other nova cores on the same page might be prudent17:21
mriedemildikov: but we could hold off on that until next week17:21
mriedemi think it's the correct long-term direction, to reserve in the API,17:22
mriedembut the mechanics are difficult17:22
ildikovmriedem: API behavior change in case of failure you mean?17:22
mriedemildikov: no, that we reserve the volume in the API now17:22
mriedemrather than not at all for BFV17:22
mriedemit's an internal change, but it might be noticeable17:22
ildikovmriedem: so with the new flow we will have attachment-create for reserve and that's how the PoC is implemented today17:23
mriedemi just want more people (like dansmith and jaypipes) in the know on that idea17:23
ildikovmriedem: it was a BfV case where we didn't, but for everything else I think the volume was always reserved in the API17:23
jgriffithle sigh17:24
ildikovmriedem: so that patch is about to remove check_attach as the functionality is  in the current reserve_volume17:24
mriedemyes i know17:24
mriedemi'm aware :) from the molesting, remember?17:24
ildikovmriedem: and it turned out that reserve as a matter of fact is missing from BfV, not all the cases but one or maybe two17:25
mriedemin the case that we are given a volume, that's the change17:25
mriedemif nova creates the volume during BFV, there is no reserve to be done17:25
mriedembut you'll see more comments about that inline17:25
ildikovmriedem: if you would've molested my patch about 9 months ago, I wouldn't have reacted like this ;)17:26
ildikovmriedem: ok, I will check all the comments in line and we can have a 10 minutes chat about it next week17:27
ildikovmriedem: and I hope a Launchpad blueprint will do as a "worst case scenario"17:27
ildikovmriedem: does it sound ok?17:27
mriedemwe can talk about the spec next week, a bp doesn't give the level of detail or doc artifact that a spec does for a big change17:29
mriedembefore any of that though, we can talk about the general idea with the nova group17:29
mriedemthat's the main thing i want17:29
mriedemmore visibility17:29
ildikovso this started as a bug fix and I'm happy to quick update the whole core team about it next week in like 3 minutes and then talk about it at most 7 so we can move to the more complex things like migrate or evacuate or upgrade17:30
ildikovor we can add a separate slot for it next week to not eat up the time of the Cinder-Nova slot with this marginal item17:31
ildikovmriedem: is there 10 minutes in the Nova agenda for this?17:31
mriedemildikov: it's going to take however long it's going to take17:32
mriedemi don't want to get into a fight about what you consider a 10 minute issue17:33
mriedemthis is not a trivial change17:33
mriedemand if we screw it up we'll have volumes left in attaching state17:33
mriedemthat the admin will have to reset on the cinder side17:33
ildikovmriedem: sure, my point was more to have it on the pure Nova agenda so we can discuss the interaction related things on the joint session17:33
mriedemit's related to cinder so we can talk about it at that time17:33
mriedemcan we move on?17:33
mriedemi'm trying to get ocata GA'ed today17:34
ildikovmriedem: ok, let's not go down the rabbit hole of how much it's related to what17:35
ildikovhopefully next week face2face will make this easier17:35
ildikovI think we are mainly clear on what needs to be discussed next week17:37
mriedemyes i hope so, i need other cores in the know about this, but we've all been heads down on getting ocata out the door and the things that were priorities for that release17:37
* jungleboyj mic comes from the ceiling "Let's Get Ready to RRRRRRRRUMBLE!!!!!!!!!!"17:37
ildikovmriedem: sure, I get that part17:38
ildikovmriedem: jgriffith: do you have any items in mind we would need to touch on today in prep for next week?17:38
mriedemwhat else do we need to discuss in this meeting?17:38
jgriffithildikov nah, nothing worth going in to here17:39
ildikovI will add the multi-attach slot to the Cinder etherpad and sync up with johnthetubaguy about having the summary up for the spec and prepare a short draft agenda of items we need to to touch on17:39
ildikovI will also add the remove check_attach topic to the Cinder-Nova slot17:39
ildikovI think these are the main big items17:40
johnthetubaguyyeah, got dragged into other things today, but was hoping to do the cinder spec today/yesterday17:40
ildikovplease shout now if I missed anything17:40
ildikovjohnthetubaguy: if there isn't one yet we can create an etherpad for the cross-porject slot and add some notes there for people who're not aware of the  whole spec (yet)17:41
mriedemthere isn't a xp etherpad, it's just in https://etherpad.openstack.org/p/nova-ptg-pike17:42
ildikovmriedem: I will create one then if you don't mind and will add the link to the Nova and Cinder etherpads too17:44
mriedemthat's fine17:44
ildikovmriedem: cool, tnx17:45
ildikovok, if nothing else we can wrap up here17:45
ildikovthanks everyone17:46
ildikovsafe travels! :)17:46
ildikovsee you next week! :)17:46
ildikov#endmeeting17:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:47
openstackMeeting ended Thu Feb 16 17:47:19 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder_nova_api_changes/2017/cinder_nova_api_changes.2017-02-16-17.00.html17:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder_nova_api_changes/2017/cinder_nova_api_changes.2017-02-16-17.00.txt17:47
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder_nova_api_changes/2017/cinder_nova_api_changes.2017-02-16-17.00.log.html17:47
*** mriedem has left #openstack-meeting-cp17:47
*** diablo_rojo has quit IRC18:24
*** jaugustine__ has joined #openstack-meeting-cp18:27
*** jaugustine has quit IRC18:28
*** jaugustine__ is now known as jaugustine18:28
*** rdopiera has joined #openstack-meeting-cp19:07
*** edtubill has quit IRC19:30
*** diablo_rojo has joined #openstack-meeting-cp19:48
*** MarkBaker has joined #openstack-meeting-cp19:57
*** gagehugo has joined #openstack-meeting-cp19:57
robcresswell#startmeeting keystone_horizon20:00
openstackMeeting started Thu Feb 16 20:00:00 2017 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: keystone_horizon)"20:00
openstackThe meeting name has been set to 'keystone_horizon'20:00
lbragstado/20:00
robcresswello/20:00
david-lyleo/20:00
lbragstadrobcresswell wow - nice timing, you started the meeting exactly as my client hit 14:00:0020:00
robcresswelllbragstad: I do my best20:01
lbragstadagenda #link https://etherpad.openstack.org/p/ocata-keystone-horizon20:01
rdopierao/20:01
* lbragstad bets robcresswell is a fan of automation 20:01
robcresswelllbragstad: I actually just happened to be looking at my client :p20:01
robcresswellSorry to disappoint20:01
lbragstadlol20:01
robcresswellSo I wanted to kick these off again and keep using the meeting slot; if we dont use the hour, thats obviously not a problem20:02
robcresswellLast cycle was really, really helpful for Horizon in solving some key issues, and helpful for me personally in understanding how the **** domains work20:02
*** lamt has quit IRC20:03
robcresswellThe first thing to do is probably review the etherpad and cross off work that is completed20:03
robcresswellThere are also some outstanding patches in Horizon that im not entirely sure of, so would be good to discuss now or in the future meetings.20:03
lbragstadi spent some time trying to do that last week20:03
robcresswellAh nice, thanks20:04
robcresswellAnything anyone would like to start with?20:05
robcresswellWorking through then...20:05
robcresswell#link https://review.openstack.org/#/c/339487/20:05
robcresswellThis got flagged again today as a potential solution to a problem someone was having in the horizon channel20:06
lbragstadis cmurphy around?20:06
robcresswellI've not looked at it yet, david-lyle, cmurphy, thoughts?20:06
*** ayoung has quit IRC20:07
david-lylei haven't reviewed that yet20:07
david-lylebut not sure user20:07
david-lyles20:07
david-lyleargh20:07
robcresswellAh you -1'd it a while back20:07
robcresswellJust wondered if you'd seen it recently, but np20:07
david-lylenot sure user's domain id is the right policy target even if one is warranted20:08
*** lamt has joined #openstack-meeting-cp20:08
david-lyleshould be the domain I'm auth'd into20:08
david-lyleI believe20:08
lbragstadso the domain of the project you've scoped your token to, or the domain scope of your token?20:08
david-lylebut our cross-domain user support is woefully inadequate in general20:09
david-lyledomain scope for identity operations20:09
david-lylewhat we really need is to figure out the cross-openstack answer for what can I do20:10
david-lylebecause our policy implementation is limited to what we've seen, but you could add random required policy targets in your policy files and Horizon wouldn't handle them unless it's something we populate by default20:11
lbragstadyeah20:11
robcresswellcapabilities API?20:12
lbragstadthought be the ideal solution I would think20:12
lbragstadthat would be*20:12
* lbragstad can't type20:12
david-lylebut we have the several releases until we get that even being optimistic20:13
david-lyleso we'll do what we can20:13
robcresswellYeah, I know Nova have mentioned it a few times too.20:13
robcresswellRight20:13
lbragstadfwiw - there is going to be a time slot dedicated to capabilities during the Arch WG sessions on tuesday20:13
* robcresswell loses track of the WG's20:14
lbragstad#link https://etherpad.openstack.org/p/ptg-architecture-workgroup20:14
lbragstadI don't believe they have time slots allocated yet20:14
lbragstadbut it's in their list of topics20:14
robcresswellOkay, lets keep an eye on that20:15
david-lyleah, I see that patch is targeting the sample v3 example policy, should still be scoped domain not user domain I think20:15
robcresswellSo, the domain of the project, is that?20:16
lbragstadyeah - because technically there is nothing stopping a user in one domain from having role assignments on other domains20:16
lbragstadwell - that's tricky too because it depends20:17
david-lylecross-domain user support should be added to the etherpad20:17
david-lyleit blocked part of cmurphy's patch to doa20:17
lbragstadas a user of keystone, i can explicitly ask for a token scoped to a specific domain that I have a role on, or I can ask for a token scoped to a project in some random domain20:17
david-lylebut I only have permission based on the scope of my current token20:18
david-lyleso it would be the domain I auth'd into to20:18
david-lyleno?20:18
* david-lyle reviews v3 sample policy again, crying softly20:19
lbragstadright - would authenticating for a specific scope be considered just that?20:19
david-lylebut the target is the project.domain_id, hmm20:20
david-lyleI need more time to walk that through20:20
lbragstadhttp://cdn.pasteraw.com/6badyzj32kns0bjhbbxk58zsc59hxrq20:20
*** ayoung has joined #openstack-meeting-cp20:20
lbragstad^ that would technically give me a token scoped to a domain20:21
david-lylethe target will be  the project.domain_id and then the horizon policy will match that in the credentials check20:21
david-lyleso either cloud_admin, domain_admin for the target domain20:22
david-lylethe patch may be right20:22
*** gouthamr has quit IRC20:24
robcresswellI need some time to get my round this :/20:25
david-lyleI think the logic is correct, we just didn't include the targets as specified in v3 sample policy20:26
lbragstaddo we think this is something we need more involvement in from other projects, too?20:26
*** _-___-_ has joined #openstack-meeting-cp20:26
*** _-___-_ has left #openstack-meeting-cp20:26
david-lylelbragstad: which part?20:26
lbragstaddavid-lyle the domain parts20:26
lbragstaddavid-lyle or the *which* domains part20:26
robcresswellThis particular issue just seems like part of the underlying horizon-keystone domain confusion20:27
lbragstaddavid-lyle because you also mentioned the "what can this use do across OpenStack" point of view20:27
david-lyleso my understanding is... this really only effects keystone and horizon, the other projects' policies are completely project based20:28
lbragstadok20:28
david-lyleso they only use the project scoped token20:28
david-lyledomain token is only used for identity operations20:28
lbragstadso this should be something we can whiteboard next week20:28
david-lyleyes20:29
lbragstad(pending everyone has time to digest the information)20:29
david-lyleI think we just missed the target when we added support for the v3 sample20:29
david-lyleand this bug will cover that, or the target was added later, I'm unsuer20:29
david-lyle*unsure20:29
robcresswellI'll take a look at it over the next week20:31
robcresswellwell, maybe the week after due to PTG, but before next meeting20:31
robcresswellAssuming I can wrap my tiny UI brain around these lofty auth concepts :p20:31
david-lyleI will draw pictures :P20:32
david-lyleI lived domain hell for a long time20:32
* lbragstad *loves* pictures20:32
robcresswellOkay to move on for now? I see rdopiera has dropped a review on it too20:33
david-lylethe other 2 patches in the first block still need review20:33
david-lyleerr 1 other20:33
david-lyle1 merged20:33
robcresswellyep20:33
lbragstad#link https://review.openstack.org/#/c/397332/2 this guy?20:34
david-lyleyes, it looks fine, I just want to test to make sure20:35
david-lyleno point in wasting the effort of trying to get a domain scoped token in a single domain env20:35
david-lylethe base policy file will handle things20:35
david-lylewithout the domain scoped token20:36
robcresswellAh, yeah that looks a little more straightforward20:36
robcresswellWould be nice to add a separate test for it I think20:38
*** kberger has quit IRC20:39
*** gouthamr has joined #openstack-meeting-cp20:40
david-lyleso down to the PCI entry I think is done20:40
david-lylethere are a couple of potentially unaddressed bugs in domain-admin support section20:41
lbragstadyeah - that's what I spent a bunch of time on last week, trying to figure out what was left20:41
lbragstad(PCI ^)20:41
david-lyledid we figure out how to get the passwd strength regex to horizon?20:42
lbragstaddavid-lyle into horizon?20:43
david-lyleyes20:43
lbragstadkeystone now expose it through an api20:43
robcresswellSide note, isn't the hard requirement on subsets of characters considered bad practice?20:43
david-lyleok, I was trying to read through the patches20:43
lbragstadimplemented here - #link https://review.openstack.org/#/q/topic:bp/pci-dss-password-requirements-api20:44
lbragstaddocs #link https://developer.openstack.org/api-ref/identity/v3/index.html?expanded=show-domain-group-option-configuration-detail#domain-configuration20:44
lbragstadGET /v3/domains/default/config/security_compliance/password_regex20:46
* david-lyle can20:46
david-lyleI may regret asking this, keystone doesn't support microversions, correct?20:47
lbragstaddavid-lyle correct20:47
robcresswell:D20:47
lbragstaddavid-lyle it's actually one of the *first* things we talk about next week20:47
robcresswellplease no20:47
robcresswell:)20:47
lbragstadno what?20:47
david-lyleso in an older v3 install, I just get a 404?20:47
robcresswellplease no microversions20:48
lbragstaddavid-lyle correct - we had to be careful with that20:48
robcresswellI'm not a fan, though I can explain why separately.20:48
lbragstaddavid-lyle because it exposes config over the api20:48
lbragstadrobcresswell i'd be interested in hearing your view point20:49
david-lyleok, so for a while horizon will have to check, but if 404 use our internal setting20:49
lbragstaddavid-lyle I believe so - but let me double check the logic20:49
robcresswelllbragstad: I'll message after the meeting if you like, or I can drop in on your PTG session.20:49
lbragstadrobcresswell first thing wednesday morning - https://etherpad.openstack.org/p/pike-ptg-keystone-ocata-carry-over20:49
robcresswelldavid-lyle: Yeah, I suppose so20:50
robcresswelllbragstad: Got it20:50
david-lylerobcresswell: grab me before you go, as I will forget :P20:50
robcresswelldavid-lyle: Ha will do20:50
lbragstadrobcresswell i'd still be interested in hearing the gist of it prior to the PTG though20:50
robcresswellsure20:51
*** ducttape_ has quit IRC20:51
*** ducttape_ has joined #openstack-meeting-cp20:51
david-lylerobcresswell: do we have a microversion support group session as part of horizon's time at the PTG?20:51
lbragstaddavid-lyle https://github.com/openstack/keystone/blob/master/keystone/resource/core.py#L111520:52
robcresswelldavid-lyle: Whatever bar I end up in on Tuesday night20:52
lbragstadit should be either a 404 or a 403 if the option is not set20:52
david-lyleok, we can handle that20:52
lbragstadand it should be something that you can get with a valid token20:53
lbragstad(as opposed to other things in the domain config - which typically require admin)20:53
david-lyleright the policy was default20:53
david-lyleerr ""20:53
cmurphyhi - sorry this meeting slipped my mind, i'll have a look at 33948720:53
lbragstaddavid-lyle yeah - we shimmied that in here and beat with a hammer until it worked - https://github.com/openstack/keystone/blob/master/keystone/resource/controllers.py#L188-L19720:54
david-lyleseems like time is low20:58
david-lyleanything pressing to hit in the last couple of minutes?20:58
david-lylewe can talk more about "Looking Forward" next week20:59
robcresswellNothing else from me20:59
lbragstadnot that i know of - if there is something we need to add to the agenda next week let me know20:59
robcresswellThanks for attending; I'll keep sending out the email reminders etc20:59
lbragstador add it20:59
lbragstadhttps://etherpad.openstack.org/p/pike-ptg-keystone-horizon20:59
lbragstad#link https://etherpad.openstack.org/p/pike-ptg-keystone-horizon20:59
robcresswelllbragstad: If you could give the weekly meeting a shout out during the PTG that would be much appreciated21:00
david-lylehorizon folks will be loitering the second half of the week so pull us in as needed21:00
lbragstadrobcresswell will do - to get more keystone devs involved?21:00
lbragstadI assume?21:00
* david-lyle may be speaking for himself only21:00
robcresswelllbragstad: Just so people are aware its ongoing21:00
lbragstad++21:01
lbragstadwill do21:01
david-lyleoh they're aware, that's why they're not here now21:01
robcresswellI've not intention of bullying people into attending :)21:01
robcresswellhaha21:01
robcresswellthanks all21:01
robcresswell#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Thu Feb 16 21:01:46 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
lbragstadthanks!21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone_horizon/2017/keystone_horizon.2017-02-16-20.00.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone_horizon/2017/keystone_horizon.2017-02-16-20.00.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone_horizon/2017/keystone_horizon.2017-02-16-20.00.log.html21:01
david-lylethanks21:01
*** gagehugo has left #openstack-meeting-cp21:05
*** diablo_rojo_phon has joined #openstack-meeting-cp21:27
*** diablo_rojo has quit IRC21:31
*** ducttape_ has quit IRC21:42
*** ducttape_ has joined #openstack-meeting-cp21:50
*** ducttape_ has quit IRC22:03
*** ducttape_ has joined #openstack-meeting-cp22:10
*** bknudson has left #openstack-meeting-cp22:13
*** bknudson has joined #openstack-meeting-cp22:14
*** gouthamr has quit IRC22:15
*** diablo_rojo has joined #openstack-meeting-cp22:22
*** lamt has quit IRC22:47
*** lamt has joined #openstack-meeting-cp22:48
*** lamt has quit IRC22:50
*** lamt has joined #openstack-meeting-cp23:03
*** lamt has quit IRC23:30
*** diablo_rojo_phon has quit IRC23:40
*** jaugustine has quit IRC23:51

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