From rushi.ns at sap.com  Tue May  2 02:33:04 2017
From: rushi.ns at sap.com (Ns, Rushi)
Date: Tue, 2 May 2017 08:33:04 +0000
Subject: [caasp-beta] grafana,
 influxdb load balance bind-IP  is not working
Message-ID: <FC024B1B-DB58-40AB-8EED-833BFA0CADEB@sap.com>

Does anone experience the same issue I see also the kubectl proxy never get stuck so there is no way to expose the application outside network as they are in cluster network (172.20.*.*)





Best Regards,
 
Rushi.
I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE
 

On 4/26/17, 8:59 PM, "caasp-beta-bounces at lists.suse.com on behalf of Ns, Rushi" <caasp-beta-bounces at lists.suse.com on behalf of rushi.ns at sap.com> wrote:

    Hello
    
    I have deployed load balancer, grafana, influx db . pretty all active , grafana and influxbd wih load balancer (also kubernetes dashboard) .
    
    From cluster info output everything seems fine but I cannot get the  access using browser (chrome, IE )
    
    Kubernetes master is running at http://localhost:8080
    Heapster is running at http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/heapster
    monitoring-grafana is running at http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana
    monitoring-influxdb is running at http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb
    
    
    NAME                      ENDPOINTS           AGE
    heapster                  172.20.92.2:8082    11d
    kube-controller-manager   <none>              21d
    kube-scheduler            <none>              21d
    kubernetes-dashboard      172.20.92.3:9090    11d
    monitoring-grafana        172.20.104.3:3000   11d
    monitoring-influxdb       172.20.104.2:8086   11d
    
    
    dashboard show bind-ip 
    
    kubectl get configmap grafana-configmap-dashboard-svc -o yaml
    apiVersion: v1
    data:
      bind-ip: 10.48.230.130
    
    the IP seems acive (icmp responds) but http://10.48.230.130:8080/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana is not working 
    
    Any idea 
    
    
    Best Regards,
     
    Rushi.
    I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE
     
    
    On 4/26/17, 5:07 PM, "caasp-beta-bounces at lists.suse.com on behalf of Ralf Bueker" <caasp-beta-bounces at lists.suse.com on behalf of Ralf.Bueker at suse.com> wrote:
    
        
        Found it... .
        
        Thanks  :-)
        
        kind regards
        
        Ralf
        On Wed, 2017-04-26 at 16:48 +0200, Thorsten Kukuk wrote:
        > On Wed, Apr 26, Ralf Bueker wrote:
        > 
        > > 
        > > Hi, 
        > > 
        > > I am trying to install caasp Beta 2 from DVD. 
        > > As far as I understood ( I am not so sure if I did ... ) salt master should
        > > be
        > > installed on the admin node, installed first. 
        > > 
        > > But it seems that does not happen. 
        > 
        > Run "docker images" ;)
        > 
        > The salt-master is inside a container
        > 
        >   Thorsten
        > 
        _______________________________________________
        caasp-beta mailing list
        caasp-beta at lists.suse.com
        http://lists.suse.com/mailman/listinfo/caasp-beta
        
    
    _______________________________________________
    caasp-beta mailing list
    caasp-beta at lists.suse.com
    http://lists.suse.com/mailman/listinfo/caasp-beta
    


From msabate at suse.com  Tue May  2 04:25:39 2017
From: msabate at suse.com (Miquel =?utf-8?B?U2FiYXTDqSBTb2zDoA==?=)
Date: Tue, 02 May 2017 12:25:39 +0200
Subject: [caasp-beta] grafana,
	influxdb load balance bind-IP  is not working
In-Reply-To: <FC024B1B-DB58-40AB-8EED-833BFA0CADEB@sap.com>
References: <FC024B1B-DB58-40AB-8EED-833BFA0CADEB@sap.com>
Message-ID: <877f1zeesc.fsf@suse.com>

Hi,

First of all, what do you exactly mean when you say that you "have 
deployed load balancer" ? Are you talking about an ingress 
controller ? Could you give us more details ? Could you also 
provide the manifest files that you have used ?

Could you also provide the output for (or similar, and make sure 
you are using the proper namespace):

      $ kubectl describe svc grafana

That output might give us some further hints in regard to how to 
consume it.

Greetings,

Ns, Rushi @ 2017-05-02 08:33 GMT:

> Does anone experience the same issue I see also the kubectl 
> proxy never get stuck so there is no way to expose the 
> application outside network as they are in cluster network 
> (172.20.*.*)
>
>
>
>
>
> Best Regards,
>
> Rushi.
> I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A 
> DIFFERENCE
>
>
> On 4/26/17, 8:59 PM, "caasp-beta-bounces at lists.suse.com on 
> behalf of Ns, Rushi" <caasp-beta-bounces at lists.suse.com on 
> behalf of rushi.ns at sap.com> wrote:
>
>     Hello
>
>     I have deployed load balancer, grafana, influx db . pretty 
>     all active , grafana and influxbd wih load balancer (also 
>     kubernetes dashboard) .
>
>     From cluster info output everything seems fine but I cannot 
>     get the  access using browser (chrome, IE )
>
>     Kubernetes master is running at http://localhost:8080
>     Heapster is running at 
>     http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/heapster
>     monitoring-grafana is running at 
>     http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana
>     monitoring-influxdb is running at 
>     http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb
>
>
>     NAME                      ENDPOINTS           AGE
>     heapster                  172.20.92.2:8082    11d
>     kube-controller-manager   <none>              21d
>     kube-scheduler            <none>              21d
>     kubernetes-dashboard      172.20.92.3:9090    11d
>     monitoring-grafana        172.20.104.3:3000   11d
>     monitoring-influxdb       172.20.104.2:8086   11d
>
>
>     dashboard show bind-ip
>
>     kubectl get configmap grafana-configmap-dashboard-svc -o 
>     yaml
>     apiVersion: v1
>     data:
>       bind-ip: 10.48.230.130
>
>     the IP seems acive (icmp responds) but 
>     http://10.48.230.130:8080/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana 
>     is not working
>
>     Any idea
>
>
>     Best Regards,
>
>     Rushi.
>     I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES 
>     A DIFFERENCE
>
>
>     On 4/26/17, 5:07 PM, "caasp-beta-bounces at lists.suse.com on 
>     behalf of Ralf Bueker" <caasp-beta-bounces at lists.suse.com on 
>     behalf of Ralf.Bueker at suse.com> wrote:
>
>
>         Found it... .
>
>         Thanks  :-)
>
>         kind regards
>
>         Ralf
>         On Wed, 2017-04-26 at 16:48 +0200, Thorsten Kukuk wrote:
>         > On Wed, Apr 26, Ralf Bueker wrote:
>         >
>         > >
>         > > Hi,
>         > >
>         > > I am trying to install caasp Beta 2 from DVD.
>         > > As far as I understood ( I am not so sure if I did 
>         > > ... ) salt master should
>         > > be
>         > > installed on the admin node, installed first.
>         > >
>         > > But it seems that does not happen.
>         >
>         > Run "docker images" ;)
>         >
>         > The salt-master is inside a container
>         >
>         >   Thorsten
>         >
>         _______________________________________________
>         caasp-beta mailing list
>         caasp-beta at lists.suse.com
>         http://lists.suse.com/mailman/listinfo/caasp-beta
>
>
>     _______________________________________________
>     caasp-beta mailing list
>     caasp-beta at lists.suse.com
>     http://lists.suse.com/mailman/listinfo/caasp-beta
>
>
> _______________________________________________
> caasp-beta mailing list
> caasp-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/caasp-beta


--
Miquel Sabat? Sol?,
PGP: 4096R / 1BA5 3C7A C93D CA2A CFDF DA97 96BE 8C6F D89D 6565
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 800 bytes
Desc: not available
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20170502/bd39e2d1/attachment.sig>

From rushi.ns at sap.com  Tue May  2 04:47:07 2017
From: rushi.ns at sap.com (Ns, Rushi)
Date: Tue, 2 May 2017 10:47:07 +0000
Subject: [caasp-beta] grafana,
 influxdb load balance bind-IP  is not working
In-Reply-To: <877f1zeesc.fsf@suse.com>
References: <FC024B1B-DB58-40AB-8EED-833BFA0CADEB@sap.com>
	<877f1zeesc.fsf@suse.com>
Message-ID: <DBF57C67-060C-45BF-BE4A-C3E63482B412@sap.com>

Hi 

Yes ingresss. 

Here is the details of service.
===========================

hostmaster:/etc/kubernetes # kubectl describe svc monitoring-grafana --namespace=kube-system
Name:  			monitoring-grafana
Namespace:     		kube-system
Labels:			kubernetes.io/cluster-service=true
       			kubernetes.io/name=monitoring-grafana
Selector:      		k8s-app=grafana
Type:  			ClusterIP
IP:    			172.21.70.111
Port:  			<unset>	80/TCP
Endpoints:     		172.17.0.2:3000
Session Affinity:      	None
No events.


Here is the output of load balancer BIND IP
=============================
hostmaster:/kubectl get configmap grafana-configmap-dashboard-svc -o yaml
apiVersion: v1
data:
  bind-ip: 10.125.0.225
  namespace: kube-system
  status: SUCCESS
  target-service-name: monitoring-grafana
