15:03:40 <gabriel_yuyang> #startmeeting Testperf Weekly Meeting 20180712
15:03:40 <collabot> Meeting started Thu Jul 12 15:03:40 2018 UTC.  The chair is gabriel_yuyang. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:03:40 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:03:40 <collabot> The meeting name has been set to 'testperf_weekly_meeting_20180712'
15:03:50 <gabriel_yuyang> #topic Roll Call
15:04:06 <gabriel_yuyang> #info Gabriel Yu
15:04:12 <dmcbride> #info David McBride
15:04:16 <mbeierl> #info Mark Beierl
15:05:02 <gabriel_yuyang> #topic Container Performance Testing
15:07:34 <mj_rex> #info Rex
15:07:40 <gabriel_yuyang> #info Storperf needs more information from stor4nfv about container volume testing
15:08:07 <gabriel_yuyang> #link https://github.com/kubernetes/perf-tests
15:08:26 <mbeierl> #info StorPerf uses Heat to launch a VM which then gets an SSH key from the orchestrator.  We can then ssh to the VM and copy FIO to it and start executing workloads.
15:09:10 <mbeierl> #info with Containers, I don't know if SSH is possible, as containers do not usually run sshd and they might not get the SSH key from the orchestrator (like VM with cloud-init)
15:09:34 <gabriel_yuyang> #link https://github.com/kubernetes/perf-tests/tree/master/clusterloader
15:09:40 <mbeierl> #info So, StorPerf needs to investigate how to communicate with the container for copying FIO to it, as well as for remotely executing FIO
15:09:56 <mj_rex> mbeierl: you can have ssh service with container
15:11:09 <mbeierl> mj_rex: that is true.  I guess an idea would be to find a previously published container (or even publish one from StorPerf) and make sure that it either has an SSH key in it, or can have a hard-coded username password?
15:12:02 <mbeierl> I think I need to find more information on how containers can be launched by OpenStack and Heat.
15:12:29 <gabriel_yuyang> #info VSPERF present ideas about the container network testing in earlier meeting
15:13:55 <gabriel_yuyang> #info As to Yardstick, Rex working on a docker images including iperf, netperf, fio,..
15:14:27 <gabriel_yuyang> #info Yardstck is capable of setting up pods through k8s and 2 sample tests
15:15:07 <gabriel_yuyang> #link https://github.com/kubernetes/test-infra/tree/master/kubetest
15:17:20 <gabriel_yuyang> #link https://github.com/kubernetes/test-infra
15:23:42 <gabriel_yuyang> #link https://gerrit.opnfv.org/gerrit/#/c/51635/
15:24:44 <mj_rex> #link https://git.opnfv.org/yardstick/tree/yardstick/common/kubernetes_utils.py
15:24:51 <mj_rex> mbeierl: some sample of utilizing kubernetes api in Yardstick
15:25:02 <gabriel_yuyang> #link https://gist.github.com/djkonro/d087ae4cf70caa59fb55c8e0a0755aba
15:30:46 <gabriel_yuyang> #info in case anyone want to set up a kubernetes cluster: https://wiki.opnfv.org/display/compass4nfv/Containerized+Compass+for+K8S+Integration
15:33:18 <gabriel_yuyang> #info David: in the next release, milestone of kubernetes should be set up
15:38:54 <gabriel_yuyang> #link https://etherpad.opnfv.org/p/minum_test_sets_gating_cd
15:40:52 <dmcbride> #info to be clear, I'm proposing two things:  1) k8s scenarios should be running HC for kubernetes; and 2) increase the requirements for MS3 to include k8s scenario deployment and passing HC for kubernetes
15:43:56 <gabriel_yuyang> #link https://wiki.opnfv.org/display/dovetail/Proposed+Test+Scope+of+OVP+2018.0x
15:51:41 <gabriel_yuyang> #AoB Gates for OPNFV CD Release
15:52:06 <gabriel_yuyang> #info David will reach out to Steaven about SNAPS status
15:53:01 <gabriel_yuyang> #info David want to Cedric to present about details of healthcheck in either Testperf or the Tech discussion
15:53:42 <gabriel_yuyang> #endmeeting