13:00:54 <joehuang> #startmeeting tricircle
13:00:56 <openstack> Meeting started Wed Nov 23 13:00:54 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:57 <longxiongqiu> hello
13:00:58 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:01:00 <openstack> The meeting name has been set to 'tricircle'
13:01:07 <liukun> #hello
13:01:08 <joehuang> #topic rollcall
13:01:09 <yinxiulin> hello
13:01:13 <joehuang> #info joehuang
13:01:19 <RongHui11> #info ronghui
13:01:23 <zhiyuan> #info zhiyuan
13:01:24 <longxiongqiu> #info longxiongqiu
13:01:24 <yinxiulin> #info xiulin
13:01:28 <Yipei> #info Yipei
13:02:09 <dongfeng> #info dongfeng
13:02:16 <hejiawei> #info jiawei
13:02:18 <joehuang> #topic Ocata feature development review
13:03:02 <joehuang> let's have a short review for the feature development, the coming milestone is in the middle of Dec
13:03:34 <joehuang> please have a brief description of the feature you are working for
13:04:49 <dongfeng> the patch for documentation for resource routing is in review, and the blueprint for resource routing is also in review.
13:05:33 <zhiyuan> (1) the manual installation guide is under review. (2) the spec for combined bridge network is under review (3) the code for combined bridge network is under development, I will start to test the code with DevStack tomorrow
13:05:37 <joehuang> to Dongfeng, yes, just receive the notification of the blueprint
13:06:36 <RongHui11> for the configuraton i still try to use the document tools to get the configuraton guide
13:06:42 <joehuang> is there anyone install tricircle according to the manual
13:07:25 <RongHui11> i install the tircircle according th the manual for singlenode
13:08:02 <RongHui11> sorry
13:08:15 <RongHui11> not the manual
13:08:21 <RongHui11> is the devstack
13:09:38 <joehuang> you can install the devstack without tricircle first, then try to configure the tricircle according to the manual guide
13:09:49 <joehuang> hello Junsik, not see you some time
13:10:24 <RongHui11> ok
13:10:29 <RongHui11> i will try it
13:10:38 <joehuang> to Zhiyuan, thank you for your great effort
13:10:45 <Yipei> implement LBaaS for tricircle, still studying LBaaS. plan to run LBaaS in one OpenStack instance.
13:10:47 <joehuang> thank you, ronghui
13:11:03 <joehuang> to yipei, great
13:11:20 <joehuang> LBaaS is applying openstack bigtent
13:11:35 <Yipei> will try installing devstack tomorrow by following the manual
13:11:37 <joehuang> the project name is Ocataiva
13:12:36 <Yipei> ok, i will pay more attention to the project
13:13:26 <joehuang> you can refer to this guide: http://docs.openstack.org/mitaka/networking-guide/config-lbaas.html
13:13:54 <joehuang> this is mitaka version, you'd better to read the newton release
13:14:08 <Yipei> ok, got it. thx for sharing
13:14:30 <yinxiulin> I am learning tricircle design documents. plan to start resource update function next week
13:15:21 <joehuang> you can discuss any questions in mail-list or irc
13:15:56 <joehuang> Hello, there are several patches in review
13:16:28 <joehuang> I hope that everyone can spend some time to review other's patch
13:17:15 <joehuang> you can have more broad knowledge on what's being developed, and improve the quality of each patch
13:18:36 <dongfeng> ok.
13:18:40 <Yipei> ok, got it
13:18:45 <zhiyuan> sure
13:18:56 <Junsik> ok
13:19:07 <RongHui11> ok
13:19:11 <hejiawei> ok
13:19:38 <joehuang> thank you all, we are a team, team work can make everything better
13:19:53 <joehuang> #topic Py35, Ubuntu Xenial gate and check jobs
13:21:30 <joehuang> according to community requirement
13:21:51 <joehuang> all project needs to adapt to pyhon3
13:22:40 <joehuang> and tested in ubuntu xenial release
13:23:16 <joehuang> #link https://review.openstack.org/#/c/400493/1/jenkins/jobs/projects.yaml
13:23:39 <zhiyuan> to support python 3, we need to use "six" library in the list and dict traverse
13:24:29 <joehuang> after the jobs enabled, two more jobs will be added in the gate and check test, but at first it's not voting job, that means it's ok if it failed
13:24:41 <joehuang> to zhiyuan, yes, some update is needed
13:25:46 <zhiyuan> when will the two jobs become voting job?
13:26:05 <joehuang> we needs to fix the error in the failure job step by step, at last in this release, we should be able to migrate to python3 and xenial
13:26:13 <joehuang> no, non-voting jobs
13:27:05 <joehuang> after all failure are fixed, I hope by the end of Ocata release
13:27:23 <joehuang> the earlier, the better
13:27:30 <joehuang> the sooner, the better
13:28:04 <joehuang> it'll take one week or so to enable these jobs
13:28:37 <joehuang> and one more job doc-publisher-site: docs.openstack.org is also added
13:28:43 <zhiyuan> i think we just enable the jobs then we know what error needs to be fixed
13:29:26 <joehuang> that means all docs of tricircle will be published to docs.openstack.org website
13:30:20 <joehuang> the jobs will report failure, but will not block any patch's merge
13:32:06 <zhiyuan> so if the doc job fails, the doc will not be updated in the website?
13:32:30 <joehuang> it's better if someone of us can install tricircle under python35, and execute the pep8/unit/functest to see what error occured
13:32:59 <joehuang> yes
13:34:16 <joehuang> infra team always suggest to enable a job as non-voting at first, after it's stable for the job, then make it as voting job
13:35:14 <joehuang> currently our doc test is successfully for each patch
13:35:51 <zhiyuan> we can use virtualenv to setup a python3 environment
13:36:22 <joehuang> But it's strange that all jobs are already ubuntu-xenial based
13:36:53 <joehuang> for example https://review.openstack.org/#/c/396564/, I am not sure whether we need to enable special job for xenial
13:37:18 <joehuang> yes, venv is a good way to try python3
13:37:28 <joehuang> or container
13:38:19 <zhiyuan> i think our test is already runnint on xenial, we just need to enable python3 test
13:38:49 <joehuang> will consult that in infra team
13:39:22 <joehuang> #action consult infra team whether tricircle needs to enable special xenial jobs or alreay support that
13:40:58 <joehuang> #topic open discussion
13:41:09 <joehuang> any topic to discuss?
13:41:45 <zhiyuan> for me, there may be risk to support shared vxlan network in this circle
13:41:45 <RongHui11> no for me
13:42:25 <zhiyuan> if we are going to follow the "vtep info in port" change in neutron
13:43:40 <joehuang> to zhiyuan, understand the risk
13:44:02 <joehuang> we need to work closely with anil for this feature
13:44:18 <joehuang> at the same time, enhance Tricircle basic capabilities
13:44:41 <joehuang> for example, qos, update operation, metering, etc
13:45:07 <joehuang> do you have other proposal to reduce the risk?
13:45:22 <joehuang> or bypass the risk?
13:47:29 <zhiyuan> there's other solution to support shared vxlan network, like the "remote port" way, but if we would like to use the "vtep info in port" feature, it will be a waste to implement "remote port" in this circle
13:50:07 <joehuang> we can discuss if it's possible, or how to reduce the waste, at least we need to know how Anil will implement the VTEP info in port bindings
13:51:33 <zhiyuan> ok, so let's keep our eye on Anil's work
13:52:00 <zhiyuan> at least we can finish the bridge network combination change
13:52:05 <joehuang> sure
13:52:31 <joehuang> actively involve in Anil's improvement
13:52:38 <joehuang> if necessary
13:53:11 <joehuang> ok, other topics?
13:53:18 <zhiyuan> no
13:53:28 <dongfeng> no
13:53:30 <Yipei> no
13:53:31 <RongHui11> no
13:53:32 <Junsik> no
13:53:42 <joehuang> ok, thank you for your attending
13:53:49 <joehuang> #endmeeting