New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
metrics: cleans k8s iperf deployment when the test finishes. #8542
metrics: cleans k8s iperf deployment when the test finishes. #8542
Conversation
8b5c8f0
to
db573d4
Compare
db573d4
to
c3f633c
Compare
/test |
tests/metrics/network/iperf3_kubernetes/k8s-network-metrics-iperf3.sh
Outdated
Show resolved
Hide resolved
|
||
trap remove_tmp_file EXIT | ||
if [ -z "${bandwidth_result}" ] || [ -z "${jitter_result}" ] || [ -z "${cpu_result}" ] || [ -z "${parallel_result}" ]; then | ||
die "iperf has not results to save" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggested rewording: iperf couldn't find any results to save
tests/metrics/network/iperf3_kubernetes/k8s-network-metrics-iperf3.sh
Outdated
Show resolved
Hide resolved
metrics_json_end_array "Results" | ||
fi | ||
metrics_json_add_array_element "${json}" | ||
metrics_json_end_array "Results" | ||
} | ||
|
||
function iperf3_cpu() { | ||
# Start server |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this comment still relevant in this part of the function? iiuc, the iperf server is started in the iperf3_start_deployment
function. I see this same comment in other functions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can't get rid of this comment, thanks @chavafg
c3f633c
to
8fd0eb7
Compare
/test |
tests/metrics/network/iperf3_kubernetes/runtimeclass_workloads/iperf3-deployment.yaml
Show resolved
Hide resolved
This PR fixes small issues like: 1. Cleaning up the k8s environment by removing the iperf test implementation even when the test fails. 2. Checks if the workload returned a result before generating an empty results json file as it was bein done. 3. Removes the redundancy of calls to functions that process subtests and should compose the results json file only when all results are ready and not before. 4. The tcp service manifest was added to the server deployment which targets TCP port 5201. Fixes: kata-containers#8534 Signed-off-by: David Esparza <david.esparza.borquez@intel.com>
A prerequisite for measuring kata network bandwidth is run Iperf3 tool at a the transport layer provided by a k8s service for exposing a network where the clients inside the cluster can use to contact Pods in the service. Signed-off-by: David Esparza <david.esparza.borquez@intel.com>
8fd0eb7
to
b257700
Compare
/test |
This PR fixes small issues like:
Fixes: #8534