========================================================= #opnfv-meeting: Testing community weekly meeting July 7th ========================================================= Meeting started by morgan_orange at 13:59:28 UTC. The full logs are available at http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-07-07-13.59.log.html . Meeting summary --------------- * call role (morgan_orange, 13:59:37) * Morgan Richomme (Functest) (morgan_orange, 13:59:45) * Chris Price (lurking IRC only) (ChrisPriceAB, 14:00:06) * kubi (kubi001, 14:00:21) * Jose Lausuch (jose_lausuch, 14:03:04) * Colorado status (morgan_orange, 14:04:12) * status for yardstick (morgan_orange, 14:05:23) * LINK: https://wiki.opnfv.org/display/yardstick/Yardstick+Colorado+Release+Planning (morgan_orange, 14:05:25) * LINK: https://etherpad.opnfv.org/p/yardstick_release_c_feature_freeze (kubi001, 14:06:39) * Jing (Jing_, 14:07:03) * status Functest (morgan_orange, 14:07:06) * integration phase in progress: copper, moon, security_scan, sfc-odl, sfc-onos (morgan_orange, 14:07:35) * status Vsperf (morgan_orange, 14:08:21) * everything should be in the repo :) interaction with yardstick project for integration, no major concerns (morgan_orange, 14:09:23) * release criteria (morgan_orange, 14:10:38) * easy for functional testing.. (PASS/FAIL) (morgan_orange, 14:10:49) * not easy for performance/qualification, KPI not easy to define (morgan_orange, 14:11:12) * for performance tests (yardstick/vsperf) if we can get figure, we will consider the test as PASS (morgan_orange, 14:12:09) * Functest criteria in the test case => automatic reporting (morgan_orange, 14:25:43) * LINK: http://testresults.opnfv.org/reporting/functest/release/master/index-status-fuel.html (morgan_orange, 14:25:48) * code of automatic reporting is in the releng repo (morgan_orange, 14:26:26) * LINK: https://git.opnfv.org/cgit/releng/tree/utils/test/reporting (morgan_orange, 14:26:29) * ELK and influxDB and grafan will coexist (morgan_orange, 14:26:47) * you can use both solutions, it depends on your usage and what you want to visualize (morgan_orange, 14:27:02) * question on the 4 consecutive runs: concerns from the infra group (morgan_orange, 14:36:11) * concerns because we experienced in Brahmaputra that simple Functional tests may fail/pass without one line change => concern on the robustness (morgan_orange, 14:36:42) * side effects due to complex configuration may lead to strange behavior and inconsistancy in test results (morgan_orange, 14:37:16) * ACTION: dmcbride: organize a sync meeting Infra/testing (Daniel chairing the topic) to discuss this topic (morgan_orange, 14:39:56) * documentation (morgan_orange, 14:43:18) * need for OPNFV testing = overall picture of all the test projects (morgan_orange, 14:52:43) * ~ conversation with the community (morgan_orange, 14:52:53) * Dave Urschatz (durschatz, 14:53:18) * ACTION: mbeierl dmcbride invite Alan for a status on testing whitepaper (morgan_orange, 14:57:19) * Dave ask management if possible to coordinate the redaction of such document (morgan_orange, 14:58:32) * ACTION: all PTLs: ask preference for meeting time (allow Asian contributors to join) (morgan_orange, 15:00:48) * Add Yardstick test evolution to agenda for next week (mbeierl, 15:01:44) Meeting ended at 15:02:04 UTC. Action items, by person ----------------------- * dmcbride * dmcbride: organize a sync meeting Infra/testing (Daniel chairing the topic) to discuss this topic * mbeierl dmcbride invite Alan for a status on testing whitepaper * mbeierl * mbeierl dmcbride invite Alan for a status on testing whitepaper People present (lines said) --------------------------- * morgan_orange (35) * collabot` (5) * kubi001 (4) * ChrisPriceAB (2) * mbeierl (2) * Jing_ (1) * durschatz (1) * jose_lausuch (1) * dmcbride (1) * yujunz (1) Generated by `MeetBot`_ 0.1.4