01:02:16 #startmeeting tricircle 01:02:17 Meeting started Wed Jul 18 01:02:16 2018 UTC and is due to finish in 60 minutes. The chair is zhiyuan. Information about MeetBot at http://wiki.debian.org/MeetBot. 01:02:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 01:02:20 The meeting name has been set to 'tricircle' 01:02:47 xuzhuang, any update for your patch? 01:03:57 I have tried to use anthor physical network 01:04:36 I think there is a problem in neutron/services/segments:db.py:117 01:06:32 that line will trigger a notification and invoke registered callback 01:06:54 so functions subscribe that event will be called 01:07:27 yeah, It will have an affect on unittest and the logic that we use routed network. 01:08:44 what functions will be called by that event? 01:09:03 When we use routed network, we don't need create a network for each segment, we just use segment to maintain the relationship of routed network and real external network 01:09:53 In the unit test, it calls : Callback unit.network.test_local_plugin.FakePlugin._handle_segment_change 01:10:57 so _handle_segment_change has some logics to process segment change 01:11:30 can we override that function? if it affect our logic? 01:12:21 I haven't finded the method of _handle_segment_change in test_local_plugin 01:13:25 so the test fails becauuse missing that function? 01:15:30 the method may be created in program dynamically, it fails because the callback method need to create network 01:17:01 you can find this function in plugins/ml2/plugin.py 01:17:11 If we use mock to fix the bug in unit test, how we deal the network creation in callback when we actually use routed network and segment in new l3 network model. 01:17:41 so I think you may need to override this function 01:20:47 from the function I don't see it is creating a network 01:21:52 yeah, I have tride to override but they used notify in the db layer of segment 01:22:35 you can override the handler, the "handle_segment_change" 01:25:39 ok, I see 01:33:25 ok, have a try 01:33:39 other topics? 01:34:08 no 01:35:25 no 01:38:55 ok, let's end the meeting shortly 01:39:01 thanks for attending 01:39:10 #endmeeting