========================================
#opnfv-yardstick: Yardstick Work Meeting
========================================


Meeting started by kubi001 at 00:02:19 UTC.  The full logs are available
at
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-yardstick/2016/opnfv-yardstick.2016-11-01-00.02.log.html
.



Meeting summary
---------------

* Trevor Cooper  (trevor_intel, 00:02:32)
* roll call  (kubi001, 00:02:32)
  * kubi  (kubi001, 00:02:39)
  * Jing  (JingLu, 00:02:44)

* action follow up  (kubi001, 00:04:00)
  * LINK:
    http://ircbot.wl.linuxfoundation.org/meetings/opnfv-yardstick/2016/opnfv-yardstick.2016-10-31-08.31.txt
    (kubi001, 00:04:57)
  * chenjiankun  (chenjiankun, 00:20:00)
  * LINK:
    http://www.etsi.org/deliver/etsi_gs/NFV-TST/001_099/001/01.01.01_60/gs_nfv-tst001v010101p.pdf
    (Mingjiang, 00:26:04)
  * ACTION: kubi would update the rest-api part statement about
    bottlenecks integration  (Mingjiang, 00:35:44)

* D planning review  (kubi001, 00:53:45)
  * trevor, kubi and other Yardstick members went through the Yardstick
    Danube planing  (JingLu, 01:03:35)
  * Yardstick team will check if the generic testcase's metrics from the
    ETSI TST-001 is example.  (JingLu, 01:05:14)
  * chenjiankun clarify the requirements for Yardstick API in Danube
    (JingLu, 01:11:00)
  * for Vsperf integration, Yardstick and Vsperf will find out a good
    way to present Vsperf results in dashboard.  (JingLu, 01:14:53)
  * trevor propose Yardstick provides an accurate description of what is
    being tested, details of metrics measured, relevant specifications /
    references in Danube  (JingLu, 02:04:57)
  * Yardstick will provide suitability and accuracy Test tool (i.e.
    traffic  generators) in D release  (JingLu, 02:10:08)



Meeting ended at 02:10:37 UTC.



People present (lines said)
---------------------------

* kubi001 (9)
* JingLu (8)
* Mingjiang (4)
* collabot` (4)
* trevor_intel (2)
* chenjiankun (1)



Generated by `MeetBot`_ 0.1.4