From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: autotest@test.kernel.org
Cc: Eduardo Habkost <ehabkost@redhat.com>, kvm@vger.kernel.org
Subject: [PATCH 2/8] KVM test: rename 'mode' to 'install_mode' on the sample cfg files
Date: Wed, 29 Dec 2010 20:37:24 -0200 [thread overview]
Message-ID: <1293662250-18292-3-git-send-email-lmr@redhat.com> (raw)
In-Reply-To: <1293662250-18292-1-git-send-email-lmr@redhat.com>
From: Eduardo Habkost <ehabkost@redhat.com>
The old name still works, but the new name is clearer.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
---
client/tests/kvm/build.cfg.sample | 14 +++++++-------
1 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/client/tests/kvm/build.cfg.sample b/client/tests/kvm/build.cfg.sample
index b6a20f7..a689ed4 100644
--- a/client/tests/kvm/build.cfg.sample
+++ b/client/tests/kvm/build.cfg.sample
@@ -16,7 +16,7 @@ variants:
save_results = no
variants:
- release:
- mode = release
+ install_mode = release
## Install from a kvm release. You can optionally specify
## a release tag. If you omit it, the build test will get
## the latest release tag available at that moment.
@@ -27,7 +27,7 @@ variants:
# files can be copied from there to your source based install
# path_to_rom_images = /usr/share/kvm
- snapshot:
- mode = snapshot
+ install_mode = snapshot
## Install from a kvm snapshot location. You can optionally
## specify a snapshot date. If you omit it, the test will get
## yesterday's snapshot.
@@ -37,21 +37,21 @@ variants:
# files can be copied from there to your source based install
# path_to_rom_images = /usr/share/kvm
- localtar:
- mode = localtar
+ install_mode = localtar
## Install from tarball located on the host's filesystem.
tarball = /tmp/kvm-84.tar.gz
# In some cases, you might want to provide a ROM dir, so ROM
# files can be copied from there to your source based install
# path_to_rom_images = /usr/share/kvm
- localsrc:
- mode = localsrc
+ install_mode = localsrc
## Install from tarball located on the host's filesystem.
srcdir = /tmp/kvm-84
# In some cases, you might want to provide a ROM dir, so ROM
# files can be copied from there to your source based install
# path_to_rom_images = /usr/share/kvm
- git:
- mode = git
+ install_mode = git
## Install KVM from git repositories.
## If you provide only "git_repo" and "user_git_repo", the
## build test will assume it will perform all build from the
@@ -80,7 +80,7 @@ variants:
# files can be copied from there to your source based install
# path_to_rom_images = /usr/share/kvm
- yum:
- mode = yum
+ install_mode = yum
src_pkg = qemu
## Name of the rpms we need installed
pkg_list = ['qemu-kvm', 'qemu-kvm-tools', 'qemu-system-x86', 'qemu-common', 'qemu-img']
@@ -89,7 +89,7 @@ variants:
## List of RPMs that will be installed
pkg_path_list = ['http://foo.com/rpm1', 'http://foo.com/rpm2']
- koji:
- mode = koji
+ install_mode = koji
## Install KVM from koji (Fedora build server)
## It is possible to install packages right from Koji if you
## provide a release tag or a build.
--
1.7.2.3
next prev parent reply other threads:[~2010-12-29 22:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 22:37 [PATCH 0/8] KVM test: Build code refactor + module_probe test Lucas Meneghel Rodrigues
2010-12-29 22:37 ` [PATCH 1/8] KVM test: Refactor the KVM build code into installer Lucas Meneghel Rodrigues
2010-12-29 22:37 ` Lucas Meneghel Rodrigues [this message]
2010-12-29 22:37 ` [PATCH 3/8] KVM test: add methods to store a installer object in 'env' Lucas Meneghel Rodrigues
2010-12-29 22:37 ` [PATCH 4/8] KVM test: Make the build test to use the installer library Lucas Meneghel Rodrigues
2010-12-29 22:37 ` [PATCH 5/8] KVM test: installer: fix the 'layout 1' detection Lucas Meneghel Rodrigues
2010-12-29 22:37 ` [PATCH 6/8] KVM test: load/unload kvm module Lucas Meneghel Rodrigues
2010-12-29 22:37 ` [PATCH 7/8] KVM test: add interface to get modules from cfg file, and load/unload them Lucas Meneghel Rodrigues
2010-12-29 22:37 ` [PATCH 8/8] KVM test: test/module_probe: use installer object to load modules Lucas Meneghel Rodrigues
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1293662250-18292-3-git-send-email-lmr@redhat.com \
--to=lmr@redhat.com \
--cc=autotest@test.kernel.org \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox