01:01:39 #startmeeting tricircle 01:01:40 Meeting started Wed Jul 12 01:01: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:01:41 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 01:01:43 The meeting name has been set to 'tricircle' 01:01:47 hello 01:01:52 hi 01:01:54 hi 01:01:57 #topic rollcall 01:01:59 hi 01:02:02 #info joehuang 01:02:04 hi 01:02:05 #info zhiyuan 01:02:07 #info dongfeng 01:02:09 #info hejiawei 01:02:39 #info ronghui 01:02:45 #info xuzhuang 01:02:55 #topic feature implementation review 01:02:56 #info xiulin 01:03:05 #info Yipei 01:03:14 the pike-3 is approching 01:03:33 the date is july 28 01:03:53 let's have a short review for the ongoing development features 01:04:55 for me, the pagination feature for routing is under review. 01:05:11 to dongfeng, yes, almost done 01:05:27 for job pagination, paginate_query has finished, and some test cases has added, now I need to modify the code after your review 01:05:28 en, a question left there after your comment. 01:05:55 the spec for smoke test has been merged, hopefully the patches for single/multiple gateway topology test can be merged in Pike 01:07:18 for lbaas, already finish installing octavia in multiple pods, plan to test lbaas across instances of different subnets 01:07:21 @dongfeng, ok, so should we support sort filter in the api request 01:07:44 to joe, for simplicity, sort by id is more simple 01:07:56 for importing external network, already begin coding 01:08:17 to zhiyuan, smoke test landing is very important to guarantee the code quality, so it'll be put with high priority 01:08:26 the sfc's update patch is under review 01:08:31 to Yipei, great progress 01:08:47 hope LBaaS can work soon for multi-pod 01:09:06 ok, got it. i will make it 01:09:27 how do you guys think about the pagination sort key? 01:09:52 if we sort by a key, then this key will served as marker. 01:10:31 how about server pagination and port pagination? 01:10:45 currently marker is hardcoded to id. 01:11:26 what's the requirement for server pagination and port pagination? 01:12:07 I meant do you have an idea about the server pagination/port pagination to deal with sort 01:12:24 according to https://specs.openstack.org/openstack/api-wg/guidelines/pagination_filter_sort.html 01:12:42 the sort key is usually the ID of the item, but not require to 01:13:33 this page also talks about ID: https://developer.openstack.org/api-guide/compute/paginated_collections.html 01:14:18 "The ``marker`` parameter is the ID of the last item in the previous list. By default, the service sorts items by create time in descending order. When the service cannot identify a create time, it sorts items by ID.The ``marker`` parameter is the ID of the last item in the previous list. By default, the service sorts items by create time in descending order. When the service cannot identify a 01:14:24 create time, it sorts items by ID." 01:16:09 By default, the service sorts items by create time in descending order 01:16:34 for qos, xiongqiu will update it tonight. 01:17:33 for routing table, because the id is bigint, so desceding is fine 01:17:45 from latest one to the oldest one 01:18:18 sorry, from the last one to the first one 01:18:20 you mean like 4 3 2 1 ？ 01:18:56 yes, just change "asc" to "desc" 01:19:11 when you check, you often want to know the new added items 01:19:14 so, filter won't contain sorts? 01:19:25 so descending is more reasonable 01:19:48 ok, I will change sort direction. 01:21:52 currently id representation can denote creation time 01:22:43 ok 01:23:31 then I will hardcoded sort key to id. change its direction to desc. 01:24:01 for qos, the patch needs to fix the issue in gate/check test, for example pep8 01:24:45 and functional test 01:25:17 reviewers only do review if a patch passes all test 01:27:16 #topic open discussion 01:27:23 topic to discuss? 01:27:49 no for me 01:28:01 no for me 01:28:05 no 01:28:08 no 01:28:15 no for me 01:29:19 #info reviewers only do review if a patch passes all test 01:29:49 fine, let's end the meeting, and discuss in #openstack-tricicle if needed 01:29:56 #endmeeting