14:00:51 <joehuang> #startmeeting tricircle
14:00:51 <openstack> Meeting started Wed Mar 29 14:00:51 2017 UTC and is due to finish in 60 minutes.  The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:52 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:55 <openstack> The meeting name has been set to 'tricircle'
14:01:05 <joehuang> #topic rollcall
14:01:09 <joehuang> #info joehuang
14:01:14 <hejiawei_> #info hejiawei
14:01:21 <dongfeng> #info dongfeng
14:01:29 <zhiyuan> #info zhiyuan
14:01:58 <yinxiulin> #info xiulin
14:03:07 <joehuang> #topic Pike-1 prioritized patches
14:04:12 <joehuang> hello, several prioritized patches for pike-1 were sent in the mail-list
14:04:46 <joehuang> according to our plan, we'd like to make these patches being merged into pike-1
14:04:48 <electrocucaracha> o/
14:05:11 <joehuang> hi, electrocucaracha
14:05:34 <electrocucaracha> hey joehuang , go ahead with the meeting sorry for the interruption
14:05:38 <joehuang> would like to know if more comments on the way for these patches
14:05:53 <joehuang> thanks
14:06:01 <joehuang> the first one is Add multi-region configuration in gate_hook.sh: https://review.openstack.org/#/c/438382/
14:06:28 <zhiyuan> I left one comment in the QoS spec patch
14:06:30 <joehuang> this is to setup the multi-region test environment
14:06:50 <Yipei> #info Yipei
14:07:14 <joehuang> to zhiyuan, ok.
14:07:39 <joehuang> 2.  Cross-pod VxLAN network spec: https://review.openstack.org/#/c/429155/
14:08:12 <joehuang> the spec for cross pod vxlan network had been reviewed many rounds
14:09:00 <joehuang> 3. Shared VxLAN (Part4: bridge network l3) : https://review.openstack.org/#/c/425131/
14:09:17 <joehuang> 4. Shared VxLAN (Part5: bulk create shadow port): https://review.openstack.org/#/c/444112/
14:09:40 <joehuang> 3 & 4 are two patches for vxlan network
14:10:03 <joehuang> 5.  Update doc and add release note for vxlan: https://review.openstack.org/#/c/448524/
14:10:29 <joehuang> the fifth is about documentation delivered for VxAN network
14:10:54 <joehuang> WSGI deployments has been merged
14:11:28 <joehuang> these five patches are must to have in pike-1
14:12:13 <joehuang> would like to know are you reviewing these patches, or have finished the review
14:12:46 <zhiyuan> qos spec is not targeted in pike-1?
14:13:23 <joehuang> QoS spec is "nice to have"
14:13:32 <zhiyuan> ok
14:13:51 <joehuang> and another patch is also nice to have  Update networking-guide-single-external-network: https://review.openstack.org/#/c/446883/
14:14:04 <joehuang> Networking Qos service spec£º https://review.openstack.org/#/c/417947/
14:14:20 <joehuang> these two are "nice to have" patches
14:17:05 <joehuang> ok, if there is no more comments on the way for these patches, we'd like to approve these patches
14:17:45 <joehuang> so please review as much as possible
14:18:23 <joehuang> to victor, only one patch left for tricircle-pythonclient to release, isn't it?
14:21:48 <electrocucaracha> yeah, we can add other unit test later
14:22:04 <electrocucaracha> sorry, the delete portion is missing
14:22:11 <electrocucaracha> deleting pods
14:22:29 <electrocucaracha> but that can be easily done
14:22:56 <joehuang> sorry, my link was broken
14:23:26 <joehuang> hello?
14:23:30 <hejiawei_> hi
14:23:37 <joehuang> ok, it works now
14:24:34 <electrocucaracha> I'm going to check with sindhu about here patch https://review.openstack.org/#/c/448819/
14:24:46 <electrocucaracha> she only need to rebase it
14:25:08 <joehuang> ok, thank you, electrocucaracha. yes, only rebase is needed
14:25:23 <joehuang> sorry, for the unstable link
14:26:01 <joehuang> #topic Requirements from  VNF high availability across OpenStack (which will be a demo in OPNFV Beijing Summit)
14:26:11 <sindhu> hi, yes rebasing now :)
14:26:23 <joehuang> hi, sindhu, thank you very much!
14:27:13 <joehuang> in OPNFV, a requirement for multiple external-network with east-west enabled networking mode
14:27:56 <joehuang> #link https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-March/015728.html
14:28:16 <joehuang> fortunately there is exactly one spec for this requirements
14:28:41 <joehuang> #link  https://review.openstack.org/#/c/448359/3/specs/pike/l3-networking-multi-NS-with-EW-enabled.rst
14:29:10 <joehuang> and explanation for why the topology varied a little
14:29:22 <joehuang> #link https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-March/015747.html
14:29:49 <joehuang> it seems this a quite typical networking topology
14:30:12 <joehuang> even for another application, video conference
14:30:41 <joehuang> on the other hand, during the demo preparation
14:31:11 <joehuang> it's also necessary to support flat type of external network
14:32:18 <zhiyuan> patch for flat network support: https://review.openstack.org/#/c/450061/
14:32:22 <joehuang> and once again, fortunately enough, zhiyuan submitted a patch for flat type of network support
14:32:44 <zhiyuan> just sent the link :)
14:32:50 <joehuang> yes, just want to point out this. you guy reads my mind
14:34:32 <joehuang> with these patches help, it's good enough to support typical VNF high availability across OpenStack
14:35:40 <joehuang> so may be we can set a small step for next milestone, but no need to align with community level pike-2, if we want to use it in OPNFV
14:35:56 <joehuang> what's your proposal?
14:37:24 <zhiyuan> when is the summit?
14:37:39 <joehuang> in Jun 15~
14:38:38 <joehuang> community's pike-2 is jun-9
14:41:02 <zhiyuan> how about just using te community pike-2? it's before jun-15. you would like to set a earlier milestone before pike-2 because the preparation for the summit demo?
14:42:13 <joehuang> we need some time to prepare summit PoC, currently CMCC is working with us on the PoC, not sure Orange will join or not
14:43:47 <joehuang> we can think about the milestone plan and the features to be prioritized in milestone 2
14:43:50 <zhiyuan> is one month enough?
14:44:13 <joehuang> I think so
14:44:52 <joehuang> the longer preparation, the better
14:45:15 <electrocucaracha> +1
14:45:37 <joehuang> we can think about if offline, and continue the detail plan and content for pike-2 in next weekly meeting
14:46:43 <zhiyuan> ok
14:47:28 <joehuang> to electrocucaracha, after the client is released, there two steps to make it being integrated in tricircle
14:47:44 <joehuang> one is to add it into global requirements
14:48:14 <joehuang> the other one is to update tricircle's requirements.txt
14:49:12 <electrocucaracha> ack
14:49:38 <joehuang> these two steps can be done after release
14:49:46 <joehuang> not so urgent :)
14:50:28 <joehuang> #open discussion
14:50:39 <joehuang> #topic open discussion
14:51:31 <joehuang> hello, there is one patch in review by TCs
14:52:07 <joehuang> which may give tricircle a tag "single vendor"
14:52:09 <joehuang> https://review.openstack.org/#/c/448667/
14:52:36 <joehuang> the criteria is that if the review from one company > 50%
14:53:11 <joehuang> we have diversity contributors
14:53:48 <joehuang> more review from all of us and more contributors are encouraged
14:55:19 <joehuang> and recruit those who are interested in tricircle as much as possible
14:55:45 <joehuang> how can we improve the diversity?
14:56:49 <electrocucaracha> good question, maybe blogging
14:57:18 <joehuang> #info blogging to have more contribtors on board
14:58:06 <joehuang> and more?
14:58:40 <joehuang> we have on board session in Boston summit
14:58:57 <joehuang> this may be one more opportunity
14:59:31 <joehuang> ok, time is up
14:59:40 <joehuang> we have to end today's meeting
14:59:50 <joehuang> let's think about it offline
15:00:10 <joehuang> thank you for attending today's meeting
15:00:19 <joehuang> #endmeeting