13:00:57 #startmeeting tricircle 13:00:58 Meeting started Wed Feb 8 13:00:57 2017 UTC and is due to finish in 60 minutes. The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:59 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:01:02 The meeting name has been set to 'tricircle' 13:01:25 #topic rollcall 13:01:30 #info joehuang 13:01:42 #info Yipei 13:01:44 #info xiulin 13:01:50 #info dongfeng 13:02:03 #info zhiyuan 13:02:06 #info fanyishi 13:03:03 #topic Ocata release dates 13:03:40 Now only one "must to have" patch left in the review queue for Ocata release 13:04:04 #link https://review.openstack.org/#/c/424601/ 13:04:31 #info jiawei 13:04:40 after this patch get merged, we'll create a RC release and ocata branch 13:05:11 need to do regression test for features after the rc release is created 13:05:35 to verify that features basic functionalities work well 13:06:06 the branch will be created on Friday 13:06:32 and regression test after then, to Feb.15 13:06:57 Ocata release on Feb.16 13:07:49 3 days for regression test, all urgent bugs, please report and submit patch, and contact me and zhiyuan for fast review and approvement 13:08:25 we'll stay in the IRC channel to close urgent fix AFAP. 13:08:54 Every one who submitted features need to test his own feature 13:09:04 to make sure the function work 13:09:17 Any question? 13:09:33 no 13:09:43 no 13:09:46 no 13:09:49 For example, for routing feature 13:09:53 no 13:10:03 need to verify the routing api work well 13:10:17 basic functionalities 13:10:36 no need to test all scenarios 13:11:19 especially for abnormal scenarios, you may have no enough time to simulate the condition 13:11:51 ok, if no other question, we'll create Ocata branch once the patch get merged 13:12:22 then I'll send messgae in IRC channel to start the regression test 13:13:04 #info Ocata branch this Friday or early 13:13:28 #info after then, start regression test until Feb.15 13:13:42 #info formal Ocata release Feb.16 13:14:32 #info stay in tough in IRC to make fast response to any bug in your feature (if there) 13:14:46 ok 13:15:08 Hello, xiongqiu and Jiawei, do you have any question? 13:15:57 seems that his network broken 13:16:23 #topic Pike meetup before PTG 13:17:04 hello, the PTG will be held Feb.20~Feb.24 at Atalanta 13:17:38 Zhiyuan will be the representative from Huawei 13:18:00 is there any other one will go to Atalanta? 13:19:05 no for members of HUST 13:20:12 ok, I remembered that we'd plan to have a meetup for those who can't go to Atalanta 13:20:50 so how about next Friday (Feb.17) at Shenzhen, Huawei Industrial Base 13:21:02 no question, I am reading document to learn to developer network 13:21:18 thany you joe, happy new year 13:21:27 welcome jiawei 13:22:34 Is it feasible for you to have a meetup at Shenzhen 13:22:57 next Friday, the day after the release date 13:24:16 dongfeng and I will attend the meeting in Shenzhen 13:24:18 I I'm afraid I can't come 13:24:27 ok 13:26:07 so let's hold a meetup next Friday to discuss features implementation for Pike 13:27:26 #info Pike meetup on next Friday(Feb.17) at Huawei Industrial Base, Shenzhen 13:28:18 #info meetup etherpad: https://etherpad.openstack.org/p/tricircle-pike-design-topics 13:28:27 I will told ronghui 13:29:11 so please prepare your topics and what need to discuss, then let's discuss f2f 13:29:33 to Jiawei, thanks 13:30:26 #topic need help from PTG 13:30:46 hello, Zhiyuan will go to Atalanta for the PTG 13:31:31 what topic do you want to discuss in PTG? Zhiyuan may help you on this 13:31:50 as our project's representative 13:32:47 hi, how long will the f2f gathering last in shenzhen? 13:33:00 do you have any challenge need to address by other projects? 13:34:06 from 9:00am to 4:00pm 13:34:32 what's your suggestion? 13:38:37 if no other proposal, it's fine to work on this time slot 13:39:02 #topic open discussion 13:39:10 any topics? 13:39:25 yes 13:39:38 please, Yipei 13:39:48 i do some investigation on allowed address pair 13:40:11 and update the topic in https://etherpad.openstack.org/p/tricircle-pike-design-topics 13:41:39 Great 13:41:52 no need to sync the info of the port across OpenStacks 13:42:30 To support load balancing in tricircle in one region, enable allowed address pair in local neutron may work. 13:43:20 how about the loadbalance in RegionOne, but the member in RegionTwo 13:44:11 In respect of balancing load among members across OpenStacks, i will do more investigation on the scheme of adding members. 13:44:12 LB(RegionOne) and the member(RegionTwo) in same network, or in different network 13:44:49 thank you, same thoughts 13:45:17 please go on your investigation, and let's discuss more next week 13:45:23 ok 13:45:32 for extra-routes 13:46:59 is it related to the external router? 13:47:00 extra-routes is from the concerns if LB and member is not in same network, and in different OpenStack 13:47:30 i see, i will go on investigation on the scheme of adding members 13:47:52 You can run Ocatavia and Tricircle now? 13:48:32 no, the reason is the local neutron does not support allowed address pair 13:48:36 of only Ocatavia, without Tricircle 13:48:44 I see 13:48:50 of only octavia, it works 13:49:21 Good 13:49:48 other topic? 13:50:00 no for me now 13:50:05 no from me 13:50:10 Please review the patch for VxLAN L2 networking 13:50:10 no for me 13:50:13 no for me 13:50:44 https://review.openstack.org/#/c/429155/ 13:50:53 thanks for attending the meeting 13:51:05 #endmeeting