increment in time to detect a failed vm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Triaged
|
High
|
ya.wang |
Bug Description
StarlingX bug reporting guidelines:
Please use the template below when opening StarlingX bugs.
Brief Description
-----------------
After getting the initial performance numbers, we found that one of the important gaps we have is in the early detection of failed VM.
We confirm that this gap is fixed by the patch that your team very kindly provide from R1:
https:/
Severity
--------
<Major: System/Feature is usable but degraded>
Steps to Reproduce
------------------
1) Launch a VM with the next features:
RAM 2GB
Disk 20GB
VCPUS 1
Properties hw:mem_
Image Debian
2) Detect the compute where that VM was deployed and kill the QEMU process,
immediately after this, the initial time must be taken.
3) Make a constant of pull request of the VM status and stop the test when it
changes.
4) Finally take the end time and calculate the delta.
Expected Behavior
------------------
Around 500 ms
Actual Behavior
----------------
Seconds
Reproducibility
---------------
<Reproducible/
State if the issue is 100% reproducible with 10% of Coefficient of Variation (CV). CV is a measure of relative variability. It is the ratio of the standard deviation to the mean (average)
System Configuration
-------
Two node system
Branch/Pull Time/Commit
-------
R2.0
Changed in starlingx: | |
importance: | Undecided → High |
Assigning to distro.openstack PL to review/follow up.
This appears to be a request to propose a code change to nova. I'm not sure why this is an stx launchpad.