======================================== #opnfv-yardstick: Yardstick Work Meeting ======================================== Meeting started by kubi001 at 08:33:03 UTC. The full logs are available at http://ircbot.wl.linuxfoundation.org/meetings/opnfv-yardstick/2017/opnfv-yardstick.2017-02-27-08.33.log.html . Meeting summary --------------- * roll call (kubi001, 08:33:08) * kubi (kubi001, 08:33:11) * Jing (JingLu, 08:33:19) * Mingjiang (Mingjian_, 08:33:26) * Ross (rbbratta, 08:33:29) * Kanglin (Kanglin, 08:33:36) * LINK: https://wiki.opnfv.org/display/yardstick/Meetings (kubi001, 08:33:43) * mingjiang->rex (Mingjian_, 08:33:48) * deepak (sdeepak001, 08:33:55) * action items follows up (kubi001, 08:34:28) * LINK: http://ircbot.wl.linuxfoundation.org/meetings/opnfv-yardstick/2017/opnfv-yardstick.2017-02-20-08.34.html (kubi001, 08:34:43) * AP1: deepak_ will clean up and share the script (kubi001, 08:35:16) * AP1: Done https://gerrit.opnfv.org/gerrit/#/c/29413/ (kubi001, 08:36:47) * AP2 kubi will send the email to notify the Yardstick MS6 status (kubi001, 08:37:04) * AP2: Done kubi have replied David's imail about MS6 compliance (kubi001, 08:37:41) * AP3: kubi will initialize a etherpad to trace the CI issue (kubi001, 08:38:00) * Done https://etherpad.opnfv.org/p/yardstick_release_d_troubleshooting (kubi001, 08:38:12) * JIRA review (kubi001, 08:39:09) * LINK: https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=145&view=planning&selectedIssue=YARDSTICK-572 (Mingjian_, 08:40:09) * we should update the status of JIRA once you start a task or implement task (kubi001, 08:41:00) * Branch close time (kubi001, 08:45:23) * MS7 is Mar 10th (kubi001, 08:45:36) * LINK: https://jira.opnfv.org/issues/?jql=project%20%3D%20YARDSTICK%20and%20type%20%3D%20bug (Mingjian_, 08:46:02) * we can checkout the branch before Mar .10th. so we need to decide which date we want to checkout (kubi001, 08:47:38) * CI status (kubi001, 08:52:29) * keep watch on CI job https://build.opnfv.org/ci/view/yardstick/ (kubi001, 08:54:20) * everyone should read http://mywiki.wooledge.org/BashPitfalls before writing bash (kubi001, 08:56:16) * for openstack API, we can assume the python clients are installed already, if not, then use command line cliens, but use JSON or YAML output, ideally we should use SNAPS-OO (kubi001, 09:00:42) * We can use check_output/check_call also. This will raise a CalledProcessError if the called process returns a non-zero return code. (kubi001, 09:01:47) Meeting ended at 09:25:42 UTC. People present (lines said) --------------------------- * kubi001 (41) * Mingjian_ (26) * rbbratta (25) * JingLu (11) * sdeepak001 (6) * collabot` (3) * Kanglin (1) Generated by `MeetBot`_ 0.1.4