[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: PUBLIC_IP in node.conf



My test seems to say the PUBLIC_IP config option is not used, at least in my test case. That is to say, I can still “rhc app ssh” into my apps after node reboots and IP changes, although node.conf still specifies a stale PUBLIC_IP value.

 

I am a bit confused… Thoughts?

 

p.s. I am using the release 1.

 

Thanks,

Shoumeng

 

From: Yan, Shoumeng
Sent: Wednesday, June 26, 2013 12:13 PM
To: 'Krishna Raman'
Cc: dev lists openshift redhat com; Yan, Shoumeng
Subject: RE: PUBLIC_IP in node.conf

 

Is there a way to automatically update the PUBLIC_IP every time the nodes are restarted?

 

Thanks,

Shoumeng

 

From: Krishna Raman [mailto:kraman gmail com]
Sent: Wednesday, June 26, 2013 2:04 AM
To: Yan, Shoumeng
Cc: dev lists openshift redhat com
Subject: Re: PUBLIC_IP in node.conf

 

Hi Shoumeng,

 

We use the public Ip of the node to add iptables and other routing rules within the node. We also use the public IP and hostname

to associate a DNS address with the applications hosted on the node. 

 

I would recommend setting up a static IP or re-applying the puppet script when the ipaddress changes.

 

HTH

--Krishna

 

On Jun 25, 2013, at 5:37 AM, "Yan, Shoumeng" <shoumeng yan intel com> wrote:

 

There is a PUBLIC_IP config option in node.conf. Is it necessary? I don’t have static IPs for my nodes, so it might be an issue if IP needs to be specified statically.  

 

Thanks,

Shoumeng

_______________________________________________
dev mailing list
dev lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev

 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]