01:00:39 #startmeeting tricircle 01:00:40 Meeting started Wed Jun 28 01:00:39 2017 UTC and is due to finish in 60 minutes. The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot. 01:00:41 hi 01:00:42 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 01:00:44 The meeting name has been set to 'tricircle' 01:00:57 #topic rollcall 01:01:02 #info joehuang 01:01:07 #info dongfeng 01:01:08 #info Yipei 01:01:10 #info xiulin 01:01:14 #info zhiyuan 01:01:19 #info xuzhuang 01:02:14 #topic feature implementation review 01:02:31 hello, as the pike-3 is approaching 01:02:43 hello 01:02:52 good morning 01:02:53 let's review the feature wants to land in pike 01:03:05 for lbaas, already finish lbaas in one region successfully 01:03:30 great message, yipei 01:03:41 plan to configure it again to make sure it is reproducible 01:03:49 you mean the LBaaS can work with tricircle now 01:03:59 yes, in one region, it works well 01:04:20 and one central neutron, one local neutron 01:04:21 i will update spec and prepare for a guide 01:04:24 yes 01:04:42 great progress, look forward for landing the spec and code update 01:05:20 #info LBaaS work in one region scenario where Tricircle is installed 01:05:25 for async job paginate_query, in first time I use union in query, but can show status of jobs, so now I plan to use dongfeng's paginate_query in core.py 01:05:36 OK, got it. i will continue with lbaas across multi region in the meantime 01:05:50 thanks 01:05:58 sfc'create and delete can land in pike-3 01:06:05 to xuzhuang, great 01:06:24 to xiulin, welcome the feature 01:06:50 thanks 01:06:51 sorry, using union in query can't show status of jobs, so I plan to use paginate_query now 01:07:35 to yipei, have you registered BP for LBaaS 01:07:42 yes 01:07:52 the job-log table doesn't have "status" field, since all jobs in that table are considered successful 01:08:59 to zhiyuan,yes so in order to show status of job table, I giving up using union in query 01:09:29 i see 01:09:59 for routing pagination, I think it can be landed in pike3, the replacement of "cross OpenStack L2 network" can be completed in pike3 too 01:10:53 good, will review patches ASAP, but I have to leave tomorrow/Friday, will review next Monday 01:11:20 to ronghui, how about qos series patches? 01:11:50 ok, thx~ 01:12:16 is xiongqiu online? 01:12:21 will update ASAP 01:12:48 Seemingly absent 01:13:03 ok 01:13:40 I have posted the newest comment. Two main concerns: (1) try to use driver instead of plugin (2) try not to bring ML2 extension manager to central plugin 01:13:55 for the qos patches 01:14:10 ok 01:14:43 yes, qos is high priority feature, hope that it can be merged in pike-3 01:15:13 it has been postponed two milestones 01:16:23 we will try best to finish 01:17:18 RonghUI: please, it is quite important and urgent 01:17:33 got it 01:17:46 after pike-3, it'll be difficult to land big feature, we need to test the code, and make sure the quality is good 01:18:13 so if you miss the pike-3, the feature has to be postponed to next release 01:18:33 udpate not enought frequent, part3 is submitted on Jun 25, failed in all the tests, however, not updated yet 01:19:53 fine, I am sure ronghui can deal with it 01:19:57 :) 01:20:19 #topic Community wide goals, PTG and Sydney summit topics 01:20:50 hello, there are more and more people are trying to use tricircle 01:21:26 If you find any topic in the mail-list related to tricircle 01:22:07 we can reply and help new committter 01:23:05 ok, got it 01:23:15 he/she may seek for help or propose new feature / scenario or implementation discussion 01:23:59 if more and more people get on board, it'll make tricircle better and better 01:24:27 yes! 01:24:34 yes 01:24:59 if you receive someone send you message in private, you can ask him whether to discuss the topic in mail-list publicly 01:25:47 if someone send you message in private, you can ask him whether to discuss the topic in mail-list publicly 01:26:41 ok 01:26:47 there are lots of enhancement we can do to make it easy for new committer to get on board 01:26:48 it's fine 01:27:00 got it 01:27:31 for community wide goals in pike 01:28:04 there are two goals, one is python3 support 01:29:54 the other one is Control Plane API endpoints deployment via WSGI 01:30:12 we have finished these two goals, need to submit a patch 01:31:03 it should be submitted by PTL, so I'll submit the patch 01:31:23 one more thing 01:31:30 a patch to declare we have done that? 01:31:56 yes, you have to submit a patch to update this page https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html 01:32:07 and https://governance.openstack.org/tc/goals/pike/python35.html 01:32:10 i see 01:33:25 during opnfv demo preparation, it's important to import external network to central Neutron if there is already ext-network in local neutron 01:33:56 it's especially useful if Tricricle will be running in VM or container inside some cloud 01:34:21 who can help to provide such an import function? 01:34:48 i want to have a try 01:35:25 does this need a spec, to talk about the solution? 01:35:52 by command like like python db-sync, or admin api, spec is prefered 01:36:05 it could be short, but good for discussion 01:37:08 code is not complex, how to support such management purpose function is an interesting area 01:38:10 thank you Yipei 01:38:12 lbaas in one region do not need much code, only one guide, so i would like to try 01:38:50 your contribution and guide for LBaaS is very important 01:39:20 in real production, LBaaS is a must sometimes 01:39:53 for PTG and summit, what's your idea and proposal? 01:42:25 since most of the developers are in China, we can hold PTG in China, if needed, or just discuss online 01:43:30 we may have several time slots for the discussion 01:43:49 one guy from orange is also working on tricircle 01:44:47 currently he is trying to deploy tricircle 01:45:56 and some other contributors also express the interest in contribution during OPNFV summit 01:46:28 so friendly time slot is very important for them to get involved, except mail-list 01:47:27 is our weekly meeting time convenient for them? 01:48:00 I am not sure yet, if more and more contributors from different time zone, we may rotate the weekly meeting 01:48:23 so that everyone can work with comfort time slot 01:49:39 Do you have topics for Sydney summit? 01:50:27 You can submit presentation or forum session in Sydney summit 01:51:56 If nova cellV2 is finished in Pike, we can show a demo about the integration between tricircle and cellv2 01:51:57 it's not urgent, we can continue discuss in next weekly meeting :) 01:53:10 to Zhiyuan, good idea 01:53:35 also talk with Dan Smith whether to have a session about cells V2 and tricircle 01:54:12 #topic open discussion 01:54:18 other topic? 01:54:25 no from me 01:54:29 no for me 01:54:43 no for me 01:54:47 no from me 01:54:49 no for me 01:55:24 ok, thank you for attending the weekly meeting 01:55:28 #endmeeting