kind: ConfigMap
metadata:
  creationTimestamp: 2017-04-28T12:19:39Z
  labels:
    app: loadbalancer
  name: grafana-configmap-dashboard-svc
  namespace: default
  resourceVersion: "342438"
  selfLink: /api/v1/namespaces/default/configmaps/grafana-configmap-dashboard-svc
  uid: f396ebba-2c0c-11e7-8c82-ac162dbc0bac


here is the  grafana manifest file
===========================
hostmaster:/tmp/heapster # more grafana-configmap-dashboard.yaml
apiVersion: v1
kind: ConfigMap
metadata:
    name: grafana-configmap-dashboard-svc
    labels:
        app: loadbalancer
data:
  namespace: "kube-system"
  target-service-name: "monitoring-grafana"
============


Best Regards,
 
Rushi.
I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE
 

On 5/2/17, 12:25 PM, "Miquel Sabat? Sol?" <msabate at suse.com> wrote:

    Hi,
    
    First of all, what do you exactly mean when you say that you "have 
    deployed load balancer" ? Are you talking about an ingress 
    controller ? Could you give us more details ? Could you also 
    provide the manifest files that you have used ?
    
    Could you also provide the output for (or similar, and make sure 
    you are using the proper namespace):
    
          $ kubectl describe svc grafana
    
    That output might give us some further hints in regard to how to 
    consume it.
    
    Greetings,
    
    Ns, Rushi @ 2017-05-02 08:33 GMT:
    
    > Does anone experience the same issue I see also the kubectl 
    > proxy never get stuck so there is no way to expose the 
    > application outside network as they are in cluster network 
    > (172.20.*.*)
    >
    >
    >
    >
    >
    > Best Regards,
    >
    > Rushi.
    > I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A 
    > DIFFERENCE
    >
    >
    > On 4/26/17, 8:59 PM, "caasp-beta-bounces at lists.suse.com on 
    > behalf of Ns, Rushi" <caasp-beta-bounces at lists.suse.com on 
    > behalf of rushi.ns at sap.com> wrote:
    >
    >     Hello
    >
    >     I have deployed load balancer, grafana, influx db . pretty 
    >     all active , grafana and influxbd wih load balancer (also 
    >     kubernetes dashboard) .
    >
    >     From cluster info output everything seems fine but I cannot 
    >     get the  access using browser (chrome, IE )
    >
    >     Kubernetes master is running at http://localhost:8080
    >     Heapster is running at 
    >     http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/heapster
    >     monitoring-grafana is running at 
    >     http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana
    >     monitoring-influxdb is running at 
    >     http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb
    >
    >
    >     NAME                      ENDPOINTS           AGE
    >     heapster                  172.20.92.2:8082    11d
    >     kube-controller-manager   <none>              21d
    >     kube-scheduler            <none>              21d
    >     kubernetes-dashboard      172.20.92.3:9090    11d
    >     monitoring-grafana        172.20.104.3:3000   11d
    >     monitoring-influxdb       172.20.104.2:8086   11d
    >
    >
    >     dashboard show bind-ip
    >
    >     kubectl get configmap grafana-configmap-dashboard-svc -o 
    >     yaml
    >     apiVersion: v1
    >     data:
    >       bind-ip: 10.48.230.130
    >
    >     the IP seems acive (icmp responds) but 
    >     http://10.48.230.130:8080/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana 
    >     is not working
    >
    >     Any idea
    >
    >
    >     Best Regards,
    >
    >     Rushi.
    >     I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES 
    >     A DIFFERENCE
    >
    >
    >     On 4/26/17, 5:07 PM, "caasp-beta-bounces at lists.suse.com on 
    >     behalf of Ralf Bueker" <caasp-beta-bounces at lists.suse.com on 
    >     behalf of Ralf.Bueker at suse.com> wrote:
    >
    >
    >         Found it... .
    >
    >         Thanks  :-)
    >
    >         kind regards
    >
    >         Ralf
    >         On Wed, 2017-04-26 at 16:48 +0200, Thorsten Kukuk wrote:
    >         > On Wed, Apr 26, Ralf Bueker wrote:
    >         >
    >         > >
    >         > > Hi,
    >         > >
    >         > > I am trying to install caasp Beta 2 from DVD.
    >         > > As far as I understood ( I am not so sure if I did 
    >         > > ... ) salt master should
    >         > > be
    >         > > installed on the admin node, installed first.
    >         > >
    >         > > But it seems that does not happen.
    >         >
    >         > Run "docker images" ;)
    >         >
    >         > The salt-master is inside a container
    >         >
    >         >   Thorsten
    >         >
    >         _______________________________________________
    >         caasp-beta mailing list
    >         caasp-beta at lists.suse.com
    >         http://lists.suse.com/mailman/listinfo/caasp-beta
    >
    >
    >     _______________________________________________
    >     caasp-beta mailing list
    >     caasp-beta at lists.suse.com
    >     http://lists.suse.com/mailman/listinfo/caasp-beta
    >
    >
    > _______________________________________________
    > caasp-beta mailing list
    > caasp-beta at lists.suse.com
    > http://lists.suse.com/mailman/listinfo/caasp-beta
    
    
    --
    Miquel Sabat? Sol?,
    PGP: 4096R / 1BA5 3C7A C93D CA2A CFDF DA97 96BE 8C6F D89D 6565
    



From alvaro.saurin at suse.com  Tue May  2 09:26:45 2017
From: alvaro.saurin at suse.com (Alvaro Saurin)
Date: Tue, 2 May 2017 17:26:45 +0200
Subject: [caasp-beta] grafana,
 influxdb load balance bind-IP is not working
In-Reply-To: <DBF57C67-060C-45BF-BE4A-C3E63482B412@sap.com>
References: <FC024B1B-DB58-40AB-8EED-833BFA0CADEB@sap.com>
	<877f1zeesc.fsf@suse.com>
	<DBF57C67-060C-45BF-BE4A-C3E63482B412@sap.com>
Message-ID: <f4db378f-a4eb-d56d-7c43-af00fe717726@suse.com>


Hi there,

Can you access the Kubernetes dashboard? If you can, how are you
accessing it? What URL are you connecting to? Are you using "kubectl
proxy"? Where are you running it?
What kind of environment are you using? VMs?
Have you tried to run some other simple Kubernetes application?




Alvaro




