Re: questions about externalIP usage

2017-08-15 Thread Yu Wei 
Hi Erik,

I configured "externalIPs" with cluster setup using flannel but it didn't work.

Then I reinstalled cluster with openvswitch. This time "externalIP" worked.


Is openvwitch suggested network plugin for openshift origin?

I deployed same application in k8s cluster and it worked.


Thanks,

Jared, (韦煜）
Software developer
Interested in open source software, big data, Linux


From: Erik Jacobs 
Sent: Wednesday, August 16, 2017 8:16:07 AM
To: Yu Wei
Cc: us...@lists.openshift.redhat.com; dev@lists.openshift.redhat.com
Subject: Re: questions about externalIP usage

Hi Jared,

Did you previously configure the cluster for externalip usage?

https://docs.openshift.org/latest/admin_guide/tcp_ingress_external_ports.html

---

ERIK JACOBS

PRINCIPAL TECHNICAL MARKETING MANAGER, OPENSHIFT

Red Hat Inc

ejac...@redhat.comM: 
646.462.3745 @: erikonopen

[https://www.redhat.com/files/brand/email/sig-redhat.png]
TRIED. TESTED. TRUSTED.


On Thu, Aug 10, 2017 at 4:12 AM, Yu Wei 
> wrote:

Hi guys,

I deployed redis with replication controller successfully on openshift origin 
cluster.

Then I tried to create service for external clients to connect.

However, it seemed that it didn't work.

How could I debug similar problem? Is there any guidance about using externalIP 
in openshift?


The detailed information is as below,

[root@host-10-1-236-92 gluster]# oc get svc
NAMECLUSTER-IP EXTERNAL-IP   
PORT(S)  AGE
glusterfs-cluster   172.30.6.143   1/TCP  
  1d
redis-svc   172.30.51.20   10.1.236.92,10.1.236.93,10.1.241.55   
26379/TCP,6379/TCP   24m
[root@host-10-1-236-92 gluster]# oc describe svc redis-svc
Name:redis-svc
Namespace:openshiift-servicebroker
Labels:
Selector:sb-2017-redis-master=master
Type:ClusterIP
IP:172.30.51.20
Port:redis-sen26379/TCP
Endpoints:172.30.41.5:26379
Port:redis-master6379/TCP
Endpoints:172.30.41.5:6379
Session Affinity:None
No events.
[root@host-10-1-236-92 gluster]# cat redis-master-svc.yaml
---
kind: Service
apiVersion: v1
metadata:
  name: redis-svc
spec:
selector:
  sb-2017-redis-master: master
ports:
  - name: redis-sen
protocol: TCP
port: 26379
targetPort: 26379
  - name: redis-master
protocol: TCP
port: 6379
targetPort: 6379
externalIPs:
  -  10.1.236.92
  -  10.1.236.93
  -  10.1.241.55



Thanks,

Jared, (韦煜）
Software developer
Interested in open source software, big data, Linux

___
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

Re: questions about externalIP usage

2017-08-15 Thread Erik Jacobs 
Hi Jared,

Did you previously configure the cluster for externalip usage?

https://docs.openshift.org/latest/admin_guide/tcp_ingress_external_ports.html

---

ERIK JACOBS

PRINCIPAL TECHNICAL MARKETING MANAGER, OPENSHIFT

Red Hat Inc 

ejac...@redhat.comM: 646.462.3745 @: erikonopen

TRIED. TESTED. TRUSTED. 

On Thu, Aug 10, 2017 at 4:12 AM, Yu Wei  wrote:

> Hi guys,
>
> I deployed redis with replication controller successfully on openshift
> origin cluster.
>
> Then I tried to create service for external clients to connect.
>
> However, it seemed that it didn't work.
>
> How could I debug similar problem? Is there any guidance about using
> externalIP in openshift?
>
>
> The detailed information is as below,
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *[root@host-10-1-236-92 gluster]# oc get svc NAME
> CLUSTER-IP EXTERNAL-IP   PORT(S)
> AGE glusterfs-cluster   172.30.6.143
> 1/TCP1d
> redis-svc   172.30.51.20   10.1.236.92,10.1.236.93,10.1.241.55
> 26379/TCP,6379/TCP   24m [root@host-10-1-236-92 gluster]# oc describe svc
> redis-svc Name:redis-svc Namespace:
>  openshiift-servicebroker Labels: Selector:
>  sb-2017-redis-master=master Type:ClusterIP IP:
>  172.30.51.20 Port:redis-sen26379/TCP Endpoints:
>  172.30.41.5:26379  Port:
>  redis-master6379/TCP Endpoints:172.30.41.5:6379
>  Session Affinity:None No events.*
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *[root@host-10-1-236-92 gluster]# cat redis-master-svc.yaml --- kind:
> Service apiVersion: v1 metadata:   name: redis-svc spec: selector:
>   sb-2017-redis-master: master ports:   - name: redis-sen
> protocol: TCP port: 26379 targetPort: 26379   -
> name: redis-master protocol: TCP port: 6379
> targetPort: 6379 externalIPs:   -  10.1.236.92   -  10.1.236.93
>   -  10.1.241.55*
>
>
> Thanks,
>
> Jared, (韦煜）
> Software developer
> Interested in open source software, big data, Linux
>
> ___
> 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

Re: query on persistent volumes

2017-08-15 Thread Erik Jacobs 
Hi Pri,

Are you asking about what happens when you scale up the Gluster pods, or
the app pods?

---

ERIK JACOBS

PRINCIPAL TECHNICAL MARKETING MANAGER, OPENSHIFT

Red Hat Inc 

ejac...@redhat.comM: 646.462.3745 @: erikonopen

TRIED. TESTED. TRUSTED. 

On Fri, Aug 4, 2017 at 10:59 AM, Pri  wrote:

> Hi,
>
> I am using glusterfs (container native storage) on OCP 3.5. I have one
> doubt, what happens to the storage when we scale up the pods (replicas=5) ,
> will all the pods persist data on same storage?
>
> Would be great if someone can help me understand this.
>
> Thanks in advance.
> Pri
>
> ___
> 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

Re: HAProxy not running on master

2017-08-15 Thread Yu Wei 
Yes, I set master as work nodes and as infra nodes.

Thanks for your help. I understood this concept now.



Thanks,

Jared, (韦煜）
Software developer
Interested in open source software, big data, Linux


From: Akram Ben Aissi 
Sent: Tuesday, August 15, 2017 7:11:03 PM
To: Yu Wei
Cc: us...@lists.openshift.redhat.com; dev@lists.openshift.redhat.com
Subject: Re: HAProxy not running on master

Hi Yui,

the masters runs the OpenShift API and web console on port 8443. OpenShift CLI 
or nodes communicates with master on this port.
OpenShift router are not really supposed to run on masters, unless you set your 
masters also as nodes, and specifically as infra nodes (region=infra)

If you do so, then, indeed, you will have an additional HAProxy process running 
on masters and listening on ports 80 and 443.




On 15 August 2017 at 12:47, Yu Wei 
> wrote:

Hi,


I setup cluster with 1 lb, 2 masters and 2 work nodes.

On host lb, haproxy service and openshift_loadbalancer was running.

On master node, I found that haproxy was failed to start. And 
openshift/origin-haproxy-router was running with container name 
k8s_router.xxx.

I also observed that on that master node many connections was established via 
port 8443.


Is this expected behavior? Or anything goes wrong?


Thanks,

Jared, (韦煜）
Software developer
Interested in open source software, big data, Linux

___
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

Re: HAProxy not running on master

2017-08-15 Thread Akram Ben Aissi 
Hi Yui,

the masters runs the OpenShift API and web console on port 8443. OpenShift
CLI or nodes communicates with master on this port.
OpenShift router are not really supposed to run on masters, unless you set
your masters also as nodes, and specifically as infra nodes (region=infra)

If you do so, then, indeed, you will have an additional HAProxy process
running on masters and listening on ports 80 and 443.




On 15 August 2017 at 12:47, Yu Wei  wrote:

> Hi,
>
>
> I setup cluster with 1 lb, 2 masters and 2 work nodes.
>
> On host lb, haproxy service and openshift_loadbalancer was running.
>
> On master node, I found that haproxy was failed to start. And
> openshift/origin-haproxy-router was running with container name
> k8s_router.xxx.
>
> I also observed that on that master node many connections was established
> via port 8443.
>
>
> Is this expected behavior? Or anything goes wrong?
>
>
> Thanks,
>
> Jared, (韦煜）
> Software developer
> Interested in open source software, big data, Linux
>
> ___
> 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

HAProxy not running on master

2017-08-15 Thread Yu Wei 
Hi,


I setup cluster with 1 lb, 2 masters and 2 work nodes.

On host lb, haproxy service and openshift_loadbalancer was running.

On master node, I found that haproxy was failed to start. And 
openshift/origin-haproxy-router was running with container name 
k8s_router.xxx.

I also observed that on that master node many connections was established via 
port 8443.


Is this expected behavior? Or anything goes wrong?


Thanks,

Jared, (韦煜）
Software developer
Interested in open source software, big data, Linux
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev

Different behavior between installing openshift origin with openvswitch and flannel

2017-08-15 Thread Yu Wei 
Hi guys,

I tried to get external traffic into openshift origin cluster using 
nodeport/externalIPs.

When I setup openshift cluster with flannel, exposing service with 
nodeport/externalIPs did not work.

When switched to openvswitch, both worked.


Is this expected behavior? Or did I miss anything?


Thanks,

Jared, (韦煜）
Software developer
Interested in open source software, big data, Linux
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev