To measure the time to pod network, a deployment that uses agnhost
image is used, which get exposed as a net server and replies to curl
calls, the test measure this reply time and saves it for further reporting.
Then, only the exposed net service gets deleted.
Signed-off-by: Morales Quispe, Marcela <marcela.morales.quispe@intel.com>
If the cpu-load function is enabled, save its config settings into the
JSON results file.
This required a little bit of re-sequencing of the json library calls,
to ensure we did the init of the JSON early enough, but not more than
once.
Signed-off-by: Graham Whaley <graham.whaley@intel.com>
Rejig the framework a little to unify the init/shutdown calls and code,
which allows us to add the cpu-load enable/disable ability to all the
existing metrics.
Signed-off-by: Graham Whaley <graham.whaley@intel.com>
Add library code that can generate a variety of cpu loads across the
cluster. Configuration is via environment variables, documented in the
.md file.
Signed-off-by: Graham Whaley <graham.whaley@intel.com>
- Send n requests for each of the running pods.
- Measure response time to response.
- Report response time percentiles: 5-25-50-75-95 %.
- Refactor scaling/*.sh variables to scaling/common.bash.
Signed-off-by: Antti Kervinen <antti.kervinen@intel.com>
Use `tr` rather than `sed` for doing the line/whitespace conversions
on the JSON stream, if asked. Slightly more efficient, and we also drop
the wrapping ""'s, to allow the data to land in logstash without error.
Signed-off-by: Graham Whaley <graham.whaley@intel.com>
If a RUNTIME is not set, then save it as 'default' in the JSON
rather than an empty string, as the emptry string does not render
well later in any graphing.
Signed-off-by: Graham Whaley <graham.whaley@intel.com>
We were carrying a bunch of legacy docker based functions
that we do not use. Drop them. We can always add them back
in later if we find we do need some.
Signed-off-by: Graham Whaley <graham.whaley@intel.com>
We are very likely to re-use the k8s api code in many/all of the
tests, so move common code out to a common libray file.
Signed-off-by: Graham Whaley <graham.whaley@intel.com>
Capture some of the k8s setup information in the JSON results
files. Add sections for:
- kubectl version
- kubectl get nodes
Signed-off-by: Graham Whaley <graham.whaley@intel.com>
If we have $RUNTIME set in the env, then we set up the pod
RuntimeClass, otherwise, just use the default node runtimes.
Clean up some of the un-used library code around docker/RUNTIME
as well whilst we are there.
Signed-off-by: Graham Whaley <graham.whaley@intel.com>
Morales Quispe, Marcela