On 05/02/2017 12:47 PM, Ns, Rushi wrote:
> Hi 
>
> Yes ingresss. 
>
> Here is the details of service.
> ===========================
>
> hostmaster:/etc/kubernetes # kubectl describe svc monitoring-grafana --namespace=kube-system
> Name:  			monitoring-grafana
> Namespace:     		kube-system
> Labels:			kubernetes.io/cluster-service=true
>        			kubernetes.io/name=monitoring-grafana
> Selector:      		k8s-app=grafana
> Type:  			ClusterIP
> IP:    			172.21.70.111
> Port:  			<unset>	80/TCP
> Endpoints:     		172.17.0.2:3000
> Session Affinity:      	None
> No events.
>
>
> Here is the output of load balancer BIND IP
> =============================
> hostmaster:/kubectl get configmap grafana-configmap-dashboard-svc -o yaml
> apiVersion: v1
> data:
>   bind-ip: 10.125.0.225
>   namespace: kube-system
>   status: SUCCESS
>   target-service-name: monitoring-grafana
> kind: ConfigMap
> metadata:
>   creationTimestamp: 2017-04-28T12:19:39Z
>   labels:
>     app: loadbalancer
>   name: grafana-configmap-dashboard-svc
>   namespace: default
>   resourceVersion: "342438"
>   selfLink: /api/v1/namespaces/default/configmaps/grafana-configmap-dashboard-svc
>   uid: f396ebba-2c0c-11e7-8c82-ac162dbc0bac
>
>
> here is the  grafana manifest file
> ===========================
> hostmaster:/tmp/heapster # more grafana-configmap-dashboard.yaml
> apiVersion: v1
> kind: ConfigMap
> metadata:
>     name: grafana-configmap-dashboard-svc
>     labels:
>         app: loadbalancer
> data:
>   namespace: "kube-system"
>   target-service-name: "monitoring-grafana"
> ============
>
>
> Best Regards,
>  
> Rushi.
> I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE
>  
>
> On 5/2/17, 12:25 PM, "Miquel Sabat? Sol?" <msabate at suse.com> wrote:
>
>     Hi,
>     
>     First of all, what do you exactly mean when you say that you "have 
>     deployed load balancer" ? Are you talking about an ingress 
>     controller ? Could you give us more details ? Could you also 
>     provide the manifest files that you have used ?
>     
>     Could you also provide the output for (or similar, and make sure 
>     you are using the proper namespace):
>     
>           $ kubectl describe svc grafana
>     
>     That output might give us some further hints in regard to how to 
>     consume it.
>     
>     Greetings,
>     
>     Ns, Rushi @ 2017-05-02 08:33 GMT:
>     
>     > Does anone experience the same issue I see also the kubectl 
>     > proxy never get stuck so there is no way to expose the 
>     > application outside network as they are in cluster network 
>     > (172.20.*.*)
>     >
>     >
>     >
>     >
>     >
>     > Best Regards,
>     >
>     > Rushi.
>     > I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A 
>     > DIFFERENCE
>     >
>     >
>     > On 4/26/17, 8:59 PM, "caasp-beta-bounces at lists.suse.com on 
>     > behalf of Ns, Rushi" <caasp-beta-bounces at lists.suse.com on 
>     > behalf of rushi.ns at sap.com> wrote:
>     >
>     >     Hello
>     >
>     >     I have deployed load balancer, grafana, influx db . pretty 
>     >     all active , grafana and influxbd wih load balancer (also 
>     >     kubernetes dashboard) .
>     >
>     >     From cluster info output everything seems fine but I cannot 
>     >     get the  access using browser (chrome, IE )
>     >
>     >     Kubernetes master is running at http://localhost:8080
>     >     Heapster is running at 
>     >     http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/heapster
>     >     monitoring-grafana is running at 
>     >     http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana
>     >     monitoring-influxdb is running at 
>     >     http://localhost:8080/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb
>     >
>     >
>     >     NAME                      ENDPOINTS           AGE
>     >     heapster                  172.20.92.2:8082    11d
>     >     kube-controller-manager   <none>              21d
>     >     kube-scheduler            <none>              21d
>     >     kubernetes-dashboard      172.20.92.3:9090    11d
>     >     monitoring-grafana        172.20.104.3:3000   11d
>     >     monitoring-influxdb       172.20.104.2:8086   11d
>     >
>     >
>     >     dashboard show bind-ip
>     >
>     >     kubectl get configmap grafana-configmap-dashboard-svc -o 
>     >     yaml
>     >     apiVersion: v1
>     >     data:
>     >       bind-ip: 10.48.230.130
>     >
>     >     the IP seems acive (icmp responds) but 
>     >     http://10.48.230.130:8080/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana 
>     >     is not working
>     >
>     >     Any idea
>     >
>     >
>     >     Best Regards,
>     >
>     >     Rushi.
>     >     I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES 
>     >     A DIFFERENCE
>     >
>     >
>     >     On 4/26/17, 5:07 PM, "caasp-beta-bounces at lists.suse.com on 
>     >     behalf of Ralf Bueker" <caasp-beta-bounces at lists.suse.com on 
>     >     behalf of Ralf.Bueker at suse.com> wrote:
>     >
>     >
>     >         Found it... .
>     >
>     >         Thanks  :-)
>     >
>     >         kind regards
>     >
>     >         Ralf
>     >         On Wed, 2017-04-26 at 16:48 +0200, Thorsten Kukuk wrote:
>     >         > On Wed, Apr 26, Ralf Bueker wrote:
>     >         >
>     >         > >
>     >         > > Hi,
>     >         > >
>     >         > > I am trying to install caasp Beta 2 from DVD.
>     >         > > As far as I understood ( I am not so sure if I did 
>     >         > > ... ) salt master should
>     >         > > be
>     >         > > installed on the admin node, installed first.
>     >         > >
>     >         > > But it seems that does not happen.
>     >         >
>     >         > Run "docker images" ;)
>     >         >
>     >         > The salt-master is inside a container
>     >         >
>     >         >   Thorsten
>     >         >
>     >         _______________________________________________
>     >         caasp-beta mailing list
>     >         caasp-beta at lists.suse.com
>     >         http://lists.suse.com/mailman/listinfo/caasp-beta
>     >
>     >
>     >     _______________________________________________
>     >     caasp-beta mailing list
>     >     caasp-beta at lists.suse.com
>     >     http://lists.suse.com/mailman/listinfo/caasp-beta
>     >
>     >
>     > _______________________________________________
>     > caasp-beta mailing list
>     > caasp-beta at lists.suse.com
>     > http://lists.suse.com/mailman/listinfo/caasp-beta
>     
>     
>     --
>     Miquel Sabat? Sol?,
>     PGP: 4096R / 1BA5 3C7A C93D CA2A CFDF DA97 96BE 8C6F D89D 6565
>     
>
>
> _______________________________________________
> caasp-beta mailing list
> caasp-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/caasp-beta

-- 
Alvaro Saurin <alvaro.saurin at suse.com>
Senior Software Engineer
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 N?rnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/
SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg)


From alvaro.saurin at suse.com  Wed May  3 04:54:41 2017
From: alvaro.saurin at suse.com (Alvaro Saurin)
Date: Wed, 3 May 2017 12:54:41 +0200
Subject: [caasp-beta] CaaS 1.0 beta2 pods issues with behind proxy server
In-Reply-To: <0DB04740-33B8-417B-A31A-854D490F5B09@suse.com>
References: <A26DA7AD-B43E-465E-BD89-A510A4464271@sap.com>
	<2f61573e-3c5e-69c5-be9d-98a86c11db42@suse.com>
	<06D6B1A5-74ED-4BFC-9AB1-447FD5F536ED@sap.com>
	<baa837de-efd3-fafd-420e-fb29e7ea5463@suse.com>
	<7EBB480F-68E3-47F4-92DD-651F73BE3FA3@sap.com>
	<87k264evoq.fsf@suse.com>
	<0DB04740-33B8-417B-A31A-854D490F5B09@suse.com>
Message-ID: <3f10d7b9-1ce6-22e0-1b66-df78af9197e4@suse.com>


Hi Robert,

Sorry but I don't understand the relation between /etc/default/docker
and the HTTP_PROXY environment variable. Could you give more details?

Cheers


Alvaro



On 04/28/2017 06:09 PM, Robert Roland wrote:
> That shouldn't be necessary because our default Docker systemd uses
> /etc/default/docker as an EnvironmentFile?
>
>
> On April 28, 2017 2:19:17 AM PDT, "Miquel Sabat? Sol?"
> <msabate at suse.com> wrote:
>
>     Hello,
>
>     I've just opened a ticket in our internal bugzilla. We are 
>     tracking this issue internally and working on it. That being said, 
>     to make it work manually you should follow this steps:
>
>     1. ssh to each machine in the cluster
>
>     2. create a systemd drop-in directory for the docker service:
>
>         $ mkdir /etc/systemd/system/docker.service.d
>
>     3. create a file called 
>     /etc/systemd/system/docker.service.d/http-proxy.conf that adds the 
>     HTTP_PROXY environment variable:
>
>         [Service]
>         Environment="HTTP_PROXY=http://proxy.example.com:80/"
>
>     4. flush changes:
>
>         $ sudo systemctl daemon-reload
>
>     5. verify that the configuration has been loaded:
>
>         $ sudo systemctl show --property Environment docker
>         Environment=HTTP_PROXY=http://proxy.example.com:80/
>
>     6. restart Docker:
>
>         $ sudo systemctl restart docker
>
>     In the future we should ask the user about proxies in some 
>     "advanced configuration" option in YaST, pass it to the worker 
>     nodes through the autoyast.xml and set automatically the 
>     HTTP_PROXY for docker.
>
>     Cheers,
>
>     Ns @ 2017-04-27 15:20 GMT:
>
>         Hi Flavio, Yes I got information from Robert, however it
>         wasn?t working ?? Best Regards, Rushi. I MAY BE ONLY ONE
>         PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE On
>         4/27/17, 4:49 PM, "caasp-beta-bounces at lists.suse.com on behalf
>         of Flavio Castelli" <caasp-beta-bounces at lists.suse.com on
>         behalf of fcastelli at suse.com> wrote: On 04/26/2017 06:09 AM,
>         Ns, Rushi wrote:
>
>             As you mentioned you should try to provide that
>             information during the installation or some sort of
>             post-steps as all most all enterprise customers have proxy
>             to go internet. 
>
>         You are right, this is definitely something we should provide
>         either during the installation time or when deploying the
>         cluster from the web UI. I think Robert pointed you in the
>         right direction, please let us know if the proposed solution
>         is not working. Thanks for your feedback. Cheers Flavio
>         ------------------------------------------------------------------------
>         caasp-beta mailing list caasp-beta at lists.suse.com
>         http://lists.suse.com/mailman/listinfo/caasp-beta
>         ------------------------------------------------------------------------
>         caasp-beta mailing list caasp-beta at lists.suse.com
>         http://lists.suse.com/mailman/listinfo/caasp-beta 
>
>
>
>     --
>     Miquel Sabat? Sol?,
>     PGP: 4096R / 1BA5 3C7A C93D CA2A CFDF DA97 96BE 8C6F D89D 6565
>
> _______________________________________________
> caasp-beta mailing list
> caasp-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/caasp-beta
-- 
Alvaro Saurin <alvaro.saurin at suse.com>
Senior Software Engineer
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 N?rnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/
SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20170503/9aa230bf/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20170503/9aa230bf/attachment.sig>

From robert.roland at suse.com  Wed May  3 10:50:56 2017
From: robert.roland at suse.com (Robert Roland)
Date: Wed, 3 May 2017 09:50:56 -0700
Subject: [caasp-beta] CaaS 1.0 beta2 pods issues with behind proxy server
In-Reply-To: <3f10d7b9-1ce6-22e0-1b66-df78af9197e4@suse.com>
References: <A26DA7AD-B43E-465E-BD89-A510A4464271@sap.com>
	<2f61573e-3c5e-69c5-be9d-98a86c11db42@suse.com>
	<06D6B1A5-74ED-4BFC-9AB1-447FD5F536ED@sap.com>
	<baa837de-efd3-fafd-420e-fb29e7ea5463@suse.com>
	<7EBB480F-68E3-47F4-92DD-651F73BE3FA3@sap.com>
	<87k264evoq.fsf@suse.com>
	<0DB04740-33B8-417B-A31A-854D490F5B09@suse.com>
	<3f10d7b9-1ce6-22e0-1b66-df78af9197e4@suse.com>
Message-ID: <0ed58795-9898-7bdf-b1f7-194feb829c0c@suse.com>

The systemd unit for Docker contains:

[Service]
EnvironmentFile=/etc/sysconfig/docker

