Attachment 710696 Details for Bug 921238 – patch to rename hwc -> hwcert-backend and add hwcert command

[patch] patch to rename hwc -> hwcert-backend and add hwcert command

rename.patch (text/plain), 42.97 KB, created by Greg Nichols on 2013-03-15 14:40:27 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Greg Nichols

Created: 2013-03-15 14:40:27 UTC

Size: 42.97 KB

patch

obsolete

>diff --git a/Makefile b/Makefile
>index 577fc5e..e94d6cc 100644
>--- a/Makefile
>+++ b/Makefile
>@@ -77,8 +77,8 @@ hwcert-server-$(HWCERT_VERSION_RELEASE).el$(HWCERT_RHEL_VERSION).tar.bz2: /tmp/h
> 	echo "save" >> $@
> 	echo ".*" >> $@
> 	echo ".patch" >> $@
>-	echo "hwcert/*.pyc" >> $@
>-	echo "test-env/bin/*.pyc" >> $@
>+	echo "*.pyc" >> $@
>+	echo "*.pyo" >> $@
> 	echo "*.bz2" >> $@
> 	echo "hwcertClientSpec.*" >> $@
> 
>diff --git a/docs/man/Makefile b/docs/man/Makefile
>index 860144f..ba9c2a9 100644
>--- a/docs/man/Makefile
>+++ b/docs/man/Makefile
>@@ -17,21 +17,27 @@
> 
> 
> clean:
>-	rm -f $(DESTDIR)/usr/share/man/man8/hwc.8.gz
>+	rm -f $(DESTDIR)/usr/share/man/man8/hwcert.8.gz
>+	rm -f $(DESTDIR)/usr/share/man/man8/hwcert-backend.8.gz
> 	rm -f $(DESTDIR)/var/hwcert/docs/hwcert-man.html
>-	rm -f /var/cache/man/cat1/hwc.8.bz2
>-	rm -f hwc.8
>+	rm -f $(DESTDIR)/var/hwcert/docs/hwcert-backend-man.html
>+	rm -f /var/cache/man/cat1/hwcert.8.bz2
>+	rm -f /var/cache/man/cat1/hwcert-backend.8.bz2
>+	rm -f hwcert.8
>+	rm -f hwcert-backend.8
> 
> install-noarch: install
> 
> install:
>-	cat hwc.8.in | sed -e 's/@HWCERT_VERSION@/$(HWCERT_VERSION)/g' -e 's/@HWCERT_RELEASE@/$(HWCERT_RELEASE)/g' > hwc.8
>+	cat hwcert.8.in | sed -e 's/@HWCERT_VERSION@/$(HWCERT_VERSION)/g' -e 's/@HWCERT_RELEASE@/$(HWCERT_RELEASE)/g' > hwcert.8
>+	cat hwcert-backend.8.in | sed -e 's/@HWCERT_VERSION@/$(HWCERT_VERSION)/g' -e 's/@HWCERT_RELEASE@/$(HWCERT_RELEASE)/g' > hwcert-backend.8
> 	mkdir -p $(DESTDIR)/usr/share/man/man8
>-	gzip hwc.8 -c > $(DESTDIR)/usr/share/man/man8/hwc.8.gz
>+	gzip hwcert.8 -c > $(DESTDIR)/usr/share/man/man8/hwcert.8.gz
>+	gzip hwcert-backend.8 -c > $(DESTDIR)/usr/share/man/man8/hwcert-backend.8.gz
> 	
> install-server:
> 	mkdir -p $(DESTDIR)/var/hwcert/docs
>-	if test -s /usr/bin/man2html; then /usr/bin/man2html hwc.8 > $(DESTDIR)/var/hwcert/docs/index.html; fi
>+	if test -s /usr/bin/man2html; then /usr/bin/man2html hwcert.8 hwcert-backend.8 > $(DESTDIR)/var/hwcert/docs/index.html; fi
> 
> 	
> 
>diff --git a/docs/man/hwc.8.in b/docs/man/hwc.8.in
>deleted file mode 100644
>index 789cf42..0000000
>--- a/docs/man/hwc.8.in
>+++ /dev/null
>@@ -1,313 +0,0 @@
>-.TH hwc 8  Red Hat
>-
>-.SH NAME
>-hwc - The Red Hat Hardware Certification Test Suite, version 
>-@HWCERT_VERSION@, release @HWCERT_RELEASE@.
>-
>-.SH SYNOPSIS
>-
>-.B "hwc ["
>-.I command
>-.B "] ["
>-.I options
>-.B ]
>-
>-.SH OVERVIEW
>-
>-hwcert is the hardware certification test suite for Red Hat Enterprise Linux.   
>-hwcert is comprised of a suite of tests intended to verify compatibility of the 
>-hardware devices and functions.
>-
>-Each hwcert test run builds a test results database that is submitted
>-to Red Hat by uploading to a certification request in Red Hat's Hardware Catalog.
>-
>-.SS General Options
>-
>-.B --debug {low | medium | high}
>-
>-This option enables debugging output.  Note that test results with --debug set may not
>-be acceptable for certification.
>-
>-.B --help
>-
>-Prints a list of available commands and options.
>-
>-.B --mode { normal | auto }
>-
>-In 
>-.I auto
>-mode, hwcert runs non-interactively to the extent possible.   Some user confirmations and prompts will be skipped and reasonable options assumed.  The default mode is 
>-.I normal,
>-which will prompt the user for test options and confirm significant actions taken.
>-
>-.SH hwc COMMANDS
>-
>-.SS certify
>-.B hwc certify  [ --tag <test tag> ]
>-
>-The 
>-.I certify
>-command runs all tests that have not yet passed.
>-
>-.IP Options
>-
>-.B --tag 
>-<test tag>
>-
>-If test tags are used, then hwc will run tests with the given tag(s) that have not yet passed.   This option may appear multiple times for multiple tags.
>-Interactive tests may be selected with the 
>-.I interactive
>-tag.  Similarly, non-interactive tests may be chosen with the 
>-.I non-interactive
>-tag.   If the option is not present, the 
>-.I certification
>-tag is assumed.  Available tags for the planned tests may be displayed using the print command.
>-
>-.SS clean
>-.B hwc clean
>-.P
>-The 
>-.I clean 
>-command deletes the test results database.
>-
>-
>-.IP Options
>-
>-.B all
>-
>-.B hwc clean all
>-also prompts for removal of certification data from the test results database,
>-such as vendor, make and model, and any linked certification request in the Hardware Catalog.
>-
>-.SS continue
>-.B hwc continue
>-.P
>-The 
>-.I continue 
>-command will continue a test run that has been interrupted.
>-
>-.SS plan
>-.P
>-.B hwc plan [ ( --disable | --enable | --add) (--test <testname> | --udi <udi> | --device <device>) [--server <hwc server host>] [--model] 
>-
>-.P
>-The plan command analyzes the hardware devices and system configuration
>-to determine which tests from the suite are applicable to certification.
>-
>-hwc will prompt for certification information, such as the hardware vendor, make and model, as well
>-as a product URL and category.   If the Hardware Catalog is reachable, hwc will prompt for or create 
>-a new certification request on the Hardware Catalog and link it to the test results.
>-
>-Depending on tests planned, hwc may also prompt for the installation of additional RPM packages required for testing.
>-
>-.IP Options
>-
>-.B --disable
>-
>-Disables a test in the test plan - the certify command will skip disabled tests. The test(s) to be disabled may be indicated using 
>-the --test --udi, or --device options.
>-
>-.B --enable
>-
>-Re-enables a disabled test. The test(s) to be enabled may be indicated using the --test --udi, or --device options.
>-
>-.B --add
>-
>-Adds a test. both --test and --udi or --device must be supplied to indicate both the test to be added, and the device to be tested.
>-
>-.B --test 
>-<testname>
>-
>-Specifies test(s) in an existing test plan to be modified. This option may be repeated to specify multiple tests.
>-
>-.B --udi 
>-<udi>
>-
>-Specifies test(s) in an existing test plan to be modified. The UDI for specific devices may be found via the "info.udi" attribute Device Manager's Advanced tab. This option may be repeated to specify multiple UDIs. This option is not supported when certifying RHEL 4.
>-
>-.B --device 
>-<device>
>-
>-A logical device name indicating the device to be tested. Logical device names are typically the device names under the /dev directory.
>-
>-.B --server 
>-<hwc server host>
>-
>-Specifies the hwc Server host name to be used for the specific test identified using the --test, --udi and --device parameters. This setting overrides the hwc server setting for the test plan.
>-
>-.B --model
>-
>-Prompts the user to edit vendor, make and model information in the test plan.  It also allows the 
>-link to the Hardware Catalog 
>-certification request to be changed, or a new request created.
>-
>-.SS print
>-.P
>-.B hwc print [--report (plan|summary|full) ] [ --udi <udi> | --test <test name> | --device <device name>] [--failures] [--last]
>-.P
>-The
>-.I print
>-command prints the test plan or test results to standard output, in human-readable form. 
>-The Options allow you to generate a summary and to select various test results.
>-
>-.IP Options
>-
>-.B --report (plan|summary|full)
>-
>-The format of the report to be output.  
>-
>-.B --udi 
>-<udi>
>-
>-Show test results for devices matching the supplied HAL udi.
>-
>-.B --test 
>-<test name>
>-
>-Show results for a specific test.
>-
>-.B --device 
>-<device name>
>-
>-Show results for test runs matching the supplied logical device name.
>-
>-.B --failures
>-
>-Show only test failures.
>-
>-.B --last
>-
>-Show only the most recent test run.
>-
>-.B --tag
>-<test tag>
>-
>-Print results for tests with the test tag(s).
>-
>-
>-.I plan 
>-prints the test plan, and is the default format if there are no test results.  
>-
>-.I summary 
>-print past/fail results totals for each test
>-
>-.I full 
>-prints complete test results and logging output.
>-
>-
>-.SS run
>-.P
>-.B hwc run [ (--test <test name> | --udi <udi> | --device <device name>) (--tag <test tag> )] [ --server <server host name> ]
>-
>-.P
>-The
>-.I run 
>-command allows specific tests to be run.   The SUT's hardware device list will be 
>-re-analyzed to determine if the new test run data should be appended to the results, 
>-or a new results database should be created for changes in hardware.
>-
>-.IP Options
>-
>-.B --test 
>-<test name>
>-
>-Specifies that a specific test should be run for any relevant device. This option may be repeated to specify multiple tests.
>-
>-.B --udi 
>-<udi>
>-
>-Only tests of the specified device should be run. This option may be repeated to specify multiple UDIs.
>-
>-.B --device
>-<udi>
>-
>-Only tests of the specified device logical name should be run. This option may be repeated to specify multiple devices.
>-
>-.B --tag
>-<test tag>
>-
>-hwc will run tests with the given tag(s).  This option may appear multiple times for multiple tags.
>-Interactive tests may be selected with the 
>-.I interactive
>-tag.  Similarly, non-interactive tests may be chosen with the 
>-.I non-interactive
>-tag.   Available tags for the planned tests may be displayed using the print command.
>-
>-.B --server 
>-<server host hame>
>-
>-host name of the server running the hwc test server, required for some tests, such as network.
>-
>-
>-
>-.SS save
>-.P 
>-.B hwc save [--server <hwc server host>]
>-.P
>-The
>-.I save
>-command copies the test results to /var/hwc/store for later reference.  If 
>-.I --server
>-is set, it will also prompt to upload a copy of the test results to the hwc-server.
>-
>-
>-.SS server
>-.P 
>-.B hwc server {start | status | stop | daemon}
>-.P
>-The
>-.I server
>-command controls the hwc Test Server, which is run on a system separate from the
>-SUT to support the network, fencing, and virtualization tests.  The hwc server may also 
>-be run on the SUT to allow access and review of test results via http://<hostname>/hwc/
>-
>-The
>-.I daemon 
>-option stops the hwc server daemon process, and restarts it in foreground.   The hwc daemon
>-process is used for tests such as the fencing test where server-side tests must be run.
>-
>-.SS submit
>-.P
>-.B hwc submit
>-.P
>-.I Submit
>-uploads the test results to the Hardware Catalog.  If
>-.I --mode 
>-is set to 
>-.I auto
>-hwc will package the test results into an RPM.
>-
>-.SS verify
>-.P
>-.B hwc verify
>-.P
>-The verify command checks configuration requirements for the tests without actually
>-running the tests.   Test verification is also run as part of the
>-.I certify
>-and
>-.I run
>-commands.
>-
>-.SS version
>-.P
>-.B hwc version
>-.P
>-Prints the version and release of hwc.
>-
>-.SH FILES
>-
>-.B /etc/hwcert.xml 
>-- configuration of directory locations
>-
>-.B /usr/share/hwcert 
>-- hwc harness and test source files
>-
>-.B /var/hwcert 
>-- hwc data files and test results for hwc-client on the SUT
>-
>-.B /var/www/hwcert
>-- The and web/NFS root for hwcert-server
>-
>-
>-
>-
>diff --git a/docs/man/hwcert-backend.8.in b/docs/man/hwcert-backend.8.in
>new file mode 100644
>index 0000000..789cf42
>--- /dev/null
>+++ b/docs/man/hwcert-backend.8.in
>@@ -0,0 +1,313 @@
>+.TH hwc 8  Red Hat
>+
>+.SH NAME
>+hwc - The Red Hat Hardware Certification Test Suite, version 
>+@HWCERT_VERSION@, release @HWCERT_RELEASE@.
>+
>+.SH SYNOPSIS
>+
>+.B "hwc ["
>+.I command
>+.B "] ["
>+.I options
>+.B ]
>+
>+.SH OVERVIEW
>+
>+hwcert is the hardware certification test suite for Red Hat Enterprise Linux.   
>+hwcert is comprised of a suite of tests intended to verify compatibility of the 
>+hardware devices and functions.
>+
>+Each hwcert test run builds a test results database that is submitted
>+to Red Hat by uploading to a certification request in Red Hat's Hardware Catalog.
>+
>+.SS General Options
>+
>+.B --debug {low | medium | high}
>+
>+This option enables debugging output.  Note that test results with --debug set may not
>+be acceptable for certification.
>+
>+.B --help
>+
>+Prints a list of available commands and options.
>+
>+.B --mode { normal | auto }
>+
>+In 
>+.I auto
>+mode, hwcert runs non-interactively to the extent possible.   Some user confirmations and prompts will be skipped and reasonable options assumed.  The default mode is 
>+.I normal,
>+which will prompt the user for test options and confirm significant actions taken.
>+
>+.SH hwc COMMANDS
>+
>+.SS certify
>+.B hwc certify  [ --tag <test tag> ]
>+
>+The 
>+.I certify
>+command runs all tests that have not yet passed.
>+
>+.IP Options
>+
>+.B --tag 
>+<test tag>
>+
>+If test tags are used, then hwc will run tests with the given tag(s) that have not yet passed.   This option may appear multiple times for multiple tags.
>+Interactive tests may be selected with the 
>+.I interactive
>+tag.  Similarly, non-interactive tests may be chosen with the 
>+.I non-interactive
>+tag.   If the option is not present, the 
>+.I certification
>+tag is assumed.  Available tags for the planned tests may be displayed using the print command.
>+
>+.SS clean
>+.B hwc clean
>+.P
>+The 
>+.I clean 
>+command deletes the test results database.
>+
>+
>+.IP Options
>+
>+.B all
>+
>+.B hwc clean all
>+also prompts for removal of certification data from the test results database,
>+such as vendor, make and model, and any linked certification request in the Hardware Catalog.
>+
>+.SS continue
>+.B hwc continue
>+.P
>+The 
>+.I continue 
>+command will continue a test run that has been interrupted.
>+
>+.SS plan
>+.P
>+.B hwc plan [ ( --disable | --enable | --add) (--test <testname> | --udi <udi> | --device <device>) [--server <hwc server host>] [--model] 
>+
>+.P
>+The plan command analyzes the hardware devices and system configuration
>+to determine which tests from the suite are applicable to certification.
>+
>+hwc will prompt for certification information, such as the hardware vendor, make and model, as well
>+as a product URL and category.   If the Hardware Catalog is reachable, hwc will prompt for or create 
>+a new certification request on the Hardware Catalog and link it to the test results.
>+
>+Depending on tests planned, hwc may also prompt for the installation of additional RPM packages required for testing.
>+
>+.IP Options
>+
>+.B --disable
>+
>+Disables a test in the test plan - the certify command will skip disabled tests. The test(s) to be disabled may be indicated using 
>+the --test --udi, or --device options.
>+
>+.B --enable
>+
>+Re-enables a disabled test. The test(s) to be enabled may be indicated using the --test --udi, or --device options.
>+
>+.B --add
>+
>+Adds a test. both --test and --udi or --device must be supplied to indicate both the test to be added, and the device to be tested.
>+
>+.B --test 
>+<testname>
>+
>+Specifies test(s) in an existing test plan to be modified. This option may be repeated to specify multiple tests.
>+
>+.B --udi 
>+<udi>
>+
>+Specifies test(s) in an existing test plan to be modified. The UDI for specific devices may be found via the "info.udi" attribute Device Manager's Advanced tab. This option may be repeated to specify multiple UDIs. This option is not supported when certifying RHEL 4.
>+
>+.B --device 
>+<device>
>+
>+A logical device name indicating the device to be tested. Logical device names are typically the device names under the /dev directory.
>+
>+.B --server 
>+<hwc server host>
>+
>+Specifies the hwc Server host name to be used for the specific test identified using the --test, --udi and --device parameters. This setting overrides the hwc server setting for the test plan.
>+
>+.B --model
>+
>+Prompts the user to edit vendor, make and model information in the test plan.  It also allows the 
>+link to the Hardware Catalog 
>+certification request to be changed, or a new request created.
>+
>+.SS print
>+.P
>+.B hwc print [--report (plan|summary|full) ] [ --udi <udi> | --test <test name> | --device <device name>] [--failures] [--last]
>+.P
>+The
>+.I print
>+command prints the test plan or test results to standard output, in human-readable form. 
>+The Options allow you to generate a summary and to select various test results.
>+
>+.IP Options
>+
>+.B --report (plan|summary|full)
>+
>+The format of the report to be output.  
>+
>+.B --udi 
>+<udi>
>+
>+Show test results for devices matching the supplied HAL udi.
>+
>+.B --test 
>+<test name>
>+
>+Show results for a specific test.
>+
>+.B --device 
>+<device name>
>+
>+Show results for test runs matching the supplied logical device name.
>+
>+.B --failures
>+
>+Show only test failures.
>+
>+.B --last
>+
>+Show only the most recent test run.
>+
>+.B --tag
>+<test tag>
>+
>+Print results for tests with the test tag(s).
>+
>+
>+.I plan 
>+prints the test plan, and is the default format if there are no test results.  
>+
>+.I summary 
>+print past/fail results totals for each test
>+
>+.I full 
>+prints complete test results and logging output.
>+
>+
>+.SS run
>+.P
>+.B hwc run [ (--test <test name> | --udi <udi> | --device <device name>) (--tag <test tag> )] [ --server <server host name> ]
>+
>+.P
>+The
>+.I run 
>+command allows specific tests to be run.   The SUT's hardware device list will be 
>+re-analyzed to determine if the new test run data should be appended to the results, 
>+or a new results database should be created for changes in hardware.
>+
>+.IP Options
>+
>+.B --test 
>+<test name>
>+
>+Specifies that a specific test should be run for any relevant device. This option may be repeated to specify multiple tests.
>+
>+.B --udi 
>+<udi>
>+
>+Only tests of the specified device should be run. This option may be repeated to specify multiple UDIs.
>+
>+.B --device
>+<udi>
>+
>+Only tests of the specified device logical name should be run. This option may be repeated to specify multiple devices.
>+
>+.B --tag
>+<test tag>
>+
>+hwc will run tests with the given tag(s).  This option may appear multiple times for multiple tags.
>+Interactive tests may be selected with the 
>+.I interactive
>+tag.  Similarly, non-interactive tests may be chosen with the 
>+.I non-interactive
>+tag.   Available tags for the planned tests may be displayed using the print command.
>+
>+.B --server 
>+<server host hame>
>+
>+host name of the server running the hwc test server, required for some tests, such as network.
>+
>+
>+
>+.SS save
>+.P 
>+.B hwc save [--server <hwc server host>]
>+.P
>+The
>+.I save
>+command copies the test results to /var/hwc/store for later reference.  If 
>+.I --server
>+is set, it will also prompt to upload a copy of the test results to the hwc-server.
>+
>+
>+.SS server
>+.P 
>+.B hwc server {start | status | stop | daemon}
>+.P
>+The
>+.I server
>+command controls the hwc Test Server, which is run on a system separate from the
>+SUT to support the network, fencing, and virtualization tests.  The hwc server may also 
>+be run on the SUT to allow access and review of test results via http://<hostname>/hwc/
>+
>+The
>+.I daemon 
>+option stops the hwc server daemon process, and restarts it in foreground.   The hwc daemon
>+process is used for tests such as the fencing test where server-side tests must be run.
>+
>+.SS submit
>+.P
>+.B hwc submit
>+.P
>+.I Submit
>+uploads the test results to the Hardware Catalog.  If
>+.I --mode 
>+is set to 
>+.I auto
>+hwc will package the test results into an RPM.
>+
>+.SS verify
>+.P
>+.B hwc verify
>+.P
>+The verify command checks configuration requirements for the tests without actually
>+running the tests.   Test verification is also run as part of the
>+.I certify
>+and
>+.I run
>+commands.
>+
>+.SS version
>+.P
>+.B hwc version
>+.P
>+Prints the version and release of hwc.
>+
>+.SH FILES
>+
>+.B /etc/hwcert.xml 
>+- configuration of directory locations
>+
>+.B /usr/share/hwcert 
>+- hwc harness and test source files
>+
>+.B /var/hwcert 
>+- hwc data files and test results for hwc-client on the SUT
>+
>+.B /var/www/hwcert
>+- The and web/NFS root for hwcert-server
>+
>+
>+
>+
>diff --git a/docs/man/hwcert.8.in b/docs/man/hwcert.8.in
>new file mode 100644
>index 0000000..789cf42
>--- /dev/null
>+++ b/docs/man/hwcert.8.in
>@@ -0,0 +1,313 @@
>+.TH hwc 8  Red Hat
>+
>+.SH NAME
>+hwc - The Red Hat Hardware Certification Test Suite, version 
>+@HWCERT_VERSION@, release @HWCERT_RELEASE@.
>+
>+.SH SYNOPSIS
>+
>+.B "hwc ["
>+.I command
>+.B "] ["
>+.I options
>+.B ]
>+
>+.SH OVERVIEW
>+
>+hwcert is the hardware certification test suite for Red Hat Enterprise Linux.   
>+hwcert is comprised of a suite of tests intended to verify compatibility of the 
>+hardware devices and functions.
>+
>+Each hwcert test run builds a test results database that is submitted
>+to Red Hat by uploading to a certification request in Red Hat's Hardware Catalog.
>+
>+.SS General Options
>+
>+.B --debug {low | medium | high}
>+
>+This option enables debugging output.  Note that test results with --debug set may not
>+be acceptable for certification.
>+
>+.B --help
>+
>+Prints a list of available commands and options.
>+
>+.B --mode { normal | auto }
>+
>+In 
>+.I auto
>+mode, hwcert runs non-interactively to the extent possible.   Some user confirmations and prompts will be skipped and reasonable options assumed.  The default mode is 
>+.I normal,
>+which will prompt the user for test options and confirm significant actions taken.
>+
>+.SH hwc COMMANDS
>+
>+.SS certify
>+.B hwc certify  [ --tag <test tag> ]
>+
>+The 
>+.I certify
>+command runs all tests that have not yet passed.
>+
>+.IP Options
>+
>+.B --tag 
>+<test tag>
>+
>+If test tags are used, then hwc will run tests with the given tag(s) that have not yet passed.   This option may appear multiple times for multiple tags.
>+Interactive tests may be selected with the 
>+.I interactive
>+tag.  Similarly, non-interactive tests may be chosen with the 
>+.I non-interactive
>+tag.   If the option is not present, the 
>+.I certification
>+tag is assumed.  Available tags for the planned tests may be displayed using the print command.
>+
>+.SS clean
>+.B hwc clean
>+.P
>+The 
>+.I clean 
>+command deletes the test results database.
>+
>+
>+.IP Options
>+
>+.B all
>+
>+.B hwc clean all
>+also prompts for removal of certification data from the test results database,
>+such as vendor, make and model, and any linked certification request in the Hardware Catalog.
>+
>+.SS continue
>+.B hwc continue
>+.P
>+The 
>+.I continue 
>+command will continue a test run that has been interrupted.
>+
>+.SS plan
>+.P
>+.B hwc plan [ ( --disable | --enable | --add) (--test <testname> | --udi <udi> | --device <device>) [--server <hwc server host>] [--model] 
>+
>+.P
>+The plan command analyzes the hardware devices and system configuration
>+to determine which tests from the suite are applicable to certification.
>+
>+hwc will prompt for certification information, such as the hardware vendor, make and model, as well
>+as a product URL and category.   If the Hardware Catalog is reachable, hwc will prompt for or create 
>+a new certification request on the Hardware Catalog and link it to the test results.
>+
>+Depending on tests planned, hwc may also prompt for the installation of additional RPM packages required for testing.
>+
>+.IP Options
>+
>+.B --disable
>+
>+Disables a test in the test plan - the certify command will skip disabled tests. The test(s) to be disabled may be indicated using 
>+the --test --udi, or --device options.
>+
>+.B --enable
>+
>+Re-enables a disabled test. The test(s) to be enabled may be indicated using the --test --udi, or --device options.
>+
>+.B --add
>+
>+Adds a test. both --test and --udi or --device must be supplied to indicate both the test to be added, and the device to be tested.
>+
>+.B --test 
>+<testname>
>+
>+Specifies test(s) in an existing test plan to be modified. This option may be repeated to specify multiple tests.
>+
>+.B --udi 
>+<udi>
>+
>+Specifies test(s) in an existing test plan to be modified. The UDI for specific devices may be found via the "info.udi" attribute Device Manager's Advanced tab. This option may be repeated to specify multiple UDIs. This option is not supported when certifying RHEL 4.
>+
>+.B --device 
>+<device>
>+
>+A logical device name indicating the device to be tested. Logical device names are typically the device names under the /dev directory.
>+
>+.B --server 
>+<hwc server host>
>+
>+Specifies the hwc Server host name to be used for the specific test identified using the --test, --udi and --device parameters. This setting overrides the hwc server setting for the test plan.
>+
>+.B --model
>+
>+Prompts the user to edit vendor, make and model information in the test plan.  It also allows the 
>+link to the Hardware Catalog 
>+certification request to be changed, or a new request created.
>+
>+.SS print
>+.P
>+.B hwc print [--report (plan|summary|full) ] [ --udi <udi> | --test <test name> | --device <device name>] [--failures] [--last]
>+.P
>+The
>+.I print
>+command prints the test plan or test results to standard output, in human-readable form. 
>+The Options allow you to generate a summary and to select various test results.
>+
>+.IP Options
>+
>+.B --report (plan|summary|full)
>+
>+The format of the report to be output.  
>+
>+.B --udi 
>+<udi>
>+
>+Show test results for devices matching the supplied HAL udi.
>+
>+.B --test 
>+<test name>
>+
>+Show results for a specific test.
>+
>+.B --device 
>+<device name>
>+
>+Show results for test runs matching the supplied logical device name.
>+
>+.B --failures
>+
>+Show only test failures.
>+
>+.B --last
>+
>+Show only the most recent test run.
>+
>+.B --tag
>+<test tag>
>+
>+Print results for tests with the test tag(s).
>+
>+
>+.I plan 
>+prints the test plan, and is the default format if there are no test results.  
>+
>+.I summary 
>+print past/fail results totals for each test
>+
>+.I full 
>+prints complete test results and logging output.
>+
>+
>+.SS run
>+.P
>+.B hwc run [ (--test <test name> | --udi <udi> | --device <device name>) (--tag <test tag> )] [ --server <server host name> ]
>+
>+.P
>+The
>+.I run 
>+command allows specific tests to be run.   The SUT's hardware device list will be 
>+re-analyzed to determine if the new test run data should be appended to the results, 
>+or a new results database should be created for changes in hardware.
>+
>+.IP Options
>+
>+.B --test 
>+<test name>
>+
>+Specifies that a specific test should be run for any relevant device. This option may be repeated to specify multiple tests.
>+
>+.B --udi 
>+<udi>
>+
>+Only tests of the specified device should be run. This option may be repeated to specify multiple UDIs.
>+
>+.B --device
>+<udi>
>+
>+Only tests of the specified device logical name should be run. This option may be repeated to specify multiple devices.
>+
>+.B --tag
>+<test tag>
>+
>+hwc will run tests with the given tag(s).  This option may appear multiple times for multiple tags.
>+Interactive tests may be selected with the 
>+.I interactive
>+tag.  Similarly, non-interactive tests may be chosen with the 
>+.I non-interactive
>+tag.   Available tags for the planned tests may be displayed using the print command.
>+
>+.B --server 
>+<server host hame>
>+
>+host name of the server running the hwc test server, required for some tests, such as network.
>+
>+
>+
>+.SS save
>+.P 
>+.B hwc save [--server <hwc server host>]
>+.P
>+The
>+.I save
>+command copies the test results to /var/hwc/store for later reference.  If 
>+.I --server
>+is set, it will also prompt to upload a copy of the test results to the hwc-server.
>+
>+
>+.SS server
>+.P 
>+.B hwc server {start | status | stop | daemon}
>+.P
>+The
>+.I server
>+command controls the hwc Test Server, which is run on a system separate from the
>+SUT to support the network, fencing, and virtualization tests.  The hwc server may also 
>+be run on the SUT to allow access and review of test results via http://<hostname>/hwc/
>+
>+The
>+.I daemon 
>+option stops the hwc server daemon process, and restarts it in foreground.   The hwc daemon
>+process is used for tests such as the fencing test where server-side tests must be run.
>+
>+.SS submit
>+.P
>+.B hwc submit
>+.P
>+.I Submit
>+uploads the test results to the Hardware Catalog.  If
>+.I --mode 
>+is set to 
>+.I auto
>+hwc will package the test results into an RPM.
>+
>+.SS verify
>+.P
>+.B hwc verify
>+.P
>+The verify command checks configuration requirements for the tests without actually
>+running the tests.   Test verification is also run as part of the
>+.I certify
>+and
>+.I run
>+commands.
>+
>+.SS version
>+.P
>+.B hwc version
>+.P
>+Prints the version and release of hwc.
>+
>+.SH FILES
>+
>+.B /etc/hwcert.xml 
>+- configuration of directory locations
>+
>+.B /usr/share/hwcert 
>+- hwc harness and test source files
>+
>+.B /var/hwcert 
>+- hwc data files and test results for hwc-client on the SUT
>+
>+.B /var/www/hwcert
>+- The and web/NFS root for hwcert-server
>+
>+
>+
>+
>diff --git a/hwcert-client.spec.in b/hwcert-client.spec.in
>index 8b3702b..5bd0516 100644
>--- a/hwcert-client.spec.in
>+++ b/hwcert-client.spec.in
>@@ -64,10 +64,12 @@ DESTDIR=$RPM_BUILD_ROOT make HWCERT_RHEL_VERSION=%{rhel_version} install
> /usr/bin/hwcert-environment.sh
> /usr/bin/hwcert-run-simple-test
> /usr/bin/hwcert-report-result
>-/usr/bin/hwc
>+/usr/bin/hwcert
>+/usr/bin/hwcert-backend
> /usr/share/hwcert
>-/usr/share/man/man8/hwc.8.gz
>-/etc/init.d/hwc
>+/usr/share/man/man8/hwcert.8.gz
>+/usr/share/man/man8/hwcert-backend.8.gz
>+/etc/init.d/hwcert-backend
> 
> %files -n hwcert-server
> %defattr(-,root,root)
>diff --git a/hwcert/continuation.py b/hwcert/continuation.py
>index d1115e3..debd10e 100644
>--- a/hwcert/continuation.py
>+++ b/hwcert/continuation.py
>@@ -40,7 +40,7 @@ class Continuation(Controller):
>     def setInitConfig(self, marker, method=None):
>         if method:
>             self.method = method
>-        chkconfig = Command("chkconfig --add hwc")
>+        chkconfig = Command("chkconfig --add " + Constants.hwcert-backend)
>         chkconfig.echo()
>         # get a timestamo, save it
>         theTime = time.localtime(time.time())
>@@ -57,7 +57,7 @@ class Continuation(Controller):
>         syslog.syslog(self.getSystemLogMarker(markerName, "begin", pid=False))
>         
>     def removeInitConfig(self):
>-        chkconfig = Command("chkconfig --del hwc")
>+        chkconfig = Command("chkconfig --del " + Constants.hwcert-backend)
>         chkconfig.echo()
>         
>     def isInitialized(self):
>diff --git a/hwcert/daemon.py b/hwcert/daemon.py
>index 0f2200c..e2238ad 100644
>--- a/hwcert/daemon.py
>+++ b/hwcert/daemon.py
>@@ -159,7 +159,7 @@ class HwCertDaemon(Controller):
>     def do(self, subcommand):
>         try:
>             command = Command("ps ax")
>-            command.getString("hwc server daemon", singleLine=False)
>+            command.getString("%s server daemon" % Constants.hwcert_backend, singleLine=False)
>             running = True
>         except:
>             running = False
>@@ -170,7 +170,7 @@ class HwCertDaemon(Controller):
>                 return True
>             print "Starting hwcert daemon"
>             sys.stdout.flush()
>-            if os.system("hwc server daemon > /dev/null &"):
>+            if os.system("%s server daemon > /dev/null &" % Constants.hwcert_backend):
>                 print "Error: could not start hwcert server daemon"
>                 return False                    
>         elif subcommand == "stop":
>diff --git a/hwcert/fvtest.py b/hwcert/fvtest.py
>index efb5fdc..869f6d1 100644
>--- a/hwcert/fvtest.py
>+++ b/hwcert/fvtest.py
>@@ -44,15 +44,15 @@ class FvTest(Test):
>         Test.__init__(self, name)
>         self.deviceClass = DeviceClass.system
>         self.hardwarePlatform = Command("uname -i").getString()
>-        self.guestName = "hwcert%s" % self.hardwarePlatform
>-        self.guestImageFile = 'hwcert' + self.hardwarePlatform + '.img'
>+        self.guestName = "hwcert-%s" % self.hardwarePlatform
>+        self.guestImageFile = 'hwcert-' + self.hardwarePlatform + '.img'
>         self.loopBackDevice = None
>         self.dataImageFile = 'hwcertData.img'
>         if self.hardwarePlatform == "ia64":
>         	self.nvramFile = "nvram_hwcertia64"
>         	self.nvramUuidFile = "nvram_hwcertia64.uuid"
>         # defaults
>-        self.hwcertCommandInGuest = "hwc certify "
>+        self.hwcertCommandInGuest = "%s certify " % Constants.hwcert_backend
>         self.testToRun = ""
>         self.environment = Environment()
>         self.waitTime = self.environment.getFVGuestTimelimit()
>@@ -366,7 +366,7 @@ class FvTest(Test):
>             # try to install hwcert
>             guestScript.write("rpm -ivh /mnt/hwcert-client-*.noarch.rpm 2>&1 > /var/log/hwcertfv.log\n")
>             # run the tests 
>-            guestScript.write("hwc plan --mode auto\n")
>+            guestScript.write("%s plan --mode auto\n" % Constants.hwcert_backend)
>             commandToRun = self.hwcertCommandInGuest + "  --mode auto --test " + self.testToRun 
>             if self.getTestServer():
>                 commandToRun += ' --server ' + self.getTestServer()
>@@ -375,7 +375,7 @@ class FvTest(Test):
>             # copy the results to hwcertdata.imghp-dl580g5-01.rhts.bos.redhat.com
>             guestScript.write("mv /var/hwcert/results.xml /mnt/.\n")
>             # remove the tmp files
>-            guestScript.write("echo -e \'y\' | hwc clean\n")
>+            guestScript.write("echo -e \'y\' | %s clean\n" % Constants.hwcert_backend)
>             # remove hwcert rpm
>             guestScript.write("rpm -e hwcert-client\n")          
>             # poweroff
>diff --git a/hwcert/hardwarecertification.py b/hwcert/hardwarecertification.py
>new file mode 100644
>index 0000000..7f63a26
>--- /dev/null
>+++ b/hwcert/hardwarecertification.py
>@@ -0,0 +1,50 @@
>+# Copyright (c) 2013 Red Hat, Inc. All rights reserved. This copyrighted material 
>+# is made available to anyone wishing to use, modify, copy, or 
>+# redistribute it subject to the terms and conditions of the GNU General 
>+# Public License v.2.
>+# 
>+# This program is distributed in the hope that it will be useful, but WITHOUT ANY
>+# WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
>+# PARTICULAR PURPOSE. See the GNU General Public License for more details.
>+#
>+# You should have received a copy of the GNU General Public License
>+# along with this program; if not, write to the Free Software
>+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
>+#
>+# Author: Greg Nichols
>+#
>+
>+import os, sys
>+from optparse import OptionParser
>+
>+from hwcert.controller import Controller
>+from hwcert.hardwaretest import HardwareTestHarness
>+    
>+class HardwareCertification(HardwareTestHarness):
>+    
>+    def __init__(self ):
>+        # probably need to block old syntax here.
>+        HardwareTestHarness.__init__(self)
>+    
>+    def run(self):
>+        print "The Red Had Hardware Certification Test Suite"
>+        if not self.getLock():
>+            return False
>+        print "\nPreparing for certification"
>+        sys.stdout.flush()
>+        while True:
>+            self.load(silent=True)
>+            if self.certification:
>+                # cert results from a prior run, submit them.
>+                if self.doSubmit():
>+                    # if submitted, clean
>+                    self.doClean()
>+                    
>+                if not self.ui.promptConfirm("Would you like to continue certification testing?"):
>+                    break
>+        
>+            self.doCertify()
>+        
>+        self.releaseLock()
>+        
>+        return True
>diff --git a/hwcert/tags.py b/hwcert/tags.py
>index ce59efe..82bc3cf 100644
>--- a/hwcert/tags.py
>+++ b/hwcert/tags.py
>@@ -161,6 +161,7 @@ class Constants:
>     failed = "failed"
>     HwCert = "HwCert"
>     hwcert = "hwcert"
>+    hwcert_backend = "hwcert-backend"
>     off = "off"
>     low = "low"
>     medium = "medium"
>diff --git a/test-env/bin/Makefile b/test-env/bin/Makefile
>index 7460e53..53edc71 100644
>--- a/test-env/bin/Makefile
>+++ b/test-env/bin/Makefile
>@@ -19,7 +19,8 @@
> FILES := hwcert-environment.sh \
>          hwcert-run-simple-test \
>          hwcert-report-result \
>-         hwc 
>+         hwcert \
>+         hwcert-backend
> 
> all install:
> 	mkdir -p $(DESTDIR)/usr/bin
>diff --git a/test-env/bin/hwc b/test-env/bin/hwc
>deleted file mode 100644
>index 2f03ef1..0000000
>--- a/test-env/bin/hwc
>+++ /dev/null
>@@ -1,51 +0,0 @@
>-#!/usr/bin/python
>-# Copyright (c) 2006 Red Hat, Inc. All rights reserved. This copyrighted material 
>-# is made available to anyone wishing to use, modify, copy, or 
>-# redistribute it subject to the terms and conditions of the GNU General 
>-# Public License v.2.
>-# 
>-# This program is distributed in the hope that it will be useful, but WITHOUT ANY
>-# WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
>-# PARTICULAR PURPOSE. See the GNU General Public License for more details.
>-#
>-# You should have received a copy of the GNU General Public License
>-# along with this program; if not, write to the Free Software
>-# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
>-#
>-# Author: Greg Nichols
>-#
>-
>-import os,sys
>-hwcertClassLibraryPath = '/usr/share/hwcert/lib/'
>-sys.path.append(hwcertClassLibraryPath)
>-os.putenv("PYTHONPATH", hwcertClassLibraryPath)
>-
>-from hwcert.test import Test
>-from hwcert.hardwaretest import HardwareTestHarness
>-
>-# bail out if user is not root
>-if os.getuid() > 0:
>-    sys.stderr.write("You need to be root to run this program.\n")
>-    sys.exit(1)
>-
>-hwcert=HardwareTestHarness()
>-args = hwcert.getArgs()
>-
>-
>-command = None
>-if args:
>-    command=args[0]
>-
>-success = False
>-if command == "test":
>-    test = Test("generic")
>-    success = test.do(args[1:])
>-else:
>-    
>-    success = hwcert.do(args)
>-
>-if not success:
>-    sys.exit(1)
>-
>-
>-
>diff --git a/test-env/bin/hwcert b/test-env/bin/hwcert
>new file mode 100755
>index 0000000..7d2422e
>--- /dev/null
>+++ b/test-env/bin/hwcert
>@@ -0,0 +1,34 @@
>+#!/usr/bin/python
>+# Copyright (c) 2006 Red Hat, Inc. All rights reserved. This copyrighted material 
>+# is made available to anyone wishing to use, modify, copy, or 
>+# redistribute it subject to the terms and conditions of the GNU General 
>+# Public License v.2.
>+# 
>+# This program is distributed in the hope that it will be useful, but WITHOUT ANY
>+# WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
>+# PARTICULAR PURPOSE. See the GNU General Public License for more details.
>+#
>+# You should have received a copy of the GNU General Public License
>+# along with this program; if not, write to the Free Software
>+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
>+#
>+# Author: Greg Nichols
>+#
>+
>+import os,sys
>+hwCertClassLibraryPath = '/usr/share/hwcert/lib/'
>+sys.path.append(hwCertClassLibraryPath)
>+os.putenv("PYTHONPATH", hwCertClassLibraryPath)
>+
>+from hwcert.hardwaretest import HardwareTestHarness
>+from hwcert.hardwarecertification import HardwareCertification
>+
>+# bail out if user is not root
>+if os.getuid() > 0:
>+    sys.stderr.write("You need to be root to run this program.\n")
>+    sys.exit(1)
>+
>+hwcert = HardwareCertification()
>+if not hwcert.run():
>+    sys.exit(1)
>+
>diff --git a/test-env/bin/hwcert-backend b/test-env/bin/hwcert-backend
>new file mode 100644
>index 0000000..2f03ef1
>--- /dev/null
>+++ b/test-env/bin/hwcert-backend
>@@ -0,0 +1,51 @@
>+#!/usr/bin/python
>+# Copyright (c) 2006 Red Hat, Inc. All rights reserved. This copyrighted material 
>+# is made available to anyone wishing to use, modify, copy, or 
>+# redistribute it subject to the terms and conditions of the GNU General 
>+# Public License v.2.
>+# 
>+# This program is distributed in the hope that it will be useful, but WITHOUT ANY
>+# WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
>+# PARTICULAR PURPOSE. See the GNU General Public License for more details.
>+#
>+# You should have received a copy of the GNU General Public License
>+# along with this program; if not, write to the Free Software
>+# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
>+#
>+# Author: Greg Nichols
>+#
>+
>+import os,sys
>+hwcertClassLibraryPath = '/usr/share/hwcert/lib/'
>+sys.path.append(hwcertClassLibraryPath)
>+os.putenv("PYTHONPATH", hwcertClassLibraryPath)
>+
>+from hwcert.test import Test
>+from hwcert.hardwaretest import HardwareTestHarness
>+
>+# bail out if user is not root
>+if os.getuid() > 0:
>+    sys.stderr.write("You need to be root to run this program.\n")
>+    sys.exit(1)
>+
>+hwcert=HardwareTestHarness()
>+args = hwcert.getArgs()
>+
>+
>+command = None
>+if args:
>+    command=args[0]
>+
>+success = False
>+if command == "test":
>+    test = Test("generic")
>+    success = test.do(args[1:])
>+else:
>+    
>+    success = hwcert.do(args)
>+
>+if not success:
>+    sys.exit(1)
>+
>+
>+
>diff --git a/test-env/init/Makefile b/test-env/init/Makefile
>index 0eaea1e..5105594 100644
>--- a/test-env/init/Makefile
>+++ b/test-env/init/Makefile
>@@ -15,7 +15,7 @@
> .PHONY: clean
> 
> 
>-FILES := hwc 
>+FILES := hwcert-backend
> 
> all install:
> 	mkdir -p $(DESTDIR)/etc/init.d
>diff --git a/test-env/init/hwc b/test-env/init/hwc
>deleted file mode 100755
>index 92ddaa8..0000000
>--- a/test-env/init/hwc
>+++ /dev/null
>@@ -1,61 +0,0 @@
>-#!/bin/sh
>-#
>-# hwcert: Red Hat Hardware Test Suite
>-#
>-# chkconfig: 2345 35 98
>-# description: Red Hat Hardware Test Suite
>-
>-. /etc/rc.d/init.d/functions
>-RETVAL=0
>-HWCERT=/usr/bin
>-
>-start() {
>-    $HWCERT/hwc continue  --mode auto &
>-}
>-
>-stop() {
>-	killall hwc
>-}
>-
>-reload() {
>-	stop
>-	start
>-}
>-
>-hwcert_status() {
>-	if ps ax | fgrep hwc &>/dev/null; then 
>-		echo $"hwc is running"
>-		return 0
>-	else
>-		echo $"hwc is not running"
>-		return 3
>-	fi
>-}
>-
>-case "$1" in
>-	start)
>-		start
>-		;;
>-	stop)
>-		stop
>-		;;
>-	status)
>-		hwcert_status
>-		RETVAL=$?
>-		;;
>-	restart)
>-		stop
>-		start
>-		;;
>-	condrestart)
>-		if qemu_status &>/dev/null; then
>-			stop
>-			start
>-		fi
>-		;;
>-	*)
>-		echo $"Usage: $prog {start|stop|status|restart|condrestart}"
>-		exit 1
>-esac
>-exit $RETVAL
>-
>diff --git a/test-env/init/hwcert-backend b/test-env/init/hwcert-backend
>new file mode 100755
>index 0000000..d8710a4
>--- /dev/null
>+++ b/test-env/init/hwcert-backend
>@@ -0,0 +1,61 @@
>+#!/bin/sh
>+#
>+# hwcert: Red Hat Hardware Test Suite
>+#
>+# chkconfig: 2345 35 98
>+# description: Red Hat Hardware Test Suite
>+
>+. /etc/rc.d/init.d/functions
>+RETVAL=0
>+HWCERT=/usr/bin/hwcert-backend
>+
>+start() {
>+    $HWCERT continue  --mode auto &
>+}
>+
>+stop() {
>+	killall hwcert-backend
>+}
>+
>+reload() {
>+	stop
>+	start
>+}
>+
>+hwcert_status() {
>+	if ps ax | fgrep hwcert-backend &>/dev/null; then 
>+		echo $"hwcert-backend is running"
>+		return 0
>+	else
>+		echo $"hwcert-backend is not running"
>+		return 3
>+	fi
>+}
>+
>+case "$1" in
>+	start)
>+		start
>+		;;
>+	stop)
>+		stop
>+		;;
>+	status)
>+		hwcert_status
>+		RETVAL=$?
>+		;;
>+	restart)
>+		stop
>+		start
>+		;;
>+	condrestart)
>+		if qemu_status &>/dev/null; then
>+			stop
>+			start
>+		fi
>+		;;
>+	*)
>+		echo $"Usage: $prog {start|stop|status|restart|condrestart}"
>+		exit 1
>+esac
>+exit $RETVAL
>+
>diff --git a/tests/fv_core/fv_core.py b/tests/fv_core/fv_core.py
>index 387f852..37e3cff 100644
>--- a/tests/fv_core/fv_core.py
>+++ b/tests/fv_core/fv_core.py
>@@ -26,7 +26,7 @@ class FvCoreTest(FvTest):
>     
>     def __init__(self):
>         FvTest.__init__(self, name="fv_core")
>-        self.hwcertCommandInGuest = "hwc run "
>+        self.hwcertCommandInGuest = Constants.hwcert_backend + " run "
>         self.testToRun = 'core'
> 
> if __name__ == "__main__":
>diff --git a/tests/fv_memory/fv_memory.py b/tests/fv_memory/fv_memory.py
>index e6e1c70..58f4117 100644
>--- a/tests/fv_memory/fv_memory.py
>+++ b/tests/fv_memory/fv_memory.py
>@@ -26,7 +26,7 @@ class FvMemoryTest(FvTest):
>     
>     def __init__(self):
>         FvTest.__init__(self, name="fv_memory")
>-        self.hwcertCommandInGuest = "hwc run "
>+        self.hwcertCommandInGuest = Constants.hwcert_backend + " run "
>         self.testToRun = 'memory'
> 
> if __name__ == "__main__":
>diff --git a/tests/fv_network/fv_network.py b/tests/fv_network/fv_network.py
>index 68f21da..9436175 100644
>--- a/tests/fv_network/fv_network.py
>+++ b/tests/fv_network/fv_network.py
>@@ -26,7 +26,7 @@ class FvNetworkTest(FvTest):
>     
>     def __init__(self):
>         FvTest.__init__(self, name="fv_network")
>-        self.hwcertCommandInGuest = "hwc run "
>+        self.hwcertCommandInGuest = Constants.hwcert_backend + " run "
>         self.testToRun = 'network'
>         
>     def run(self):
>diff --git a/tests/fv_storage/fv_storage.py b/tests/fv_storage/fv_storage.py
>index fe62959..ce8e8bb 100644
>--- a/tests/fv_storage/fv_storage.py
>+++ b/tests/fv_storage/fv_storage.py
>@@ -26,7 +26,7 @@ class FvStorageTest(FvTest):
>     
>     def __init__(self):
>         FvTest.__init__(self, name="fv_storage")
>-        self.hwcertCommandInGuest = "hwc run "
>+        self.hwcertCommandInGuest = Constants.hwcert_backend + " run "
>         self.testToRun = 'storage'
> 
> if __name__ == "__main__":

Actions: View | Diff

Attachments on bug 921238: 710696