08:29:44 #startmeeting Yardstick work meeting 08:29:44 Meeting started Mon May 23 08:29:44 2016 UTC. The chair is kubi. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:29:44 Useful Commands: #action #agreed #help #info #idea #link #topic. 08:29:44 The meeting name has been set to 'yardstick_work_meeting' 08:29:56 #topic call role 08:30:03 #info Jing 08:30:04 #info Kubi 08:30:28 #info Mingjiang 08:30:46 #info qiujuan 08:30:56 #info Jun Li 08:31:06 #info Yaoguang Wang 08:31:33 #topic enhanced HA framework 08:31:45 #info Kanglin 08:32:05 #info qiujuan: JIRA task has been created for you 08:32:32 #info QiLiang 08:33:10 #topic Merge Conflict 08:33:10 #info kubi: I got it, I will start working on it ASAP. 08:33:19 qiujuan: great 08:33:23 #info Federico Ressi 08:33:39 #info dongwenjuan 08:34:02 # info goutham 08:34:40 :), welcome, all my friends 08:34:49 :) 08:35:44 Mingjiang6: do you have any plan to update this patch https://gerrit.opnfv.org/gerrit/#/c/14409/ 08:35:56 sorry, this is for Jing 08:36:24 Mingjiang6: this is for you, https://gerrit.opnfv.org/gerrit/#/c/14191/ 08:37:12 kubi: will update later 08:37:18 kubi: https://gerrit.opnfv.org/gerrit/#/c/14455/ 08:37:18 Mingjiang6: great 08:37:29 I will fix the conflict right after the meeting. 08:38:22 fdegir: do you mean that patch could be merged now? 08:38:31 kubi: yes please 08:38:46 fdegir: great, thank you. 08:38:53 thx 08:39:11 fdegir: done 08:39:18 good 08:39:20 #topic code review 08:39:55 please review patchs https://gerrit.opnfv.org/gerrit/#/c/14405/ 08:40:06 #info please review patchs https://gerrit.opnfv.org/gerrit/#/c/14405/ 08:40:28 #link https://gerrit.opnfv.org/gerrit/#/c/13703/ 08:41:10 let 's keep actively code review 08:41:21 #topic Yardstick CI imporvement 08:42:04 yep I have created a JIRA task there 08:42:20 MatthewLi: could you give us a intro about your idea of yardstick CI improvement 08:43:13 Kubi: the basic idea is that I want to make it's more clear to developers 08:43:42 i have a suggestion. 08:43:47 first move /ci directory into /tests 08:43:51 goutham: go ahead 08:44:01 go ahead 08:44:33 i am sorry i am new can we develop a gui jus like rally 08:44:36 our own GUI 08:45:04 That's very cool 08:45:06 goutham: that's great 08:45:26 basically yardstick executes a test_Case generates a HOT template using which two Vms will be created 08:45:37 based upon the scenario(PING) 08:45:53 creates a stack, and later on it deletes the stack 08:46:27 it stores the results in yardstick.out or in mongodb based upon the defaulter in etc 08:46:48 we generate a task-id as well while running a test_Case 08:47:27 so jus as in rally we create a option for user/ developer yardstick report generate 08:48:26 so now he can view the JSON and another command like yardstick report generate this will give a good html 08:49:23 The output can be viewed in the grafana at present. 08:49:31 sorry yardstick html generate to generate a html page i think this helps a developer 08:49:31 by now we use influxdb and grafana 08:49:44 yea i have gone through that as well 08:50:00 but somehow i feel a own GUI jus like rally would be great 08:50:57 goutham: i think that is also a good choice for user:). 08:50:58 what say poeple ?? 08:51:19 personally I think its good just do that 08:51:24 GUI is great for users and developers to use, that' totally true. 08:51:39 agree 08:51:42 qiliang27: any comments? 08:52:01 and if u can combine the grafana solution 08:52:22 goutham: could you like to do something about own Gui 08:52:30 yes kubi 08:52:39 goutham: that's great! 08:52:54 i have some good knowledge on python/and front end development 08:53:09 goutham: cool 08:53:20 i have not gone through angular js till now but if needed i can extend my skills to angular as well.. 08:53:45 goutham: good 08:53:59 goutham: awesome 08:54:08 then back to my topic? 08:54:13 :) 08:54:14 thank you :) 08:54:21 yea sure mathew :D 08:54:24 #agree we develop a gui jus like rally, we create a option for user/ developer yardstick report generate . 08:54:32 MatthewLi: it's your turn 08:54:55 goutham: thank you for your good proposal 08:55:07 you are welcome 08:55:14 the idea is also same as rally, if u looks its directory, put CI into tests is how they done 08:55:53 my idea is that it must also have multiple scenario executions 08:56:03 the second is that we have 2 run-test.sh one for unittest and one for test suite , we should adjust its names.... 08:56:05 jus like rally 08:57:48 third is that some hint bugs fix, such as https://gerrit.opnfv.org/gerrit/#/c/14405/ 08:58:10 MatthewLi: 2 run-test.sh, one for baisc test including unitest and one for Ci task (test suite), they are same name 08:59:03 MatthewLi: it will be a little confused for developer 08:59:07 kubi: so I plan to do some adjustment, these are written by different people previously 08:59:20 MatthewLi: yes, you are right 09:00:00 so, any comments about MatthewLi's proposal? 09:00:26 as goutham said we can extend to more scenarios, finally 09:01:16 MatthewLi: great 09:02:33 so I will list the actions here..... 09:03:01 #action Jun Li CI directory moves into /tests 09:03:39 #action Jun Li rename 2 same run_tests.sh scripts 09:04:21 #action Jun Li CI workflow bugs fix and improvement 09:04:43 any comments? 09:05:20 MatthewLi: great, thank you for your great work. 09:05:38 #topic others 09:06:35 #info HA team will attend our thursday IRC meeting to discuss HA test cases 09:06:53 #the meeting has been extended to one hour 09:07:08 #info the meeting has been extended to one hour 09:07:43 anything else? 09:08:46 ok, thank you for today. 09:08:53 #endmeeting