So, setting:

HTTP_PROXY=...
HTTPS_PROXY=...
NO_PROXY=...

inside /etc/sysconfig/docker should be sufficient to configure the 
proxies. You shouldn't need additional systemd drop-in files.


On 05/03/2017 03:54 AM, Alvaro Saurin wrote:
>
> Hi Robert,
>
> Sorry but I don't understand the relation between /etc/default/docker 
> and the HTTP_PROXY environment variable. Could you give more details?
>
> Cheers
>
>
> Alvaro
>
>
>
> On 04/28/2017 06:09 PM, Robert Roland wrote:
>> That shouldn't be necessary because our default Docker systemd uses 
>> /etc/default/docker as an EnvironmentFile?
>>
>>
>> On April 28, 2017 2:19:17 AM PDT, "Miquel Sabat? Sol?" 
>> <msabate at suse.com> wrote:
>>
>>     Hello,
>>
>>     I've just opened a ticket in our internal bugzilla. We are
>>     tracking this issue internally and working on it. That being said,
>>     to make it work manually you should follow this steps:
>>
>>     1. ssh to each machine in the cluster
>>
>>     2. create a systemd drop-in directory for the docker service:
>>
>>          $ mkdir /etc/systemd/system/docker.service.d
>>
>>     3. create a file called
>>     /etc/systemd/system/docker.service.d/http-proxy.conf that adds the
>>     HTTP_PROXY environment variable:
>>
>>          [Service]
>>          Environment="HTTP_PROXY=http://proxy.example.com:80/"
>>
>>     4. flush changes:
>>
>>          $ sudo systemctl daemon-reload
>>
>>     5. verify that the configuration has been loaded:
>>
>>          $ sudo systemctl show --property Environment docker
>>          Environment=HTTP_PROXY=http://proxy.example.com:80/
>>
>>     6. restart Docker:
>>
>>          $ sudo systemctl restart docker
>>
>>     In the future we should ask the user about proxies in some
>>     "advanced configuration" option in YaST, pass it to the worker
>>     nodes through the autoyast.xml and set automatically the
>>     HTTP_PROXY for docker.
>>
>>     Cheers,
>>
>>     Ns @ 2017-04-27 15:20 GMT:
>>
>>         Hi Flavio, Yes I got information from Robert, however it
>>         wasn?t working ?? Best Regards, Rushi. I MAY BE ONLY ONE
>>         PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE On
>>         4/27/17, 4:49 PM, "caasp-beta-bounces at lists.suse.com on
>>         behalf of Flavio Castelli" <caasp-beta-bounces at lists.suse.com
>>         on behalf of fcastelli at suse.com> wrote: On 04/26/2017 06:09
>>         AM, Ns, Rushi wrote:
>>
>>             As you mentioned you should try to provide that
>>             information during the installation or some sort of
>>             post-steps as all most all enterprise customers have
>>             proxy to go internet. 
>>
>>         You are right, this is definitely something we should provide
>>         either during the installation time or when deploying the
>>         cluster from the web UI. I think Robert pointed you in the
>>         right direction, please let us know if the proposed solution
>>         is not working. Thanks for your feedback. Cheers Flavio
>>         ------------------------------------------------------------------------
>>         caasp-beta mailing list caasp-beta at lists.suse.com
>>         http://lists.suse.com/mailman/listinfo/caasp-beta
>>         ------------------------------------------------------------------------
>>         caasp-beta mailing list caasp-beta at lists.suse.com
>>         http://lists.suse.com/mailman/listinfo/caasp-beta 
>>
>>
>>
>>     --
>>     Miquel Sabat? Sol?,
>>     PGP: 4096R / 1BA5 3C7A C93D CA2A CFDF DA97 96BE 8C6F D89D 6565
>>
>> _______________________________________________
>> caasp-beta mailing list
>> caasp-beta at lists.suse.com
>> http://lists.suse.com/mailman/listinfo/caasp-beta
> -- 
> Alvaro Saurin<alvaro.saurin at suse.com>
> Senior Software Engineer
> SUSE Linux GmbH, Maxfeldstr. 5, D-90409 N?rnberg Tel: +49-911-74053-0; Fax: +49-911-7417755;https://www.suse.com/
> SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20170503/8960e595/attachment.htm>

From aherzig at suse.com  Thu May  4 03:21:19 2017
From: aherzig at suse.com (Alexander Herzig)
Date: Thu, 4 May 2017 11:21:19 +0200
Subject: [caasp-beta] How to use the VM images in Beta3
In-Reply-To: <CFE618853F2AA643B9C669DA7C205FDF14A6EEF2@SUSHDC8004.TD.TERADATA.COM>
References: <CFE618853F2AA643B9C669DA7C205FDF14A6EEF2@SUSHDC8004.TD.TERADATA.COM>
Message-ID: <bc7ab7ee-5253-9283-a272-511e1532556e@suse.com>

Dear Qiyan,

thank you for testing our product.
May I point your attention to our documentation which you can find here: 
https://www.suse.com/betaprogram/caasp-beta/doc-quickstart/

Further we have made a video about how to setup a cluster here:
https://www.youtube.com/watch?v=hJf6FqNQhJ4&t=180s

If you install via autoyast or one of the provided VMX beta images 
(KVM,Xen,VMware,...) please set a password or SSH key via cloud-init to 
be able to login.

If you have further questions, please don't hesitate to drop some lines 
on this mailing list.

Best regards
Alexander


Am 03.05.2017 um 19:56 schrieb Sun, Qiyan:
> How to activate the administration node in Beta3 using the VM images?
> How to add a cluster node?
>
>
>
> Thanks,
>
> Qiyan
>
>
>
> _______________________________________________
> caasp-beta mailing list
> caasp-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/caasp-beta
>



From alvaro.saurin at suse.com  Thu May  4 07:02:21 2017
From: alvaro.saurin at suse.com (Alvaro Saurin)
Date: Thu, 4 May 2017 15:02:21 +0200
Subject: [caasp-beta] CaaS 1.0 beta2 pods issues with behind proxy server
In-Reply-To: <0ed58795-9898-7bdf-b1f7-194feb829c0c@suse.com>
References: <A26DA7AD-B43E-465E-BD89-A510A4464271@sap.com>
	<2f61573e-3c5e-69c5-be9d-98a86c11db42@suse.com>
	<06D6B1A5-74ED-4BFC-9AB1-447FD5F536ED@sap.com>
	<baa837de-efd3-fafd-420e-fb29e7ea5463@suse.com>
	<7EBB480F-68E3-47F4-92DD-651F73BE3FA3@sap.com>
	<87k264evoq.fsf@suse.com>
	<0DB04740-33B8-417B-A31A-854D490F5B09@suse.com>
	<3f10d7b9-1ce6-22e0-1b66-df78af9197e4@suse.com>
	<0ed58795-9898-7bdf-b1f7-194feb829c0c@suse.com>
Message-ID: <385ac097-c4de-9e40-9a25-76aa7c24b81d@suse.com>


Hi Robert,

