From beta-programs at lists.suse.com Mon May 7 12:50:14 2018 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Mon, 07 May 2018 18:50:14 +0000 Subject: [caasp-beta] [ANNOUNCE] SUSE Container as a Service Platform 3 Beta 1 is available! Message-ID: <5af09fe6d6364_345cc6b31c445a@sle-prjmgr.mail> We are happy to announce the SUSE Container as a Service Platform 3 Beta 1: Download[2] Please check out our dedicated SUSE CaaS Platform Beta web page[1], where you will find all the information needed around SUSE CaaS Platform Beta. What?s New with SUSE CaaS Platform 3 Beta 1? ===== - Ability to run offline deployments with a proxy registry - Enhanced performance, extensibility, and hardware support with Kubernetes 1.9 and SUSE MicroOS updates - Enhanced debugging tools delivered via a new Toolchain module for SUSE CaaS Platform with a registered system - There is now an option in Velum to retry failed orchestrations - We enabled Node removal on a bootstrapped cluster in our dashboard Velum Things to consider for this Beta? ===== - Node Removal In rare cases we noticed that node removal can fail. In this case you may make use of Force Removal in the UI, to progress. - DHCP Your DHCP server should provide resolveable hostnames. If this is not the case like with libvirt/KVM, you should consider providing one yourself by appending this kernel parameter "hostname=HOSTNAME" during installation. However, the kubeconfig file downloaded from the Dashboard could contain an incorrect "server" hostname that should be replaced with the IP address of your Master. For more information read: https://en.opensuse.org/SDB:Linuxrc#Network_Configuration - Autoyast/VMX-Images 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. Release schedule[4] Documentation[5] Have fun beta testing! Your SUSE Linux Enterprise Team Please refer to our dedicated SUSE CaaSP Beta Program webpage[1] for any general information. However, do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. You received this email because you're signed up to get updates from us. Please send an email to beta-programs at lists.suse.com if you want to unsubscribe. [1]https://www.suse.com/betaprogram/caasp-beta [2]https://www.suse.com/betaprogram/caasp-beta/#download [4]https://www.suse.com/betaprogram/caasp-beta/#releases [5]https://www.suse.com/betaprogram/caasp-beta/#documentation -------------- next part -------------- An HTML attachment was scrubbed... URL: From special011 at gmail.com Fri May 11 22:35:05 2018 From: special011 at gmail.com (Jerry Hwang) Date: Fri, 11 May 2018 21:35:05 -0700 Subject: [caasp-beta] Storageclass volume plug-in on baremetal Message-ID: Hi, Does anyone know what storageclass plug-in I should use for suse caas on baremetal? https://kubernetes.io/docs/concepts/storage/storage-classes/#provisioner For vSphere, I use this. provisioner: kubernetes.io/vsphere-volume Thanks, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: From rob.decanha-knight at suse.com Sun May 13 02:38:36 2018 From: rob.decanha-knight at suse.com (Rob de Canha-Knight) Date: Sun, 13 May 2018 08:38:36 +0000 Subject: [caasp-beta] Storageclass volume plug-in on baremetal In-Reply-To: References: Message-ID: <0FFB22B6-0740-44C8-B900-DFB81B8E0880@suse.com> Hi Jerry. The only storageclass that we support on bare metal is the Ceph RBD one to connect it to your SES cluster. https://kubernetes.io/docs/concepts/storage/storage-classes/#ceph-rbd The NFS related provisioners also work okay (https://github.com/kubernetes-incubator/external-storage/tree/master/nfs and https://github.com/kubernetes-incubator/external-storage/tree/master/nfs-client) however these are unsupported as they?re incubator projects so we can?t help with any issues encountered. Rob ----- Rob de Canha-Knight EMEA Platform and Management Technical Strategist SUSE rob.decanha-knight at suse.com (P) +44 (0) 1635 937689 (M) +44 (0) 7869 113493 (TW) rssfed23 I work in GMT/BST time zone ---- From: on behalf of Jerry Hwang Date: Saturday, 12 May 2018 at 05:35 To: "caasp-beta at lists.suse.com" Subject: [caasp-beta] Storageclass volume plug-in on baremetal Hi, Does anyone know what storageclass plug-in I should use for suse caas on baremetal? https://kubernetes.io/docs/concepts/storage/storage-classes/#provisioner For vSphere, I use this. provisioner: kubernetes.io/vsphere-volume Thanks, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: From special011 at gmail.com Sun May 13 09:21:05 2018 From: special011 at gmail.com (Jerry Hwang) Date: Sun, 13 May 2018 08:21:05 -0700 Subject: [caasp-beta] Storageclass volume plug-in on baremetal In-Reply-To: <0FFB22B6-0740-44C8-B900-DFB81B8E0880@suse.com> References: <0FFB22B6-0740-44C8-B900-DFB81B8E0880@suse.com> Message-ID: Thank you Rob for the answer. We have been actively using/testing storagclass/PVC for k8s, but we don't (even plan to) use ceph-rbd. Regards, Jerry On Sun, May 13, 2018 at 1:38 AM, Rob de Canha-Knight < rob.decanha-knight at suse.com> wrote: > Hi Jerry. > > > > The only storageclass that we support on bare metal is the Ceph RBD one to > connect it to your SES cluster. https://kubernetes.io/docs/ > concepts/storage/storage-classes/#ceph-rbd > > > > The NFS related provisioners also work okay (https://github.com/ > kubernetes-incubator/external-storage/tree/master/nfs and > https://github.com/kubernetes-incubator/external-storage/ > tree/master/nfs-client) however these are unsupported as they?re > incubator projects so we can?t help with any issues encountered. > > > > Rob > > > > ----- > > *Rob de Canha-Knight* > > EMEA Platform and Management Technical Strategist > > SUSE > > rob.decanha-knight at suse.com > > (P) +44 (0) 1635 937689 > > (M) +44 (0) 7869 113493 > > (TW) rssfed23 > > I work in GMT/BST time zone > > ---- > > > > > > *From: * on behalf of Jerry Hwang < > special011 at gmail.com> > *Date: *Saturday, 12 May 2018 at 05:35 > *To: *"caasp-beta at lists.suse.com" > *Subject: *[caasp-beta] Storageclass volume plug-in on baremetal > > > > Hi, > > > > Does anyone know what storageclass plug-in I should use for suse caas on > baremetal? > > > > https://kubernetes.io/docs/concepts/storage/storage-classes/#provisioner > > > > For vSphere, I use this. > > provisioner: kubernetes.io/vsphere-volume > > > > Thanks, > Jerry > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aj at suse.com Mon May 14 06:40:16 2018 From: aj at suse.com (Andreas Jaeger) Date: Mon, 14 May 2018 14:40:16 +0200 Subject: [caasp-beta] Storageclass volume plug-in on baremetal In-Reply-To: References: Message-ID: <054f25a6-0a66-5450-5ab5-fd48b2fd621d@suse.com> On 2018-05-12 06:35, Jerry Hwang wrote: > Hi, > > Does anyone know what storageclass plug-in I should use for suse caas on > baremetal? > > https://kubernetes.io/docs/concepts/storage/storage-classes/#provisioner > > For vSphere, I use this. > provisioner: kubernetes.io/vsphere-volume > What kind of storage do you have that you want to use in your cluster? Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From special011 at gmail.com Mon May 14 07:24:46 2018 From: special011 at gmail.com (Jerry Hwang) Date: Mon, 14 May 2018 06:24:46 -0700 Subject: [caasp-beta] Storageclass volume plug-in on baremetal In-Reply-To: <054f25a6-0a66-5450-5ab5-fd48b2fd621d@suse.com> References: <054f25a6-0a66-5450-5ab5-fd48b2fd621d@suse.com> Message-ID: Andreas, Each node has a few HDD (7TB) for storage. No special SAN or storage software cluster. On Mon, May 14, 2018 at 5:40 AM, Andreas Jaeger wrote: > On 2018-05-12 06:35, Jerry Hwang wrote: > > Hi, > > > > Does anyone know what storageclass plug-in I should use for suse caas on > > baremetal? > > > > https://kubernetes.io/docs/concepts/storage/storage-classes/#provisioner > > > > For vSphere, I use this. > > provisioner: kubernetes.io/vsphere-volume > > > > What kind of storage do you have that you want to use in your cluster? > > Andreas > -- > Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany > GF: Felix Imend?rffer, Jane Smithard, Graham Norton, > HRB 21284 (AG N?rnberg) > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aj at suse.com Mon May 14 08:13:37 2018 From: aj at suse.com (Andreas Jaeger) Date: Mon, 14 May 2018 16:13:37 +0200 Subject: [caasp-beta] Storageclass volume plug-in on baremetal In-Reply-To: References: <054f25a6-0a66-5450-5ab5-fd48b2fd621d@suse.com> Message-ID: <15de68fa-f808-38c0-9669-09be48aedcf4@suse.com> On 2018-05-14 15:24, Jerry Hwang wrote: > Andreas, > > Each node has a few HDD (7TB) for storage. No special SAN or storage > software cluster. Then you won't have persistent dynamic storage at all, only Local storage would work on your system, Andreas > > On Mon, May 14, 2018 at 5:40 AM, Andreas Jaeger > wrote: > > On 2018-05-12 06:35, Jerry Hwang wrote: > > Hi, > > > > Does anyone know what storageclass plug-in I should use for suse > caas on > > baremetal? > > > > > https://kubernetes.io/docs/concepts/storage/storage-classes/#provisioner > > > > > For vSphere, I use this. > > provisioner: kubernetes.io/vsphere-volume > > > > > > What kind of storage do you have that you want to use in your cluster? > > Andreas > -- > ?Andreas Jaeger aj@{suse.com ,opensuse.org > } Twitter: jaegerandi > ? SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany > ? ?GF: Felix Imend?rffer, Jane Smithard, Graham Norton, > ? ? ? ?HRB 21284 (AG N?rnberg) > ? ? GPG fingerprint = 93A3 365E CE47 B889 DF7F? FED1 389A 563C C272 A126 > > -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany GF: Felix Imend?rffer, Jane Smithard, Graham Norton, HRB 21284 (AG N?rnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From special011 at gmail.com Mon May 14 08:45:28 2018 From: special011 at gmail.com (Jerry Hwang) Date: Mon, 14 May 2018 07:45:28 -0700 Subject: [caasp-beta] Storageclass volume plug-in on baremetal In-Reply-To: <15de68fa-f808-38c0-9669-09be48aedcf4@suse.com> References: <054f25a6-0a66-5450-5ab5-fd48b2fd621d@suse.com> <15de68fa-f808-38c0-9669-09be48aedcf4@suse.com> Message-ID: Thanks Andreas. On Mon, May 14, 2018 at 7:13 AM, Andreas Jaeger wrote: > On 2018-05-14 15:24, Jerry Hwang wrote: > > Andreas, > > > > Each node has a few HDD (7TB) for storage. No special SAN or storage > > software cluster. > > Then you won't have persistent dynamic storage at all, only Local > storage would work on your system, > > Andreas > > > > > On Mon, May 14, 2018 at 5:40 AM, Andreas Jaeger > > wrote: > > > > On 2018-05-12 06:35, Jerry Hwang wrote: > > > Hi, > > > > > > Does anyone know what storageclass plug-in I should use for suse > > caas on > > > baremetal? > > > > > > > > https://kubernetes.io/docs/concepts/storage/storage- > classes/#provisioner > > classes/#provisioner> > > > > > > For vSphere, I use this. > > > provisioner: kubernetes.io/vsphere-volume > > > > > > > > > > > What kind of storage do you have that you want to use in your > cluster? > > > > Andreas > > -- > > Andreas Jaeger aj@{suse.com ,opensuse.org > > } Twitter: jaegerandi > > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany > > GF: Felix Imend?rffer, Jane Smithard, Graham Norton, > > HRB 21284 (AG N?rnberg) > > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 > A126 > > > > > > > -- > Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany > GF: Felix Imend?rffer, Jane Smithard, Graham Norton, > HRB 21284 (AG N?rnberg) > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ettore.simone at gmail.com Tue May 15 09:19:13 2018 From: ettore.simone at gmail.com (Ettore Simone) Date: Tue, 15 May 2018 17:19:13 +0200 Subject: [caasp-beta] Calico CNI integration Message-ID: Hi, I'm trying to integrate Calico as a policy security enforcement at the end of a simple CaaSP 3.0 deployment without any success. To simplify the deployment and test we are using a single master, single worker layout. Following the official Calico documentation for Canal[1] will result in . First, Calico recommend to use the Kubernetes API datastore against the etcd one. Is there a best practice to follow in CaaSP for it? Should I go with etcd datastore instead? Second, are there any one who already adapted the RBAC[2] and Service/Deployment/DaemonSet[3] to run under SUSE CaaSP? Thanks, Ettore [1] https://docs.projectcalico.org/v3.1/getting-started/kubernetes/installation/flannel [2] https://docs.projectcalico.org/v3.1/getting-started/kubernetes/installation/hosted/canal/rbac.yaml [3] https://docs.projectcalico.org/v3.1/getting-started/kubernetes/installation/hosted/canal/canal.yaml -------------- next part -------------- An HTML attachment was scrubbed... URL: From beta-programs at lists.suse.com Fri May 18 11:43:18 2018 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Fri, 18 May 2018 17:43:18 +0000 Subject: [caasp-beta] [ANNOUNCE] SUSE CaaS Platform 3 Beta 2 is available! Message-ID: <5aff10b618a42_41fb5ed30025737@sle-prjmgr.mail> We are happy to announce the SUSE Container as a Service Platform 3 Beta 2: Download[2] Please check out our dedicated SUSE CaaS Platform Beta web page[1], where you will find all the information needed around SUSE CaaS Platform Beta. What?s New with SUSE CaaS Platform 3 Beta? ===== - Ability to run offline deployments with a proxy registry - Enhanced performance, extensibility, and hardware support with Kubernetes 1.9 and SUSE MicroOS updates - Enhanced debugging tools delivered via a new Toolchain module for SUSE CaaS Platform with a registered system - There is now an option in Velum to retry failed orchestrations - We enabled Node removal on a bootstrapped cluster in our dashboard Velum Fixed in Beta 2 ==== - Node Removal failures - (bsc#1091361) Worker node removal fails (not forced removal) - worker is not etcd member - (bsc#1092614) Node removal fails: crio.stop not available on the salt master - (bsc#1091077) L3: Cluster bootstrap fails in macro get_primary_iface for all master and worker nodes - (bsc#1091419) UI CPI config - bootstrap fails - (bsc#1091843) When updating from 2.0 the `update all nodes` link disappears - (bsc#1090841) updates can break when container-feeder skips loading images - (bsc#1092140) opting out of PodSecurityPolicy makes bootstrap fail Things to consider for this Beta? ===== - DHCP Your DHCP server should provide resolveable hostnames. If this is not the case like with libvirt/KVM, you should consider providing one yourself by appending this kernel parameter "hostname=HOSTNAME" during installation. However, the kubeconfig file downloaded from the Dashboard could contain an incorrect "server" hostname that should be replaced with the IP address of your Master. For more information read: https://en.opensuse.org/SDB:Linuxrc#Network_Configuration - Autoyast/VMX-Images 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. Release schedule[4] Documentation[5] Have fun beta testing! Your SUSE CaaS Platform Team Please refer to our dedicated SUSE CaaSP Beta Program webpage[1] for any general information. However, do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. You received this email because you're signed up to get updates from us. Please send an email to beta-programs at lists.suse.com if you want to unsubscribe. [1]https://www.suse.com/betaprogram/caasp-beta [2]https://www.suse.com/betaprogram/caasp-beta/#download [4]https://www.suse.com/betaprogram/caasp-beta/#releases [5]https://www.suse.com/betaprogram/caasp-beta/#documentation -------------- next part -------------- An HTML attachment was scrubbed... URL: From lproven at suse.com Thu May 24 04:25:43 2018 From: lproven at suse.com (Liam Proven) Date: Thu, 24 May 2018 12:25:43 +0200 Subject: [caasp-beta] How to deploy CaaSP on EC2? In-Reply-To: References: Message-ID: <20180524122543.4a56aea7.lproven@suse.com> On Thu, 24 May 2018 06:34:27 +0000 "Yoshise, Junichi" wrote: > I?m trying to deploy CaaSP 3.0 beta2 on AWS EC2. Since AMI is not > available, I?ve converted qcow2 or vmdk file then tried to import to > EC2, but it didn?t work. Is there any way to deploy CaaSP on EC2? As I understand it, currently, for public cloud use, you should be looking at CaaSP 2.1, not 3.0 -- and I believe it has not yet reached beta phase. -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, K?i??kova 148/34, 186-00 Praha 8 - Karl?n, Czechia Email: lproven at suse.com - Office telephone: +420 284 241 084 From vrothberg at suse.com Thu May 24 06:06:57 2018 From: vrothberg at suse.com (Valentin Rothberg) Date: Thu, 24 May 2018 14:06:57 +0200 Subject: [caasp-beta] Strange behaviour docker CAASP v3 beta 1 In-Reply-To: References: Message-ID: <20180524120657.chzuzutvc5nxnxug@nebuchadnezzar> Hi, thanks a lot for reaching out to us. On May/24/18 10:04, Le Bihan St?phane (AMUNDI-ITS) wrote: [...] > Error response from daemon: rpc error: code = Unknown desc = containerd: container not found > > I don't understand why container is not destroyed. Have you any idea ? Similar issues usually happen when processes inside the containers are not properly shutdown (e.g., when the system runs out of memory or when a process has forcefully been killed for any other reason). In addition to steps mentioned below, may I ask how much RAM the node you extracted the logs above from has? This is hard to say without looking at the logs. If possible, could you provide a supportconfig for us to have a first glimpse at your issue? Feel free to open a bug or upload the logs somewhere reachable for us as described here [1]. Kind regards, Valentin [1] https://www.suse.com/c/free_tools/supportconfig-linux/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: not available URL: From stephane.lebihan at amundi.com Thu May 24 06:34:32 2018 From: stephane.lebihan at amundi.com (=?utf-8?B?TGUgQmloYW4gU3TDqXBoYW5lIChBTVVOREktSVRTKQ==?=) Date: Thu, 24 May 2018 12:34:32 +0000 Subject: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? In-Reply-To: <20180524122543.4a56aea7.lproven@suse.com> References: <20180524122543.4a56aea7.lproven@suse.com> Message-ID: Thanks for your response. I launch support_config, but it's stuck at Docker line .... I wait. Memory limit on server is not at limit (big server :D) total used free shared buffers cached Mem: 377 14 363 0 0 9 -/+ buffers/cache: 4 373 Swap: 0 0 0 And for application developer say me : "Influxtreon consumes about 150kB to run" I wait for support_config. Regards, St?phane Le Bihan SDE/DSI/IPR/SSD/UNX 90, Boulevard Pasteur - 75015 Paris Web: www.amundi.com Tel: +33 1 76 32 32 08 Tel Unix Team: +33 1 76 32 02 30 @: stephane.lebihan at amundi.com @: sits.unix at amundi.com Visit us on: -----Message d'origine----- De?: caasp-beta-bounces at lists.suse.com [mailto:caasp-beta-bounces at lists.suse.com] De la part de Liam Proven Envoy??: jeudi 24 mai 2018 12:26 ??: Yoshise, Junichi Cc?: caasp-beta at lists.suse.com Objet?: [Marketing Mail] Re: [caasp-beta] How to deploy CaaSP on EC2? On Thu, 24 May 2018 06:34:27 +0000 "Yoshise, Junichi" wrote: > I?m trying to deploy CaaSP 3.0 beta2 on AWS EC2. Since AMI is not > available, I?ve converted qcow2 or vmdk file then tried to import to > EC2, but it didn?t work. Is there any way to deploy CaaSP on EC2? As I understand it, currently, for public cloud use, you should be looking at CaaSP 2.1, not 3.0 -- and I believe it has not yet reached beta phase. -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, K?i??kova 148/34, 186-00 Praha 8 - Karl?n, Czechia Email: lproven at suse.com - Office telephone: +420 284 241 084 _______________________________________________ caasp-beta mailing list caasp-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/caasp-beta From stephane.lebihan at amundi.com Thu May 24 06:42:39 2018 From: stephane.lebihan at amundi.com (=?utf-8?B?TGUgQmloYW4gU3TDqXBoYW5lIChBTVVOREktSVRTKQ==?=) Date: Thu, 24 May 2018 12:42:39 +0000 Subject: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? In-Reply-To: References: <20180524122543.4a56aea7.lproven@suse.com> Message-ID: For information another response from another develloper : " Hi, I've created new test cron job and even that generates the Terminating pods: $ kp get pods -n tick NAME READY STATUS RESTARTS AGE data-influxdb-5c7b44ff76-fcf5m 1/1 Running 2 9d grafana-7dc9f4bccc-k6gbc 1/1 Running 3 9d influxtreon-1527164760-64xf9 0/1 Terminating 0 5m influxtreon-1527164940-27565 0/1 Completed 0 2m influxtreon-1527165000-mh27k 0/1 Completed 0 1m influxtreon-1527165060-d8jww 0/1 Completed 0 16s sleeper-1527164640-9njtv 0/1 Terminating 0 7m sleeper-1527164760-xm79v 0/1 Completed 0 5m sleeper-1527164820-ptb64 0/1 Terminating 0 4m sleeper-1527164880-q6f6d 0/1 Completed 0 3m sleeper-1527164940-j2k8f 0/1 Completed 0 2m sleeper-1527165000-bp5vx 0/1 Terminating 0 1m sleeper-1527165060-72b9l 0/1 Completed 0 15s Here's the cron configuraton: --- apiVersion: batch/v1beta1 kind: CronJob metadata: name: sleeper spec: schedule: "*/1 * * * *" concurrencyPolicy: Replace successfulJobsHistoryLimit: 3 failedJobsHistoryLimit: 3 jobTemplate: spec: template: spec: containers: - name: sleeper image: /library/ubuntu:18.04 args: - "/bin/sleep" - "5" restartPolicy: OnFailure imagePullSecrets: - name: regcred Here's the source code for sleep: https://github.com/coreutils/coreutils/blob/master/src/sleep.c I'd say there's definitely other pods that have the same issue. :D" Regards St?phane Le Bihan SDE/DSI/IPR/SSD/UNX 90, Boulevard Pasteur - 75015 Paris Web: www.amundi.com Tel: +33 1 76 32 32 08 Tel Unix Team: +33 1 76 32 02 30 @: stephane.lebihan at amundi.com @: sits.unix at amundi.com Visit us on: -----Message d'origine----- De?: caasp-beta-bounces at lists.suse.com [mailto:caasp-beta-bounces at lists.suse.com] De la part de Le Bihan St?phane (AMUNDI-ITS) Envoy??: jeudi 24 mai 2018 14:35 ??: lproven at suse.com; Yoshise, Junichi Cc?: caasp-beta at lists.suse.com Objet?: Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? Thanks for your response. I launch support_config, but it's stuck at Docker line .... I wait. Memory limit on server is not at limit (big server :D) total used free shared buffers cached Mem: 377 14 363 0 0 9 -/+ buffers/cache: 4 373 Swap: 0 0 0 And for application developer say me : "Influxtreon consumes about 150kB to run" I wait for support_config. Regards, St?phane Le Bihan SDE/DSI/IPR/SSD/UNX 90, Boulevard Pasteur - 75015 Paris Web: www.amundi.com Tel: +33 1 76 32 32 08 Tel Unix Team: +33 1 76 32 02 30 @: stephane.lebihan at amundi.com @: sits.unix at amundi.com Visit us on: -----Message d'origine----- De?: caasp-beta-bounces at lists.suse.com [mailto:caasp-beta-bounces at lists.suse.com] De la part de Liam Proven Envoy??: jeudi 24 mai 2018 12:26 ??: Yoshise, Junichi Cc?: caasp-beta at lists.suse.com Objet?: [Marketing Mail] Re: [caasp-beta] How to deploy CaaSP on EC2? On Thu, 24 May 2018 06:34:27 +0000 "Yoshise, Junichi" wrote: > I?m trying to deploy CaaSP 3.0 beta2 on AWS EC2. Since AMI is not > available, I?ve converted qcow2 or vmdk file then tried to import to > EC2, but it didn?t work. Is there any way to deploy CaaSP on EC2? As I understand it, currently, for public cloud use, you should be looking at CaaSP 2.1, not 3.0 -- and I believe it has not yet reached beta phase. -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, K?i??kova 148/34, 186-00 Praha 8 - Karl?n, Czechia Email: lproven at suse.com - Office telephone: +420 284 241 084 _______________________________________________ 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 junichi.yoshise at hpe.com Thu May 24 06:58:06 2018 From: junichi.yoshise at hpe.com (Yoshise, Junichi) Date: Thu, 24 May 2018 12:58:06 +0000 Subject: [caasp-beta] How to deploy CaaSP on EC2? In-Reply-To: <20180524122543.4a56aea7.lproven@suse.com> References: <20180524122543.4a56aea7.lproven@suse.com> Message-ID: Even for 2.1, I can't find any AMI nor document. Is it really ready? -----Original Message----- From: Liam Proven Sent: Thursday, May 24, 2018 7:26 PM To: Yoshise, Junichi Cc: caasp-beta at lists.suse.com Subject: Re: [caasp-beta] How to deploy CaaSP on EC2? On Thu, 24 May 2018 06:34:27 +0000 "Yoshise, Junichi" wrote: > I?m trying to deploy CaaSP 3.0 beta2 on AWS EC2. Since AMI is not > available, I?ve converted qcow2 or vmdk file then tried to import to > EC2, but it didn?t work. Is there any way to deploy CaaSP on EC2? As I understand it, currently, for public cloud use, you should be looking at CaaSP 2.1, not 3.0 -- and I believe it has not yet reached beta phase. -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, K?i??kova 148/34, 186-00 Praha 8 - Karl?n, Czechia Email: lproven at suse.com - Office telephone: +420 284 241 084 From stephane.lebihan at amundi.com Thu May 24 07:39:45 2018 From: stephane.lebihan at amundi.com (=?utf-8?B?TGUgQmloYW4gU3TDqXBoYW5lIChBTVVOREktSVRTKQ==?=) Date: Thu, 24 May 2018 13:39:45 +0000 Subject: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? References: <20180524122543.4a56aea7.lproven@suse.com> Message-ID: Log docker : 2018-05-24T15:31:45.955719+02:00 dl360o-101 dockerd[2055]: time="2018-05-24T15:31:45.954756307+02:00" level=warning msg="container kill failed because of 'container not found' or 'no such process': Cannot kill container f87327727cc5d4628082cb4d0c09503f82ddcbd6d8055db63cf8020c10f6cb11: rpc error: code = Unknown desc = containerd: container not found" 2018-05-24T15:31:45.955852+02:00 dl360o-101 dockerd[2055]: time="2018-05-24T15:31:45.954770487+02:00" level=warning msg="container kill failed because of 'container not found' or 'no such process': Cannot kill container bbb9a2b7215fdd144391d198e6a3c3a11bc9cc035d36701a21d3bb92a3799200: rpc error: code = Unknown desc = containerd: container not found" 2018-05-24T15:31:45.955985+02:00 dl360o-101 dockerd[2055]: time="2018-05-24T15:31:45.954773986+02:00" level=warning msg="container kill failed because of 'container not found' or 'no such process': Cannot kill container d4e3cad021df83cd9ba3bcb04d8c9cc0bd54a4f85c6935bec65fead9e2fa9840: rpc error: code = Unknown desc = containerd: container not found" Support config is stuck : root at dl360o-101:/root$ supportconfig ============================================================================= Support Utilities - Supportconfig Script Version: 3.0-105 Script Date: 2018 01 05 Detailed system information and logs are collected and organized in a manner that helps reduce service request resolution times. Private system information can be disclosed when using this tool. If this is a concern, please prune private data from the log files. Several startup options are available to exclude more sensitive information. Supportconfig data is used only for diagnostic purposes and is considered confidential information. See http://www.novell.com/company/legal/privacy/ ============================================================================= Gathering system information Data Directory: /var/log/nts_dl360o-101_180524_1401 Basic Server Health Check... Done RPM Database... Done Basic Environment... Done System Modules... Done Memory Details... Done Disk I/O... Done B-tree File System... Done YaST Files... Done File System List... Skipped Auditing... Done Crash Info... Done NTP... Done PROC... Done Boot Files... Done SLERT... Skipped Updates... Done SMT... Skipped HA Cluster... Skipped OCFS2... Skipped DRBD... Skipped HAPROXY... Skipped PAM... Done LDAP... Skipped System Security Services... Skipped CIMOM... Skipped Open Files... Done Environment... Done Command History... Excluded ETC... Done SYSCONFIG... Done SYSFS... Done SystemD... Done Docker... # ps axjf | egrep "PPID|13967" PPID PID PGID SID TTY TPGID STAT UID TIME COMMAND 12419 12427 12427 12427 pts/0 13967 Ss 0 0:00 | \_ -bash 12427 13967 13967 12427 pts/0 13967 S+ 0 0:28 | \_ /bin/bash /sbin/supportconfig 13967 12731 13967 12427 pts/0 13967 S+ 0 0:00 | \_ bash 12731 12732 13967 12427 pts/0 13967 Sl+ 0 0:00 | \_ /usr/bin/docker top 843c6dd27ae7 26499 47700 47699 26499 pts/1 47699 S+ 0 0:00 \_ egrep PPID|13967 # /usr/bin/docker top 843c6dd27ae7 ^C # docker logs 843c6dd27ae7 ^C # docker ps | grep 843c6dd27ae7 # docker ps -a | grep 843c6dd27ae7 843c6dd27ae7 sles12/pause:1.0.0 "/usr/share/suse-d..." 5 hours ago Created k8s_POD_influxtreon-1527151380-b879p_tick_7aafe27b-5f2e-11e8-8f7c-525400cfa2b7_1 # kill 12732 .... Nothing.... # kill 12731 /sbin/supportconfig: line 551: 12730 Done echo "$CMDLINE" 12731 Terminated | bash >> $LOGFILE 2>&1 Now support config is stuck on : # ps axjf | egrep "PPID|13967" PPID PID PGID SID TTY TPGID STAT UID TIME COMMAND 12419 12427 12427 12427 pts/0 13967 Ss 0 0:00 | \_ -bash 12427 13967 13967 12427 pts/0 13967 S+ 0 0:28 | \_ /bin/bash /sbin/supportconfig 13967 48779 13967 12427 pts/0 13967 S+ 0 0:00 | \_ bash 48779 48780 13967 12427 pts/0 13967 Sl+ 0 0:00 | \_ /usr/bin/docker inspect 843c6dd27ae7 26499 49026 49025 26499 pts/1 49025 S+ 0 0:00 \_ egrep PPID|13967 1 12732 13967 12427 pts/0 13967 Sl+ 0 0:00 /usr/bin/docker top 843c6dd27ae7 I make "^C" on support config and relauch it. Regards St?phane Le Bihan SDE/DSI/IPR/SSD/UNX 90, Boulevard Pasteur - 75015 Paris Web: www.amundi.com Tel: +33 1 76 32 32 08 Tel Unix Team: +33 1 76 32 02 30 @: stephane.lebihan at amundi.com @: sits.unix at amundi.com Visit us on: -----Message d'origine----- De?: Le Bihan St?phane (AMUNDI-ITS) Envoy??: jeudi 24 mai 2018 14:43 ??: Le Bihan St?phane (AMUNDI-ITS); lproven at suse.com; Yoshise, Junichi Cc?: caasp-beta at lists.suse.com Objet?: RE: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? For information another response from another develloper : " Hi, I've created new test cron job and even that generates the Terminating pods: $ kp get pods -n tick NAME READY STATUS RESTARTS AGE data-influxdb-5c7b44ff76-fcf5m 1/1 Running 2 9d grafana-7dc9f4bccc-k6gbc 1/1 Running 3 9d influxtreon-1527164760-64xf9 0/1 Terminating 0 5m influxtreon-1527164940-27565 0/1 Completed 0 2m influxtreon-1527165000-mh27k 0/1 Completed 0 1m influxtreon-1527165060-d8jww 0/1 Completed 0 16s sleeper-1527164640-9njtv 0/1 Terminating 0 7m sleeper-1527164760-xm79v 0/1 Completed 0 5m sleeper-1527164820-ptb64 0/1 Terminating 0 4m sleeper-1527164880-q6f6d 0/1 Completed 0 3m sleeper-1527164940-j2k8f 0/1 Completed 0 2m sleeper-1527165000-bp5vx 0/1 Terminating 0 1m sleeper-1527165060-72b9l 0/1 Completed 0 15s Here's the cron configuraton: --- apiVersion: batch/v1beta1 kind: CronJob metadata: name: sleeper spec: schedule: "*/1 * * * *" concurrencyPolicy: Replace successfulJobsHistoryLimit: 3 failedJobsHistoryLimit: 3 jobTemplate: spec: template: spec: containers: - name: sleeper image: /library/ubuntu:18.04 args: - "/bin/sleep" - "5" restartPolicy: OnFailure imagePullSecrets: - name: regcred Here's the source code for sleep: https://github.com/coreutils/coreutils/blob/master/src/sleep.c I'd say there's definitely other pods that have the same issue. :D" Regards St?phane Le Bihan SDE/DSI/IPR/SSD/UNX 90, Boulevard Pasteur - 75015 Paris Web: www.amundi.com Tel: +33 1 76 32 32 08 Tel Unix Team: +33 1 76 32 02 30 @: stephane.lebihan at amundi.com @: sits.unix at amundi.com Visit us on: -----Message d'origine----- De?: caasp-beta-bounces at lists.suse.com [mailto:caasp-beta-bounces at lists.suse.com] De la part de Le Bihan St?phane (AMUNDI-ITS) Envoy??: jeudi 24 mai 2018 14:35 ??: lproven at suse.com; Yoshise, Junichi Cc?: caasp-beta at lists.suse.com Objet?: Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? Thanks for your response. I launch support_config, but it's stuck at Docker line .... I wait. Memory limit on server is not at limit (big server :D) total used free shared buffers cached Mem: 377 14 363 0 0 9 -/+ buffers/cache: 4 373 Swap: 0 0 0 And for application developer say me : "Influxtreon consumes about 150kB to run" I wait for support_config. Regards, St?phane Le Bihan SDE/DSI/IPR/SSD/UNX 90, Boulevard Pasteur - 75015 Paris Web: www.amundi.com Tel: +33 1 76 32 32 08 Tel Unix Team: +33 1 76 32 02 30 @: stephane.lebihan at amundi.com @: sits.unix at amundi.com Visit us on: -----Message d'origine----- De?: caasp-beta-bounces at lists.suse.com [mailto:caasp-beta-bounces at lists.suse.com] De la part de Liam Proven Envoy??: jeudi 24 mai 2018 12:26 ??: Yoshise, Junichi Cc?: caasp-beta at lists.suse.com Objet?: [Marketing Mail] Re: [caasp-beta] How to deploy CaaSP on EC2? On Thu, 24 May 2018 06:34:27 +0000 "Yoshise, Junichi" wrote: > I?m trying to deploy CaaSP 3.0 beta2 on AWS EC2. Since AMI is not > available, I?ve converted qcow2 or vmdk file then tried to import to > EC2, but it didn?t work. Is there any way to deploy CaaSP on EC2? As I understand it, currently, for public cloud use, you should be looking at CaaSP 2.1, not 3.0 -- and I believe it has not yet reached beta phase. -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, K?i??kova 148/34, 186-00 Praha 8 - Karl?n, Czechia Email: lproven at suse.com - Office telephone: +420 284 241 084 _______________________________________________ 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 stephane.lebihan at amundi.com Thu May 24 09:09:47 2018 From: stephane.lebihan at amundi.com (=?utf-8?B?TGUgQmloYW4gU3TDqXBoYW5lIChBTVVOREktSVRTKQ==?=) Date: Thu, 24 May 2018 15:09:47 +0000 Subject: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? References: <20180524122543.4a56aea7.lproven@suse.com> Message-ID: Oh sorry, I made a mistake about thread :s Regards, St?phane Le Bihan SDE/DSI/IPR/SSD/UNX 90, Boulevard Pasteur - 75015 Paris Web: www.amundi.com Tel: +33 1 76 32 32 08 Tel Unix Team: +33 1 76 32 02 30 @: stephane.lebihan at amundi.com @: sits.unix at amundi.com Visit us on: -----Message d'origine----- De?: Le Bihan St?phane (AMUNDI-ITS) Envoy??: jeudi 24 mai 2018 15:40 ??: 'lproven at suse.com'; 'Yoshise, Junichi' Cc?: 'caasp-beta at lists.suse.com' Objet?: RE: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? Log docker : 2018-05-24T15:31:45.955719+02:00 dl360o-101 dockerd[2055]: time="2018-05-24T15:31:45.954756307+02:00" level=warning msg="container kill failed because of 'container not found' or 'no such process': Cannot kill container f87327727cc5d4628082cb4d0c09503f82ddcbd6d8055db63cf8020c10f6cb11: rpc error: code = Unknown desc = containerd: container not found" 2018-05-24T15:31:45.955852+02:00 dl360o-101 dockerd[2055]: time="2018-05-24T15:31:45.954770487+02:00" level=warning msg="container kill failed because of 'container not found' or 'no such process': Cannot kill container bbb9a2b7215fdd144391d198e6a3c3a11bc9cc035d36701a21d3bb92a3799200: rpc error: code = Unknown desc = containerd: container not found" 2018-05-24T15:31:45.955985+02:00 dl360o-101 dockerd[2055]: time="2018-05-24T15:31:45.954773986+02:00" level=warning msg="container kill failed because of 'container not found' or 'no such process': Cannot kill container d4e3cad021df83cd9ba3bcb04d8c9cc0bd54a4f85c6935bec65fead9e2fa9840: rpc error: code = Unknown desc = containerd: container not found" Support config is stuck : root at dl360o-101:/root$ supportconfig ============================================================================= Support Utilities - Supportconfig Script Version: 3.0-105 Script Date: 2018 01 05 Detailed system information and logs are collected and organized in a manner that helps reduce service request resolution times. Private system information can be disclosed when using this tool. If this is a concern, please prune private data from the log files. Several startup options are available to exclude more sensitive information. Supportconfig data is used only for diagnostic purposes and is considered confidential information. See http://www.novell.com/company/legal/privacy/ ============================================================================= Gathering system information Data Directory: /var/log/nts_dl360o-101_180524_1401 Basic Server Health Check... Done RPM Database... Done Basic Environment... Done System Modules... Done Memory Details... Done Disk I/O... Done B-tree File System... Done YaST Files... Done File System List... Skipped Auditing... Done Crash Info... Done NTP... Done PROC... Done Boot Files... Done SLERT... Skipped Updates... Done SMT... Skipped HA Cluster... Skipped OCFS2... Skipped DRBD... Skipped HAPROXY... Skipped PAM... Done LDAP... Skipped System Security Services... Skipped CIMOM... Skipped Open Files... Done Environment... Done Command History... Excluded ETC... Done SYSCONFIG... Done SYSFS... Done SystemD... Done Docker... # ps axjf | egrep "PPID|13967" PPID PID PGID SID TTY TPGID STAT UID TIME COMMAND 12419 12427 12427 12427 pts/0 13967 Ss 0 0:00 | \_ -bash 12427 13967 13967 12427 pts/0 13967 S+ 0 0:28 | \_ /bin/bash /sbin/supportconfig 13967 12731 13967 12427 pts/0 13967 S+ 0 0:00 | \_ bash 12731 12732 13967 12427 pts/0 13967 Sl+ 0 0:00 | \_ /usr/bin/docker top 843c6dd27ae7 26499 47700 47699 26499 pts/1 47699 S+ 0 0:00 \_ egrep PPID|13967 # /usr/bin/docker top 843c6dd27ae7 ^C # docker logs 843c6dd27ae7 ^C # docker ps | grep 843c6dd27ae7 # docker ps -a | grep 843c6dd27ae7 843c6dd27ae7 sles12/pause:1.0.0 "/usr/share/suse-d..." 5 hours ago Created k8s_POD_influxtreon-1527151380-b879p_tick_7aafe27b-5f2e-11e8-8f7c-525400cfa2b7_1 # kill 12732 .... Nothing.... # kill 12731 /sbin/supportconfig: line 551: 12730 Done echo "$CMDLINE" 12731 Terminated | bash >> $LOGFILE 2>&1 Now support config is stuck on : # ps axjf | egrep "PPID|13967" PPID PID PGID SID TTY TPGID STAT UID TIME COMMAND 12419 12427 12427 12427 pts/0 13967 Ss 0 0:00 | \_ -bash 12427 13967 13967 12427 pts/0 13967 S+ 0 0:28 | \_ /bin/bash /sbin/supportconfig 13967 48779 13967 12427 pts/0 13967 S+ 0 0:00 | \_ bash 48779 48780 13967 12427 pts/0 13967 Sl+ 0 0:00 | \_ /usr/bin/docker inspect 843c6dd27ae7 26499 49026 49025 26499 pts/1 49025 S+ 0 0:00 \_ egrep PPID|13967 1 12732 13967 12427 pts/0 13967 Sl+ 0 0:00 /usr/bin/docker top 843c6dd27ae7 I make "^C" on support config and relauch it. Regards St?phane Le Bihan SDE/DSI/IPR/SSD/UNX 90, Boulevard Pasteur - 75015 Paris Web: www.amundi.com Tel: +33 1 76 32 32 08 Tel Unix Team: +33 1 76 32 02 30 @: stephane.lebihan at amundi.com @: sits.unix at amundi.com Visit us on: -----Message d'origine----- De?: Le Bihan St?phane (AMUNDI-ITS) Envoy??: jeudi 24 mai 2018 14:43 ??: Le Bihan St?phane (AMUNDI-ITS); lproven at suse.com; Yoshise, Junichi Cc?: caasp-beta at lists.suse.com Objet?: RE: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? For information another response from another develloper : " Hi, I've created new test cron job and even that generates the Terminating pods: $ kp get pods -n tick NAME READY STATUS RESTARTS AGE data-influxdb-5c7b44ff76-fcf5m 1/1 Running 2 9d grafana-7dc9f4bccc-k6gbc 1/1 Running 3 9d influxtreon-1527164760-64xf9 0/1 Terminating 0 5m influxtreon-1527164940-27565 0/1 Completed 0 2m influxtreon-1527165000-mh27k 0/1 Completed 0 1m influxtreon-1527165060-d8jww 0/1 Completed 0 16s sleeper-1527164640-9njtv 0/1 Terminating 0 7m sleeper-1527164760-xm79v 0/1 Completed 0 5m sleeper-1527164820-ptb64 0/1 Terminating 0 4m sleeper-1527164880-q6f6d 0/1 Completed 0 3m sleeper-1527164940-j2k8f 0/1 Completed 0 2m sleeper-1527165000-bp5vx 0/1 Terminating 0 1m sleeper-1527165060-72b9l 0/1 Completed 0 15s Here's the cron configuraton: --- apiVersion: batch/v1beta1 kind: CronJob metadata: name: sleeper spec: schedule: "*/1 * * * *" concurrencyPolicy: Replace successfulJobsHistoryLimit: 3 failedJobsHistoryLimit: 3 jobTemplate: spec: template: spec: containers: - name: sleeper image: /library/ubuntu:18.04 args: - "/bin/sleep" - "5" restartPolicy: OnFailure imagePullSecrets: - name: regcred Here's the source code for sleep: https://github.com/coreutils/coreutils/blob/master/src/sleep.c I'd say there's definitely other pods that have the same issue. :D" Regards St?phane Le Bihan SDE/DSI/IPR/SSD/UNX 90, Boulevard Pasteur - 75015 Paris Web: www.amundi.com Tel: +33 1 76 32 32 08 Tel Unix Team: +33 1 76 32 02 30 @: stephane.lebihan at amundi.com @: sits.unix at amundi.com Visit us on: -----Message d'origine----- De?: caasp-beta-bounces at lists.suse.com [mailto:caasp-beta-bounces at lists.suse.com] De la part de Le Bihan St?phane (AMUNDI-ITS) Envoy??: jeudi 24 mai 2018 14:35 ??: lproven at suse.com; Yoshise, Junichi Cc?: caasp-beta at lists.suse.com Objet?: Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? Thanks for your response. I launch support_config, but it's stuck at Docker line .... I wait. Memory limit on server is not at limit (big server :D) total used free shared buffers cached Mem: 377 14 363 0 0 9 -/+ buffers/cache: 4 373 Swap: 0 0 0 And for application developer say me : "Influxtreon consumes about 150kB to run" I wait for support_config. Regards, St?phane Le Bihan SDE/DSI/IPR/SSD/UNX 90, Boulevard Pasteur - 75015 Paris Web: www.amundi.com Tel: +33 1 76 32 32 08 Tel Unix Team: +33 1 76 32 02 30 @: stephane.lebihan at amundi.com @: sits.unix at amundi.com Visit us on: -----Message d'origine----- De?: caasp-beta-bounces at lists.suse.com [mailto:caasp-beta-bounces at lists.suse.com] De la part de Liam Proven Envoy??: jeudi 24 mai 2018 12:26 ??: Yoshise, Junichi Cc?: caasp-beta at lists.suse.com Objet?: [Marketing Mail] Re: [caasp-beta] How to deploy CaaSP on EC2? On Thu, 24 May 2018 06:34:27 +0000 "Yoshise, Junichi" wrote: > I?m trying to deploy CaaSP 3.0 beta2 on AWS EC2. Since AMI is not > available, I?ve converted qcow2 or vmdk file then tried to import to > EC2, but it didn?t work. Is there any way to deploy CaaSP on EC2? As I understand it, currently, for public cloud use, you should be looking at CaaSP 2.1, not 3.0 -- and I believe it has not yet reached beta phase. -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, K?i??kova 148/34, 186-00 Praha 8 - Karl?n, Czechia Email: lproven at suse.com - Office telephone: +420 284 241 084 _______________________________________________ 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 stephane.lebihan at amundi.com Thu May 24 09:25:17 2018 From: stephane.lebihan at amundi.com (=?utf-8?B?TGUgQmloYW4gU3TDqXBoYW5lIChBTVVOREktSVRTKQ==?=) Date: Thu, 24 May 2018 15:25:17 +0000 Subject: [caasp-beta] Strange behaviour docker CAASP v3 beta 1 In-Reply-To: <20180524120657.chzuzutvc5nxnxug@nebuchadnezzar> References: <20180524120657.chzuzutvc5nxnxug@nebuchadnezzar> Message-ID: Hi Valentin, Sorry i made mistake on thread.... :s Thanks for your response. I join to mail. One with mistake thread on mailing beta. Who I explain support config is stuck on Docker test. One with thread with other user of CAASP plateform here. I copy and modified supportconfig for don't make test "docker top" or docker log because supportconfig stuck on their command. Here diff on two file : dl360o-101:~ # diff supportconfig /sbin/supportconfig 2826,2831c2826,2831 < #for i in $(docker ps -a 2>/dev/null | grep -v "COMMAND" | awk '{print $1}'); < #do < # log_cmd $OF "docker top $i" < # log_cmd $OF "docker logs $i" < # log_cmd $OF "docker inspect $i" < #done --- > for i in $(docker ps -a 2>/dev/null | grep -v "COMMAND" | awk '{print $1}'); > do > log_cmd $OF "docker top $i" > log_cmd $OF "docker logs $i" > log_cmd $OF "docker inspect $i" > done Example of stuck : dl360o-101:~ # docker ps -a | grep 843c6dd27ae7 843c6dd27ae7 sles12/pause:1.0.0 "/usr/share/suse-d..." 7 hours ago Created k8s_POD_influxtreon-1527151380-b879p_tick_7aafe27b-5f2e-11e8-8f7c-525400cfa2b7_1 dl360o-101:~ # /usr/bin/docker logs 843c6dd27ae7 (Nothing, I stop with ^C) dl360o-101:~ # /usr/bin/docker inspect 843c6dd27ae7 ^C I can't open bug on SCC for Beta program, just for SLES12 Entreprise Server and I don't find how open issue in bugzilla. How or where I can put supportconfig for you ? Regards, St?phane Le Bihan SDE/DSI/IPR/SSD/UNX 90, Boulevard Pasteur - 75015 Paris Web: www.amundi.com Tel: +33 1 76 32 32 08 Tel Unix Team: +33 1 76 32 02 30 @: stephane.lebihan at amundi.com @: sits.unix at amundi.com Visit us on: -----Message d'origine----- De?: Valentin Rothberg [mailto:vrothberg at suse.com] Envoy??: jeudi 24 mai 2018 14:07 ??: Le Bihan St?phane (AMUNDI-ITS) Cc?: caasp-beta at lists.suse.com Objet?: Re: [caasp-beta] Strange behaviour docker CAASP v3 beta 1 Hi, thanks a lot for reaching out to us. On May/24/18 10:04, Le Bihan St?phane (AMUNDI-ITS) wrote: [...] > Error response from daemon: rpc error: code = Unknown desc = > containerd: container not found > > I don't understand why container is not destroyed. Have you any idea ? Similar issues usually happen when processes inside the containers are not properly shutdown (e.g., when the system runs out of memory or when a process has forcefully been killed for any other reason). In addition to steps mentioned below, may I ask how much RAM the node you extracted the logs above from has? This is hard to say without looking at the logs. If possible, could you provide a supportconfig for us to have a first glimpse at your issue? Feel free to open a bug or upload the logs somewhere reachable for us as described here [1]. Kind regards, Valentin [1] https://www.suse.com/c/free_tools/supportconfig-linux/ -------------- next part -------------- An embedded message was scrubbed... From: =?utf-8?B?TGUgQmloYW4gU3TDqXBoYW5lIChBTVVOREktSVRTKQ==?= Subject: Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? Date: Thu, 24 May 2018 13:39:45 +0000 Size: 21724 URL: -------------- next part -------------- An embedded message was scrubbed... From: "Chesnoy Bernard (AMUNDI-ITS)" Subject: RE: [caasp-beta] Strange behaviour docker CAASP v3 beta 1 Date: Thu, 24 May 2018 13:37:38 +0000 Size: 20968 URL: From paul.gonin at suse.com Thu May 24 09:32:37 2018 From: paul.gonin at suse.com (Paul Gonin) Date: Thu, 24 May 2018 17:32:37 +0200 Subject: [caasp-beta] How to deploy CaaSP on EC2? In-Reply-To: References: <20180524122543.4a56aea7.lproven@suse.com> Message-ID: Hi, Look for suse-caasp in Community AMIs suse-caasp-2-1-admin-byos-v20180516-hvm-ssd-x86_64 - ami-f171c08c suse-caasp-2-1-cluster-byos-v20180516-hvm-ssd-x86_64 - ami-de71c0a3 rgds Paul Gonin Le jeudi 24 mai 2018 ? 12:58 +0000, Yoshise, Junichi a ?crit : > Even for 2.1, I can't find any AMI nor document. Is it really ready? > > > -----Original Message----- > From: Liam Proven > Sent: Thursday, May 24, 2018 7:26 PM > To: Yoshise, Junichi > Cc: caasp-beta at lists.suse.com > Subject: Re: [caasp-beta] How to deploy CaaSP on EC2? > > On Thu, 24 May 2018 06:34:27 +0000 > "Yoshise, Junichi" wrote: > > > I?m trying to deploy CaaSP 3.0 beta2 on AWS EC2. Since AMI is not > > available, I?ve converted qcow2 or vmdk file then tried to import > > to > > EC2, but it didn?t work. Is there any way to deploy CaaSP on EC2? > > As I understand it, currently, for public cloud use, you should be > looking at CaaSP 2.1, not 3.0 -- and I believe it has not yet reached > beta phase. > > -- > Liam Proven - Technical Writer, SUSE Linux s.r.o. > Corso II, K?i??kova 148/34, 186-00 Praha 8 - Karl?n, Czechia > Email: lproven at suse.com - Office telephone: +420 284 241 084 > > > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/caasp-beta From lcavajani at suse.com Thu May 24 09:45:49 2018 From: lcavajani at suse.com (Ludovic Cavajani) Date: Thu, 24 May 2018 17:45:49 +0200 Subject: [caasp-beta] How to deploy CaaSP on EC2? In-Reply-To: References: <20180524122543.4a56aea7.lproven@suse.com> Message-ID: <9f7f9a78-2f74-431c-9bc0-2fa73b73140a@suse.com> Hi, The AMIs are available in the Community AMIs, you can find them by searching "suse-caasp-2-1". There is currently no public documentation but it will be available soon so you must be aware that the deployment is ***different*** than on-premises. In the case of public clouds, the bootstrapping of the cluster nodes (masters/workers) is done through Velum leveraging the underlying cloud api. Here is an totally ***unsupported******* quick start guide to deploy a cluster***usable only from inside the tenant***. Deploying a cluster accessible from outside require ***a lot more security considerations***. 1. An IAM role with the following policies attached to it must exit. * AWSMarketplaceFullAccess * AmazonRDSFullAccess * AmazonEC2FullAccess * AWSLambdaFullAccess * AmazonS3FullAccess * ReadOnlyAccess * AmazonEC2ContainerServiceFullAccess * AmazonVPCFullAccess * AmazonElasticFileSystemFullAccess * AWSMarketplaceManageSubscriptions 2. Launch a virtual instance of an admin node * Search Community AMIs -> suse-caasp-2-1-*admin* * Select and choose an instance type like t2.large * Fill in the common fields (Subnet, VPC etc), it is very important to select the ***iam role*** otherwise it is not possible to create a cluster * Select SSH keypair * Launch the instance 3. SSH to the admin node with the user 'ec2-user', run the script /usr/sbin/caasp-admin-setup as root and answer the questions. * Would you like to use your own certificate from a known (public or self signed) Certificate Authority? * Email address for login to Admin Dashboard? * Password for login to Admin Dashboard * Would you like to register the system with the SUSE Customer Center (SCC) to receive updates? (e-mail and registration code required) (Y/n) 4. Edit the security group attached to the admin node and allow inbound connection on port 443. Only then you can access to Velum with https://admin-node-public-dns For testing, you can use the public DNS associated with your instance, something like "ec2-public-ip.eu-west-1.compute.amazonaws.com" 5. In the first Velum page, it is the same as usual if you're familiar with the on-premises. 6. In the second Velum page, here is the selection of the flavor for the nodes and the number of wanted nodes. 7. The nodes will be created and appear in the cluster configuration where there is the selection of the role for each node. ??? ? External kubernetes (use internal DNS): ip-private.eu-west-1.compute.internal External dashboard FQDN (use public DNS): ec2-public.eu-west-1.compute.amazonaws.com 8. Start the cluster bootstrap 9. Once bootstrapped, you'll get the info on how to get your kubeconfig? with caasp-cli from the admin node and start using the cluster from there. $ caasp-cli login -s https://ip-private.eu-west-1.compute.internal:6443 -u USER -p PASSWORD Enjoy, On 05/24/2018 05:32 PM, Paul Gonin wrote: > Hi, > > Look for suse-caasp in Community AMIs > suse-caasp-2-1-admin-byos-v20180516-hvm-ssd-x86_64 - ami-f171c08c > suse-caasp-2-1-cluster-byos-v20180516-hvm-ssd-x86_64 - ami-de71c0a3 > > rgds > Paul Gonin > > > Le jeudi 24 mai 2018 ? 12:58 +0000, Yoshise, Junichi a ?crit : >> Even for 2.1, I can't find any AMI nor document. Is it really ready? >> >> >> -----Original Message----- >> From: Liam Proven >> Sent: Thursday, May 24, 2018 7:26 PM >> To: Yoshise, Junichi >> Cc: caasp-beta at lists.suse.com >> Subject: Re: [caasp-beta] How to deploy CaaSP on EC2? >> >> On Thu, 24 May 2018 06:34:27 +0000 >> "Yoshise, Junichi" wrote: >> >>> I?m trying to deploy CaaSP 3.0 beta2 on AWS EC2. Since AMI is not >>> available, I?ve converted qcow2 or vmdk file then tried to import >>> to >>> EC2, but it didn?t work. Is there any way to deploy CaaSP on EC2? >> As I understand it, currently, for public cloud use, you should be >> looking at CaaSP 2.1, not 3.0 -- and I believe it has not yet reached >> beta phase. >> >> -- >> Liam Proven - Technical Writer, SUSE Linux s.r.o. >> Corso II, K?i??kova 148/34, 186-00 Praha 8 - Karl?n, Czechia >> Email: lproven at suse.com - Office telephone: +420 284 241 084 >> >> >> _______________________________________________ >> 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 -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From junichi.yoshise at hpe.com Thu May 24 11:12:05 2018 From: junichi.yoshise at hpe.com (Yoshise, Junichi) Date: Thu, 24 May 2018 17:12:05 +0000 Subject: [caasp-beta] How to deploy CaaSP on EC2? In-Reply-To: <9f7f9a78-2f74-431c-9bc0-2fa73b73140a@suse.com> References: <20180524122543.4a56aea7.lproven@suse.com> <9f7f9a78-2f74-431c-9bc0-2fa73b73140a@suse.com> Message-ID: Ludovic-san, Paul-san, Thank you for the information! I will try 2.1 AMI first, then 3.0 when it's available. Best Regards, Junichi -----Original Message----- From: Ludovic Cavajani Sent: Friday, May 25, 2018 12:46 AM To: Paul Gonin ; Yoshise, Junichi ; Proven, Liam Cc: caasp-beta at lists.suse.com Subject: Re: [caasp-beta] How to deploy CaaSP on EC2? Hi, The AMIs are available in the Community AMIs, you can find them by searching "suse-caasp-2-1". There is currently no public documentation but it will be available soon so you must be aware that the deployment is ***different*** than on-premises. In the case of public clouds, the bootstrapping of the cluster nodes (masters/workers) is done through Velum leveraging the underlying cloud api. Here is an totally ***unsupported******* quick start guide to deploy a cluster***usable only from inside the tenant***. Deploying a cluster accessible from outside require ***a lot more security considerations***. 1. An IAM role with the following policies attached to it must exit. * AWSMarketplaceFullAccess * AmazonRDSFullAccess * AmazonEC2FullAccess * AWSLambdaFullAccess * AmazonS3FullAccess * ReadOnlyAccess * AmazonEC2ContainerServiceFullAccess * AmazonVPCFullAccess * AmazonElasticFileSystemFullAccess * AWSMarketplaceManageSubscriptions 2. Launch a virtual instance of an admin node * Search Community AMIs -> suse-caasp-2-1-*admin* * Select and choose an instance type like t2.large * Fill in the common fields (Subnet, VPC etc), it is very important to select the ***iam role*** otherwise it is not possible to create a cluster * Select SSH keypair * Launch the instance 3. SSH to the admin node with the user 'ec2-user', run the script /usr/sbin/caasp-admin-setup as root and answer the questions. * Would you like to use your own certificate from a known (public or self signed) Certificate Authority? * Email address for login to Admin Dashboard? * Password for login to Admin Dashboard * Would you like to register the system with the SUSE Customer Center (SCC) to receive updates? (e-mail and registration code required) (Y/n) 4. Edit the security group attached to the admin node and allow inbound connection on port 443. Only then you can access to Velum with https://admin-node-public-dns For testing, you can use the public DNS associated with your instance, something like "ec2-public-ip.eu-west-1.compute.amazonaws.com" 5. In the first Velum page, it is the same as usual if you're familiar with the on-premises. 6. In the second Velum page, here is the selection of the flavor for the nodes and the number of wanted nodes. 7. The nodes will be created and appear in the cluster configuration where there is the selection of the role for each node. ??? ? External kubernetes (use internal DNS): ip-private.eu-west-1.compute.internal External dashboard FQDN (use public DNS): ec2-public.eu-west-1.compute.amazonaws.com 8. Start the cluster bootstrap 9. Once bootstrapped, you'll get the info on how to get your kubeconfig with caasp-cli from the admin node and start using the cluster from there. $ caasp-cli login -s https://ip-private.eu-west-1.compute.internal:6443 -u USER -p PASSWORD Enjoy, On 05/24/2018 05:32 PM, Paul Gonin wrote: > Hi, > > Look for suse-caasp in Community AMIs > suse-caasp-2-1-admin-byos-v20180516-hvm-ssd-x86_64 - ami-f171c08c > suse-caasp-2-1-cluster-byos-v20180516-hvm-ssd-x86_64 - ami-de71c0a3 > > rgds > Paul Gonin > > > Le jeudi 24 mai 2018 ? 12:58 +0000, Yoshise, Junichi a ?crit : >> Even for 2.1, I can't find any AMI nor document. Is it really ready? >> >> >> -----Original Message----- >> From: Liam Proven >> Sent: Thursday, May 24, 2018 7:26 PM >> To: Yoshise, Junichi >> Cc: caasp-beta at lists.suse.com >> Subject: Re: [caasp-beta] How to deploy CaaSP on EC2? >> >> On Thu, 24 May 2018 06:34:27 +0000 >> "Yoshise, Junichi" wrote: >> >>> I?m trying to deploy CaaSP 3.0 beta2 on AWS EC2. Since AMI is not >>> available, I?ve converted qcow2 or vmdk file then tried to import to >>> EC2, but it didn?t work. Is there any way to deploy CaaSP on EC2? >> As I understand it, currently, for public cloud use, you should be >> looking at CaaSP 2.1, not 3.0 -- and I believe it has not yet reached >> beta phase. >> >> -- >> Liam Proven - Technical Writer, SUSE Linux s.r.o. >> Corso II, K?i??kova 148/34, 186-00 Praha 8 - Karl?n, Czechia >> Email: lproven at suse.com - Office telephone: +420 284 241 084 >> >> >> _______________________________________________ >> 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 fcastelli at suse.com Fri May 25 02:51:37 2018 From: fcastelli at suse.com (Flavio Castelli) Date: Fri, 25 May 2018 10:51:37 +0200 Subject: [caasp-beta] Litte question ? In-Reply-To: References: Message-ID: <23296d4a-0045-8d40-f23e-f18b02e536d0@suse.com> Starting with v3 we introduced support for Docker registry mirrors. The problem it solves: * You are deploying container images from a remote registry (eg: Docker Hub, gcr, Quay, corporate private registry from a different geo,...). * You don't want all your nodes to waste time and bandwidth pulling the same image over and over again. The only solution available so far: * Setup a local registry * Pull the images from the remote registry, retag them, push them to the local registry: "docker pull redis; docker tag redis registry.local/redis; docker push registry.local/redis" * Change all the scripts, Dockerfile(s), Kubernetes manifests to reference "registry.local/redis" instead of "redis". What is now possible: * Setup a local registry, configure that to act as a mirror of Docker Hub/gcr/Quay/... (we will provide documentation about that). * Go to the SUSE CaaS Platform UI / settings / registries. * Make SUSE CaaS Platform aware that hub-mirror.local is a mirror of the Docker Hub(just using the Docker Hub as an example here). * Deploy your images without making changes to scripts/kubernetes manifests/... What happens behind the scene: * The docker/daemon.json is configured by us to make the docker open-source engine aware of the hub-mirror.local <-> Docker Hub relationship. * Images hosted on the Docker Hub will be pulled from the local mirror. * The local mirror acts as a pull through cache: images are pulled only when they are not yet cached or a stale. * The nodes only reach the upstream registry (the Docker Hub in this case) if the local registry mirror is unreachable. This can be used also to implement air-gapped deployments of SUSE CaaS Platform. We will provide documentation about that too. This can be useful if your company has a central registry and wants to have different mirrors of it closer to branch offices (each region/office can have its own registry mirror). How is that done: * The docker distribution daemon (aka docker registry) has always been capable of mirroring upstream registries. * The docker open-source engine has a long standing limitation: it can be configured to pull images from a local mirror, but that can only be a mirror of the Docker Hub. It won't work with local mirrors of registries like gcr, Quay or your corporate registry. We provided a patch that extends the docker open-source engine to address this limitation [1]. The patch is being discussed upstream, it will be certainly merged into the docker open-source engine. In the meantime the docker open-source engine shipped with SUSE CaaS Platform already has this patch applied. As for the configuration you have seen into the docker daemon.json. This is a spurious entry for the SUSE registry. This line doesn't have any impact on the behaviour of the docker open-source engine because no local mirror of the SUSE registry has been configured. BTW, the SUSE registry is already being used to distribute container images of our products like the SUSE Cloud Application Platform. To prevent further confusion: we are NOT preventing pulls from the Docker Hub or other registries; eg: "docker pull redis" will keep pulling the Redis image from the dockerhub unless you configure a local mirror of it. I hope that helps. Cheers Flavio [1] https://github.com/moby/moby/pull/34319 On 05/24/2018 11:33 AM, Le Bihan St?phane (AMUNDI-ITS) wrote: > Hi all, > > ? > > ????????? I see this option in /etc/docker/daemon.json : > > "registries": [ > > ??? { > > ????? "Prefix": "https://registry.suse.com" > > ??? } > > ? ], > > ? > > But I don?t find who is it ? Can you explain me ? > > ? > > ????????? I install cluster with CAASP v3 beta 1, all server as register > in SMT, and registration code for beta is registered on SCC. > > But it?s seems patch in Suse CAASP v3 beta 2 DVD is not available on SMT. > > For update nodes of cluster, I must use DVD on it ? > > ? > > Regards, > > ? > > cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5 > * > **St?phane Le Bihan* > > SDE/DSI/IPR/SSD/UNX > > 90, Boulevard Pasteur - 75015 Paris > > *Web: www.amundi.com* > > Tel: +33 1 76 32 32 08 > > Tel Unix Team: +33 1 76 32 02 30 > > @: stephane.lebihan at amundi.com > > @: sits.unix at amundi.com > > ? > > /Visit us on: / > > /?/ > > twitter ? linkedin > ??facebook > ??Sans titre-1 > ??youtube > // > > ? > > > > _______________________________________________ > caasp-beta mailing list > caasp-beta at lists.suse.com > http://lists.suse.com/mailman/listinfo/caasp-beta > From vrothberg at suse.com Fri May 25 03:15:39 2018 From: vrothberg at suse.com (Valentin Rothberg) Date: Fri, 25 May 2018 11:15:39 +0200 Subject: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? In-Reply-To: References: <20180524122543.4a56aea7.lproven@suse.com> Message-ID: <20180525091539.2weqb5oyk5jibzsp@nebuchadnezzar> Hi, given the issue is reproducible in your environment, could you open a bug on bugzilla.suse.com and upload the supportconfig there? If supportconfig hangs, we can initially have a look at the Docker logs (e.g., `journalctl -u docker`) and start from there. Thanks a lot and kind regards, Valentin On May/24/18 12:42, Le Bihan St?phane (AMUNDI-ITS) wrote: > For information another response from another develloper : > > " Hi, > > I've created new test cron job and even that generates the Terminating pods: > > $ kp get pods -n tick > NAME READY STATUS RESTARTS AGE > data-influxdb-5c7b44ff76-fcf5m 1/1 Running 2 9d > grafana-7dc9f4bccc-k6gbc 1/1 Running 3 9d > influxtreon-1527164760-64xf9 0/1 Terminating 0 5m > influxtreon-1527164940-27565 0/1 Completed 0 2m > influxtreon-1527165000-mh27k 0/1 Completed 0 1m > influxtreon-1527165060-d8jww 0/1 Completed 0 16s > sleeper-1527164640-9njtv 0/1 Terminating 0 7m > sleeper-1527164760-xm79v 0/1 Completed 0 5m > sleeper-1527164820-ptb64 0/1 Terminating 0 4m > sleeper-1527164880-q6f6d 0/1 Completed 0 3m > sleeper-1527164940-j2k8f 0/1 Completed 0 2m > sleeper-1527165000-bp5vx 0/1 Terminating 0 1m > sleeper-1527165060-72b9l 0/1 Completed 0 15s > > Here's the cron configuraton: > > --- > apiVersion: batch/v1beta1 > kind: CronJob > metadata: > name: sleeper > spec: > schedule: "*/1 * * * *" > concurrencyPolicy: Replace > successfulJobsHistoryLimit: 3 > failedJobsHistoryLimit: 3 > jobTemplate: > spec: > template: > spec: > containers: > - name: sleeper > image: /library/ubuntu:18.04 > args: > - "/bin/sleep" > - "5" > restartPolicy: OnFailure > imagePullSecrets: > - name: regcred > > Here's the source code for sleep: > https://github.com/coreutils/coreutils/blob/master/src/sleep.c > > I'd say there's definitely other pods that have the same issue. :D" > > Regards > > St?phane Le Bihan > SDE/DSI/IPR/SSD/UNX > 90, Boulevard Pasteur - 75015 Paris > Web: www.amundi.com > Tel: +33 1 76 32 32 08 > Tel Unix Team: +33 1 76 32 02 30 > @: stephane.lebihan at amundi.com > @: sits.unix at amundi.com > > Visit us on: > > > > > -----Message d'origine----- > De?: caasp-beta-bounces at lists.suse.com [mailto:caasp-beta-bounces at lists.suse.com] De la part de Le Bihan St?phane (AMUNDI-ITS) > Envoy??: jeudi 24 mai 2018 14:35 > ??: lproven at suse.com; Yoshise, Junichi > Cc?: caasp-beta at lists.suse.com > Objet?: Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? > > Thanks for your response. > > I launch support_config, but it's stuck at Docker line .... > I wait. > > Memory limit on server is not at limit (big server :D) > > total used free shared buffers cached > Mem: 377 14 363 0 0 9 > -/+ buffers/cache: 4 373 > Swap: 0 0 0 > > And for application developer say me : > "Influxtreon consumes about 150kB to run" > > I wait for support_config. > > Regards, > > > St?phane Le Bihan > SDE/DSI/IPR/SSD/UNX > 90, Boulevard Pasteur - 75015 Paris > Web: www.amundi.com > Tel: +33 1 76 32 32 08 > Tel Unix Team: +33 1 76 32 02 30 > @: stephane.lebihan at amundi.com > @: sits.unix at amundi.com > > Visit us on: > > > > > -----Message d'origine----- > De?: caasp-beta-bounces at lists.suse.com [mailto:caasp-beta-bounces at lists.suse.com] De la part de Liam Proven > Envoy??: jeudi 24 mai 2018 12:26 > ??: Yoshise, Junichi > Cc?: caasp-beta at lists.suse.com > Objet?: [Marketing Mail] Re: [caasp-beta] How to deploy CaaSP on EC2? > > On Thu, 24 May 2018 06:34:27 +0000 > "Yoshise, Junichi" wrote: > > > I?m trying to deploy CaaSP 3.0 beta2 on AWS EC2. Since AMI is not > > available, I?ve converted qcow2 or vmdk file then tried to import to > > EC2, but it didn?t work. Is there any way to deploy CaaSP on EC2? > > As I understand it, currently, for public cloud use, you should be > looking at CaaSP 2.1, not 3.0 -- and I believe it has not yet reached > beta phase. > > -- > Liam Proven - Technical Writer, SUSE Linux s.r.o. > Corso II, K?i??kova 148/34, 186-00 Praha 8 - Karl?n, Czechia > Email: lproven at suse.com - Office telephone: +420 284 241 084 > > > _______________________________________________ > 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 -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: not available URL: From stephane.lebihan at amundi.com Fri May 25 04:05:55 2018 From: stephane.lebihan at amundi.com (=?utf-8?B?TGUgQmloYW4gU3TDqXBoYW5lIChBTVVOREktSVRTKQ==?=) Date: Fri, 25 May 2018 10:05:55 +0000 Subject: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? In-Reply-To: <20180525091539.2weqb5oyk5jibzsp@nebuchadnezzar> References: <20180524122543.4a56aea7.lproven@suse.com> <20180525091539.2weqb5oyk5jibzsp@nebuchadnezzar> Message-ID: Hi Valentin, I'm not familar with bugzilla and url " https://www.suse.com/betaprogram/beta-guideline.html#bugzilla" return "Page not found" ... Regards, St?phane Le Bihan SDE/DSI/IPR/SSD/UNX 90, Boulevard Pasteur - 75015 Paris Web: www.amundi.com Tel: +33 1 76 32 32 08 Tel Unix Team: +33 1 76 32 02 30 @: stephane.lebihan at amundi.com @: sits.unix at amundi.com Visit us on: -----Message d'origine----- De?: Valentin Rothberg [mailto:vrothberg at suse.com] Envoy??: vendredi 25 mai 2018 11:16 ??: Le Bihan St?phane (AMUNDI-ITS) Cc?: Junichi Yoshise; Liam Proven; vrothberg at suse.de; caasp-beta at lists.suse.com Objet?: Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? Hi, given the issue is reproducible in your environment, could you open a bug on bugzilla.suse.com and upload the supportconfig there? If supportconfig hangs, we can initially have a look at the Docker logs (e.g., `journalctl -u docker`) and start from there. Thanks a lot and kind regards, Valentin On May/24/18 12:42, Le Bihan St?phane (AMUNDI-ITS) wrote: > For information another response from another develloper : > > " Hi, > > I've created new test cron job and even that generates the Terminating pods: > > $ kp get pods -n tick > NAME READY STATUS RESTARTS AGE > data-influxdb-5c7b44ff76-fcf5m 1/1 Running 2 9d > grafana-7dc9f4bccc-k6gbc 1/1 Running 3 9d > influxtreon-1527164760-64xf9 0/1 Terminating 0 5m > influxtreon-1527164940-27565 0/1 Completed 0 2m > influxtreon-1527165000-mh27k 0/1 Completed 0 1m > influxtreon-1527165060-d8jww 0/1 Completed 0 16s > sleeper-1527164640-9njtv 0/1 Terminating 0 7m > sleeper-1527164760-xm79v 0/1 Completed 0 5m > sleeper-1527164820-ptb64 0/1 Terminating 0 4m > sleeper-1527164880-q6f6d 0/1 Completed 0 3m > sleeper-1527164940-j2k8f 0/1 Completed 0 2m > sleeper-1527165000-bp5vx 0/1 Terminating 0 1m > sleeper-1527165060-72b9l 0/1 Completed 0 15s > > Here's the cron configuraton: > > --- > apiVersion: batch/v1beta1 > kind: CronJob > metadata: > name: sleeper > spec: > schedule: "*/1 * * * *" > concurrencyPolicy: Replace > successfulJobsHistoryLimit: 3 > failedJobsHistoryLimit: 3 > jobTemplate: > spec: > template: > spec: > containers: > - name: sleeper > image: /library/ubuntu:18.04 > args: > - "/bin/sleep" > - "5" > restartPolicy: OnFailure > imagePullSecrets: > - name: regcred > > Here's the source code for sleep: > https://github.com/coreutils/coreutils/blob/master/src/sleep.c > > I'd say there's definitely other pods that have the same issue. :D" > > Regards > > St?phane Le Bihan > SDE/DSI/IPR/SSD/UNX > 90, Boulevard Pasteur - 75015 Paris > Web: www.amundi.com > Tel: +33 1 76 32 32 08 > Tel Unix Team: +33 1 76 32 02 30 > @: stephane.lebihan at amundi.com > @: sits.unix at amundi.com > > Visit us on: > > > > > -----Message d'origine----- > De?: caasp-beta-bounces at lists.suse.com > [mailto:caasp-beta-bounces at lists.suse.com] De la part de Le Bihan > St?phane (AMUNDI-ITS) Envoy??: jeudi 24 mai 2018 14:35 ??: > lproven at suse.com; Yoshise, Junichi Cc?: caasp-beta at lists.suse.com > Objet?: Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? > > Thanks for your response. > > I launch support_config, but it's stuck at Docker line .... > I wait. > > Memory limit on server is not at limit (big server :D) > > total used free shared buffers cached > Mem: 377 14 363 0 0 9 > -/+ buffers/cache: 4 373 > Swap: 0 0 0 > > And for application developer say me : > "Influxtreon consumes about 150kB to run" > > I wait for support_config. > > Regards, > > > St?phane Le Bihan > SDE/DSI/IPR/SSD/UNX > 90, Boulevard Pasteur - 75015 Paris > Web: www.amundi.com > Tel: +33 1 76 32 32 08 > Tel Unix Team: +33 1 76 32 02 30 > @: stephane.lebihan at amundi.com > @: sits.unix at amundi.com > > Visit us on: > > > > > -----Message d'origine----- > De?: caasp-beta-bounces at lists.suse.com > [mailto:caasp-beta-bounces at lists.suse.com] De la part de Liam Proven > Envoy??: jeudi 24 mai 2018 12:26 ??: Yoshise, Junichi Cc?: > caasp-beta at lists.suse.com Objet?: [Marketing Mail] Re: [caasp-beta] > How to deploy CaaSP on EC2? > > On Thu, 24 May 2018 06:34:27 +0000 > "Yoshise, Junichi" wrote: > > > I?m trying to deploy CaaSP 3.0 beta2 on AWS EC2. Since AMI is not > > available, I?ve converted qcow2 or vmdk file then tried to import to > > EC2, but it didn?t work. Is there any way to deploy CaaSP on EC2? > > As I understand it, currently, for public cloud use, you should be > looking at CaaSP 2.1, not 3.0 -- and I believe it has not yet reached > beta phase. > > -- > Liam Proven - Technical Writer, SUSE Linux s.r.o. > Corso II, K?i??kova 148/34, 186-00 Praha 8 - Karl?n, Czechia > Email: lproven at suse.com - Office telephone: +420 284 241 084 > > > _______________________________________________ > 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 stephane.lebihan at amundi.com Fri May 25 04:07:08 2018 From: stephane.lebihan at amundi.com (=?utf-8?B?TGUgQmloYW4gU3TDqXBoYW5lIChBTVVOREktSVRTKQ==?=) Date: Fri, 25 May 2018 10:07:08 +0000 Subject: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? References: <20180524122543.4a56aea7.lproven@suse.com> <20180525091539.2weqb5oyk5jibzsp@nebuchadnezzar> Message-ID: And link vers bugzilla print warn : Sorry, either the product Beta SUSE CaaS Platform 3 does not exist or you aren't authorized to enter a bug into it. May be I'm not autorized St?phane Le Bihan SDE/DSI/IPR/SSD/UNX 90, Boulevard Pasteur - 75015 Paris Web: www.amundi.com Tel: +33 1 76 32 32 08 Tel Unix Team: +33 1 76 32 02 30 @: stephane.lebihan at amundi.com @: sits.unix at amundi.com Visit us on: -----Message d'origine----- De?: Le Bihan St?phane (AMUNDI-ITS) Envoy??: vendredi 25 mai 2018 12:06 ??: 'Valentin Rothberg' Cc?: Junichi Yoshise; Liam Proven; vrothberg at suse.de; caasp-beta at lists.suse.com Objet?: RE: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? Hi Valentin, I'm not familar with bugzilla and url " https://www.suse.com/betaprogram/beta-guideline.html#bugzilla" return "Page not found" ... Regards, St?phane Le Bihan SDE/DSI/IPR/SSD/UNX 90, Boulevard Pasteur - 75015 Paris Web: www.amundi.com Tel: +33 1 76 32 32 08 Tel Unix Team: +33 1 76 32 02 30 @: stephane.lebihan at amundi.com @: sits.unix at amundi.com Visit us on: -----Message d'origine----- De?: Valentin Rothberg [mailto:vrothberg at suse.com] Envoy??: vendredi 25 mai 2018 11:16 ??: Le Bihan St?phane (AMUNDI-ITS) Cc?: Junichi Yoshise; Liam Proven; vrothberg at suse.de; caasp-beta at lists.suse.com Objet?: Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? Hi, given the issue is reproducible in your environment, could you open a bug on bugzilla.suse.com and upload the supportconfig there? If supportconfig hangs, we can initially have a look at the Docker logs (e.g., `journalctl -u docker`) and start from there. Thanks a lot and kind regards, Valentin On May/24/18 12:42, Le Bihan St?phane (AMUNDI-ITS) wrote: > For information another response from another develloper : > > " Hi, > > I've created new test cron job and even that generates the Terminating pods: > > $ kp get pods -n tick > NAME READY STATUS RESTARTS AGE > data-influxdb-5c7b44ff76-fcf5m 1/1 Running 2 9d > grafana-7dc9f4bccc-k6gbc 1/1 Running 3 9d > influxtreon-1527164760-64xf9 0/1 Terminating 0 5m > influxtreon-1527164940-27565 0/1 Completed 0 2m > influxtreon-1527165000-mh27k 0/1 Completed 0 1m > influxtreon-1527165060-d8jww 0/1 Completed 0 16s > sleeper-1527164640-9njtv 0/1 Terminating 0 7m > sleeper-1527164760-xm79v 0/1 Completed 0 5m > sleeper-1527164820-ptb64 0/1 Terminating 0 4m > sleeper-1527164880-q6f6d 0/1 Completed 0 3m > sleeper-1527164940-j2k8f 0/1 Completed 0 2m > sleeper-1527165000-bp5vx 0/1 Terminating 0 1m > sleeper-1527165060-72b9l 0/1 Completed 0 15s > > Here's the cron configuraton: > > --- > apiVersion: batch/v1beta1 > kind: CronJob > metadata: > name: sleeper > spec: > schedule: "*/1 * * * *" > concurrencyPolicy: Replace > successfulJobsHistoryLimit: 3 > failedJobsHistoryLimit: 3 > jobTemplate: > spec: > template: > spec: > containers: > - name: sleeper > image: /library/ubuntu:18.04 > args: > - "/bin/sleep" > - "5" > restartPolicy: OnFailure > imagePullSecrets: > - name: regcred > > Here's the source code for sleep: > https://github.com/coreutils/coreutils/blob/master/src/sleep.c > > I'd say there's definitely other pods that have the same issue. :D" > > Regards > > St?phane Le Bihan > SDE/DSI/IPR/SSD/UNX > 90, Boulevard Pasteur - 75015 Paris > Web: www.amundi.com > Tel: +33 1 76 32 32 08 > Tel Unix Team: +33 1 76 32 02 30 > @: stephane.lebihan at amundi.com > @: sits.unix at amundi.com > > Visit us on: > > > > > -----Message d'origine----- > De?: caasp-beta-bounces at lists.suse.com > [mailto:caasp-beta-bounces at lists.suse.com] De la part de Le Bihan > St?phane (AMUNDI-ITS) Envoy??: jeudi 24 mai 2018 14:35 ??: > lproven at suse.com; Yoshise, Junichi Cc?: caasp-beta at lists.suse.com > Objet?: Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? > > Thanks for your response. > > I launch support_config, but it's stuck at Docker line .... > I wait. > > Memory limit on server is not at limit (big server :D) > > total used free shared buffers cached > Mem: 377 14 363 0 0 9 > -/+ buffers/cache: 4 373 > Swap: 0 0 0 > > And for application developer say me : > "Influxtreon consumes about 150kB to run" > > I wait for support_config. > > Regards, > > > St?phane Le Bihan > SDE/DSI/IPR/SSD/UNX > 90, Boulevard Pasteur - 75015 Paris > Web: www.amundi.com > Tel: +33 1 76 32 32 08 > Tel Unix Team: +33 1 76 32 02 30 > @: stephane.lebihan at amundi.com > @: sits.unix at amundi.com > > Visit us on: > > > > > -----Message d'origine----- > De?: caasp-beta-bounces at lists.suse.com > [mailto:caasp-beta-bounces at lists.suse.com] De la part de Liam Proven > Envoy??: jeudi 24 mai 2018 12:26 ??: Yoshise, Junichi Cc?: > caasp-beta at lists.suse.com Objet?: [Marketing Mail] Re: [caasp-beta] > How to deploy CaaSP on EC2? > > On Thu, 24 May 2018 06:34:27 +0000 > "Yoshise, Junichi" wrote: > > > I?m trying to deploy CaaSP 3.0 beta2 on AWS EC2. Since AMI is not > > available, I?ve converted qcow2 or vmdk file then tried to import to > > EC2, but it didn?t work. Is there any way to deploy CaaSP on EC2? > > As I understand it, currently, for public cloud use, you should be > looking at CaaSP 2.1, not 3.0 -- and I believe it has not yet reached > beta phase. > > -- > Liam Proven - Technical Writer, SUSE Linux s.r.o. > Corso II, K?i??kova 148/34, 186-00 Praha 8 - Karl?n, Czechia > Email: lproven at suse.com - Office telephone: +420 284 241 084 > > > _______________________________________________ > 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 vrothberg at suse.com Fri May 25 04:15:25 2018 From: vrothberg at suse.com (Valentin Rothberg) Date: Fri, 25 May 2018 12:15:25 +0200 Subject: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? In-Reply-To: References: <20180524122543.4a56aea7.lproven@suse.com> <20180525091539.2weqb5oyk5jibzsp@nebuchadnezzar> Message-ID: <20180525101525.hjgqlhpcrqcgswbo@nebuchadnezzar> Hi St?phane, On May/25/18 10:05, Le Bihan St?phane (AMUNDI-ITS) wrote: > Hi Valentin, > > I'm not familar with bugzilla and url " https://www.suse.com/betaprogram/beta-guideline.html#bugzilla" return "Page not found" ... May I ask where you got that link from? > St?phane Le Bihan > SDE/DSI/IPR/SSD/UNX > 90, Boulevard Pasteur - 75015 Paris > Web: www.amundi.com > Tel: +33 1 76 32 32 08 > Tel Unix Team: +33 1 76 32 02 30 > @: stephane.lebihan at amundi.com > @: sits.unix at amundi.com > > Visit us on: > > > > -----Message d'origine----- > De?: Valentin Rothberg [mailto:vrothberg at suse.com] > Envoy??: vendredi 25 mai 2018 11:16 > ??: Le Bihan St?phane (AMUNDI-ITS) > Cc?: Junichi Yoshise; Liam Proven; vrothberg at suse.de; caasp-beta at lists.suse.com > Objet?: Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? > > Hi, > > given the issue is reproducible in your environment, could you open a bug on bugzilla.suse.com and upload the supportconfig there? If supportconfig hangs, we can initially have a look at the Docker logs (e.g., `journalctl -u docker`) and start from there. > > Thanks a lot and kind regards, > Valentin > > On May/24/18 12:42, Le Bihan St?phane (AMUNDI-ITS) wrote: > > For information another response from another develloper : > > > > " Hi, > > > > I've created new test cron job and even that generates the Terminating pods: > > > > $ kp get pods -n tick > > NAME READY STATUS RESTARTS AGE > > data-influxdb-5c7b44ff76-fcf5m 1/1 Running 2 9d > > grafana-7dc9f4bccc-k6gbc 1/1 Running 3 9d > > influxtreon-1527164760-64xf9 0/1 Terminating 0 5m > > influxtreon-1527164940-27565 0/1 Completed 0 2m > > influxtreon-1527165000-mh27k 0/1 Completed 0 1m > > influxtreon-1527165060-d8jww 0/1 Completed 0 16s > > sleeper-1527164640-9njtv 0/1 Terminating 0 7m > > sleeper-1527164760-xm79v 0/1 Completed 0 5m > > sleeper-1527164820-ptb64 0/1 Terminating 0 4m > > sleeper-1527164880-q6f6d 0/1 Completed 0 3m > > sleeper-1527164940-j2k8f 0/1 Completed 0 2m > > sleeper-1527165000-bp5vx 0/1 Terminating 0 1m > > sleeper-1527165060-72b9l 0/1 Completed 0 15s > > > > Here's the cron configuraton: > > > > --- > > apiVersion: batch/v1beta1 > > kind: CronJob > > metadata: > > name: sleeper > > spec: > > schedule: "*/1 * * * *" > > concurrencyPolicy: Replace > > successfulJobsHistoryLimit: 3 > > failedJobsHistoryLimit: 3 > > jobTemplate: > > spec: > > template: > > spec: > > containers: > > - name: sleeper > > image: /library/ubuntu:18.04 > > args: > > - "/bin/sleep" > > - "5" > > restartPolicy: OnFailure > > imagePullSecrets: > > - name: regcred > > > > Here's the source code for sleep: > > https://github.com/coreutils/coreutils/blob/master/src/sleep.c > > > > I'd say there's definitely other pods that have the same issue. :D" > > > > Regards > > > > St?phane Le Bihan > > SDE/DSI/IPR/SSD/UNX > > 90, Boulevard Pasteur - 75015 Paris > > Web: www.amundi.com > > Tel: +33 1 76 32 32 08 > > Tel Unix Team: +33 1 76 32 02 30 > > @: stephane.lebihan at amundi.com > > @: sits.unix at amundi.com > > > > Visit us on: > > > > > > > > > > -----Message d'origine----- > > De?: caasp-beta-bounces at lists.suse.com > > [mailto:caasp-beta-bounces at lists.suse.com] De la part de Le Bihan > > St?phane (AMUNDI-ITS) Envoy??: jeudi 24 mai 2018 14:35 ??: > > lproven at suse.com; Yoshise, Junichi Cc?: caasp-beta at lists.suse.com > > Objet?: Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? > > > > Thanks for your response. > > > > I launch support_config, but it's stuck at Docker line .... > > I wait. > > > > Memory limit on server is not at limit (big server :D) > > > > total used free shared buffers cached > > Mem: 377 14 363 0 0 9 > > -/+ buffers/cache: 4 373 > > Swap: 0 0 0 > > > > And for application developer say me : > > "Influxtreon consumes about 150kB to run" > > > > I wait for support_config. > > > > Regards, > > > > > > St?phane Le Bihan > > SDE/DSI/IPR/SSD/UNX > > 90, Boulevard Pasteur - 75015 Paris > > Web: www.amundi.com > > Tel: +33 1 76 32 32 08 > > Tel Unix Team: +33 1 76 32 02 30 > > @: stephane.lebihan at amundi.com > > @: sits.unix at amundi.com > > > > Visit us on: > > > > > > > > > > -----Message d'origine----- > > De?: caasp-beta-bounces at lists.suse.com > > [mailto:caasp-beta-bounces at lists.suse.com] De la part de Liam Proven > > Envoy??: jeudi 24 mai 2018 12:26 ??: Yoshise, Junichi Cc?: > > caasp-beta at lists.suse.com Objet?: [Marketing Mail] Re: [caasp-beta] > > How to deploy CaaSP on EC2? > > > > On Thu, 24 May 2018 06:34:27 +0000 > > "Yoshise, Junichi" wrote: > > > > > I?m trying to deploy CaaSP 3.0 beta2 on AWS EC2. Since AMI is not > > > available, I?ve converted qcow2 or vmdk file then tried to import to > > > EC2, but it didn?t work. Is there any way to deploy CaaSP on EC2? > > > > As I understand it, currently, for public cloud use, you should be > > looking at CaaSP 2.1, not 3.0 -- and I believe it has not yet reached > > beta phase. > > > > -- > > Liam Proven - Technical Writer, SUSE Linux s.r.o. > > Corso II, K?i??kova 148/34, 186-00 Praha 8 - Karl?n, Czechia > > Email: lproven at suse.com - Office telephone: +420 284 241 084 > > > > > > _______________________________________________ > > 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 -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: not available URL: From vmoutoussamy at suse.com Fri May 25 04:15:48 2018 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Fri, 25 May 2018 12:15:48 +0200 Subject: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? In-Reply-To: References: <20180524122543.4a56aea7.lproven@suse.com> <20180525091539.2weqb5oyk5jibzsp@nebuchadnezzar> Message-ID: <9365394C-2EAC-4F25-9465-913000D8892C@suse.com> Bonjour, > On 25 May 2018, at 12:07, Le Bihan St?phane (AMUNDI-ITS) wrote: > > And link vers bugzilla print warn : > > Sorry, either the product Beta SUSE CaaS Platform 3 does not exist or you aren't authorized to enter a bug into it. > > May be I'm not autorized Could you send me all the information via email and I will create the bug for you? > I'm not familar with bugzilla and url " https://www.suse.com/betaprogram/beta-guideline.html#bugzilla" return "Page not found" ... > > Regards, > > St?phane Le Bihan > SDE/DSI/IPR/SSD/UNX > 90, Boulevard Pasteur - 75015 Paris > Web: www.amundi.com > Tel: +33 1 76 32 32 08 > Tel Unix Team: +33 1 76 32 02 30 > @: stephane.lebihan at amundi.com > @: sits.unix at amundi.com Both will be fixed ASAP! Thanks for the report and sorry for the inconvenience, Regards, -- Vincent Moutoussamy SUSE Beta Program and SDK Project Manager -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL: From stephane.lebihan at amundi.com Fri May 25 05:29:52 2018 From: stephane.lebihan at amundi.com (=?utf-8?B?TGUgQmloYW4gU3TDqXBoYW5lIChBTVVOREktSVRTKQ==?=) Date: Fri, 25 May 2018 11:29:52 +0000 Subject: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? In-Reply-To: <20180525101525.hjgqlhpcrqcgswbo@nebuchadnezzar> References: <20180524122543.4a56aea7.lproven@suse.com> <20180525091539.2weqb5oyk5jibzsp@nebuchadnezzar> <20180525101525.hjgqlhpcrqcgswbo@nebuchadnezzar> Message-ID: Yes, you may. :D It's on this, in Bugzilla section : https://www.suse.com/betaprogram/caasp-beta/#documentation " Please refer to our complete Bugzilla guideline for more information and before creating your first bug report: how to use Bugzilla" St?phane Le Bihan SDE/DSI/IPR/SSD/UNX 90, Boulevard Pasteur - 75015 Paris Web: www.amundi.com Tel: +33 1 76 32 32 08 Tel Unix Team: +33 1 76 32 02 30 @: stephane.lebihan at amundi.com @: sits.unix at amundi.com Visit us on: -----Message d'origine----- De?: Valentin Rothberg [mailto:vrothberg at suse.com] Envoy??: vendredi 25 mai 2018 12:15 ??: Le Bihan St?phane (AMUNDI-ITS) Cc?: Junichi Yoshise; Liam Proven; vrothberg at suse.de; caasp-beta at lists.suse.com Objet?: Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? Hi St?phane, On May/25/18 10:05, Le Bihan St?phane (AMUNDI-ITS) wrote: > Hi Valentin, > > I'm not familar with bugzilla and url " https://www.suse.com/betaprogram/beta-guideline.html#bugzilla" return "Page not found" ... May I ask where you got that link from? > St?phane Le Bihan > SDE/DSI/IPR/SSD/UNX > 90, Boulevard Pasteur - 75015 Paris > Web: www.amundi.com > Tel: +33 1 76 32 32 08 > Tel Unix Team: +33 1 76 32 02 30 > @: stephane.lebihan at amundi.com > @: sits.unix at amundi.com > > Visit us on: > > > > -----Message d'origine----- > De?: Valentin Rothberg [mailto:vrothberg at suse.com] Envoy??: vendredi > 25 mai 2018 11:16 ??: Le Bihan St?phane (AMUNDI-ITS) Cc?: Junichi > Yoshise; Liam Proven; vrothberg at suse.de; caasp-beta at lists.suse.com > Objet?: Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? > > Hi, > > given the issue is reproducible in your environment, could you open a bug on bugzilla.suse.com and upload the supportconfig there? If supportconfig hangs, we can initially have a look at the Docker logs (e.g., `journalctl -u docker`) and start from there. > > Thanks a lot and kind regards, > Valentin > > On May/24/18 12:42, Le Bihan St?phane (AMUNDI-ITS) wrote: > > For information another response from another develloper : > > > > " Hi, > > > > I've created new test cron job and even that generates the Terminating pods: > > > > $ kp get pods -n tick > > NAME READY STATUS RESTARTS AGE > > data-influxdb-5c7b44ff76-fcf5m 1/1 Running 2 9d > > grafana-7dc9f4bccc-k6gbc 1/1 Running 3 9d > > influxtreon-1527164760-64xf9 0/1 Terminating 0 5m > > influxtreon-1527164940-27565 0/1 Completed 0 2m > > influxtreon-1527165000-mh27k 0/1 Completed 0 1m > > influxtreon-1527165060-d8jww 0/1 Completed 0 16s > > sleeper-1527164640-9njtv 0/1 Terminating 0 7m > > sleeper-1527164760-xm79v 0/1 Completed 0 5m > > sleeper-1527164820-ptb64 0/1 Terminating 0 4m > > sleeper-1527164880-q6f6d 0/1 Completed 0 3m > > sleeper-1527164940-j2k8f 0/1 Completed 0 2m > > sleeper-1527165000-bp5vx 0/1 Terminating 0 1m > > sleeper-1527165060-72b9l 0/1 Completed 0 15s > > > > Here's the cron configuraton: > > > > --- > > apiVersion: batch/v1beta1 > > kind: CronJob > > metadata: > > name: sleeper > > spec: > > schedule: "*/1 * * * *" > > concurrencyPolicy: Replace > > successfulJobsHistoryLimit: 3 > > failedJobsHistoryLimit: 3 > > jobTemplate: > > spec: > > template: > > spec: > > containers: > > - name: sleeper > > image: /library/ubuntu:18.04 > > args: > > - "/bin/sleep" > > - "5" > > restartPolicy: OnFailure > > imagePullSecrets: > > - name: regcred > > > > Here's the source code for sleep: > > https://github.com/coreutils/coreutils/blob/master/src/sleep.c > > > > I'd say there's definitely other pods that have the same issue. :D" > > > > Regards > > > > St?phane Le Bihan > > SDE/DSI/IPR/SSD/UNX > > 90, Boulevard Pasteur - 75015 Paris > > Web: www.amundi.com > > Tel: +33 1 76 32 32 08 > > Tel Unix Team: +33 1 76 32 02 30 > > @: stephane.lebihan at amundi.com > > @: sits.unix at amundi.com > > > > Visit us on: > > > > > > > > > > -----Message d'origine----- > > De?: caasp-beta-bounces at lists.suse.com > > [mailto:caasp-beta-bounces at lists.suse.com] De la part de Le Bihan > > St?phane (AMUNDI-ITS) Envoy??: jeudi 24 mai 2018 14:35 ??: > > lproven at suse.com; Yoshise, Junichi Cc?: caasp-beta at lists.suse.com > > Objet?: Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? > > > > Thanks for your response. > > > > I launch support_config, but it's stuck at Docker line .... > > I wait. > > > > Memory limit on server is not at limit (big server :D) > > > > total used free shared buffers cached > > Mem: 377 14 363 0 0 9 > > -/+ buffers/cache: 4 373 > > Swap: 0 0 0 > > > > And for application developer say me : > > "Influxtreon consumes about 150kB to run" > > > > I wait for support_config. > > > > Regards, > > > > > > St?phane Le Bihan > > SDE/DSI/IPR/SSD/UNX > > 90, Boulevard Pasteur - 75015 Paris > > Web: www.amundi.com > > Tel: +33 1 76 32 32 08 > > Tel Unix Team: +33 1 76 32 02 30 > > @: stephane.lebihan at amundi.com > > @: sits.unix at amundi.com > > > > Visit us on: > > > > > > > > > > -----Message d'origine----- > > De?: caasp-beta-bounces at lists.suse.com > > [mailto:caasp-beta-bounces at lists.suse.com] De la part de Liam Proven > > Envoy??: jeudi 24 mai 2018 12:26 ??: Yoshise, Junichi Cc?: > > caasp-beta at lists.suse.com Objet?: [Marketing Mail] Re: [caasp-beta] > > How to deploy CaaSP on EC2? > > > > On Thu, 24 May 2018 06:34:27 +0000 > > "Yoshise, Junichi" wrote: > > > > > I?m trying to deploy CaaSP 3.0 beta2 on AWS EC2. Since AMI is not > > > available, I?ve converted qcow2 or vmdk file then tried to import > > > to EC2, but it didn?t work. Is there any way to deploy CaaSP on EC2? > > > > As I understand it, currently, for public cloud use, you should be > > looking at CaaSP 2.1, not 3.0 -- and I believe it has not yet > > reached beta phase. > > > > -- > > Liam Proven - Technical Writer, SUSE Linux s.r.o. > > Corso II, K?i??kova 148/34, 186-00 Praha 8 - Karl?n, Czechia > > Email: lproven at suse.com - Office telephone: +420 284 241 084 > > > > > > _______________________________________________ > > 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 vrothberg at suse.com Fri May 25 05:45:07 2018 From: vrothberg at suse.com (Valentin Rothberg) Date: Fri, 25 May 2018 13:45:07 +0200 Subject: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? In-Reply-To: References: <20180524122543.4a56aea7.lproven@suse.com> <20180525091539.2weqb5oyk5jibzsp@nebuchadnezzar> <20180525101525.hjgqlhpcrqcgswbo@nebuchadnezzar> Message-ID: <20180525114507.o2p3ilm77m4qgpuz@nebuchadnezzar> On May/25/18 11:29, Le Bihan St?phane (AMUNDI-ITS) wrote: > Yes, you may. :D > > It's on this, in Bugzilla section : > https://www.suse.com/betaprogram/caasp-beta/#documentation Thanks a lot, and sorry for the inconvenience. The link will be fixed. > " Please refer to our complete Bugzilla guideline for more information and before creating your first bug report: how to use Bugzilla" I would appreciate if you could open the bug in Bugzilla, so we can move communication there. You can also upload the logs there directly. What you need to do is to login, so you may create an account if not present. You can go on bugzilla.suse.com, click on login and follow the steps from there. Thanks a lot, and kind regards, Valentin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: not available URL: From stephane.lebihan at amundi.com Wed May 30 07:51:53 2018 From: stephane.lebihan at amundi.com (=?utf-8?B?TGUgQmloYW4gU3TDqXBoYW5lIChBTVVOREktSVRTKQ==?=) Date: Wed, 30 May 2018 13:51:53 +0000 Subject: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? In-Reply-To: References: <20180524122543.4a56aea7.lproven@suse.com> <20180525091539.2weqb5oyk5jibzsp@nebuchadnezzar> <20180525101525.hjgqlhpcrqcgswbo@nebuchadnezzar> <20180525114507.o2p3ilm77m4qgpuz@nebuchadnezzar> Message-ID: Hi all, Have you more news of this bug ? I'm also not authorized to see bug https://bugzilla.suse.com/show_bug.cgi?id=1094680 For information we have find this : So I've found related PR: https://github.com/opencontainers/runc/pull/1477 (possibly) This is something in logs just before it all goes crazy: level=error msg="Handler for POST /v1.31/containers/0ebea7ea2522e14a1fec46ee8991ea2195b76898b5f778dc2f9e57dd36f52efe/start returned error: oci runtime error: container_linux.go:258: creating new parent process caused \"container_linux.go:1545: running lstat on namespace path \\"/proc/49701/ns/ipc\\" caused \\"lstat /proc/49701/ns/ipc: no such file or directory\\"\" The problem is, that the version of runc with the PR merged is still only 1.0 RC5 I can't quite find if docker is using the same code or if they import some RC code Regards, St?phane Le Bihan SDE/DSI/IPR/SSD/UNX 90, Boulevard Pasteur - 75015 Paris Web: www.amundi.com Tel: +33 1 76 32 32 08 Tel Unix Team: +33 1 76 32 02 30 @: stephane.lebihan at amundi.com @: sits.unix at amundi.com Visit us on: -----Message d'origine----- De?: Le Bihan St?phane (AMUNDI-ITS) Envoy??: lundi 28 mai 2018 11:20 ??: Valentin Rothberg Cc?: vrothberg at suse.de; Junichi Yoshise; caasp-beta at lists.suse.com; Liam Proven Objet?: RE: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? Hi all. After successfully upgrade of all nodes with Suse CAASP 3beta 2 DVD next Friday, we have no docker in "Terminating" state this Monday. We left sleeper run this week. --- apiVersion: batch/v1beta1 kind: CronJob metadata: name: sleeper spec: schedule: "*/1 * * * *" concurrencyPolicy: Replace successfulJobsHistoryLimit: 3 failedJobsHistoryLimit: 3 jobTemplate: spec: template: spec: containers: - name: sleeper image: registry-docker.intramundi.com/library/ubuntu:18.04 args: - "/bin/sleep" - "5" restartPolicy: OnFailure imagePullSecrets: - name: regcred Here's the source code for sleep: https://github.com/coreutils/coreutils/blob/master/src/sleep.c State of cluster this morning. In "state_2018-05-28_11-15.txt" file. I join support config of same node. Regards, ? St?phane Le Bihan Ing?nieur syst?me et production 90, Boulevard Pasteur ? 75015 Paris Web?: www.amundi.com T?l?: +33 1 76 32 32 08 Equipe Unix?: +33 1 76 32 02 30 @ : stephane.lebihan at amundi.com @ : sits.unix at amundi.com -----Message d'origine----- De?: Valentin Rothberg [mailto:vrothberg at suse.com] Envoy??: vendredi 25 mai 2018 13:45 ??: Le Bihan St?phane (AMUNDI-ITS) Cc?: vrothberg at suse.de; Junichi Yoshise; caasp-beta at lists.suse.com; Liam Proven Objet?: Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? On May/25/18 11:29, Le Bihan St?phane (AMUNDI-ITS) wrote: > Yes, you may. :D > > It's on this, in Bugzilla section : > https://www.suse.com/betaprogram/caasp-beta/#documentation Thanks a lot, and sorry for the inconvenience. The link will be fixed. > " Please refer to our complete Bugzilla guideline for more information and before creating your first bug report: how to use Bugzilla" I would appreciate if you could open the bug in Bugzilla, so we can move communication there. You can also upload the logs there directly. What you need to do is to login, so you may create an account if not present. You can go on bugzilla.suse.com, click on login and follow the steps from there. Thanks a lot, and kind regards, Valentin From vrothberg at suse.com Wed May 30 10:03:28 2018 From: vrothberg at suse.com (Valentin Rothberg) Date: Wed, 30 May 2018 18:03:28 +0200 Subject: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? In-Reply-To: References: <20180524122543.4a56aea7.lproven@suse.com> <20180525091539.2weqb5oyk5jibzsp@nebuchadnezzar> <20180525101525.hjgqlhpcrqcgswbo@nebuchadnezzar> <20180525114507.o2p3ilm77m4qgpuz@nebuchadnezzar> Message-ID: <20180530160328.bz5bszjd4sasihdu@nebuchadnezzar.local> Hi St?phane, On May/30/18 13:51, Le Bihan St?phane (AMUNDI-ITS) wrote: > Hi all, > > Have you more news of this bug ? > I'm also not authorized to see bug https://bugzilla.suse.com/show_bug.cgi?id=1094680 I am a bit confused. Didn't you write earlier this week that issue doesn't occur anymore? Maybe, I misread your email. Can you clarify? > For information we have find this : > > So I've found related PR: https://github.com/opencontainers/runc/pull/1477 > (possibly) > This is something in logs just before it all goes crazy: > level=error msg="Handler for POST /v1.31/containers/0ebea7ea2522e14a1fec46ee8991ea2195b76898b5f778dc2f9e57dd36f52efe/start returned error: oci runtime error: container_linux.go:258: creating new parent process caused \"container_linux.go:1545: running lstat on namespace path \\"/proc/49701/ns/ipc\\" caused \\"lstat /proc/49701/ns/ipc: no such file or directory\\"\" > The problem is, that the version of runc with the PR merged is still only 1.0 RC5 > I can't quite find if docker is using the same code or if they import some RC code Thanks a lot for checking. We will look into the issue as soon as possible. Kind regards, Valentin > St?phane Le Bihan > SDE/DSI/IPR/SSD/UNX > 90, Boulevard Pasteur - 75015 Paris > Web: www.amundi.com > Tel: +33 1 76 32 32 08 > Tel Unix Team: +33 1 76 32 02 30 > @: stephane.lebihan at amundi.com > @: sits.unix at amundi.com > > Visit us on: > > > > -----Message d'origine----- > De?: Le Bihan St?phane (AMUNDI-ITS) > Envoy??: lundi 28 mai 2018 11:20 > ??: Valentin Rothberg > Cc?: vrothberg at suse.de; Junichi Yoshise; caasp-beta at lists.suse.com; Liam Proven > Objet?: RE: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? > > Hi all. > > After successfully upgrade of all nodes with Suse CAASP 3beta 2 DVD next Friday, we have no docker in "Terminating" state this Monday. > We left sleeper run this week. > > --- > apiVersion: batch/v1beta1 > kind: CronJob > metadata: > name: sleeper > spec: > schedule: "*/1 * * * *" > concurrencyPolicy: Replace > successfulJobsHistoryLimit: 3 > failedJobsHistoryLimit: 3 > jobTemplate: > spec: > template: > spec: > containers: > - name: sleeper > image: registry-docker.intramundi.com/library/ubuntu:18.04 > args: > - "/bin/sleep" > - "5" > restartPolicy: OnFailure > imagePullSecrets: > - name: regcred > > Here's the source code for sleep: > https://github.com/coreutils/coreutils/blob/master/src/sleep.c > > State of cluster this morning. In "state_2018-05-28_11-15.txt" file. > I join support config of same node. > > Regards, > ? > St?phane Le Bihan > Ing?nieur syst?me et production > 90, Boulevard Pasteur ? 75015 Paris > Web?: www.amundi.com > T?l?: +33 1 76 32 32 08 > Equipe Unix?: +33 1 76 32 02 30 > @ : stephane.lebihan at amundi.com > @ : sits.unix at amundi.com > > -----Message d'origine----- > De?: Valentin Rothberg [mailto:vrothberg at suse.com] Envoy??: vendredi 25 mai 2018 13:45 ??: Le Bihan St?phane (AMUNDI-ITS) Cc?: vrothberg at suse.de; Junichi Yoshise; caasp-beta at lists.suse.com; Liam Proven Objet?: Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? > > On May/25/18 11:29, Le Bihan St?phane (AMUNDI-ITS) wrote: > > Yes, you may. :D > > > > It's on this, in Bugzilla section : > > https://www.suse.com/betaprogram/caasp-beta/#documentation > > Thanks a lot, and sorry for the inconvenience. The link will be fixed. > > > " Please refer to our complete Bugzilla guideline for more information and before creating your first bug report: how to use Bugzilla" > > I would appreciate if you could open the bug in Bugzilla, so we can move communication there. You can also upload the logs there directly. What you need to do is to login, so you may create an account if not present. > You can go on bugzilla.suse.com, click on login and follow the steps from there. > > Thanks a lot, and kind regards, > Valentin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: not available URL: From stephane.lebihan at amundi.com Wed May 30 23:29:37 2018 From: stephane.lebihan at amundi.com (=?utf-8?B?TGUgQmloYW4gU3TDqXBoYW5lIChBTVVOREktSVRTKQ==?=) Date: Thu, 31 May 2018 05:29:37 +0000 Subject: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? In-Reply-To: <20180530160328.bz5bszjd4sasihdu@nebuchadnezzar.local> References: <20180524122543.4a56aea7.lproven@suse.com> <20180525091539.2weqb5oyk5jibzsp@nebuchadnezzar> <20180525101525.hjgqlhpcrqcgswbo@nebuchadnezzar> <20180525114507.o2p3ilm77m4qgpuz@nebuchadnezzar> <20180530160328.bz5bszjd4sasihdu@nebuchadnezzar.local> Message-ID: Hi all, I ask for update bug with information, and I'm not use "reply all". So it seemed OK Friday and Saturday but on Monday new pods in "Terminating" state. We observed node state switch to NotReady for a few moment, when node host more pods in "Terminating" state. We have search more information, and we think it's a Docker problem who don't terminate correctly container. The only option for clear "Terminating" container we find is : for pod2delete in $(kubectl get po -n | grep Terminating | awk '{ print $1 }'); do kubectl delete po/$pod2delete -n --force --grace-period=0 done And sometimes, because node is more often "NotReady", or all node is "NotReady" we restart docker and kubelet..... For information we have restart docker and kubelet at 17:00 yesterday, and this morning I have 286 po in "Terminating" State. I joined status of nodes and pods this morning. Regards, St?phane Le Bihan SDE/DSI/IPR/SSD/UNX 90, Boulevard Pasteur - 75015 Paris Web: www.amundi.com Tel: +33 1 76 32 32 08 Tel Unix Team: +33 1 76 32 02 30 @: stephane.lebihan at amundi.com @: sits.unix at amundi.com Visit us on: -----Message d'origine----- De?: Valentin Rothberg [mailto:vrothberg at suse.com] Envoy??: mercredi 30 mai 2018 18:03 ??: Le Bihan St?phane (AMUNDI-ITS) Cc?: vrothberg at suse.de; 'Junichi Yoshise'; 'caasp-beta at lists.suse.com'; Liam Proven Objet?: Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? Hi St?phane, On May/30/18 13:51, Le Bihan St?phane (AMUNDI-ITS) wrote: > Hi all, > > Have you more news of this bug ? > I'm also not authorized to see bug > https://bugzilla.suse.com/show_bug.cgi?id=1094680 I am a bit confused. Didn't you write earlier this week that issue doesn't occur anymore? Maybe, I misread your email. Can you clarify? > For information we have find this : > > So I've found related PR: > https://github.com/opencontainers/runc/pull/1477 > (possibly) > This is something in logs just before it all goes crazy: > level=error msg="Handler for POST /v1.31/containers/0ebea7ea2522e14a1fec46ee8991ea2195b76898b5f778dc2f9e57dd36f52efe/start returned error: oci runtime error: container_linux.go:258: creating new parent process caused \"container_linux.go:1545: running lstat on namespace path \\"/proc/49701/ns/ipc\\" caused \\"lstat /proc/49701/ns/ipc: no such file or directory\\"\" > The problem is, that the version of runc with the PR merged is still > only 1.0 RC5 I can't quite find if docker is using the same code or if > they import some RC code Thanks a lot for checking. We will look into the issue as soon as possible. Kind regards, Valentin > St?phane Le Bihan > SDE/DSI/IPR/SSD/UNX > 90, Boulevard Pasteur - 75015 Paris > Web: www.amundi.com > Tel: +33 1 76 32 32 08 > Tel Unix Team: +33 1 76 32 02 30 > @: stephane.lebihan at amundi.com > @: sits.unix at amundi.com > > Visit us on: > > > > -----Message d'origine----- > De?: Le Bihan St?phane (AMUNDI-ITS) > Envoy??: lundi 28 mai 2018 11:20 > ??: Valentin Rothberg > Cc?: vrothberg at suse.de; Junichi Yoshise; caasp-beta at lists.suse.com; > Liam Proven Objet?: RE: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? > > Hi all. > > After successfully upgrade of all nodes with Suse CAASP 3beta 2 DVD next Friday, we have no docker in "Terminating" state this Monday. > We left sleeper run this week. > > --- > apiVersion: batch/v1beta1 > kind: CronJob > metadata: > name: sleeper > spec: > schedule: "*/1 * * * *" > concurrencyPolicy: Replace > successfulJobsHistoryLimit: 3 > failedJobsHistoryLimit: 3 > jobTemplate: > spec: > template: > spec: > containers: > - name: sleeper > image: registry-docker.intramundi.com/library/ubuntu:18.04 > args: > - "/bin/sleep" > - "5" > restartPolicy: OnFailure > imagePullSecrets: > - name: regcred > > Here's the source code for sleep: > https://github.com/coreutils/coreutils/blob/master/src/sleep.c > > State of cluster this morning. In "state_2018-05-28_11-15.txt" file. > I join support config of same node. > > Regards, > ? > St?phane Le Bihan > Ing?nieur syst?me et production > 90, Boulevard Pasteur ? 75015 Paris > Web?: www.amundi.com > T?l?: +33 1 76 32 32 08 > Equipe Unix?: +33 1 76 32 02 30 > @ : stephane.lebihan at amundi.com > @ : sits.unix at amundi.com > > -----Message d'origine----- > De?: Valentin Rothberg [mailto:vrothberg at suse.com] Envoy??: vendredi 25 mai 2018 13:45 ??: Le Bihan St?phane (AMUNDI-ITS) Cc?: vrothberg at suse.de; Junichi Yoshise; caasp-beta at lists.suse.com; Liam Proven Objet?: Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2? > > On May/25/18 11:29, Le Bihan St?phane (AMUNDI-ITS) wrote: > > Yes, you may. :D > > > > It's on this, in Bugzilla section : > > https://www.suse.com/betaprogram/caasp-beta/#documentation > > Thanks a lot, and sorry for the inconvenience. The link will be fixed. > > > " Please refer to our complete Bugzilla guideline for more information and before creating your first bug report: how to use Bugzilla" > > I would appreciate if you could open the bug in Bugzilla, so we can move communication there. You can also upload the logs there directly. What you need to do is to login, so you may create an account if not present. > You can go on bugzilla.suse.com, click on login and follow the steps from there. > > Thanks a lot, and kind regards, > Valentin -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: state_no-po_20180531.txt URL: