Add kepler_vm metrics test when CPU load is high #310
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The test implements a scenario when test VM has a period of high CPU load during the test. Scenario: 1. Get VM power consumption in idle state 2. Run a process that causes high CPU load of VM for 30 seconds and make sure that VM power consumption metrics increased accordingly 3. After high CPU load process completed get VM metrics again and make sure that value is similar to the one received in step 1
elfiesmelfie
requested changes
Sep 23, 2025
| port_id=$({{ openstack_cmd }} port list --device-id='{{ test_vm_id }}' --network '{{ kepler_test_vm_network }}' -c id -f value) | ||
| floating_ip=$({{ openstack_cmd }} floating ip list --port $port_id -c 'Floating IP Address' -f value) | ||
| ssh_options='-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null' | ||
| ssh -i '{{ kepler_test_vm_key }}' $ssh_options '{{kepler_test_vm_user}}'@$floating_ip 'nohup timeout 30 openssl speed -multi $(grep -ci processor /proc/cpuinfo) > /dev/null 2>&1 &' |
Collaborator
There was a problem hiding this comment.
Suggested change
| ssh -i '{{ kepler_test_vm_key }}' $ssh_options '{{kepler_test_vm_user}}'@$floating_ip 'nohup timeout 30 openssl speed -multi $(grep -ci processor /proc/cpuinfo) > /dev/null 2>&1 &' | |
| ssh -i '{{ kepler_test_vm_key }}' $ssh_options '{{ kepler_test_vm_user }}'@$floating_ip 'nohup timeout 30 openssl speed -multi $(grep -ci processor /proc/cpuinfo) > /dev/null 2>&1 &' |
| until: value2.rc == 0 and (value2.stdout|float > value1.stdout|float) | ||
|
|
||
| - name: | | ||
| TEST Check kepler metrics dynamics when test VM is under load for some time |
Collaborator
There was a problem hiding this comment.
If you're using the custom xml logger, I recommend checking the output, since I am not sure how these three tasks will be reported, since they have the same name.
I think they'll each get a testcase entry in the XML, but I don't know if polarion will like that or not
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The test implements a scenario when test VM has a period of high CPU load during the test.
Scenario: