Re: [PATCH 0/3] Launch other test during migration

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello guys:

Any further suggestion which I need to improve those patches?

I agree that there's no much tests need to be run is this way except for
migration. In order to validate the function of migration, many tests need to be
run in parallel with migration and this series is just aimed at this.

One major advantage of this is that it could greatly simplified the test design
and could reuse existed test cases without modification. Without this, we must
split the tests cases itself or split the migration test and modification to 
existed code is also required.

One major issue is that not all tests could be run in this way, tests which
needs to do monitor operation may not work well, but ususally this kind of test
is meaningless during migration.

Another probably issue is that we can not control precisely when the migration
start, but it's not important to tests I post here because the background tests
are usually launch as a kind of stress and need much more time than just a
single migration to complete, so what we need to do here is just let the
migration run until the background tests finish.

The fact is that these tests work well and have find real issues with migration.

Any comments or suggestions?

----- "Jason Wang" <jasowang@xxxxxxxxxx> wrote:

> We could give a further test of migration by launch test during
> migartion. So
> the following series implements:
> 
> - A simple class to run a specified test in the background which could
> be used
> to launch other test during migartion. Its design is rather simple and
> its usage
> is a little tricky, but it work well.
> - Two sample tests which take advantages of the background class: Test
> reboot
> during guest migration and test file_transfer during guest migration.
> 
> In the future, we could even lauch autotest client test during guest
> migation.
> 
> ---
> 
> Jason Wang (3):
>       KVM Test: Introduce a helper class to run a test in the
> background
>       KVM test: Test reboot during migration
>       KVM test: Test the file transfer during migartion
> 
> 
>  client/tests/kvm/kvm_test_utils.py                 |   44
> +++++++++++++++
>  .../kvm/tests/migration_with_file_transfer.py      |   59
> ++++++++++++++++++++
>  client/tests/kvm/tests/migration_with_reboot.py    |   45
> +++++++++++++++
>  client/tests/kvm/tests_base.cfg.sample             |   12 ++++
>  4 files changed, 159 insertions(+), 1 deletions(-)
>  create mode 100644
> client/tests/kvm/tests/migration_with_file_transfer.py
>  create mode 100644 client/tests/kvm/tests/migration_with_reboot.py
> 
> -- 
> Jason Wang
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux