00:05:27 <thinrichs> #startmeeting CongressTeamMeeting
00:05:28 <openstack> Meeting started Thu Nov 10 00:05:27 2016 UTC and is due to finish in 60 minutes.  The chair is thinrichs. Information about MeetBot at http://wiki.debian.org/MeetBot.
00:05:29 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
00:05:31 <openstack> The meeting name has been set to 'congressteammeeting'
00:05:44 <ramineni_> Hi
00:05:56 <masahito> hi
00:06:24 <thinrichs> This may be the first time I've been on time to the irc meeting the week of the U.S. time change in the fall
00:06:25 <thinrichs> :)
00:06:49 <thinrichs> ekcs is out of town, so he asked me to run the meeting.
00:06:50 <aimeeu> I know the feeling/1
00:06:54 <thinrichs> Agenda:
00:06:58 <thinrichs> 1. ocata-1
00:07:04 <thinrichs> 2. Newton.0.1
00:07:20 <thinrichs> 3. ocata-2+
00:07:34 <thinrichs> 4. Gate
00:07:39 <thinrichs> 5. critical patch
00:07:44 <thinrichs> 6. PTG
00:07:47 <thinrichs> Phew!
00:07:49 <thinrichs> Anything else?
00:08:40 <thinrichs> #topic ocata-1
00:08:54 <thinrichs> ocata-1 is scheduled for next week.  (Time flies!)
00:09:30 <thinrichs> Here's the list of work scheduled for ocata-1
00:09:31 <thinrichs> https://launchpad.net/congress/+milestone/ocata-1
00:10:20 <thinrichs> ekcs says he's confident about getting the ones he has signed up for done
00:11:15 <thinrichs> masahito, ramineni_: for the ones you signed up for, does it look like they'll be finished?
00:11:54 <masahito> I could push it by the day, but don't have confidence to merger it.
00:13:06 <ramineni_> The one assigned to me looks like already fixed
00:13:13 <ramineni_> I'll check again
00:13:59 <thinrichs> ramineni_: ekcs left a note about re-opening the bug.  See the bottom of the page...
00:14:04 <thinrichs> https://bugs.launchpad.net/congress/+bug/1612008
00:14:04 <openstack> Launchpad bug 1612008 in congress "HAHT - Update synchronizer for distributed deployment" [Critical,Triaged] - Assigned to Anusha (anusha-iiitm)
00:15:17 <thinrichs> Looks like there's a number of bugs no one signed up for.  I picked up one of them.
00:15:53 <ramineni_1> thinrichs: that is also fixed by ekcs https://review.openstack.org/#/c/394598/
00:15:58 <thinrichs> 2 actually, since they're both the same problem
00:16:06 <ramineni_1> the reopened one
00:16:22 <thinrichs> ramineni_: maybe we just add a reference to ekcs's patch then and close it.
00:16:53 <ramineni_1> thinrichs: yes, ill do that
00:17:06 <thinrichs> ramineni_: there's one more High priority work item that's unassigned
00:17:49 <thinrichs> ramineni_ and/or aimeeu: maybe you could take a look at that one, if you have time.
00:17:59 <thinrichs> https://bugs.launchpad.net/congress/+bug/1637185
00:18:00 <openstack> Launchpad bug 1637185 in congress "two nodes may insert rules using conflicting schema" [High,Confirmed]
00:18:32 <thinrichs> That looks like a pretty substantial change though.  Would be good to at least understand more before ocata-1.
00:18:33 <ramineni_1> thinrichs: ok
00:19:15 <thinrichs> First question is whether it is worth fixing
00:19:36 <thinrichs> What are the problems that it creates?
00:19:49 <thinrichs> for the users?
00:20:10 <thinrichs> Anything else for ocata1?
00:20:26 <ramineni_1> thinrichs: but synchronizing rules before create wouldnt solve that issue
00:21:00 <thinrichs> I think it's not even a distributed-systems problem.
00:21:15 <thinrichs> People could write p(x) :- q(x) and p(x) :- q(x,y) on a single node.
00:21:40 <thinrichs> If q is a datasource schema, we're checking that already and will throw out whichever q is wrong.
00:22:02 <thinrichs> If q is defined by a rule, the system won't die—it will pick the correct one during evaluation.
00:22:39 <thinrichs> Today I don't think we check schemas on rules at all.
00:22:50 <thinrichs> except for the datasource schemas, I mean
00:23:23 <thinrichs> #topic Newton0.1
00:23:43 <thinrichs> We're planning to do another Newton release around ocata-1.
00:23:50 <thinrichs> Anyone have anything else they think needs to go in?
00:24:01 <ramineni_1> thinrichs: i didnt understand the problem correctly, so picking up correct at evaluation should be ok ?
00:24:09 <ramineni_1> may be we could discus later
00:25:21 <thinrichs> ramineni_1: agreed that picking up correct at eval seems okay.  Only downside I can see is that people will make mistakes and not realize it.  But not sure it's worth the effort to fix it given the other work we're trying to do.
00:26:05 <ramineni_1> thinrichs: ok
00:27:32 <thinrichs> Seems that no one has anything else pressing to push into the next Newton release.
00:27:54 <thinrichs> #topic ocata-2+
00:28:51 <thinrichs> Looking forward to the rest of ocata, we should look at the work items and try to understand if that's everything we want to do
00:29:03 <thinrichs> and whether the milestone assignments make sense.
00:29:28 <thinrichs> Said another way, let's take a quick look at ocata-2 bugs and see if we think they're reasonable...
00:29:49 <thinrichs> https://launchpad.net/congress/+milestone/ocata-2
00:32:07 <aimeeu> I told ecks I should be able to find the time to fix the minor bug assigned to me
00:33:03 <ramineni_1> thinrichs: mine seems to be very old bug , from kilo , ill check if the problem exists still
00:34:41 <thinrichs> ramineni_1: you may have signed up for that a long time ago.  It's probably just never been fixed.
00:34:57 <ramineni_1> thinrichs: yes, ill have a look at it
00:35:11 <thinrichs> Janet was assigned to one of the bugs, but she hasn't contributed for a long time, so I removed her.  My guess is that it was another old bug
00:36:14 <thinrichs> Any other thoughts/comments on work items for ocata-2?
00:37:40 <thinrichs> If there are things that should be added-to/deleted-from that list of work items, go ahead and do that.
00:37:48 <masahito> got it.
00:38:08 <masahito> btw, sorry slow response. I'm in kubecon@seattle now :-)
00:38:12 <thinrichs> #topic Gate
00:38:39 <thinrichs> There's been some instability in the gate with tempest Doctor test and tempest HA test
00:38:51 <thinrichs> Anyone make any progress on that?
00:39:16 <ramineni_1> thinrichs: i tried to debug , troubleshooting patch always passes :)
00:39:35 <ramineni_1> thinrichs: one looks like always timeout
00:40:39 <thinrichs> Can we replicate the timeout locally?
00:41:24 <ramineni_1> no, i tried to reproduce doctor error, but couldnt
00:41:50 <ramineni_1> thinrichs: HA test , ill try to reproduce
00:42:50 <thinrichs> ramineni_1: great!
00:43:02 <thinrichs> Anything else to discuss about the gate?
00:44:28 <thinrichs> #topic critical patch
00:44:52 <thinrichs> ekcs asked us all to look at the following patch, but then I noticed everyone did and I had yesterday, so I +2ed it
00:45:00 <thinrichs> https://review.openstack.org/394598
00:45:12 <thinrichs> and cherry-picked it to Newton, as he requested
00:45:29 <thinrichs> #topic PTG
00:45:42 <thinrichs> Did everyone see that the PTG registration is now officially open?
00:46:06 <aimeeu> Yes - what days are you all going to be there?
00:47:39 <masahito> Congress session is scheduled in Wed.-Thu.
00:47:49 <thinrichs> masahito: do you have a link to the schedule?
00:48:16 <masahito> #link http://www.openstack.org/ptg
00:48:43 <aimeeu> I guess I'm asking if there are sessions on M-T that are relevant to Congress
00:49:52 <thinrichs> I haven't heard about any session M-T that we should be attending
00:51:12 <thinrichs> ekcs should have more info.
00:51:21 <aimeeu> ok - thanks
00:51:32 <thinrichs> That's all for the agenda today.  open discussion for the last 9 minutes.
00:51:35 <thinrichs> #topic open discussion
00:51:48 <thinrichs> Or status updates
00:52:46 <thinrichs> If no one has anything to discuss, we can end a bit early.
00:53:32 <thinrichs> Let's end early then.  Thanks all!
00:53:48 <ramineni_1> thinrichs: ok
00:53:54 <aimeeu> bye!
00:54:12 <thinrichs> #endmeeting