Closed sax closed 10 years ago
@sax This is great! Just two remarks:
ohai-private-ipaddress
? Can that include only be used if they are using the code-paths that require it? Seems like that might create an unneeded dependency for a lot of users.graphite[bind]
setting for?Hmmm you're right. In the long run I think the private-ipaddress stuff should be in ohai, but I'm just getting familiar with that codebase. It was my attempt to centralize the code for finding RFC1918 addresses, which we use to keep our private services off the public internet.
In the meantime, I'll refactor it so it only gets loaded when necessary. I'll also add to the readme, so the bind stuff makes more sense. Basically, if your graphite server is multi-homed, it lets you choose whether to bind the public or private ip.
My apologies for not staying on top of this. It looks like many of these changes have been incorporated since through various PRs. Can you resubmit any remaining deltas?
It's fine closing this. Since then, we've completely changed how we manage public/private IP addresses and don't use ohai-private-ipaddress any more.
On Tue, Jul 29, 2014 at 1:19 PM, Mike Heffner notifications@github.com wrote:
My apologies for not staying on top of this. It looks like many of these changes have been incorporated since through various PRs. Can you resubmit any remaining deltas?
— Reply to this email directly or view it on GitHub https://github.com/librato/statsd-cookbook/pull/6#issuecomment-50532414.
e s
This is a lot of changes, so I would understand if you do not want to pull this upstream. I figured I'd start a pull request, though, to see if you want any of these changes.
If you see any problems or prefer anything done differently, let me know!