Re: What actually is required for DNS and Origin?

2016-07-21 Thread Scott Dodson
If you're running the installer we deploy dnsmasq to all nodes and you can supply an additional config file to add wildcard support. The only thing preventing dnsmasq from being accessible outside of a node is the need to manually open up port 53. https://github.com/openshift/openshift-ansible/blo

Re: What actually is required for DNS and Origin?

2016-07-21 Thread Aleksandar Kostadinov
Josh Berkus wrote on 07/22/16 00:21: On 07/21/2016 02:07 PM, Aleksandar Kostadinov wrote: Then use plain IPs for nodes and masters. Then use xip.io for automatic generated DNS names pointing at your NAT router. Make sure NAT router forwards 80 and 443 to OpenShift cluster 80 and 443 ports respe

Re: What actually is required for DNS and Origin?

2016-07-21 Thread Jonathan Yu
This might help: https://github.com/peterhellberg/xip.name I can't vouch for its quality as I haven't tried it yet, though. On Thu, Jul 21, 2016 at 2:21 PM, Josh Berkus wrote: > On 07/21/2016 02:07 PM, Aleksandar Kostadinov wrote: > > > Then use plain IPs for nodes and masters. Then use xip.io

Re: What actually is required for DNS and Origin?

2016-07-21 Thread Aleksandar Kostadinov
Josh Berkus wrote on 07/21/16 23:54: On 07/21/2016 01:40 PM, Alex Wauck wrote: On Thu, Jul 21, 2016 at 3:29 PM, Josh Berkus mailto:jber...@redhat.com>> wrote: There is no external DNS server, here. I'm talking about a portable microcluster, a stack of microboard computers, self-conta

Re: What actually is required for DNS and Origin?

2016-07-21 Thread Josh Berkus
On 07/21/2016 01:40 PM, Alex Wauck wrote: > > > On Thu, Jul 21, 2016 at 3:29 PM, Josh Berkus > wrote: > > There is no external DNS server, here. I'm talking about a portable > microcluster, a stack of microboard computers, self-contained. The idea > woul

Re: What actually is required for DNS and Origin?

2016-07-21 Thread Alex Wauck
On Thu, Jul 21, 2016 at 3:29 PM, Josh Berkus wrote: > There is no external DNS server, here. I'm talking about a portable > microcluster, a stack of microboard computers, self-contained. The idea > would be to run some kind of local DNS server so that, on directly > connected machines, we could

Re: What actually is required for DNS and Origin?

2016-07-21 Thread Josh Berkus
On 07/21/2016 02:07 PM, Aleksandar Kostadinov wrote: > Then use plain IPs for nodes and masters. Then use xip.io for automatic > generated DNS names pointing at your NAT router. Make sure NAT router > forwards 80 and 443 to OpenShift cluster 80 and 443 ports respectively > of working router node(s

Re: What actually is required for DNS and Origin?

2016-07-21 Thread Aleksandar Kostadinov
Alex Wauck wrote on 07/21/16 23:40: On Thu, Jul 21, 2016 at 3:29 PM, Josh Berkus mailto:jber...@redhat.com>> wrote: There is no external DNS server, here. I'm talking about a portable microcluster, a stack of microboard computers, self-contained. The idea would be to run some kin

Re: What actually is required for DNS and Origin?

2016-07-21 Thread Josh Berkus
On 07/21/2016 01:03 PM, Aleksandar Kostadinov wrote: > Could you explain what kind of DNS are you talking about here? For the > exposed services? > Presently you just create wildcard A records pointing at your "router" > nodes and put the subdomain name in configuration. That you can do once > (or

Re: What actually is required for DNS and Origin?

2016-07-21 Thread Aleksandar Kostadinov
Josh Berkus wrote on 07/21/16 22:59: ... Just testing, for now, so the AWS DNS will work. I'll have to give some thought as to how I'll handle DNS on the hardware microcluster. Anyone have suggestions for a minimalist solution? I'd love to just run BIND on a container, but there's a bit of a c

Re: What actually is required for DNS and Origin?

2016-07-21 Thread Josh Berkus
On 07/21/2016 12:46 PM, Alex Wauck wrote: > > On Thu, Jul 21, 2016 at 2:32 PM, Aleksandar Kostadinov > mailto:akost...@redhat.com>> wrote: > > Two things as listed in the doc. One is to have hostnames of masters > and slaves resolvable over the configured DNS servers. > > > If you're on

Re: What actually is required for DNS and Origin?

2016-07-21 Thread Alex Wauck
On Thu, Jul 21, 2016 at 2:32 PM, Aleksandar Kostadinov wrote: > Two things as listed in the doc. One is to have hostnames of masters and > slaves resolvable over the configured DNS servers. > If you're on AWS, this is taken care of for you. Your masters and slaves and whatnot will all be referr

Re: What actually is required for DNS and Origin?

2016-07-21 Thread Aleksandar Kostadinov
Josh Berkus wrote on 07/21/16 22:17: Folks: https://docs.openshift.org/latest/install_config/install/prerequisites.html#install-config-install-prerequisites This goes on a bit about DNS requirements, but what's *actually* required is a bit unclear. Do I just need DNS support for the hostnames?

What actually is required for DNS and Origin?

2016-07-21 Thread Josh Berkus
Folks: https://docs.openshift.org/latest/install_config/install/prerequisites.html#install-config-install-prerequisites This goes on a bit about DNS requirements, but what's *actually* required is a bit unclear. Do I just need DNS support for the hostnames? Or do I need external DNS which suppo