There are multiple places where those vars could be defined: the systemd
unit files, dropin units, /etc/sysconfig/docker, etc... I don't think
the file you mentioned would be the best place for doing that and we
should avoid confusion and stick to the recommended solution you can
find in the Docker documentation
(https://docs.docker.com/engine/admin/systemd/#custom-docker-daemon-options)
that I provided to our user...

Cheers


Alvaro





On 05/03/2017 06:50 PM, Robert Roland wrote:
>
> The systemd unit for Docker contains:
>
> [Service]
> EnvironmentFile=/etc/sysconfig/docker
>
> So, setting:
>
> HTTP_PROXY=...
> HTTPS_PROXY=...
> NO_PROXY=...
>
> inside /etc/sysconfig/docker should be sufficient to configure the
> proxies. You shouldn't need additional systemd drop-in files.
>
>
> On 05/03/2017 03:54 AM, Alvaro Saurin wrote:
>>
>> Hi Robert,
>>
>> Sorry but I don't understand the relation between /etc/default/docker
>> and the HTTP_PROXY environment variable. Could you give more details?
>>
>> Cheers
>>
>>
>> Alvaro
>>
>>
>>
>> On 04/28/2017 06:09 PM, Robert Roland wrote:
>>> That shouldn't be necessary because our default Docker systemd uses
>>> /etc/default/docker as an EnvironmentFile?
>>>
>>>
>>> On April 28, 2017 2:19:17 AM PDT, "Miquel Sabat? Sol?"
>>> <msabate at suse.com> wrote:
>>>
>>>     Hello,
>>>
>>>     I've just opened a ticket in our internal bugzilla. We are 
>>>     tracking this issue internally and working on it. That being said, 
>>>     to make it work manually you should follow this steps:
>>>
>>>     1. ssh to each machine in the cluster
>>>
>>>     2. create a systemd drop-in directory for the docker service:
>>>
>>>         $ mkdir /etc/systemd/system/docker.service.d
>>>
>>>     3. create a file called 
>>>     /etc/systemd/system/docker.service.d/http-proxy.conf that adds the 
>>>     HTTP_PROXY environment variable:
>>>
>>>         [Service]
>>>         Environment="HTTP_PROXY=http://proxy.example.com:80/"
>>>
>>>     4. flush changes:
>>>
>>>         $ sudo systemctl daemon-reload
>>>
>>>     5. verify that the configuration has been loaded:
>>>
>>>         $ sudo systemctl show --property Environment docker
>>>         Environment=HTTP_PROXY=http://proxy.example.com:80/
>>>
>>>     6. restart Docker:
>>>
>>>         $ sudo systemctl restart docker
>>>
>>>     In the future we should ask the user about proxies in some 
>>>     "advanced configuration" option in YaST, pass it to the worker 
>>>     nodes through the autoyast.xml and set automatically the 
>>>     HTTP_PROXY for docker.
>>>
>>>     Cheers,
>>>
>>>     Ns @ 2017-04-27 15:20 GMT:
>>>
>>>         Hi Flavio, Yes I got information from Robert, however it
>>>         wasn?t working ?? Best Regards, Rushi. I MAY BE ONLY ONE
>>>         PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE On
>>>         4/27/17, 4:49 PM, "caasp-beta-bounces at lists.suse.com on
>>>         behalf of Flavio Castelli"
>>>         <caasp-beta-bounces at lists.suse.com on behalf of
>>>         fcastelli at suse.com> wrote: On 04/26/2017 06:09 AM, Ns, Rushi
>>>         wrote:
>>>
>>>             As you mentioned you should try to provide that
>>>             information during the installation or some sort of
>>>             post-steps as all most all enterprise customers have
>>>             proxy to go internet. 
>>>
>>>         You are right, this is definitely something we should
>>>         provide either during the installation time or when
>>>         deploying the cluster from the web UI. I think Robert
>>>         pointed you in the right direction, please let us know if
>>>         the proposed solution is not working. Thanks for your
>>>         feedback. Cheers Flavio
>>>         ------------------------------------------------------------------------
>>>         caasp-beta mailing list caasp-beta at lists.suse.com
>>>         http://lists.suse.com/mailman/listinfo/caasp-beta
>>>         ------------------------------------------------------------------------
>>>         caasp-beta mailing list caasp-beta at lists.suse.com
>>>         http://lists.suse.com/mailman/listinfo/caasp-beta 
>>>
>>>
>>>
>>>     --
>>>     Miquel Sabat? Sol?,
>>>     PGP: 4096R / 1BA5 3C7A C93D CA2A CFDF DA97 96BE 8C6F D89D 6565
>>>
>>> _______________________________________________
>>> caasp-beta mailing list
>>> caasp-beta at lists.suse.com
>>> http://lists.suse.com/mailman/listinfo/caasp-beta
>> -- 
>> Alvaro Saurin <alvaro.saurin at suse.com>
>> Senior Software Engineer
>> SUSE Linux GmbH, Maxfeldstr. 5, D-90409 N?rnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/
>> SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg)
-- 
Alvaro Saurin <alvaro.saurin at suse.com>
Senior Software Engineer
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 N?rnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/
SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20170504/651c5106/attachment.htm>

From Qiyan.Sun at Teradata.com  Thu May  4 08:09:11 2017
From: Qiyan.Sun at Teradata.com (Sun, Qiyan)
Date: Thu, 4 May 2017 14:09:11 +0000
Subject: [caasp-beta] How to use the VM images in Beta3
In-Reply-To: <bc7ab7ee-5253-9283-a272-511e1532556e@suse.com>
References: <CFE618853F2AA643B9C669DA7C205FDF14A6EEF2@SUSHDC8004.TD.TERADATA.COM>,
	<bc7ab7ee-5253-9283-a272-511e1532556e@suse.com>
Message-ID: <CFE618853F2AA643B9C669DA7C205FDF14A6F09E@SUSHDC8004.TD.TERADATA.COM>

Hi Alexander,

In beta2 activate.sh can be run to bring the services, velum container, etc. This does not work in beta3 anymore. In an early email, someone said it will be different in beta3. A one line documentation says the services will be brought up by system role. Can you give more details?

Thanks,
Qiyan
________________________________________
From: Alexander Herzig [aherzig at suse.com]
Sent: Thursday, May 04, 2017 2:21 AM
To: Sun, Qiyan; caasp-beta at lists.suse.com
Subject: Re: [caasp-beta] How to use the VM images in Beta3

Dear Qiyan,

thank you for testing our product.
May I point your attention to our documentation which you can find here:
https://www.suse.com/betaprogram/caasp-beta/doc-quickstart/

Further we have made a video about how to setup a cluster here:
https://www.youtube.com/watch?v=hJf6FqNQhJ4&t=180s

If you install via autoyast or one of the provided VMX beta images
(KVM,Xen,VMware,...) please set a password or SSH key via cloud-init to
be able to login.

If you have further questions, please don't hesitate to drop some lines
on this mailing list.

Best regards
Alexander


Am 03.05.2017 um 19:56 schrieb Sun, Qiyan:
> How to activate the administration node in Beta3 using the VM images?
> How to add a cluster node?
>
>
>
> Thanks,
>
> Qiyan
>
>
>
> _______________________________________________
> caasp-beta mailing list
> caasp-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/caasp-beta
>



From kukuk at suse.com  Thu May  4 08:39:07 2017
From: kukuk at suse.com (Thorsten Kukuk)
Date: Thu, 4 May 2017 16:39:07 +0200
Subject: [caasp-beta] How to use the VM images in Beta3
In-Reply-To: <CFE618853F2AA643B9C669DA7C205FDF14A6F09E@SUSHDC8004.TD.TERADATA.COM>
References: <CFE618853F2AA643B9C669DA7C205FDF14A6EEF2@SUSHDC8004.TD.TERADATA.COM>
	<CFE618853F2AA643B9C669DA7C205FDF14A6F09E@SUSHDC8004.TD.TERADATA.COM>
Message-ID: <20170504143907.GA26113@suse.com>

On Thu, May 04, Qiyan Sun wrote:

> Hi Alexander,
> 
> In beta2 activate.sh can be run to bring the services, velum container, etc. This does not work in beta3 anymore. In an early email, someone said it will be different in beta3. A one line documentation says the services will be brought up by system role. Can you give more details?

Using the VMX images as cluster node is easy doable with cloud-init.
You need the following lines in your user-data file:

suse_caasp:
  role: cluster
  admin_node: admin.example.com

Running a VMX images as admin node does currently not work. 

  Thorsten

-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

From rushi.ns at sap.com  Fri May  5 02:13:19 2017
From: rushi.ns at sap.com (Ns, Rushi)
Date: Fri, 5 May 2017 08:13:19 +0000
Subject: [caasp-beta] single master failure of etcd cluster is unavailable
	or misconfigured
Message-ID: <A8E3BCD3-268E-45F4-B45E-AC8E88F1E487@sap.com>


Hello

We got this error in one our beta cluster (etcd cluster is unavailable or misconfigured ) and need somone who can explain from SUSE how to add secondary master since CAASP allows only one master.? Any clue or solution how to fix this error etcd cluster is unavailable or misconfigured.


Best Regards,
 
Rushi.
I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE
 
 


From rushi.ns at sap.com  Mon May  8 03:24:02 2017
From: rushi.ns at sap.com (Ns, Rushi)
Date: Mon, 8 May 2017 09:24:02 +0000
Subject: [caasp-beta] docker service down on master ?
Message-ID: <73B82475-64A4-4BBF-A088-5941FF8E15BC@sap.com>

Hello

One of our master server rebooted due to hardware issue and after that docker service is not starting. Getting weird issues .  Did anyone experience this issue.

hostmaster systemd[1]: Dependency failed for Docker Application Container Engine.
hostmaster systemd[1]: docker.service: Job docker.service/start failed with result 'dependency'.


Best Regards,

Rushi.
I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE


From: <caasp-beta-bounces at lists.suse.com> on behalf of Liam McCafferty <Liam.McCafferty at smartodds.co.uk>
Date: Sunday, May 7, 2017 at 12:11 PM
To: "caasp-beta at lists.suse.com" <caasp-beta at lists.suse.com>
Subject: [caasp-beta] Changing the IP range docker binds on across the kube cluster


HI guys,



How would you change the bind IP for kube cluster im assuming this cant just be done in sysconfig docker. as would need to be changed somewhere on the master is there a kube/Suse  way of doing this? unfortunately 172.18 range is an actual range we use.

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

This e-mail and any files transmitted with it are confidential and may be legally privileged. If you receive it in error or are not the intended recipient you must not copy, distribute or take any action in reliance upon it. Instead, please notify us immediately by telephoning +44 (20) 74820223 and delete the material from your systems. Smartodds is a business carried on by Smartodds Limited, a company registered with the Registrar of Companies for England and Wales with number 05108548. Registered office: Unit 531 Highgate Studios, 53-79 Highgate Road, London NW5 1TL

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20170508/a775d115/attachment.htm>

From rushi.ns at sap.com  Mon May  8 03:36:06 2017
From: rushi.ns at sap.com (Ns, Rushi)
Date: Mon, 8 May 2017 09:36:06 +0000
Subject: [caasp-beta] docker service down on master ?
In-Reply-To: <73B82475-64A4-4BBF-A088-5941FF8E15BC@sap.com>
References: <73B82475-64A4-4BBF-A088-5941FF8E15BC@sap.com>
Message-ID: <9024595E-075A-4B28-BDA7-249927E7747D@sap.com>

Is this error due to Flanneld service not running .

Hostmaster:/var/lib # systemctl status flanneld
? flanneld.service - Flanneld overlay address etcd agent
   Loaded: loaded (/usr/lib/systemd/system/flanneld.service; enabled; vendor preset: disabled)
   Active: activating (start) since Mon 2017-05-08 02:28:27 PDT; 3s ago
 Main PID: 50399 (flanneld)
    Tasks: 8 (limit: 512)
   Memory: 4.4M
      CPU: 20ms
   CGroup: /system.slice/flanneld.service
           ??50399 /usr/sbin/flanneld -etcd-endpoints=http://hostmaster:2379 -etcd-prefix=

