Re: Openshift origin - nodes in vlans

2017-06-20 Thread Frederic Giloux
Hi Lukasz, this is not an unusual setup. You will need: - the SDN port: 4789 UDP (both directions: masters/nodes to nodes) - the kubelet port: 10250 TCP (masters to nodes) - the DNS port: 8053 TCP/UDP (nodes to masters) If you can't reach VLAN b pods from VLAN A the issue is probably with the SDN

Openshift origin - nodes in vlans

2017-06-20 Thread Łukasz Strzelec
-- Hello, I have to install OSO with dedicated HW nodes for one of my customer. Current cluster is placed in VLAN (for the sake of this question) called: VLAN_A The Customer's nodes have to be place in another vlan: VLAN_B Now the question, what ports and routes I have to setup to get this t

Re: oc whoami bug?

2017-06-20 Thread Louis Santillan
Whoops. Hit the Send button early. $ ocx () { ( oc project >/dev/null 2>&1 ) && oc $@ || echo "ERROR: You may not be logged in!" ; } $ ocx get pods -o wide --- LOUIS P. SANTILLAN SENIOR CONSULTANT, OPENSHIFT, MIDDLEWARE & DEV

Re: oc whoami bug?

2017-06-20 Thread Louis Santillan
$ ocx () { oc project 2&>/dev/null && oc $@ || echo "ERROR: You may not be logged in!" ; } $ ocx get pods -o wide --- LOUIS P. SANTILLAN SENIOR CONSULTANT, OPENSHIFT, MIDDLEWARE & DEVOPS Red Hat Consulting, NA US WEST

Re: oc whoami bug?

2017-06-20 Thread Jordan Liggitt
`oc whoami -t` doesn't talk to the server at all... it just prints your current session's token On Tue, Jun 20, 2017 at 2:31 PM, Louis Santillan wrote: > The `oc` command always looks for the current session in > `~/.kube/config`. It doesn't know if a session is expired or not since > session

Re: oc whoami bug?

2017-06-20 Thread Louis Santillan
The `oc` command always looks for the current session in `~/.kube/config`. It doesn't know if a session is expired or not since session timeouts are configurable and could have changed since the last API call was made to the master(s). You can run your `oc` commands to with `--loglevel=8` to see t

Re: split long log records

2017-06-20 Thread Rich Megginson
On 06/19/2017 10:48 AM, Peter Portante wrote: Hi Andre, This is a hard-coded Docker size. For background see: * https://bugzilla.redhat.com/show_bug.cgi?id=1422008, "[RFE] Fluentd handling of long log lines (> 16KB) split by Docker and indexed into several ES documents" * And the reason

Re: oc whoami bug?

2017-06-20 Thread Philippe Lafoucrière
On Mon, Jun 19, 2017 at 4:56 PM, Louis Santillan wrote: > The default user for any request is `system:anonymous` a user is not > logged in or a valid token is not found. Depending on your cluster, this > usually has almost no access (less than `system:authenticated`). Maybe an > RFE is order (o

Re: OpenShift build from git repo

2017-06-20 Thread Ben Parees
On Tue, Jun 20, 2017 at 9:24 AM, Jonathan Alvarsson < jonathan.alvars...@genettasoft.com> wrote: > Hi! > > I am trying to initialise an OpenShift build from a git repository > using an ssh-key as as secret: > > $ oc new-build --name=modelingweb > g...@bitbucket.org:genettasoft/gs_modelling_web

OpenShift build from git repo

2017-06-20 Thread Jonathan Alvarsson
Hi! I am trying to initialise an OpenShift build from a git repository using an ssh-key as as secret: $ oc new-build --name=modelingweb g...@bitbucket.org:genettasoft/gs_modelling_web.git --build-secret deploymentkey But it seems like my git url is not recognised as a git url: error: no

Re: split long log records

2017-06-20 Thread Andre Esser
Understood. Thanks Peter On 2017-06-19 17:48, Peter Portante wrote: Hi Andre, This is a hard-coded Docker size. For background see: * https://bugzilla.redhat.com/show_bug.cgi?id=1422008, "[RFE] Fluentd handling of long log lines (> 16KB) split by Docker and indexed into several ES document