Perry:

I'll add something along these lines for 6.1, since that's pretty straightforward, but I don't know what to do about Paul's suggestion that something along these lines be incorporated into the GUI itself -- it certainly would be more effective there (in general people only look at GUI documentation if they have problems I suspect), but I don't know where or when such a statement might appear. That seems a GUI design/interface question rather than a documentation question.

It does seem a given to me, but how about this as the note in the Conga doc:

"Conga is a graphical user interface that you can use to administer the Red Hat High Availability Add-On. Note, however, that in order to use this interface effectively you need to have a good and clear understanding of the underlying concepts. Learning about cluster configuration by exploring the available features in the user interface is not recommended, as it may result in a system that is not robust enough to keep all services running when components fail."

(In reply to comment #4)
> Perry:
> 
> I'll add something along these lines for 6.1, since that's pretty
> straightforward, but I don't know what to do about Paul's suggestion that
> something along these lines be incorporated into the GUI itself -- it certainly
> would be more effective there (in general people only look at GUI documentation
> if they have problems I suspect), but I don't know where or when such a
> statement might appear. That seems a GUI design/interface question rather than
> a documentation question.

ack, I'll clone this for Luci component as that is a good idea.
 
> It does seem a given to me, but how about this as the note in the Conga doc:
> 
> "Conga is a graphical user interface that you can use to administer the Red Hat
> High Availability Add-On. Note, however, that in order to use this interface
> effectively you need to have a good and clear understanding of the underlying
> concepts. Learning about cluster configuration by exploring the available
> features in the user interface is not recommended, as it may result in a system
> that is not robust enough to keep all services running when components fail."

I'd say Luci instead of Conga perhaps?  Otherwise that warning looks fine to me.

Perry: 

Thanks for the quick turnaround. This note would go right at the beginning of an existing chapter in the Cluster Admin Guide which is titled "Configuring Red Hat High Availability Add-On With Conga" (and then uses Conga to refer to the whole system). That title (and specific usage) predates my involvement in the chapter, so I'm only thinking about that now that you've brought it up -- but I think that using "Conga" in this case refers to the whole package, both the luci and ricci components -- even though I get your point that the graphical configuration interface itself is the luci component. But in general it seems consistent to me to leave that as Conga here.

I think the luci distinction is important for things like developement and installation, but in talking about using the interface in a general way, from the admin's perspective, using Conga here makes sense to me.

-Steven

(In reply to comment #6)
Sounds resonable, ack

I have added this note to the 6.1 working draft of the Cluster Administration Guide and I have checked the updated files into the svn repository so I am moving this bug to MODIFIED.

Red_Hat_Enterprise_Linux-Cluster_Administration-6-web-en-US-0-75.el5

Verified the note is added as per comment#4. 

One minor point, the last sentence is missing a full stop:

"Learning about cluster configuration by exploring the available features in the user interface is not recommended, as it may result in a system that is not robust enough to keep all services running when components fail "

I have added the full stop to the sentence in my working copy. I will move this to ON_QA when I rebuild the document.

Verified: Red_Hat_Enterprise_Linux-Cluster_Administration-6-web-en-US-0-76.el5

With the release of RHEL 6.1, I'm closing this bug.