Host Setup: SUSE Edge 3.7 Workshop¶

This workshop deploys on a bare metal Linux host with KVM. These steps cover host prep and initial deploy.

Requirements¶

Resource	Minimum
OS	SLES 15 SP6 / SLES 16 / openSUSE Leap 15.6
RAM	40 GiB
vCPU	16
Disk	250 GiB (free in `/var/lib/libvirt/images`)
Network	Internet access during deploy only: lab exercises run fully offline

Install rodeo-cli¶

curl -fsSL https://raw.githubusercontent.com/avaleror/rodeo-cli/main/install.sh | bash

This installs prerequisites (python3, pip, git), clones the repo to /opt/rodeo-cli, creates a venv with system-site-packages (needed for libvirt-python), and symlinks rodeo to /usr/local/bin.

To pin a specific version:

curl -fsSL https://raw.githubusercontent.com/avaleror/rodeo-cli/main/install.sh | bash -s -- --ref v0.16.1

Deploy¶

git clone https://github.com/avaleror/suse-edge-workshop.git
cd suse-edge-workshop
rodeo up

Because you are inside a directory that already contains rodeo-plan.yaml, rodeo up auto-detects the lab, so no separate rodeo init step is needed. It self-escalates with sudo, silently generates ~/.rodeo/secrets.yaml (the rodeo-plan.yaml in this repo references the passwords via ??placeholder notation), wraps the deploy in tmux so a dropped SSH doesn't kill it, and runs the pipeline: kvm_host → vms → boot → rancher → elemental → apply → finalise → custom_scripts. Total time is 30-60 minutes depending on internet speed (Hauler pulls several GB of images). See Lab overview for a detailed breakdown of what each phase does.

If your SSH session drops, re-attach with the session name rodeo up printed at the start (tmux attach -t <name>).

When complete, the success screen shows:

Rancher URL and admin password location
EIB VM SSH command
Edge node MAC/IP reference table
Next steps for the lab guide

Lab runs offline after deploy¶

Once rodeo deploy completes, the lab is fully self-contained. No internet access is needed during the exercises.

During the elemental phase, rodeo-cli automatically populates the Hauler store on the EIB VM with everything students need:

Artifact	Served at	Used in
EIB container image (`edge-image-builder:1.3.4`)	Hauler OCI registry `:5000`	Exercise 3: EIB builds
`elemental-operator` image (the `elemental-register` agent ships inside it)	Hauler OCI registry `:5000`	Exercise 3: Elemental ISO builds
vertex-bank-app image	Hauler OCI registry `:5000`	Exercise 6: Fleet deploy
openSUSE Leap Micro 6.2 SelfInstall ISO	Hauler fileserver `:8080`	Exercise 3: EIB Elemental ISO base
openSUSE Leap Micro 6.2 Default RAW	Hauler fileserver `:8080`	Exercise 3: EIB standalone RAW base
`elemental-register` / `elemental-system-agent` RPMs	`/home/eib-config/rpms/` (side-loaded, public openSUSE source)	Exercise 3: EIB Elemental ISO base, no SCC code needed
`gitea/vertex-bank-app` repo	Gitea `:3000`	Exercise 6: Fleet GitRepo source
`gitea/eib-config` repo	Gitea `:3000`	Exercise 2: students clone this for EIB definitions + scripts

Edge nodes boot with registries.yaml baked in by EIB, pointing all container pulls (docker.io, registry.suse.com, ghcr.io) to the local Hauler registry at 192.168.122.20:5000. Fleet syncs from local Gitea at 192.168.122.20:3000. No GitHub access needed. EIB pulls image definitions and scripts from the eib-config Gitea repo.

See the Disconnected environment reference for full details on what runs offline and why.

Verify before handing to students¶

# Management cluster healthy
ssh -i /root/.ssh/id_ed25519 root@192.168.122.9 \
  "kubectl get nodes && kubectl get pods -n cattle-elemental-system"

# EIB VM + Hauler running, both openSUSE Leap Micro files in the store
ssh -i /root/.ssh/id_ed25519 root@192.168.122.20 \
  "systemctl is-active hauler-registry hauler-fileserver && \
   curl -s http://localhost:8080/ | grep -E 'leap-micro.*iso|leap-micro.*raw'"

# openSUSE Leap Micro base images staged for EIB
ssh -i /root/.ssh/id_ed25519 root@192.168.122.20 \
  "ls -lh /home/eib-config/base-images/"

# Elemental RPMs staged for EIB (side-loaded, no SCC code needed)
ssh -i /root/.ssh/id_ed25519 root@192.168.122.20 \
  "ls -lh /home/eib-config/rpms/"

# Gitea running and both repos present
ssh -i /root/.ssh/id_ed25519 root@192.168.122.20 \
  "podman ps --filter name=gitea --format '{{.Status}}' && \
   curl -s http://localhost:3000/api/v1/repos/gitea/vertex-bank-app \
   | python3 -c \"import sys,json; r=json.load(sys.stdin); print('vertex-bank-app:', r['full_name'])\" && \
   curl -s http://localhost:3000/api/v1/repos/gitea/eib-config \
   | python3 -c \"import sys,json; r=json.load(sys.stdin); print('eib-config:', r['full_name'])\""

# MachineRegistration exists
ssh -i /root/.ssh/id_ed25519 root@192.168.122.9 \
  "kubectl get machineregistration -n fleet-default"

# Edge VMs are defined but off
virsh list --all | grep edge

Everything should be green before students start lab-guide.md.

Tear down¶

sudo rodeo clean --yes

This removes all VMs, disk images, and libvirt network config. The host is left clean.