14:00:00 #startmeeting networking 14:00:01 Meeting started Tue Feb 14 14:00:00 2017 UTC and is due to finish in 60 minutes. The chair is jlibosva. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:05 The meeting name has been set to 'networking' 14:00:08 Hello friends! o/ 14:00:12 hi 14:00:13 Hi 14:00:16 o/ 14:00:29 #topic Announcements 14:00:35 hi 14:00:37 O/ 14:00:40 o/ 14:00:46 o/ 14:00:50 The PTG is next week - http://lists.openstack.org/pipermail/openstack-dev/2017-January/110040.html 14:00:56 o/ 14:00:58 We already have quite an attendance :) 14:01:08 Ideas/topics to discuss are put here: https://etherpad.openstack.org/p/neutron-ptg-pike 14:01:08 o/ 14:01:12 o/ 14:01:17 o/ 14:01:22 I assume it's gonna we walked through soon and somehow organized 14:01:40 hi 14:01:43 Pike specs are now open https://review.openstack.org/#/c/429855/ 14:01:44 o/ 14:01:55 yeah. note there is a -final version: https://etherpad.openstack.org/p/neutron-ptg-pike-final 14:02:15 hi 14:02:16 ihrachys: ah, thanks. I didn't know about that one 14:02:20 though it's not final, I believe kevinbenton was going to scrap it once more 14:02:40 yeah, i want to go over one last time to assign some chairs with ihrachys and armax 14:02:50 oh, i haven't added me.... 14:02:58 but i think the topics are pretty finalized 14:03:19 i need to see what new stuff has hit https://etherpad.openstack.org/p/neutron-ptg-pike 14:03:23 over the weekend 14:04:35 kevinbenton: since you're here, do you want to lead? :) 14:05:08 no 14:05:14 ok 14:05:17 :) 14:05:33 So about the Pike specs open - please if you have any proposals that didn't make it to Ocata, you'll need to rebase/re-propose for Pike. 14:06:12 We have a sort of a new Neutron CI meeting regularly on Tuesdays at 4pm UTC. 14:06:19 That's in 2 hours. I encourage everyone interested in gate stability to join. 14:07:08 late allo allo 14:07:14 \ 14:07:20 About Ocata - we have an assessment https://review.openstack.org/#/c/425990/ 14:07:29 if you are a feature owner, please have a look 14:08:09 and comment 14:08:22 Ocata is planned to be coordinated release on Feb 22nd 14:08:53 That's all I had to announce. Anybody else wants to announce anything? 14:09:47 ok, moving on 14:09:49 #topic Blueprints 14:10:32 As I said, Pike specs are now open so please rebase to Pike proposals that didn't make it to Ocata 14:11:29 For Ocata, I believe only very-very-critical things can be set - https://launchpad.net/neutron/+milestone/ocata-rc2 14:12:16 ihrachys: korzen I see no patches for ovo in the wiki, do you want a dedicated topic? 14:12:59 Some changes for enginefacade switch will be glad to get reviews - https://review.openstack.org/#/c/402750/ and https://review.openstack.org/#/c/404715/ 14:13:01 I will only mention that korzen and electrocucaracha started working on online migration mechanism in neutron-db-manage, and they have a WIP: https://review.openstack.org/432494 14:13:28 it's not ready right now, and there is some design work to do, but that's a topic that will require some oversight from the whole team later, so a heads up 14:14:18 other than that, I don't think there is much to bring up right now 14:14:52 ihrachys: ok, thanks for heads up 14:15:06 ataraday_: thanks for bringing this up, I see one already has +2 :) 14:16:08 anybody else has some links that need attention? 14:16:29 #info enginefacade patches: https://review.openstack.org/#/c/402750/ https://review.openstack.org/#/c/404715/ 14:16:49 #info online migration mechanism WIP patch https://review.openstack.org/#/c/432494/ 14:17:31 I think we can move on 14:17:35 #topic Bugs and gate failures 14:18:08 jlibosva: I have one 14:18:10 :S 14:18:21 electrocucaracha: for blueprints? 14:18:26 electrocucaracha: or bugs? 14:18:39 well, it was related with the code coverage 14:19:08 any comment is welcome https://review.openstack.org/#/c/432432/ 14:19:38 electrocucaracha: ok, thanks 14:20:00 I think that belongs here to gate 14:20:44 I'd also like to remind here again the Neutron CI meeting, which will be in 1.66 hours: https://wiki.openstack.org/wiki/Meetings/NeutronCI 14:21:12 I was the bug deputy for the last week 14:21:20 Nothing major has been reported last week, was pretty calm 14:21:37 weird for a week so close to release :) 14:21:53 no one tests rc :P 14:22:45 armax is the bug deputy for this week, so we're in good hands 14:23:07 anybody wants to raise any bug here? 14:24:39 no? so we can move to the next topic 14:24:42 #topic Docs 14:25:07 jlibosva: Hi! 14:25:09 I saw john-davidge waving at the beginning of this meeting :) Do you want to give any updates about docs? 14:25:12 * jlibosva is too slow 14:25:14 hm do we have deputies for next weeks? just sayin 14:25:30 wanna go back to bugs for a deputy? 14:25:36 ihrachys: hmm, good point. I forgot about PTG 14:25:41 #undo 14:25:41 Removing item from minutes: #topic Docs 14:26:16 any volunteer for keeping an eye on bugs during PTG? :) 14:27:02 preferrably someone not on ptg 14:28:05 I can 14:28:09 electrocucaracha: thanks! 14:28:12 electrocucaracha: phew! thanks 14:28:16 I mean, I won't go so I can do it 14:28:29 thanks electrocucaracha! 14:28:40 yay electrocucaracha 14:28:41 we'll miss you in Atlante, though 14:28:51 indeed 14:28:52 we all hope not many bugs will be filed in the release week :) 14:29:16 mlavalle: i won't miss electrocucaracha in AtlantE ;) 14:29:22 that will be boring amotoki 14:29:45 I think we can get back to docs :) 14:29:48 #topic Docs 14:29:53 john-davidge: hi again :) 14:30:15 Ok, so recently we've been landing lots of patches related to #link https://bugs.launchpad.net/openstack-manuals/+bug/1656378 14:30:15 Launchpad bug 1656378 in openstack-manuals "Networking Guide uses RFC1918 IPv4 ranges instead of RFC5737" [High,In progress] - Assigned to John Davidge (john-davidge) 14:30:39 Anybody is welcome to pick up a related patch if they have some free time 14:31:15 Also, there will be an openstack-manuals/neutron corss project session at the PTG sometime on monday or tuesday 14:31:38 Particularly to discuss a re-organisation of the networking guide and encourage contributions 14:32:12 That's it from me 14:32:23 you can check the networking guide for newton release at http://docs.openstack.org/draft/draft-index.html 14:32:40 amotoki: Thanks :) 14:32:52 john-davidge: thanks for updates 14:32:54 If you find points to be changed or added, let's file a bug and hopefully propose a patch 14:34:02 yep, thanks amotoki 14:34:03 Yes, final version will be cut just before the PTG 14:34:32 john-davidge: did the docs team change the timing of branch cut? 14:35:13 IIRC previously the branch was cut after several weeks after the release 14:35:22 amotoki: Not that I'm aware of, that's what I last heard from asettle 14:35:35 Will double check with her 14:35:39 john-davidge: okay, let's ask her 14:36:20 anything else related to docs? 14:36:26 not from me 14:36:37 me to 14:36:38 too 14:36:47 john-davidge: amotoki ok, thank you for all updates :) 14:36:51 #topic Transition to OSC 14:36:56 amotoki: do you want "the mic"? 14:37:16 i have no specific update this week 14:37:46 I plan to discuss the remaining transition plan in Atlanta with OSC team 14:37:58 amotoki: is neutron client gonna be released the same time with all other projects? 14:38:23 jlibosva: could you elaborate more? 14:38:31 amotoki: I mean if the releases are synced 14:38:43 jlibosva: afaik neutron cli is already released 14:38:55 jlibosva: cli releases were 2 (or maybe 3) weeks ag 14:38:57 o 14:39:01 dasm: aah, ok. thanks 14:39:05 in Ocata, we didn't release neutronclient in the middle of releases. 14:39:19 I agree it is not good. 14:39:43 as dasm said we released neutron client for Ocata release 14:40:01 amotoki: ok, thanks. I must have missed that 14:40:24 that's all from me today 14:40:30 ok, moving on 14:40:32 but, worth to mention, neutron cli is rleeased as 6.1 and marked as deprecated 14:40:37 *released 14:41:47 dasm: good, thanks for info 14:42:05 #topic Neutron-lib and planned neutron refactoring 14:42:10 boden: hi, are you around? 14:43:27 it seems like he is not 14:43:38 maybe too early for him 14:43:49 yeah though he usually shows up 14:44:09 #topic Open discussion 14:44:17 there are no new items to on demand agenda 14:44:34 so if anybody wants to discuss anything here, now is the chance 14:44:44 we have 15 mins left, so we have plenty of time 14:44:51 jlibosva: sorry I was away for a min 14:45:00 boden: I knew you are around :) 14:45:05 #undo 14:45:06 Removing item from minutes: #topic Open discussion 14:45:21 boden: do you want to give any updates :) 14:46:26 Much of the same as last week in neutron-lib. As armax mentioned last week we can likely start landing more lib patches this week and into next so I would encourge folks to take a peek at the reviews out there 14:46:55 #link https://review.openstack.org/#/q/project:openstack/neutron-lib+status:open 14:47:06 I think we have 1 active neutron-lib impact patch.. give me 1 sec 14:49:31 The 2 lib impact patches are listed on the neutron meeting wiki; although the patches need to be refreshed once merged they will impact consumers of the relevant functionality 14:50:06 #link https://review.openstack.org/#/c/421562/ uses the providernet API definition from lib 14:50:35 #link https://review.openstack.org/#/c/422210/ uses the portbindings api def from neutron-lib 14:51:01 #link https://review.openstack.org/#/c/421562/ uses the providernet API definition from lib 14:51:16 oh, the bot doesn't say anything? ok 14:51:36 for more details, please see the neutron-lib section of the meeting wiki 14:51:55 and lastely, please don’t forget to add any relevant neutron-lib topics to the PTG etherpad 14:51:58 that’s it from me 14:52:04 boden: ok, thanks 14:52:28 #topic Open discussion 14:52:31 we have 8 minutes left 14:52:33 I've sent an email for openstack-dev about "Alternative approaches for L3 HA" and I'll happy to get some comments there :) 14:53:03 #link http://lists.openstack.org/pipermail/openstack-dev/2017-February/111953.html 14:53:07 ataraday_: thanks :) I put a link here 14:53:32 jlibosva, thanks :) 14:53:50 ataraday_: do you want to discuss it here? or ML is doing fine? 14:53:58 ML fine :) 14:54:13 cool 14:54:33 just to bring some attention to it :) 14:55:10 I'm sure people will read 14:55:19 anybody else has anything to mention here? we have 5 minutes 14:56:11 I think we will skip the meeting next week 14:56:20 I would just like mention here again that there is a Neutron CI meeting in an hour :) at this channel, please show up if you're interested in gate stability 14:56:27 amotoki: yeah, good point. 14:56:33 jlibosva: you go extra mile to advertise it, thanks :))) 14:56:37 kevinbenton: are you still here? I guess next week there won't be a meeting, right? 14:56:51 next next meeting? 14:56:57 jlibosva: yeah, i assume no meeting next week 14:57:09 kevinbenton: you assume? you're the boss now, you must be sure :) 14:57:11 for the record, next is 28th then 14:57:19 maybe a message to the ML will be helpful 14:57:20 jlibosva: yeah, no meeting 14:57:26 :] 14:57:30 jlibosva: it would be too soon to provide feedback from PTG 14:57:52 very first hours of ptg vertical track, not bad maybe 14:58:07 or horizontal maybe 14:58:31 kevinbenton: jlibosva: are you talking about the meeting of the week Feb 28th? 14:58:54 amotoki: yeah, the next meeting will be 28th 14:59:00 yeah, it's confusing how kevinbenton mentioned feedback 14:59:16 unless it was a joke, that I struggle to distinguish that early 14:59:18 ihrachys: i was thinking if we had some sessions done already 14:59:25 ihrachys: we could provide some info for remote folks 14:59:28 it will be just a start, and only cross project 14:59:32 ah, I got it as a joke 14:59:38 :) 14:59:56 so indeed next 28th I assume then 15:00:01 ok, we're out of time 15:00:04 thanks for showing up :) 15:00:08 o/ 15:00:09 #endmeeting