18:00:27 #startmeeting networking_ovn 18:00:29 Meeting started Thu Sep 22 18:00:27 2016 UTC and is due to finish in 60 minutes. The chair is rtheis. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:33 The meeting name has been set to 'networking_ovn' 18:00:40 * regXboi wanders in 18:00:56 o/ 18:01:02 #topic Announcements 18:01:18 ovs 2.6.0 should be released soon 18:01:35 Once released and Newton is closed, we should include in Ocata 18:01:38 #link https://bugs.launchpad.net/networking-ovn/+bug/1622647 18:01:40 Launchpad bug 1622647 in networking-ovn "Move OpenStack requirements to ovs 2.6.0" [Undecided,Confirmed] - Assigned to Richard Theis (rtheis) 18:02:07 That's all I have for announcements today 18:02:15 anyone else? 18:02:45 #topic: Newton RC2 18:03:16 We'll need rc2 after several DHCP issues were encountered over the last week 18:03:33 Here is the WIP for RC2 release 18:03:36 #link https://review.openstack.org/#/c/374820/ 18:04:05 Should be able to cut RC2 once the following merge on stable/newton 18:04:08 #link https://review.openstack.org/#/c/374852/ 18:04:17 #link https://review.openstack.org/#/c/374454/ 18:05:22 neutron DHCP force_metadata end enable_isolated_metadata features seem to be broken in the gate 18:06:13 There was one more fix on the rc2 list 18:06:15 #link https://review.openstack.org/#/c/371191/ 18:06:26 rtheis: Can we get the NAT stuff in RC2. 18:06:31 Ramu are you able to continue with this ^^^ 18:06:36 chandrav: no 18:06:41 hi, i'm technically out today, sorry i'm late (and missed ovn meeting) 18:07:01 russellb_ and I discussed a couple days ago 18:07:03 oops, late. 18:07:11 russellb_ - go away and vacate, man! 18:07:14 I don't think stable maintainers will allow it 18:07:17 i'd really like to get the NAT stuff in 18:07:22 got it 18:07:31 russellb_: rc2? 18:07:32 but it's probably against stable policy 18:07:36 yes 18:08:09 feature backports are no 18:08:09 I have not asked, but could 18:08:17 * mestery lurks 18:08:23 @rtheis: I am updating: https://review.openstack.org/#/c/371191/ based on comments + unit test 18:08:27 bug fixes and sec patches go back 1 rel, sec patches go back 2 iirc 18:08:36 yep. 18:08:58 you could argue that lack of nat is a bug. i consider it a feature :) 18:09:10 that lack of, that is :) 18:09:29 are there any other items that we should target for rc2? 18:10:34 we could always propose it and see what happens ... 18:10:44 since this is first release, no regression risk 18:10:51 this is also true 18:11:13 sure, I can ask 18:11:30 ok, well +1 from me fwiw 18:12:09 #topic Reviews 18:12:32 We have several big features in review queue 18:13:04 (1) NAT support, (2) native DHCP v6 and (3) native metadata 18:13:16 please take a look if you have time 18:14:04 Also starting to setup a multinode job: https://review.openstack.org/#/c/373528/ 18:14:13 experimental to start 18:14:19 is the multi-node job using native services? 18:14:24 Yes 18:14:32 k :) 18:14:33 rtheis: cool 18:14:45 i'd like to remove out l3 agent job once we merge NAT support 18:14:48 anyone opposed to that? 18:14:57 and related, remote support for that entirely 18:15:04 remove* 18:15:27 support for the conventional l3 agent? 18:15:45 correct 18:15:46 if there's no realistic reason anyone would run it, go for it. 18:15:50 I'd like to see the same for dhcp and metadata 18:16:05 we had them there to work around missing native functionality 18:16:06 Sam-I-Am: that's my thinking 18:16:19 dhcp agent still provides some minor functionality that native dhcp does not 18:16:26 dns? 18:16:28 metadata support is 1 (though we'll have that resolved soon) 18:16:30 dns, yes 18:16:40 what about dns? resolution forwarding? 18:16:47 yes, internal dns support 18:16:56 resolving internal names -- nova instance name, usually 18:17:11 but you can hand it a dns ip address, right? 18:17:19 yes 18:17:21 russellb_ the only concern with removing the L3 agent job is that it also cover dhcp 18:17:28 rtheis: hm, fair point 18:17:36 most installs i know about always specify dns as something besides the dnsmasq ip address 18:17:39 we could just change it to be a variant of native services that uses dhcp agent instead 18:17:44 ack 18:17:50 makes sense 18:18:17 another CI related thing that i think babu will work on when it's time is updating our grenade migration job to use native services 18:18:20 using dnsmasq is sort of there as a last resort for resolution. however, using dns integration might be a different story. 18:18:41 it uses the l3 agent because the tests expect floating ips 18:19:46 rtheis: sorry, topic was reviews, i took us on a tangent.. 18:19:52 np 18:20:08 so just one grenade job for now 18:20:19 yes, but maybe we need 2 18:20:26 or do we also now need newton to ocata 18:20:31 the current one does a migration from ml2+ovs to ovn as a part of the upgrade 18:20:46 we probably need a new one that does newton->master with ovn before and after 18:20:49 oh, i didnt know we were doing that 18:20:55 Sam-I-Am: yeah man 18:21:06 it's got some hacks, but making it work was step 1 :) 18:21:09 a huge step 1 18:21:16 yes 18:21:18 guess we need to document it 18:21:44 I think we may have a bug opened for the newton->master grenade job 18:21:44 probably! 18:21:50 I'll check 18:21:57 hm sounds familiar 18:22:07 i remember filing a bug for "we should add a grenade job someday when it makes sense" 18:22:08 I'll also open a bug to track deprecating L3 agent 18:22:18 yeah 18:22:20 that one 18:23:33 anything else on this or other reviews to discuss? 18:24:11 #topic Conferences 18:24:28 OpenStack summit in a month 18:24:34 etherpad started 18:24:36 #link https://etherpad.openstack.org/p/networking-ovn-ocata-summit 18:24:40 feel free to add topics 18:24:57 my room request was denied for now 18:25:12 hopefully something will open or we just do an ad-hoc meetup 18:25:35 i've been wondering if it'd make sense to propose ovn as a neutron room topic 18:25:44 not sure if it makes sense to discuss it with the broader neutron dev team 18:26:13 review status, talk about future 18:26:26 was thinking devs of ovs support might be interested in talking about it 18:26:33 but i dunno 18:27:00 who to ask on that? 18:27:17 armax 18:27:47 sure, I can ask him 18:28:39 i don't feel strongly about, just happy to do it if there's enough people interested 18:29:24 sounds good 18:30:03 speaking of conferences, OVSCon is a couple weeks after the barcelona summit 18:30:15 call for presentation proposals is open until end of this week i believe 18:30:18 just going to mention that ;) 18:30:30 i'll be there 18:30:40 haven't proposed any talks though 18:31:36 i wont be there 18:31:44 me either 18:32:19 anything else on the conferences? 18:32:32 #topic Open Discussion 18:32:56 We already covered my one topic on deprecating L3 agent 18:33:34 I do want to note with Ocata opened, we should be adding release notes for new features, deprecations, upgrade notes, etc. 18:33:51 rtheis: ah, good point 18:34:16 It's nice to have them with the code review but they are easy enough to add later 18:34:28 we should probably do out best to require them with the code ... 18:34:34 agreed 18:34:37 #link http://docs.openstack.org/project-team-guide/release-management.html#managing-release-notes 18:35:09 and as alway docs would be nics 18:35:40 Sam-I-Am: should we be doing additional items for docs? 18:36:04 I feel we've been falling behind on docs 18:36:39 rtheis: yeah 18:36:45 docs have more or less stalled out 18:37:14 if you're writing a feature into networking-ovn, you must include docs with it 18:37:26 its a little difficult because of the disconnect between ovs/ovn and networking-ovn 18:37:38 docs can be within the project or ...? 18:37:46 yeah, they're all within networking-ovn 18:37:52 good 18:38:16 granted native implementations get a little weird 18:38:45 someone enabling the feature in networking-ovn for openstack should not be reponsible for writing all the docs for the underlying ovn implementation 18:39:05 primarily write about how to configure it and how it pertains to openstack 18:39:20 hopefully people are writing docs in ovn for the operation of things 18:39:45 i've got to run 18:39:55 thanks russellb_ 18:40:04 talk to you all later 18:40:07 I don't have anything else for today 18:40:10 back monday 18:40:26 other topics? 18:40:56 nothing here 18:41:01 but reminding people of docs is a thing :) 18:41:15 definitely 18:41:19 me and ryan cant be the only ones writing them 18:41:35 and occasionally you, i think 18:42:24 okay, let's wrap up for today 18:42:30 thanks 18:42:31 #endmeeting