16:06:50 #startmeeting networking_cisco 16:06:50 Meeting started Tue Nov 22 16:06:50 2016 UTC and is due to finish in 60 minutes. The chair is sambetts. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:06:51 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:06:54 The meeting name has been set to 'networking_cisco' 16:07:11 As normal agenda is avaiable here: https://wiki.openstack.org/wiki/Meetings/networking-cisco]# 16:07:15 As normal agenda is avaiable here: https://wiki.openstack.org/wiki/Meetings/networking-cisco 16:07:32 #topic Roll call 16:07:36 o/ 16:07:37 o/ 16:07:44 o/ 16:09:12 * tbachman is here now 16:09:12 caboucha o/ 16:09:47 anyone else? bobmel? 16:09:56 sambetts: Hi, here 16:10:29 cool, moving on 16:10:36 #topic Announcements 16:11:39 #info It appears that the RDO maintainers are trying to CI networking-cisco in master OpenStack 16:11:50 anyone got anything else? 16:13:22 ok moving on 16:13:29 #topic Compatibility shim work 16:14:54 So more things are being moved from neutron to neutron_lib in the Ocata cycle, so we need to start handling more variables/constants etc in our backward compatibility layer 16:15:11 sambetts: I have this patch: https://review.openstack.org/399552 16:15:33 where I'm trying to fix a bunch of those issues 16:15:54 Yup :) thats definatly a great start 16:16:05 But it's not so easy, one thing after the other breaking 16:16:58 So as more things get added I wanted to use this topic to address some of the structural design of the compatiblity layer 16:16:58 But I'm getting closer 16:17:43 right now we're using the backwards_compatiblity module to handle all of this, but I'd like to move away from having a single big bloated file 16:17:59 +1 16:18:31 I'd much rather we went down the path of having modules like networking-cisco.constants that handles constants and a networking-cisco.attributes for handling attributes 16:19:49 this makes it transparent from the drivers/plugins perspectives that there is a compatiblity layer in place 16:20:22 I think that's fine, I think we may want to break stuff down to ml2 and non-ml2 too maybe? 16:24:43 the basic design I'm thinking is if we can build the compat stuff into our existing modules instead of being so explicit about it 16:25:17 in the 399552 I bring all neutron.common.constants and neutron_lib.constants into backwards_compatibility.constants 16:26:04 But the same thing could be done so that the constants instead go into neutron_cisco.constants 16:26:20 bobmel: yeah, I would prefer if that was simply networking-cisco.constants 16:28:11 bobmel: and then I also want to try (over time of course) to move the networking-cisco specific constants dotted around networking-cisco into that module too 16:29:26 sambetts: Departing for other meeting 16:29:34 ok o/ caboucha 16:29:39 Something that add complexity is that we're not having releases so in mitaka some of it is in neutron.common.constants and in newton some of that has moved to neutrn_lib 16:30:30 right thats what we handle in our compatiblity layer 16:31:23 Yes, but implementing the compatibility layer itself is the crux. At least that is what my experience in 399552 :-) 16:34:30 right, but that pain is something we decided to absorb to because its outweighed by what we gain being compatible with multiple versions 16:36:52 #topic Stable Ocata (master) compatibility 16:37:50 So how is that patch going bobmel? It looks quite complete, do you need any help other than reviews? 16:43:27 sambetts: No, don't think so. But reviews will be good. But it is not yet passing master and newton 16:43:35 But fairly close 16:44:55 bobmel: awesome :) I'll try to review it again soon 16:45:05 #topic CI Status 16:46:07 #info CI is still down because of lab issues, continuing to investigate 16:47:42 #topic Sub/Driver team feedback 16:48:29 Any updates from the driver teams? 16:49:03 bobmel: I believe the asr patches are a high priority now? 16:54:58 * tbachman wonders if sambetts is looking at tbachman for this ;) 16:57:34 this https://review.openstack.org/#/c/399228/ patch is the one I was wondering if we needed to push for reviews on 16:58:21 is it ready to go? and which patches do we want to land before we cut 4.1.0? 16:59:48 sambetts: sorry for the delay, yes I think ASR is the prio now, both for ACI and standalone (i.e., without ACI) 17:00:24 sambetts: But might be good to check with Leon/Brian too 17:00:52 sambetts: I’ll have a look at that patch today 17:00:55 ok thanks 17:01:01 we're out of time 17:01:07 thanks for coming guys 17:01:10 #endmeeting