Re: [Pacemaker] System Health backend patch part 1 (Andrew Beekhof)

2009-07-02 Thread Mark Hamzy
and...@beekhof.net wrote on 06/30/2009 14:14:12 PM: > I'd prefer sbin_PROGRAMS instead of halib_PROGRAMS for > notifyServicelogEvent (the others are only installed there for legacy > reasons). > Also, since you're linking against crmcommon (which should be > $(top_builddir)/lib/common/libcrmcommon

Re: [Pacemaker] Pacemaker Digest, Vol 19, Issue 44

2009-06-30 Thread Mark Hamzy
and...@beekhof.net wrote on 06/30/2009 14:14:12 PM: > I'd prefer sbin_PROGRAMS instead of halib_PROGRAMS for > notifyServicelogEvent (the others are only installed there for legacy > reasons). > Also, since you're linking against crmcommon (which should be > $(top_builddir)/lib/common/libcrmcommon

Re: [Pacemaker] System Health backend patch part 1

2009-06-09 Thread Mark Hamzy
and...@beekhof.net wrote on 06/09/2009 00:00:20 AM: > You might find: > > + syslog (LOG_INFO, "Event id:"U64T"\n", event_id); > + syslog (LOG_INFO, "Log timestamp: %s\n", ctime (&(event-> time_logged))); > + syslog (LOG_INFO, "Event timestamp: %s\n", ctime (&(event-> time_event)));

[Pacemaker] System Health backend patch part 1

2009-06-08 Thread Mark Hamzy
Okay, here is my first pass at the backend part needed for system health. Comments/suggestions? (See attached file: pacemaker.mark.patch) Mark Common Information Model/Web-Based Enterprise Management at http://www.openpegasus.org/ Take a look at the Linux Omni Printer Driver Framework at http:/

Re: [Pacemaker] System Health backend part

2009-06-02 Thread Mark Hamzy
and...@beekhof.net wrote on 06/02/2009 16:46:55 PM: > Do you think this should live in pacemaker or with the RAs? > I'm inclined to think the latter but am open to persuasion. Well, I think that these files do not fit within the Resource Agent model. While you could theoretically start and stop

[Pacemaker] System Health backend part

2009-05-29 Thread Mark Hamzy
I would like to see a complete solution for system health shipped with pacemaker. Would you be opposed to including the backend parts that monitor system health into pacemaker such as daemons or command line programs? One of the ways to determine the health of a system is to listen to IPMI even

Re: [Pacemaker] Pacemaker Digest, Vol 18, Issue 27

2009-05-18 Thread Mark Hamzy
l...@suse.de wrote on 05/18/2009 15:28:34 AM: > Can you provide a description and example of how this final version > would be used? Maybe a wiki page or something? Sure thing. On http://clusterlabs.org/wiki/ somewhere? What parent page? HowTos? How do you create an account on that wiki? Mark

[Pacemaker] New patch for System Health feature

2009-05-15 Thread Mark Hamzy
Here is attempt #3: (See attached file: pacemaker.mark.patch) I chose not to use pe_working_set_t* in char2score and instead used a small structure. I noticed a couple of things about crm_int_helper(). 1) It doesn't have a way to indicate an error. It returns -1, but aren't signed integers val

Re: [Pacemaker] New patch for System Health feature

2009-05-14 Thread Mark Hamzy
and...@beekhof.net wrote on 05/13/2009 21:08:36 PM: > This is missing the modification to char2score that i mentioned (which > would also simplify calculate_system_health()). > ... > Oh, and initialize_health_value() should probably just set a something > in data_set (which would be passed to cha

[Pacemaker] New patch for System Health feature

2009-05-13 Thread Mark Hamzy
Okay, here is attempt #2: (See attached file: pacemaker.mark.patch) Questions/comments? -- Mark pacemaker.mark.patch Description: Binary data ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacema

Re: [Pacemaker] System Health

2009-05-08 Thread Mark Hamzy
and...@beekhof.net wrote on 05/08/2009 13:26:16 PM: > On Thu, May 7, 2009 at 10:24 PM, Mark Hamzy wrote: > > So what I think we need is the scores: > - node-health-score-red (defaults to -INFINITY), > - node-health-score-yellow (defaults to 0), > - node-health-score-gr

Re: [Pacemaker] System Health

2009-05-07 Thread Mark Hamzy
and...@beekhof.net wrote on 05/07/2009 17:06:23 PM: > On Wed, May 6, 2009 at 11:32 PM, Mark Hamzy wrote: > > > This is where the disconnect is. > You seem convinced that everyone will want to sum them up the same way > you do, for every resource in the cluster. > I'm no

Re: [Pacemaker] New System Health feature

2009-05-06 Thread Mark Hamzy
beek...@gmail.com wrote on 04/28/2009 10:31:43 AM: > > On Mon, Apr 27, 2009 at 22:25, Mark Hamzy wrote: > > beek...@gmail.com wrote on 04/24/2009 11:00:01 AM: > >> > >> On Thu, Apr 23, 2009 at 17:49, Mark Hamzy wrote: > >> > > > Not only does t

Re: [Pacemaker] New System Health feature

2009-04-27 Thread Mark Hamzy
beek...@gmail.com wrote on 04/24/2009 11:00:01 AM: > > On Thu, Apr 23, 2009 at 17:49, Mark Hamzy wrote: > > > > Health Attribute-value Meaning > > green 1000 server is happy, capable of running any resource > > yellow 0 server is marginal - it is desirable to sc

Re: [Pacemaker] New System Health feature

2009-04-23 Thread Mark Hamzy
Here is the start of a patch. Right now I am using hardcoded values for green/yellow/red. I am posting this to see if I am modifying the correct part of pacemaker. Also, where and how should the system defined values for g/y/r be stored? (See attached file: pacemaker.mark.patch) Mark pacemak

[Pacemaker] New System Health feature

2009-04-23 Thread Mark Hamzy
Hello, I am working on a feature to add system health metrics to HA. With this information, HA could failover nodes away from hardware that might have problems. The initial proposal briefly started on the linux-HA mailing list, but it has been moved to the pacemaker mailing list. The followin