From rushi.ns at sap.com Sat Jun 1 08:03:16 2019 From: rushi.ns at sap.com (Ns, Rushi) Date: Sat, 1 Jun 2019 14:03:16 +0000 Subject: [caasp-beta] CAASP v4 beta 3 In-Reply-To: References: <74b70f0c-eeab-433c-94df-9aef60707995@email.android.com> Message-ID: <05AFBAA3-10EF-4883-8F1B-08B50B9733C3@sap.com> Ok my cluster with 3 nodes bootstrapped and Kubernetes is up . however I am running into runtime issues because it does had ?CRIO? runtime which is why pulling standard docker images get issues as I am not able to find CRIO images. Do you guys know or tested to pull CRIO images and install crictl on suse 15sp1 ? Here is the tutorial I found for CRICTl but none working for SUSE 15 SP1 https://github.com/cri-o/cri-o/blob/master/tutorials/crictl.md BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Rushi NS Date: Thursday, May 30, 2019 at 7:18 PM To: Alejandro Bonilla , "Le Bihan St?phane (AMUNDI-ITS)" Cc: "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Thanks, Alejandro. Glad to see you back Yes I did all but I see the documentation said ?xfs? not btrfs ? so this is confusing . I got this error on node join . any clue ? is this because of filesystem I0530 19:15:30.262605 13335 states.go:38] === state kubelet.enable applied successfully === I0530 19:15:30.262638 13335 states.go:33] === applying state kubeadm.join === F0530 19:16:45.311529 13335 join.go:153] could not create new bootstrap token BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: caasp-beta on behalf of Alejandro Bonilla Date: Thursday, May 30, 2019 at 7:16 PM To: "Le Bihan St?phane (AMUNDI-ITS)" Cc: "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 I deployed yesterday on NUCs and it worked easily. Install SLES with btrfs, no separate home sir, no swap. Register against SCC, Containers Module and CaaSP Product. Install the pattern as documented, install the packages on all nodes as documented in the section after the VMware chapter, ssh-keygen then ssh-copy-id to all nodes, then do the ssh-agent magic and follow the documentation. Having said that, I succeeded with two deployments yesterday but folks where having problems today - perhaps images changed!? HTH On May 29, 2019 7:12 AM, "Le Bihan St?phane (AMUNDI-ITS)" wrote: Hello all, I am disappointed to see that the CAASP v4 beta version is only available for VMware and Suse Openstack cloud 8. We plan to migrate to version 4 for the network segregation part and have a better provision for the CEPHfs SES and we would like to validate everything we already have on CAASP v3. Do you have a release date for KVM / bare-metal? Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: From rushi.ns at sap.com Sat Jun 1 08:43:25 2019 From: rushi.ns at sap.com (Ns, Rushi) Date: Sat, 1 Jun 2019 14:43:25 +0000 Subject: [caasp-beta] CAASP v4 beta 3 In-Reply-To: <05AFBAA3-10EF-4883-8F1B-08B50B9733C3@sap.com> References: <74b70f0c-eeab-433c-94df-9aef60707995@email.android.com> <05AFBAA3-10EF-4883-8F1B-08B50B9733C3@sap.com> Message-ID: <6BCA6080-8C0C-413F-8785-7DD9E4D1C999@sap.com> Ok I figured out putting PODS with crictl (CRIO ) Installed dashboard and some pods (nginx ) ?seems working all.. Need to start testing other areas (load balancer and storage) BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Rushi NS Date: Saturday, June 1, 2019 at 7:03 AM To: Alejandro Bonilla , "Le Bihan St?phane (AMUNDI-ITS)" Cc: "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Ok my cluster with 3 nodes bootstrapped and Kubernetes is up . however I am running into runtime issues because it does had ?CRIO? runtime which is why pulling standard docker images get issues as I am not able to find CRIO images. Do you guys know or tested to pull CRIO images and install crictl on suse 15sp1 ? Here is the tutorial I found for CRICTl but none working for SUSE 15 SP1 https://github.com/cri-o/cri-o/blob/master/tutorials/crictl.md BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Rushi NS Date: Thursday, May 30, 2019 at 7:18 PM To: Alejandro Bonilla , "Le Bihan St?phane (AMUNDI-ITS)" Cc: "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Thanks, Alejandro. Glad to see you back Yes I did all but I see the documentation said ?xfs? not btrfs ? so this is confusing . I got this error on node join . any clue ? is this because of filesystem I0530 19:15:30.262605 13335 states.go:38] === state kubelet.enable applied successfully === I0530 19:15:30.262638 13335 states.go:33] === applying state kubeadm.join === F0530 19:16:45.311529 13335 join.go:153] could not create new bootstrap token BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: caasp-beta on behalf of Alejandro Bonilla Date: Thursday, May 30, 2019 at 7:16 PM To: "Le Bihan St?phane (AMUNDI-ITS)" Cc: "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 I deployed yesterday on NUCs and it worked easily. Install SLES with btrfs, no separate home sir, no swap. Register against SCC, Containers Module and CaaSP Product. Install the pattern as documented, install the packages on all nodes as documented in the section after the VMware chapter, ssh-keygen then ssh-copy-id to all nodes, then do the ssh-agent magic and follow the documentation. Having said that, I succeeded with two deployments yesterday but folks where having problems today - perhaps images changed!? HTH On May 29, 2019 7:12 AM, "Le Bihan St?phane (AMUNDI-ITS)" wrote: Hello all, I am disappointed to see that the CAASP v4 beta version is only available for VMware and Suse Openstack cloud 8. We plan to migrate to version 4 for the network segregation part and have a better provision for the CEPHfs SES and we would like to validate everything we already have on CAASP v3. Do you have a release date for KVM / bare-metal? Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: From abonilla at suse.com Sat Jun 1 09:06:11 2019 From: abonilla at suse.com (Alejandro Bonilla) Date: Sat, 1 Jun 2019 15:06:11 +0000 Subject: [caasp-beta] CAASP v4 beta 3 Message-ID: Rushi, CRI is fully compatible with docker images. All the images I've deployed so far are docker built. Have fun! -------------- next part -------------- An HTML attachment was scrubbed... URL: From aj at suse.com Sat Jun 1 10:44:59 2019 From: aj at suse.com (Andreas Jaeger) Date: Sat, 1 Jun 2019 16:44:59 +0000 Subject: [caasp-beta] CAASP v4 beta 3 In-Reply-To: <05AFBAA3-10EF-4883-8F1B-08B50B9733C3@sap.com> References: <74b70f0c-eeab-433c-94df-9aef60707995@email.android.com> <05AFBAA3-10EF-4883-8F1B-08B50B9733C3@sap.com> Message-ID: On 01/06/2019 16.03, Ns, Rushi wrote: > Ok my cluster with 3 nodes bootstrapped and Kubernetes is up . however I > am running into runtime issues ?because it does had ??CRIO? runtime > ?which is why pulling standard docker images get issues as I am not able > to find CRIO images. CRI-O and Docker use the same run-time, runC, so no need to change anything on your container images. Also, no need to change your Kubernetes manifest. Rushi, where exactly did you run into a problem? What should we do to avoid that? Andreas -- Andreas Jaeger aj at suse.com Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany GF: Felix Imend?rffer, Mary Higgins, Sri Rasiah HRB 21284 (AG N?rnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From rushi.ns at sap.com Sat Jun 1 18:44:19 2019 From: rushi.ns at sap.com (Ns, Rushi) Date: Sun, 2 Jun 2019 00:44:19 +0000 Subject: [caasp-beta] CAASP v4 beta 3 In-Reply-To: References: Message-ID: <6F49BE06-3695-4EF8-A93E-20BC3E6B7730@sap.com> Hi Alejandro, Yes I read the document that CRI is does support both docker and CRIO (clear containers as well) but somereason it didn?t? get through first BR, Rushi. I MAY BE ONLY ONE PERSON, BUT I CAN BE ONE PERSON WHO MAKES A DIFFERENCE From: Alejandro Bonilla Date: Saturday, June 1, 2019 at 8:06 AM To: Rushi NS Cc: "caasp-beta at lists.suse.com" Subject: Re: [caasp-beta] CAASP v4 beta 3 Rushi, CRI is fully compatible with docker images. All the images I've deployed so far are docker built. Have fun! -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane.lebihan at amundi.com Fri Jun 14 09:36:01 2019 From: stephane.lebihan at amundi.com (=?iso-8859-1?Q?Le_Bihan_St=E9phane_=28AMUNDI-ITS=29?=) Date: Fri, 14 Jun 2019 15:36:01 +0000 Subject: [caasp-beta] CAASP loadbalancer for master Message-ID: Hi all, I prepare environnement for CAAS v4. I have just question about laodbalancer use for master. We have two solution : Use Big IP F5 for loadbalancing, but it's was in another VLAN Use nginx, but for me it's not very resilient. If I lose server, my kubectl can't contact master node, no ? So, I wanted to know what you are using or plan to use, in order to move towards the best solution in the future. Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: From rushi.ns at sap.com Fri Jun 14 09:44:25 2019 From: rushi.ns at sap.com (Ns, Rushi) Date: Fri, 14 Jun 2019 15:44:25 +0000 Subject: [caasp-beta] CAASP loadbalancer for master In-Reply-To: References: Message-ID: I used BIGIP f5 on another VLAN for 3 multi master HA stacked cluster setup , no issues as master stacked HA can listen to traffic on bigip though there will be little latency but that?s just minimal milli seconds latency . Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race Sent from my iPhone please excuse typos and brevity On Jun 14, 2019, at 08:37, Le Bihan St?phane (AMUNDI-ITS) > wrote: Hi all, I prepare environnement for CAAS v4. I have just question about laodbalancer use for master. We have two solution : Use Big IP F5 for loadbalancing, but it?s was in another VLAN Use nginx, but for me it?s not very resilient. If I lose server, my kubectl can?t contact master node, no ? So, I wanted to know what you are using or plan to use, in order to move towards the best solution in the future. Regards, _______________________________________________ caasp-beta mailing list caasp-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/caasp-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane.lebihan at amundi.com Mon Jun 17 03:02:54 2019 From: stephane.lebihan at amundi.com (=?utf-8?B?TGUgQmloYW4gU3TDqXBoYW5lIChBTVVOREktSVRTKQ==?=) Date: Mon, 17 Jun 2019 09:02:54 +0000 Subject: [caasp-beta] CAASP loadbalancer for master In-Reply-To: References: Message-ID: <5983ba272f7940a19044f18d77095012@amundi.com> Thanks for your response. Regards, From: Ns, Rushi Sent: vendredi 14 juin 2019 17:44 To: Le Bihan St?phane (AMUNDI-ITS) Cc: caasp-beta at lists.suse.com Subject: Re: [caasp-beta] CAASP loadbalancer for master I used BIGIP f5 on another VLAN for 3 multi master HA stacked cluster setup , no issues as master stacked HA can listen to traffic on bigip though there will be little latency but that?s just minimal milli seconds latency . Best Regards, Rushi. Success is not a matter of being the best & winning the race. Success is a matter of handling the worst & finishing the race Sent from my iPhone please excuse typos and brevity On Jun 14, 2019, at 08:37, Le Bihan St?phane (AMUNDI-ITS) > wrote: Hi all, I prepare environnement for CAAS v4. I have just question about laodbalancer use for master. We have two solution : Use Big IP F5 for loadbalancing, but it?s was in another VLAN Use nginx, but for me it?s not very resilient. If I lose server, my kubectl can?t contact master node, no ? So, I wanted to know what you are using or plan to use, in order to move towards the best solution in the future. Regards, _______________________________________________ caasp-beta mailing list caasp-beta at lists.suse.com http://lists.suse.com/mailman/listinfo/caasp-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From beta-programs at lists.suse.com Mon Jun 24 06:18:49 2019 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Mon, 24 Jun 2019 14:18:49 +0200 Subject: [caasp-beta] [ANNOUNCE] SUSE CaaS Platform 4.0 Beta 3 is out! Message-ID: <5d10bfa980943_45b3c9a66c676b6@zourite.lab.gb.mail> We are happy to announce the Beta 3 of SUSE CaaS Platform 4.0. SUSE CaaS Platform 4.0 is built on top of SLE 15 SP1 and requires either the JeOS[1] version shipped from the product repositories or a regular SLE 15 SP1 installation. Please note that SLE 15 SP1 is now officially out! Check out the official announcement[2] for more information. Thus you should not use a SLES 15 SP1 environment with the SLE Beta Registration Code anymore. Because the SLE Beta Registration Code has expired now, but you can either use your regular SLE Registration Code or use a Trial. Beta 3 SUSE CaaS Platform 4.0 makes use of skuba (a wrapper for kubeadm) to bootstrap and update a cluster, making the whole process smoother, stable and easier to automate. kubeadm replaces the admin node and the salt states used in previous versions of SUSE CaaS Platform. Updates are implemented with skuba-update, that makes use of the kured tool and the SLE package manager. That being said please check: - Our Major Themes for SUSE CaaS Platform 4.0[3] on the dedicated beta web page, - Our Release Notes[4] for more information, - Known Issues[5] for Beta 3. Changes from Beta 2 - caaspctl has been renamed to skuba In Beta2, the tool for bootstrapping a cluster was named caaspctl. From Beta3, this tool has been renamed to skuba. This is not only a more aquatic name (in the Kubernetes tradition), but also reflects our desire to make this tool more generic. - Beta 3 implements base OS upgrades. Non-interactive updates are applied to nodes on a regular basis; updates that need a reboot (i.e. kernel) will schedule not only the reboot of the node, but the needed kubernetes orchestration. This is implemented in the skuba-update tool which glues zypper and the kured tool (https://github.com/weaveworks/kured). - Deployment instructions for bare metal and how to deploy a Centralized Logging node, for aggregating logs from all the nodes in the kubernetes cluster. - More Quality Assurance were done on Bare Metal installation. For more details, see the Release Notes[6]. Beta Registration codes You should not use a SLES 15 SP1 environment with the SLE Beta Registration Code anymore. Because the SLE Beta Registration Code is expired now but you can either use your regular SLE Registration Code or use a Trial. Registration is not working with your regular key, special Beta Registration Code is required. You need to request one for SUSE CaaS Platform 4.0 Beta Program by contacting us at beta-programs at lists.suse.com[6]. Installation Use the terraform package to install SUSE CaaS Platform. Refer to the Deployment Guide[7]. Architecture and working features: The architecture of SUSE CaaS Platform 4.0 is described here[8]. This build has been tested on SUSE OpenStack Cloud 8, VMware ESXi 6.7.0 and bare metal. We have validated the following features: - Bootstrap a cluster - Deploying with Terraform in SUSE OpenStack Cloud and VMware - Deploying with autoyast for Bare Metal - Adding and removing nodes - Deploying, scaling, and exposing nginx:alpine image - PodSecurityPolicy deployment and conformance - Applying Base OS updates - Centralized Logging Please check our Release Notes[9] for most recent changes and Known Issues[9]. Note that the product is not feature complete yet, we will continue to improve it. Beta Page ?[9] Documentation ?[10] Have fun beta testing! Your SUSE CaaS Platform Team Please refer to our dedicated SUSE CaaSP Beta Program[11] webpage 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. Click here to unsubscribe.[12] [1]:https://www.suse.com/products/server/jeos/ [2]:https://www.suse.com/c/are-you-ready-for-the-worlds-first -multimodal-operating-system/ [3]:https://www.suse.com/betaprogram/caasp-beta/#themes [4]:https://www.suse.com/betaprogram/caasp-beta/#releasenotes [5]:https://www.suse.com/betaprogram/caasp-beta/#knownissues [6]:mailto:beta-programs at lists.suse.com?subject=Requesting%20 SUSE%20CaaSP%204.0%20Beta%20Registration%20Codes&body=Request ing%20SUSE%20CaaSP%204.0 [7]:https://susedoc.github.io/doc-caasp/master/caasp-deployme nt/single-html/ [8]:https://susedoc.github.io/doc-caasp/master/caasp-architec ture/single-html/ [9]:https://www.suse.com/betaprogram/caasp-beta [10]:https://www.suse.com/betaprogram/caasp-beta/#documentati on [11]:https://www.suse.com/betaprogram/caasp-beta/ [12]:mailto:beta-programs at lists.suse.com?subject=Unsubscribe% 20from%20SUSE%20CaaSP%20Beta&body=Unsubscribe%20from%20SUSE%2 0CaaSP%20Beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From lukas.grossar at adfinis-sygroup.ch Wed Jun 26 02:25:18 2019 From: lukas.grossar at adfinis-sygroup.ch (Lukas Grossar) Date: Wed, 26 Jun 2019 10:25:18 +0200 Subject: [caasp-beta] Roadmap for SUSE CaaSP 4 GA release Message-ID: <4cfeb691c5b3c438c3489dcc5e88867366fd3798.camel@adfinis-sygroup.ch> Hi everyone Can you provide any information about a roadmap and possible dates for the final GA (or a least RC) release of SUSE CaaSP 4? We currently working successfully with the Beta 2 and planning an upgrade to Beta 3, but performing the production deploy with a RC or GA release would be preferable. Regards Lukas -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: