Status

RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: arich, Assigned: dividehex)

Tracking

Details

Attachments

(2 attachments)

(Reporter)

Description

4 years ago
We're running diamond on the AWS linux nodes and reporting to hostedgraphite, but we're not actually looking at that data. We need to uninstall diamond and remove its config files.

Since we're not looking at the data, this does not need to block on fixing up collectd.
(Reporter)

Comment 1

4 years ago
This will be reversing the steps taken in bug 968381
Created attachment 8611482 [details] [diff] [review]
bug1164220-1.patch

Removes diamond from the aws node defs.  Next golden image builds will therefore *NOT* include diamond.
Attachment #8611482 - Flags: review?(dustin)
Attachment #8611482 - Flags: review?(dustin) → review+
Once diamond has made itself scarce I'll remove the packages, modules and any other unused bits from puppet.
Created attachment 8613812 [details] [diff] [review]
bug1164220-2.patch

This just clean up work.  It removes diamond from puppet and the diamond instance_metadata bits.

I still don't have access to hostedgraphite so this won't land until I can confirm the golden images are no longer built with diamond.  I could also spot check a few instances if I can't get access.
Attachment #8613812 - Flags: review?(dustin)
Attachment #8613812 - Flags: review?(dustin) → review+
In an effort to move this forward, I spot checked a handful of instances.  Diamond is no longer being baked into the golden images.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.