Opened 13 years ago

Closed 8 years ago

#46 closed task (fixed)

prepare for Ganglia 3.1.0

Reported by: bastiaans Owned by: ramonb
Priority: major Milestone: 1.0
Component: general Version: 1.0
Keywords: Cc:
Estimated Number of Hours:

Description

Need to test Job Monarch with the upcoming Ganglia 3.1.0 release.

In 3.1.0 many features are changed, including a major redesign of gmond.

Gmond 3.1.0 supports python modules, although it doesn't support dynamic metric names.

A possibility is to enable jobmond with a 'gmond module'-mode, which in turn still submits it's own dynamic metrics but is called by gmond. That would no longer require a daemon mode.

Change History (6)

comment:1 Changed 13 years ago by bastiaans

  • Owner changed from somebody to bastiaans
  • Status changed from new to assigned

comment:2 Changed 13 years ago by bastiaans

  • Type changed from defect to task

comment:3 Changed 13 years ago by ramonb

  • Owner changed from bastiaans to ramonb
  • Status changed from assigned to new

my username changed

comment:4 Changed 13 years ago by felix@…

anybody working on this? I'd be interested to run jobmonarch with ganglia 3.1.1 and lava 1.0 (a free version of LSF)

comment:5 Changed 13 years ago by ramonb

  • Priority changed from normal to major

Not yet, I have not been able to try out Ganglia 3.1 myself. Hopefully I can start on this month...

The following tasks are defined for this:

  • Test 3.1 gmetad XML parsing done by Job Monarch's PHP, does it still work
  • update the embedded Gmetric code in gmond to be compatible with 3.1
  • make sure that embedded and external Gmetric injection still works for jobmond

Pretty much to make sure it still works with 3.1. These are probably the biggest show stoppers for a new release.

Later on, further enhancements with lower priority:

  • implement jobmond as a 3.1 gmond module
  • implement jobarchived as a 3.1 gmetad module

Module support should be optional while retaining backwards compatibility mode for standalone/daemonized operation. I'm not sure however how this would work out for jobarchived.

comment:6 Changed 8 years ago by ramonb

  • Milestone set to 1.0
  • Resolution set to fixed
  • Status changed from new to closed
  • Version changed from trunk to 1.0

fixed in 1.0

Note: See TracTickets for help on using tickets.