20:00:24 #startmeeting barbican 20:00:25 Meeting started Mon Mar 27 20:00:24 2017 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:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:28 The meeting name has been set to 'barbican' 20:00:33 #topic roll call 20:00:48 o/ 20:00:59 hi hockeynut! 20:01:07 hi everyone 20:01:09 greetings and salutations! 20:01:12 hi namnh 20:01:22 Hi everyone 20:01:24 o/ 20:01:28 o/ 20:01:30 * hockeynut has to disappear in 30 mins for another meeting - sadness 20:01:51 hockeynut i saw you at the ptg, but when i went looking for you again to say hi, you'd already left town. 20:02:20 we were only allowed to go for Mon and Tues :-( Budgets suck... 20:03:18 thanks for coming everyone! our agenda is in the usual place: https://wiki.openstack.org/wiki/Meetings/Barbican 20:03:29 #topic backlog review 20:04:00 we're making great progress on both bugs and reviews. the queues are shrinking every week. :-) 20:04:33 i don't have much else to say on that, except Thanks! 20:04:42 #topic Pike Status 20:04:57 :-) 20:05:07 We have two weeks left until Milestone 1. We've already got a bunch stuff in and more in progress. 20:05:18 https://etherpad.openstack.org/p/barbican-tracker-pike 20:05:33 https://launchpad.net/barbican/+milestone/pike-1 20:05:51 the second link shows what we've schedule for Pike 1. 20:06:04 the first link is our plan for Pike overall. 20:06:36 does anyone have an update on their work items? 20:07:32 The KMIP gate check merged (yay!) 20:07:51 Is there a way you want to cross things off the pike tracker etherpad? 20:07:52 kfarr \o/ 20:08:13 Or otherwise note that they've been completed? 20:08:17 i added a new gate job for functional tests on python 3. it's part of a "community goal" for Pike. i fixed one bug, and have the functional tests running locally. the gate job still isn't working yet... i'm working on the yaml foo to fix it. 20:09:51 kfarr yes, let's update this etherpad with status as we go. 20:10:01 +1 +1 20:10:49 i think we've already done more this cycle than last, :-) but let's keep at it... the summit is taking a big bite out of the middle of the schedule this time. 20:11:13 namnh how are upgrades looking? 20:12:03 dave-mccowan: I think I have a good process for the feature :) 20:12:53 namnh thanks for working on this. we'll get another point on the maturity index when you're done. :-) 20:13:02 dave-mccowan, kfarr: by the way, could you please review and leave your comment on two patch set: https://review.openstack.org/#/c/449022/ https://review.openstack.org/#/c/447689/ 20:13:24 any thing else pike related? 20:13:44 Oh, yes, namh, I had a question about the grenade gate 20:14:01 Did you want the Barbican functional tests to run, or the Barbican tempest plugin? Or both? 20:14:50 kfarr: I mean do you need run barbican tempest during offline upgrade using grenade? 20:15:11 s/you/we/ 20:16:05 I am not sure 20:16:27 does anyone know what other project typically do with grenade to verify it "worked"? 20:16:28 kfarr: as your comment on this patch: https://review.openstack.org/#/c/446870/ 20:17:30 My understanding is that for the core services, the grenade tests will launch a stable devstack, migrate to the latest dev version, then run the tempest tests 20:17:46 dave-mccowan its normally tempest tests run before and after the upgrade 20:18:22 note that grenade isn't going to be useful for rolling or zero downtime upgrades - the OSIC team is working on a replacement tool 20:19:04 So we can run the barbican tempest plugin tests, but also I thought the barbican functional tests would be more thorough 20:20:16 kfarr i agree, functional tests would give better coverage. 20:20:29 no reason you can't put up a CR for grenade to add the barbican functional tests - I am sure others do something similiar 20:20:50 if we do a cross project tempest run, would we also need to upgrade the other projects? 20:21:58 We probably do? 20:23:21 let's take this question back to the barbican channel. i think we need to dig more into what the normal workflow is for upgrade testing. 20:23:33 moving on... 20:23:51 #topic summit 20:24:02 the summit has two parts: The main summit and a new thing, The Forum, that's kind of a skinny design summit. 20:24:41 For the Forum, Barbican has one session confirmed: an onboarding room to meet/greet and help new contributors get started. 20:24:59 gee, what if they scrap the PTG idea and just combine it with the Forum/Summit? Then everyone is in the same place at the same time? :-) 20:25:34 I have submitted a request for an additional Fishbowl session. I requested it genericly: "Key Management Contributor/Operator/Community Discussion", or something like that. 20:26:15 I think there are another couple days to submit other suggestions, if you have any. 20:26:58 the link in the email list. if you want it and can't find it, let me know. 20:27:51 does anyone want to discuss our other Summit presentation? i think between us, barbicaneers have 4 sessions to prepare for summit. 20:29:09 #topic Any Other Business 20:31:11 OK. We'll wrap up for this week. Thanks everyone! 20:31:51 #endmeeting