systemd[1]: Starting Flanneld overlay address etcd agent...
I0508 02:28:27.560847 50399 main.go:126] Installing signal handlers
flanneld[50399]: E0508 02:28:27.566046 50399 network.go:106] failed to retrieve network config: 100: Key not found (/config) [1140212]

Best Regards,

Rushi.
I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE


From: "Ns, Rushi" <rushi.ns at sap.com>
Date: Monday, May 8, 2017 at 11:24 AM
To: "caasp-beta at lists.suse.com" <caasp-beta at lists.suse.com>
Subject: docker service down on master ?

Hello

One of our master server rebooted due to hardware issue and after that docker service is not starting. Getting weird issues .  Did anyone experience this issue.

hostmaster systemd[1]: Dependency failed for Docker Application Container Engine.
hostmaster systemd[1]: docker.service: Job docker.service/start failed with result 'dependency'.


Best Regards,

Rushi.
I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE


From: <caasp-beta-bounces at lists.suse.com> on behalf of Liam McCafferty <Liam.McCafferty at smartodds.co.uk>
Date: Sunday, May 7, 2017 at 12:11 PM
To: "caasp-beta at lists.suse.com" <caasp-beta at lists.suse.com>
Subject: [caasp-beta] Changing the IP range docker binds on across the kube cluster


HI guys,



How would you change the bind IP for kube cluster im assuming this cant just be done in sysconfig docker. as would need to be changed somewhere on the master is there a kube/Suse  way of doing this? unfortunately 172.18 range is an actual range we use.

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

This e-mail and any files transmitted with it are confidential and may be legally privileged. If you receive it in error or are not the intended recipient you must not copy, distribute or take any action in reliance upon it. Instead, please notify us immediately by telephoning +44 (20) 74820223 and delete the material from your systems. Smartodds is a business carried on by Smartodds Limited, a company registered with the Registrar of Companies for England and Wales with number 05108548. Registered office: Unit 531 Highgate Studios, 53-79 Highgate Road, London NW5 1TL


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20170508/18256042/attachment.htm>

From rfernandezlopez at suse.com  Tue May  9 03:49:52 2017
From: rfernandezlopez at suse.com (=?UTF-8?Q?Rafael_Fern=c3=a1ndez_L=c3=b3pez?=)
Date: Tue, 9 May 2017 11:49:52 +0200
Subject: [caasp-beta] docker service down on master ?
In-Reply-To: <9024595E-075A-4B28-BDA7-249927E7747D@sap.com>
References: <73B82475-64A4-4BBF-A088-5941FF8E15BC@sap.com>
	<9024595E-075A-4B28-BDA7-249927E7747D@sap.com>
Message-ID: <6f867927-1885-2415-cf69-cac653d3b1f2@suse.com>

Hello,

It looks like etcd lost some important information.

What was the size of the cluster? Was the master server the only one
that was rebooted?

From the kubernetes master node, can you run the following command:

etcdctl ls -r /


Thank you,
Rafael Fern?ndez L?pez.

On 05/08/2017 11:36 AM, Ns, Rushi wrote:
> Is this error due to Flanneld service not running .
> 
>  
> 
> *Hostmaster:/var/lib #*systemctl status flanneld
> 
> ? flanneld.service - Flanneld overlay address etcd agent
> 
>    Loaded: loaded (/usr/lib/systemd/system/flanneld.service; enabled;
> vendor preset: disabled)
> 
>    Active: activating (start) since Mon 2017-05-08 02:28:27 PDT; 3s ago
> 
>  Main PID: 50399 (flanneld)
> 
>     Tasks: 8 (limit: 512)
> 
>    Memory: 4.4M
> 
>       CPU: 20ms
> 
>    CGroup: /system.slice/flanneld.service
> 
>            ??50399 /usr/sbin/flanneld
> -etcd-endpoints=http://hostmaster:2379 -etcd-prefix=
> 
>  
> 
> systemd[1]: Starting Flanneld overlay address etcd agent...
> 
> I0508 02:28:27.560847 50399 main.go:126] Installing signal handlers
> 
> flanneld[50399]: E0508 02:28:27.566046 50399 network.go:106] failed to
> retrieve network config: 100: Key not found (/config) [1140212]
> 
>  
> 
> Best Regards,
> 
>  
> 
> Rushi.
> 
> I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE
> 
>  
> 
>  
> 
> *From: *"Ns, Rushi" <rushi.ns at sap.com>
> *Date: *Monday, May 8, 2017 at 11:24 AM
> *To: *"caasp-beta at lists.suse.com" <caasp-beta at lists.suse.com>
> *Subject: *docker service down on master ?
> 
>  
> 
> Hello
> 
>  
> 
> One of our master server rebooted due to hardware issue and after that
> docker service is not starting. Getting weird issues .  Did anyone
> experience this issue.
> 
>  
> 
> hostmaster systemd[1]: *Dependency failed for Docker Application
> Container Engine.*
> 
> hostmaster systemd[1]: *docker.service: Job docker.service/start failed
> with result 'dependency'.*
> 
>  
> 
>  
> 
> Best Regards,
> 
>  
> 
> Rushi.
> 
> I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE
> 
>  
> 
>  
> 
> *From: *<caasp-beta-bounces at lists.suse.com> on behalf of Liam McCafferty
> <Liam.McCafferty at smartodds.co.uk>
> *Date: *Sunday, May 7, 2017 at 12:11 PM
> *To: *"caasp-beta at lists.suse.com" <caasp-beta at lists.suse.com>
> *Subject: *[caasp-beta] Changing the IP range docker binds on across the
> kube cluster
> 
>  
> 
> HI guys,
> 
>  
> 
> How would you change the bind IP for kube cluster im assuming this cant
> just be done in sysconfig docker. as would need to be changed somewhere
> on the master is there a kube/Suse  way of doing this? unfortunately
> 172.18 range is an actual range we use.  
> 
> 
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
> 
> This e-mail and any files transmitted with it are confidential and may
> be legally privileged. If you receive it in error or are not the
> intended recipient you must not copy, distribute or take any action in
> reliance upon it. Instead, please notify us immediately by telephoning
> +44 (20) 74820223 and delete the material from your systems. Smartodds
> is a business carried on by Smartodds Limited, a company registered with
> the Registrar of Companies for England and Wales with number 05108548.
> Registered office: Unit 531 Highgate Studios, 53-79 Highgate Road,
> London NW5 1TL
> 
> 
> 
> 
> _______________________________________________
> caasp-beta mailing list
> caasp-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/caasp-beta
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20170509/58110e15/attachment.sig>

From rfernandezlopez at suse.com  Tue May  9 03:53:18 2017
From: rfernandezlopez at suse.com (=?UTF-8?Q?Rafael_Fern=c3=a1ndez_L=c3=b3pez?=)
Date: Tue, 9 May 2017 11:53:18 +0200
Subject: [caasp-beta] single master failure of etcd cluster is
 unavailable or misconfigured
In-Reply-To: <A8E3BCD3-268E-45F4-B45E-AC8E88F1E487@sap.com>
References: <A8E3BCD3-268E-45F4-B45E-AC8E88F1E487@sap.com>
Message-ID: <9414b5a6-8f2e-a635-ac96-d00892d78a88@suse.com>

Hello,

On the released version there is only one master, and there is no way to
recreate it whatsoever or add more master nodes. This will be improved
in upcoming versions.

On a deployed cluster you shouldn't get this error, unless something bad
or unexpected has happened.


Thank you,
Rafael Fern?ndez L?pez.

On 05/05/2017 10:13 AM, Ns, Rushi wrote:
> 
> Hello
> 
> We got this error in one our beta cluster (etcd cluster is unavailable or misconfigured ) and need somone who can explain from SUSE how to add secondary master since CAASP allows only one master.? Any clue or solution how to fix this error etcd cluster is unavailable or misconfigured.
> 
> 
> Best Regards,
>  
> Rushi.
> I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE
>  
>  
> 
> _______________________________________________
> caasp-beta mailing list
> caasp-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/caasp-beta
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20170509/280004aa/attachment.sig>

From rushi.ns at sap.com  Tue May  9 12:30:26 2017
From: rushi.ns at sap.com (Ns, Rushi)
Date: Tue, 9 May 2017 18:30:26 +0000
Subject: [caasp-beta] [caasp-beta3] NTP setup
Message-ID: <52358BF6-E1FE-4658-B0EC-957ED82D94EE@sap.com>

Hi Vincent, THorsten

This is regards to NTP option is being added to BETA3.

What I notice is that its only promoted to enter NTP server details when you select System Role ?Administrtion dashboard? but not when you select Cluster Node role.




Best Regards,
 
Rushi.
I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE
 

