#128: pst: Create a mechanism to ensure test clients are fully up-to-date
---------------------+------------------------------------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: major | Milestone: Package Sanity Tests
Component: tests | Version: 1.0
Resolution: | Keywords: tps
---------------------+------------------------------------------------------
Changes (by jlaska):
* cc: mmcgrath (added)
Comment:
mmcgrath demo'd a clever way of creating disposable virt guests for use
with our tests. I've modified the script slightly to make the
requirements more explicit. The general idea is ...
* Create a master virt guest on the test system backed by a local volume
* When a test needs a disposable system, use the attached script to
create a slave virt guest
* new guest storage uses an LVM snapshot of the ''master'' guest
* any changes in new slave guest are not saved to the ''master'' LVM
volume
* Periodically, keep the master guest updated to the latest content
mmcgrath and I discussed several techniques for using this.
1. Use the setup above to create dedicated test clients for autotest used
for any AutoQA tests that do not require virt
* Pros
* No/little code required
* Cons
* Autotest virt test clients would need to be setup to not accept
any KVM jobs. Virt guests can't create more virt guests. Might be
confusing if jobs fail on these test clients b/c they wouldn't support
Virt
1. Or, add the above logic to the setup() and teardown() methods of a new
autotest test class inherited from ''autotest/client/bin/test::test()''
which can be used by any AutoQA tests.
* Pros
* transparent to the tester
* allows us to maintain all autotest test clients as KVM guests
(don't need to worry about virt capable vs non-virt client systems)
* Cons
* might be a pain to administer, not sure ... would need to test
--
Ticket URL: <
https://fedorahosted.org/autoqa/ticket/128#comment:4>
AutoQA <
http://autoqa.fedorahosted.org>
Automated QA project