01:00:15 #startmeeting tricircle 01:00:16 Meeting started Wed Mar 14 01:00:15 2018 UTC and is due to finish in 60 minutes. The chair is zhiyuan. Information about MeetBot at http://wiki.debian.org/MeetBot. 01:00:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 01:00:19 The meeting name has been set to 'tricircle' 01:01:14 I have sent out a mail to nominate song as the core reviewer of tricircle, please vote on that mail :) 01:01:33 thanks for zhiyuan. 01:02:11 OK 01:02:12 ok 01:03:26 ok 01:04:07 #link http://lists.openstack.org/pipermail/openstack-dev/2018-March/128142.html 01:04:08 Yipei, I have read your new spec, the overall proposal looks good. could you elaborate how routed network API is used to store the external network infomation in segments? 01:05:39 ok, no problem 01:06:34 fine, then you can start coding 01:06:48 ok 01:08:17 for the port deletion patch, I see CI fails 01:09:37 pep8 failed 01:09:39 looking at the log, I guess that's because the handle function mistakenly processes "shadow port" 01:11:10 just have to review 01:11:45 the "device_owner" of "shadow port" is "compute:shadow", so "_delete_bottom_unbond_port" will also process it 01:13:18 shadow ports will exist across regions, we don't need to delete it 01:13:32 they are deleted when the central port is deleted 01:15:20 i got it 01:17:59 hello, everyone~ 01:18:07 hi jintao 01:18:19 hello 01:18:55 I am dealing with this problem 01:19:25 'oslo.config and oslo.service have implemented basic functions' 01:19:57 but Tricircle have not used these functions 01:20:22 so I want to bring these functions to Tricircle 01:21:07 so ,what can I get more information about it 01:21:59 and which part of source code I should concentrate on ? 01:22:26 the goal is to make tricircle api and xmanager support configuration dynamical loading 01:22:54 it is the bp enable mutable configuration in rocky? 01:23:09 yes 01:23:22 good 01:23:34 I would like do it with zhujintao student. 01:23:48 i have see the rocky blueprint plan and i want to do the enable mutable configuration. 01:23:48 i think we have miss two bps which are in q but have not yet finished . we should also add they to the r. how about it? 01:23:48 the miss two bps are Service function chaining and Driver-based implementation of Trunk 01:24:58 oh, please add them in the ethpad page 01:25:10 so you will co-work with jintao? 01:25:20 thanks I will add they after meeting. 01:25:23 yes. 01:25:33 ok~ 01:26:47 so we can also add the bps which are in developing to lanuchpad? 01:28:55 if you would like to take it, register the feature in launchpad 01:29:47 yes, I would like to do it.and which we register in the launchpad will promise to finished. 01:30:23 Has the work item port deletion in rokcy commited by xiaohan? 01:30:50 yes,he is working no it now. 01:31:58 sorry s/no/on 01:32:05 https://docs.openstack.org/oslo.service/latest/reference/service.html 01:32:39 i see both ProcessLauncher and ServiceLauncher have handle_signal() function 01:33:14 i think this can be used to catch sighup and reload configuration 01:33:54 yes, also kill command and so on. 01:34:21 i see the ceph code used the watcher and notify. 01:34:43 when the conf change the will notify the watcher. 01:34:49 https://docs.openstack.org/oslo.config/latest/reference/mutable.html 01:35:02 and page of oslo.config 01:35:44 good.thanks for zhiyuan. we will learn the doc after the meeting. 01:36:29 thanks for your help~ 01:36:50 it is our pleasure. 01:37:53 and for tricircle code, tricircle/cmd/api.py tricircle/cmd/xjob.py are the entrypoints of api and xmanager 01:39:05 got it 01:40:52 ok, other topics? 01:41:25 no for me. 01:41:27 no from me 01:42:13 no for me 01:42:18 no from me 01:43:25 ok, then let's finish our meeting 01:43:29 #endmeeting