Bug 758467

Summary: Chapter 13 - Fixes for Red Hat HA management of the job queue
Product: Red Hat Enterprise MRG Reporter: Robert Rati <rrati>
Component: Grid_User_GuideAssignee: Alison Young <alyoung>
Status: CLOSED CURRENTRELEASE QA Contact: Jeff Needle <jneedle>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: DevelopmentCC: jneedle, lbrindle, matt
Target Milestone: 2.1   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-26 19:24:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Robert Rati 2011-11-29 21:22:18 UTC 
Description of problem:
There are a few errors we need to fix in "13.1.2 Using Red Hat High Availability to Manage the Job Queue":
1) Add an important note: "All nodes configured to use Red Hat High Availability to manage the job queue must have supported integrated baseboard management controllers to fence nodes."

13.1.2.2 
  step 3 - "ask for values for SPOOL" -> "ask for values SCHEDD.SPOOL"
  step 3 - "configuration for SPOOL" -> "configuration for SCHEDD.SPOOL"
  step 3 - Add important note: "The SCHEDD.SPOOL should be different than SPOOL.  The SCHEDD.SPOOL is used by the condor_schedd for job queue data, and it is only mounted on the system running the condor_schedd process.  SPOOL and SCHEDD.SPOOL can be accessing the same shared resource, but must be mounted at separate mount points."

13.1.2.1 "For further information" - Any way we can make the references stand out more?  We have 3 references in that sentence and all the italics run together for me.  Maybe a list of references?

13.1.2.3 Insert step before step 3 - "Configure fencing devices.  Each node must have a fence device defined for service failover to succeed.  See "5.5. Configuring Fence Devices" and "5.7. Configuring Fencing for Cluster Members" in "Red Hat Enterprise Linux 6 Cluster Administration" guide.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Alison Young 2011-11-30 23:43:14 UTC 
(In reply to comment #0)
> 13.1.2.1 "For further information" - Any way we can make the references stand
> out more?  We have 3 references in that sentence and all the italics run
> together for me.  Maybe a list of references?

I'll reorder the sentence and add a list of the relevant chapters to try and clarify. The style of reference used is correct.
Comment 2 Robert Rati 2011-12-01 16:38:41 UTC 
(In reply to comment #1)
> (In reply to comment #0)
> > 13.1.2.1 "For further information" - Any way we can make the references stand
> > out more?  We have 3 references in that sentence and all the italics run
> > together for me.  Maybe a list of references?
> 
> I'll reorder the sentence and add a list of the relevant chapters to try and
> clarify. The style of reference used is correct.


I wasn't saying the style was incorrect, only that I was having issues separating out the 3 references in the sentence.

Also, please add a note at the top of 13.1.2 somewhere stating something to the effect of: "The minimum number of nodes supported for a Red Hat High Availability cluster is 3" (Minimum 3 nodes needed for a cluster)

Remove the note about a cluster containing only two nodes "If the cluster will only contain two nodes ..."
Comment 4 Lana Brindley 2012-01-26 19:24:55 UTC 
This book is now available on redhat.com/docs. Please raise a new bug if you spot any issues.

Thanks,
LKB