21:00:57 #startmeeting networking 21:00:58 Meeting started Mon Apr 3 21:00:57 2017 UTC and is due to finish in 60 minutes. The chair is kevinbenton. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:59 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:01:02 hi 21:01:03 The meeting name has been set to 'networking' 21:01:53 #topic announcements 21:02:19 o/ 21:02:23 hi 21:02:47 the openstack summit is about a month away from now 21:03:51 hello 21:03:58 there will be a component of it called "The Forum" that is relevant to developers 21:04:00 https://wiki.openstack.org/wiki/Forum 21:04:25 to get feedback from users and operators 21:04:40 that's a good idea 21:04:48 the topics people are interested in have been submitted here: http://forumtopics.openstack.org/ 21:05:40 we will find out soon which of those are selected 21:05:47 by the forum selection committee 21:06:04 and then we will know which neutron relevant sections have been picked 21:06:26 so people at the summit can plan to attend 21:06:40 and people that can't make it can offer feedback ahead of time 21:07:30 that's all for the forum 21:07:43 does anyone have any other announcements? 21:08:50 this is the firs time using that approach right? 21:09:00 yes 21:09:20 since there wont' be a design summit 21:09:30 this is the way operators are supposed to get feedback to users 21:09:32 ok, let's give a try 21:09:44 sorry (to developers) 21:09:50 finally more DevOps culture 21:10:07 ok, moving on 21:10:11 #topic neutron-lib 21:10:44 boden can't make it to this meeting but he left me this message 21:11:07 (a) we need to cleanup the periodic failures before the␜ 1.4.0 release can happen (see ^^).. (b) there are some core neutron rehoming patches that could use some review lovin: https://review.openstack.org/#/q/project:openstack/neutron-lib+status:open+topic:bp/neutron-lib-networking-ovn 21:12:40 so it sounds like there are some failures that need to be fixed before we can release 1.4.0 21:13:06 boden took care of one of failures inside midonet, althought now it's failing in other place ;) 21:13:12 and odl is almost done. 21:13:24 when we'll be past that, we will release new neutron-lib 21:13:32 dasm: ok, so these are just failures in stadium projects and not the main repo? 21:13:38 both failures seem to be unrelated to neutron-lib, but better have it covered 21:13:48 kevinbenton: yes. just midonet and odl 21:13:56 dasm: ok, thanks 21:14:40 #topic bugs 21:15:00 amotoki is going to be bug deputy it looks like this week 21:15:23 haleyb: do you have any bugs from last week that need some attention? 21:15:23 i was deputy last week 21:16:07 https://bugs.launchpad.net/neutron/+bug/1677729 21:16:07 i'm wondering if the work on that is done 21:16:07 Launchpad bug 1677729 in neutron "some tests failing after merge of "Skip DHCP agent query in provisioning block setup"" [Undecided,New] 21:16:14 there's the bot 21:16:41 haleyb: oh, yes 21:16:51 haleyb: it's been temporarily fixed with a revert 21:17:21 ok, i'll leave open then ? 21:17:22 haleyb: but we need to get fullstack fixed so we can remove it again 21:17:25 haleyb: yeah 21:17:37 haleyb: and assign to Jakub 21:17:49 haleyb: he was going to look into adding the dhcp agent to fullstack 21:17:52 kevinbenton: always a good idea when someone isn't here :) 21:17:59 LOL 21:18:00 haleyb: ;) 21:18:01 haleyb: yes :) 21:18:21 this was another one that i have not triaged, but was also port race condition 21:18:23 https://bugs.launchpad.net/neutron/+bug/1677131 21:18:23 Launchpad bug 1677131 in neutron "race condition between interface detach and port delete" [Undecided,New] 21:18:28 it's on mitaka 21:19:33 kevinbenton: i was wondering if that rang a bell with you 21:19:54 it's not a common scenarios meddling with your own ports 21:20:53 haleyb: i'll dig into that one afterwards 21:21:00 haleyb: haven't heard of that issue before 21:21:23 ok, nothing else critical that i saw 21:21:29 haleyb: ack 21:22:07 anyone have any other bugs that need reviews or attention? 21:22:54 ok 21:23:00 #topic blueprints 21:23:17 https://review.openstack.org/#/c/410101/ 21:23:40 ah 21:23:43 this is will fix the issue of qos_policy with mechanism_driver so review will help 21:24:10 just need another core review for that 21:24:10 mlavalle: ^^ 21:24:10 kevinbenton: will take alook 21:24:21 thanks mlavalle kevinbenton 21:24:21 for blueprints, is anyone with an approved blueprint blocked by anything? 21:24:37 e.g. not getting reviews, dependent work not moving, etc 21:25:51 ok 21:26:04 #topic docs 21:26:43 kevinbenton: I have a question retaed to this https://review.openstack.org/#/c/383673/ 21:26:51 kevinbenton: https://review.openstack.org/#/c/348947/ 21:26:52 princenana: sure 21:27:18 kevinbenton: need reviews for https://review.openstack.org/#/c/347867 21:27:21 armax: proposed a slightly different approach to what's been implemented 21:28:10 kevinbenton: in general for the config options refactoring patches 21:28:14 Can you check out his comments on https://review.openstack.org/#/c/383673/ kevinbenton 21:28:32 princenana: yes, i'll make a note to review this later today 21:29:02 sindhu: ack, i'll add it to my queue 21:29:13 haleyb: can you take a look at it as well? 21:29:14 ok kevinbenton 21:29:20 kevinbenton: great, thank you :) 21:29:23 haleyb: looks mainly agent related 21:29:47 kevinbenton: ack 21:30:08 I don't see john-davidge online 21:30:25 so unless someone else can give use a docs update we'll just move on 21:31:21 #topic OSC 21:31:38 anyone online that can give us an update here? 21:31:55 i see last week amotoki just announced that things were progressing steadily 21:32:03 so i assume that's still the the case 21:32:41 #topic open discussion 21:33:18 ok, anyone have anything else to bring up? 21:33:18 yeah, I want to update on the Upstream Institute 21:33:18 otherwise we might have a nice short meeting this week :) 21:33:18 mlavalle: sure 21:33:28 mlavalle: "Upstream Institute"? 21:33:29 We are going to have a Neutron on-boarding room in Boston 21:33:59 The Upstream Institute is the training that takes place for new comers the weekend before the summit 21:34:19 ack 21:34:19 As sindhu mentioned earlier, it would be great to have these patches merged https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bug/1563069 21:34:42 and after that initial training, new contributors are encouraged to go to the projects on-boarding rooms, during the week 21:34:50 ours will be on Wednesday 21:35:07 I'll put together an agenda and submit for the team to review 21:35:34 I would like some of our team memebers come and see hello to the newbies 21:35:35 say hello^^^ 21:35:39 I had a question regarding Neutron policy: Is the Neutron policy.json meant to be an exhaustive list of Neutron policies? And is Neutron planning on moving to policy in code any time soon? 21:35:48 that was it, a quick update :-) 21:36:20 mlavalle: thanks. assuming I can go i'll try to show up :) 21:37:05 that would be great, to have the PTL there :-) 21:37:05 mlavalle: when things get a little closer we should put together an etherpad of neutron dev attendees 21:37:06 yeah, let's do it 21:37:06 mlavalle: just for general coordination 21:37:13 i'll add that to my todo for the next couple of weeks 21:37:20 ++ 21:37:45 blancos: there isn't a plan to move it into code yet 21:38:15 blancos: it's been discussed before occasionally 21:38:15 blancos: usually at design summits 21:39:07 blancos: but it's one of those things where it's going to be a lot of work and it will inevitably break someone's deployment 21:39:17 blancos: so it's been lower priority 21:40:11 kevinbenton: I see, thank you :) 21:40:35 for context, what blancos is talking about is getting rid of the /etc/neutron/policy.json file and having all of those permissions directly in the neutron code 21:40:43 so operators wouldn't be able to modify it 21:41:36 ok, if that's all 21:41:46 we can take 18 minutes back 21:41:52 yaay! 21:41:54 thanks yall 21:41:55 have a nice day! 21:41:59 thank you 21:42:02 #endmeeting