We are doing some work to use charm actions as a replacement of the peer relation based iperf testing in juju status. If I'm not mistaken, using a peer relation to run this type of tests with a certain duration like 30 seconds is not scalable by design. So setting check_iperf=False and running iperf in an action should make the whole testing process shorter.
- https://review.opendev.org/c/openstack/charm-magpie/+/867756
"Change run-iperf action total-run-time to seconds"
and
"unconditionally install the iperf apt package in the charm, because it should always be available for the case where the user wants to run the run-iperf action"
We are doing some work to use charm actions as a replacement of the peer relation based iperf testing in juju status. If I'm not mistaken, using a peer relation to run this type of tests with a certain duration like 30 seconds is not scalable by design. So setting check_iperf=False and running iperf in an action should make the whole testing process shorter.
- https:/ /review. opendev. org/c/openstack /charm- magpie/ +/867756
"Change run-iperf action total-run-time to seconds"
and
"unconditionally install the iperf apt package in the charm, because it should always be available for the case where the user wants to run the run-iperf action"
- https:/ /review. opendev. org/c/openstack /charm- magpie/ +/879333 /bugs.launchpad .net/charm- magpie/ +bug/2015173 /bugs.launchpad .net/charm- magpie/ +bug/2015174
For
"run-iperf action does not allow to precise a single concurrency mode"
https:/
and
"Bandwidth output from run-iperf action is not calculated properly"
https:/