Thursday, 2016-12-01

*** ravelar has joined #openstack-meeting-cp00:04
*** tovin07_ has joined #openstack-meeting-cp00:52
*** ravelar has quit IRC01:05
*** zhurong has joined #openstack-meeting-cp01:11
*** piet_ has quit IRC01:12
*** topol has joined #openstack-meeting-cp02:47
*** topol has quit IRC03:11
*** Rockyg has quit IRC03:28
*** tovin07 has quit IRC03:31
*** tovin07 has joined #openstack-meeting-cp03:35
*** ravelar has joined #openstack-meeting-cp03:37
*** ravelar has quit IRC03:37
*** prateek has joined #openstack-meeting-cp03:55
*** jgriffith is now known as jgriffith_away04:28
*** jamespage has quit IRC05:00
*** jamespag` has joined #openstack-meeting-cp05:01
*** prateek_ has joined #openstack-meeting-cp05:11
*** prateek has quit IRC05:14
*** parora has joined #openstack-meeting-cp05:15
*** prateek_ has quit IRC05:17
*** gouthamr has joined #openstack-meeting-cp05:33
*** parora has quit IRC06:13
*** prateek has joined #openstack-meeting-cp06:13
*** zhurong__ has joined #openstack-meeting-cp07:07
*** zhurong has quit IRC07:10
*** mars has joined #openstack-meeting-cp07:20
*** rarcea_ has joined #openstack-meeting-cp07:53
*** ativelkov has quit IRC08:25
*** ativelkov has joined #openstack-meeting-cp08:25
*** MarkBaker has quit IRC08:26
*** beisner has quit IRC08:33
*** beisner has joined #openstack-meeting-cp08:35
*** prateek has quit IRC09:07
*** hogepodge has quit IRC09:11
*** hogepodge has joined #openstack-meeting-cp09:12
*** mars has quit IRC09:22
*** mars has joined #openstack-meeting-cp09:25
*** hogepodge has quit IRC09:31
*** hogepodge has joined #openstack-meeting-cp09:32
*** MarkBaker has joined #openstack-meeting-cp09:47
*** openstack has joined #openstack-meeting-cp10:04
*** ChanServ sets mode: +o openstack10:04
*** homerp_ has joined #openstack-meeting-cp10:31
*** sdague_ has joined #openstack-meeting-cp10:34
*** MarkBaker has quit IRC10:39
*** bswartz has quit IRC10:39
*** homerp has quit IRC10:39
*** luzC has quit IRC10:39
*** tonyb has quit IRC10:39
*** dansmith has quit IRC10:39
*** lbragstad has quit IRC10:39
*** MarkBaker has joined #openstack-meeting-cp10:43
*** bswartz has joined #openstack-meeting-cp10:43
*** luzC has joined #openstack-meeting-cp10:43
*** tonyb has joined #openstack-meeting-cp10:43
*** dansmith has joined #openstack-meeting-cp10:43
*** lbragstad has joined #openstack-meeting-cp10:43
*** MarkBaker has quit IRC10:47
*** gouthamr has quit IRC11:35
*** topol has joined #openstack-meeting-cp11:39
*** MarkBaker has joined #openstack-meeting-cp11:50
*** topol has quit IRC11:56
*** topol has joined #openstack-meeting-cp12:05
*** topol has quit IRC12:05
*** sdague_ is now known as sdague12:20
*** topol has joined #openstack-meeting-cp12:41
*** topol has quit IRC12:41
*** mars has quit IRC12:43
*** lamt has joined #openstack-meeting-cp13:34
*** lamt has quit IRC14:01
*** lamt has joined #openstack-meeting-cp14:07
*** gouthamr has joined #openstack-meeting-cp14:17
*** gouthamr_ has joined #openstack-meeting-cp14:22
*** jaugustine has quit IRC14:22
*** gouthamr has quit IRC14:22
*** jamespag` is now known as jamespage14:31
*** gouthamr has joined #openstack-meeting-cp14:34
*** gouthamr_ has quit IRC14:36
*** vkmc has left #openstack-meeting-cp15:07
*** stevemar has joined #openstack-meeting-cp15:12
*** edtubill has joined #openstack-meeting-cp15:20
*** stevemar_znc has joined #openstack-meeting-cp15:29
*** jgriffith_away is now known as jgriffith15:32
*** dims has quit IRC15:46
*** MarkBaker has quit IRC15:55
*** dims has joined #openstack-meeting-cp16:00
*** topol has joined #openstack-meeting-cp16:04
*** MarkBaker has joined #openstack-meeting-cp16:08
*** stevemar_znc is now known as topol_16:12
*** topol has quit IRC16:20
*** topol_ is now known as topol16:20
*** MarkBaker has quit IRC16:37
*** MarkBaker has joined #openstack-meeting-cp16:38
*** MarkBaker has quit IRC17:11
*** garloff has quit IRC17:39
*** piet has joined #openstack-meeting-cp17:40
*** rarcea_ has quit IRC18:07
*** xyang1 has joined #openstack-meeting-cp19:13
*** Rockyg has joined #openstack-meeting-cp19:26
*** Rocky_g has joined #openstack-meeting-cp19:27
*** david-lyle_ has joined #openstack-meeting-cp19:28
*** Rocky_g has quit IRC19:30
*** david-lyle has quit IRC19:31
*** bknudson has left #openstack-meeting-cp19:46
*** r1chardj0n3s has joined #openstack-meeting-cp19:53
r1chardj0n3sstevemar: would you like to chair the meeting today?19:53
stevemarr1chardj0n3s: sure thing19:53
stevemarr1chardj0n3s: oh wait19:53
stevemarr1chardj0n3s: i randomly have a phone call in 30 minutes (not regularly scheduled)19:54
r1chardj0n3sah dang :-)19:54
r1chardj0n3sI will work through my sleep haze and chair it :-)19:54
lbragstado/19:57
lbragstadr1chardj0n3s you're a trooper19:57
r1chardj0n3s\o/19:57
*** jamielennox has joined #openstack-meeting-cp19:57
crinkleo/19:58
stevemaro/19:58
edtubillo/19:59
stevemarif i could make a suggestion, we don't need to motor through all the topics. getting into the nitty gritty is fine :)20:00
r1chardj0n3s#startmeeting keystone_horizon20:00
openstackMeeting started Thu Dec  1 20:00:07 2016 UTC and is due to finish in 60 minutes.  The chair is r1chardj0n3s. 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
r1chardj0n3sstevemar: I'm always open to suggestions how to better run things!20:00
jamielennoxo/20:00
r1chardj0n3s#link https://etherpad.openstack.org/p/ocata-keystone-horizon is our current list of issues20:01
david-lyle_o/20:01
*** david-lyle_ is now known as david-lyle20:01
stevemarwhat are we starting with first? :)20:01
r1chardj0n3slooks like rderose has an update for Proper Domain-admin support20:02
r1chardj0n3s"still in WIP"20:02
rderoseo/20:02
stevemari think the initial bug goes beyond the limitations imposed by a federated user20:03
r1chardj0n3s(otherwise doesn't look like a lot of updates in the issues etherpad)20:03
rderoseyep, still in WIP, but once done, all federated users will belong to a real domain20:04
r1chardj0n3sso, who has a topic they'd like to discuss?20:04
stevemarr1chardj0n3s: we have edtubill and crinkle around, they're both working on bugs20:04
crinkleo/20:05
stevemarpick on one of them :P20:05
r1chardj0n3scrinkle, what're you working on?20:05
rderosealso, I'd like to quickly discuss PCI20:05
stevemarrderose: get in line!20:05
r1chardj0n3srderose: ack20:05
crinklehttps://review.openstack.org/#/c/389679/ and https://review.openstack.org/#/c/389337/ could use keystone and horizon eyes20:05
crinklei don't have an update beyond that20:06
*** ying_zuo has joined #openstack-meeting-cp20:06
stevemarcrinkle: so https://review.openstack.org/#/c/389679/ seems like an issue from when we moved to the bootstrap command?20:06
crinklestevemar: no, it's that different parts of the code were using a config setting as either an ID or a name20:07
stevemarcrinkle: hmm, yeah.. "OPENSTACK_KEYSTONE_DEFAULT_DOMAIN" isn't very clear is it20:07
stevemar"NOTE: This value must be the name of the default domain, NOT the ID"20:08
stevemarisn't that backwards incompatible?20:09
stevemarthis: https://review.openstack.org/#/c/389679/4/openstack_dashboard/local/local_settings.py.example20:09
stevemar?20:09
crinkleno because it was a bug, if you were using it the way it was documented it wasn't working20:09
david-lylestevemar: the comment was incorrect before20:10
knikollao/20:10
david-lylewe expect a name20:10
stevemarah okay20:10
david-lylebecause that's the only way the login form makes sense20:10
stevemardavid-lyle: so what's the hold up on getting this merged? :)20:10
stevemardavid-lyle: true20:10
david-lylecrappy reviewer20:10
* david-lyle points at self20:10
crinkle:)20:10
r1chardj0n3sthat patch hasn't hit the mandatory 69-day minimum delay for Horizon reviews yet :/20:10
stevemarr1chardj0n3s: team review in the meeting :P20:11
stevemarship it!20:11
r1chardj0n3s:-)20:11
lbragstadaaaand break!20:11
stevemar(i am only half joking)20:11
*** bknudson has joined #openstack-meeting-cp20:12
r1chardj0n3sstevemar: and I am intrigued by the idea!20:12
stevemarokay, crinkle also has https://review.openstack.org/#/c/389337/ up20:12
crinkleslightly more involved20:12
stevemarcrinkle: this was a bug you noticed when playing around with federation / sso?20:13
crinklestevemar: yes20:13
crinklethis could use someone from keystone saying "yep that's how that API works" or "no that's not how it's supposed to work at all"20:13
david-lylejust to reverify, the list_domains call will work with an unscoped token in the federation case?20:13
crinkledavid-lyle: yes, and only in the federation case20:14
stevemardavid-lyle: yes, that is correct i believe... http://developer.openstack.org/api-ref/identity/v3-ext/index.html?expanded=list-domains-a-federated-user-can-access-detail#list-domains-a-federated-user-can-access20:14
david-lyleand that's not guarded by policy?20:15
knikollasays deprecated20:16
jamielennoxthat one only works in the federation case, but we replaced it with a general purpose api a while ago20:16
rderosejamielennox: ++20:16
david-lylebut that one is guarded to "admin" only?20:16
david-lyleoh wait it's auth20:16
jamielennoxlisting /v3/auth/projects or /v3/auth/domains should tell you the projects/domains a user has access to, regardless of federated/regular login20:16
jamielennoxchecking on client equivalent...20:17
stevemarjamielennox: right, those are the new APIs /auth/project not the one i pointed out (old ones)20:17
jamielennoxv3.Client.auth.projects20:17
jamielennoxv3.client.auth.domains20:17
lbragstadyeah - i thought we deprecated the OS-FEDERATED apis a while ago20:17
crinklejamielennox: could you comment on the review and I'll fix it?20:17
stevemardavid-lyle: so why don't we check what domains a user has access to, in addition to projects?20:17
jamielennoxnot all, but we deprecated those20:17
david-lylewasn't accessible when I wrote the original implementation20:18
stevemari suppose we can put that as a follow-on if someone wanted it20:19
david-lylebut I'm not sure dumping into an arbitrary domain is ideal20:19
stevemarbut this is decently isolated20:19
lbragstadjamielennox ah - yes... specifically the apis for getting domains and projects for federated users20:19
stevemarcrinkle: commented20:20
crinklethanks20:20
stevemardavid-lyle: r1chardj0n3s y'all good with this once crinkle updates?20:20
crinkledavid-lyle | but I'm not sure dumping into an arbitrary domain is ideal20:21
r1chardj0n3scrinkle: also, as a matter of procedure, could you please link those to a bug to aid our tracking backports?20:21
stevemarr1chardj0n3s: ++20:21
crinkler1chardj0n3s: okay20:21
r1chardj0n3sthanks20:21
david-lylein the federation case, will there be more than 1 domain?20:21
stevemardavid-lyle: possible?20:22
rderosedavid-lyle: federated users will belong to only a single domain20:22
rderosedifferent domain, different user20:22
david-lylebecause we're shadowing the users?20:23
stevemarrderose: belong to != have access to20:23
david-lylehorizon doesn't have a switch to change domains20:23
stevemaroh no?20:23
stevemarthats a bummer20:24
stevemaris/was there a reason why?20:24
david-lyleso if we dump into the first of possibly many then they can never get to the other20:24
rderosedavid-lyle: yeah, because we're shadowing federated users, they are like any other keystone user and will have to belong to a single domain.20:24
david-lyleuntil your newer API domain list was guarded to be "admin" only by the policy file20:24
david-lyleso there was no point adding it20:25
stevemari see what you mean20:25
david-lylethis all went into the Havana release, btw20:25
david-lyleso it has some gray hair now20:25
stevemarmight be worth adding it since we have /auth/domains now20:25
stevemaranywho, getting off topic for this specific change/bug20:25
r1chardj0n3sgood discussion tho, I think :-)20:25
stevemaryep20:26
david-lyleright, the method to switch would go into doa, but the actual user interface would be in Horizon20:26
stevemaredtubill: still around?20:26
edtubillstevemar: yeah20:26
edtubillI can talk about k2k federation for horizon: david-lyle approved the new k2k dropdown blueprint. I am currently writing some patches, I'll push them out for review soon.20:26
stevemardammit, stupid call starting soon20:26
david-lylestevemar, I'm not sure it's off topic20:26
david-lylebecause the unnavigable domain issue above, based on the current patch20:26
crinkleis it worth the effort to make domains navigable or is it usually expected that all users have projects and this doesn't need to be fixed?20:27
david-lylesomething is better than nothing I suppose, but adding the switch method to forms.py would be a good piece for this patch as well20:27
stevemardavid-lyle: okay, maybe crinkle's assumption that a federation setup result in a domain admin isn't a good one?20:28
crinkledavid-lyle: okay i can work on that20:28
stevemardavid-lyle: so it'll be like the project switcher?20:28
david-lylestevemar: yes20:28
stevemarthanks for volunteering to do the work crinkle20:28
crinkleofc20:28
david-lylethen once it's merged in doa and released we can put a user control in horizon20:29
stevemardavid-lyle crinkle okay, let's let crinkle tinker around for now, she can come back with an update next week?20:29
david-lylesounds good20:29
stevemara domain switcher would be all kinds of useful, i think20:29
david-lyleyes, didn't realize we had gained access to the list for the user20:30
stevemarhas to dial into a call, will be half paying attention :(20:30
r1chardj0n3sso edtubill, any issues or will we await the patches?20:30
stevemaroh wait, meeting at 4!20:30
stevemaryay!20:30
r1chardj0n3s\o/ stevemar20:30
stevemar\o/20:30
stevemardavid-lyle: edtubill: so what was actually decided?20:31
edtubillNo issues so far20:31
r1chardj0n3s#link https://blueprints.launchpad.net/horizon/+spec/k2k-horizon this blueprint20:31
edtubillAnd also I will make the 'K2K at login time' work with the new blueprint as well.20:32
stevemaredtubill: so it'll be a drop down next to projects (and the new domains drop down ;)) ?20:32
david-lyleedtubill: make that a separate bp20:32
david-lylestevemar: that's the current bp yes20:33
stevemardavid-lyle: cool20:33
edtubilldavid-lyle: ok I'll make that a seperate bp for 'k2k at login time'20:33
stevemardavid-lyle: how is the list of SPs selected?20:33
stevemaredtubill: ^20:33
edtubillIt's taken from the access info object for a scoped token.20:33
david-lylefor the current bp, or the latter20:33
stevemardavid-lyle: i guess on login time it's a set of config options? and once logged in, from the token?20:34
david-lylethe latter will require another hardcoded list unless keystone has an open call to obtain it, or we go to a two step login process, which I'm not excited about20:34
*** MarkBaker has joined #openstack-meeting-cp20:35
edtubillstevemar: So the user logs in and gets to see the list of available sps in a dropdown. The blueprint is different from the 'k2k at login time'. It gets it dynamically from the token and not the config file.20:35
stevemarso it sounds like both are on the table right now?20:35
stevemaris there a reason we are not deciding one over the other?20:35
stevemaror is it -- we can do both, so why not?20:36
david-lylehardcoded lists are bad20:36
stevemar(sorry for all the questions, i think i've missed a few meetings :( )20:36
david-lyleand my thoughts were the selector once logged in was cleaner and useful, but did not bar the login case20:36
david-lyleI'm not excited about how we have to do the login case at this point20:37
stevemardavid-lyle: okay, sounds like since both can happily co-exist, we let them co-exist?20:38
edtubillI am for having them co-exist incase someone wants them both.20:38
edtubillBut prioritize the drop down blueprint more.20:38
david-lyleI think so, but I'm open to other opinions20:38
stevemari'm trying to get a firm decision on what will be accepted by the team, so we don't make edtubill go back and forth20:39
stevemar:)20:39
stevemarand if the decision is 'meh', that's cool too!20:39
stevemar(we can move to another topic, i think i beat this horse to death)20:39
r1chardj0n3sI'm deferring to people who know more about what's going on (hi, david-lyle)20:39
stevemarhehe20:40
stevemardavid-lyle, pressure's on20:40
r1chardj0n3sso, rderose, about about that PCI?20:40
david-lyleI would think if you had other keystones that were cost inducing, you could use the current endpoint list on login page and let the user choose20:40
rderoseI've added a patch to support "PCI-DSS 8.2.6 Set passwords/passphrases for first-time use and upon reset to a unique value for each user, and change immediately after the first use"20:40
rderosehttps://review.openstack.org/#/c/403916/20:40
rderoseSo after first auth, the user's password will be set to expire and they will be required to change their password.20:40
rderose1) horizon gets token for user (first time after password reset)20:40
rderose2) horizon will inpsect the 'password_expires_at' attribute in the token20:40
rderose2a) if expired, show password dialog for user to change their password20:40
rderosesound good?20:41
stevemarlookin'20:41
rderosequestions?20:41
r1chardj0n3ssounds good to me. we have some expiry interface work in progress, just not sure if we have the step 2) stuff covered yet20:42
*** openstack has joined #openstack-meeting-cp20:44
*** ChanServ sets mode: +o openstack20:44
david-lyleit could20:44
stevemargrey out / disable the rest of the pages, force the user to change password20:44
r1chardj0n3srderose: can I confirm that the password_expires_at will be in the past for *all* tokens not just the "first time after password reset"?20:44
r1chardj0n3suntil the password is changed, that is20:44
rderoseyes, it will be in all tokens20:44
stevemara password change should revoke all old tokens20:45
r1chardj0n3sstevemar: hmm, disabling all other things is more challenging20:45
r1chardj0n3srderose: ok cool20:45
stevemarr1chardj0n3s: whatever the UX is, i assume you guys can handle that, i'm just talking a loud20:45
david-lyler1chardj0n3s: could add a new page on a splash20:45
r1chardj0n3sdavid-lyle: yeah20:45
david-lyleand redirect to that20:45
stevemarrderose: who's doing the horizon work?20:45
rderosestevemar: Juan Pablo lopez Gutierrez20:46
rderosehttps://review.openstack.org/#/q/owner:juan.pablo.lopez.gutierrez%2540intel.com+status:open20:46
stevemarrderose: cool irc name20:46
stevemaryou should tell him to come to our super cool meeting20:46
rderosestevemar: will do, forgot his IRC nic20:46
david-lyleour authenticated decorator may have to get an upgrad20:46
stevemaris there a patch already up?20:46
david-lylee20:46
rderosestevemar: not for requiring a user to change their password after reset20:47
rderoseno20:47
david-lylestevemar: only for similar work, not this work specifically20:47
stevemarcool20:47
r1chardj0n3sI've pinged JP to join us20:47
stevemari'll be patient20:47
rderoseRegarding making the password strength requirements discoverable, are we thinking an API call?  Currently, it's in Keystone config.20:47
stevemarthat'll be tough20:48
stevemarmight just be better to keep the horizon setting20:48
r1chardj0n3shmm, duplicated settings make david-lyle sad20:48
r1chardj0n3sand you don't want his sad face20:48
rderosestevemar: but this is needed outside of Horizon, right?20:49
david-lyleOSC anyone?20:49
stevemardavid-lyle: what's that? <sarcasm>20:49
david-lyleI guess you just let them fail in OSC20:49
stevemarthat's what we've been doing :D20:50
rderose:)20:50
david-lyledo they get any hints as to what magical rules they're attempting to satisfy?20:50
stevemarokay, keystoners, any ideas on how to expose the password regex config and what policy it should have?20:50
stevemardavid-lyle: they sure do20:51
david-lyleok20:51
stevemarhttps://github.com/openstack/keystone/blob/master/keystone/conf/security_compliance.py#L124-L13120:51
lbragstadby expose it you mean just advertise it?20:51
stevemarconfigurable message20:51
stevemarlbragstad: yeah20:51
r1chardj0n3soh, yes, please expose password_regex_description!20:51
lbragstadyeah - the description is the import thing to expose20:52
lbragstadi wouldn't think exposing the regex through horizon would be all that useful20:52
david-lylelbragstad: it saves trips and failures to the server20:52
r1chardj0n3swe could do real-time feedback for the user, but ueah, that's icing20:52
rderoselbragstad: how would we expose it?20:52
stevemarso we have "config" related stuff already in the API for ldap stuff: https://github.com/openstack/keystone/blob/master/etc/policy.v3cloudsample.json#L22420:52
stevemarlbragstad: the regex is also important to expose!20:52
lbragstaddavid-lyle oh - meaning horizon would check the password against the regex before sending it to keystone?20:53
stevemarfrom an OSC point of view too!20:53
stevemarlbragstad: currently we just pass whatever crap the user inputs20:53
david-lylelbragstad: yeah, like UIs you like, rather than the ones you hate ;-)20:53
lbragstadah20:53
lbragstadthat's a good point20:53
david-lylewe check it currently20:53
david-lylebut we have a setting that predates keystone's20:54
stevemari just wondered what the harm is in an API call to show the entire config -- lol20:54
stevemaronly about a bunch of passwords20:54
david-lyleno risk there20:54
* stevemar needs coffee20:54
lbragstad+220:54
stevemardavid-lyle: trouble with showing the option for passwords is, what policy do we surround it with?20:55
stevemarjust "", so any authenticated user?20:55
david-lyleI would assume so20:55
stevemarwe only show the [security_compliance] section20:55
lbragstadwhy no just the regex and regex description?20:55
lbragstadnot*20:55
david-lylethat's the ask20:55
stevemarlbragstad: could limit it to that20:56
stevemarGET /v3/users ...20:56
stevemarGET /v3/compliance ?20:56
lbragstadwe have a password api for password changes... maybe the path makes sense there?20:56
rderoselbragstad: that might work20:56
stevemarprobably /v3/users/compliance20:56
stevemarlbragstad: rderose one of you want to pick it up?20:57
lbragstadsince it'd be the api that users go to when they want to reset their password, they could use it to ask for the requirement they need to meet20:57
stevemarit would need a spec :(20:57
lbragstadah20:57
lbragstadi can tackle the spec20:57
rderosestevemar: I can take it20:57
rderose:)20:57
*** jlopezgu has joined #openstack-meeting-cp20:57
stevemaryou two work it out :P20:57
rderoselbragstad: go for it20:57
r1chardj0n3sthanks rderose20:57
r1chardj0n3sok, and we're pretty much out of time20:58
lbragstadi'll get a spec up20:58
r1chardj0n3ssay hi to jlopezgu tho ;-)20:58
stevemarr1chardj0n3s: yeppers20:58
jlopezguo/20:58
jlopezguhahah20:58
jlopezguwere you talking about me? xD20:58
stevemarr1chardj0n3s: next week i want to talk about the "v3 policy is not parseable using oslo.policy" bug20:58
stevemarthat thing is a mess20:58
r1chardj0n3sstevemar: oh, let's! :-)20:58
david-lyleI'll bring the matches20:58
* stevemar goes to that call20:59
r1chardj0n3sthanks everyone!20:59
r1chardj0n3s#endmeeting20:59
crinkleo/20:59
r1chardj0n3shello, bot?20:59
r1chardj0n3s*tap tap*20:59
r1chardj0n3s#endmeeting21:00
r1chardj0n3sdarn it21:00
david-lylebot died and reappeared in the middle21:01
fungioh, i wonder if someone merged a change to its configuration in the middle of a meeting, checking21:02
r1chardj0n3sah, so half the meeting won't have been recorded?21:02
fungiwe normally try to avoid that when there are meetings underway, but someone might have failed to check before approving a change21:02
r1chardj0n3s:-( ah well21:03
fungiin which case, yeah, you can refer to the channel log for this channel and i can optionally try to splice some of it into the meeting log21:03
r1chardj0n3sI think we'll be right just referring to the channel log, thanks21:04
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:07
*** ying_zuo has quit IRC21:17
*** MarkBaker has quit IRC21:47
*** garloff has joined #openstack-meeting-cp22:00
*** gouthamr has quit IRC22:17
*** MarkBaker has joined #openstack-meeting-cp22:17
*** MarkBaker has quit IRC22:39
*** edtubill has quit IRC22:52
*** edtubill has joined #openstack-meeting-cp22:53
*** edtubill has quit IRC22:58
*** xyang1 has quit IRC23:12
*** piet has quit IRC23:38

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