rancher-users #elemental

elemental

silly-airline-38945

12/05/2022, 9:32 AM

Hi, Im I correct to assume that the when using emulate-tpm, the tpmhash is bound to the built iso? No tpm support in my current vcenter so testing emulation. Booting multiple vms from same iso has the same hash, hence only one entry in mchineinventory.

shy-hamburger-95730

12/05/2022, 12:58 PM

Is there are a way to utilize ranchers cluster feature to spin up/scale the actual vms for elemental?

shy-hamburger-95730

12/05/2022, 4:57 PM

How would one install rancher itself on elemental? I saw @ripe-mechanic-63260s "watson" PoC, but I fail to see how to register multiple nodes to it? I could create a elemental cluster via rancher, then install rancher on it, I suppose. But "rancher in rancher" didnt work last time I tried it, iirc.

hundreds-hospital-60917

12/23/2022, 4:11 PM

Howdy ! Just in time for the x-mas break, we've added instructions how to run Elemental on Raspberry Pi ! Just head over to our development documentation and follow the instructions. If you have other ARM boards you want to run Elemental on, we'd love to hear from you.

🍓 3

🙌 5

🎉 3

ripe-mechanic-63260

12/30/2022, 8:39 AM

Hey Ethan, for that you could build your own iso. The default user/pass for the iso is located on https://github.com/rancher/elemental/blob/main/framework/files/system/oem/04_accounting.yaml so you could modify that and then build your iso with the

make build && make iso

targets

strong-shoe-72392

01/05/2023, 7:14 PM

Hey all! Just kicking the tires on the new Elemental on Raspberry Pi instructions. One quick piece of feedback, when I was using a newer LG 4k monitor, the screen would go black toward the end of the Elemental boot process and would not come back. I switched to an older (not 4k) Dell monitor and the screen comes back at that part of the boot process. I'm assuming a driver or resolution issue but just wanted to throw it out there for those working on the new releases of the TEAL Elemental for Pi. Thanks!

👍 1

strong-shoe-72392

01/05/2023, 10:52 PM

Has anyone else seen the following errors when registering a Raspberry Pi 4 k3s cluster (using elemental-operator 1.1.0). The Raspberry Pi boots up and reaches out to Rancher MCM but it seems to fail to establish a websocket connection. elemental-operator pod logs

time="2023-01-05T22:41:38Z" level=info msg="Incoming HTTP request for /elemental/registration/9tb...9"
Thu, Jan 5 2023 5:41:39 pm	time="2023-01-05T22:41:39Z" level=info msg="Negotiated protocol version: 5"
Thu, Jan 5 2023 5:41:39 pm	time="2023-01-05T22:41:39Z" level=error msg="websocket communication interrupted: unknown message"

elemental client logs

Jan 05 22:46:04 rancher-31733 elemental[1417]: time="2023-01-05T22:46:04Z" level=info msg="Enable TPM emulation"
Jan 05 22:46:04 rancher-31733 elemental[1417]: time="2023-01-05T22:46:04Z" level=info msg="Connect to <https://rancher>.<redacted>"
Jan 05 22:46:05 rancher-31733 elemental[1417]: time="2023-01-05T22:46:05Z" level=info msg="Using TPMHash <redacted> to dial <wss://rancher>.<redacted>/elemental/registration/9tb...9"
Jan 05 22:46:05 rancher-31733 elemental[1417]: time="2023-01-05T22:46:05Z" level=debug msg="Start TPM attestation"
Jan 05 22:46:06 rancher-31733 elemental[1417]: time="2023-01-05T22:46:06Z" level=info msg="TPM attestation successful"
Jan 05 22:46:06 rancher-31733 elemental[1417]: time="2023-01-05T22:46:06Z" level=debug msg="elemental-register protocol version: 8"
Jan 05 22:46:06 rancher-31733 elemental[1417]: time="2023-01-05T22:46:06Z" level=info msg="Negotiated protocol version: 5"
Jan 05 22:46:06 rancher-31733 elemental[1417]: time="2023-01-05T22:46:06Z" level=info msg="Send SMBIOS data"
Jan 05 22:46:06 rancher-31733 elemental[1417]: time="2023-01-05T22:46:06Z" level=info msg="Send system data"
Jan 05 22:46:06 rancher-31733 elemental[1417]: time="2023-01-05T22:46:06Z" level=debug msg="system data:..."
Jan 05 22:46:06 rancher-31733 elemental[1417]: time="2023-01-05T22:46:06Z" level=error msg="failed to register machine inventory: failed to send system data: websocket: close 1006 (abnormal closure): unexpected EOF"

