nodes_up N in setup.sh creates node1 to nodeN, up to 9. Each node is a podman container running AlmaLinux 10, with systemd, sshd, cron and dnf. They sit at 10.99.1.11 and up, with their names in /etc/hosts.
Helpers: in_node [-i] NAME CMD, nodes_names, node_addr and nodes_wait.
The containers are kept, so a student's work survives a VM reboot. le-lab-nodes.service starts them again at boot.
Reset runs nodes_down. It removes the containers, the network, the unit, the images and the hosts lines, and removes podman too if setup installed it.
docs/writing-labs.md has a new "Managed nodes" section. It says what works in a node and what doesn't (SELinux, storage, chronyd, the reboot module, host names), and tells authors to give those tasks to the control node.
First lab: EX294 3.1 "Preparing managed nodes". It passes on AlmaLinux with and without firewalld. LFCS 2.4 also still passes with the new reset step.
Managed nodes for the EX294 (Ansible) labs.
- `nodes_up N` in setup.sh creates `node1` to `nodeN`, up to 9. Each node is a podman container running AlmaLinux 10, with systemd, sshd, cron and dnf. They sit at `10.99.1.11` and up, with their names in `/etc/hosts`.
- Helpers: `in_node [-i] NAME CMD`, `nodes_names`, `node_addr` and `nodes_wait`.
- The containers are kept, so a student's work survives a VM reboot. `le-lab-nodes.service` starts them again at boot.
- Reset runs `nodes_down`. It removes the containers, the network, the unit, the images and the hosts lines, and removes podman too if setup installed it.
- `docs/writing-labs.md` has a new "Managed nodes" section. It says what works in a node and what doesn't (SELinux, storage, chronyd, the reboot module, host names), and tells authors to give those tasks to the control node.
- First lab: EX294 3.1 "Preparing managed nodes". It passes on AlmaLinux with and without firewalld. LFCS 2.4 also still passes with the new reset step.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Managed nodes for the EX294 (Ansible) labs.
nodes_up Nin setup.sh createsnode1tonodeN, up to 9. Each node is a podman container running AlmaLinux 10, with systemd, sshd, cron and dnf. They sit at10.99.1.11and up, with their names in/etc/hosts.in_node [-i] NAME CMD,nodes_names,node_addrandnodes_wait.le-lab-nodes.servicestarts them again at boot.nodes_down. It removes the containers, the network, the unit, the images and the hosts lines, and removes podman too if setup installed it.docs/writing-labs.mdhas a new "Managed nodes" section. It says what works in a node and what doesn't (SELinux, storage, chronyd, the reboot module, host names), and tells authors to give those tasks to the control node.