On 4/10/17, 5:28 PM, "caasp-beta-bounces at lists.suse.com on behalf of Vincent Moutoussamy" <caasp-beta-bounces at lists.suse.com on behalf of vmoutoussamy at suse.com> wrote:

     
    Hi,
    
    FYI, Thorsten is referencing this message:  
    
    > as you should have noticed, the administration dashboard of CaaSP generates  
    > a certificate during the first login for communication with the cluster.  
    > Such a certificate only works, if the date/time on all machines in the  
    > cluster is correct.  
    >  
    > Our cloud-init documentation contains an example, how to configure ntpd  
    > with cloud-init during the first boot.  
    > If you don't want to use cloud-init, please configure ntpd yourself.  
    > If you don't want to use ntpd, you could also use systemd-timesyncd.  
    > For this, adjust /etc/systemd/timesyncd.conf and enable it with:  
    > # timedatectl set-ntp true  
    >  
    > For Beta3 we will think about a mechanism to automatically setup  
    > time synchronisation in the cluster.  
    
    I will add this message to the known issue section 
    (https://www.suse.com/betaprogram/caasp-beta/#releasenotes).
    
    For inclusion of the NTP message in the ?Installation Guide?, let?s wait for the
    potential mechanism in Beta 3.
    
    Regards,  
    --  
    Vincent Moutoussamy
    SUSE Beta Program and SDK Project Manager
    
    
    _______________________________________________
    caasp-beta mailing list
    caasp-beta at lists.suse.com
    http://lists.suse.com/mailman/listinfo/caasp-beta
    




From kukuk at suse.com  Tue May  9 12:39:43 2017
From: kukuk at suse.com (Thorsten Kukuk)
Date: Tue, 9 May 2017 20:39:43 +0200
Subject: [caasp-beta] [caasp-beta3] NTP setup
In-Reply-To: <52358BF6-E1FE-4658-B0EC-957ED82D94EE@sap.com>
References: <52358BF6-E1FE-4658-B0EC-957ED82D94EE@sap.com>
Message-ID: <20170509183943.GA8279@suse.com>


Hi

On Tue, May 09, Rushi Ns wrote:

> Hi Vincent, THorsten
> 
> This is regards to NTP option is being added to BETA3.
> 
> What I notice is that its only promoted to enter NTP server details when you select System Role ?Administrtion dashboard? but not when you select Cluster Node role.

This is correct, on the cluster node we configure the timesyncd service
automatically to sync the time with the admin node.
You can download the autoyast profile from the admin dashboard and
look at or change it.

Regards,
  Thorsten


> 
> 
> 
> 
> Best Regards,
>  
> Rushi.
> I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE
>  
> 
> On 4/10/17, 5:28 PM, "caasp-beta-bounces at lists.suse.com on behalf of Vincent Moutoussamy" <caasp-beta-bounces at lists.suse.com on behalf of vmoutoussamy at suse.com> wrote:
> 
>      
>     Hi,
>     
>     FYI, Thorsten is referencing this message:  
>     
>     > as you should have noticed, the administration dashboard of CaaSP generates  
>     > a certificate during the first login for communication with the cluster.  
>     > Such a certificate only works, if the date/time on all machines in the  
>     > cluster is correct.  
>     >  
>     > Our cloud-init documentation contains an example, how to configure ntpd  
>     > with cloud-init during the first boot.  
>     > If you don't want to use cloud-init, please configure ntpd yourself.  
>     > If you don't want to use ntpd, you could also use systemd-timesyncd.  
>     > For this, adjust /etc/systemd/timesyncd.conf and enable it with:  
>     > # timedatectl set-ntp true  
>     >  
>     > For Beta3 we will think about a mechanism to automatically setup  
>     > time synchronisation in the cluster.  
>     
>     I will add this message to the known issue section 
>     (https://www.suse.com/betaprogram/caasp-beta/#releasenotes).
>     
>     For inclusion of the NTP message in the ?Installation Guide?, let?s wait for the
>     potential mechanism in Beta 3.
>     
>     Regards,  
>     --  
>     Vincent Moutoussamy
>     SUSE Beta Program and SDK Project Manager
>     
>     
>     _______________________________________________
>     caasp-beta mailing list
>     caasp-beta at lists.suse.com
>     http://lists.suse.com/mailman/listinfo/caasp-beta
>     
> 
> 
> 

-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

From Liam.McCafferty at smartodds.co.uk  Wed May 10 07:12:12 2017
From: Liam.McCafferty at smartodds.co.uk (Liam McCafferty)
Date: Wed, 10 May 2017 13:12:12 +0000
Subject: [caasp-beta] Changing the IP range docker binds on across the
 kube cluster
In-Reply-To: <1bfc6d20-fbd1-9166-050e-37919d91fbb2@suse.com>
References: <1494151873006.46581@smartodds.co.uk>,
	<1bfc6d20-fbd1-9166-050e-37919d91fbb2@suse.com>
Message-ID: <1494421931949.23402@smartodds.co.uk>

Hi Rafael ,

current ip addr on my master node is :


1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:50:56:90:11:94 brd ff:ff:ff:ff:ff:ff
    inet 172.17.1.73/24 brd 172.17.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::250:56ff:fe90:1194/64 scope link 
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:5d:f5:33:db brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 scope global docker0
       valid_lft forever preferred_lft forever
4: flannel0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1472 qdisc pfifo_fast state UNKNOWN group default qlen 500
    link/none 
    inet 172.20.84.0/16 scope global flannel0
       valid_lft forever preferred_lft foreve

issue is 172.18 and 172.20 are both routeable on our network, 

We have had many issues with docker before which were caused by the default network bindings.


________________________________________
From: Rafael Fern?ndez L?pez <rfernandezlopez at suse.com>
Sent: 08 May 2017 11:12
To: Liam McCafferty; caasp-beta at lists.suse.com
Subject: Re: [caasp-beta] Changing the IP range docker binds on across the kube cluster

Hello Liam,

The cluster CIDR uses 172.20.0.0/16 by default.

Docker defaults to 172.17.0.0/16 by default.

None of them are in the 127.18.0.0/16 range.

Can you please confirm what is the range that is conflicting with your
organization internal network range so we can take proper action and
register a bug to make this configurable if applies?


Thank you,
Rafael Fern?ndez L?pez.

On 05/07/2017 12:11 PM, Liam McCafferty wrote:
> HI guys,
>
>
> How would you change the bind IP for kube cluster im assuming this cant
> just be done in sysconfig docker. as would need to be changed somewhere
> on the master is there a kube/Suse  way of doing this? unfortunately
> 172.18 range is an actual range we use.
>
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
>
> This e-mail and any files transmitted with it are confidential and may
> be legally privileged. If you receive it in error or are not the
> intended recipient you must not copy, distribute or take any action in
> reliance upon it. Instead, please notify us immediately by telephoning
> +44 (20) 74820223 and delete the material from your systems. Smartodds
> is a business carried on by Smartodds Limited, a company registered with
> the Registrar of Companies for England and Wales with number 05108548.
> Registered office: Unit 531 Highgate Studios, 53-79 Highgate Road,
> London NW5 1TL
>
>
> _______________________________________________
> caasp-beta mailing list
> caasp-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/caasp-beta
>


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

This e-mail and any files transmitted with it are confidential and may be legally privileged. If you receive it in error or are not the intended recipient you must not copy, distribute or take any action in reliance upon it. Instead, please notify us immediately by telephoning +44 (20) 74820223 and delete the material from your systems. Smartodds is a business carried on by Smartodds Limited, a company registered with the Registrar of Companies for England and Wales with number 05108548. Registered office: Unit 531 Highgate Studios, 53-79 Highgate Road, London NW5 1TL

From deniskulagin at foxwilder.com  Fri May 12 16:25:05 2017
From: deniskulagin at foxwilder.com (Denis Kulagin)
Date: Fri, 12 May 2017 18:25:05 -0400
Subject: [caasp-beta] beta3 try1 - cluster bootstrap stuck
Message-ID: <CANJtUt=AFnBLpe752A_gHYbhfZtuRD3NXcS8a6XNMpLf0JQRNw@mail.gmail.com>

Hi All,

Just found out about this list. And wanted to share my experience here and
ask a few questions.

Trying beta3 now. First downloaded VMware image, booted it and... nothing
happens :) Only port 22 is open, couldn't find root password. Pinged my
friend David, who recommended installing from ISOs. Though I'm lazy - I
actually did. Installation went smoothly on blank VMware image. However,
you have to say I will install OS later, do not use easy/auto install
VMware offers, it messes up the installer.

I was able to log into controller node. Created account.

Created a brand new VMware image with the same ISO for the first worker
node. Installed with "autoyast=http://<my_ip>/autoyast netsetup=dhcp". It
did show up in the console with the hostname linux. At this point I decided
to create one more to have dedicated master. Did the same exact install for
the second worker, it finished successfully, but never showed up in the
console.

So now I have only one node with id 1 and hostname 'linux' and I try to
bootstrap. Its been hanging out for an hour now and I believe its stuck.

One more thing to mention - I did not provide NTP server.

Any ideas? I'm thinking I will try this scenario one more time tomorrow
with the ntp server. And then with just one worker node (somehow I'm
suspicion about both working may have the same 'linux' hostname...).


Denis Kulagin
deniskulagin at foxwilder.com
+1 (212) 706-0172
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20170512/f27cc25e/attachment.htm>

From abonilla at suse.com  Fri May 12 20:01:34 2017
From: abonilla at suse.com (Alejandro Bonilla)
Date: Sat, 13 May 2017 02:01:34 +0000
Subject: [caasp-beta] beta3 try1 - cluster bootstrap stuck
In-Reply-To: <CANJtUt=AFnBLpe752A_gHYbhfZtuRD3NXcS8a6XNMpLf0JQRNw@mail.gmail.com>
References: <CANJtUt=AFnBLpe752A_gHYbhfZtuRD3NXcS8a6XNMpLf0JQRNw@mail.gmail.com>
Message-ID: <C81A626B-7B30-4999-B61E-4D93A65A69EF@suse.com>

Hi Denis,

> On May 12, 2017, at 6:25 PM, Denis Kulagin <deniskulagin at foxwilder.com> wrote:
> 
> Hi All,
> 
> Just found out about this list. And wanted to share my experience here and ask a few questions.
> 
> Trying beta3 now. First downloaded VMware image, booted it and... nothing happens :) Only port 22 is open, couldn't find root password. Pinged my friend David, who recommended installing from ISOs. Though I'm lazy - I actually did. Installation went smoothly on blank VMware image. However, you have to say I will install OS later, do not use easy/auto install VMware offers, it messes up the installer.

