08:30:03 #startmeeting Yardstick work meeting 08:30:03 Meeting started Thu Oct 29 08:30:03 2015 UTC. The chair is anac1. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:30:03 Useful Commands: #action #agreed #help #info #idea #link #topic. 08:30:03 The meeting name has been set to 'yardstick_work_meeting' 08:30:10 #info Ana Cunha 08:30:52 #info QiLiang 08:31:00 #info gao liang 08:31:01 #info Yimin Wang 08:31:24 #topic Lmbench bug fix 08:31:57 what is the status on this ? 08:32:00 #info Jingwen Hou 08:32:38 fix in kristian 's patch 08:33:06 #info patrick 08:33:08 #info Rex 08:33:26 I added it to my patch when I rebased it so it could pass all unit tests 08:33:29 ok, so nothing to discuss, the patch https://gerrit.opnfv.org/gerrit/#/c/2623/ is fixing the issue? 08:33:45 yes 08:33:56 #info patch https://gerrit.opnfv.org/gerrit/#/c/2623/ fix the problems 08:34:00 thanks 08:34:13 #topic test result API 08:35:07 #info Jose Lausuch 08:35:12 I have comments for this section :) 08:35:24 yardstick2dashboard is merged in releng 08:35:24 ok, go ahead 08:35:38 for all the test projects reporting results to the DB 08:35:54 #info yardstick2dashboard is merged in releng 08:35:55 jiust add ping for poc 08:36:03 we have to agree on a common way to have an option to push the results or not 08:36:14 we talked about this last week in functest 08:36:31 by default we shouldnt push anything 08:36:35 and if we want, we add a flag to our scripts 08:36:42 why we shouldn't push anything? 08:36:47 something like --push_results=true or something like that 08:36:55 because we dont want everyone that tries opnfv to push it 08:37:08 there will be credentials in the DB soon 08:37:18 and if someone doesnt have access, that push function will fail 08:38:11 jose_lausuch: if we are using a result api, the default should NOT be DONT PUSH, doesn't make sense to me... 08:38:28 imagine, I am individual and Im testing opnfv on my private lab 08:38:33 and then I run the tests 08:38:39 why should I have to push? 08:38:49 I wont have credentials, it will fail anyway 08:38:52 what do you think? 08:39:08 ci triggerd test can push result ? 08:39:09 (this is not 100% decided, so we can share different views) 08:39:33 yes a flag to push or not is ok 08:39:33 i think CI triggered should push results 08:39:34 now it does 08:39:57 CI connected labs is ok, they will have credentials to the target DB 08:40:11 but Im concerned about everyone else testing opnfv 08:40:21 this could cause a lot of pushes from different sources 08:40:22 so private test cannot use the api ? 08:40:26 we are currently not continously pushing in ci job but im working on that 08:40:53 we should all have credentials in the target db, thats for sure, all the opnfv community labs for sure 08:41:15 yes, agree to the need to have credentials 08:41:32 but in the end if I triy it on my private server, and another one does the same, and so 100 people, we can have 10000 different sources in the DB 08:41:42 to avoid it, we will use credentials 08:41:51 so what do you thing about the flag ? 08:41:51 yes we need credentials tpo avoid that 08:41:54 and by default dont push? 08:42:20 yes 08:42:51 so when is the credentials implemented? 08:43:01 not sure when 08:43:04 but we will know :) 08:43:28 when? 08:43:41 I dont have the details now 08:43:57 jnon, qiliang: do we need a local dB? 08:44:15 not for this , we can dumpt to file 08:44:35 ok 08:44:41 agree with jnon 08:44:46 ok 08:44:46 that was all what I had to say, please add a flag to push results to DB as an option 08:44:47 :) 08:45:09 ok, thanks 08:45:15 jose_lausuch: how is the documentation for the api? 08:45:33 that is what morgan has been working on 08:45:40 what do you mean by "how" ? :) 08:45:53 i mean, wiki, gerrit ? 08:46:08 :) 08:46:15 https://wiki.opnfv.org/collection_of_test_results 08:46:30 guy rodrigue is working on that 08:46:37 ok, will it always be in the wiki? 08:46:44 for now... I think so 08:46:55 i need a link to the documentation, that's why i ask 08:46:55 not sure if morgan has plans to put it somewhere else, I will ask 08:46:59 ok 08:47:04 thans ! 08:47:10 thanks! 08:47:36 so, jnon, qiliang: we agree to put a flag, default dont push? 08:48:01 agree 08:48:07 yes that is a flag to the ci scripts 08:48:38 ci will push right ? 08:48:45 yes 08:48:45 #agreed to add a flag to result api, default DONT push 08:48:46 i already added a flag to set db server address to the scripts (not pushed yet) 08:49:13 thanks :) 08:49:14 if not set it dumps to file 08:50:09 jose_lausuch: do you know if the installer type is a variable from all installers? 08:50:34 actually we use the yarsick.conf to config to sent to DB or just dump to file. so pay attention to this config should not to conflict with the flag value. 08:50:38 thats a tricky question 08:50:45 even worse is the user and password of the installer 08:51:03 we know the defaults, but you can install it without defaults (different usr/pass) 08:51:07 for the installe type 08:51:12 I give the parameters in the jenkins job 08:51:21 installer_type and installer_ip 08:51:25 patrik1: yes the flag updates yardstick.conf in docker image 08:52:01 jose_lausuch i have check the code today :) 08:52:20 jnon: that's the point, tks. 08:52:41 are you guys using fetch_os_credssh? 08:52:53 yes 08:53:08 so we have a common problem 08:53:27 someone contacted us because he was not using root/r00tme in fuel, he changed the defaults 08:53:31 and then that script failed 08:53:38 so we will figure out how to do that 08:53:41 not clear yet 08:53:58 ok 08:54:07 the only thing I can imagine now is to provide also together with installer_type and ip, installer_user and installer_password 08:54:18 pod name is needed also 08:54:26 but thats not very safe ... 08:54:33 providing passwords like this :) 08:54:42 ok jnon 08:54:49 ok, moving on 08:54:50 you mean for fetch_os_creds? 08:55:00 #topic HA test cases 08:55:17 no for other things 08:55:26 patrick1: are you ok with the 5 test cases in the etherpad ? 08:55:51 #link https://etherpad.opnfv.org/p/yardstick_ha 08:55:58 not yet . I gave the first, and try to finish all of them this weekend. 08:56:18 but I gave the five test case name and scope. 08:56:28 ok, but that is the list to develop for r2? 08:56:35 we need pod name to choose test suite, and in info dumped to db 08:56:50 yes. 08:56:59 ok 08:57:21 #info the list in etherpad is the R2 target 08:57:22 I try to finish all of them in R2, 08:57:44 the first is almost done, where will you test? 08:57:57 but if some are not finished for some reason, I will delay it to C 08:58:01 ok 08:58:19 Now I test it on huawei lab. 08:58:30 and then on china mobile's lab? 08:58:54 for ha project, i mean 08:59:04 I have talked to Fuqiao, I hope so 08:59:12 ok, good 08:59:26 but I think maybe we can share a demo to HA team first 08:59:36 and talk about some details 08:59:54 yes, when the code is ready 09:00:14 when the test case stable , we can deploy and run on China Mobiles lab 09:00:40 sounds like a plan 09:00:56 In OPNFV Summit , HA has a session 09:01:08 you mean breakout? 09:01:33 I will share the five test cases on it. And discuss with other guys from HA team. 09:02:12 ok 09:02:25 that's all for today, thanks everyone 09:02:28 #endmeeting