20:00:19 #startmeeting barbican 20:00:20 Meeting started Mon Oct 12 20:00:19 2015 UTC and is due to finish in 60 minutes. The chair is redrobot. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:23 The meeting name has been set to 'barbican' 20:00:29 #topic Roll Call 20:00:38 As usual the meeting agenda can be found here: 20:00:42 o/ 20:00:43 o/ 20:00:46 \o/ 20:00:47 #link https://wiki.openstack.org/wiki/Meetings/Barbican 20:00:53 o/ 20:00:56 o/ 20:01:02 o/ 20:01:05 o/ 20:01:13 o/ 20:01:23 o/ 20:01:38 o/ 20:01:40 woot! lots of barbicaneers here today 20:01:48 let's get started! 20:01:52 o/ 20:01:52 its a murder of barbicaneers 20:01:55 #topic Tokyo Summit 20:02:04 #link https://etherpad.openstack.org/p/barbican-m-design-sessions 20:02:24 A few items here 20:02:30 o/ 20:02:38 First, I added the topics for the fishbowls to the etherpad 20:02:58 unless someone really needs them to be flipped, I will go ahead and update the description on Sched to match. 20:03:11 Fishbowl 1: Wednesday, 12:05pm - Barbican Roadmap and Integration Status 20:03:17 Fishbowl 2: Wednesday, 2:00pm - Barbican Key Federation 20:03:40 o? 20:04:07 spotz I think you really are here! ;) 20:04:18 hehehe 20:04:28 o/ 20:05:12 o/ 20:05:13 I'm going to guess by the silence that everyone is on-board with the fishbowl topics 20:05:39 I'm good +1 20:05:47 good with me 20:05:52 +1 20:05:54 +1 20:06:12 I've also added a section to the etherpad to hopefully identify some Cross-project liaisons for the Summit 20:06:40 these would be folks who are interested in attending other project's design sessions to talk about possible Barbican integrations 20:07:18 For example hockeynut is our official QA (QE?) Cross-project liaison, so he'll probably be spending a lot of time with the QE folks 20:07:53 It would be good to identify someone to attend Magnum design sessions 20:07:54 Do we have anyone familiar with Swift? 20:08:00 redrobot I tried to do 50/50 @ Vancouver, will do the same in NRT 20:08:00 redrobot, sorry - whats the etherpad link again? 20:08:14 https://etherpad.openstack.org/p/barbican-m-design-sessions 20:08:20 alee ^ 20:08:21 alee https://etherpad.openstack.org/p/barbican-m-design-sessions 20:08:23 thanks 20:08:26 rellerreller jinx! 20:09:08 redrobot, I'll go to the magnum sessions 20:09:08 rellerreller, I know some swift 20:09:19 alee awesome, thanks! 20:09:24 diazjf are you attending the summit? 20:09:37 rellerreller, yeah I'll be there 20:09:45 diazjf awesome! 20:10:13 diazjf I know they have a spec out for a KeyMaster, which is almost identical to Castellan's KeyManager. 20:10:29 redrobot, I'll probably go talk with the Manila guys too 20:11:04 redrobot I will sneak into some Neutron as well. 20:11:32 rellerreller, I have actually been working on that. jrichli on our team owns it. 20:11:56 diazjf I thought you knew them. I thought you mentioned that at the mid-cycle. 20:12:12 I would like to discuss that at some point. 20:12:36 rellerreller, yup a new version is in the works involving Castellan. Yes that would be great 20:13:16 I wrote it on my white board under "Tokyo agenda" so it's official now. 20:13:35 ^rellerreller, awesome 20:14:37 I may need to stop by Nova and Cinder. I'm not sure where we are with that yet. 20:14:49 alee hockeynut diazjf feel free to add to the etherpad with the project's you'll also be working with. 20:14:54 I don't know if they have the latest KeyManager from Castellan yet. 20:15:03 ack 20:15:33 redrobot, rm_work whats the status of neutron/octavia with barbican? 20:15:55 #info Please vote on the etherpad by adding a +1 to topics you're interested in 20:16:08 redrobot, I'll add it under New Topics 20:16:18 The plan is to do the usual etherpad-driven design discussions from the last summit/mid-cycle 20:16:45 with the "big tent" our design time is a lot shorter than previous summits 20:16:56 so I want to focus on stuff that's important to everyone 20:17:21 #info notify redrobot if you think we need dedicated design sessions 20:17:22 redrobot: why did "big tent" shorten our design times? 20:17:24 Do we vote on new topics and punted ones as well? 20:17:38 lisaclark1 lots more projects under the big tent now, not as much space to go around for everyone. 20:17:40 I was not sure if punted items are still under consideration. 20:18:25 rellerreller that's why I think we should +1 individual topics 20:18:40 rellerreller we should be able to shake out what's still important from previous design topics 20:18:57 What's the deadline for the voting? 20:19:16 Does next Monday's meeting sound reasonable? 20:19:29 Is there a max number of votes or anything? 20:19:39 Next Monday sounds reasonable to me. 20:20:04 rellerreller nah, i don't think we need to limit the amount of votes 20:20:24 just limit to one +1 per person per topic 20:21:15 And these are votes for design session talks? 20:21:33 There are things on here that interest me, but not necessarily enough to warrant a design session. 20:21:38 rellerreller yeah... well to get an idea of priorities for design session time 20:21:54 OK, sorry for all of the questions. 20:22:08 rellerreller I don't want to limit to one topic per session because we only have a handful of them. 20:22:56 but I will definitely consider full session requests 20:23:12 redrobot did you notice that you're on a panel at the same time as one of our design sessions? 20:23:23 last summit, for example, we had a full session dedicated to CA PLugins specifically to meet with Symantec folks that were unavailable at other times. 20:23:42 dave-mccowan have not noticed that... 20:24:02 dave-mccowan they're usually pretty good about not having conflicts... I may need to dust off my cloning machine :-\ 20:25:46 Any other questions/comments about the summit, or planning before the summit? 20:26:46 meetups and parties^^ :) 20:26:50 Are there options to attend remotely? 20:26:58 + oo diazjf 20:27:03 If one is willing to stay up for the time change, taht is 20:27:07 that 20:27:57 kfarr: we tried to do a remote vidyo session for some of our rackers during the vancouver summit and ran into challenges 20:27:58 kfarr I'm not sure what the rooms will be like... we can definitely plan to do a google hangout if there's interest 20:28:16 Ok! 20:28:28 I'd like to be a part of that as well! 20:29:03 kfarr, silos: if we get a google hangout going we can add the details on the design session etherpad 20:29:19 sounds good, thanks lisaclark1! 20:29:20 kfarr silos ok, we'll plan for it... although as lisaclark1 pointed out, it wasn't an optimal way to get remote folks participating 20:29:39 ok. 20:29:50 thanks! 20:31:19 ok, moving on 20:31:28 #topic py34 update 20:31:41 dave-mccowan would you mind updating? 20:31:53 as we all have noticed, there have been about 20 CRs over the last couple of months with weird byte vs. string patches 20:32:04 victor and pradeep have done most of them 20:32:41 the last few they got in the weeds with some of our our plugin code. it's hard enough keeping base64 vs. text straight, and now bytes vs strings too. 20:32:51 so, i did a big patch to finish up the rest of the tests. 20:32:53 https://review.openstack.org/233633 20:33:19 it has all the tests running, but requires oslo.serialization 1.10 which is not in global-requirements yet. 20:33:36 but, please review mercilessly... especially the kmip stuff. 20:33:50 after this, the PY34 CRs will stop. 20:34:07 :-) that's all. any questions? 20:35:20 i have a question... the goal per openstack now is to just get the code to be compatible.... not actually work. right? anyone know? 20:35:33 Thanks dave-mccowan! Will take a look, and will look at the kmip changes in particular 20:35:55 Are they making changes that break things? 20:36:13 python3 breaks All the Things 20:36:24 dave-mccowan hehe, I think the goal is to get the service to where deployers can run it on py3 if they choose to. 20:37:27 i'd be really surprised if our functional tests worked with python3. i'm not sure if it's worth trying. i'd be curious to know if other projects have done more than unit tests. 20:39:37 dave-mccowan interesting... definitely a good challenge for someone wanting to get it running on py3 20:39:50 ok, moving on 20:39:58 #topic Liberty release notes 20:40:00 arunkant ping 20:40:13 redrobot: yes 20:40:26 #link http://lists.openstack.org/pipermail/openstack-dev/2015-October/076012.html 20:40:33 arunkant since you were asking about release notes 20:40:44 there was an ask on the mailing list to get those written up on the wiki 20:40:56 * hockeynut has to pick son up now. 20:40:56 I was wondering if you would want to write them arunkant ? 20:41:34 redrobot: let me check the mail.thanks for looking into this. 20:42:24 Lana Brindley messaged me about them over the weekend. She said the doc team is willing to proofread, but they would like to have the wiki updated today... 20:42:27 well by EOB today anyway. 20:43:04 * rellerreller has to leave now 20:43:21 ok..let me check what is needed. 20:43:30 awesome, thanks arunkant 20:43:42 #action arunkant to write Liberty release notes in OpenStack wiki 20:44:30 redrobot: will ping you if have questions 20:44:31 arunkant I know it's not a whole lot of time, so just let me know when you can get to it. 20:44:34 arunkant thanks! 20:45:13 redrobot: will look into this in next hour or so. 20:45:25 #topic Naughty project list 20:45:30 #link http://lists.openstack.org/pipermail/openstack-dev/2015-October/076559.html 20:46:18 we're on a list of projects that may break with an upcoming devstack change 20:47:19 it would be good to get things fixed up before it becomes a problem 20:47:35 I also noticed we were on another list of clients that may break, but I can't find the mail link right now 20:49:38 ... If I find it, i'll post it to our irc channel 20:49:55 anyone have time/interest into fixing the devstack issue? 20:51:37 #help we need someone to fix the devstack issue mentioned in http://lists.openstack.org/pipermail/openstack-dev/2015-October/076559.html 20:51:47 ok, that's all I have on the agenda for today 20:52:00 got a few minutes left 20:52:05 #topic Open Discussion 20:54:10 Is there a reason why the Orders Resource doesn't have an API page? I was going to create one unless there's a reason it didn't survive the migration from the old wiki to the new one. 20:55:30 silos I think it still needs to be moved/rewritten 20:55:42 redrobot: gotcha. 20:56:17 silos http://git.openstack.org/cgit/openstack/barbican/tree/doc/source/api.rst has some info on it 20:56:23 silos that page is an orphan though 20:56:30 silos so it's not getting built into the html site 20:56:59 redrobot: Ah I see. thanks for the link. I'll see what I can do. 20:57:00 redrobot i don't think barbican is on the naughty anymore. http://goo.gl/6p8lvn 20:57:46 silos certificates.rst has some info too, but a full on orders doc would be awesome. 20:58:29 dave-mccowan: I noticed that. I'll reference certificates as an example. Some good examples in there. 21:01:42 alright y'all 21:01:44 we're out of time 21:01:50 thanks for coming! 21:01:53 #endmeeting