01:01:04 #startmeeting tricircle 01:01:05 Meeting started Wed Nov 1 01:01:04 2017 UTC and is due to finish in 60 minutes. The chair is zhiyuan. Information about MeetBot at http://wiki.debian.org/MeetBot. 01:01:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 01:01:08 The meeting name has been set to 'tricircle' 01:01:33 #feature progress 01:01:45 #topic feature progress 01:02:11 let's update our progress of feature development 01:02:57 hello 01:03:03 hi joe 01:03:23 for lbaas, already installed tricircle with nova cell, try integrating lbaas with nova cell. 01:03:52 improve smoke test to adapt the newly added attribute "enable_tap" 01:05:02 improve patch https://review.openstack.org/#/c/498407/ and https://review.openstack.org/#/c/511667/ based on the comments 01:05:55 for default security group the patch is still under reviewing. for the direction of requests bettween central neutron and local neutron I am thinking the technical scheme 01:08:23 for the cell lbaas integration, each lbaas service will connect to one cell, is that correct? 01:09:11 to zhiyuan, yes 01:09:21 for cells integration, only one LBaaS? 01:09:41 I tested and found the patch for default security group worked well, I only have one little comment on the unit test 01:10:59 we need a spec for LBaaS and cells integration, though code development may be just a little 01:12:16 to joehuang, i will prepare a spec. i just plan to verify the idea we discussed, and then will submit a spec 01:12:27 perfect 01:13:04 to xuzhuang, is my reply in the mail clear for you? 01:13:36 may we use openstack maillist to discuss some topic 01:13:39 hello 01:13:50 sorry for late 01:14:22 hi, i am song from szzt, is there any small work and not very hurry we can do. 01:15:43 i have understanded the global plan, but still have a little problems 01:16:25 to joehuang, what kind of topic? 01:16:51 I did not see the mail zhiyuan sent to xuzhuang 01:17:55 ah, yes, the mail is sent to my personal mail address 01:18:19 oh, sorry joe, i sended to zhiyuan and yipei for asking the plan of direction of requests 01:19:42 joe's suggestion is that we can discuss such implementation detail in openstack mail-list, with tricircle in the subject 01:20:12 ok, I got it 01:20:14 to song, what about the improvement of trunk smoke test? 01:20:58 it has worked by our team zhang xiaohan. 01:21:37 if we continue to work on the smoke test for some other functions. there is some spec for learn ? 01:21:47 trunk somke test is under working. 01:22:09 or some test case we should test? 01:23:34 one feature targeting queens-2 is network deletion reliability 01:24:01 and security group deletion depends on it 01:26:45 song, is this feature already taken by your team? 01:27:22 my team taken qos and trunk somke test 01:27:33 we have not taken it. 01:28:16 we can do it, if it is not very hard and hurry. 01:29:06 queens-2 is from Dec 4 to Dec 8 so it'll be about a month 01:31:09 there's already some ideas during the PTG, https://etherpad.openstack.org/p/tricircle-queens-ptg, but we need a spec to discuss the detail 01:31:32 see the "Network deletion reliability" section 01:31:38 oh,we can try do it. 01:32:11 last time we discuss this function and seems not find a good way to solve this problem 01:33:08 sorry, another meeting is waiting for me, I have to leave early. 01:33:15 bye 01:33:17 bye 01:33:20 record the operation state in memory is not enough, so we may need to store the state in DB 01:33:23 bye joe 01:33:45 bye joe 01:33:54 bye joe 01:35:07 the basic idea is to store a "network-in-delete" state at the beginning of network deletion, so during the deletion, if one "network-get" request comes, we can return 404 01:35:39 ok 01:36:10 good 01:37:31 in the spec, we need to enumerate the cocurrent request scenarios, and see if our solution can handle each 01:39:20 if it do not have the good solution may be queues-2 is hurry for this feature. 01:41:36 we need to find a good way to solve the conflict 01:42:20 yes, it may take some time to reach the solution 01:43:43 we can try to finish the spec in queens-2 01:44:03 ok, we try our best to do it. 01:44:26 we will write a doc and send a email.if we have good solution. 01:44:37 to see other people have any other idea. 01:44:47 after that we begin to coding. 01:45:06 fine, discuss via the mail list, as Joe suggest 01:45:25 yes 01:45:28 i think the best way came from experiment 01:46:37 yes, the issue for network deletion is easy to reproduce 01:47:00 so it's easy for us to test some solutions 01:47:43 no experiment, if some other conflict come out, it is hard to fix the spec and submit codes 01:50:30 that's right 01:50:49 other topics? 01:50:56 no 01:51:00 no for me 01:51:04 no for me 01:51:47 no 01:52:04 ok, thanks for attending the meeting 01:52:09 #endmeeting