14:59:52 <regXboi> #startmeeting neutron_northbound 14:59:52 <odl_meetbot> Meeting started Fri Oct 2 14:59:52 2015 UTC. The chair is regXboi. Information about MeetBot at http://ci.openstack.org/meetbot.html. 14:59:52 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:59:52 <odl_meetbot> The meeting name has been set to 'neutron_northbound' 15:00:02 <regXboi> #chair flaviof edwarnicke 15:00:02 <odl_meetbot> Current chairs: edwarnicke flaviof regXboi 15:00:31 <regXboi> #link https://wiki.opendaylight.org/view/NeutronNorthbound:Meetings#Agenda_for_Next_Meeting_.2810.2F2.29 agenda in the usual place 15:00:39 <regXboi> #topic agenda bashing and roll call 15:00:55 <regXboi> #info regXboi 15:01:29 <regXboi> anybody? 15:02:06 <regXboi> hello? 15:02:14 <yamahata> #info yamahata 15:02:35 <regXboi> #info still waiting for quorum 15:02:44 <regXboi> flaviof, edwarnicke: ping? 15:04:10 <flaviof> #info flaviof 15:04:20 <regXboi> #info ok, that's quorum 15:05:43 <regXboi> #info edwarnicke is on firedrill, so won't make it 15:07:14 <regXboi> #topic Announcements 15:07:22 <regXboi> #info M3 was yesterday, so we are behind 15:08:06 * regXboi hopes to look at filing over the weekend 15:08:12 <regXboi> after we figure out what we are going to say today 15:08:34 <regXboi> anybody willing to help with the "paperwork?" 15:09:37 <yamahata> What kind of paper work? I'm not so familiar with the process. 15:10:12 <regXboi> yamahata: it's documented in the Simultaneous Release Process wiki page(s) 15:10:26 * regXboi looks for link 15:10:58 <regXboi> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Beryllium_Release_Plan Be SRP wiki page 15:11:19 <regXboi> #topic action items from last meeting 15:11:32 <regXboi> #info regXboi to look at adding out of order IT tests to catch other issues like bug 4188 15:11:46 <regXboi> I've not done this because the silo is burning 15:11:57 <regXboi> and I'm not going to carry it forward because the silo is burning 15:12:07 <regXboi> #info regXboi to schedule network to device map patch set at top of list for 10/2 meeting 15:12:24 <regXboi> This is on the agenda, but has been pre-empted by the silo burning issues 15:12:46 <regXboi> #info flaviof, edwarnicke to use -Dkaraf.debug to see if they can get more information on gate instability 15:13:06 <regXboi> flaviof: any progess or am I correct in this ran into the silo burning? 15:14:40 <regXboi> hello? 15:14:47 <flaviof> i did attempt to make progress on this 15:14:54 <flaviof> but my findings are nothing new 15:15:00 <flaviof> it works fine on jdk8 15:15:30 <regXboi> flaviof: since the silo is now jdk8 only, this becomes a stable/Li issue 15:15:35 <regXboi> ? 15:15:36 <flaviof> I reached out to Ryan Goulwin (sp?) to see if he know why aaa takes so long to strt 15:16:01 <flaviof> yes, that is correct, in jdk8 we doge the bullet 15:16:09 <flaviof> dodge 15:16:16 <regXboi> and we are waiting for an answer back from aaa? 15:16:56 <flaviof> Ryan opened a bug on this: https://bugs.opendaylight.org/show_bug.cgi?id=4385 15:17:31 <flaviof> but the truth is that aaa is just a red herring. 15:17:51 <regXboi> hmm 15:18:03 <regXboi> ok, that's not great, but we've bigger fish to fry 15:18:10 <flaviof> ack 15:18:30 <regXboi> #info regXboi to include multiple ODL topic in 10/2 meeting along with updated from minutes/log 15:18:43 <regXboi> again, it is there, but pre-empted by the next topic 15:18:53 <regXboi> #topic Merge and Verify Job instability 15:19:03 <regXboi> #info (otherwise known as the silo is burning) 15:19:08 <flaviof> lol 15:19:17 <regXboi> so... the yang parser merge has broken the verify silo 15:19:27 <regXboi> and I'd like to devote the rest of this meeting to getting that fixed 15:19:40 <regXboi> because we are at a dead stop until it is fixed 15:20:05 <flaviof> regXboi: do we know if in order to get it fixed involves changes in nn project, or in yangtools? 15:20:24 <regXboi> we do not know 15:20:33 <regXboi> I am hoping that it is only nn project changes 15:20:48 <regXboi> the issue appears to be with augmentation 15:20:55 <flaviof> ack 15:21:01 <regXboi> that is where the failures occur 15:21:13 <regXboi> flaviof: does ovsdb use augmentation and if so, is it working? 15:21:38 <flaviof> yes and yes. 15:21:43 * flaviof looking for an example 15:22:21 * regXboi goes and updates ovsdb repo 15:23:14 <flaviof> regXboi: southbound/southbound-api/src/main/yang/ovsdb.yang 15:23:27 * regXboi looks 15:23:58 * regXboi goes and looks at our augmentation 15:24:42 <regXboi> well, I don't see it 15:24:53 <regXboi> unless 15:25:19 <regXboi> no, I just don't see it 15:26:14 * regXboi wishes for a yang expert 15:27:10 <regXboi> the problem isn't in the parser - that compiles 15:27:15 <regXboi> but the tests blow up 15:27:27 <regXboi> because the top level namespace isn't found 15:28:55 <flaviof> colindixon: ^^ 15:31:00 <regXboi> and it's not just us 15:31:11 <regXboi> it's all sorts of things 15:32:26 <regXboi> I think I'm going to need to check the release list 15:32:57 <flaviof> regXboi: running the tests in your local system... it fails for you too, right? 15:33:01 <regXboi> yes 15:33:04 <regXboi> same way 15:33:56 <regXboi> ok, this hasn't been reported in the release mailing list 15:34:01 <regXboi> so let me send some email 15:37:46 <regXboi> and mail sent 15:37:57 <regXboi> so... we are at a dead stop until we get this fixed :( 15:38:52 <regXboi> so I'm not sure whether to continue the meeting or just call it a day until we get this fixed 15:40:40 <regXboi> flaviof: what do you think? 15:41:00 <flaviof> regXboi: we can talk about https://git.opendaylight.org/gerrit/#/c/25500/ ? 15:41:36 * regXboi looks 15:41:37 <flaviof> lingering question on that is if it is ready to be merged (aside the ongoing issue)? 15:41:59 <regXboi> um 15:42:18 <regXboi> why are we pulling mdsal items directly into neutron-spi and not via parent? 15:42:43 <flaviof> yamahata: do you have a link on the tempest test results with this gerrit? 15:42:51 <regXboi> flaviof: I don't need that 15:42:55 * flaviof more curious than anything else.... 15:42:57 <regXboi> I'm asking a question about the pom.xml 15:43:13 <yamahata> I haven't uploaded the log anywhere. 15:43:25 <flaviof> yamahata: ack, np. 15:44:02 <flaviof> regXboi: mdsal items ? 15:44:49 <regXboi> we already pull mdsal items in the parent 15:44:57 <regXboi> if we aren't getting them there, then we should 15:44:59 <regXboi> shouldn't we? 15:45:23 * flaviof looking at pom and comparing with ovsdb's 15:45:29 <regXboi> so 15:45:32 <regXboi> I gotta ask 15:45:39 <regXboi> *why* are we doing it this way 15:46:15 <flaviof> i guess that is because that is what we had in the archetype?!? 15:46:25 <regXboi> that's not quite what I meant 15:46:48 <regXboi> ok... I see 15:47:31 <regXboi> so... I would prefer the poms to be cleaner 15:47:41 <regXboi> but that can be another patch 15:47:52 <regXboi> yeah - this is ready - once the silo is back 15:48:43 <regXboi> I think it was on my list to look at yesterday, when I found the silo was burning :( 15:48:52 <flaviof> np. 15:49:13 <regXboi> I've +2d it 15:49:21 <regXboi> we can S+1 when the silo comes back 15:49:30 <flaviof> cool. thanks yamahata ! 15:49:34 <regXboi> the same with the revisioning 15:49:37 <regXboi> er reversioning 15:49:47 <regXboi> ok... anything else? 15:50:12 <regXboi> other than keep an eye on the silo? 15:50:46 * flaviof that is all from me for now. 15:51:23 <regXboi> ok, let's wrap this up 15:51:36 <regXboi> we'll see about the other issues next week 15:51:46 <regXboi> and M3 will likely be delayed by the silo 15:51:53 <regXboi> #endmeeting