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

Re: PUBLIC_IP in node.conf



+1 - lookup makes more sense than hardcode, but we could hit private/public ip problems there as well.    I'm assuming that the node is ultimately the one that has to report this.

On Jul 1, 2013, at 10:14 AM, Michael McGrath <mmcgrath redhat com> wrote:

> ----- Original Message -----
>> From: "Krishna Raman" <kraman gmail com>
>> To: "Michael McGrath" <mmcgrath redhat com>
>> Cc: lmeyer redhat com, dev lists openshift redhat com
>> Sent: Monday, July 1, 2013 9:09:02 AM
>> Subject: Re: PUBLIC_IP in node.conf
>> 
>> Hi Mike,
>> 
>> If I remember right, the Public IP in that case was uses as a stop gap till
>> dns propagation completed.
>> In those cases, we might be able to lookup the public IP rather than having
>> it hardcoded into the conf file as well.
> 
> That's true, and I am all for smaller/simpler config files.
> 
>   -Mike
> 
>> --kr
>> 
>> On Jul 1, 2013, at 7:01 AM, Michael McGrath <mmcgrath redhat com> wrote:
>> 
>>> Public IP was requested for a few very specific use cases where waiting for
>>> DNS was undesirable.  It was to be sent back to the client via the REST
>>> api so users could consume the gears immediately.
>>> 
>>> Sent from my Android phone
>>> 
>>> 
>>> -----Original Message-----
>>> From: Krishna Raman [kraman gmail com]
>>> Received: Monday, 01 Jul 2013, 8:58AM
>>> To: Luke Meyer [lmeyer redhat com]
>>> CC: dev lists openshift redhat com
>>> Subject: Re: PUBLIC_IP in node.conf
>>> 
>>> 
>>> Hi Shoumeng,
>>> 
>>> I looked through code as well and came to the same conclusion as Luke. For
>>> an all-in-one install this will not break anything.
>>> 
>>> If you create a multi node OpenShift installation, then the DNS server IP
>>> will need to be static otherwise DNS lookups will fail.
>>> But other than that we should be able to use DNS lookups for everything
>>> else.
>>> 
>>> In the libvirt container code I am working on, I will be adding IP tables
>>> rules which may use this variable, but even there I am
>>> trying to reply on the name of the external interface rather than the IP so
>>> you should be safe in the future as well.
>>> 
>>> --kr
>>> 
>>> On Jul 1, 2013, at 6:26 AM, Luke Meyer <lmeyer redhat com> wrote:
>>> 
>>>> When I looked through the code some time ago (and just now), I could not
>>>> find an important use of PUBLIC_IP (there was one point where it's
>>>> logged; that's it). OpenShift Online may have some uses for this but in
>>>> Origin at this point I think it may be vestigial. Routing appears to be
>>>> name-based (even in scaled apps which route to secondary gears by IP, I
>>>> think it is simply resolved from DNS). We don't have IP-specific iptables
>>>> rules (yet?).
>>>> 
>>>> So the summary is, if this is wrong, you likely won't see any problems,
>>>> aside from complaints via oo-accept-node / oo-accept-systems.
>>>> 
>>>> It's still a good idea to keep PUBLIC_IP updated, though, as it seems
>>>> inevitable to me that something important *will* depend on this at some
>>>> point. Look into dhclient config for ways to have a dhcp lease event
>>>> trigger changes, but be aware that SElinux policy often needs to be
>>>> created to enable dhclient to make necessary modifications (it might be
>>>> better to create a service to do this at boot, assuming that's the only
>>>> time you have IP changes). Also be aware that changing IPs on an existing
>>>> node will leave secondary gears in scaled apps unroutable (hopefully this
>>>> will be fixed as part of the upcoming HA work).
>>>> 
>>>> ----- Original Message -----
>>>> From: "Shoumeng Yan" <shoumeng yan intel com>
>>>> To: dev lists openshift redhat com
>>>> Sent: Tuesday, June 25, 2013 8:37:08 AM
>>>> Subject: PUBLIC_IP in node.conf
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 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
>>>> 
>>>> _______________________________________________
>>>> dev mailing list
>>>> dev lists openshift redhat com
>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>> 
>>> 
>>> _______________________________________________
>>> dev mailing list
>>> dev lists openshift redhat com
>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
> 
> _______________________________________________
> 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]