This appears to be the same error that was addressed by https://github.com/rancher/elemental/issues/346 and https://github.com/rancher/elemental-operator/issues/176 Any help is greatly appreciated! Thanks!

strong-shoe-72392

01/11/2023, 5:29 PM

On the latest version of the elemental-teal ISO x86, I'm seeing the following error

time="2023-01-11T17:26:09Z" level=warning msg="Detected old elemental-register client: cloud-config data may not be applied correctly"

And it does not execute my cloud-config to set the username/password to be able to log into the instance after installation. Any ideas? I'm using Elemental-Operator 1.1.0.

mysterious-whale-87222

01/12/2023, 5:39 PM

Hey Everybody, short question: How to set rke2/k3s command line params like `--kubelet-arg`by elemental? Didn't find anything in docs.

loud-sundown-69515

01/16/2023, 11:02 PM

On the Quickstart guide it says having rancher running is a requirement. Looking at ripping out K3os. 1. Does elemental provide that same experience? Specifically bringing up bare VMs into a multi node cluster? 2. Is cilium supported?

careful-piano-35019

01/16/2023, 11:10 PM

Hi Jesse. Yes (one of) Elemental purpose is to enable deploying and managing multiple multi nodes clusters from Rancher on bare metal (but also on virtual machines)

careful-piano-35019

01/16/2023, 11:12 PM

it leverages Rancher provisioning so it can deploy any configuration possible with Rancher

careful-piano-35019

01/16/2023, 11:15 PM

with K3s => https://ranchermanager.docs.rancher.com/reference-guides/cluster-configuration/rancher-server-configuration/k3s-cluster-configuration#clust[…]g-file

careful-piano-35019

01/16/2023, 11:15 PM

with RKE2 => https://ranchermanager.docs.rancher.com/reference-guides/cluster-configuration/rancher-server-configuration/rke2-cluster-configuration#conta[…]vider

silly-airline-38945

01/17/2023, 12:19 PM

Hi, testing the elemental-iso-add-registration from the docs. Its failing on

<http://ftp.lysator.liu.se|ftp.lysator.liu.se> 404 not found

Is this the one to use or should the elemental-iso-build be used?

careful-piano-35019

01/17/2023, 12:29 PM

it looks like an issue related to openSUSE infrastructure

careful-piano-35019

01/17/2023, 12:33 PM

can you try

wget <https://download.opensuse.org/repositories/isv:/Rancher:/Elemental:/Stable:/Teal53/media/iso/elemental-teal.x86_64.iso>

careful-piano-35019

01/17/2023, 12:33 PM

