From special011 at gmail.com Tue Dec 5 15:55:49 2017 From: special011 at gmail.com (Jerry Hwang) Date: Tue, 5 Dec 2017 14:55:49 -0800 Subject: [caasp-beta] kubernetes dashboard in v2.0 GA Message-ID: Hi, Not sure if this mailing list is still usable for caas v2 GA though. I have a question about kubernetes dashboard. It worked with v1, however the same way now doesn't work. According to documentation, I did 1. kubectl create -f (on kubernetes master node) https://raw.githubusercontent.com/kubernetes/dashboard/v1.6.3/src/deploy/kubernetes-dashboard.yaml I see 1 'kubernetes-dashboard' in pod/service/deployment list 2. kubectl proxy --address=10.2.240.232 --accept-hosts='^*$'& (10.2.240.232 is kubernetes master) 3. now if I try http://10.2.240.232:8001/ui it is loading then redirected to http://10.2.240.232:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy and show a blank page Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: From cseader at suse.com Tue Dec 5 17:02:02 2017 From: cseader at suse.com (Cameron Seader) Date: Tue, 5 Dec 2017 17:02:02 -0700 Subject: [caasp-beta] kubernetes dashboard in v2.0 GA In-Reply-To: References: Message-ID: Watch and try my video for secure k8s cluster. if you want details I am happy to share. The video should have everything you need. Its an unlisted video right now, but as soon as I video I will make it public. https://youtu.be/ftgjuu323c0 Thanks, Cameron On 12/05/2017 03:55 PM, Jerry Hwang wrote: > Hi, > > Not sure if this mailing list is still usable for caas v2 GA though. > > I have a question about kubernetes dashboard. > It worked with v1, however the same way now doesn't work. > > According to documentation, I did > > 1.?kubectl create -f (on kubernetes master node) > https://raw.githubusercontent.com/kubernetes/dashboard/v1.6.3/src/deploy/kubernetes-dashboard.yaml > > I see 1 'kubernetes-dashboard' in pod/service/deployment list > > 2.?kubectl proxy --address=10.2.240.232 --accept-hosts='^*$'& > (10.2.240.232 is kubernetes master) > > 3. now if I try http://10.2.240.232:8001/ui > it is loading then redirected to > http://10.2.240.232:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy > and show a blank page > > Jerry > > > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/caasp-beta > -- Cameron Seader Technology Strategist SUSE cs at suse.com (P)+1 208.572.0095 (M)+1 208.420.2167 From cseader at suse.com Tue Dec 5 17:03:08 2017 From: cseader at suse.com (Cameron Seader) Date: Tue, 5 Dec 2017 17:03:08 -0700 Subject: [caasp-beta] kubernetes dashboard in v2.0 GA In-Reply-To: References: Message-ID: That came out wrong. As soon as I add some audio to it I will make it public. -Cameron On 12/05/2017 05:02 PM, Cameron Seader wrote: > Watch and try my video for secure k8s cluster. if you want details I am > happy to share. The video should have everything you need. Its an > unlisted video right now, but as soon as I video I will make it public. > > https://youtu.be/ftgjuu323c0 > > Thanks, > Cameron > > On 12/05/2017 03:55 PM, Jerry Hwang wrote: >> Hi, >> >> Not sure if this mailing list is still usable for caas v2 GA though. >> >> I have a question about kubernetes dashboard. >> It worked with v1, however the same way now doesn't work. >> >> According to documentation, I did >> >> 1.?kubectl create -f (on kubernetes master node) >> https://raw.githubusercontent.com/kubernetes/dashboard/v1.6.3/src/deploy/kubernetes-dashboard.yaml >> >> >> I see 1 'kubernetes-dashboard' in pod/service/deployment list >> >> 2.?kubectl proxy --address=10.2.240.232 --accept-hosts='^*$'& >> (10.2.240.232 is kubernetes master) >> >> 3. now if I try http://10.2.240.232:8001/ui >> it is loading then redirected to >> http://10.2.240.232:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy >> and show a blank page >> >> Jerry >> >> >> _______________________________________________ >> caasp-beta mailing list >> caasp-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/caasp-beta >> > -- Cameron Seader Technology Strategist SUSE cs at suse.com (P)+1 208.572.0095 (M)+1 208.420.2167 From special011 at gmail.com Tue Dec 5 17:07:39 2017 From: special011 at gmail.com (Jerry Hwang) Date: Tue, 5 Dec 2017 16:07:39 -0800 Subject: [caasp-beta] kubernetes dashboard in v2.0 GA In-Reply-To: References: Message-ID: I was able to resolve it by using the NodePort type then access the dashboard and I see that's also how you did :) I didn't have to with v1 though. I will try the securing part, thanks. Jerry On Tue, Dec 5, 2017 at 4:03 PM, Cameron Seader wrote: > That came out wrong. As soon as I add some audio to it I will make it > public. > -Cameron > > On 12/05/2017 05:02 PM, Cameron Seader wrote: > >> Watch and try my video for secure k8s cluster. if you want details I am >> happy to share. The video should have everything you need. Its an unlisted >> video right now, but as soon as I video I will make it public. >> >> https://youtu.be/ftgjuu323c0 >> >> Thanks, >> Cameron >> >> On 12/05/2017 03:55 PM, Jerry Hwang wrote: >> >>> Hi, >>> >>> Not sure if this mailing list is still usable for caas v2 GA though. >>> >>> I have a question about kubernetes dashboard. >>> It worked with v1, however the same way now doesn't work. >>> >>> According to documentation, I did >>> >>> 1. kubectl create -f (on kubernetes master node) >>> https://raw.githubusercontent.com/kubernetes/dashboard/v1.6. >>> 3/src/deploy/kubernetes-dashboard.yaml >>> >>> I see 1 'kubernetes-dashboard' in pod/service/deployment list >>> >>> 2. kubectl proxy --address=10.2.240.232 --accept-hosts='^*$'& >>> (10.2.240.232 is kubernetes master) >>> >>> 3. now if I try http://10.2.240.232:8001/ui >>> it is loading then redirected to http://10.2.240.232:8001/api/v >>> 1/namespaces/kube-system/services/kubernetes-dashboard/proxy and show a >>> blank page >>> >>> Jerry >>> >>> >>> _______________________________________________ >>> caasp-beta mailing list >>> caasp-beta at lists.suse.com >>> http://lists.suse.com/mailman/listinfo/caasp-beta >>> >>> >> > -- > Cameron Seader > Technology Strategist > SUSE > cs at suse.com > (P)+1 208.572.0095 > (M)+1 208.420.2167 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From special011 at gmail.com Tue Dec 5 17:15:41 2017 From: special011 at gmail.com (Jerry Hwang) Date: Tue, 5 Dec 2017 16:15:41 -0800 Subject: [caasp-beta] kubernetes dashboard in v2.0 GA In-Reply-To: References: Message-ID: To clarify, this one was used for v1.. https://raw.githubusercontent.com/SUSE/caasp-services/master/contrib/addons/kubedns/dns.yaml But I noticed it's not available any more and it's not mentioned in the v2 doc either. Maybe it might have NodePort as type.. On Tue, Dec 5, 2017 at 4:07 PM, Jerry Hwang wrote: > I was able to resolve it by using the NodePort type then access the > dashboard and I see that's also how you did :) > I didn't have to with v1 though. > I will try the securing part, thanks. > > Jerry > > On Tue, Dec 5, 2017 at 4:03 PM, Cameron Seader wrote: > >> That came out wrong. As soon as I add some audio to it I will make it >> public. >> -Cameron >> >> On 12/05/2017 05:02 PM, Cameron Seader wrote: >> >>> Watch and try my video for secure k8s cluster. if you want details I am >>> happy to share. The video should have everything you need. Its an unlisted >>> video right now, but as soon as I video I will make it public. >>> >>> https://youtu.be/ftgjuu323c0 >>> >>> Thanks, >>> Cameron >>> >>> On 12/05/2017 03:55 PM, Jerry Hwang wrote: >>> >>>> Hi, >>>> >>>> Not sure if this mailing list is still usable for caas v2 GA though. >>>> >>>> I have a question about kubernetes dashboard. >>>> It worked with v1, however the same way now doesn't work. >>>> >>>> According to documentation, I did >>>> >>>> 1. kubectl create -f (on kubernetes master node) >>>> https://raw.githubusercontent.com/kubernetes/dashboard/v1.6. >>>> 3/src/deploy/kubernetes-dashboard.yaml >>>> >>>> I see 1 'kubernetes-dashboard' in pod/service/deployment list >>>> >>>> 2. kubectl proxy --address=10.2.240.232 --accept-hosts='^*$'& >>>> (10.2.240.232 is kubernetes master) >>>> >>>> 3. now if I try http://10.2.240.232:8001/ui >>>> it is loading then redirected to http://10.2.240.232:8001/api/v >>>> 1/namespaces/kube-system/services/kubernetes-dashboard/proxy and show >>>> a blank page >>>> >>>> Jerry >>>> >>>> >>>> _______________________________________________ >>>> caasp-beta mailing list >>>> caasp-beta at lists.suse.com >>>> http://lists.suse.com/mailman/listinfo/caasp-beta >>>> >>>> >>> >> -- >> Cameron Seader >> Technology Strategist >> SUSE >> cs at suse.com >> (P)+1 208.572.0095 >> (M)+1 208.420.2167 >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From special011 at gmail.com Tue Dec 5 17:31:50 2017 From: special011 at gmail.com (Jerry Hwang) Date: Tue, 5 Dec 2017 16:31:50 -0800 Subject: [caasp-beta] tcpdump Message-ID: I see no tcpdump available in micro-os v2. tried to install manually however it failed for read-only file system (no surprise). any suggestion to have tcpdump? thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From special011 at gmail.com Tue Dec 5 18:27:44 2017 From: special011 at gmail.com (Jerry Hwang) Date: Wed, 06 Dec 2017 01:27:44 +0000 Subject: [caasp-beta] kubernetes dashboard in v2.0 GA In-Reply-To: <8E985CB4-DED4-447F-8861-7362E33AF6E3@sap.com> References: <8E985CB4-DED4-447F-8861-7362E33AF6E3@sap.com> Message-ID: That was a new challenge too with v2. I noticed the url redirects to fqdn so I had to add the mapping to hosts file on my mgmt computer and it also requires login that is same for velum login. I was able to download to my mac as before after that. Documentation has not much enhanced in v2. Regards, Jerry On Tue, Dec 5, 2017 at 5:22 PM Ns, Rushi wrote: > Hi jerry, > > How did you download the kubeconfig from velum web , I get errrors . Did > you get any errors while download > > Best Regards, > > > > Rushi. > > Success is not a matter of being the best & winning the race. Success is a > matter of handling the worst & finishing the race > > Sent from my iPhone > please excuse typos and brevity > > On Dec 5, 2017, at 15:16, Jerry Hwang wrote: > > Hi, > > Not sure if this mailing list is still usable for caas v2 GA though. > > I have a question about kubernetes dashboard. > It worked with v1, however the same way now doesn't work. > > According to documentation, I did > > 1. kubectl create -f (on kubernetes master node) > https://raw.githubusercontent.com/kubernetes/dashboard/v1.6.3/src/deploy/kubernetes-dashboard.yaml > > I see 1 'kubernetes-dashboard' in pod/service/deployment list > > 2. kubectl proxy --address=10.2.240.232 --accept-hosts='^*$'& > (10.2.240.232 is kubernetes master) > > 3. now if I try http://10.2.240.232:8001/ui > it is loading then redirected to > http://10.2.240.232:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy > and show a blank page > > Jerry > > _______________________________________________ > > > caasp-beta mailing list > caasp-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/caasp-beta > > -- Sent from iPhone -------------- next part -------------- An HTML attachment was scrubbed... URL: From cseader at suse.com Tue Dec 5 22:30:46 2017 From: cseader at suse.com (Cameron Seader) Date: Tue, 5 Dec 2017 22:30:46 -0700 Subject: [caasp-beta] kubernetes dashboard in v2.0 GA In-Reply-To: References: <8E985CB4-DED4-447F-8861-7362E33AF6E3@sap.com> Message-ID: <07aa1dd8-8f2a-d6d9-570e-d3a6941a002d@suse.com> Yes, since in v2 you are now having more than one master node you must setup some round robin DNS so that the Kubernetes API FQDN points to the IP addresses of the master nodes. -Cameron On 12/05/2017 06:27 PM, Jerry Hwang wrote: > That was a new challenge too with v2. > I noticed the url redirects to fqdn so I had to add the mapping to hosts > file on my mgmt computer and it also requires login that is same for > velum login. > I was able to download to my mac as before after that. > > Documentation has not much enhanced in v2. > > Regards, > Jerry > > On Tue, Dec 5, 2017 at 5:22 PM Ns, Rushi > wrote: > > Hi jerry, > > How did you download the kubeconfig from velum web , I get errrors . > Did you get any errors while download > >> Best Regards,____ >> >> Rushi.____ >> > Success is not a matter of being the best & winning the race. > Success is a matter of handling the worst & finishing the race > > Sent from my iPhone > please excuse typos and brevity > > On Dec 5, 2017, at 15:16, Jerry Hwang > wrote: > >> Hi, >> >> Not sure if this mailing list is still usable for caas v2 GA though. >> >> I have a question about kubernetes dashboard. >> It worked with v1, however the same way now doesn't work. >> >> According to documentation, I did >> >> 1.?kubectl create -f (on kubernetes master node) >> https://raw.githubusercontent.com/kubernetes/dashboard/v1.6.3/src/deploy/kubernetes-dashboard.yaml >> >> I see 1 'kubernetes-dashboard' in pod/service/deployment list >> >> 2.?kubectl proxy --address=10.2.240.232 --accept-hosts='^*$'& >> (10.2.240.232 is kubernetes master) >> >> 3. now if I try http://10.2.240.232:8001/ui >> it is loading then redirected to >> http://10.2.240.232:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy >> and show a blank page >> >> Jerry >> _______________________________________________ >> >> caasp-beta mailing list >> caasp-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/caasp-beta > > -- > Sent from iPhone > > > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/caasp-beta > -- Cameron Seader Technology Strategist SUSE cs at suse.com (P)+1 208.572.0095 (M)+1 208.420.2167 From rushi.ns at sap.com Tue Dec 5 22:34:56 2017 From: rushi.ns at sap.com (Ns, Rushi) Date: Wed, 6 Dec 2017 05:34:56 +0000 Subject: [caasp-beta] kubernetes dashboard in v2.0 GA In-Reply-To: <07aa1dd8-8f2a-d6d9-570e-d3a6941a002d@suse.com> References: <8E985CB4-DED4-447F-8861-7362E33AF6E3@sap.com> <07aa1dd8-8f2a-d6d9-570e-d3a6941a002d@suse.com> Message-ID: <6DE99CCD-9287-4BF6-89E8-7972CD45738C@sap.com> My setup had only 1 master and 3 minons and I have used my admin node (Velum) as the load balaner host , I get error while downloading the kubeconfig but the same login works with velum web and I can see my nodes and master information. ? As per Jerry I have added my hostnames and Ip address on /etc/hosts file ? I have filed this bug with SUSE when I came across this but I don?t see any response or fix for my bug. Do you know how to fix this . ----------------- Internal Server Error Login error. ----------- Best Regards, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE On 12/5/17, 9:31 PM, "Cameron Seader" wrote: Yes, since in v2 you are now having more than one master node you must setup some round robin DNS so that the Kubernetes API FQDN points to the IP addresses of the master nodes. -Cameron On 12/05/2017 06:27 PM, Jerry Hwang wrote: > That was a new challenge too with v2. > I noticed the url redirects to fqdn so I had to add the mapping to hosts > file on my mgmt computer and it also requires login that is same for > velum login. > I was able to download to my mac as before after that. > > Documentation has not much enhanced in v2. > > Regards, > Jerry > > On Tue, Dec 5, 2017 at 5:22 PM Ns, Rushi > wrote: > > Hi jerry, > > How did you download the kubeconfig from velum web , I get errrors . > Did you get any errors while download > >> Best Regards,____ >> >> Rushi.____ >> > Success is not a matter of being the best & winning the race. > Success is a matter of handling the worst & finishing the race > > Sent from my iPhone > please excuse typos and brevity > > On Dec 5, 2017, at 15:16, Jerry Hwang > wrote: > >> Hi, >> >> Not sure if this mailing list is still usable for caas v2 GA though. >> >> I have a question about kubernetes dashboard. >> It worked with v1, however the same way now doesn't work. >> >> According to documentation, I did >> >> 1. kubectl create -f (on kubernetes master node) >> https://raw.githubusercontent.com/kubernetes/dashboard/v1.6.3/src/deploy/kubernetes-dashboard.yaml >> >> I see 1 'kubernetes-dashboard' in pod/service/deployment list >> >> 2. kubectl proxy --address=10.2.240.232 --accept-hosts='^*$'& >> (10.2.240.232 is kubernetes master) >> >> 3. now if I try http://10.2.240.232:8001/ui >> it is loading then redirected to >> http://10.2.240.232:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy >> and show a blank page >> >> Jerry >> _______________________________________________ >> >> caasp-beta mailing list >> caasp-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/caasp-beta > > -- > Sent from iPhone > > > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/caasp-beta > -- Cameron Seader Technology Strategist SUSE cs at suse.com (P)+1 208.572.0095 (M)+1 208.420.2167 From ananda at fieldday.io Tue Dec 5 22:43:36 2017 From: ananda at fieldday.io (Ananda Kammampati) Date: Tue, 5 Dec 2017 21:43:36 -0800 Subject: [caasp-beta] kubernetes dashboard in v2.0 GA In-Reply-To: <07aa1dd8-8f2a-d6d9-570e-d3a6941a002d@suse.com> References: <8E985CB4-DED4-447F-8861-7362E33AF6E3@sap.com> <07aa1dd8-8f2a-d6d9-570e-d3a6941a002d@suse.com> Message-ID: <798880c2-c3d3-d2ae-5980-eee48a92193e@fieldday.io> Has anyone tried to have HAProxy as Load Balancer in front of multi-masters and have that LB as Kubernetes API FQDN ? I tried it but couldn't get it working successfully. May be I am missing something. thanks, Ananda On 12/5/17 9:30 PM, Cameron Seader wrote: > Yes, since in v2 you are now having more than one master node you must > setup some round robin DNS so that the Kubernetes API FQDN points to > the IP addresses of the master nodes. > -Cameron > > On 12/05/2017 06:27 PM, Jerry Hwang wrote: >> That was a new challenge too with v2. >> I noticed the url redirects to fqdn so I had to add the mapping to >> hosts file on my mgmt computer and it also requires login that is >> same for velum login. >> I was able to download to my mac as before after that. >> >> Documentation has not much enhanced in v2. >> >> Regards, >> Jerry >> >> On Tue, Dec 5, 2017 at 5:22 PM Ns, Rushi > > wrote: >> >> ??? Hi jerry, >> >> ??? How did you download the kubeconfig from velum web , I get errrors . >> ??? Did you get any errors while download >> >>> ??? Best Regards,____ >>> >>> ??? Rushi.____ >>> >> ??? Success is not a matter of being the best & winning the race. >> ??? Success is a matter of handling the worst & finishing the race >> >> ??? Sent from my iPhone >> ??? please excuse typos and brevity >> >> ??? On Dec 5, 2017, at 15:16, Jerry Hwang > ??? > wrote: >> >>> ??? Hi, >>> >>> ??? Not sure if this mailing list is still usable for caas v2 GA >>> though. >>> >>> ??? I have a question about kubernetes dashboard. >>> ??? It worked with v1, however the same way now doesn't work. >>> >>> ??? According to documentation, I did >>> >>> ??? 1.?kubectl create -f (on kubernetes master node) >>> https://raw.githubusercontent.com/kubernetes/dashboard/v1.6.3/src/deploy/kubernetes-dashboard.yaml >>> >>> ??? I see 1 'kubernetes-dashboard' in pod/service/deployment list >>> >>> ??? 2.?kubectl proxy --address=10.2.240.232 --accept-hosts='^*$'& >>> ??? (10.2.240.232 is kubernetes master) >>> >>> ??? 3. now if I try http://10.2.240.232:8001/ui >>> ??? it is loading then redirected to >>> http://10.2.240.232:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy >>> ??? and show a blank page >>> >>> ??? Jerry >>> ??? _______________________________________________ >>> >>> ??? caasp-beta mailing list >>> ??? caasp-beta at lists.suse.com >>> ??? http://lists.suse.com/mailman/listinfo/caasp-beta >> >> -- >> Sent from iPhone >> >> >> _______________________________________________ >> caasp-beta mailing list >> caasp-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/caasp-beta >> > From rushi.ns at sap.com Tue Dec 5 22:50:39 2017 From: rushi.ns at sap.com (Ns, Rushi) Date: Wed, 6 Dec 2017 05:50:39 +0000 Subject: [caasp-beta] kubernetes dashboard in v2.0 GA In-Reply-To: <798880c2-c3d3-d2ae-5980-eee48a92193e@fieldday.io> References: <8E985CB4-DED4-447F-8861-7362E33AF6E3@sap.com> <07aa1dd8-8f2a-d6d9-570e-d3a6941a002d@suse.com> <798880c2-c3d3-d2ae-5980-eee48a92193e@fieldday.io> Message-ID: <59F99E3D-04B0-47AD-ABEF-0B64E3A92759@sap.com> Yes, I tried Load Balancer as API FQDN but it wasn?t working that way ? also you cannot download kubeconfig file from velum , it seems several bugs ont his release which we have to wait until SUSE guys respond on this type of use cases. Best Regards, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE On 12/5/17, 9:48 PM, "Ananda Kammampati" wrote: Has anyone tried to have HAProxy as Load Balancer in front of multi-masters and have that LB as Kubernetes API FQDN ? I tried it but couldn't get it working successfully. May be I am missing something. thanks, Ananda On 12/5/17 9:30 PM, Cameron Seader wrote: > Yes, since in v2 you are now having more than one master node you must > setup some round robin DNS so that the Kubernetes API FQDN points to > the IP addresses of the master nodes. > -Cameron > > On 12/05/2017 06:27 PM, Jerry Hwang wrote: >> That was a new challenge too with v2. >> I noticed the url redirects to fqdn so I had to add the mapping to >> hosts file on my mgmt computer and it also requires login that is >> same for velum login. >> I was able to download to my mac as before after that. >> >> Documentation has not much enhanced in v2. >> >> Regards, >> Jerry >> >> On Tue, Dec 5, 2017 at 5:22 PM Ns, Rushi > > wrote: >> >> Hi jerry, >> >> How did you download the kubeconfig from velum web , I get errrors . >> Did you get any errors while download >> >>> Best Regards,____ >>> >>> Rushi.____ >>> >> Success is not a matter of being the best & winning the race. >> Success is a matter of handling the worst & finishing the race >> >> Sent from my iPhone >> please excuse typos and brevity >> >> On Dec 5, 2017, at 15:16, Jerry Hwang > > wrote: >> >>> Hi, >>> >>> Not sure if this mailing list is still usable for caas v2 GA >>> though. >>> >>> I have a question about kubernetes dashboard. >>> It worked with v1, however the same way now doesn't work. >>> >>> According to documentation, I did >>> >>> 1. kubectl create -f (on kubernetes master node) >>> https://raw.githubusercontent.com/kubernetes/dashboard/v1.6.3/src/deploy/kubernetes-dashboard.yaml >>> >>> I see 1 'kubernetes-dashboard' in pod/service/deployment list >>> >>> 2. kubectl proxy --address=10.2.240.232 --accept-hosts='^*$'& >>> (10.2.240.232 is kubernetes master) >>> >>> 3. now if I try http://10.2.240.232:8001/ui >>> it is loading then redirected to >>> http://10.2.240.232:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy >>> and show a blank page >>> >>> Jerry >>> _______________________________________________ >>> >>> caasp-beta mailing list >>> caasp-beta at lists.suse.com >>> http://lists.suse.com/mailman/listinfo/caasp-beta >> >> -- >> Sent from iPhone >> >> >> _______________________________________________ >> 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 kukuk at suse.com Wed Dec 6 00:28:33 2017 From: kukuk at suse.com (Thorsten Kukuk) Date: Wed, 6 Dec 2017 08:28:33 +0100 Subject: [caasp-beta] tcpdump In-Reply-To: References: Message-ID: <20171206072833.GB21150@suse.com> On Tue, Dec 05, Jerry Hwang wrote: > I see no tcpdump available in micro-os v2. > tried to install manually however it failed for read-only file system (no > surprise). > any suggestion to have tcpdump? The transactional-update help says: transactional-update pkg install 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 kukuk at suse.com Wed Dec 6 02:22:52 2017 From: kukuk at suse.com (Thorsten Kukuk) Date: Wed, 6 Dec 2017 10:22:52 +0100 Subject: [caasp-beta] Antw: Re: tcpdump In-Reply-To: <5A27AA5E0200001C003094EA@gwmail.emea.novell.com> References: <20171206072833.GB21150@suse.com> <5A27AA5E0200001C003094EA@gwmail.emea.novell.com> Message-ID: <20171206092252.GA4482@suse.com> On Wed, Dec 06, Martin Weiss wrote: > An other approach for all that debugging purposes could be to use a special > docker image / docker container that delivers all the trouble shooting tools > required and run that with proper elevated rights.. > Maybe we can deliver such an image for troubleshooting in general in the > future? A special container was planned, don't know what happend with that. There is an open request from me to deliver a "Tool-Module" like we have for SLE12, which could contain all this additional tools for trouble shooting. Thorsten > Martin > > > > On Tue, Dec 05, Jerry Hwang wrote: > > > I see no tcpdump available in micro-os v2. > > tried to install manually however it failed for read-only file system (no > > surprise). > > any suggestion to have tcpdump? > > The transactional-update help says: > > transactional-update pkg install > > 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) > _______________________________________________ > 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 Martin.Weiss at suse.com Wed Dec 6 02:37:12 2017 From: Martin.Weiss at suse.com (Martin Weiss) Date: Wed, 06 Dec 2017 02:37:12 -0700 Subject: [caasp-beta] Antw: Re: Antw: Re: tcpdump In-Reply-To: <20171206092252.GA4482@suse.com> References: <20171206072833.GB21150@suse.com> <5A27AA5E0200001C003094EA@gwmail.emea.novell.com> <20171206092252.GA4482@suse.com> Message-ID: <5A27BA480200001C003095A8@prv-mh.provo.novell.com> > On Wed, Dec 06, Martin Weiss wrote: > >> An other approach for all that debugging purposes could be to use a special >> docker image / docker container that delivers all the trouble shooting tools >> required and run that with proper elevated rights.. >> Maybe we can deliver such an image for troubleshooting in general in the >> future? > > A special container was planned, don't know what happend with that. > There is an open request from me to deliver a "Tool?Module" like we > have for SLE12, which could contain all this additional tools > for trouble shooting. Yes - but installing them and then updating and patching them will again increase the size and time required for patching / updating etc. I sill would vote for a way to "temporarily" and "on demand" add the debugging tools required and remove them quickly after we do not need them anymore automatically.. (there are so many debugging tools that might be required in different situations that might use more disk space than the basic OS ;-)) Martin > > Thorsten > >> Martin >> >> >> >> On Tue, Dec 05, Jerry Hwang wrote: >> >> > I see no tcpdump available in micro?os v2. >> > tried to install manually however it failed for read?only file system (no >> > surprise). >> > any suggestion to have tcpdump? >> >> The transactional?update help says: >> >> transactional?update pkg install >> >> 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) >> _______________________________________________ >> 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) > _______________________________________________ > caasp?beta mailing list > caasp?beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/caasp?beta From special011 at gmail.com Wed Dec 6 04:46:02 2017 From: special011 at gmail.com (Jerry Hwang) Date: Wed, 6 Dec 2017 03:46:02 -0800 Subject: [caasp-beta] tcpdump In-Reply-To: <20171206072833.GB21150@suse.com> References: <20171206072833.GB21150@suse.com> Message-ID: cool thanks. btw, looks need a reboot to use after transactional-update? On Tue, Dec 5, 2017 at 11:28 PM, Thorsten Kukuk wrote: > On Tue, Dec 05, Jerry Hwang wrote: > > > I see no tcpdump available in micro-os v2. > > tried to install manually however it failed for read-only file system (no > > surprise). > > any suggestion to have tcpdump? > > The transactional-update help says: > > transactional-update pkg install > > 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) > _______________________________________________ > 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: From kukuk at suse.com Wed Dec 6 04:49:43 2017 From: kukuk at suse.com (Thorsten Kukuk) Date: Wed, 6 Dec 2017 12:49:43 +0100 Subject: [caasp-beta] tcpdump In-Reply-To: References: <20171206072833.GB21150@suse.com> Message-ID: <20171206114943.GA4389@suse.com> On Wed, Dec 06, Jerry Hwang wrote: > cool thanks. > btw, looks need a reboot to use after transactional-update? Yes. Thorsten > On Tue, Dec 5, 2017 at 11:28 PM, Thorsten Kukuk wrote: > > On Tue, Dec 05, Jerry Hwang wrote: > > > I see no tcpdump available in micro-os v2. > > tried to install manually however it failed for read-only file system (no > > surprise). > > any suggestion to have tcpdump? > > The transactional-update help says: > > transactional-update pkg install > > ? 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) > _______________________________________________ > 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 special011 at gmail.com Wed Dec 6 04:51:45 2017 From: special011 at gmail.com (Jerry Hwang) Date: Wed, 6 Dec 2017 03:51:45 -0800 Subject: [caasp-beta] tcpdump In-Reply-To: <20171206114943.GA4389@suse.com> References: <20171206072833.GB21150@suse.com> <20171206114943.GA4389@suse.com> Message-ID: I understand why but hmm inconvenient... On Wed, Dec 6, 2017 at 3:49 AM, Thorsten Kukuk wrote: > On Wed, Dec 06, Jerry Hwang wrote: > > > cool thanks. > > btw, looks need a reboot to use after transactional-update? > > Yes. > > Thorsten > > > On Tue, Dec 5, 2017 at 11:28 PM, Thorsten Kukuk wrote: > > > > On Tue, Dec 05, Jerry Hwang wrote: > > > > > I see no tcpdump available in micro-os v2. > > > tried to install manually however it failed for read-only file > system (no > > > surprise). > > > any suggestion to have tcpdump? > > > > The transactional-update help says: > > > > transactional-update pkg install > > > > 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) > > _______________________________________________ > > 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) > _______________________________________________ > 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: From special011 at gmail.com Wed Dec 6 04:52:32 2017 From: special011 at gmail.com (Jerry Hwang) Date: Wed, 6 Dec 2017 03:52:32 -0800 Subject: [caasp-beta] Antw: Re: tcpdump In-Reply-To: <20171206092252.GA4482@suse.com> References: <20171206072833.GB21150@suse.com> <5A27AA5E0200001C003094EA@gwmail.emea.novell.com> <20171206092252.GA4482@suse.com> Message-ID: yes, i had to use a special container (named toolbox) to run smarttool & adv sys tools in another os, it's cool micro-os allows to install rpm directly. On Wed, Dec 6, 2017 at 1:22 AM, Thorsten Kukuk wrote: > On Wed, Dec 06, Martin Weiss wrote: > > > An other approach for all that debugging purposes could be to use a > special > > docker image / docker container that delivers all the trouble shooting > tools > > required and run that with proper elevated rights.. > > Maybe we can deliver such an image for troubleshooting in general in the > > future? > > A special container was planned, don't know what happend with that. > There is an open request from me to deliver a "Tool-Module" like we > have for SLE12, which could contain all this additional tools > for trouble shooting. > > Thorsten > > > Martin > > > > > > > > On Tue, Dec 05, Jerry Hwang wrote: > > > > > I see no tcpdump available in micro-os v2. > > > tried to install manually however it failed for read-only file system > (no > > > surprise). > > > any suggestion to have tcpdump? > > > > The transactional-update help says: > > > > transactional-update pkg install > > > > 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) > > _______________________________________________ > > 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) > _______________________________________________ > 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: From abonilla at suse.com Wed Dec 6 09:01:28 2017 From: abonilla at suse.com (Alejandro Bonilla) Date: Wed, 6 Dec 2017 16:01:28 +0000 Subject: [caasp-beta] kubernetes dashboard in v2.0 GA In-Reply-To: <59F99E3D-04B0-47AD-ABEF-0B64E3A92759@sap.com> References: <8E985CB4-DED4-447F-8861-7362E33AF6E3@sap.com> <07aa1dd8-8f2a-d6d9-570e-d3a6941a002d@suse.com> <798880c2-c3d3-d2ae-5980-eee48a92193e@fieldday.io> <59F99E3D-04B0-47AD-ABEF-0B64E3A92759@sap.com> Message-ID: The way I have the LB working on my side is: named-DNS: caasp-master IN A IP.ADDRESS.OF.LB (floating IP) The above FQDN is for the Kubernetes API which needs to be provided in Velum so the certificate allows connections to that address. The LB/Master DNS entry needs to exist before deploying. OpenStack LoadBalancer 1 LoadBalancer, with 2 Listeners Name Description Protocol Port Actions rr-api - TCP 6443 Edit rr-dex - TCP 32000 Edit Each listener has the 3 master nodes as members going to the corresponding port. Hope that helps. > On Dec 5, 2017, at 11:50 PM, Ns, Rushi wrote: > > Yes, I tried Load Balancer as API FQDN but it wasn?t working that way ? also you cannot download kubeconfig file from velum , it seems several bugs ont his release which we have to wait until SUSE guys respond on this type of use cases. > > > > > Best Regards, > > Rushi. > I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE > > > On 12/5/17, 9:48 PM, "Ananda Kammampati" wrote: > > Has anyone tried to have HAProxy as Load Balancer in front of > multi-masters and have that LB as Kubernetes API FQDN ? I tried it but > couldn't get it working successfully. May be I am missing something. > > thanks, > > Ananda > > > On 12/5/17 9:30 PM, Cameron Seader wrote: >> Yes, since in v2 you are now having more than one master node you must >> setup some round robin DNS so that the Kubernetes API FQDN points to >> the IP addresses of the master nodes. >> -Cameron >> >> On 12/05/2017 06:27 PM, Jerry Hwang wrote: >>> That was a new challenge too with v2. >>> I noticed the url redirects to fqdn so I had to add the mapping to >>> hosts file on my mgmt computer and it also requires login that is >>> same for velum login. >>> I was able to download to my mac as before after that. >>> >>> Documentation has not much enhanced in v2. >>> >>> Regards, >>> Jerry >>> >>> On Tue, Dec 5, 2017 at 5:22 PM Ns, Rushi >> > wrote: >>> >>> Hi jerry, >>> >>> How did you download the kubeconfig from velum web , I get errrors . >>> Did you get any errors while download >>> >>>> Best Regards,____ >>>> >>>> Rushi.____ >>>> >>> Success is not a matter of being the best & winning the race. >>> Success is a matter of handling the worst & finishing the race >>> >>> Sent from my iPhone >>> please excuse typos and brevity >>> >>> On Dec 5, 2017, at 15:16, Jerry Hwang >> > wrote: >>> >>>> Hi, >>>> >>>> Not sure if this mailing list is still usable for caas v2 GA >>>> though. >>>> >>>> I have a question about kubernetes dashboard. >>>> It worked with v1, however the same way now doesn't work. >>>> >>>> According to documentation, I did >>>> >>>> 1. kubectl create -f (on kubernetes master node) >>>> https://raw.githubusercontent.com/kubernetes/dashboard/v1.6.3/src/deploy/kubernetes-dashboard.yaml >>>> >>>> I see 1 'kubernetes-dashboard' in pod/service/deployment list >>>> >>>> 2. kubectl proxy --address=10.2.240.232 --accept-hosts='^*$'& >>>> (10.2.240.232 is kubernetes master) >>>> >>>> 3. now if I try http://10.2.240.232:8001/ui >>>> it is loading then redirected to >>>> http://10.2.240.232:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy >>>> and show a blank page >>>> >>>> Jerry >>>> _______________________________________________ >>>> >>>> caasp-beta mailing list >>>> caasp-beta at lists.suse.com >>>> http://lists.suse.com/mailman/listinfo/caasp-beta >>> >>> -- >>> Sent from iPhone >>> >>> >>> _______________________________________________ >>> 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 From normand at linux.vnet.ibm.com Thu Dec 7 04:08:37 2017 From: normand at linux.vnet.ibm.com (Normand) Date: Thu, 7 Dec 2017 12:08:37 +0100 Subject: [caasp-beta] Is there a plan to have Kubic on other architectures ? Message-ID: <4a59b51b-cdf2-3c04-d9e8-1e703b2fc018@linux.vnet.ibm.com> Hi Thorsten, Is there a detailed plan to have Kubic on other architectures ? There was a general statement in video (1) (around 36mn) but no details, Could you elaborate on what is required and how community could help ? I am specifically interested by porting to ppc64le. (1) https://github.com/kubic-project/community -- Michel Normand From magnus at linuxtag.org Wed Dec 6 07:54:49 2017 From: magnus at linuxtag.org (Nils Magnus) Date: Wed, 6 Dec 2017 15:54:49 +0100 Subject: [caasp-beta] Antw: Re: Antw: Re: tcpdump In-Reply-To: <5A27BA480200001C003095A8@prv-mh.provo.novell.com> References: <20171206072833.GB21150@suse.com> <5A27AA5E0200001C003094EA@gwmail.emea.novell.com> <20171206092252.GA4482@suse.com> <5A27BA480200001C003095A8@prv-mh.provo.novell.com> Message-ID: Hi, On 06.12.2017 10:37, Martin Weiss wrote: >> On Wed, Dec 06, Martin Weiss wrote: >>> An other approach for all that debugging purposes could be to use a special >>> docker image / docker container that delivers all the trouble shooting tools >>> required and run that with proper elevated rights.. That is either complex, as the container has not all capabilities needed for proper debugging purposes, or a security nightmare, or most probably both. Regards, Nils From beta-programs at lists.suse.com Thu Dec 7 07:14:01 2017 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Thu, 07 Dec 2017 15:14:01 +0100 Subject: [caasp-beta] SUSE Container as a Service Platform 2 End of Beta Program Message-ID: <5a294ca98a20f_1dfa55530c8997c@boucane.mail> Thank you all! We hope that you have enjoyed beta testing SUSE Container as a Service Platform 2 Beta and that we have provided the necessary help in your ongoing project. To be sure that everything went well and to improve the next Beta Program, we would like to kindly ask you to take 5 minutes to fill the following survey[1] SUSE Container as a Service Platform 2 was announced mid-November 2017. Check out the announcement![2] Rest assured that we will communicate more information, in the future, on the next SUSE Container as a Service Platform Beta Program. ==Closing the Beta Program - Web pages: https://www.suse.com/betaprogram/caasp-beta/ was "cleaned-up" iand will be updated when we have more information to share for the next Beta Program. - Download links: Beta isos links are disabled and removed. - Mailing List: The caasp-beta at lists.suse.com is left untouched. However please use our support process to report SUSE CaaS Platform 2 issues, other than that feel free to post in the mailing list. - Bugzilla: You won't be able to create any new bug for "Beta SUSE CaaS Platform 2." ==Question? And if you have any question regarding the Beta Program itself, please reach us via beta-programs at lists.suse.com. Your SUSE CaaS Platform Team [1] https://www.surveymonkey.com/r/caasp-beta [2] https://www.suse.com/communities/blog/suse-caas-platform-2-now-generally-available/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From Martin.Weiss at suse.com Thu Dec 7 07:56:17 2017 From: Martin.Weiss at suse.com (Martin Weiss) Date: Thu, 07 Dec 2017 07:56:17 -0700 Subject: [caasp-beta] Antw: Re: Antw: Re: Antw: Re: tcpdump In-Reply-To: References: <20171206072833.GB21150@suse.com> <5A27AA5E0200001C003094EA@gwmail.emea.novell.com> <20171206092252.GA4482@suse.com> <5A27BA480200001C003095A8@prv-mh.provo.novell.com> Message-ID: <5A2956910200001C00309E88@prv-mh.provo.novell.com> >>>> An other approach for all that debugging purposes could be to use a special >>>> docker image / docker container that delivers all the trouble shooting tools >>>> required and run that with proper elevated rights.. > > That is either complex, as the container has not all capabilities needed > for proper debugging purposes, or a security nightmare, or most probably > both. > Yes - there is security and complexity assigned - but installing all the required debug packages on all the servers might be even worse from a security point of view and they might not be even part of the CaaSP delivery channels. Advantage of a debug container is that it can be added on demand and cleanup is fully automated.. when installing all the debug packages these are a security problem while they are installed and the also need to be upgraded / patched etc. So both ways have their pros and cons ;-) Martin From rob.decanha-knight at suse.com Thu Dec 7 08:25:37 2017 From: rob.decanha-knight at suse.com (Rob de Canha-Knight) Date: Thu, 7 Dec 2017 15:25:37 +0000 Subject: [caasp-beta] Antw: Re: Antw: Re: Antw: Re: tcpdump In-Reply-To: <5A2956910200001C00309E88@prv-mh.provo.novell.com> References: <20171206072833.GB21150@suse.com> <5A27AA5E0200001C003094EA@gwmail.emea.novell.com> <20171206092252.GA4482@suse.com> <5A27BA480200001C003095A8@prv-mh.provo.novell.com> , <5A2956910200001C00309E88@prv-mh.provo.novell.com> Message-ID: <80B2378E-5998-4405-B514-DCB810C4A1F1@suse.com> It?s also worth mentioning that we have privileged containers enabled within CaaSP so the vast majority of debugging containers should work without issue when you pass ?privileged into the docker run command. As Martin points out we try to keep the security surface as small as possible by only installing the bare minimum needed to run containers. MicroOS is designed to only run containers and isn?t recommended for running any kind of binary or package so a debug container is the best approach IMHO. If you have a specific issue with a specific tool inside of a privileged debug container please let us know as we can definitely look into this and try and fix any compatibility issues that may arise. Rob Sent from my iPhone - please excuse any shortness > On 7 Dec 2017, at 15:57, Martin Weiss wrote: > > > >>>>> An other approach for all that debugging purposes could be to use a special >>>>> docker image / docker container that delivers all the trouble shooting tools >>>>> required and run that with proper elevated rights.. >> >> That is either complex, as the container has not all capabilities needed >> for proper debugging purposes, or a security nightmare, or most probably >> both. >> > > Yes - there is security and complexity assigned - but installing all the required debug packages on all the servers might be even worse from a security point of view and they might not be even part of the CaaSP delivery channels. > Advantage of a debug container is that it can be added on demand and cleanup is fully automated.. when installing all the debug packages these are a security problem while they are installed and the also need to be upgraded / patched etc. > > So both ways have their pros and cons ;-) > > Martin > > > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/caasp-beta From rob.decanha-knight at suse.com Thu Dec 7 08:38:13 2017 From: rob.decanha-knight at suse.com (Rob de Canha-Knight) Date: Thu, 7 Dec 2017 15:38:13 +0000 Subject: [caasp-beta] kubeconfig download error In-Reply-To: <6D181E7A-9FC6-4ACF-AD08-BE05CB375F88@sap.com> References: <6D181E7A-9FC6-4ACF-AD08-BE05CB375F88@sap.com> Message-ID: <943AE357-E27A-4D98-863A-DA71DA625511@suse.com> Hi Rushi, As before you have to use the beta list for communication. I saw a couple of people like Martin send you a couple of suggestions I don?t know if these were followed (I didn?t see any further emails) but please give these a try. I know there are a few other colleagues in SAP have set this up successfully (for Vora) so you might wish to check in with them for assistance. I can only log support tickets for paying customers however as I mentioned before you are free to log a bugzilla as you did before. If that bug hasn?t yet had any progress on it you are welcome to add a comment to it asking for an update. As before really emailing myself and other colleagues is going to make it harder for us to help and I?m not in a position to help anyway so please use the beta list and bugzilla as per the known process. Sent from my iPhone - please excuse any shortness > On 7 Dec 2017, at 16:29, Ns, Rushi wrote: > > Hi Rob,. > > Do you have time , I still have the issue downloading the kubeconfig and I filed the bug. , however no solution yet from SUSE. > > > > Best Regards, > > Rushi. > I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE > > > On 12/7/17, 7:25 AM, "caasp-beta-bounces at lists.suse.com on behalf of Rob de Canha-Knight" wrote: > > It?s also worth mentioning that we have privileged containers enabled within CaaSP so the vast majority of debugging containers should work without issue when you pass ?privileged into the docker run command. > > As Martin points out we try to keep the security surface as small as possible by only installing the bare minimum needed to run containers. MicroOS is designed to only run containers and isn?t recommended for running any kind of binary or package so a debug container is the best approach IMHO. > > If you have a specific issue with a specific tool inside of a privileged debug container please let us know as we can definitely look into this and try and fix any compatibility issues that may arise. > > Rob > > Sent from my iPhone - please excuse any shortness > >> On 7 Dec 2017, at 15:57, Martin Weiss wrote: >> >> >> >>>>>> An other approach for all that debugging purposes could be to use a special >>>>>> docker image / docker container that delivers all the trouble shooting tools >>>>>> required and run that with proper elevated rights.. >>> >>> That is either complex, as the container has not all capabilities needed >>> for proper debugging purposes, or a security nightmare, or most probably >>> both. >>> >> >> Yes - there is security and complexity assigned - but installing all the required debug packages on all the servers might be even worse from a security point of view and they might not be even part of the CaaSP delivery channels. >> Advantage of a debug container is that it can be added on demand and cleanup is fully automated.. when installing all the debug packages these are a security problem while they are installed and the also need to be upgraded / patched etc. >> >> So both ways have their pros and cons ;-) >> >> Martin >> >> >> _______________________________________________ >> 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 rob.decanha-knight at suse.com Thu Dec 7 08:44:50 2017 From: rob.decanha-knight at suse.com (Rob de Canha-Knight) Date: Thu, 7 Dec 2017 15:44:50 +0000 Subject: [caasp-beta] kubeconfig download error In-Reply-To: <7CD890FF-4755-479B-B290-8D4533BB7777@sap.com> References: <6D181E7A-9FC6-4ACF-AD08-BE05CB375F88@sap.com> <943AE357-E27A-4D98-863A-DA71DA625511@suse.com>, <7CD890FF-4755-479B-B290-8D4533BB7777@sap.com> Message-ID: Please escalate internally then as I am unfortunately not in a position to help you. Happy holidays, Rob Sent from my iPhone - please excuse any shortness > On 7 Dec 2017, at 16:43, Ns, Rushi wrote: > > Hi Rob, > > Yes I know and all ways totally waster, no one really have clue including SUSE guys (I am part of VORA supporting clusters for different distributions, (we have tectonic, coreos, redhat, kubeadm based clusters, including SUSE CAAS) but SUSE CAAS is the pain with authorization file download(VORA Dev experienced as well) other than all the players. > > I think its waste my time contacting everyone. > > You guys certified SUSE for VORA but when it comes to help from SAP guys , no one from SUSE really care about it. I will escalate further on this and see what the outcome. > > > > Best Regards, > > Rushi. > I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE > > > On 12/7/17, 7:38 AM, "Rob de Canha-Knight" wrote: > > Hi Rushi, > > As before you have to use the beta list for communication. > > I saw a couple of people like Martin send you a couple of suggestions I don?t know if these were followed (I didn?t see any further emails) but please give these a try. > > I know there are a few other colleagues in SAP have set this up successfully (for Vora) so you might wish to check in with them for assistance. > > I can only log support tickets for paying customers however as I mentioned before you are free to log a bugzilla as you did before. If that bug hasn?t yet had any progress on it you are welcome to add a comment to it asking for an update. > > As before really emailing myself and other colleagues is going to make it harder for us to help and I?m not in a position to help anyway so please use the beta list and bugzilla as per the known process. > > Sent from my iPhone - please excuse any shortness > >> On 7 Dec 2017, at 16:29, Ns, Rushi wrote: >> >> Hi Rob,. >> >> Do you have time , I still have the issue downloading the kubeconfig and I filed the bug. , however no solution yet from SUSE. >> >> >> >> Best Regards, >> >> Rushi. >> I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE >> >> >> On 12/7/17, 7:25 AM, "caasp-beta-bounces at lists.suse.com on behalf of Rob de Canha-Knight" wrote: >> >> It?s also worth mentioning that we have privileged containers enabled within CaaSP so the vast majority of debugging containers should work without issue when you pass ?privileged into the docker run command. >> >> As Martin points out we try to keep the security surface as small as possible by only installing the bare minimum needed to run containers. MicroOS is designed to only run containers and isn?t recommended for running any kind of binary or package so a debug container is the best approach IMHO. >> >> If you have a specific issue with a specific tool inside of a privileged debug container please let us know as we can definitely look into this and try and fix any compatibility issues that may arise. >> >> Rob >> >> Sent from my iPhone - please excuse any shortness >> >>> On 7 Dec 2017, at 15:57, Martin Weiss wrote: >>> >>> >>> >>>>>>> An other approach for all that debugging purposes could be to use a special >>>>>>> docker image / docker container that delivers all the trouble shooting tools >>>>>>> required and run that with proper elevated rights.. >>>> >>>> That is either complex, as the container has not all capabilities needed >>>> for proper debugging purposes, or a security nightmare, or most probably >>>> both. >>>> >>> >>> Yes - there is security and complexity assigned - but installing all the required debug packages on all the servers might be even worse from a security point of view and they might not be even part of the CaaSP delivery channels. >>> Advantage of a debug container is that it can be added on demand and cleanup is fully automated.. when installing all the debug packages these are a security problem while they are installed and the also need to be upgraded / patched etc. >>> >>> So both ways have their pros and cons ;-) >>> >>> Martin >>> >>> >>> _______________________________________________ >>> 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 rushi.ns at sap.com Thu Dec 7 09:03:45 2017 From: rushi.ns at sap.com (Ns, Rushi) Date: Thu, 7 Dec 2017 16:03:45 +0000 Subject: [caasp-beta] kubeconfig download error In-Reply-To: References: <6D181E7A-9FC6-4ACF-AD08-BE05CB375F88@sap.com> <943AE357-E27A-4D98-863A-DA71DA625511@suse.com> <7CD890FF-4755-479B-B290-8D4533BB7777@sap.com> Message-ID: <605096D2-61D6-4EFB-B1CB-30AB76668748@sap.com> No worries, you carry on. Will not bother you any more. Best Regards, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE On 12/7/17, 7:45 AM, "Rob de Canha-Knight" wrote: Please escalate internally then as I am unfortunately not in a position to help you. Happy holidays, Rob Sent from my iPhone - please excuse any shortness > On 7 Dec 2017, at 16:43, Ns, Rushi wrote: > > Hi Rob, > > Yes I know and all ways totally waster, no one really have clue including SUSE guys (I am part of VORA supporting clusters for different distributions, (we have tectonic, coreos, redhat, kubeadm based clusters, including SUSE CAAS) but SUSE CAAS is the pain with authorization file download(VORA Dev experienced as well) other than all the players. > > I think its waste my time contacting everyone. > > You guys certified SUSE for VORA but when it comes to help from SAP guys , no one from SUSE really care about it. I will escalate further on this and see what the outcome. > > > > Best Regards, > > Rushi. > I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE > > > On 12/7/17, 7:38 AM, "Rob de Canha-Knight" wrote: > > Hi Rushi, > > As before you have to use the beta list for communication. > > I saw a couple of people like Martin send you a couple of suggestions I don?t know if these were followed (I didn?t see any further emails) but please give these a try. > > I know there are a few other colleagues in SAP have set this up successfully (for Vora) so you might wish to check in with them for assistance. > > I can only log support tickets for paying customers however as I mentioned before you are free to log a bugzilla as you did before. If that bug hasn?t yet had any progress on it you are welcome to add a comment to it asking for an update. > > As before really emailing myself and other colleagues is going to make it harder for us to help and I?m not in a position to help anyway so please use the beta list and bugzilla as per the known process. > > Sent from my iPhone - please excuse any shortness > >> On 7 Dec 2017, at 16:29, Ns, Rushi wrote: >> >> Hi Rob,. >> >> Do you have time , I still have the issue downloading the kubeconfig and I filed the bug. , however no solution yet from SUSE. >> >> >> >> Best Regards, >> >> Rushi. >> I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE >> >> >> On 12/7/17, 7:25 AM, "caasp-beta-bounces at lists.suse.com on behalf of Rob de Canha-Knight" wrote: >> >> It?s also worth mentioning that we have privileged containers enabled within CaaSP so the vast majority of debugging containers should work without issue when you pass ?privileged into the docker run command. >> >> As Martin points out we try to keep the security surface as small as possible by only installing the bare minimum needed to run containers. MicroOS is designed to only run containers and isn?t recommended for running any kind of binary or package so a debug container is the best approach IMHO. >> >> If you have a specific issue with a specific tool inside of a privileged debug container please let us know as we can definitely look into this and try and fix any compatibility issues that may arise. >> >> Rob >> >> Sent from my iPhone - please excuse any shortness >> >>> On 7 Dec 2017, at 15:57, Martin Weiss wrote: >>> >>> >>> >>>>>>> An other approach for all that debugging purposes could be to use a special >>>>>>> docker image / docker container that delivers all the trouble shooting tools >>>>>>> required and run that with proper elevated rights.. >>>> >>>> That is either complex, as the container has not all capabilities needed >>>> for proper debugging purposes, or a security nightmare, or most probably >>>> both. >>>> >>> >>> Yes - there is security and complexity assigned - but installing all the required debug packages on all the servers might be even worse from a security point of view and they might not be even part of the CaaSP delivery channels. >>> Advantage of a debug container is that it can be added on demand and cleanup is fully automated.. when installing all the debug packages these are a security problem while they are installed and the also need to be upgraded / patched etc. >>> >>> So both ways have their pros and cons ;-) >>> >>> Martin >>> >>> >>> _______________________________________________ >>> 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 Martin.Weiss at suse.com Fri Dec 8 02:48:55 2017 From: Martin.Weiss at suse.com (Martin Weiss) Date: Fri, 08 Dec 2017 02:48:55 -0700 Subject: [caasp-beta] Antw: Re: kubeconfig download error In-Reply-To: <943AE357-E27A-4D98-863A-DA71DA625511@suse.com> References: <6D181E7A-9FC6-4ACF-AD08-BE05CB375F88@sap.com> <943AE357-E27A-4D98-863A-DA71DA625511@suse.com> Message-ID: <5A2A60070200001C0030A120@prv-mh.provo.novell.com> Hi Rushi, just to be sure to be sure - could you check the dex logs for the error you see, there? (I ran into a similar issue recently where the SSL certificates for the LDAP server were not correct and I have seen that dex comlains about that..) Thanks, Martin Hi Rushi, As before you have to use the beta list for communication. I saw a couple of people like Martin send you a couple of suggestions I don?t know if these were followed (I didn?t see any further emails) but please give these a try. I know there are a few other colleagues in SAP have set this up successfully (for Vora) so you might wish to check in with them for assistance. I can only log support tickets for paying customers however as I mentioned before you are free to log a bugzilla as you did before. If that bug hasn?t yet had any progress on it you are welcome to add a comment to it asking for an update. As before really emailing myself and other colleagues is going to make it harder for us to help and I?m not in a position to help anyway so please use the beta list and bugzilla as per the known process. Sent from my iPhone - please excuse any shortness > On 7 Dec 2017, at 16:29, Ns, Rushi wrote: > > Hi Rob,. > > Do you have time , I still have the issue downloading the kubeconfig and I filed the bug. , however no solution yet from SUSE. > > > > Best Regards, > > Rushi. > I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE > > > On 12/7/17, 7:25 AM, "caasp-beta-bounces at lists.suse.com on behalf of Rob de Canha-Knight" wrote: > > It?s also worth mentioning that we have privileged containers enabled within CaaSP so the vast majority of debugging containers should work without issue when you pass ?privileged into the docker run command. > > As Martin points out we try to keep the security surface as small as possible by only installing the bare minimum needed to run containers. MicroOS is designed to only run containers and isn?t recommended for running any kind of binary or package so a debug container is the best approach IMHO. > > If you have a specific issue with a specific tool inside of a privileged debug container please let us know as we can definitely look into this and try and fix any compatibility issues that may arise. > > Rob > > Sent from my iPhone - please excuse any shortness > >> On 7 Dec 2017, at 15:57, Martin Weiss wrote: >> >> >> >>>>>> An other approach for all that debugging purposes could be to use a special >>>>>> docker image / docker container that delivers all the trouble shooting tools >>>>>> required and run that with proper elevated rights.. >>> >>> That is either complex, as the container has not all capabilities needed >>> for proper debugging purposes, or a security nightmare, or most probably >>> both. >>> >> >> Yes - there is security and complexity assigned - but installing all the required debug packages on all the servers might be even worse from a security point of view and they might not be even part of the CaaSP delivery channels. >> Advantage of a debug container is that it can be added on demand and cleanup is fully automated.. when installing all the debug packages these are a security problem while they are installed and the also need to be upgraded / patched etc. >> >> So both ways have their pros and cons ;-) >> >> Martin >> >> >> _______________________________________________ >> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From special011 at gmail.com Sun Dec 10 21:13:25 2017 From: special011 at gmail.com (Jerry Hwang) Date: Sun, 10 Dec 2017 20:13:25 -0800 Subject: [caasp-beta] caas v2 networking Message-ID: Hi, I have a general question. CaaS v2 networking is flannel overlay networking using udp encapsulation for traffic between nodes. If my app is based on docker "host" networking (net=host), how to make the app migration from docker to caas/kubernetes env possible? Thanks, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: From fcastelli at suse.com Wed Dec 20 02:26:21 2017 From: fcastelli at suse.com (Flavio Castelli) Date: Wed, 20 Dec 2017 10:26:21 +0100 Subject: [caasp-beta] caas v2 networking In-Reply-To: References: Message-ID: On 12/11/2017 05:13 AM, Jerry Hwang wrote: > I have a general question. > CaaS v2 networking is flannel overlay networking using udp encapsulation > for traffic between nodes. > If my app is based on docker "host" networking (net=host), how to make > the app migration from docker to caas/kubernetes env possible? You can still tell kubernetes to create a pod that uses the host network: kind: Pod spec: hostNetwork: True ... However please evaluate whether that makes still sense in the kubernetes context. Cheers Flavio From special011 at gmail.com Wed Dec 20 13:05:21 2017 From: special011 at gmail.com (Jerry Hwang) Date: Wed, 20 Dec 2017 12:05:21 -0800 Subject: [caasp-beta] caas v2 networking In-Reply-To: References: Message-ID: Thanks Flavio. So SUSE CaaS v2 networking is flannel (overlay). Regardless I set "hostNetwork: True" for Pod, the inter-nodes traffic will be still encapsulated in udp backend? Any consideration for non-overlay networking solution for v3+? Jerry On Wed, Dec 20, 2017 at 1:26 AM, Flavio Castelli wrote: > On 12/11/2017 05:13 AM, Jerry Hwang wrote: > > I have a general question. > > CaaS v2 networking is flannel overlay networking using udp encapsulation > > for traffic between nodes. > > If my app is based on docker "host" networking (net=host), how to make > > the app migration from docker to caas/kubernetes env possible? > > You can still tell kubernetes to create a pod that uses the host network: > > kind: Pod > spec: > hostNetwork: True > ... > > However please evaluate whether that makes still sense in the kubernetes > context. > > Cheers > Flavio > _______________________________________________ > 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: From alvaro.saurin at suse.com Wed Dec 20 14:38:41 2017 From: alvaro.saurin at suse.com (Alvaro Saurin) Date: Wed, 20 Dec 2017 22:38:41 +0100 Subject: [caasp-beta] caas v2 networking In-Reply-To: References: Message-ID: <538cbdcf-c3f4-7c81-5a3c-44d2edcd9de0@suse.com> When a pod is configured with "hostNetwork: true", the applications running in such a pod can directly see the network interfaces of the host machine where the pod was started. From the networking point of view, it will behave as any other application running in the host. And, even if flannel is still running in the host, the pod will not be automatically connected to that overlay network but use the native routing mechanism. Cheers Alvaro On 12/20/2017 09:05 PM, Jerry Hwang wrote: > Thanks Flavio. > So SUSE CaaS v2 networking is flannel (overlay). > Regardless I set "hostNetwork: True" for Pod, the inter-nodes traffic > will be still encapsulated in udp backend? > Any consideration for non-overlay networking solution for v3+? > > Jerry > > On Wed, Dec 20, 2017 at 1:26 AM, Flavio Castelli > wrote: > > On 12/11/2017 05:13 AM, Jerry Hwang wrote: > > I have a general question. > > CaaS v2 networking is flannel overlay networking using udp > encapsulation > > for traffic between nodes. > > If my app is based on docker "host" networking (net=host), how > to make > > the app migration from docker to caas/kubernetes env possible? > > You can still tell kubernetes to create a pod that uses the host > network: > > kind: Pod > spec: > ? hostNetwork: True > ... > > However please evaluate whether that makes still sense in the > kubernetes > context. > > 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 -- Alvaro Saurin 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: OpenPGP digital signature URL: From special011 at gmail.com Wed Dec 20 14:52:54 2017 From: special011 at gmail.com (Jerry Hwang) Date: Wed, 20 Dec 2017 13:52:54 -0800 Subject: [caasp-beta] caas v2 networking In-Reply-To: <538cbdcf-c3f4-7c81-5a3c-44d2edcd9de0@suse.com> References: <538cbdcf-c3f4-7c81-5a3c-44d2edcd9de0@suse.com> Message-ID: Nice, thanks Alvaro for the clarification. Jerry On Wed, Dec 20, 2017 at 1:38 PM, Alvaro Saurin wrote: > > > When a pod is configured with "hostNetwork: true", the applications > running in such a pod can directly see the network interfaces of the host > machine where the pod was started. From the networking point of view, it > will behave as any other application running in the host. And, even if > flannel is still running in the host, the pod will not be automatically > connected to that overlay network but use the native routing mechanism. > > Cheers > > > Alvaro > > > > > On 12/20/2017 09:05 PM, Jerry Hwang wrote: > > Thanks Flavio. > So SUSE CaaS v2 networking is flannel (overlay). > Regardless I set "hostNetwork: True" for Pod, the inter-nodes traffic will > be still encapsulated in udp backend? > Any consideration for non-overlay networking solution for v3+? > > Jerry > > On Wed, Dec 20, 2017 at 1:26 AM, Flavio Castelli > wrote: > >> On 12/11/2017 05:13 AM, Jerry Hwang wrote: >> > I have a general question. >> > CaaS v2 networking is flannel overlay networking using udp encapsulation >> > for traffic between nodes. >> > If my app is based on docker "host" networking (net=host), how to make >> > the app migration from docker to caas/kubernetes env possible? >> >> You can still tell kubernetes to create a pod that uses the host network: >> >> kind: Pod >> spec: >> hostNetwork: True >> ... >> >> However please evaluate whether that makes still sense in the kubernetes >> context. >> >> Cheers >> Flavio >> _______________________________________________ >> caasp-beta mailing list >> caasp-beta at lists.suse.com >> http://lists.suse.com/mailman/listinfo/caasp-beta >> > > > > _______________________________________________ > caasp-beta mailing listcaasp-beta at lists.suse.comhttp://lists.suse.com/mailman/listinfo/caasp-beta > > > -- > Alvaro Saurin > Senior Software Engineer > SUSE Linux GmbH, Maxfeldstr. 5, D-90409 N?rnberg Tel: +49-911-74053-0; Fax: +49-911-7417755 <+49%20911%207417755>; 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: