| Summary: | Clarify why there are redundant alert notifications for PCS | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Steven J. Levine <slevine> |
| Component: | doc-High_Availability_Add-On_Reference | Assignee: | Steven J. Levine <slevine> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ecs-bugs |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.3 | CC: | jkortus, kgaillot, kwenning, rhel-docs |
| Target Milestone: | rc | Keywords: | Documentation |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-07 21:36:02 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Steven J. Levine
2016-08-22 19:41:56 UTC
Just to clarify on the subject line, there are no redundant notifications, just redundant entries (duplicates if you wish) with different names in one notification. For documentation I consider the way "Pacemaker Explained" is handling the issue appealing: Document just the new interface in detail and have a note about compatibility: "The alerts interface is designed to be backward compatible with the external scripts interface used by the ocf:pacemaker:ClusterMon resource, which is now deprecated. To preserve this compatibility, the environment variables passed to alert agents are available prepended with CRM_notify_ as well as CRM_alert_. One break in compatibility is that ClusterMon ran external scripts as the root user, while alert agents are run as the hacluster user." That should naturally make people use the new interface ... The pacemaker implementation is done so that it is just about modifying a table to have either or the other interface - or both at the same time. That would even work on a per entry basis. At the moment I added the CRM_notify_* versions even for variables that are new with the alerts feature. If preferred for kind of "educative reasons" we could drop those though easily. one more thing to note: if cluster contains resources which cannot fail (onfail=fence), there will be multiple fence notifications (one for each of these resources perhaps, plus one). Stonith decides to fence the node (is lost), crmd also decides to fence it (resource failed), each of them sends the notificaiton. Pacemaker joins these request to one actual fence operation, so there will be finally only one, no matter how many notifications were sent. I filed this BZ in sort of a hurry just before getting on an airplane, so I didn't really check things out: The 7.3 version of the PCS Reference manual does include the note that Klaus noted in Comment 2, at the end of section 13.1.7 http://jenkinscat.gsslab.pnq.redhat.com:8080/job/doc-Red_Hat_Enterprise_Linux-7-High_Availability_Add-On_Reference%20%28html-single%29/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#s2-alertagentwrite-HAAR So it seems that all I need to do here is note what Jaroslav reports in Comment 3. Jaroslav: Section 13.1.7 -- link in comment 4 -- already contains a note about the different alert notifications, and it now contains a last bullet point of considerations that summarizes comment 3. Does this address your concenrs? Steven all looks good, thank you for taking care of it :) |