14:01:09 #startmeeting tricircle 14:01:11 Meeting started Wed Mar 22 14:01:09 2017 UTC and is due to finish in 60 minutes. The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:14 The meeting name has been set to 'tricircle' 14:01:37 #topic rollcall 14:01:41 #info joehuang 14:01:51 #info zhiyuan 14:01:51 #info dongfeng 14:02:01 #info fanyishi 14:02:11 #info xiulin 14:02:17 #info ronghui 14:02:55 #info hejiawei 14:03:12 #topic Pike-1 patches review 14:04:32 for VxLAN L2 networking, there are two patches are waiting for approve 14:04:50 #link https://review.openstack.org/#/c/425131/ 14:05:10 Shared VxLAN (Part4: bridge network l3) 14:05:32 Shared VxLAN (Part5: bluk create shadow port) https://review.openstack.org/#/c/444112/ 14:06:23 and the spec is waitfing for approve too: 14:06:26 Cross-pod VxLAN network spec 14:06:31 https://review.openstack.org/#/c/429155/ 14:07:00 I would like to know if there are more comments on the way for these patches 14:07:21 I have just submitted a patch for the vxlan network doc and release notes: https://review.openstack.org/448524 14:08:11 thank you, zhiyuan, this is what we just need to have pike-1 release 14:10:39 ok, will talk to Victor after he is online if he need to do more review for the first 3 patches 14:11:29 how about other patches which target at pike-1 is still in review 14:12:39 as far as I know, QoS spec is still in review 14:14:01 there are three features: qos spec, wsgi deployment and multi-region job 14:14:22 I have voted +2 for the second and third one 14:15:07 ok, for wsgi and multi-region, need to consult victor, whether he need more time to review 14:15:56 For Qos spec, several rounds review may be needed 14:16:00 qos spec was updated this afternoon. I will check it tomorrow morning 14:16:09 good 14:17:26 thinks zhiyuan. :) 14:17:55 thank you zhiyuan 14:18:15 #topic Pike-1 release 14:19:41 consider that there are still several patches in review, and our milestone is ahead of Neutron pike-1, how about to postpone the milestone pike-1, we need to include VxLAN features 14:21:12 as tricircle is cycle-with-intermediary project 14:21:13 postpone to the end of this month? 14:21:35 it's not date based milestone, but feature based milestone 14:22:11 I think it's ok, Neutron's pike is in early of Apirl 14:23:02 It's Apr.10 ~ Apr.14 14:23:52 what's your proposal for milestone pike-1 reschedule? 14:24:33 I think the end of this month is fine. So we can have enough time to review the qos spec and my change for the doc 14:25:23 #info electrocucaracha 14:25:31 hello, victor, morning 14:25:57 hey good morning joehuang 14:26:16 morning victor 14:26:22 we are talking about whether to postpone pike-1 14:26:22 hey zhiyuan 14:26:33 consider that there are still several patches in review, and our milestone is ahead of Neutron pike-1, how about to 14:26:36 postpone the milestone pike-1, we need to include VxLAN features 14:26:42 as tricircle is cycle-with-intermediary project 14:26:53 it's not date based milestone, but feature based milestone 14:27:46 zhiyuan's proposal is " the end of this month " 14:28:23 basically all depends on reviews instead of coding right? 14:28:56 I mean, the patches has been submitted and it's only matter of doing reviews to complete them 14:28:57 yes, and also want to know do you need more time to review these patches, there 5 patches got zhiyuan's or mine +2 14:29:06 yes 14:29:25 for patches target at pike-1 14:29:29 yes, sounds reasonable 14:30:21 so let's postpone the pike-1 to Mar.31 14:30:51 and for tricircle-client, could submit a patch to make a release 14:31:18 yes, I'm going to consult to dasm how do it 14:31:29 electrocucaracha: ack. i can assist you with that 14:31:45 I know how to do that 14:31:48 one second 14:31:52 * dasm is neutron release liaison :) 14:32:16 ok 14:32:29 just like this one https://review.openstack.org/#/c/432166/ 14:32:49 princenana and sindhu are adding more UTs to the client, that will give us more stabiliy 14:32:56 submit a patch in release repository 14:33:04 ok, we can wait for that 14:33:36 after these patches are merged, then I can do the release work for tricircle-client 14:33:53 #info pike-1 postponed to Mar.31 14:34:15 #info add more UT for tricircle-client to make it more stable 14:34:20 joehuang: fyi. pie1 is Apr 10-Apr 14 14:34:25 https://releases.openstack.org/pike/schedule.html 14:34:27 *pike1 14:34:55 so, you're not even postponing, but you're planning to release it earlier 14:35:14 yes, but tricircle released a little early, should we make it being aligned to Neutron 14:35:19 joehuang: ack 14:35:45 tricircle is cycle-with-intermediary 14:35:54 but not cycle-with-milestone 14:37:07 we planned to release pike-1 tomorrow, from our plan, it's "postpone" :) 14:38:08 more comment on the release plan? 14:38:50 sorry, I missed some information 14:39:28 electrocucaracha said he can do release, and dasm can assist electrocucaracha 14:39:44 my fault, I did not catch this information 14:40:06 so, electrocucaracha, I am pleased that you can do the release work 14:40:28 joehuang: sure no problem 14:40:48 sindhu, dasm and I are in the same office 14:41:00 that's great! 14:41:42 I am so sorry that I just made a fault 14:42:13 thank you electrocucaracha and dasm, sindhu :) 14:42:52 #info electrocucaracha to release tricircle-client 14:43:28 next topic 14:43:36 #topic Demo and talk of VNF high availability across OpenStack with Tricircle in OPNFV Beijing summit 14:43:42 hello 14:44:20 for the demo, there is one video conferrence APP is recommended 14:44:37 to do the high availability across OpenStack cloud 14:45:02 with the help by Tricircle 14:45:15 joehuang: hi :) 14:45:22 hi, sindhu 14:45:29 nice to meet you here 14:45:34 joehuang: sorry for joining in late 14:46:01 always welcome 14:46:56 I will discuss with the committers in OPNFV in more detail about the demo 14:46:56 thank u :) 14:47:05 and will share information here 14:47:19 and discuss topics as needed 14:48:20 And also planned to submit a presentation in OPNFV beijing summit together with Victor 14:48:52 victor proposed to use the title ¡°Shared networks to support VNF High Availability across OpenStack Multi Region deployment¡± 14:49:12 your comments? 14:49:26 and more presentations to submit? 14:49:59 good titile 14:51:04 thank you zhiyuan 14:51:32 if no more comments, then it's time for open discussion 14:51:41 #topic open discussion 14:51:57 any other topic to be discussed 14:52:27 well, yesterday I saw a patch for removing log translations 14:52:49 apparently there is an effort from i18n team to remove that information 14:52:55 yes, it's good idea to remove log translation 14:53:00 https://review.openstack.org/#/c/448162/ 14:53:19 it's hard to do maintainnce using translated info :) 14:53:30 +1, will review that 14:53:56 and I also submitted a spec for east-west networking enhancement 14:54:02 #link https://review.openstack.org/#/c/448359/ 14:55:33 please review the enhancement, it'll make it more flexible on networking demands 14:55:52 ack 14:55:54 Shall we also create a patch to remove log translations in tricircle? 14:55:57 ok 14:56:24 already some patches submitted in tricircle for log translation 14:56:47 i see 14:57:38 ok, if no other topics, we may end the meeting 14:57:52 think you for attending the meeting 14:58:24 /s/think/thank 14:58:29 fyi, we won't be able to attend the summit 14:58:36 :'( 14:58:47 electrocucaracha, a little pity 14:59:28 I think whether I can fly to Austin to meet with you 15:00:08 that will be nice, at least you'll have the opportunity to meet all OSIC 15:00:15 yes 15:00:26 discuss offline 15:00:35 #endmeeting