Re: Low Disk Watermark

2016-08-31 Thread Luke Meyer
Looks like you're using your root partition for docker volume storage (and thus Elasticsearch storage). That is the default configuration, but not a recommended one - we recommend specifying storage specifically for docker

Re: Error from server: Timeout: timed out waiting for build ruby-hello-world-1 to start after 10s

2016-08-31 Thread Ben Parees
On Wed, Aug 31, 2016 at 1:09 PM, Ricardo Aguirre Reyes | BEEVA MX < ricardo.aguirre.contrac...@beeva.com> wrote: > Hi, > I just installed Openshift in a Cluster > etcd > infrastructure > NFS > LB > Master1 > Master2 > Node1 > Node2 > Node3 > > At first I have some problems because on the NFS

Error from server: Timeout: timed out waiting for build ruby-hello-world-1 to start after 10s

2016-08-31 Thread Ricardo Aguirre Reyes | BEEVA MX
Hi, I just installed Openshift in a Cluster etcd infrastructure NFS LB Master1 Master2 Node1 Node2 Node3 At first I have some problems because on the NFS host, the directory /exports/registry/ was bussy and openshift couldn't write there Then I removed it and created a new one with: mkdir

Re: Spurious warning when updating route without spec.host

2016-08-31 Thread Pieter Nagel
On Wed, Aug 31, 2016 at 2:44 PM, Jessica Forrester wrote: > Can you check the About page in the console (under the ? menu), or run `oc > version` to get the openshift master version I just confirmed, the bug is gone in the v1.3.0-alpha.3+bbeb2f3 all-in-one VM. I had been

Re: Spurious warning when updating route without spec.host

2016-08-31 Thread Jessica Forrester
Can you check the About page in the console (under the ? menu), or run `oc version` to get the openshift master version On Wed, Aug 31, 2016 at 8:36 AM, Pieter Nagel wrote: > > On Wed, Aug 31, 2016 at 2:30 PM, Jordan Liggitt > wrote: > >> What version

Re: Spurious warning when updating route without spec.host

2016-08-31 Thread Pieter Nagel
On Wed, Aug 31, 2016 at 2:30 PM, Jordan Liggitt wrote: > What version are you using? A similar bug (https://github.com/openshift/ > origin/issues/9417) was fixed in 1.3.0-alpha3 in https://github.com/ > openshift/origin/pull/9425 >

Re: Spurious warning when updating route without spec.host

2016-08-31 Thread Jordan Liggitt
What version are you using? A similar bug ( https://github.com/openshift/origin/issues/9417) was fixed in 1.3.0-alpha3 in https://github.com/openshift/origin/pull/9425 On Aug 31, 2016, at 8:25 AM, Clayton Coleman wrote:

Re: Spurious warning when updating route without spec.host

2016-08-31 Thread Clayton Coleman
Yes, please file a bug. On Aug 31, 2016, at 4:08 AM, Pieter Nagel wrote: Given a route definition in yaml that omits the spec.host value, OpenShift will auto-generate a suitable host value, i.e. blah-project.apps.10.2.2.2.xip.io on the all-in-one VM. That's great, because

Re: Openshift SDN considerations

2016-08-31 Thread Skarbek, John
Boris, Regarding question one, this would be solved by using a route that is exposed by said authentication service. This prevents the need for having to join the various projects together. Only services between namespaces are locked down. The exposed route will still be available to any and

Spurious warning when updating route without spec.host

2016-08-31 Thread Pieter Nagel
Given a route definition in yaml that omits the spec.host value, OpenShift will auto-generate a suitable host value, i.e. blah-project.apps.10.2.2.2.xip.io on the all-in-one VM. That's great, because then I can write route definitions that work unchanged in the all-in-one VM and RedHat's