18:02:20 #startmeeting astara 18:02:22 Meeting started Mon Feb 8 18:02:20 2016 UTC and is due to finish in 60 minutes. The chair is adam_g. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:02:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:02:25 The meeting name has been set to 'astara' 18:02:25 o/ all 18:02:57 o/ 18:03:27 hola.. 18:04:05 hey guys 18:04:40 #topic mitaka development 18:05:00 o/ 18:05:52 so we're quickly coming up on mitaka-3 18:06:10 hoping that we can have any feature work we want in at least up for review this week 18:06:37 ive been busy hackng away on the first of a few patches to add HA appliances, which i'll clean up and untag as WIP today or tomorrow 18:06:47 awesome 18:06:51 #link https://review.openstack.org/267263 18:07:07 I've been bit a bit sidetracked running down l2pop interaction issues 18:07:16 on top of that i think we can start layering the appliance configuration components and clustering intelligence 18:07:50 nice 18:07:57 markmcclain, is the BYONF stuff in a state where it can be thrown up onto gerrit? 18:08:40 no.. it's based on old forks... I've got to rebase and cleanup 18:08:47 ah ok 18:09:12 rods and i chatted last week about posisbly adding some hooks into the management API for viewing worker stats from the outside 18:09:33 rods, any chance you can file a quick BP just so we have something to track its work toward the release? 18:09:44 adam_g sure 18:10:20 thanks 18:11:09 markmcclain: what can I do to help with the l2pop issue as I've run into this 18:11:23 anyone else have anything to report feature-wise? any updates on VPNaaS? 18:11:28 elopez: we've got 2 issues 18:11:47 once is how to address for <= liberty and the other is how to fix to mitaka forward 18:12:06 I also have l2pop issues running Linux bridge 18:12:17 okay lets move this to next topic 18:12:18 #topic bugs 18:12:25 I'm not certain we can properly fix <=liberty without making backward incompatible changes to appliance 18:13:36 this will affect Fuel and RDO since they are behind current 18:14:21 i assume we're talking about https://bugs.launchpad.net/astara/+bug/1541864 here ? 18:14:22 Launchpad bug 1541864 in Astara "astara build router using wrong ports" [Undecided,New] 18:14:24 or is this another issue/ 18:14:45 * markmcclain reads backscroll since bouncer froze 18:15:54 yes, part of the problem. I ran into a multicast issue as well with vxlan. I think phil_h also hit this issue as well 18:15:56 That one seems to be realeted to the neutron address pair bug 18:16:13 phil_h, bug #? 18:16:30 yeah... so that's the bug that kicked off the exploration 18:16:47 I believe I may have found a kernel bug relating to vxlan multicasting 18:17:00 I've been leaning towards dividing the bug into small portions 18:17:09 I will send details off line to eric 18:18:03 ok. right now we only have 1541864 tracking this in LP. it would be good to at least update that with some triage notes 18:18:30 check out https://bugs.launchpad.net/neutron/+bug/1445089 18:18:31 Launchpad bug 1445089 in neutron "allowed-address-pairs broken with l2pop/arp responder and LinuxBridge/VXLAN" [Undecided,Confirmed] - Assigned to yalei wang (yalei-wang) 18:18:39 rods, did you guys have any luck testng https://review.openstack.org/#/c/276875/ ? 18:20:16 phil_h: I'm thinking of submitting a fix for that to address one of the >=mitaka issue 18:20:46 the would be good - othewise I cannot get linux bridge to work 18:25:23 markmcclain, which repos dose this affect? astara, astara-neutron, and neutron? 18:25:50 for mitaka would impact neutron and release notes for astara 18:26:25 for liberty and earlier astara-neutron and astara-appliance 18:26:35 ok 18:26:50 is the bug more than whats captured in https://bugs.launchpad.net/astara/+bug/1541864 or do we need others filed elsewhere? 18:26:51 Launchpad bug 1541864 in Astara "astara build router using wrong ports" [Undecided,New] 18:26:59 or is there a neutron bug already for it? 18:28:26 adam_g: yeah need to update and likely why I want to split the bug because it is a series of things 18:28:41 ok, thanks 18:28:59 some on unique to l2pop and don't impact say vxfld based deployments 18:29:19 #action markmcclain to add info and split up bug 1541864 18:29:20 bug 1541864 in Astara "astara build router using wrong ports" [Undecided,New] https://launchpad.net/bugs/1541864 18:29:29 thanks. that'd make it easier to track whats going on 18:30:40 ryanpetrello, rods did you guys have a chance to test https://review.openstack.org/#/c/276875/ and see if it addresses the blocking thread issue you saw? 18:31:15 adam_g we deployed a new package with the fix today in the morning 18:31:22 looks good so far 18:31:37 oh, cool 18:31:51 ill ping you later/tomorrow to see if it solved it. thanks 18:31:59 #topic open discussion 18:32:26 anyone with anything else to bring up? 18:32:55 not off hand 18:32:58 I'm still working on the patch to remove auto address resources 18:33:09 functional testing is the last hurdle 18:33:35 oh ya 18:33:39 the routers are going into error state, but I think that might a real bug introduced by the change 18:33:46 i messed with that a bit locally on thurs or fri 18:34:04 so have to go back and triage it a bit more 18:34:18 markmcclain, i was seeing issues with our router model, specifically router.ports, with your patch applied + how we create the router in the test suite 18:34:54 IIRC it looked liek the make_ports_callback was blowing up when router.ports=[None, None] or something similar 18:35:16 ok.. I hadn't seen that yet 18:36:05 i just pulled the patch down and ran the tests, tests failed and saw the tracebacks in the astara logs 18:36:25 ill see if i can reproduce it in the gate 18:36:30 ah cool 18:37:13 ok unless anyone else has anything, we can wrap it up 18:38:26 ok tty later 18:38:28 #endmeeting