Bug 702695

Summary: v7 server should have it's own package
Product: [Retired] Red Hat Hardware Certification Program Reporter: Rob Landry <rlandry>
Component: Test Suite (harness)Assignee: Greg Nichols <gnichols>
Status: CLOSED ERRATA QA Contact: Petr Beňas <pbenas>
Severity: medium Docs Contact:
Priority: high    
Version: 1.3CC: czhang, gbai, pbenas, pstehlik, rlandry
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
in v7 1.4, there are two separate packages: v7 and v7-server. v7-server is only required in v7 test server side.
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-08 15:43:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
hardware test patch to add a check for v7-server when "v7 server" command is used none

Description Rob Landry 2011-05-06 15:50:13 UTC
Description of problem:

python-lxml is reported as required by 'v7 server start'; this package is only needed when using the v7 server webUI and may not be installed on RHEL5.

Version-Release number of selected component (if applicable):

v7-1.3-35


Additional info:

This issue is similar to the fence-agent rpm bug 702168. There may have been a configuration issue on the RHEL5 repo's and this package is normally available; perhaps it is only part of RHEL6?  Eitherway, the webUI is not currently a requirement for a v7 test server for the purposes of certifying so we should investigate options to have a cleaner user experience.

Comment 1 Greg Nichols 2011-06-15 16:54:58 UTC
I'd propose we split v7 into two packages.  The "v7" package would be for the SUT, and required for certification.   The web-serving parts would be moved to a "v7-server" rpm  to be installed on the v7 Test Server, and optionally on the SUT if the user would like to use the web/XSLT reporting interface to monitor testing.

The v7-server package would require v7 and python-lxml.  It might also require fence-agents, though that still might be better-handled in another way.

The following tables summarize the layout of v7's sources, and where they're installed, and shows how the sources split into the new rpm for the server:

v7
-------------------------------------------------------------------------
docs/man		-> 	/usr/share/man/man8
test-env/bin		->	/usr/bin
test-env/init		-> 	/etc/init.d (init script for SUT on reboot/fencing)
test-env/kickstart	->	/usr/share/v7/kickstart
test-env/lib		->	/usr/share/v7/lib
v7			->	/usr/share/v7/lib/v7
tests  			->	/user/share/v7/tests
tools/bin		-> 	/usr/bin


v7-server
--------------------------------------------------------------------------

docs/man		-> /var/v7/docs		(html version of man page)
test-env/www/index.html	-> /var/v7/index.html
test-env/www/cgi	-> /var/v7/cgi
			-> /etc/httpd/conf.d (v7 web configuration)
test-env/www/css	-> /var/v7/css
test-env/www/images	-> /var/v7/images

In addtion to splitting these sources to a new package, I propose we reorganize the source and destinations as well.   The test-env/www directory should move to a new "server" directory for the web sources.    The web directory these install to should be changed to /var/www/v7, which will be clearer, and may resolve some selinux issues.

Comment 4 Greg Nichols 2011-10-06 15:51:28 UTC
Created attachment 526742 [details]
hardware test patch to add a check for v7-server when "v7 server" command is used

Comment 9 Caspar Zhang 2011-10-21 15:45:42 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
in v7 1.4, there are two separate packages: v7 and v7-server. v7-server is only required in v7 test server side.

Comment 10 errata-xmlrpc 2011-11-08 15:43:45 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1436.html

Comment 11 errata-xmlrpc 2011-11-08 18:30:45 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1436.html