00:02:23 <thinrichs> #startmeeting CongressTeamMeeting
00:02:24 <openstack> Meeting started Thu Sep 29 00:02:23 2016 UTC and is due to finish in 60 minutes.  The chair is thinrichs. Information about MeetBot at http://wiki.debian.org/MeetBot.
00:02:26 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
00:02:28 <openstack> The meeting name has been set to 'congressteammeeting'
00:02:55 <masahito> hi
00:03:24 <thinrichs> Agenda for this week..
00:03:29 <thinrichs> 1. Newton release
00:03:33 <thinrichs> 2. Barcelona
00:03:36 <thinrichs> Anything else?
00:05:11 <thinrichs> #topic Newton
00:05:37 <thinrichs> ekcs: you've been quite busy getting Newton ready.  Want to give a report?
00:05:44 <ekcs> sure.
00:06:25 <ekcs> we’ve had quite a few late breaking bugs exposed by replicated PE testing
00:06:55 <ekcs> thinrichs and I have gotten fixes merged or in review.
00:07:34 <ekcs> all other newton target bugs fixes are in place as far as I can tell.
00:07:45 <thinrichs> ekcs: For sure it was great that you put that replicated PE test framework together!
00:07:52 <thinrichs> ekcs: never would have found those bugs otherwise
00:08:10 <ekcs> one exception is that ceilometer driver breaks on updating alarms.
00:08:41 <ekcs> but I haven’t heard back from anyone on ceilometer and I tihnk we just have to release that with documented known issue.
00:08:51 <thinrichs> ekcs: how comprehensive are those replicated PE tests at this point?  Are they covering the full API: policies/rules, datasources, drivers
00:09:03 <thinrichs> ekcs: agreed on ceilometer
00:09:42 <ekcs> here’s the ceilometer issue. #link https://bugs.launchpad.net/python-ceilometerclient/+bug/1626404
00:09:43 <openstack> Launchpad bug 1626404 in python-ceilometerclient "client.alarms.list() errors" [Undecided,New]
00:10:44 <thinrichs> I wonder if the ceilometer folks monitor the client bugs.  You sent an email too, right?
00:10:52 <ekcs> yea thanks thinrichs. Lesson learned for me is just because I’m confident with unit testing that the newly added code is good, and that the old code has been working well, doesn’t mean I should be confident that the combined result is good. new paths exercised.
00:11:04 <ekcs> yea I sent email too.
00:11:34 <thinrichs> ekcs: I'd say that's all we can really do given the late-bugs we found.
00:11:45 <thinrichs> for ceilometer
00:12:16 <thinrichs> ekcs: what's the coverage like for those replicated tests?  Not lines of code but rather the parts of the API.
00:12:22 <ekcs> tox replicated PE tests don’t test datasources yet. others seem covered. https://review.openstack.org/#/c/358927/ But datasources are exercised in tempest test. need to look again at how well covered.
00:12:57 <thinrichs> That's true—the datasources aren't as risky since they're not replicated.
00:13:25 <thinrichs> Same for the drivers
00:13:46 <thinrichs> masahito: anything you're working on for Newton?
00:13:58 <thinrichs> aimeeu: anything for Newton?
00:14:31 <masahito> I'm checking something related to dse2 control_bus.
00:15:37 <masahito> I noticed current heatbeat packet is little wrong.
00:16:15 <masahito> but the wrong part is not affected current behaviors.
00:16:22 <masahito> https://bugs.launchpad.net/congress/+bug/1628440
00:16:24 <openstack> Launchpad bug 1628440 in congress "HeartBeat packet has some invalid information." [Medium,New] - Assigned to Masahito Muroi (muroi-masahito)
00:17:10 <ekcs> masahito: oh yea. I’ve been aware of that issue. probably should’ve documented it.
00:17:34 <thinrichs> masahito: great.  If there's no user-visible problems we can demonstrate, I'd say we put that into Ocata
00:18:09 <ekcs> masahito: when I added new information to heartbeat, I didn’t realize that pballand already had some skeleton code in place for them. So I didn’t use the existing structures.
00:18:23 <ekcs> like masahito said. doesn’t affect behavior.
00:18:44 <masahito> yeah. It've be targeted to Ocata.
00:19:12 <masahito> ekcs: and I think we can refactor it.
00:20:09 <thinrichs> Okay, so I'm thinking that the code we have in review right now is all we need to worry about.
00:20:25 <thinrichs> So let's all go thru and review what we can and get those merged ASAP.
00:20:29 <ekcs> thinrichs: agreed.
00:20:45 <masahito> agreed.
00:20:47 <thinrichs> Then we can all do 1 more round of sanity checking that nothing is clearly broken.
00:20:56 <thinrichs> And we'll cut the final release after that.
00:21:12 <thinrichs> Hopefully Tue/Wed next week
00:22:01 <ekcs> thinrichs: do we need to release another RC this week?
00:22:01 <thinrichs> Any questions/comments about Newton?
00:22:35 <thinrichs> ekcs: I'll look, but I don't think it's a requirement.
00:23:11 <ekcs> also, I’m thinking about calling replicated PE a beta feature for newton. not sure that implications that has. not sure if it’s worth discussing. but just thorwing it out.
00:23:13 <thinrichs> Maybe we should cut rc2 once we get all this code merged
00:23:31 <thinrichs> Meaning put it into the docs as 'Beta'?
00:23:37 <ekcs> yea and release notes.
00:24:44 <ekcs> the idea being we have it working, but not well tested compared to the other features.
00:25:02 <thinrichs> Certainly I think a warning that it's the first release makes sense.  I don't have a strong opinion about whether we label it 'beta'
00:25:26 <ekcs> ok.
00:25:41 <masahito> Agreed
00:26:33 <thinrichs> ekcs: if you're willing to write the release note and update the docs, I'd say you can decide whether to call it beta or not
00:26:47 <ekcs> ok.
00:27:01 <thinrichs> Anything else?
00:27:07 <ekcs> none from me.
00:27:08 <thinrichs> On Newton?
00:28:00 <thinrichs> #topic Barcelona
00:28:22 <thinrichs> I created an etherpad for the topics for our 3 working rooms and 1 fishbowl room
00:28:51 <thinrichs> #link https://etherpad.openstack.org/p/congress-ocata-design-summit
00:29:06 <thinrichs> The topics are what we came up with at the last IRC
00:29:30 <thinrichs> masahito: one of the topics is having you give us an overview of how Congress is being used in the Doctor project
00:29:51 <thinrichs> masahito: you were sort of volunteered to do that.  Would that actually be okay with you?
00:30:08 <masahito> sure.
00:30:23 <masahito> I read last meeting logs.
00:30:38 <thinrichs> masahito: Great!
00:31:02 <masahito> And I'm asking now *real* policy Doctor project want to use in production.
00:31:49 <masahito> I could share what they want us at the room.
00:31:52 <thinrichs> That would be great!
00:33:04 <thinrichs> I'm already excited: prod policies!
00:33:15 <thinrichs> Ramineni_: you here?
00:33:24 <Ramineni_> Yes
00:33:34 <Ramineni_> Sorry ..I'm late
00:33:48 <thinrichs> No worries
00:34:06 <thinrichs> I was worried you had been here all along but with a capital R and so I had left you out of stuff.
00:34:28 <thinrichs> Ramineni_: do you have any code you're working on for Newton?
00:34:42 <Ramineni_> No
00:34:58 <thinrichs> Ramineni_: any progress on picking out dinner options for Barcelona?
00:35:46 <Ramineni_> Yes ..I'll send out mail today on the options .. can book that based on everyone opinion
00:37:01 <thinrichs> Ramineni_: Great!  We'll all get back to you as soon as we can.  Thanks for doing that!
00:37:36 <thinrichs> One other thing for Barcelona…
00:38:14 <thinrichs> Has anyone heard from external teams with feature-requests or use-cases for us?
00:38:33 <thinrichs> Or ideas about teams that we want to interact with during our fishbowl session?
00:38:59 <thinrichs> I've reached out to a couple of people but it'd be great if we had a few more ideas
00:39:21 <ekcs> i haven’t made progress on that.
00:39:24 <thinrichs> Here's one:
00:39:26 <thinrichs> https://blueprints.launchpad.net/congress/+spec/congress-fwaas
00:39:44 <masahito> I didn't hear any idea.
00:40:23 <thinrichs> If anyone comes to mind, let ekcs or myself know, or reach out to them yourselves
00:41:15 <thinrichs> Last thing on the agenda for today is status updates / open discussion
00:41:25 <thinrichs> #topic status and open discussion
00:41:44 <thinrichs> Anyone have status reports to give that they haven't already?  Or anything else to discuss?
00:43:18 <thinrichs> If not, we can finish now and use this time to review code.  :)
00:43:28 <ekcs> =)
00:44:33 <thinrichs> Okay, let's end early then.  Everyone go review some code so we can get Newton finished!
00:44:43 <thinrichs> See you all next week
00:44:50 <ekcs> laters!
00:44:56 <thinrichs> #endmeeting