(assuming you're trying Stable and x86_64)

loud-sundown-69515

01/17/2023, 1:09 PM

@careful-piano-35019 thanks for the reply, so I could use elemental like K3os. Stand up a multi node cluster on VMs with k3s or rke2 as the k distro and cilium as the networking and ingress controller. Would like to build this out locally before looking at use in a production setting.

careful-piano-35019

01/17/2023, 1:10 PM

In a similar way, yes. Main difference is that Rancher is required for the orchestration

careful-piano-35019

01/17/2023, 1:11 PM

Big advantage is that you'll get regular OS updates distributed as OCI image

loud-sundown-69515

01/17/2023, 1:24 PM

So I need to stand up an rke2 cluster with rancher to then provision elemental nodes?

careful-piano-35019

01/17/2023, 1:25 PM

yes, or one node k3s is fine

👍 1

careful-piano-35019

01/17/2023, 1:25 PM

it's a bit work at the beginning that you gain later 🙂 bc you can basically deploy without any access to the nodes

careful-piano-35019

01/17/2023, 2:23 PM

the ISO is customized with your rancher URL and registration endpoint, and when you start your VM, it will contact Rancher and OS setup and control plan (K3s or RKE2) will be setup and you'll get your kubeconfig from Rancher dashboard

sparse-monitor-30665

01/18/2023, 8:25 PM

Hi Everyone, sorry if this has been discussed before, but I don't see anything recent, and there's nothing about it in the docs.... What's the best way to go about formatting and mounting additional disks (with lvm?) for /var/lib/longhorn? I have tried adding commands in the Cloud Config stage, or with "Plans", but neither worked very well, and I could not get the disk to mount unless I did so manually. Perhaps I'm missing something, or is the general consensus to use the boot disk and increase it's size as needed? With an "Instructions" Plan I was able to get the LV created, but that only runs once so I can't mount it there. I've tried to create and mount it with the cloud-config: runcmd, but it just fails to ever execute.

INFO[2023-01-18T19:28:39Z] Applying 'Cloud init' for stage 'boot'. Total stages: 1

INFO[2023-01-18T19:28:39Z] Processing stage step ''. ( commands: 2, files: 0, ... )

ERRO[2023-01-18T19:28:39Z] Udev database has incomplete information about device /dev/sda.

/dev/sda: Failed to get external handle [udev].

Udev database has incomplete information about device /dev/sda1.

/dev/sda1: Failed to get external handle [udev].

Udev database has incomplete information about device /dev/sda2.

/dev/sda2: Failed to get external handle [udev].

Udev database has incomplete information about device /dev/sda3.

/dev/sda3: Failed to get external handle [udev].

Udev database has incomplete information about device /dev/sda4.

/dev/sda4: Failed to get external handle [udev].

Udev database has incomplete information about device /dev/sda5.

/dev/sda5: Failed to get external handle [udev].

Udev database has incomplete information about device /dev/sdb.

/dev/sdb: Failed to get external handle [udev].

Device /dev/sdb excluded by a filter.

: failed to run if test -z "$(blkid /dev/rancher/longhorn)"; then vgcreate rancher /dev/sdb && lvcreate -l 100%FREE -n rancher/longhorn && mkfs -t ext4 -L longhorn /dev/rancher/longhorn; fi: exit status 5

Same with the mount statement after it

if test "$(blkid /dev/rancher/longhorn)"; then mount ... fi

Cheers!

sparse-monitor-30665

01/24/2023, 2:58 PM

Expected behaviour??? In Rancher Manager, if I delete a cluster created from Elemental Machines, the MachineInventory gets removed. Ideally I would want to reuse these machines to either re-create the cluster, or be used in other clusters. Currently I have been reinstalling to get it back. Is there a better way to go about this? Is this expected or am I doing something wrong (maybe I'm not waiting long enough?) When the cluster gets removed, is there steps taken on the machines to clean up the kube install and reset it, or is there a way I can add this in?

orange-airplane-98016

01/24/2023, 10:35 PM

@orange-airplane-98016 has left the channel

strong-shoe-72392

01/31/2023, 9:13 PM

Hello again! Are there any other resources that need to be installed to use the Elemental OS Upgrade capability besides the prerequisites here - https://elemental.docs.rancher.com/next/quickstart/#what-is-the-rancher-elemental-stack- ? I tried to perform an Elemental Teal OS Upgrade on a Raspberry Pi 4 (that successfully provisioned k3s using the Quickstart and raw image for RPi) using the following:

apiVersion: <http://elemental.cattle.io/v1beta1|elemental.cattle.io/v1beta1>
kind: ManagedOSImage
metadata:
  name: elemental-rpi-upgrade-demo
  namespace: fleet-default
spec:
  # Set to the new Elemental version you would like to upgrade to or track the latest tag
  osImage: "<http://registry.opensuse.org/isv/rancher/elemental/dev/teal53/15.4/rancher/elemental-teal/5.3:1.1.0-60.7|registry.opensuse.org/isv/rancher/elemental/dev/teal53/15.4/rancher/elemental-teal/5.3:1.1.0-60.7>"
  clusterTargets:
    - clusterName: elemental-rpi-cluster

My current version according to /etc/os-release is:

IMAGE_REPO="<http://registry.opensuse.org/isv/rancher/elemental/dev/teal53/15.4/rancher/elemental-teal/5.3|registry.opensuse.org/isv/rancher/elemental/dev/teal53/15.4/rancher/elemental-teal/5.3>"
IMAGE_TAG="1.0.0-40.2"

When applied, I see that Fleet tries to make a new bundle but errors out on what appears to be missing CRDs:

elemental-rpi-cluster-managed-system-agent
ErrApplied(1) [Cluster fleet-default/elemental-rpi-cluster: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "system-agent-upgrader" namespace: "cattle-system" from "": no matches for kind "Plan" in version "<http://upgrade.cattle.io/v1|upgrade.cattle.io/v1>" ensure CRDs are installed first, resource mapping not found for name: "system-agent-upgrader-windows" namespace: "cattle-system" from "": no matches for kind "Plan" in version "<http://upgrade.cattle.io/v1|upgrade.cattle.io/v1>" ensure CRDs are installed first]]

I even attempted to install the Rancher System-Upgrade-Controller into our Rancher Server/MCM cluster as it looked like it had some of those CRDs, but that didn't fix anything. Did I miss a step? Is this not yet supported for Raspberry Pis (although it seems to be failing before the bundle is created anyway)? As usual, any help is greatly appreciated!

refined-analyst-8898

03/25/2023, 12:58 AM

Should I use Elemental for the node image when creating an RKE2 cluster in Rancher with Harvester as cloud provider? I was looking for a good node image anyway, and just heard about Elemental. I was using the Ubuntu Minimal Cloud image because it works with cloud-init and doesn't require an interactive installation step. I am also considering the Tumbleweed Minimal Cloud image which appears to have that same capability. My goal is to learn Rancher and Harvester and Longhorn and automate as much as practical.

Title

refined-analyst-8898

03/25/2023, 12:58 AM

If that's a viable and advisable path, then I think I need to compose a bootable ISO with the CLI. It's not yet clear whether I need to operate a separate Elemental control plane or it's part of Rancher or Harvester.

careful-piano-35019

03/27/2023, 8:55 AM

It's part of Rancher, not Harvester directly

refined-analyst-8898

03/27/2023, 10:51 AM

I found a working configuration with the LEAP cloud image. Now I think Elemental is more about the toolkit for customizing an image than it is about an alternative, curated installation media. I'll keep an eye out for more information about Elemental, but it is not the prerequisite that I believed it might be for using the harvester node driver. I would love to know how the capabilities compare with Packer, or if that's not an apples to apples comparison, to have my view corrected.

careful-piano-35019

03/27/2023, 10:56 AM

Elemental https://elemental.docs.rancher.com/ is a few things 🙂 it relies on the toolkit https://rancher.github.io/elemental-toolkit/docs/ which is used to craft the images indeed, I would not compare it apples to apples to Packer (more opiniated and specific) There is an Operator & UI Extension for Rancher also and the full story is to organize the deployment and management of clusters without any interaction on the target systems (in a secure way) Elemental nodes are prepared to boot and reach out to a Rancher instance and the 'plan' is applied to the nodes

🙂 1

openSUSE Leap Cloud images are indeed a good choice to be used in regular provisionning of clusters from Rancher (qcow2 on Harvester)

refined-analyst-8898

03/27/2023, 11:20 AM

A noble goal: non-interactive node mgmt. Presently, I can't think of any immediate need to log in to my LEAP-based nodes, but they're young, yet. I admit there's probably a more K8sish way to go about things like packet sniffing and open files inspecting and the like, but I haven't found those tools yet. If complete life cycle management is an aim of Elemental, then I will expect good things! Appreciate the insights.

View count: 4