15:01:51 #startmeeting neutron_upgrades 15:01:52 Meeting started Mon Feb 8 15:01:51 2016 UTC and is due to finish in 60 minutes. The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:53 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:55 The meeting name has been set to 'neutron_upgrades' 15:01:56 ok let's get it rolling 15:02:11 hi all. I am back with you. thanks rossella_s for running the previous meeting! 15:02:20 hello 15:02:22 rossella_s: ++ 15:02:26 o/ 15:02:28 #topic Announcements 15:02:35 ihrachys, my pleasure :) glad to have you back! 15:02:52 pc_m was wondering why we don't have a bug to track our OVO work. so here you go: 15:02:58 #link https://bugs.launchpad.net/neutron/+bug/1541928 15:02:59 Launchpad bug 1541928 in neutron "Adopt oslo.versionedobjects for core resources (ports, networks, subnets, ...)" [Medium,Confirmed] - Assigned to Ihar Hrachyshka (ihar-hrachyshka) 15:03:15 ihrachys: Thanks! 15:03:23 time to update our patches to use that bug id 15:03:26 please mention the bug in all your patches for objectification. it should answer some concerns of people outside of the team. 15:03:27 * njohnston is listening in from the back row 15:03:38 next thing is sprint... 15:03:40 #topic March code sprint 15:03:53 so as you all know, we have a code sprint in Brno in the middle of March 15:03:59 #link http://lists.openstack.org/pipermail/openstack-dev/2016-January/085328.html 15:04:06 (in case you wonder, it's in Europe) 15:04:19 we have a nearly empty etherpad for now 15:04:20 #link https://etherpad.openstack.org/p/code-sprint-neutron-objects-brno 15:04:30 but it already contains some travel related tips 15:04:40 please add your nickname in the list of attendees if you plan to go 15:04:52 I hope to see you all there ;) 15:04:59 ihrachsy: good to see connections from other big hub airports in Europe! :) 15:05:16 ihrachys:^ 15:05:35 mhickey: you are free to update the etherpad :) 15:05:52 another thing worth mentioning is that we are almost at M3 stage (that will occur end of Feb), and the release is middle of March I guess 15:06:37 just so everyone is aware that some patches may be blocked for a bit because of core team struggling to push scheduled deliverables. but I hope it won't happened much. 15:06:45 ok, now to actual business 15:06:46 #topic Partial Multinode Grenade 15:07:05 sc68cal: do you have an update? 15:07:20 We're going through Neutron and trying to get the MTU issue fixed 15:07:21 I *presume* not much changed since recently, but maybe I miss smth 15:07:58 I have a suspicion that the last 3 errors we see with floating IPs is because of an MTU mismatch between router interfaces that Sam-I-Am has discovered - possibly. 15:08:13 sc68cal: yeah. I see Sam-I-Am testing different scenarios for MTU in his local setup. 15:08:22 although we should be setting the correct MTU to the guests. So, it's still a mystery really. 15:08:36 I actually checked that assumption in gate, I am not sure it's the case. 15:09:04 specifically, I pushed a testing patch https://review.openstack.org/274358 to dump interfaces inside network namespaces 15:09:15 and checked what's there on internal router legs 15:09:21 ooooh 15:09:24 it's the same 1450 (assuming you set 1450 for network_device_mtu) 15:10:04 Gotcha. Yeah I don't like how we have path_mtu, segment_mtu and network_device_mtu 15:10:12 lots of opportunity for error 15:10:13 see here: http://logs.openstack.org/59/265759/20/experimental/gate-grenade-dsvm-neutron-multinode/d64a6e6/logs/worlddump-2016-01-30-164508.txt.gz 15:10:42 I actually planned to set a devstack setup with 1450 mtu to see whether it experiences the failure then 15:11:00 but was traveling for the whole week and hence did not have a chance. 15:11:55 if that's a local mtu issue when using 1450 mtu for network_device_mtu and is not related to internode connectivity, then I could reproduce it I guess with all-in-one 15:12:14 anyhow, need to poke that a bit more 15:12:48 yup 15:13:06 nevertheless, it's great we take MTU thing seriously: for most setups, it's not a realistic case to run with underlying infrastructure that does not support usual 1500 size for frames. 15:13:28 ok, next... the biggest topic to cover... 15:13:34 #topic Object implementation 15:13:52 I guess rossella_s is in better position to update than me. rossella_s, your stage :) 15:14:29 so as you might see from the list of the patches, there's been a lot of progress 15:14:48 yeah, FYI the list is somewhere here: 15:14:49 #link https://wiki.openstack.org/wiki/Meetings/Neutron-Upgrades-Subteam 15:14:59 mhickey, helped a lot in get the tests passing for the port ovo and 2 of the extensions, thanks! 15:15:18 a lot of patches in flight. not many merged yet, but that will roll quicker, we just set the stage for now :) 15:15:20 mhickey++ 15:15:27 np 15:15:42 korzen, also did a great job with the subnet ovo and with handling composite keys 15:16:04 yeah, composite key patch is magic 15:16:06 #link https://review.openstack.org/275790 the magic 15:16:21 * ajo reads magic :) 15:16:26 slunkad, is working on security group extension, it's still WIP #link https://review.openstack.org/#/c/275664/ 15:17:14 I am working at handling synthetic fields in a base neutron object, will send a patch tomorrow probably 15:18:33 other people joined our efforts but I don't see them in the meeting..electrocucaracha, dguitarbite, saisriki 15:18:39 a lot of work is still ongoing in base class. apparently we haven't covered all use cases when we did qos. :) 15:19:03 Hi rossella_s 15:19:10 that's an impressive list already. seems like we'll be in good position to make progress on the sprint. 15:19:16 yep 15:19:22 saisriki, do you have an update? 15:19:43 saisriki, I don't see any link for a patch in the team page, do you have one? 15:20:48 Not much. I will update the wiki page. I started working on creating DB fields for Neutron similar to that of Nova 15:21:06 saisriki, great! if you need any help please reach out 15:21:12 saisriki: thanks. I am not sure what's the scope. Can you describe which fields do you mean? 15:21:14 ok, will do 15:21:34 like... custom types? 15:21:40 I have identified IPAddress and CIDR fields for now. I am not sure if I need to add more types 15:21:53 ihrachys: yes, custom types 15:22:02 oh ok. I thought that CIDR is already supported by OVO library. but if not, yes, we need those. 15:22:08 ihrachys, it was raised by rossella_s on the privious meeting, we need SQL alchemy decorator 15:22:17 note that korzen has the first custom field in review: https://review.openstack.org/273517 15:22:27 Oh, if it is already supported, I will re-check. 15:22:34 ihrachys those fields are supported by OVO but not by sqlalchemy 15:22:39 ok, I guess I need to educate myself. will wait for the patches. 15:23:06 ihrachys, we need a translator...look at nova/db/sqlalchemy/types 15:23:12 rossella_s: oh interesting. ok, let's discuss it in gerrit once patches are up. 15:23:13 the decorator is needed to insert IPAddress and IPNetwork OVO fields to DB 15:23:22 ihrachys, ok 15:23:38 anything else object-y worth notion? 15:23:43 yes.. 15:23:46 shoot 15:23:46 I have one 15:24:07 I need some love for following patches: https://review.openstack.org/#/c/273072/ and https://review.openstack.org/#/c/268274/ 15:24:34 mhickey: yeah right. we'll get to them. I was not in position to review till today. 15:24:50 I understand; just putting it out there. thanks. 15:24:57 korzen: what's up? 15:25:06 can I modify the db_api methods to remove the ID param? https://review.openstack.org/#/c/275790/3/neutron/db/api.py 15:26:12 korzen: well, till now we tried to avoid that. but if that hugely simplifies our lives, we could reconsider it. OR have new functions with proper signature and deprecate old ones. 15:26:57 sorry I've just got disconnected for few minutes 15:27:06 ihrachys I guess that it would look cleaner if the ID would be removed 15:27:23 ++ 15:27:34 korzen: if we can go with deprecation, I would take the path. 15:27:47 ok, sounds good to me 15:28:34 ok I also encourage folks to check the patch that adds a generic RBAC capability for objects: https://review.openstack.org/#/c/250081/ 15:28:54 it's very magic and metaclass-y, but gives a promise of easy RBAC integration in the future. 15:29:06 and we'll need it when we get to porting networks to objects. 15:29:27 from software developer ro magician, need to update my CV 15:29:40 Distinguished Alchemist 15:29:42 aye, Haim is working very hard to get the RBAC patch for M-3 15:29:42 s/ro/to 15:30:09 reviews will be appreciated for that patch 15:30:22 jschwarz: ack 15:30:28 oh yeah indeed. it's not much time left to get it in, so we should push. :) 15:30:49 there are also two patches for rpc callbacks rolling upgrades: https://review.openstack.org/265347 and https://review.openstack.org/268040 from ajo 15:30:55 the 1st one should be ready for review 15:31:11 also quite tight on time and it blocks some other initiatives like qos dscp. 15:31:25 mhickey: you also have the test-only patch: https://review.openstack.org/#/c/270309/ 15:31:34 mhickey: do we still wait for new OVO release? 15:32:22 ihrachys: yes 15:32:38 mhickey: ok I gotta request a new release today on oslo meeting 15:32:54 ihrachys: I would be grateful! :) 15:32:56 and that's about it for objects, I guess. 15:32:59 #topic Open discussion 15:33:05 anything we have not covered? 15:33:40 my open would be about copying test case from OVO 15:34:01 rossella_ ihrachys are we on the same page? 15:34:09 korzen: right. we cannot rely on non-public code from oslo libraries. 15:34:20 I hate duplication mysefl 15:34:40 maybe we could talk to oslo folks to get the test declared public 15:34:52 I think we already have cases like that 15:34:57 ihrachys, good idea 15:35:05 f.e. oslo.db provides some test class for migrations 15:35:11 and we inherit from it in neutron 15:35:27 ok let me talk to oslo folks today on the matter and we'll see what they thing 15:35:29 *think 15:35:36 ihrachys, thanks! 15:35:42 ok, thx ihrachys 15:35:46 rossella_s: Is there a backlog of objects to be done or is it clear at the moment? 15:37:06 mhickey, thanks for asking...well there's a WIP patch for sec group and I haven't see any patch for port security yet 15:37:36 mhickey, if you have spare cycles I guess we can ask people directly if they need help...it that's something that might interest you 15:37:43 I think we took on ports and subnets and networks and that's already more than we can manage right now. I suggest we collaborate on existing patches to get them merged. 15:37:56 rossella_: I should be able to complete the sec group one this week.. 15:38:21 slunkad, great 15:38:30 rossella_: ok. ihrachys: agree. I will probably have less time this week with the bug deputy work! :) 15:38:38 at least good enough for review ;) 15:38:50 mhickey, right! thanks for that too! we are here if you need help 15:38:51 slunkad: no one expects it to shine on first iteration 15:38:57 mhickey, I'm busy with subnet, so maybe you can look at network OVO, if interested? 15:39:02 ihrachys: right! 15:39:27 rossella_: thanks for offering. I may come asking! :) 15:39:50 great. I guess we can make the meeting shorter and spend the next 20 mins to review patches. :) 15:39:54 korzen: I will get back to you. Maybe maxed as have patches to drive through myself. 15:40:00 thanks all and keep up the good work 15:40:06 #endmeeting