14:00:44 <ihrachys> #startmeeting neutron_upgrades
14:00:44 <openstack> Meeting started Thu Jul 27 14:00:44 2017 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:45 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:49 <openstack> The meeting name has been set to 'neutron_upgrades'
14:01:11 <lujinluo> o/
14:01:12 <ihrachys> manjeets, lujinluo o/
14:02:08 <ihrachys> surprizingly, there were no action items in prev week
14:02:15 <ihrachys> so we will just walk through what we have
14:02:21 <lujinluo> ok
14:02:21 <ihrachys> first, gate breakages
14:02:26 <ihrachys> #topic Gate breakages
14:02:31 <ihrachys> we have several of those
14:02:56 <ihrachys> one is the FlushError on subnet create after ipallocation adoption
14:02:57 <ihrachys> https://review.openstack.org/#/c/485328/
14:03:05 <ihrachys> I now reported the bug in LP
14:03:15 <ihrachys> I tried to come up with a unit test but failed
14:03:30 <ihrachys> if someone has an idea on how to trigger it in test env, that would be great
14:04:09 <ihrachys> we also have https://bugs.launchpad.net/neutron/+bug/1704000
14:04:09 <openstack> Launchpad bug 1704000 in neutron "Sometimes OVO unit tests clash on non-unique attributes" [High,In progress] - Assigned to Lujin Luo (luo-lujin)
14:04:19 <ihrachys> for that, https://review.openstack.org/#/c/485082/ from lujinluo should do the job
14:04:25 <ihrachys> I will test it after the meeting locally
14:04:40 <ihrachys> there is a trick to make the test consistently fail, if the issue is still there
14:05:18 <ihrachys> an alternative (?) fix for that is https://review.openstack.org/#/c/485996/
14:05:18 <lujinluo> oh yes, also I think https://review.openstack.org/#/c/485082/ may also be able to fix it
14:05:25 <ihrachys> lujinluo, can you explain the relation of those two?
14:07:01 <lujinluo> so the bug 1704000 is about composite unique key violation, and behind that one necessary item is the randomly generated router_id and binding_index is already in db. In https://review.openstack.org/#/c/485082/, we switch the randomly generated router_id with an actual router's id
14:07:01 <openstack> bug 1704000 in neutron "Sometimes OVO unit tests clash on non-unique attributes" [High,In progress] https://launchpad.net/bugs/1704000 - Assigned to Lujin Luo (luo-lujin)
14:07:18 <lujinluo> in this case, since we cannot have 2 routers with the same UUIDs, we can mitigate the bug
14:08:25 <ihrachys> do we need both fixes?
14:08:33 <lujinluo> no, either one can fix it
14:09:33 <lujinluo> but since we need https://review.openstack.org/#/c/485082/ to fix bug 1705187, I think this one is enough.
14:09:33 <openstack> bug 1705187 in neutron "Add specific values to specific fields in get_random_object_fields()" [Undecided,In progress] https://launchpad.net/bugs/1705187 - Assigned to Lujin Luo (luo-lujin)
14:10:00 <ihrachys> ack
14:10:35 <ihrachys> I think that's all for gate breakages (that I am aware of)
14:10:39 <ihrachys> #topic OVO patches
14:10:44 <ihrachys> https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/adopt-oslo-versioned-objects-for-db
14:11:21 <ihrachys> first at the top is https://review.openstack.org/#/c/407868/ that is port binding
14:11:35 <ihrachys> lujinluo, I guess there is still some work to do there?
14:12:01 <lujinluo> yes, I am trying to see some logs from the Gate, because I am having trouble testing it locally
14:12:19 <ihrachys> ok. next is https://review.openstack.org/#/c/396351/ floating ip integration
14:12:34 <ihrachys> it depends on two patches (both have +2 and good chances to land quick)
14:13:10 <lujinluo> hopefully ;)
14:13:16 <ihrachys> the patch is not huge, hm
14:13:28 <ihrachys> I would expect a lot more cases of floatingip model usage
14:13:36 <ihrachys> but maybe that's indeed all there is :)
14:14:45 <ihrachys> RouterPort integration is next: https://review.openstack.org/#/c/424154/
14:14:59 <ihrachys> I left some comments yesterday, and I see lujinluo already respinned
14:15:17 <ihrachys> I will have a look
14:15:19 <lujinluo> #working hard today
14:15:46 <ihrachys> heh
14:15:57 <ihrachys> next is network dhcp agent binding: https://review.openstack.org/#/c/370452/
14:16:04 <ihrachys> manjeets, what's the status there?
14:16:22 <manjeets_> i respinned removed the synthetic field relationship and used db_obj for agent
14:16:29 <manjeets_> it fixed some tests
14:16:33 <ihrachys> seems like unit and functional tests are bust
14:16:47 <manjeets_> i saw unit test passed locally have to look over the gate results
14:17:13 <manjeets_> it did not load db_obj for object that's why its failing
14:19:00 <ihrachys> ok, more work to do
14:19:09 <ihrachys> next is type_vlan cleanup: https://review.openstack.org/#/c/482722/ by Trevor
14:19:24 <ihrachys> the fix is fine, but I am hopeful to get a unit test for that
14:19:53 <ihrachys> Trevor somewhat acked that, though his last comment is not clear to me (not sure how check-uuid is relevant there)
14:19:58 <ihrachys> anyway, we will follow up in gerrit
14:20:22 <ihrachys> next is new relationship for router-port: https://review.openstack.org/#/c/466237/ by lujinluo
14:20:38 <ihrachys> lujinluo, seems like you are now done with refresh() planting?
14:21:00 <lujinluo> yeah, i have to say that all the left .refresh()s are necessary..
14:21:20 <ihrachys> good. I will have a look.
14:21:49 <ihrachys> besides that, we don't have more patches in proper state
14:22:03 <ihrachys> James hasn't responded about his plans for subnet OVO patch: https://review.openstack.org/321001
14:22:09 <ihrachys> we may need to find someone else to take it
14:22:56 <ihrachys> oh one thing that I forgot about is the data migration CLI: https://review.openstack.org/#/c/432494/ by manjeets_
14:23:10 <ihrachys> there are no new reviews since forever
14:23:43 <ihrachys> anyway, I will need to get back to it now that I realized we will need it for updatable MTU: https://review.openstack.org/#/c/483518/
14:23:51 <ihrachys> that I am hopeful to get ready for P
14:24:42 <ihrachys> that's it
14:24:45 <ihrachys> #topic Open discussion
14:24:53 <ihrachys> note that this week is feature freeze week
14:25:04 <ihrachys> and we will have first RC1 for Pike in a week or two
14:25:29 <ihrachys> starting next week, we will probably be cautious about landing stuff like OVO switches
14:25:39 <ihrachys> I will try to nudge as many patches till Monday
14:25:49 <lujinluo> ok
14:26:08 <ihrachys> there is space for exceptions, but as long as it's approved and user visible
14:26:16 <ihrachys> so ongoing OVO transition work may need to wait
14:26:32 <ihrachys> besides that, anything else you have to share?
14:26:41 <ihrachys> who goes to Denver PTG?
14:26:48 <manjeets_> not sure yet
14:26:55 <ihrachys> I do
14:26:57 <lujinluo> me too, not sure yet
14:27:20 <lujinluo> I have one question though
14:27:36 <ihrachys> lujinluo, shoot
14:27:39 <lujinluo> for the OVO transition, are we considering other Neutron projs, like FWaaS
14:29:10 <ihrachys> lujinluo, it was not focus for the group so far
14:29:19 <ihrachys> lujinluo, which doesn't mean they shouldn't adopt
14:29:30 <ihrachys> there are some questions though to resolve before doing that
14:29:38 <ihrachys> like, moving OVO base classes into neutron-lib
14:29:49 <ihrachys> so that they can avoid importing from neutron
14:30:20 <lujinluo> ok, one of my colleagues is working on FWaaS and he is asking me if we have any plans..
14:31:05 <ihrachys> if the colleague wants to drive that, we can definitely help. so far we struggled with neutron repo only.
14:31:26 <lujinluo> ack, i will let him know
14:32:35 <ihrachys> anything else?
14:32:52 <lujinluo> none from me
14:33:19 <ihrachys> good
14:33:22 <manjeets_> none from me either
14:33:27 <ihrachys> thanks folks
14:33:31 <manjeets_> thanks
14:33:31 <ihrachys> o/
14:33:31 <ihrachys> #endmeeting