15:00:48 #startmeeting neutron_upgrades 15:00:49 Meeting started Mon Dec 19 15:00:48 2016 UTC and is due to finish in 60 minutes. The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:50 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:52 The meeting name has been set to 'neutron_upgrades' 15:00:57 o/ 15:01:02 hola 15:01:03 hi everyone 15:01:06 #link https://wiki.openstack.org/wiki/Meetings/Neutron-Upgrades-Subteam Agenda 15:01:24 ^ I updated the page a bit to include some useful links tracking our initiatives 15:01:38 #topic Announcements 15:02:07 we are heading into Christmas time. We obviously won't have a meeting on Dec 26. 15:02:20 and neither Jan 2 that is US holiday 15:02:24 \o 15:02:29 meaning, next meeting is Jan 9 15:02:47 I will send a corresponding email after the meeting 15:02:51 any objections? 15:02:56 hi dolphm! 15:03:04 +1 15:03:11 ihrachys: hello! 15:03:25 korzen: any comments from your tower? :) 15:04:29 ok I guess Artur is busy with Christmas preparation :) 15:04:51 he is on vacation, isn't it? 15:05:09 I dunno 15:05:10 in other news, we cut off Ocata-2 the prev week. 15:05:17 Ocata-3 is late January 15:05:36 so we have like 4 weeks of work before freezes start to kick in 15:05:50 #topic Partial Multinode Grenade 15:06:24 ok as some of you may know, we had linuxbridge multinode job failing for quite some time 15:06:36 it seems like we have found and solved the last issue with it with a revert: https://review.openstack.org/#/c/345428/ 15:06:41 and it now passes 15:07:01 so now it's a matter of making it into check queue, and voting 15:07:04 the first step is https://review.openstack.org/#/q/topic:linuxbridge-multinode-grenade 15:07:21 we will collect stats on how it works in check queue for a bit before making it voting 15:08:03 armax also mentioned that he would be glad to see the job converted into HA one, as well as other linuxbridge jobs we have 15:08:13 but that will happen on its own schedule 15:08:36 so with it, we have all basic setups covered for our loose definion of rolling upgrade 15:08:50 now, for a more strict one (that implies no API downtime) 15:09:01 the spec describing the approach landed: https://review.openstack.org/#/c/386685/ 15:09:33 also, korzen started investigation on getting a job that would indeed validate mixed neutron-server versions 15:09:47 afaiu he should have talked to dolphm on the matter 15:10:08 dolphm: since korzen is not here, maybe you can give a brief intro on where the infra stands on that matter 15:11:12 (sorry, i'm actually in another meeting as well!) 15:12:30 dolphm: oh sorry, nevermind. we then collect the info async to the meeting. ;) 15:13:40 ok so just to update others, I think infra and other folks are still working on foundation to be able to set such a job. I lack details though. 15:13:54 #topic Object implementation 15:14:09 the prev week, we landed some useful bits, specifically... 15:14:16 (looking at https://review.openstack.org/#/q/status:merged+project:openstack/neutron+branch:master+topic:bp/adopt-oslo-versioned-objects-for-db) 15:14:28 validating UUIDField: https://review.openstack.org/393150 15:14:37 ^ make sure all new patches use the new type! 15:14:42 \o/ 15:14:46 o/ 15:14:50 vlan allocation OVO: https://review.openstack.org/356660 15:15:13 also delete_objects method, isn't it? 15:15:28 ^ integration will need to wait I believe until https://review.openstack.org/#/c/398873/ lands. 15:15:40 RouterRoute is integrated: https://review.openstack.org/367071 15:16:08 Allocation and Endpoint also landed, will also need to wait for Ann's patch: https://review.openstack.org/396327 15:16:35 electrocucaracha: yes, delete_objects landed too: https://review.openstack.org/403832 so make sure you consider it for new patches that integrate new objects 15:16:44 ihrachys: that's right 15:16:52 also in test framework, we now have get_random_object_fields() method: https://review.openstack.org/407007 15:17:19 there was also a non-deterministic failure in unit tests introduced by vxlan OVO fixed by https://review.openstack.org/#/c/411897/ 15:17:39 I cherry picked my changes on Ann 's patch 15:18:28 dasanind: yeah. I think Ann's patch is almost ready in general, but it needs some more safety tweaks to avoid more 3party breakages. 15:18:47 I hope she will find time for respin this week 15:19:04 ihrachys: sounds good 15:19:09 now to patches on review 15:19:11 #link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/adopt-oslo-versioned-objects-for-db 15:19:37 one thing worth noting is korzen's patch adding new DictOfMiscValuesField type: https://review.openstack.org/411830 15:19:56 this should hopefully solve issues with vif_details field in port, and configurations field in Agent 15:20:20 turned out that oslo.versionedojbects DictOfStrings is not really suitable for our cases because our dicts have non-string values 15:20:38 and the library itself does not ship a dict type that would map to our need 15:21:10 we would need to have a patch on top of the one with the new type that would use it, to see that it indeed helps. 15:21:27 is there any patch on top of it already? I think korzen was going to rebase on of them 15:22:22 ok I think the patch that korzen was going to rebase is https://review.openstack.org/#/c/407868/ 15:22:25 and it's still not rebased 15:22:42 maybe someone can take that rebase while korzen is off for vacation? 15:23:03 I can try to rebase that 15:23:09 so, that means that ndahiwade should abandon the oslo patch? 15:23:12 dasanind: cool, thanks 15:23:29 electrocucaracha: I think the oslo patch is wrong, korzen also mentioned that does not make much sense 15:23:48 electrocucaracha: I think it's more like oslo.versionedobjects type does not fit us, not that there is a bug there to be fixed 15:23:55 korzen: submitted some changes in the morning 15:23:59 electrocucaracha: so maybe also closing the reported bug as Invalid? 15:25:05 Got it, I can do it 15:25:21 electrocucaracha: cool! 15:25:37 #action dasanind to rebase https://review.openstack.org/407868 on top of https://review.openstack.org/411830 15:25:58 ack 15:26:01 #action electrocucaracha to abandon oslo.versionedobjects patch and bug modifying DictOfStringsField 15:26:58 looking for patches ready to merge... 15:27:23 electrocucaracha: I see https://review.openstack.org/#/c/306685/ has a tiny comment from rossella_s that blocks the merge for the patch. you think you can respin it? 15:28:03 Sure 15:28:29 ihrachys: https://review.openstack.org/#/c/358845/ is ready, but it is dependent on Ann's patch 15:28:53 sindhu: yeah. it will land once Ann's underlying patch does 15:29:00 dasanind: it seems like kong_ consider agent in his patch https://review.openstack.org/#/c/411830/2/neutron/objects/agent.py 15:29:17 electrocucaracha: mmm, nice. 15:29:24 s/kong_/korzen 15:29:41 electrocucaracha: but it does not show integration, so it's hard to say if it makes it better 15:30:37 ihrachys: agree, definitely we'll need the dasanind patch 15:30:56 at this point, it would be worth checking the new type on one of integrated objects to see if it's of any help. 15:31:48 ok cool, I think other patches are usual business, and a matter of reviews 15:32:09 #topic Other patches on review 15:32:40 one thing that I proposed lately is to use UpgradeImpact commit message tag more widely for any runtime dep changes 15:32:51 see https://review.openstack.org/#/c/402004/ 15:32:58 * manjeets is really happy with timely reviews on his tiny patches :) 15:33:07 manjeets: my pleasure 15:33:16 we will start to track all patches marked with the tag during the weeklies 15:33:24 #link https://review.openstack.org/#/q/status:open+message:%22UpgradeImpact%22+project:openstack/neutron 15:33:54 full disclosure: I haven't actually checked the list yet, so I have no specifics, but just a PSA we will pay attention to the list from now on :) 15:34:28 we may also need to capture patches with release notes that contain 'upgrade' section, I will think about a gerrit query for that matter 15:34:44 #action ihrachys to find a way to capture all patches on review with upgrade release notes 15:36:18 of some relevance to upgrades, I will mention a patch I landed lately to update MTUs on neutron ports: https://review.openstack.org/405532 that will allow to change MTU configuration options and see update propagated to nodes with restarted agents without the need to rebind ports 15:36:31 that is often useful on major system upgrade 15:36:57 any other patches that you think can be interesting for the team? 15:37:00 ihrachys, is there any patch already with such kind of release notes ? 15:37:31 manjeets: grep 'upgrade:' -r releasenotes/ shows 32 hits in the tree 15:38:00 okay thanks 15:38:06 ihrachys: Regarding the segment_id in port binding level, we keep it for now right? 15:38:06 example being https://review.openstack.org/#/c/329481/22/releasenotes/notes/enable-sorting-pagination-754390289d3311fa.yaml 15:38:30 sshank: why? I was thinking we will explore fixing the Level object to store its synthetic field? 15:38:46 ihrachys, got it 15:38:47 has the attempt failed? 15:41:01 ihrachys: from what I observed, network segment has a foreign key which looks at segment_id in level object. And since, the segment_id is not present, level is not created. 15:42:05 sshank: I think storing values is not implemented in base class, only loading, so if we need store to happen on parent object .create() as in this case, we need to implement the logic ourselves 15:42:26 sshank: we should also fix the db test for the object that turned out is not triggered 15:43:32 ihrachys: So we will have to override the create method in port binding level ovo class to take care of this? 15:44:08 yes. I think we already do it in several other places too. it's a common pattern that we somehow missed during object review. 15:44:25 in general, each synthetic field should support loading and storing 15:44:35 loading is from base class and thru foreign keys 15:44:42 but storing requires some code 15:44:57 we could probably come up with some smart way to generalize it into base class layer 15:45:02 so that it's automatic 15:45:10 but that's another story 15:45:22 we would need rossella_s to write some more magic for that ;) 15:45:47 Okay. 15:45:50 ihrachys, :p 15:46:41 ok let's move on 15:46:42 #topic Open discussion 15:46:59 I see no topics in the wiki page so unless you are quick, we will call it a day in a minute :) 15:47:15 to recap, we will meet again Jan 9th 15:47:32 happy holidays to those who celebrate, and happy vacation for those who don't ;) 15:47:33 happy holidays sub neutrinos 15:47:56 ok thanks everyone! keep it up! 15:48:00 #endmeeting