13:02:04 #startmeeting tricircle 13:02:05 Meeting started Wed Jul 27 13:02:04 2016 UTC and is due to finish in 60 minutes. The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:02:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:02:09 The meeting name has been set to 'tricircle' 13:02:13 hello 13:02:20 #topic rollcall 13:02:24 #info joehuang 13:02:37 #info dongfeng 13:02:37 #info zhiyuan 13:02:46 #info Yipei 13:02:46 #info yinxiulin 13:03:29 hello, the first topic is about microversion 13:03:36 #topic microversion 13:03:44 I just finished microversion coding today 13:03:57 hi, Xiulin, how about the micro-version support in Tricircle? 13:04:07 I just finished microversion coding today 13:04:30 good, is there tempest test cases for microversion? 13:05:01 no yet 13:05:10 hello 13:05:17 hi, ronghui 13:05:26 hi,joe 13:05:32 no special tempest test cases for microsversion? 13:05:49 but I am sure unit test should be there in Nova \ 13:05:54 i have not debug the code 13:06:07 Nova is the first service to support microversion 13:06:22 so you can borrow Nova microverion test cases 13:06:40 what is microversion 13:06:49 ok , i wanna finisend the debug first 13:06:58 then i will coding the tempset 13:07:16 good 13:08:42 so go on the implementation, than you, xiulin 13:08:55 than -> thank 13:09:37 #topic big tent application 13:09:39 Ok 13:10:23 hello, I shared the big tent application in the irc channel about the second round discussion 13:10:48 #link https://review.openstack.org/#/c/338796/ 13:11:19 #link http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-07-26-20.02.log.html 13:11:38 would like to know your ideas on the comment 13:15:36 ok 13:15:42 hmm, the most important point tc members complain is that we are using api gateway. 13:16:09 we need to ensure api consistency through tempest test cases 13:16:40 TCs are afraid the in-consistency in the API 13:16:44 different from other openstack services, which provides its own designed api, tricircle is serving request for vm, volume and networking 13:17:02 yes 13:18:53 #topic open discussion 13:19:50 how about the features API implementation progress 13:20:07 do you think it will be more acceptable if we provide a set of new api to manage vm, volume and networking?do you think it will be more acceptable if we provide a set of new api to manage vm, volume and networking? 13:21:05 for networking part, i am working on l3 networking on shard vlan network 13:21:08 for new API, it's even more difficult to get other software work with 13:21:36 thank you zhiyuan 13:22:12 i have reconstruct the code to put networking operation in a helper module, and move the router setup to xjob 13:22:28 this is some preparation 13:23:00 good progress 13:23:06 for cinder part we are working to perfect the basic function 13:23:25 "perfect"? 13:23:44 i mean complete 13:23:55 ok 13:24:33 do you know how to open tempest test cases for new feature? 13:25:03 no 13:26:14 If there is some relevant documents can provide help 13:26:25 then what about runing tempest test on your own environment? 13:26:35 ok, there is one example in this patch to show how to open tempest test cases for volume feature 13:26:57 ok 13:27:11 since you need to run tempest test locally before you submit your code 13:27:12 still working on dynamic pod binding. recently, i am trying to catch a deadline of a conference. After the deadline (1st, Aug), i will denote myself to coding, and will finish it as planned 13:27:17 https://review.openstack.org/#/c/343517/ 13:28:50 in this file: https://github.com/openstack/tricircle/blob/master/tricircle/tempestplugin/tempest_volume.sh 13:29:44 just need to add one regex line to include the tempest test cases for your feature 13:29:49 for example TESTCASES="$TESTCASES|tempest.api.volume.test_volumes_get" 13:30:10 ok 13:30:25 i will try it in our environment 13:30:30 will include all test cases matched with test_volumes_get 13:31:12 if you submit a patch, it'll be executed by the gate-tricircle-dsvm-functional 13:32:00 if the job failed, you can click the job, and find a lot of files to provide debug information why the test cases failed 13:32:45 as zhiyuan proposed, you can test locally using tempest first, it'll be easier to find out the failure 13:32:55 ok 13:33:02 thanks so much 13:33:18 to Yipei, thanks for you information 13:33:26 to Ronghui, welcome 13:34:25 other topics? 13:34:52 no for me 13:35:16 no for me 13:35:17 no for me 13:35:18 no for me 13:35:22 no for me 13:35:38 ok. let's end this meeting now 13:35:45 i just want to ask the problem that in local.conf 13:35:51 please 13:35:57 and just see the code is update 13:36:11 ok 13:36:26 so the issue is fixed 13:36:51 ? 13:37:13 yes 13:37:44 thank you for attending the meeting, let's keep online in #openstack-tricircle for daily communication 13:37:51 #endmeeting