- From: Bryan McLellan <
>
- To:
- Subject: [chef] Re: Re: Re: why does mysql on ec2 bind to priviate i.p?
- Date: Wed, 14 Nov 2012 14:26:15 -0500
On Wed, Nov 14, 2012 at 11:33 AM, S Ahmed
<
>
wrote:
>
The problem is during deployment, I don't know the private i.p in advance
>
and during deployment all my database configuration information has
>
'localhost' in it. I understand what you guys are saying and it does make
>
sense, I just have to modify my deployment process to first pull in the
>
private ip's for each service (I should be doing this anyhow as eventually
>
not everything is going to fit on a single instance!)
You should know what interface you want to bind to at least, e.g. eth0
or eth1. There's bits of ruby for getting the IP of a specific
interface here:
http://tickets.opscode.com/browse/OHAI-88
Bryan
- [chef] RE: why does mysql on ec2 bind to priviate i.p?, (continued)
Archive powered by MHonArc 2.6.16.