01:01:02 #startmeeting tricircle 01:01:03 Meeting started Wed Jul 5 01:01:02 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:04 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 01:01:06 The meeting name has been set to 'tricircle' 01:01:16 #topic rollcall 01:01:25 #info joehuang 01:01:35 #info Yipei 01:01:51 info xiulin 01:02:10 #info zhiyuan 01:02:26 #info dongfeng 01:02:45 #topic feature implementation 01:03:37 #info xuzhuang 01:03:41 let's look at feature implementation which wants to land in pike-3 01:04:42 I am working on improving our smoke test, I propose to use YAML to define our tests. here is the spec: https://review.openstack.org/#/c/479752 01:05:14 good to know the smoke test improvement is on the way 01:05:28 could you please register a BP in launchpad too? 01:05:38 I have completed job paginate_query, and I am working on doing some tests 01:05:49 hello 01:05:57 for pagination query, a BP is also welcome 01:06:00 hi ronghui 01:06:00 two implementation patches based on this idea: https://review.openstack.org/477500 and https://review.openstack.org/480051 01:06:16 to joe, so still on launchpad? 01:06:50 trying implementing LBaaS in multiple regions and importing external network 01:07:01 at least now, we haven't migrate to storyboard yet 01:07:38 to yipei, thank you very much, hope that LBaaS and external network importing could be landed in pike 01:07:48 I think resource routing pagination feature can be landed in pike 3. 01:07:56 ok, will register a BP on launchpad 01:08:03 yes, i hope so, i try my best to make it 01:08:16 I am very busy these days, will try to review patches AFAP 01:08:54 sfc's update patch may be be landed in pike 3 01:10:43 seems that everything fine :) 01:11:02 #topic open discussion 01:11:14 any topic to be discussed? 01:11:38 no from me 01:11:43 no 01:11:54 no from me 01:12:04 no for me 01:12:12 no from me 01:12:30 to xuzhuang, thank you for the pagination patch 01:12:43 could you register a BP too? 01:12:48 to Ronghui, has Xiongqiu tested his three patches? if so, I would like to try them out in my own environment 01:13:18 his has tested his patches 01:13:26 patch1 and patch2 should be merged for testing coverage, isn't it? 01:13:46 you mean job pagination also needs a bp? 01:14:51 job pagination is another patch, but not the patch for resource routing? 01:14:54 if you say the two patches merge into one patch and tested it, no for this situation 01:15:12 patch2 has been changed to use driver to implement, but I don't see code to load the driver 01:15:34 yes, two independent patches 01:16:16 yes we try to fix it 01:16:41 we need to merget the three patches, otherwise the feature is not complete 01:16:47 s/merget/merge 01:17:28 to xuzhuang, ok. then no BP is needed, but the API documentation update is needed, to describe in detail how the API will function 01:17:36 yes next version, the two patches will merge into one patch 01:17:56 ok, got it 01:19:19 please review the smoke test spec, all new features should be added and tested with its own smoke test cases, so the spec is important for all 01:19:42 ok 01:20:10 without smoke test cases, the feature quality has no guarantee. 01:20:32 ok 01:20:40 ok 01:20:43 yeah, would like to hear your opinion whether the design of the YAML schema is reasonable 01:20:47 ok 01:20:49 ok, got it 01:21:44 because smoke test will test the system on living two region openstack together tricircle, so only such an real environment can make sure the feature work. 01:22:55 passing smoke test is basic requirement for all features, though it comes later, but we need to make it become the gate for all features. 01:23:24 other topic? 01:23:30 no for me 01:23:33 no for me 01:23:42 the YAML file is also usable for your local test during feature development, you can write a YAML then run it to test your feature, no need to type the long command again and again 01:23:55 no for me 01:24:04 no for me 01:24:12 no for me 01:25:02 ok, if there is no other topic, we can end the meeting a little early, and continue discussion in #openstack-tricircle if needed 01:25:10 #endmeeting