20:00:45 #startmeeting barbican 20:00:45 Meeting started Mon Sep 26 20:00:45 2016 UTC and is due to finish in 60 minutes. The chair is dave-mccowan. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:47 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:50 The meeting name has been set to 'barbican' 20:01:07 Hello Barbicaneers 20:01:21 o/ 20:01:26 #topic rollcall 20:01:27 hi 20:01:28 hello dave 20:01:37 o/ 20:01:48 o/ 20:02:33 o/ 20:02:47 * woodster_ not used to redrobot wave there 20:03:06 strange new world woodster_ :-) 20:03:12 o/ 20:03:49 ha! 20:03:54 * dave-mccowan channeling redrobot ... we have a few barbicaneers here today 20:04:04 haha 20:04:16 as usual, our agenda is here https://wiki.openstack.org/wiki/Meetings/Barbican#Agenda 20:04:46 #topic gate are busted 20:05:12 arunkant discovered this morning that our gates are busted due to a version upgrade to pecan 20:05:32 we have 4 failures in functional tests and 6 in unit tests related to deleting ACLs 20:05:42 * redrobot ran into failures last Friday T__T 20:06:05 we have competing interests: 1) getting gates to work, 2) not changing our API. 20:06:51 the pecan bump requires an API change? 20:06:59 dave-mccowan: should be explictly set status code to 200 ..as default behavior is changed .. 20:07:26 it's interesting. at least it's showing up in our tests in a very narrow case. our API doc and implementation says when ACL is deleted successfully, we return 200 and an empty body. 20:07:46 when we successfully delete other resources (secrets, containers), we return 204 and an empty body. 20:08:09 to keep our doc and behavior consistent, we have to trick-out pecan to keep sending 200 with an empty body. 20:08:26 wonderful 20:08:28 o/ 20:08:41 I do agree that 204 seems like the better response, but fixing success response codes is a no-no for api compatibility 20:08:52 so we're stuck with the 200s until /v2 someday 20:09:38 so to keep /v1 and be good stewards of our API, we need to figure out how to trick out pecan to keep sending 200 with an empty body. 20:09:47 yeah, sucks that slipped through though 20:10:24 the change in pecan is with a json renderer... so part of the fix might be to not use the json template for delete acl. 20:10:36 we need to be careful for unintended changes. 20:11:02 i'm working on it now, but if we there any pecan experts willing to chip in, please let me know 20:11:37 also... for some reason this gate failure is also showing up in stable/newton branch. :-( so, i think we'll need to spin an RC2. 20:12:17 I recall Oz was our last pecan expert? 20:12:34 to wrap up this topic... gates are broken, so hold off on rechecks, etc. until this is fixed. 20:13:05 #topic Newton release 20:13:24 other than the broken gates, is there any other fix that needs to go into Newton? 20:13:44 Hi Barbicaneers, I am first time here. It seems like Barbican is still not working with Neutron Lbaas TLS for non-admin tenant. 20:13:56 My update is here: https://bugs.launchpad.net/barbican/+bug/1592612/comments/5 20:13:58 Launchpad bug 1592612 in neutron "LBaaS TLS is not working with non-admin tenant" [Undecided,New] 20:14:18 welcome Jiahao 20:14:26 Thx 20:14:54 is this new behavior, or is this the first time you've tried this? 20:15:22 It stucks since late 2015 20:15:46 initially we think is only caused by bug #1519170 20:15:47 bug 1519170 in octavia "LBaaS user needs permissions to POST consumers" [High,Confirmed] https://launchpad.net/bugs/1519170 20:16:04 Jiahao please ask for help in #openstack-barbican right after this meeting. we're working through an agenda now. 20:16:07 which was fixed like 2 week ago 20:16:15 sure 20:16:16 o/ 20:16:21 will do 20:16:37 are there any other bugs that might be Newton showstoppers? 20:17:18 moving on... 20:17:29 #topic midcycle action item review 20:17:54 there were a few action items taking in the etherpad during the midcycle. 20:18:24 i just want to follow up until we decide they are done, or reassigned, or not needed any more. 20:18:51 dave-mccowan, link? 20:18:51 redrobot you had a bulk of these. any updates? (or request to pass them off?) 20:19:02 https://etherpad.openstack.org/p/barbican-newton-midcycle-topics 20:19:47 * redrobot scans etherpad 20:20:53 line 18 is done 20:21:17 I sent out an email to the dev mailing list to announce deprecation of certificate issuance 20:21:28 #link http://lists.openstack.org/pipermail/openstack-dev/2016-September/103793.html 20:21:48 there were no responses, so I assume we're good to go with deprecation 20:21:48 thanks redrobot 20:21:58 I'm punting on the blogs 20:22:38 dave-mccowan, I still think the blogs are a good idea 20:23:05 Enabling integrations would be good to have 20:23:11 dave-mccowan, (although of course I have not done the RH one yet) 20:23:43 I can't remember if Deployment Guide is the same as the Installation Guide we've started? 20:23:51 line 48 20:23:55 i think the first step is to get all the information (how-to use barbican with other projects) in one place, then we can reformat into docs, blogs, presentations, tv commercials, etc. 20:24:00 redrobot, I think so -- we need to finish it 20:24:41 dave-mccowan, I'll work on the IBM blog. Just takes some time to get through the marketing/docs people. 20:25:22 what's a good next step to make progress on this? it'd be nice to have something ready to share in barcelona. 20:26:08 start collecting info in an etherpad? 20:26:14 probably configure jobs in infra to publish the guide somewhere? 20:27:02 #action dave-mccowan find out where deployment guides need to be to get credit for maturity index 20:27:04 or wiki? 20:27:20 redrobot, dave-mccowan - there a number of different initiatives here 1) blog usage at different companies 2) collect and document integrations 3) deployment/install guide 20:27:36 maybe a wiki to track progress on each one? 20:27:45 or etherpad .. 20:28:13 there seems to be an overlap of content for each deliverable. to have a good source for verified content for these? 20:28:53 I think raising the maturity level would be a good goal to have 20:29:07 dave-mccowan, well we can put it all on the same etherpad. but they are slightly different cases 20:29:19 and yeah the maturity level thing is another initiative 20:30:12 dave-mccowan, I suggest you create an etherpad and we can start adding action items for each. 20:30:23 and track progress that way 20:30:38 #action dave-mccowan start an etherpad with a to-do list to track documentation initiatives 20:31:05 we can re-examine each week .. 20:31:28 alee_ dave-mccowan +1 20:31:45 sounds good. moving on.... 20:31:48 #topic Ocata Design Summit 20:32:05 https://etherpad.openstack.org/p/barbican-ocata-design-summit 20:32:20 please add your name to top if you plan to attend any of our sessions. 20:32:41 redrobot reserved 6 work rooms and one fish bowl for us. our schedule in on that etherpad 20:32:56 please add session ideas and vote for ones you like 20:33:28 we also need a good fishbowl idea. fishbowls are designed for a project to get input and have discussions from the broader community. 20:34:18 o/ 20:34:28 cross-project gate jobs might draw some good interest 20:34:48 hi kfarr 20:34:55 woodster_, possibly 20:35:06 woodster_ +1 20:35:13 we're adding ideas to https://etherpad.openstack.org/p/barbican-ocata-design-summit now 20:35:27 The architecture working group is interested in use cases for barbican as well...the integration tests might dove tail with those as well 20:36:09 woodster_, what use cases (other than what is already there?) 20:36:54 woodster_, maybe add that to the discussion topics 20:37:01 alee_: undercloud stuff as well as user-facing use cases. I think they'd like to formalize those use cases. 20:37:48 might be worth attending their Thursday 2pm CDT meetings 20:38:00 woodster_, well - we'd definitely like to figure out what those use cases are .. 20:38:15 woodster_ do you want to add those to the etherpad? 20:38:42 I'll carve out a placeholder section in there 20:39:20 woodster_, are you in the architecture wg meetigs? 20:40:08 dave-mccowan, might be good idea for you to attend perhaps. I can try too on occasion .. 20:40:10 I attended one last week, that's when the barbican discussions last week came from 20:41:35 #action get engaged with architecture wg to understand requirements 20:41:48 full disclosure, maybe 10% will be barbican specific, but they seem open to discussing use cases involving barbican which I think is worth attending. They are also trying to beef up arch docs in general which is interesting to some 20:42:07 i recall they really wanted a turn-key solution, and they had questions if barbican alone could add value. 20:42:53 woodster_, one of the things I have been hearing about is the idea of making barbican a less optional thing as a basic step towards improving security 20:43:12 woodster_, dave-mccowan but to do that, we need to be quite a bit more mature 20:43:37 which ties into the whole fucntional test gate thing for one thing 20:43:38 dave-mccowan Yep, and I mentiond Castellan as a way for projects to adapt into key manager support. 20:43:42 and docs 20:44:19 alee_: yeah, maturity would be a good thing to work on, as well as solid gate checks 20:44:41 woodster_, dave-mccowan the use cases envisaged by the arch wg might also be a good fishbowl topic .. 20:45:25 woodster_, though its not clear how well formed these ideas are 20:45:30 it would be great to have a barbican / security gate for lots of features 20:45:49 like cinder volume encryption and encrypted ephemeral storage and glance image signing and verificaiton 20:46:45 kfarr where is the best documentation on how to configure each of those? 20:47:42 dave-mccowan let me find them 20:48:01 kfarr, +1 20:48:17 volume encryption: http://docs.openstack.org/mitaka/config-reference/block-storage/volume-encryption.html 20:48:47 woodster_, I understand your concern about projects breaking things - but other projects are less inclined to create a gate just for barbican 20:48:48 kfarr: +1 20:49:25 woodster_, on the other hand, we have a vested interest in motifying projects when they do break barbican 20:49:36 http://docs.openstack.org/security-guide/tenant-data/data-encryption.html has a blurb on both ephemeral disk encryption and volume encryption 20:49:46 woodster_, and also have a nice place to showcase all the integrations 20:50:03 after newton release is a good time to add gates. zuul gets busy near the end of a cycle 20:50:22 kfarr thanks! 20:50:32 #topic any other business 20:50:34 alee_: yeah the concern I have is if a barbican integration gate is broken, it gets lower priority to fix, and then if the issue is another project's commit, it could take a long time to get that addressed (if at all). So if there isn't a commitment by all projects to fix things ASAP, this effort could just flounder 20:50:34 image signature verification: http://docs.openstack.org/developer/glance/signature.html 20:50:39 dave-mccowan spec https://github.com/openstack/barbican-specs/blob/master/specs/newton/deployer-specific-secret-metadata.rst needs to be removed from the Newton Release. I was unable to implement it due to critical proprietary deliverables :( We can talk more about it during the summit. 20:51:00 dave-mccowan, incidentally , as part of the barbican workship, there will be materials/ code created on how to integrate with barbican 20:51:02 normally i'd ask for review links, but since the gate is busted... 20:51:12 womp womp 20:51:39 not sure if this is a newton showstopper, but I fixed this bug: https://bugs.launchpad.net/barbican/+bug/1627176 20:51:40 Launchpad bug 1627176 in Barbican "Add secret to generic container with trailing slash fails" [Undecided,New] - Assigned to Douglas Mendizábal (dougmendizabal) 20:51:43 woodster_, yeah - understood 20:53:26 diazjf is there code that you want to remove? 20:53:49 dave-mccowan no code was merged. Just the spec should be removed. 20:55:05 alee_ great. we should make sure we can leverage that material is as many channels as possible 20:57:10 redrobot what needs to happen to release newton? we can talk later, but i'd appreciate help going through that. (or if you want to be the release steward, i'll just watch and take notes) 20:57:43 dave-mccowan sure thing 20:58:07 dave-mccowan I think the next step is letting the release manager know we may need an RC2 this week 20:58:32 dave-mccowan and we have to land the bugfixes in master 20:59:16 redrobot please check if have the permissions i need in launchpad 20:59:28 dave-mccowan: this pecan issue will likely impact stable/mitaka as well (internally we see this issue in that branch). 20:59:54 arunkant yes. thanks for identifying this. 21:00:07 out of time.... thanks everyone! 21:00:15 #endmeeting