Closed Bug 773169 Opened 13 years ago Closed 13 years ago

Manage Ganglia with PuppetAgain

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

x86_64
Windows 7
task
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 773931

People

(Reporter: Callek, Assigned: Callek)

Details

We should manage/install ganglia on puppetAgain, in everything derived from toplevel::server. My largest concern so far is how to balance the current needs of "Releng/MoCo" against the desire for puppetAgain to be independant config-wise from MoCo. http://mxr.mozilla.org/build/source/puppet-manifests/modules/ganglia/manifests/client.pp#4 dustin/arr any suggestions there? Relatedly, our current yum repos also do not have |ganglia-gmond-modules-python| where did we get that from, and do we need to mix-and-match with our mozilla::python install (as in, do we need to create a custom spec for this)? http://mxr.mozilla.org/build/source/puppet-manifests/modules/ganglia/manifests/client.pp#36
O... and lastly, because I am nieve about ganglia setup -- does Ganglia depend on nagios to work? and do we *need* something like http://mxr.mozilla.org/build/source/puppet-manifests/modules/nagios/manifests/install.pp#90 for the basic ganglia work ?
ganglia-gmond-modules-python came from the IT yum repo, I believe. And ganglia and nagios are completely separate products that don't have anything to do with each other. We have a nagios check that contacts a ganglia server, but that's it. IT is also setting up nagios to reference ganglia URLs from the nagios GUI (at a past job, we had used these references to point to documentation)
Apparantly I refiled and attached a patch for this, duping forward
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.