13:00:45 #startmeeting tricircle 13:00:47 Meeting started Wed May 11 13:00:45 2016 UTC and is due to finish in 60 minutes. The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:48 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:00:50 The meeting name has been set to 'tricircle' 13:01:04 hello 13:01:12 #topic rollcall 13:01:23 #info joehuang 13:01:27 #info Ronghui 13:01:35 #info Yipei 13:01:49 #info zhiyuan 13:02:25 #topic L2 networking 13:03:13 please wait for Xiongqiu 13:03:17 we have several round review and spec update 13:03:19 ok 13:04:06 he is comming 13:04:13 hi 13:04:17 sorry 13:04:23 i forgot it 13:04:36 welcome 13:05:06 just found that the spec is updated 13:05:08 he is trying to solove the problem of patch 13:05:17 ok 13:06:01 would like to know whether there is somethine still not clear 13:06:13 in cross pod L2 networking 13:07:33 #link https://review.openstack.org/#/c/304540/9/specs/cross-pod-l2-networking.rst 13:08:34 we are trying to write some simple test and it will help us to understanding quickly 13:08:34 i will try to write shared VLAN and local network 13:09:24 great, good to start from test cases 13:09:48 :), i will. 13:10:11 shared VLAN and local network are easy to get onboard 13:10:37 #info start from test cases, and shared VLAN, local network 13:11:18 the commit message seems will lead to some comments 13:11:49 if you remember that fengpan has already comment on this description 13:12:35 i forget the format of commit 13:12:56 so update the spec for 4 times. sorry 13:13:43 it's not unusaual :) 13:13:52 https://review.openstack.org/#/c/304540/5/specs/cross-pod-l2-networking.rst 13:15:06 I suggest you update the commit message to stress on no cross OpenStack L2 networking automation yet 13:15:33 ok 13:15:48 I found some trailing space in the spec 13:16:22 i will update as soon as possible 13:17:05 I have one idea on the development of cross pod L2 networking feature 13:17:48 how about to have a work group, just like DVR feature developed in Neutron 13:18:18 a work group? what does it mean? 13:19:18 several engineers working on the same big feature, just like DVR and cross pod L2 networking 13:19:20 u mean create a network group just that service for work group 13:20:07 it's a virtual team 13:20:21 virtual sub-team 13:20:30 more exactly 13:20:49 how it works? 13:22:21 more frequent discussion inside the sub-team, and one sub-team leader to lead the development 13:23:07 my net is unstable 13:23:23 understand 13:24:12 members in work group still discuss in #openstack-tricircle? 13:24:18 yes 13:25:06 and daily regular meeting inside the sub-team 13:25:20 to discuss what's the challenge, how to solve it 13:25:45 i see. do we need to publish the discussion in #openstack-tricircle? 13:26:04 it sounds good 13:26:11 it's encouraged to do so, we are open community 13:27:09 not sure if we can config #openstack-tricircle to use meeting-robot 13:27:10 yes, weekly meeting is too long to wait for feature development 13:27:32 understanding your concerns 13:27:49 the idea of running work group is greate 13:28:00 s/greate/great 13:28:04 or use etherpad for persistence 13:28:38 i prefer etherpad :) 13:28:45 etherpad also support online chat 13:29:03 we can discuss the network featrue step by step in work group 13:29:40 prefer etherpad 13:29:44 of course, if the team discuss in daily basis 13:29:45 agree with zhiyuan 13:30:18 #info to setup a working group( virtual sub-team ) for cross pod L2 networking 13:30:23 etherpad is good for me,xchat is unstable 13:30:29 etherpad+1 13:31:00 same situation for me 13:31:01 #info use etherpad for daily meeting, time is suggested not to longer than one hour 13:31:56 how to get informed? through mail or channel #openstack-tricircle? 13:32:02 send a mail to schedule a time? 13:32:08 I would recommend Zhiyuan as the virtual sub-team leader for the cross pod L2 networking 13:32:20 ok 13:32:22 yes, publish it in the maillist 13:32:22 great 13:32:23 +1 13:32:23 not all members are in the meeting currently 13:32:37 and the sub-team is also open 13:32:51 if you want to submit patch for cross pod L2 networking 13:33:18 than just join the sub-team daily meeting, and work on patch, and discuss 13:33:36 i am going to attend OSCON next week so it may impact the daily meeting 13:33:59 we don't close the door for others to contribute 13:34:18 it's ok, you are free to set the schedule 13:35:21 if nothing to discuss, you can close the meeting quickly, may be one second 13:36:22 #info Zhiyuan as the virtual sub-team leader of cross pod L2 networking 13:36:47 i do not understand why we need to store historical pod binding records 13:37:11 i think store current active ones is enough 13:37:15 Zhiyuan, if you feel you have no time for the meeting, you can cancel one 13:37:44 it's for histroial retrospect 13:38:09 it can be added later 13:38:34 ok, since i need some time to prepare the talk in OSCON 13:38:36 you know that in internet, everything is recorded 13:38:56 got it, i think maybe we can store then in another table 13:39:10 instead of storing them with active ones 13:39:11 to zhiyuan, no problem. You don't have to do it immediatly, it's just one idea to run this feature 13:39:22 when is the record deleted? 13:39:48 for deleted record, only tag is marked, the record is still there 13:40:23 i see 13:40:46 to Yipei, it could be like that 13:41:10 it would be better to record start time and end time 13:41:22 ok, got it. i will take it into consideration in the future 13:42:13 ok, so for dynamic pod binding, Yipei has prepared a lot 13:44:02 i think i still need to understand more details, i will send mail to you guys for help 13:44:32 #info store historical pod binding information for retrospect, and including start, end time 13:45:14 you are active in m-l, very good 13:45:45 to zhiyuan, how many features lack to pass some basic tempest test 13:45:57 still lack 13:46:30 ... what does m-l mean? :) 13:47:10 mailing-list 13:47:30 thanks 13:47:31 to pass server-create test, we need to improve server controller to support more parameters like admin-pass, key-pair 13:47:56 and server-group which i am working on 13:48:27 seems a lot of work 13:48:35 we also lack many server action operation 13:48:58 I can try to fix some server actions 13:49:07 and volume actions 13:50:06 ok any other topics? 13:50:35 so let's end the meeting 13:50:40 no for me 13:50:55 #endmeeting