Thursday, 2015-04-09

*** kebray has quit IRC00:01
*** kebray has joined #openstack-barbican00:03
openstackgerritJohn Vrbanac proposed openstack/python-barbicanclient: Fixing the broken functional tests  https://review.openstack.org/17146500:03
openstackgerritDave McCowan proposed openstack/barbican: Add Bandit security static analysis checking via tox  https://review.openstack.org/17189300:24
*** chlong has joined #openstack-barbican00:25
*** SheenaG has joined #openstack-barbican01:03
*** crc32 has quit IRC01:14
*** SheenaG has left #openstack-barbican01:16
*** alee has quit IRC01:19
*** kfarr has quit IRC01:29
*** alee has joined #openstack-barbican01:31
*** rm_you| has quit IRC03:11
*** kebray has quit IRC03:21
openstackgerritDouglas Mendizábal proposed openstack/barbican: Document public secret type  https://review.openstack.org/17185903:22
openstackgerritKaitlin Farr proposed openstack/castellan: Add Barbican key manager  https://review.openstack.org/17191803:22
*** gyee has quit IRC03:27
openstackgerritDouglas Mendizábal proposed openstack/barbican: Document public secret type  https://review.openstack.org/17185903:27
*** dave-mccowan has quit IRC03:40
*** kebray has joined #openstack-barbican03:54
woodster_alee, are you there?03:57
aleewoodster_, whats up?04:04
woodster_alee, the retry process is running right in devstack now, but my sample test fails because the dogtag plugin is installed, not the simple one. :\04:08
woodster_alee, can I make a request that just runs the simple cert plugin for the order request? Via the ca_id feature now04:09
woodster_?04:09
aleewoodster_, really?  I'd be very surprised that the dogtag plugin was installed04:09
aleedidn't think redrobot got that working04:09
aleeare  you sure the dogtag plugin is being called?04:10
woodster_This function (https://github.com/openstack/barbican/blob/master/contrib/devstack/lib/barbican#L70) is invoked from here (https://github.com/openstack/barbican/blob/master/contrib/devstack/extras.d/70-barbican.sh#L16)04:11
woodster_...I think04:11
aleewoodster_, by the way, feel free to +2 https://review.openstack.org/#/c/169600/304:11
aleewoodster_, right -- is that parameter set?04:12
aleewoodster_, do you have logs indicating the failure?04:12
woodster_I see the test fail expecting ACTIVE, I see the retry service runs during the time but never sees a retry task, and I don't see a log indicating a task needs to be retried.04:15
aleewoodster_, what does the status indicate instead of ACTIVE? PENDING?04:16
aleewoodster_, do you see any of the dogtag tests runnning?04:16
aleethere are a whole slew of tests there that only run with dogtag04:17
woodster_so those are skipped then?04:17
aleeif dogtag is not there yes ..04:17
aleeso check to see what is run ..04:18
aleethat will tell you if dogtag is there04:18
aleewoodster_, regardless though, at some point dogtag will be there -- and so the test needs to work even in the presence of dogtag04:18
aleewoodster_, thats easy enough to do.04:19
woodster_yep, they appear to be skipped due to no dogtag import04:19
woodster_yeah, the ca_id still will need to be used for reals when we have both plugins there!04:19
aleewoodster_, ok - so no dogtag04:19
aleewoodster_, see get_dogtag_ca_id() in test_certificate_orders.py04:20
woodster_yeah, so has to be using the default plugin, not sure why it fails out in devstack and runs on my machine04:20
aleeis the order created and in pending state?04:21
aleeif so, then something went wrong with setting up the workers most likely04:21
aleeif the order is not created, you have bigger problems04:22
woodster_oh, in logs too:04:22
woodster_https://www.irccloud.com/pastebin/gOW0k77V04:22
aleeyup04:22
*** alee is now known as alee_zzz04:31
*** chlong has quit IRC05:09
openstackgerritJohn Wood proposed openstack/barbican: Add retry server and functional tests to DevStack  https://review.openstack.org/17089605:48
*** jamielennox is now known as jamielennox|away08:01
*** kebray has quit IRC08:02
*** woodster_ has quit IRC08:10
*** gitorres1 has quit IRC08:46
*** gitorres has joined #openstack-barbican08:48
openstackgerritThomas Herve proposed openstack/python-barbicanclient: Fix order listing on the command line.  https://review.openstack.org/16948109:42
*** darrenmoffat has quit IRC10:22
*** darrenmoffat has joined #openstack-barbican10:23
*** jaosorior has joined #openstack-barbican10:31
*** jamielennox|away is now known as jamielennox10:42
*** woodster_ has joined #openstack-barbican11:49
*** jamielennox is now known as jamielennox|away11:53
*** alee_zzz has quit IRC12:19
*** dave-mccowan has joined #openstack-barbican12:56
*** alee has joined #openstack-barbican13:32
*** dave-mccowan has quit IRC13:33
*** dave-mccowan has joined #openstack-barbican13:34
*** openstackgerrit has quit IRC13:53
*** openstackgerrit has joined #openstack-barbican13:53
*** jorge_munoz has quit IRC13:54
aleewoodster_, redrobot , jaosorior , any more comments on https://review.openstack.org/#/c/169600 ?  I will create another version to address woodster_ comment, but want to make sure there is nothing else.14:09
aleeredrobot, deadline for rc1 is today?  then we need to get this in ..14:10
jaosorioralee: no comments from my side14:10
*** paul_glass has joined #openstack-barbican14:10
jaosorioralee: waiting for the next CR for a +214:10
aleejaosorior, great - I'll put it up momentarily then ..14:11
openstackgerritJuan Antonio Osorio Robles proposed openstack/barbican: Switch to oslo_policy  https://review.openstack.org/17207114:13
jaosoriorwoodster_: ping14:16
jaosorioralee, redrobot, woodster_: is it me or we are not using barbican.openstack.common.context at all?14:17
*** SheenaG has joined #openstack-barbican14:17
openstackgerritAde Lee proposed openstack/barbican: Changes to get remaining cert functional tests working  https://review.openstack.org/16960014:18
aleejaosorior, woodster_ , redrobot ^^ updated with John's change.  Get out those +2's and workflows!14:18
woodster_alee: +2-ed just now14:27
woodster_jaosorior: maybe not, would that be from the middleware?14:27
aleewoodster_, jaosorior thanks.14:27
aleeredrobot, can I have a whoop whoop please?14:27
*** zz_dimtruck is now known as dimtruck14:28
jaosoriorwoodster_: seems that barbican/context.py is being used instead of the barbican/openstack/common/context.py14:28
openstackgerritJohn Wood proposed openstack/barbican: Add retry server and functional tests to DevStack  https://review.openstack.org/17089614:28
jaosoriorwoodster_: They seem to do fairly similar things, but the main difference is that barbican/context.py actually adds some roles to the context, while the one in openstack.common doesn't14:29
woodster_jaosorior: would not surprise me, that is ancient code in there I believe. Adds roles?14:29
jaosoriorwoodster_: Adds roles?14:30
woodster_jaosorior: referring to what you mentioned was different between the two14:30
jaosoriorwoodster_: that the 'roles' field in the context is not mentioned whatsoever in the openstack.common.context library14:31
jaosoriorwoodster_: And it's also not used in oslo_context, which is what I actually aimed to switch to14:32
aleejvrbanac, hockeynut , redrobot - https://review.openstack.org/#/c/169600/ just needs a workflow please.14:32
woodster_jaosorior: Oh I see. Yeah if the middleware is adding that stuff already, no need in the context14:32
woodster_jaosorior: that should be fine to do then14:32
aleedave-mccowan needs that to be merged so he can get his CR rebased on top of that.14:32
woodster_jaosorior: we have a lot of unit testing around roles anyway14:32
jaosoriorwoodster_: well, I'll upload two patches. One deleting the openstack.common.context and another one attempting to use oslo_context14:33
openstackgerritJuan Antonio Osorio Robles proposed openstack/barbican: Delete openstack.common.context  https://review.openstack.org/17208814:34
*** SheenaG has quit IRC14:34
*** kebray has joined #openstack-barbican14:36
*** everjeje has joined #openstack-barbican14:37
openstackgerritwerner mendizabal proposed openstack/barbican: Create Barbican python scripts for development.  https://review.openstack.org/17096114:39
openstackgerritThierry Carrez proposed openstack/barbican: Open Liberty development  https://review.openstack.org/17210615:01
iguethsredrobot: Hey saw you modified the status of bug #1430516 a bit ago, had you planned on taking a look at my CR for that as well?15:04
openstackbug 1430516 in Barbican "Potential resource exhaustion when registering consumers to a container" [Medium,In progress] https://launchpad.net/bugs/1430516 - Assigned to Igor Gueths (igor-gueths)15:04
redrobotigueths indeed15:04
iguethsredrobot: Awesome!15:05
redrobotigueths I think it would be a good bug to include in the Kilo release15:05
iguethsredrobot: I agree...What's the current timeline for RC1?15:05
aleeredrobot, still waiting on that workflow ..15:05
iguethsIirc it was coming up pretty fast.15:05
redrobotigueths it was supposed to be today, but we still have some outstanding bugs15:05
iguethsAh.15:05
redrobotalee you're a really good CR pusher. :-P15:06
redrobotalee I'll take a look right now15:06
aleeredrobot, great.  I'm hoping we can get dave-mccowan CRs in too - but that means getting mine in first.15:07
aleeso he can rebase on top of that15:07
redrobotalee cool.  The release manager was ok with us deferring to next week.15:07
redrobotalee but it's definitely better to land these sooner rather than later15:08
aleeredrobot, ideally today.  so you have some basis for your docs/tests on content types15:08
openstackgerritwerner mendizabal proposed openstack/barbican: Create Barbican python scripts for development.  https://review.openstack.org/17096115:25
openstackgerritJohn Vrbanac proposed openstack/barbican: Potential resource exhaustion when registering consumers to containers  https://review.openstack.org/17069315:25
*** SheenaG has joined #openstack-barbican15:26
*** mecoide has joined #openstack-barbican15:26
jvrbanacigueths, I rebased your change as I was concerned that it wouldn't merge due to the existing validate_stored_key_rsa_container function.15:28
*** mecoide is now known as apodo15:29
iguethsjvrbanac: Ah thanks! I've tried to rebase it several times in the past but Gertty was acting strangely so I never knew if the process actually worked.15:29
*** dave-mccowan has quit IRC15:38
*** rellerreller has joined #openstack-barbican15:42
jaosoriorwhat was the agreed format for public keys again?15:43
*** dimtruck is now known as zz_dimtruck15:44
jaosoriornevermind, found it15:45
redrobotjaosorior yes, it's the default public key format that openssl uses15:47
redrobotjaosorior note that the RSA format is not supported15:47
*** rm_mobile has joined #openstack-barbican15:52
*** tkelsey has joined #openstack-barbican15:54
*** dave-mccowan has joined #openstack-barbican15:56
*** gyee has joined #openstack-barbican15:59
*** darrenmoffat has quit IRC16:03
*** zz_dimtruck is now known as dimtruck16:03
*** darrenmoffat has joined #openstack-barbican16:09
jaosoriorrellerreller: ping16:12
jaosorioror redrobot16:13
redrobotjaosorior pong16:13
jaosoriorin barbican/test/utils.py, there are the functions get_private_key() get_public_key() etc... a little bit irrelevant, but, wouldn't they usually have some newline after the header and before the footer?16:14
openstackgerritMerged openstack/barbican: Changes to get remaining cert functional tests working  https://review.openstack.org/16960016:15
jaosorioraaah16:16
jaosoriorI had forgotten that those newlines were added by alee already in the commit that just merged16:16
jaosorior:P16:16
redrobotjaosorior yeah... we're having to do ghetto DER -> PEM conversions since cryptography.io doesn't support it yet.16:17
jaosoriorin tha hood16:18
aleeyeah! merged!16:19
jaosorioralee: your commit is gonna make my life a lot easier (working on a fix for a bug)16:19
*** ccneill has joined #openstack-barbican16:20
aleejaosorior, excellent16:20
jaosorior:D16:20
redrobotjaosorior not that for the correct workflow, the entirety of the public.pem file needs to be base64 encoded16:20
aleerellerreller, thanks for the workflow -- redrobot , rellerreller beat you to it ..16:20
redrobotalee I saw :(16:21
jaosoriorredrobot: huh?16:21
rellerrellerredrobot ?16:21
aleeredrobot, but now at least we have something that is working -- even if its not doing what you suggest is the right thing to do.16:21
redrobotjaosorior rellerreller so I think the bug stems from mixing up a detail of the PEM implementation, and what the 'base64' encoding means for a single POST request16:22
redrobotthe fact that a PEM file uses base64 under the hood does not mean that it is base64-encoded16:22
redrobotie, if you were to read the contents of the public.pem file, and feed that to base64 decode you would get an error16:23
rellerrellerredrobot You mean because it has header and footer that are not base64?16:23
redrobotrellerreller in addition to the newlines, yes16:23
redrobotif you look at the PEM as a whole, it is not a base64 string16:23
rellerrellerredrobot I agree. I also thought of this.16:23
rellerrellerI kept it that way for backwards compatability reasons.16:24
rellerrellerI think we need PEM, binary, and base64 types16:24
redrobotrellerreller not necessarily.16:25
redrobotrellerreller take a look at these workflows: http://docs-draft.openstack.org/59/171859/3/check/gate-barbican-docs/9671d40//doc/build/html/api/reference/secret_types.html#public16:25
redrobotrellerreller the one POST workflow, and the POST+PUT workflow should result in the same thing:  A DER stored in Barbican16:25
redrobotrellerreller when a client makes a request (with application/octet-stream) they should get back the DER File they originally sent up16:26
rellerrellerredrobot It does not matter how the bytes are stored in the backend secret stores16:26
redrobotrellerreller yep, I don't think a client should care how they're stored as long as they can retrieve the same thing they sent16:27
*** darrenmoffat has left #openstack-barbican16:27
rellerrellerredrobot I agree about the request to retrieve back in DER format. Unfortunately we do not accept an enocding type for return.16:27
redrobotrellerreller yea, I think we should stick to PEM only for Kilo.  If we want to be able to request both PEM and DER, then that could be a Liberty feature16:28
rellerrellerI think the real bug is that the return type cannot be specified. I should be able to retrieve in DER or PEM or whatever.16:28
jaosoriorredrobot: well, the http://docs-draft.openstack.org/59/171859/3/check/gate-barbican-docs/9671d40//doc/build/html/api/reference/secret_types.html#example-2-2 would issue a DER with newlines...so I guess those should be stripped either by the user or us, not sure how that will end up working in the b64encode16:28
rellerrellerredrobot Every secret is returned in binary format. That is what the API specifies.16:28
redrobotrellerreller actually, every secret has a list of "content_types"16:28
redrobotrellerreller the client can make a choice of what they want16:29
redrobotrellerreller DER can be considered binary16:29
rellerrellerredrobot Every secret has a list of content types but there is no code to return back in that format.16:29
redrobotso, since we're limiting input to the DER format only, and calling that application/octet-stream, then on the retrieve application/octet-stream should return the same DER16:30
redrobotif we want to be in the business of converting from DER to PEM we'll need to define our own content-types16:30
rellerrellerredrobot "Note that even if a binary secret is provided in the base64 format, it is converted to binary by Barbican prior to encryption and storage. Thereafter the secret will only be decrypted and returned as raw binary."16:31
redrobotrellerreller yes... so that's a convenience feature provided by barbican.16:31
redrobotI hope I can clear up confusion about this16:31
redrobotif you look at example 2.1, the POST creates the metadata, and the PUT sends a binary request that includes the entire contents of the PEM16:31
rellerrellerredrobot We are not limiting on the input side. The secret can be input in several formats.16:32
*** arunkant_ has joined #openstack-barbican16:32
jaosoriorredrobot, rellerreller: so, it seems that store_crypto was trying to fetch the contents of the PEM header twice, even though it was done already by the plugin.resources, this CR https://review.openstack.org/#/c/172144/ actually returns the correct key. Taking the steps to reproduce the bug that redrobot put in the bug report16:32
rellerrellerI tried adding tests for binary input but was unable to get those working.16:33
rm_mobileCertificate orders return DER? I always assumed everyone operated with PEM :(16:33
redrobotrellerreller I think we are limiting the "public" secrets to DER only.  Let me explain16:33
redrobotso, for Example 2.1, the PEM is sent as binary in the PUT.16:33
redrobotsome clients may have an issue with sending two requests16:33
redrobotit would be more efficient to send only one request16:33
rellerrellerredrobot What do you mean by PEM is sent as binary?16:34
redrobotrellerreller I mean, it takes the bytes of the content of the pem file and sends them as is, in their entirety16:34
redrobotso, back to making only one request16:34
redrobotin order to reduce the two request workflow into a single one, it is necessary to send a JSON request to specify the metadata16:35
redrobotthe contents of the PEM file do not fit in a JSON request16:35
redrobotso in order to fit it inside the JSON request, we Base64 encode the contents of the PEM file16:35
redrobot"payload_content_encoding"="base6416:36
redrobotmeans that the base64 conversion was done to fit it inside JSON16:36
rellerrellerredrobot How does that make it smaller? It sounded like you did base64(base64(pem)).16:36
redrobotno16:36
redrobotonly base64(PEM)16:36
redrobotrellerreller look at Example 2.216:36
rellerrellerBut how can that be smaller than a PEM file?16:36
redrobotrellerreller it's not smaller.  It's just friendly to JSON16:37
redrobotbase64 by definition expands the input16:37
rellerrellerSo by fit you meant encoding issue and not size issue.16:37
aleeredrobot, when you say "friendlier", what do you mean?16:37
rellerrellerI heard fit and think it's a size issue. My mistake.16:37
redrobotalee if you look at the contents of the PEM as a whole, there are certain bytes that are not allowed inside a json string16:38
rellerrellerJSON does not sound like it will accept some of the bytes of the PEM file. Perhaps the newlines?16:38
redrobotalee namely the newlines16:38
redrobotyes, in JSON format, newlines must be escaped16:38
redrobotso, because the PEM has newline characters, we cannot place it as-is in a JSON string16:39
redrobotthus, we HAVE to encode it somehow16:39
redrobotsince we're already using base64 for symmetric secrets, it makes sense to use base64 again for a PEM16:39
aleeredrobot, so we need to use base64.encodestring()?   or base64.b64encode()?16:39
redrobotif you're doing it in python it would be something like:16:40
rellerrellerredrobot why not base64 of DER?16:40
aleeredrobot, there is a difference -- base64.b64encode() strips out the newlines.16:40
redrobotrellerreller because the PEM is what openssl produces by default.16:40
redrobotrellerreller as per your spec, we only support the DER16:40
redrobot*derp, I mean, per your spec, we only support the PEM16:40
rellerrellerredrobot My spec does not limit that16:41
aleeredrobot, this is important because without the newlines, it isn't valid PEM, and so things like load_privatekey() will fail.16:41
rellerrellerredrobot You can pass in a base64 encoded DER and it will work16:41
rellerrellerredrobot Now the API and code says it will only return in binary. That was not my doing.16:41
redrobotrellerreller http://specs.openstack.org/openstack/barbican-specs/specs/kilo/content-type.html#content-encoding-for-each-secret-type defines only the PEM type16:42
redrobotrellerreller for public key that is16:42
rellerrellerredrobot That spec defines the relationship between Barbican Core and the SecretStore. That is not with the API.16:43
redrobotalee http://paste.openstack.org/show/201398/ note that encode/decode of the entire PEM preserves newlines16:43
aleeredrobot, actually it doesn;t -- that was precisely the point of my CR16:45
redrobotalee try running that paste.16:45
jaosorioralee: it seems it did preserve them16:45
aleeredrobot, let me rephrase -- if you do this with a private key and you try to load that private key, it fails.16:45
aleethats why I ended up putting in base64.encodestring() and decodestring()16:46
redrobotalee I still haven't worked through the private key workflows16:47
aleeredrobot, well - I don't see the point of doing private keys different from public keys16:47
aleeredrobot, the public key is derivable from the private key16:48
redrobotrellerreller my mistake.  I assumed that the types you spelled out were going to be the types that were acceptable throughout barbican.  I don't think the spec is clear on what is expected from a user point of view16:48
rellerrellerredrobot The problem you are really having is that you want to give Barbican a PEM file and have it return a PEM file?16:48
redrobotalee I suspect that private keys are also not being base64 encoded in their entirety16:48
redrobotrellerreller yes.  I thought that format conversions were outside the scope of this BP16:49
rellerrellerIf you want to store a PEM and retrieve a PEM then do a POST with secret type opaque where payload is base64(pem).16:50
rellerrellerredrobot Until we can specify the return type as something other than binary then this is all that you can do.16:50
redrobotrellerreller "binary" does not necessarily mean that it has to be a DER16:51
rellerrellerredrobot For public and private keys what else would it mean?16:51
redrobotif we want to say that retrieving a key by using "application/octet-stream" means that you are getting a DER, then we should require a DER on input as well16:51
rellerrellerredrobot I disagree. I think you should be able to store a key using any format and return in any format.16:52
redrobotrellerreller I think that it is a good goal to have, but I don't think we can do that in Kilo... not if we want to release next week anyway.16:53
rellerrellerJust like with openssl. It can write keys out in DER or PEM format. Underneath the hood the bytes of the key are the only thing that matter.16:53
rellerrellerredrobot Likely not unless someone does not feel like sleeping.16:53
redrobotrellerreller I think so to, but to make that work, we would need to define new content-types for each possible format16:54
*** xaeth_afk is now known as xaeth16:54
rellerrellerredrobot I don't understand that last comment.16:54
redrobotsince the spec did not mention many different formats, I assumed that we would start with only one format and add new formats down the line16:54
redrobotok, so when I retrieve a secret from barbican, I send a content-type, right?16:55
redrobotI can choose one from all the ones that are listed in the secret metadata16:55
rellerrellerredrobot yes16:55
*** kebray_ has joined #openstack-barbican16:55
aleerellerreller, I agree with you, but thats not going to happen for K.  what does need to happen is that we need to define all the possible inputs for public and private keys, and then we need to make sure we can access them and use them in the stored key cert request case16:55
*** kebray_ has quit IRC16:55
alee(and return them as binary)16:55
rellerrellerredrobot You can also choose foo and bar. It does not matter.16:55
*** kebray_ has joined #openstack-barbican16:56
redrobotrellerreller so, the content_types property was always supposed to be used to limit the content-types that you can use to request a secret16:56
redrobotrellerreller so you can't use foo and bar16:56
redrobotrellerreller if you use a content-type that is not listed in the content_types metadata, then barbican responds witn "Not Acceptable"16:56
rellerrellerredrobot Unless that is happening in a validator then I don't know where that check happens.16:56
rellerrellerredrobot If it is then that is ok. We limited it, but it does not affect the way the result is returned.16:57
aleecrowds with pitchforks calling me for lunch --- redrobot - I'm looking forward to seeing that spec ..16:57
redrobotcrap, I need to run too16:57
*** alee is now known as alee_lunch16:57
redrobotlet's continue this discussion after lunch?16:57
*** kebray has quit IRC16:57
rellerrelleralee redrobot Google hangout?16:57
alee_lunchyes please16:57
redrobotrellerreller sure thing, mind scheduling one at about 3:30pm CST?  I have a dentist appoint ment at 2pm16:58
rellerrellerToday might be a little tough for me, but I am open all day tomorrow.16:58
redrobotok, let's aim for tomorrow then16:58
rellerrellerredrobot thanks.16:58
rellerrellerI only have one free hour this afternnon.16:58
alee_lunchfien for me tomorrow.  that gives redrobot time to write something down ..16:58
alee_lunch(it will go a lot faster if we have actual expected use cases)16:59
openstackgerritJohn Wood proposed openstack/barbican: Expose root cause plugin exceptions  https://review.openstack.org/17186817:00
*** openstack has quit IRC17:13
*** openstack has joined #openstack-barbican17:13
-sendak.freenode.net- [freenode-info] why register and identify? your IRC nick is how people know you. http://freenode.net/faq.shtml#nicksetup17:13
*** apodo has quit IRC17:22
*** ccneill has quit IRC17:27
*** rellerreller has quit IRC17:32
*** kebray_ has quit IRC17:35
*** gyee has quit IRC17:40
*** kebray has joined #openstack-barbican17:52
*** kfarr has joined #openstack-barbican18:00
*** kebray has quit IRC18:07
*** kebray has joined #openstack-barbican18:11
*** everjeje has quit IRC18:16
*** jkf has joined #openstack-barbican18:21
*** alee_lunch is now known as alee18:21
iguethsredrobot: Just saw your comment...I hadn't written a negative test specifically targetting the schema change, given that there was already a test to evaluate all the fields within the Consumer request payload.18:25
iguethsHowever, if we don't think that putting in a specific test is going to duplicate what is already there, then np I'll drop it in.18:26
*** tkelsey has quit IRC18:26
*** ccneill has joined #openstack-barbican18:48
*** nickrmc83 has joined #openstack-barbican18:53
*** nickrmc84 has quit IRC18:54
*** ccneill has quit IRC19:09
*** mdarby has joined #openstack-barbican19:12
*** mdarby has quit IRC19:13
*** mdarby has joined #openstack-barbican19:14
openstackgerritKaitlin Farr proposed openstack/barbican: Makes all alembic version scripts pep8-compliant  https://review.openstack.org/17218119:15
*** everjeje has joined #openstack-barbican19:39
*** kfarr has quit IRC19:51
*** rm_mobile has quit IRC20:11
*** jaosorior has quit IRC20:22
woodster_core devs out there, please workflow this CR: https://review.openstack.org/#/c/17096120:55
*** crc32 has joined #openstack-barbican21:01
*** rm_you has joined #openstack-barbican21:16
*** rm_you has quit IRC21:16
*** rm_you has joined #openstack-barbican21:16
*** alee has quit IRC21:22
*** mdarby has quit IRC21:27
*** kebray has quit IRC21:31
openstackgerritMerged openstack/barbican: Delete openstack.common.context  https://review.openstack.org/17208821:34
openstackgerritMerged openstack/barbican: Create Barbican python scripts for development.  https://review.openstack.org/17096121:37
*** kebray has joined #openstack-barbican21:49
*** kebray has quit IRC21:55
*** paul_glass has quit IRC22:07
*** xaeth is now known as xaeth_afk22:08
openstackgerritMerged openstack/python-barbicanclient: Fixing the broken functional tests  https://review.openstack.org/17146522:11
*** igueths has quit IRC22:21
*** dave-mccowan has quit IRC22:22
*** dimtruck is now known as zz_dimtruck22:37
*** alee has joined #openstack-barbican22:41
*** dave-mccowan has joined #openstack-barbican22:41
*** paul_glass has joined #openstack-barbican22:59
*** arunkant_ has quit IRC23:16
*** gyee has joined #openstack-barbican23:16
*** SheenaG has quit IRC23:31
*** everjeje has quit IRC23:36
*** crc32 has quit IRC23:38
*** jkf has quit IRC23:44

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