1036610 - Switch to upstream graphite multi-instance configs and init scripts

Status: RESOLVED WONTFIX

(Infrastructure & Operations :: Tools, task)

Description

[Eric Ziegenhorn :ericz]

Graphite used to not have built-in support for more than one instance but it appears to be much more capable now.  See if we can revert to a single config file and use the built-in init scripts and get rid of our customizations.

Comment 1

[Eric Ziegenhorn :ericz]

Attachment: Combined carbon.conf

Attached a combined carbon.conf.

Comment 2

[Eric Ziegenhorn :ericz]

Although for Ubuntu, these init scripts might be useful.  I like the number vs letter approach to naming cache and relay instances.  https://github.com/obfuscurity/graphite-scripts/tree/master/init.d

Comment 3

[david garvey:dgarvey]

Eric,

I took a look at the existing init script and it seemed ok. Isn't obfuscurity script a customization? I don't understand..

Comment 4

[Eric Ziegenhorn :ericz]

Yeah I think we can ignore obfuscurity's stuff but I do prefer his numeric instance naming to our current alphabetical naming.  The built-in carbon init script: https://github.com/graphite-project/carbon/blob/master/distro/redhat/init.d/carbon-cache should work fine with a single carbon.conf file.  It starts/stops all instances at once and doesn't allow for manipulating a single instance, but that's usually what we want to do so that's fine.

Comment 5

[Eric Ziegenhorn :ericz]

This will be obsolete when SCL3 dies, graphite in MDC1 is much smaller and uses the default init scripts.