SSebastian MitterleUpdate Getting Started
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
docs: flatten the directory structure And leave four main sections on the main documentation page: * User's Guide * Advanced Topics and Maintenance * API Reference * Cartesian Config Reference The first three sections are identical to Avocado's docs, again in an attempt to make the two projects' documentations more consistent. Signed-off-by: Cleber Rosa <crosa@redhat.com> | 10 年前 | |
docs: flatten the directory structure And leave four main sections on the main documentation page: * User's Guide * Advanced Topics and Maintenance * API Reference * Cartesian Config Reference The first three sections are identical to Avocado's docs, again in an attempt to make the two projects' documentations more consistent. Signed-off-by: Cleber Rosa <crosa@redhat.com> | 10 年前 | |
docs: Fix foo.cfg syntax error in DefiningNewGuests.rst This fixes a syntax error in foo.cfg example of DefiningNewGuests.rst. Fixes https://github.com/avocado-framework/avocado-vt/issues/1189 Signed-off-by: Murilo Opsfelder Araujo <muriloo@linux.vnet.ibm.com> | 8 年前 | |
Virt Test Compatibility layer: Initial import This is the base code for the virt test compatibility layer. We arrived at this initial version of the code after significant work and previous reviews. Basically the compatibility layer aims to let people run virt-test tests inside avocado, giving them avocado specific features, and letting them to get used to the new avocado world. Changes from v3 (v13): * Fixed Ruda's comment about imp import; * Made the entire test source/runner plugin code to fit into 80 columns. Changes from v1 (v11): * The LICENSE file was fixed to state that the files inside the plugin are GPLv2+ licensed (GPLv2 or later), per adereis's comments. Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com> | 11 年前 | |
Virt Test Compatibility layer: Initial import This is the base code for the virt test compatibility layer. We arrived at this initial version of the code after significant work and previous reviews. Basically the compatibility layer aims to let people run virt-test tests inside avocado, giving them avocado specific features, and letting them to get used to the new avocado world. Changes from v3 (v13): * Fixed Ruda's comment about imp import; * Made the entire test source/runner plugin code to fit into 80 columns. Changes from v1 (v11): * The LICENSE file was fixed to state that the files inside the plugin are GPLv2+ licensed (GPLv2 or later), per adereis's comments. Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com> | 11 年前 | |
Documentation: Incorporate virt-test docs into avocado-vt Bring the old virt-test docs into avocado-vt, we can go on and do the cleanups on it at a later point. Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com> | 10 年前 | |
qemu_vm: Avoid vnc ports clash on migration The ports 590x are used for VNC (-vnc :0 => 5900) but the port of the currently processed VM is not yet taken so find_free_port has no chance on judging whether the port 5900 can be taken. This can happen with any port depending on the current -vnc index so let's just limit the available range to 5899 to completely avoid such clashes. Signed-off-by: Lukáš Doktor <ldoktor@redhat.com> | 6 年前 | |
docs: Update contact informations The virt-test-devel does not exist anymore and the irc channel is dormant. Signed-off-by: Lukáš Doktor <ldoktor@redhat.com> | 8 年前 | |
Change default doc highlighting and fix typos The default Sphinx highlighting language is python is not explicitly specified. When using next-version Sphinx (>=1.4a) to build docs with non-python snippets without highlighting language specified will cause a warning message: WARNING: Could not lex literal_block as "python3". Highlighting skipped. This fix change default highlighting language to none and explicitly specify highlighting languages each snippets pygments supported. This fix also fixed several typos. Signed-off-by: Hao Liu <hliu@redhat.com> | 10 年前 | |
cartesian_config: Introduce the new operator '~=' Introduce the new operator ~= to support variable lazy assignment, which means a variable will be set only if it has not been defined in previous frames during configuration parsing. For example, by given the following configuration, the value of the variable foo should be "bar", foo ~= bar whereas, by given the following configuration, the value of the variable foo would still be "bar". foo = bar foo ~= foo This might be useful for generating configuration under uncertain conditions. For instance, we can set smp by using the value of vcpu_maxcpus in the case of smp is not being set, otherwise, let smp be what it was. Signed-off-by: Xu Han <xuhan@redhat.com> | 6 年前 | |
docs: Add note where to download virtio-win drivers ISO This ISO is used for windows testing, it makes sense to add information where to download it to our docs. Signed-off-by: Lukáš Doktor <ldoktor@redhat.com> | 7 年前 | |
docs: Add documentation on how to use TCG with Avocado-vt Running emulation especially on different architectures is fairly simple with Avocado-vt, but not many people use it. It is increasingly necessary especially with people from other architectures contributing arch-dependent patches to Avocado-vt so let's provide a guide for people to simplify cross-platform testing. Signed-off-by: Lukáš Doktor <ldoktor@redhat.com> | 7 年前 | |
Update Getting Started 1. Avocado doc has been restructured: fix broken links 2. Give more priority to pip installation: a. It's the primary installation method for Avocado (s. doc https://avocado-framework.readthedocs.io/en/latest/guides/user/chapters/installing.html "Avocado is primarily written in Python, so a standard Python installation is possible and often preferable. You can also install from your distro repository, if available." etc.) b. Pip installation is available on more environments. c. Whoever wants to develop/debug test cases is better off with pip installation. 3. Recommend to use the same installation method for both plugin and main program: a. Mixing both methods can lead to issues due to version incompatibility and command availability. 4. Add python-devel as dependency: I got installation error from dependency netifaces (Python.h: No such file or directory) 5. Add a note that test backend related progrmas should be available on target system in order to list test cases. 6. As consequence of GetStartedGuide: Add virsh to recommended programs for qemu test backend because Networking is usually done using libvirtd's virbr0 - s. https://avocado-vt.readthedocs.io/en/latest/Networking.html A user following the GetStartedGuide and gets to the point where they randomly chose any test, e.g. lvm.lvm_create for execution from avocado list --vt-type qemu will just see "ERROR: Can't add interface ... to bridge virbr0: there is no bridge in the system." It's not enough for them to just add a bridge of that name, so it can become quite tedious. By having the virsh already as a recommended program the user can at least try install it which would then automatically set up the default network with correct bridge. | 6 年前 | |
docs: Fix broken links Signed-off-by: Sergey Bronnikov <sergeyb@bronevichok.ru> | 7 年前 | |
Fix nits in the doc Spend few hours reading the doc and found some nits related to typo, format, ref, etc., this fix did not include update on the setup and testing. Signed-off-by: Wayne Sun <gsun@redhat.com> | 10 年前 | |
Shifting from 7z to xz 7z is only available in EPEL for on some archs, but xz is available in stock repos for EL. Hence shifting from 7z for compression and decompression of JeOS images to xz. Reference: https://trello.com/c/hJiQaKPu Signed-off-by: Greeshma Gopinath <ggopinat@redhat.com> Signed-off-by: Cleber Rosa <crosa@redhat.com> | 9 年前 | |
docs: Add note where to download virtio-win drivers ISO This ISO is used for windows testing, it makes sense to add information where to download it to our docs. Signed-off-by: Lukáš Doktor <ldoktor@redhat.com> | 7 年前 | |
Change default doc highlighting and fix typos The default Sphinx highlighting language is python is not explicitly specified. When using next-version Sphinx (>=1.4a) to build docs with non-python snippets without highlighting language specified will cause a warning message: WARNING: Could not lex literal_block as "python3". Highlighting skipped. This fix change default highlighting language to none and explicitly specify highlighting languages each snippets pygments supported. This fix also fixed several typos. Signed-off-by: Hao Liu <hliu@redhat.com> | 10 年前 | |
Update ListingGuests.rst | 9 年前 | |
Shifting from 7z to xz 7z is only available in EPEL for on some archs, but xz is available in stock repos for EL. Hence shifting from 7z for compression and decompression of JeOS images to xz. Reference: https://trello.com/c/hJiQaKPu Signed-off-by: Greeshma Gopinath <ggopinat@redhat.com> Signed-off-by: Cleber Rosa <crosa@redhat.com> | 9 年前 | |
docs: Fix broken links Signed-off-by: Sergey Bronnikov <sergeyb@bronevichok.ru> | 7 年前 | |
Job lock: plugin that prevents multiple runs of VT jobs This introduces a Pre/Post Job type of plugin, that attempts to create a lock file in a common location before the job is started, and remove the lock file after the job has finished. The goal is to prevent multiple runs of avocado (with VT tests) to corrupt files such as guest OS images. It's still possible to have multiple parallel jobs running on the same machine, as long as their configuration point to different lock directories, which should follow different data directories, to prevent the original problem of data file corruption. The mechanism used for locking is a simplistic one, similar to daemon PID files. It should be possible to either rewrite or improve the lock mechanism completely without bringing changes to the user expected behavior of, by default, not having multiple Avocado-VT jobs run at once. While testing for parallel execution of VT and non-VT jobs, it was found that the VT loader had a number of issues that make it fail to run in parallel. Thse have been fixed and the attempt to execute jobs in parallel works as expected. References: https://trello.com/c/hxqiVZCy References: https://trello.com/c/7xEPKDsJ Signed-off-by: Cleber Rosa <crosa@redhat.com> | 10 年前 | |
docs: Fix broken links Signed-off-by: Sergey Bronnikov <sergeyb@bronevichok.ru> | 7 年前 | |
docs: Fix broken links Signed-off-by: Sergey Bronnikov <sergeyb@bronevichok.ru> | 7 年前 | |
docs: Update kvm-unit-tests documentation The kvm-unit-tests can be run using avocado with per-test granularity. This patch adds the documentation on how to do this while it keeps the original avocado-vt documentation as people might prefer that (although it's harder to setup and provides only overall results). Signed-off-by: Lukáš Doktor <ldoktor@redhat.com> | 9 年前 | |
docs: Add note to RunningEmulationTCG about JeOS-RHEL When running in emulation, unattended install is a big overhead. Let's add a note about "fake" RHEL created from JeOS. It's obviously not the same thing, but for Avocado-vt checks should do. (I'm using it for PR checking and it works just fine). Signed-off-by: Lukáš Doktor <ldoktor@redhat.com> | 7 年前 | |
Change default doc highlighting and fix typos The default Sphinx highlighting language is python is not explicitly specified. When using next-version Sphinx (>=1.4a) to build docs with non-python snippets without highlighting language specified will cause a warning message: WARNING: Could not lex literal_block as "python3". Highlighting skipped. This fix change default highlighting language to none and explicitly specify highlighting languages each snippets pygments supported. This fix also fixed several typos. Signed-off-by: Hao Liu <hliu@redhat.com> | 10 年前 | |
Python 3: Update commands module 1. Commands module redirect stderr to stdout, but subprocess could not do it 2. The output of subprocess is bytes in Python3 Signed-off-by: Junxiang Li <junli@redhat.com> | 8 年前 | |
docs: Add documentation on how to use TCG with Avocado-vt Running emulation especially on different architectures is fairly simple with Avocado-vt, but not many people use it. It is increasingly necessary especially with people from other architectures contributing arch-dependent patches to Avocado-vt so let's provide a guide for people to simplify cross-platform testing. Signed-off-by: Lukáš Doktor <ldoktor@redhat.com> | 7 年前 |