Thursday, 2015-07-23

*** gyee has quit IRC00:33
*** chlong has quit IRC00:52
*** everjeje has quit IRC01:18
*** crc32 has joined #openstack-barbican01:27
*** shangxdy has joined #openstack-barbican01:58
*** dave-mccowan has quit IRC02:00
*** kebray has joined #openstack-barbican02:00
*** vivek-ebay has quit IRC02:01
*** kebray has quit IRC02:02
*** chlong has joined #openstack-barbican02:11
*** mikeymeitbual has quit IRC02:11
*** yuanying has joined #openstack-barbican02:49
*** tkelsey has joined #openstack-barbican02:52
*** tkelsey has quit IRC02:56
*** vivek-ebay has joined #openstack-barbican02:57
*** kebray has joined #openstack-barbican03:02
*** shangxdy has quit IRC03:16
*** dave-mccowan has joined #openstack-barbican03:22
*** vivek-ebay has quit IRC03:24
*** vivek-ebay has joined #openstack-barbican03:24
*** yuanying has quit IRC03:26
openstackgerritOpenStack Proposal Bot proposed openstack/barbican: Updated from global requirements  https://review.openstack.org/20429603:28
*** yuanying has joined #openstack-barbican03:28
*** edtubill has joined #openstack-barbican03:43
*** edtubill has left #openstack-barbican03:43
*** xaeth_afk is now known as xaeth03:44
*** dave-mccowan has quit IRC03:46
*** yuanying has quit IRC03:49
*** yuanying has joined #openstack-barbican03:59
*** yuanying has quit IRC04:02
*** xaeth is now known as xaeth_afk04:32
openstackgerritOpenStack Proposal Bot proposed openstack/barbican: Updated from global requirements  https://review.openstack.org/20429604:37
*** zz_dimtruck is now known as dimtruck04:39
*** yuanying has joined #openstack-barbican05:01
*** rm_work|away is now known as rm_work05:01
*** dimtruck is now known as zz_dimtruck05:12
*** vivek-eb_ has joined #openstack-barbican05:23
*** vivek-ebay has quit IRC05:26
*** vivek-eb_ has quit IRC05:42
*** crc32 has quit IRC06:00
*** Nirupama has joined #openstack-barbican06:03
*** shohel has joined #openstack-barbican06:09
*** nickrmc83 has joined #openstack-barbican06:13
openstackgerritOpenStack Proposal Bot proposed openstack/barbican: Imported Translations from Transifex  https://review.openstack.org/20491706:14
*** woodster_ has quit IRC06:22
*** madhuri has left #openstack-barbican06:25
*** vivek-ebay has joined #openstack-barbican06:43
*** vivek-ebay has quit IRC06:47
*** chlong has quit IRC06:49
*** tkelsey has joined #openstack-barbican06:53
*** tkelsey has quit IRC06:58
*** tkelsey has joined #openstack-barbican08:27
*** everjeje has joined #openstack-barbican08:32
*** shohel has quit IRC10:02
*** mmdurrant has quit IRC10:09
*** chlong has joined #openstack-barbican11:08
*** jaosorior has joined #openstack-barbican11:53
*** dave-mccowan has joined #openstack-barbican11:56
*** mmdurrant has joined #openstack-barbican11:58
jaosoriorwould really use a workflow for this CR https://review.openstack.org/#/c/199142/ :D12:05
*** zz_dimtruck is now known as dimtruck12:26
*** alee has quit IRC12:35
*** Nirupama has quit IRC13:01
openstackgerritJuan Antonio Osorio Robles proposed openstack/barbican: Add invalid property info to validation error message  https://review.openstack.org/20505713:22
jaosoriorhockeynut: Thanks for the workflow dude :D13:24
hockeynutanytime!13:24
hockeynutwill you be at midcycle?13:25
jaosoriorhow's it gonig over there?13:25
jaosoriorNot this time :/13:25
hockeynutsadness...13:25
hockeynutwe will go out and find some Finnish liqueur in your honor!13:25
jaosoriorWell, seems people's livers will not be in danger this mid-cycle :P13:26
hockeynutRackspace medical plan thanks you! :-)13:26
jaosoriordamn13:29
jaosoriorseems that the changes in mock actually affect the stable/kilo branch13:29
jaosoriorcherry-picking the fix13:32
*** alee has joined #openstack-barbican13:34
jaosorioralee: ping13:36
aleejaosorior, pong13:37
aleejaosorior, I had some questions for you too ..13:37
jaosorioralee: The packporting of the dogtag commits is on-going starting with this commit: https://review.openstack.org/#/c/205059/13:37
jaosoriorstay put for the gate results :D13:37
jaosoriorwhat's up?13:37
aleejaosorior, just a sec ..13:38
aleejaosorior, trying to set up my machine again - but I'm testing a certmonger helper script that talks to barbican13:42
*** darrenmoffat has quit IRC13:42
*** darrenmoffat has joined #openstack-barbican13:42
aleejaosorior, I need some help in setting up the data needed in keystone to do some real tests13:42
jaosorioralee: Sure man, what kind of setup do you want?13:42
aleejaosorior, give me a few mins to finish something up and set things up again - and I'll show you what I have.13:43
jaosoriorsure#13:43
*** rellerreller has joined #openstack-barbican13:44
jaosoriorhockeynut: By the way, do you have time to check this CR out? https://review.openstack.org/#/c/198732/13:47
hockeynut<click>13:47
jaosoriorredrobot^^13:47
openstackgerritMerged openstack/barbican: Add Private Key to the resulting container if stored-key order  https://review.openstack.org/19914213:48
jaosorioryay13:49
*** spotz_zzz is now known as spotz13:51
*** woodster_ has joined #openstack-barbican13:55
hockeynutjaosorior the cli change makes me nervous because of the "secret container" and "secret order".  I see the reasoning from the comments but I can see people confused between "container" which is well known across the codebase, and "secret container" which is just here13:55
jaosoriorhockeynut: well, we can discuss of an alternative. Problem is, there is already a "container create" in the openstack CLI13:58
jaosoriorso... that's taken13:58
hockeynutyup.  its a sticky wicket13:58
jaosoriorhockeynut: http://pastebin.com/RcDbCunr13:59
hockeynut"container" is yet another overloaded term and its not getting any better14:00
jaosoriorin the python-barbicanclient's CLI container and order make sense, since that assumes already that the terms are exclusive to barbican14:00
hockeynutexactly14:00
jaosoriorproblem is when in the context of the openstack CLI. Then we don't have that assumption14:00
jaosoriorother option would be14:00
jaosorior"barbican container"14:00
hockeynutI prefer secret to barbican14:01
rm_workI prefer barbican to secret14:01
rm_workbut that'd be assuming you just prefix EVERYTHING with barbican14:01
rm_workwhich makes sense to me...14:02
rm_work`osc barbican container create [...]`14:02
aleejaosorior, so this is the script I've been working with .. http://paste.openstack.org/show/404026/14:02
jaosoriorrm_work: That's a possibility14:02
rm_workis what i assumed it would be like14:02
hockeynutare there other OS components with their own containers that have this same issue?14:02
rm_workjumbling every project's objects into a toplevel namespace seems funky14:02
rm_workis there not already a plan to do project prefixes for EVERYTHING?14:03
aleejaosorior, now when I run certmonger, this script is executed , but it fails because of ..14:03
aleeThe server could not comply with the request since it is either malformed or otherwise incorrect.<br /><br />14:03
aleeMissing X-Project-Id14:03
jaosoriorrm_work: Not sure about that. Only project that has something similar is ironic, and they prefix everything with baremetal. But that actually makes more sense in their case14:04
aleejaosorior, which means that my keystone server needs to have some projects etc. defined.14:04
jaosorioralee: you need to change your barbican-api-paste.ini to use the keystone middleware14:04
rm_workjaosorior: so how does nova work in osc? is it *not* `osc nova server create` or `osc nova boot`?14:04
jaosoriorrm_work: no14:04
rm_worki haven't been following it14:04
aleejaosorior, ah yes ..14:04
* rm_work tries to look up example docs14:05
rm_workuhh also, heads up, i'll be bringing up Castellan-certs again14:05
jaosoriorrm_work: These are the available commands: http://pastebin.com/etZrLmC814:05
rm_workhave yet another project looking at using that interface14:05
rm_workjaosorior: ok, this is kinda dumb14:06
rm_worksomeone didn't think this through14:06
rm_workyou can't just dump every project's commands into one top level domain and just hope it makes sense14:07
hockeynutkeymgr perhaps?14:07
jaosoriorrm_work, hockeynut: Another thing is that there is no reference to barbican itself in OSC. They rather use the full project name. In our case, key manager14:07
rm_workbecause now if barbican does it properly and prefixes with our project name, we'll be yet another "different syntax"14:07
rm_workerg14:08
rm_worki mean, same diff14:08
*** pglass has joined #openstack-barbican14:08
rm_workthe point is that the syntax `osc <projectprefix> <category> <action>`14:08
jaosoriorthe problem I see there is that "key manager order create" or "keymgr order create" will be kind of confusing if you start doing stuff related to certificate workflows14:08
rm_workwould be different from the currently established `osc <category> <command>`14:08
aleejaosorior, yup - that did it -- now talking to barbican -- thanks14:08
rm_workwhich means things would be diverging again14:09
jaosoriorthat's why I thought prefixing with secret would be more appropriate14:09
jaosoriorverbose, but still not breaking off from what's already there14:09
rm_workbut that isn't even the point14:09
jaosorioralee: No problem. If you need any more help with your keystone setup let me know14:09
rm_workprefixing *at all* breaks from their current model14:09
rm_workso we'd be different again14:09
rm_workbecause no one else does that14:10
jaosoriorrm_work: "secret order" made sense for me, because even though it is verbose, it is actually an order for a "secret". In a way14:10
rm_workjaosorior: yes, but `osc secret order [get | create]`14:10
jaosoriorrm_work: We could ask stevemar if he has any recommendation there14:11
rm_workjaosorior: yes, but `osc secret secret [get | create | delete]`14:11
rm_workwhat is that even14:11
jaosorioractually, I do not prepend anything for secret14:11
rm_workah errrrr14:11
jaosorioras you may see in that CR14:11
rm_workso like half of the commands prepend and half don't?14:11
jaosoriorrm_work: https://review.openstack.org/#/c/198732/14:11
rm_workit's not even consistent across our own project? T_T14:11
jaosoriorrm_work https://review.openstack.org/#/c/198732/9/setup.cfg14:12
rm_worklooking14:12
rm_workright so14:12
rm_workeven *within the project* the syntax is inconsistent14:12
rm_workto me14:12
jaosoriorrm_work: More than a "prefix" I'm actually trying to think of it as a sole object14:13
rm_worksince there's a switch between two levels and three14:13
jaosoriorso a "secret order" is a thing, while a "secret container" is another thing, and a "secret" is an object by itself14:13
rm_work`osc secret <action | category> [action | ref] [ref?]`14:13
jaosoriormaybe a more appropriate thing to reflect that would be to have something such as "secret-order"14:14
rm_workyeah14:14
rm_worki suppose if you pretend it has a hyphen it makes a little bit more sense14:14
jaosoriorI could try to change that CR to add a hyphen there14:15
rm_workthen are we the only project using hyphens?14:15
rm_worklooks like yes14:15
jaosoriorwe would be, yes14:15
jaosoriorbut I think that will be needed at some point by another project14:15
jaosoriorthat list is only showing the projects that are actually in the openstack CLI's codebase14:15
jaosoriorI don't have any of the extensions14:15
rm_workk14:16
rm_workit just seems to indicate a lack of forethought to me14:16
jaosoriorwe could of course ask stevemar if he has an opinion about that14:16
rm_workif i were designing osc i would have automatically put each project in a namespace14:16
rm_workthen there would be zero consistency issues14:16
rm_workand no chance of naming conflicts14:16
jaosoriorrm_work: Should we take this up in the openstack-sdks chatroom?14:16
rm_workit might be a little late <_<14:16
rm_workhow much is OSC being used presently?14:17
jaosoriorkeystone has adopted it fully14:17
rm_workis it still experimental as of liberty?14:17
jaosoriorso you're not supposed to use the python-keystoneclient if you intend to use keystone v314:17
rm_workhmm14:17
jaosorioralso projects like congress rely on it fully14:17
rm_workugh14:17
rm_workthis design really irks me, but with all the shit i'm doing right now it is taking a herculean effort to muster enough caring to actually do anything14:18
rm_worki guess it can't hurt to bring it up though14:19
rm_worki am willing to bet $1 that they already had a discussion about namespacing when they first started out14:19
rm_workand someone said "i'm sure it'll be fine" >_>14:19
*** Kevin_Bishop has joined #openstack-barbican14:20
jaosoriorrm_work: In the mean time14:21
jaosoriordo you consider adding a hyphen there as an appropriate solution given what's already there?14:21
rm_worki guess that works to get it started, but you also must realize that whatever lands first is going to be very sticky14:22
rm_workso fixing this later will be rough14:22
jaosoriorwhich is why there is a CR up there and we should be discussing the best solution. Like now14:22
rm_worktrying to decide if i really think having our top-level object list as [secret secret-container secret-order] is better14:22
rm_workanyone else have an opinion?14:24
jaosoriorI think I'm more into that approach than having it the way I proposed initially14:24
rm_workhockeynut / alee / redrobot14:24
jaosoriorkind of removes some of the ambiguity14:24
*** kfarr has joined #openstack-barbican14:24
rm_workyeah i think i do prefer that, but only slightly14:24
rm_workthe real fix would be to fix all of osc to properly prefix, but i feel like that's not going to happen14:25
hockeynut^ winner14:25
openstackgerritJuan Antonio Osorio Robles proposed openstack/python-barbicanclient: Create Openstack CLI plugin for Barbican  https://review.openstack.org/19873214:25
jaosoriorrm_work: Lets drop by the #openstack-sdks channel and ask14:25
rm_workyeah14:26
rm_worki joined14:26
openstackgerritKaitlin Farr proposed openstack/castellan: Add functional tests for Barbican key manager wrapper  https://review.openstack.org/19923414:27
*** rellerreller has quit IRC14:30
aleetherve, jaosorior -- hey - can you remind me ?  how do I do a certificate order using barbican client cli?14:30
*** briancurtin has quit IRC14:31
thervealee, Let's see14:31
*** briancurtin has joined #openstack-barbican14:31
thervebarbican order create --type certificate ... ?14:32
aleetherve, yeah .. thanks -- trying it out14:37
*** kebray has quit IRC14:37
*** dave-mccowan has quit IRC14:39
*** xaeth_afk is now known as xaeth14:54
*** dave-mccowan has joined #openstack-barbican14:55
*** kebray has joined #openstack-barbican15:02
*** kebray has quit IRC15:03
*** kebray has joined #openstack-barbican15:03
*** edtubill has joined #openstack-barbican15:13
openstackgerritJuan Antonio Osorio Robles proposed openstack/python-barbicanclient: Create Openstack CLI plugin for Barbican  https://review.openstack.org/19873215:14
jaosoriorrm_work: Got some minutes? need help figuring out why this CR is failing https://review.openstack.org/#/c/205059/  :/15:17
*** david-lyle has joined #openstack-barbican15:17
*** diazjf has joined #openstack-barbican15:20
*** vivek-ebay has joined #openstack-barbican15:20
dave-mccowanjaosorior try it without the change to setup.py.  i think pbr>=1.3 won't work in kilo branch due to compatibility with other packages.15:21
rm_workjaosorior: momentarily15:23
*** rellerreller has joined #openstack-barbican15:23
jaosoriordave-mccowan: Lets try that15:23
*** vivek-ebay has quit IRC15:24
*** crc32 has joined #openstack-barbican15:25
*** arunkant_ has joined #openstack-barbican15:25
*** vivek-ebay has joined #openstack-barbican15:34
*** cbader has joined #openstack-barbican15:36
*** silos has joined #openstack-barbican15:39
*** nkinder has joined #openstack-barbican15:49
openstackgerritJuan Antonio Osorio Robles proposed openstack/python-barbicanclient: Create Openstack CLI plugin for Barbican  https://review.openstack.org/19873215:54
*** vivek-ebay has quit IRC15:56
*** nickrmc83 has quit IRC16:01
*** codekobe has quit IRC16:14
*** codekobe has joined #openstack-barbican16:15
*** dimtruck is now known as zz_dimtruck16:21
aleejaosorior, are there any acceptance/functional tests for the python-barbicanclient?16:33
aleejaosorior, I have a helper script (python file) that links certmonger to barbican using the barbican client code -- I think it makes sense for this code to live in the barbican-client tree.  thoughts?16:35
rm_workalee: i feel like you should link certmonger to barbican via castellan :P16:40
* rm_work is only partially trolling16:41
aleerm_work, ha! no comment16:41
aleerm_work, we'd need castellan-certs for that .. and yes, you can argue for that at the midcycle.16:42
jaosorioralee: Yep, there are functional tests16:43
jaosoriorperhaps you could put that in a "contrib" folder?16:43
rm_workwill be trying :)16:43
aleejaosorior, tox -e functional  ?16:44
jaosorioralee: yup16:44
aleeor run_tests.sh  ?16:44
jaosorioralee: you need to tweak the etc/functional_tests.conf16:44
jaosoriorbut use the tox one16:44
aleejaosorior, ah -- looking16:45
jaosoriornot sure if run_tests.sh actually works... haven't ran it in a long time16:45
aleejaosorior, cool - so you good with certmonger script being in the python-barbicanclient tree?16:46
jaosoriorI am16:47
jaosoriorthat would actually be pretty convenient, since if there's changes in the python-barbicanclient interface, that could easily traced and reflected in the certmonger script16:48
jaosorioronly thing I'm not sure about is actually testing that script16:48
aleejaosorior, we could put it in some kind of contrib folder -- I was just going to put it in barbicanclient/certmonger16:48
jaosorioralee: I'm more for the contrib folder16:49
aleejaosorior, yeah - well thats why I asked about functional tests16:49
jaosoriorcontrib/certmonger would be appropriate16:49
aleesure I can do that16:49
aleejaosorior, not sure how to test it as part of a gate job .. do we have those?16:50
jaosoriorthe functional tests are running as a gate job, yeah16:50
jaosoriorbut I guess for certmonger, a separate gatejob would be appropriate. Such as we have with dogtag16:51
aleejaosorior, yup16:51
aleejaosorior, although certmonger is widely available - so it could be possible to have it as part of the regular gate job16:52
jaosoriorhttp://www.daedtech.com/wp-content/uploads/2012/12/TestAllTheThings.jpg16:52
aleejaosorior, though maybe separately at first16:52
openstackgerritFernando Diaz proposed openstack/python-barbicanclient: Allow Barbican Client Secret Update Functionality  https://review.openstack.org/19687616:52
aleejaosorior, cool thanks16:53
jaosorioralee: If it's in ubuntu, and not much needs to be configured, I don't see why we can't add it to the standard gate16:53
aleejaosorior, it is - but I'm going to need to add something to certmonger, so we'll need a specific certmonger version16:54
aleejaosorior, specifically, I'm going to need to add ca_id16:55
aleejaosorior, we can start as a separate gate and then merge in when we can.16:55
jaosorioralee: fair enough16:55
aleejaosorior, is there a way yet in the client to get the /cas interface?16:56
aleeI think the answer is no .. guess I need to write it ..16:56
jaosorioralee: I think that should have been part of the implementation of the blueprint. If that's missing then we all messed up since I think that blueprint was marked as complete16:57
rm_worki think in general the client has a tendency to get neglected T_T16:58
jaosoriorrm_work: It hurts :(16:58
rm_workACLs in the client yet?16:58
jaosoriorI don't think so16:59
rm_workT_T16:59
*** alee is now known as alee_lunch16:59
jaosorioris the blueprint marked as completed?16:59
jaosoriorbecause if the client doesn't support ACLs then it shouldn't be marked as such16:59
jaosorioranyway, gonna go fetch a beer and dinner. I MIGHT be back haha17:00
*** kfarr1 has joined #openstack-barbican17:04
*** kfarr has quit IRC17:05
*** jraim has quit IRC17:07
*** jraim has joined #openstack-barbican17:08
*** kfarr1 has quit IRC17:08
jkfchellygel: ping17:19
*** kfarr has joined #openstack-barbican17:23
openstackgerritFernando Diaz proposed openstack/python-barbicanclient: DO NOT REVIEW  https://review.openstack.org/20519117:32
*** rellerreller has quit IRC17:33
openstackgerritFernando Diaz proposed openstack/python-barbicanclient: Allow Barbican Client Secret Update Functionality  https://review.openstack.org/19687617:36
*** dolphm has left #openstack-barbican17:42
*** zz_dimtruck is now known as dimtruck17:48
openstackgerritFernando Diaz proposed openstack/python-barbicanclient: DO NOT REVIEW  https://review.openstack.org/20519117:52
*** tkelsey has quit IRC18:11
jkfWhere can I find the API docs for the cert management API? It doesn't appear that the wiki docs have been updated and I'm trying to get one of our CA Devs up to speed so he can work on writing the Symantec CA plugin.18:15
jkfOf course, right after I ask, I see a link I've been missing for the past day or so. :)18:16
*** silos has left #openstack-barbican18:19
*** kebray has quit IRC18:28
*** kebray has joined #openstack-barbican18:29
*** vivek-ebay has joined #openstack-barbican18:34
*** vivek-ebay has quit IRC18:34
*** vivek-ebay has joined #openstack-barbican18:35
*** SheenaG has quit IRC18:40
*** cbader has quit IRC18:44
*** kfarr has quit IRC18:47
*** kfarr has joined #openstack-barbican18:50
*** bitblt has joined #openstack-barbican18:55
*** vivek-ebay has quit IRC18:57
*** bitblt has quit IRC18:58
*** SheenaG has joined #openstack-barbican19:00
*** jaosorior has quit IRC19:06
*** diazjf has quit IRC19:11
*** alee_lunch is now known as alee19:12
*** kebray has quit IRC19:24
*** kebray has joined #openstack-barbican19:26
*** kebray has quit IRC19:28
*** kebray has joined #openstack-barbican19:33
*** kfarr has quit IRC19:34
*** kebray has quit IRC19:34
*** kfarr has joined #openstack-barbican19:37
*** kebray has joined #openstack-barbican19:41
*** crc32 has quit IRC19:45
*** diazjf has joined #openstack-barbican19:54
*** hockeynut_afk has joined #openstack-barbican19:55
*** dimtruck is now known as zz_dimtruck19:57
*** kebray has quit IRC19:57
*** alee is now known as alee_afk20:10
*** kebray has joined #openstack-barbican20:14
*** kebray has quit IRC20:14
*** alee_afk has quit IRC20:14
*** kebray has joined #openstack-barbican20:15
*** crc32 has joined #openstack-barbican20:17
openstackgerritFernando Diaz proposed openstack/python-barbicanclient: Allow Barbican Client Secret Update Functionality  https://review.openstack.org/19687620:18
*** kfarr has quit IRC20:28
*** jaosorior has joined #openstack-barbican20:35
jaosoriordoes anyone have an idea why docs and the functional tests gate are failing for this CR? https://review.openstack.org/#/c/205059/ in the stable/kilo branch20:36
*** kfarr has joined #openstack-barbican20:36
*** vivek-ebay has joined #openstack-barbican20:38
openstackgerritJuan Antonio Osorio Robles proposed openstack/python-barbicanclient: Create Openstack CLI plugin for Barbican  https://review.openstack.org/19873220:41
*** vivek-ebay has quit IRC20:50
openstackgerritFernando Diaz proposed openstack/python-barbicanclient: Allow Barbican Client Secret Update Functionality  https://review.openstack.org/19687620:56
*** zz_dimtruck is now known as dimtruck20:57
*** arun_kant has joined #openstack-barbican21:01
hockeynutjaosorior looks like it couldn't bring up a devstack for that CR - not sure what's different for the kilo branch21:02
*** arunkant_ has quit IRC21:02
hockeynuttook about 14 minutes between "Running devstack" and a "No hosts matched" msg21:02
jaosoriorhockeynut: Neither am I :/ thought it was supposed to work21:02
hockeynutI haven't yet had the joy of putting anything anywhere but the current release.  perhaps redrobot might check in21:03
*** alee_afk has joined #openstack-barbican21:05
*** alee_afk is now known as alee21:07
*** vivek-ebay has joined #openstack-barbican21:27
*** Kevin_Bishop has quit IRC21:36
*** dave-mccowan has quit IRC21:59
*** kfarr has left #openstack-barbican22:10
*** xaeth is now known as xaeth_afk22:10
*** max_ has joined #openstack-barbican22:22
*** max_ is now known as Guest322022:22
*** Guest3220 has quit IRC22:23
*** maxabidi has joined #openstack-barbican22:23
*** nkinder has quit IRC22:30
*** SheenaG has quit IRC22:30
*** maxabidi has quit IRC22:37
*** max_a has joined #openstack-barbican22:38
*** spotz is now known as spotz_zzz22:43
*** SheenaG has joined #openstack-barbican22:48
*** dimtruck is now known as zz_dimtruck22:51
*** chlong has quit IRC22:52
*** edtubill has quit IRC22:52
*** diazjf has quit IRC22:53
*** david-lyle has quit IRC23:02
*** gyee has joined #openstack-barbican23:20
*** dave-mccowan has joined #openstack-barbican23:32
*** gyee has quit IRC23:36
*** david-lyle has joined #openstack-barbican23:36
*** SheenaG has quit IRC23:37
*** gyee has joined #openstack-barbican23:38
*** pglass has quit IRC23:40
*** edtubill has joined #openstack-barbican23:51

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