01:00:50 #startmeeting tricircle 01:00:50 Meeting started Wed Nov 29 01:00:50 2017 UTC and is due to finish in 60 minutes. The chair is zhiyuan_. Information about MeetBot at http://wiki.debian.org/MeetBot. 01:00:51 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 01:00:54 The meeting name has been set to 'tricircle' 01:01:29 thanks for yipei and xiaohan's hard work, we have merged the patches for lb and qos feature 01:02:14 you are welcome! 01:02:28 xiaohan will come a little later! 01:02:48 for qos, another patch for the document of qos is needed 01:02:49 you are welcome, zhiyuan :) 01:03:08 i think it could be part2 01:03:14 the document for qos will finish ASAP 01:03:57 great, it will be better if we can finish in queens-2 01:04:04 yes I agree with RonghUI 01:04:30 it's around Dec 4th to Dec 8th 01:04:36 the release day 01:06:24 that means we have one week to finish the qos doc? 01:07:37 see if we can finish it in one week, otherwise we put it in queens-3 01:08:28 that is all right. 01:09:27 and for lb, yipei, have you contacted with the octavia team about the auto installation of tricircle with octavia? 01:10:48 not yet, do we need to solve the gateway issue first? or contact octavia team now? 01:13:16 gateway issue is not that easy, in our design, the gateway ip in central neutron and local neutron will always be different 01:14:32 ok, so i will contact the team this week 01:15:01 thanks yipei 01:15:51 then what about the "distinguish request source" feature? 01:16:18 the modification of plugin.sh is needed to enable that filter automatically 01:16:29 yeah 01:17:02 i try to modify plugin.sh 01:17:31 Is it also need a test case or spec for it? 01:17:53 I need this patch in my BP. 01:18:07 but i do not know how use it ? 01:18:45 song, are you working on the "network deletion reliability" feature? 01:18:58 yes 01:19:35 I seed a email to xuzhuang last day. 01:19:56 to ask how to use this feature. 01:21:43 it's easy to see how it works from the code, the filter will fill the USER_AGENT field in the context object, so you can check where the request is from by checking the USER_AGENT field in plugin 01:21:48 i have recieved the mail, i will give a responce quickly. And to zhiyuan i want do the feature of deleting security group 01:22:21 https://review.openstack.org/#/c/518421 the implementation 01:22:34 hi 01:22:47 hi joe 01:23:24 to zhiyuan xuzhuang thank you! 01:23:26 we are talking about the "distinguish request resource" and "resource deletion reliability" features 01:25:02 xuzhuang, i think you can discuss with song offline to see how you can co-work. in my opinion, song will finish a framework for deletion reliability and take network as an example, xuzhuang can continue to finish the security group part based on the framework 01:25:49 I agree with zhiyuan about it. 01:26:13 ok 01:26:17 so for the network deletion, the database table that we may add includes four parameter: top_id，bottom_id，pod_id，resource_type is that enough? 01:27:43 ronghui, you can discuss how those fields are used in your spec, so we can see if all the fields are needed, or whether we lack some fields 01:28:16 to xuzhuang you can add my wechat, to zhiyuan i have send a request to add wechat for you last day :) 01:28:50 to zhiyuan, ok 01:29:02 to song, ok 01:29:55 oh, it's you! 01:30:08 I found that several patches have been merged, great progress 01:30:09 yeah.haha! 01:32:47 great! and our team xiaohan have finished the qos. is there any other bp for him? 01:33:46 there is a bug that can be fixed 01:34:04 https://bugs.launchpad.net/tricircle/+bug/1701508 01:34:04 Launchpad bug 1701508 in Tricircle "port not deleted in original region" [Undecided,New] 01:34:27 good! 01:34:36 good! 01:35:05 let me describe this bug a bit more 01:36:02 welcome. 01:36:18 to reproduce this bug, we create a port via central neutron, then boot a VM with this port in region1, then delete this VM. Here, though VM is deleted from region1, the port in region1 is still there 01:36:45 next, we boot a VM with this port in region2, the result is that both region1 and region2 have that port 01:38:25 oh that sounds we should release the port in region1 after delete the vm in region1. 01:39:39 currently we will delete both ports in region1 and region2 when port in central neutron is deleted 01:39:43 or to delete the port in region1 01:40:58 but to fix this bug, we need a mechanism to delete the port in region after the VM is removed, OR after the port is used in another region 01:42:53 when VM in region is deleting, can we do the same operation to the port in region? 01:44:39 we need some way to trigger the deletion of port 01:46:33 nova need to do something? 01:47:22 no, we cannot touch nova. nova will not delete the port if the port is not created by nova 01:47:46 in our case, we create a port before booting a VM, so nova will not delete the port 01:53:48 is this some problem for qos ? 01:54:57 ?? no, only document is needed for qos 01:55:57 oh yes if the port is deletion the qos which is bound with this port is deletion too 01:57:31 yes, so no need to modify the qos part 01:58:08 i think time's up, if you find out the solution, please submit a patch to fix the bug 01:58:20 got it 01:58:37 and thanks for attending the meeting 01:58:54 #endmeeting