mirror of
https://github.com/aljazceru/kata-containers.git
synced 2025-12-17 22:34:25 +01:00
849253e55c
As we've done some changes in the VMM vcpu allocation, let's introduce basic tests to make sure that we're getting the expected behaviour. The test consists in checking 3 scenarios: * default_vcpus = 0 | no limits set * this should allocate 1 vcpu * default_vcpus = 0.75 | limits set to 0.25 * this should allocate 1 vcpu * default_vcpus = 0.75 | limits set to 1.2 * this should allocate 2 vcpus The tests are very basic, but they do ensure we're rounding things up to what the new logic is supposed to do. Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>
41 lines
1.1 KiB
Bash
41 lines
1.1 KiB
Bash
#!/usr/bin/env bats
|
|
#
|
|
# Copyright (c) 2023 Intel Corporation
|
|
#
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
#
|
|
|
|
load "${BATS_TEST_DIRNAME}/../../common.bash"
|
|
load "${BATS_TEST_DIRNAME}/tests_common.sh"
|
|
|
|
setup() {
|
|
[ "${KATA_HYPERVISOR}" == "dragonball" ] && \
|
|
skip "runtime-rs is still using the old vcpus allocation algorithm, skipping the test"
|
|
|
|
get_pod_config_dir
|
|
pods=( "vcpus-less-than-one-with-no-limits" "vcpus-less-than-one-with-limits" "vcpus-more-than-one-with-limits" )
|
|
expected_vcpus=( 1 1 2 )
|
|
}
|
|
|
|
@test "Check the number vcpus are correctly allocated to the sandbox" {
|
|
# Create the pods
|
|
kubectl create -f "${pod_config_dir}/pod-sandbox-vcpus-allocation.yaml"
|
|
|
|
# Check the pods
|
|
for i in {0..2}; do
|
|
kubectl wait --for=jsonpath='{.status.conditions[0].reason}'=PodCompleted --timeout=$timeout pod ${pods[$i]}
|
|
[ `kubectl logs ${pods[$i]}` -eq ${expected_vcpus[$i]} ]
|
|
done
|
|
}
|
|
|
|
teardown() {
|
|
[ "${KATA_HYPERVISOR}" == "dragonball" ] && \
|
|
skip "runtime-rs is still using the old vcpus allocation algorithm, skipping the test"
|
|
|
|
for pod in "${pods[@]}"; do
|
|
kubectl logs ${pod}
|
|
done
|
|
|
|
kubectl delete -f "${pod_config_dir}/pod-sandbox-vcpus-allocation.yaml"
|
|
}
|