01:01:28 #startmeeting tricircle 01:01:29 Meeting started Wed May 24 01:01:28 2017 UTC and is due to finish in 60 minutes. The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot. 01:01:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 01:01:32 The meeting name has been set to 'tricircle' 01:01:37 hi 01:01:47 #topic rollcall 01:01:54 #info joehuang 01:02:00 #info dongfeng 01:02:24 #info zhiyuan 01:02:27 #info xiulin 01:02:39 #info Yipei 01:03:15 #topic feature implementation review 01:04:24 hello, we have a break on the weekly meeting two weeks for boston summit and bugsmash 01:04:28 let 01:04:51 please has a short description about your feature implementation 01:05:07 I am implementing sfc function 01:05:24 already submint a patch for create and delete 01:05:39 I prepare to implement routing pagination. still read neutron pagination source code. 01:05:50 ok 01:06:20 to Dongfeng, I think it's also good to implement the routing cli in python-tricircleclient 01:06:41 sorry, async job cli 01:06:48 instead 01:07:11 I recall that async job api was implemented, but cli is lack yet 01:07:20 use command line to call async job api? 01:08:11 you can refer to pod routing cli implementation in python-tricircleclcient 01:08:20 both SDK and cli 01:08:36 https://github.com/openstack/python-tricircleclient 01:08:39 ok. I'll have a try 01:08:53 for lbaas, already reinstalled the octavia with tricircle, plan to test lbaas in the new env. and check whether the amphora reboot happens 01:09:44 There are some patches to implement pod routing cli, you can refer to https://review.openstack.org/#/q/project:openstack/python-tricircleclient 01:10:11 ok, look forward to the news of lbaas 01:10:52 ok 01:11:14 to joe, thanks, I'll refer to those patch and try to implement async job cli. 01:11:40 there are several bugs and feature to be implemented during OPNFV demo preparation, zhiyuan, could you have a summary of the bugs not fixed? 01:12:33 during the opnfv demo preparation, cli to fix abnormal async job is very helpful 01:13:04 We found four bugs during the demo setup and two of them have been fixed in the bugsmash 01:13:40 the two left are "Local FIP not created after central FIP creation" and "Bridge network segment ID conflicts with local network's" 01:14:03 here are the bug links: https://bugs.launchpad.net/tricircle/+bug/1691918 and https://bugs.launchpad.net/tricircle/+bug/1692415 01:14:04 Launchpad bug 1691918 in Tricircle "Local FIP not created after central FIP creation" [Undecided,New] 01:14:05 Launchpad bug 1692415 in Tricircle "Bridge network segment ID conflicts with local network's" [Undecided,New] 01:14:28 #info two bugs left are "Local FIP not created after central FIP creation" and "Bridge network segment ID conflicts with local network's" 01:14:59 great, hope this bug fix can be landed in Pike2 01:15:30 btw, what's the time of pike2? 01:16:50 yes, before the fix, we need to (1) create a FIP then update it to associate with port (2) instead of creating local type network, try creating a flat/vxlan/vlan type network and specifying the AZ as region name 01:22:30 according to the schedule, pike-2 is from Jun 05 to Jun 09 01:23:08 we 'll release on Jun 09 01:24:28 ok. got it 01:25:31 #topic Pike-2 preparation 01:25:56 as what we just discussed, we'd like to release the pike-2 on Jun 9 01:26:16 so would like to see if there is any challenges 01:27:54 routing pagination needs more time, 01:27:55 don't own any feature task so it's fine for me :) 01:29:13 no challenges currently, but i might encounter some problems and need your help. 01:30:52 Should metering complete before Jun 9? 01:30:55 QoS will be a challenge to land on pike-2 01:31:04 the spec is still in review 01:31:14 and code update is not so frequently 01:31:48 for metering, the spec is also in review 01:32:01 if you want to land early, please update in time too 01:32:25 ok 01:32:34 got it 01:33:34 #topic open discussion 01:34:04 any other topic? 01:34:08 for pagination, dose it need reverse shown feature? 01:34:33 what do you mean "reverse"? 01:35:16 after one page is listed, then list the previous page rather than next page 01:39:45 need to check nova api server list and neutron port list 01:40:37 ok. 01:40:53 neutron api support reverse 01:41:01 for nova, seems no reverse 01:41:12 yes. nova has no reverse 01:41:12 only maker for next 01:41:21 https://developer.openstack.org/api-ref/networking/v2/#pagination 01:42:46 ok, nuetron seems do it better than nova in query support 01:43:14 so follow neutron pagination 01:43:33 got it~ 01:43:51 now no other topic for me 01:44:44 other topic? 01:45:27 no for me 01:45:37 no 01:45:38 no for me 01:46:00 ok, let's end the meeting 01:46:05 #endmeeting