[caasp-beta] CAASP v4 beta 3

[Ns, Rushi]

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 <caasp-beta-bounces at lists.suse.com> on behalf of Alejandro Bonilla <abonilla at suse.com>
Date: Thursday, May 30, 2019 at 7:16 PM
To: "Le Bihan Stéphane (AMUNDI-ITS)" <stephane.lebihan at amundi.com>
Cc: "caasp-beta at lists.suse.com" <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)" <stephane.lebihan at amundi.com> 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: <http://lists.suse.com/pipermail/caasp-beta/attachments/20190531/9693d3e3/attachment.html>