Satellite - Build New Client Systems


This article provides an outline of how to build a new, standard Client system (desktop or laptop/portable) with RedHat 8 (RH8) using Satellite to provide the installation data.

This document should NOT be used to REBUILD a system that currently has an entry on the Satellite platform.

It is possible to register a pre-built system to Satellite. This procedure is not covered in this guide.

Original Source (for primary updates) - https://uoleeds.atlassian.net/l/c/KL3tN3yh
KB Permalink (child copy) - https://it.leeds.ac.uk/it?id=kb_article&sysparm_article=KB0016032

Initial Assumptions

Not all client systems are the same. This guide is based on an assumed standard system with a simple boot Hard Disk Drive (HDD) / Solid State Disk (SSD) / Non-Volatile Memory Express (NVMe) device (henceforth referred to as the Boot Drive), default VGA/DVI/HDMI/DP graphics (i.e. the video outputs to a monitor without the need for special kernel drivers) and a single wired Local Area Network (LAN) / ethernet port (again without the need for special kernel drivers). Non-standard systems (e.g. those with RAID arrays, GPUs, etc) MAY work with this guide but they may also need extra configuration in order to get them to boot, display and connect properly.

Other assumptions include standard University requirements / procedures for BIOS protection, system registration, electrical safety testing (PAT), asset assignation, etc. This guide will not provide detail on these items.

For the purposes of this article, we will assume that we are building a laptop system with a single, NVMe Boot Drive. The name for the system used in this guide will be uol-lap-example01. The guide will highlight any differences between laptop and desktop builds as they arise. It will be built on the ‘Engineering’ network as we know that this VLAN will allow Satellite to netboot. Note - a system can be transferred to another subnet after the build process has completed - the relevant entries in DDI and Satellite should be adjusted accordingly.

System Registrations

The system should be named/registered with the CMDB, Asset Management and, if required, Electrical Safety systems. These registrations are outside the scope of this article.

The system must NOT be added to the Active Directory (AD) - if an AD entry exists then it must be removed as Satellite creates an item in a specified location and cannot complete if there is already another instance in place.

Network Registration

As mentioned in the Initial Assumptions, uol-lap-example01 will be built on/using the ‘IT staff’ subnet - VLAN152, 129.11.152.0/22. We will expand this guide to add other subnets as they are tested and found to work.

Satellite Registration

Satellite02 Access

Some users may have limited access to the Satellite02 system or no access at all. If you find that you cannot perform the operations listed below then please raise a Request with the Linux team and ask them register the system on your behalf. Please include:

Adding a New Device to Satellite02

 

 

NetBooting the New Device to Install the Operating System

WARNING - 'NetBooting for Build' requires a good, stable, fast, wired connection otherwise build failures and errors may be encountered.

(note, the green bar at the bottom shows that the system is in install mode - at this point it is possible to use another networked system to SSH in to the build process to monitor and/or interact - useful if you want to leave the system and work from another location. The ‘Install Mode - SSH Interaction’ is detailed in the standalone section, below)

Note - occasionally the system stops at the section before ‘Progress’ (in between the === lines) because it needs further information - this is usually when the disk array isn’t as expected and requires manual intervention to specify the disk partitioning. However, normally, the install process will continue automatically.

 

puppet agent -t

repeatedly until it shows no changes. At this point reboot the system again.


If you wish to expedite this (perhaps you don’t need another hot beverage) then log in with the root account (if available) and run

puppet agent -t

repeatedly until it shows no changes. At this point reboot the system again.

Do NOT power off or restart the system until the job has completed.

 

 

Then log out (do not power off unless moving the device) and let the new owner know that they should attempt to remote in to the system and set their passphrase.

It may be necessary to change the system’s IP/Subnet in DDI. If this is the case then Satellite will update when the system next checks in.

Install Mode - SSH Interaction