The variant images are provided for an automated installation which requires the use of cloud-init which would inject the information at boot. There is some documentation available in one of the links at the Beta site, but this is still WIP.

> 
> I was able to log into controller node. Created account. 
> 
> Created a brand new VMware image with the same ISO for the first worker node. Installed with "autoyast=http://<my_ip>/autoyast netsetup=dhcp". It did show up in the console with the hostname linux. At this point I decided to create one more to have dedicated master. Did the same exact install for the second worker, it finished successfully, but never showed up in the console.

I can see two reasons but I?ll have to assume things:
- You created a template, which carries the system id and then would be seen as a duplicate.
- A hostname was not provided for the VM which makes the minion to use the ?linux? hostname by default. A hostname was not provided by DNS either.

I?d recommend to boot specifying the hostname at install/boot time or configuring it the yast2 network section while at the installer.

> 
> So now I have only one node with id 1 and hostname 'linux' and I try to bootstrap. Its been hanging out for an hour now and I believe its stuck.

A master and a worker is mandatory. It will stay there? I?d suggest to reinstall the admin and then create 2 new VMs which are booted/installed via the ISO pointing to the controller IP or using the autoyast path as you did before.

> 
> One more thing to mention - I did not provide NTP server.

In a ?lab? this may not be necessary if both VMs or on the same host. They should be given the same time as the hw clock. If this is on an ESX cluster, then you certainly need to specify one when configuring the initial admin node.

> 
> Any ideas? I'm thinking I will try this scenario one more time tomorrow with the ntp server. And then with just one worker node (somehow I'm suspicion about both working may have the same 'linux' hostname?).

I think you are onto something ;-)

> 
> 
> Denis Kulagin
> deniskulagin at foxwilder.com
> +1 (212) 706-0172
> 
> 
> _______________________________________________
> caasp-beta mailing list
> caasp-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/caasp-beta


From uschairer at suse.com  Thu May 18 06:28:51 2017
From: uschairer at suse.com (Ulrich Schairer)
Date: Thu, 18 May 2017 14:28:51 +0200
Subject: [caasp-beta] CaaSP 1.0 beta 3 and external private docker registry
	with Portus
Message-ID: <29eaee55-d86c-2168-d975-75cadb1c2728@suse.com>

Hi list,

I want to connect my CaaSP 1.0 beta 3 installation ( adminnode, 
masternode and two worker nodes) with a private docker registry with 
portus in place.
So far I could set up a private docker registry with portus on a SLE 12 
SP2 installation using portus and docker-distribution-registry from the 
container module. Now I am struggeling to set up a SSL secured 
connection between the docker on CaaSP and the private registry.
I tried to copy over certificates from portus to docker on CaaSP but no 
success.
I then tried to create certificates on the admin node, signed with the 
ca located on the admin node, but this didn't work either, simple tests 
with curl failed, even giving 
--cacert=/etc/pki/trust/anchors/SUSE_CaaSP_CA.crt on cmd-line.

Any hints how to make this setup working?

Thank you.

Kind regards
Uli

-- 
Dr. Ulrich Schairer - Technical Architect SAP
SUSE LINUX GmbH, Maxfeldstrasse 5, 90409 N?rnberg,Germany
Mobil: +49-173-5876 824
Email: ulrich.schairer at suse.com
-----------------------------------------------------------------
SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard,
Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG N?rnberg)
-----------------------------------------------------------------
http://www.suse.com

From Martin.Weiss at suse.com  Thu May 18 23:34:20 2017
From: Martin.Weiss at suse.com (Martin Weiss)
Date: Thu, 18 May 2017 23:34:20 -0600
Subject: [caasp-beta] Antw: CaaSP 1.0 beta 3 and external private docker
 registry with Portus
In-Reply-To: <29eaee55-d86c-2168-d975-75cadb1c2728@suse.com>
References: <29eaee55-d86c-2168-d975-75cadb1c2728@suse.com>
Message-ID: <591E83DC0200001C002E21A4@prv-mh.provo.novell.com>

Hi Uli,

I am not sure if that is the problem and I can not test this at the moment... but depending on how the SSL certificates were created / used on the Registry - you need to export the public key of the CA that signed that certificate and then add this as trusted to the worker nodes. 
(copy to /etc/pki/trust/anchors and then execute /usr/sbin/update-ca-certificates)

Oh - and when installing Portus it is creating its own certificate with its own CA - not the SLES CA AFAIK...
So this is my workaround "before" Portus is installed and configured:
cp -av /etc/ssl/servercerts/servercert.pem /etc/ssl/servercerts/$(hostname -f)-ca.crt
cp -av /etc/ssl/servercerts/serverkey.pem /etc/ssl/servercerts/$(hostname -f)-ca.key
--> to make sure Portus uses the certificate that I already have for the server..

HTH
Martin



Hi list,

I want to connect my CaaSP 1.0 beta 3 installation ( adminnode, 
masternode and two worker nodes) with a private docker registry with 
portus in place.
So far I could set up a private docker registry with portus on a SLE 12 
SP2 installation using portus and docker-distribution-registry from the 
container module. Now I am struggeling to set up a SSL secured 
connection between the docker on CaaSP and the private registry.
I tried to copy over certificates from portus to docker on CaaSP but no 
success.
I then tried to create certificates on the admin node, signed with the 
ca located on the admin node, but this didn't work either, simple tests 
with curl failed, even giving 
--cacert=/etc/pki/trust/anchors/SUSE_CaaSP_CA.crt on cmd-line.

Any hints how to make this setup working?

Thank you.

Kind regards
Uli

-- 
Dr. Ulrich Schairer - Technical Architect SAP
SUSE LINUX GmbH, Maxfeldstrasse 5, 90409 N?rnberg,Germany
Mobil: +49-173-5876 824
Email: ulrich.schairer at suse.com
-----------------------------------------------------------------
SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard,
Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG N?rnberg)
-----------------------------------------------------------------
http://www.suse.com

_______________________________________________
caasp-beta mailing list
caasp-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/caasp-beta

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20170518/e0b1e690/attachment.htm>

From kukuk at suse.com  Tue May 23 01:32:53 2017
From: kukuk at suse.com (Thorsten Kukuk)
Date: Tue, 23 May 2017 09:32:53 +0200
Subject: [caasp-beta] kubernetes dashboard image pull error
In-Reply-To: <DM3PR12MB082788761EDA82C66479F808DDE40@DM3PR12MB0827.namprd12.prod.outlook.com>
References: <DM3PR12MB082788761EDA82C66479F808DDE40@DM3PR12MB0827.namprd12.prod.outlook.com>
Message-ID: <20170523073253.GB30137@suse.com>


Hi,

On Thu, May 18, Hwang Jerry wrote:

> For SLES, I can import the SSL proxy cert, however not possible on MicroOS for
> readonly file system.

That's a problem currently with CaaSP, correct.
The read-only root filesystem isn't that problem, you can still copy
the files into the /etc/... directory hierachy. The problem is a limitation
of openssl ...

We are working on this, but this is not an easily to solve problem.

But, what you can do is: put your certificates in a RPM, call
update-ca-certificates in the post install section, and add the
repository as additional installation source (zypper ar, cloud-init
add_repo, ...).
This has also the advantage, that you don't need to manually update the
certificate on all machines, but if you release a new RPM, all machines
will automatically install it.

  Thorsten

-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

From beta-programs at lists.suse.com  Tue May 23 09:36:44 2017
From: beta-programs at lists.suse.com (SUSE Beta Program)
Date: Tue, 23 May 2017 17:36:44 +0200
Subject: [caasp-beta] Next SUSE CaaS Platform release will be Beta 4
Message-ID: <5924570c48def_4e48114f3109999@boucane.mail>

Hi,

After internal discussions, we have decided to release the next version of 
SUSE CaaS Platform as Beta 4 and not as a "Release Candidate" like we have 
initially planned.

We should release Beta 4 on Monday 29th May.[1]

This decision is not affecting the "First Customer Shipment" schedule. 

==Question?
Please refer to our dedicated SUSE CaaSP Beta webpage[2] for any general
information. Do not hesitate to ask any technical questions to our public
mailing list caasp-beta at lists.suse.com[3]

However if you have any question regarding SUSE Beta Program itself,
or if you have a special or private inquiry please reach us at
beta-programs at lists.suse.com
You received this email because you're signed up to get updates from us.
Sent an email to beta-programs at lists.suse.com if you would like to unsubscribe.

	Your SUSE CaaSP Team
[1] https://www.suse.com/betaprogram/caasp-beta/#releases
[2] https://www.suse.com/betaprogram/caasp-beta/
[3] http://lists.suse.com/mailman/listinfo/caasp-beta
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20170523/6cbd18e2/attachment.htm>