15:08:40 <mbeierl> #startmeeting Weekly Test WG Meeting
15:08:40 <collabot> Meeting started Thu Aug  2 15:08:40 2018 UTC.  The chair is mbeierl. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:08:40 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:08:40 <collabot> The meeting name has been set to 'weekly_test_wg_meeting'
15:08:48 <mbeierl> #chair efoley
15:08:48 <collabot> Current chairs: efoley mbeierl
15:08:54 <mbeierl> #topic Roll Call
15:09:07 <mbeierl> #info Mark Beierl
15:10:00 <efoley> #info Emma Foley
15:12:58 <Alec82> #info Alec Hothan
15:13:58 <efoley> #topic k8s testing
15:14:53 <mbeierl> #info Yardstick does not currently have K8s performance tests - K8s contexts are being added
15:15:58 <mbeierl> #info Will be equivalent scenarios but different context (ie use K8s instead of OpenStack)
15:18:01 <efoley> #info Storperf is tightly coupled with Heat, so k8s support is a while away
15:18:36 <mbeierl> #topic Discussion of test document and overall cohesion of test tools
15:19:17 <mbeierl> #info At Plugfest a summary was put together for all the test tools
15:19:29 <mbeierl> #info Discussions about how to share the test tools beyond OPNFV
15:19:45 <mbeierl> #info Emma and Georg submitted talks to 3 conferences
15:20:03 <mbeierl> #info More documentation might be "forced" to occur if talks are accepted
15:24:02 <mbeierl> #info Do we attempt to standardize on a single test result db, or have each tool rely on its own method to report results
15:24:27 <mbeierl> #info Al mentions that own results are typically the most reliable way
15:24:47 <mbeierl> #info test results DB is a central point of failure
15:26:06 <mbeierl> #info test results db is becoming orphaned in that there is no real PTL, don't know where to open JIRA tickets, etc
15:27:37 <mbeierl> #info test results DB is being used as part of the release process: example http://testresults.opnfv.org/master/functest/status-apex.html
15:27:56 <mbeierl> #info the fact that it is part of the release process and no identified PTL is a concern
15:31:37 <issyl018> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
15:31:41 <issyl018> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
15:31:44 <issyl018> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
15:31:47 <issyl018> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
15:31:50 <Our> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
15:31:53 <Our> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
15:31:57 <Our> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
15:32:00 <Our> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
15:35:25 <mbeierl> #info Barometer running as a core part of this 'central test project' so that it is always collecting data and anyone could examine it to see what happened during a test run
15:36:45 <poutine15> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
15:36:45 <poutine15> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
15:36:51 <poutine15> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
15:36:51 <poutine15> A fascinating blog by freenode staff member Matthew 'mst' Trout https://MattSTrout.com/
15:38:16 <mbeierl> #info Barometer can use influx as a write source for all metrics and any read plugin (prometheus, collectd, etc,) can be used
15:40:56 <mbeierl> #info collectd needs to be manually installed on compute, control, etc,
15:42:02 <mbeierl> #info read plugins (metrics) are configured on each node and configured to send to barometer
15:43:10 <mbeierl> #info compute nodes KVM metrics are more interesting, than say control nodes
15:44:05 <mbeierl> #info Barometer upstreamed ansible scipts for the containers and made plugins
16:01:58 <efoley> #info Yardstick and Barometer could be looked at as key areas for standardisation/integration between the test projects
16:03:25 <mbeierl> #endmeeting