Register Hosts
A host is registered once and stays registered for its whole life. It boots the ISO of its OS and architecture, registers with the global cluster as a MachineInventory, and installs Alauda OS to the system disk that you select. The registered host is then an available host until a cluster takes it through one of the pools of that cluster; see How It Works.
Before you start, create the registration and the ISO of the host's OS and architecture as described in Prepare Alauda OS for Hosts.
Run the ac commands on this page from a machine where ac is logged in to the platform.
TOC
Available HostsPrepare the HostsDisks and Boot OrderClockNetwork in the Live ISOarm64 HostsBoot the HostsSelect the System DiskConfirm the RegistrationTroubleshootingNext StepsAvailable Hosts
An available host is a MachineInventory that:
- Is
Ready=True. - Has
status.install.phase=Installed. - Has a plan Secret in
status.plan.secretRef.name. - Is listed in no
MachineInventoryPool.
List the hosts:
A host is available when:
READYisTrue.PHASEisInstalled, or<none>for a host registered before ACP 4.5.PLANis not<none>.POOLis<none>. For a host that a pool lists,POOLshows that pool.
ARCH and OS show the architecture and OS of the host. Hosts named global-* belong to the global cluster. Do not put them into the pools of a workload cluster.
Prepare the Hosts
Prepare every host as follows before it boots the ISO. Before the first host boots, open the network flows in Network Connectivity.
Disks and Boot Order
Before a host boots the ISO, classify every disk and virtual disk on it. Record the OS install target and the disks that must keep their data:
- Wipe the OS install disk and any obsolete boot disk, so that the host boots the ISO and not an old OS.
- The installation wipes leftover system partitions from an earlier installation (
COS_*labels) on other disks. When a disk cannot be wiped safely, the host stops before installing. It lists the disk instatus.install.staleSystemDisksof itsMachineInventory, withaction: Blockedand the reason. Clean that disk, then boot the host from the ISO again. - Boot the virtual CD or ISO first. On virtual machines where ejecting the CD does not take effect, boot from disk first and CD second.
Clock
Make sure that every host has the correct time when it boots the ISO: the same time zone on every node, and at most 10 seconds of difference between nodes, as in Node Checks. Nothing in this procedure checks the time for you. A host with the wrong clock prevents the control plane from coming up.
- Make the site NTP servers reachable on UDP
123, and set them as the NTP servers of the cluster incluster.ntpServersofinstall-config.yaml. Every node then syncs to them through chronyd from its first boot as a node. A production cluster should not depend on public NTP. - Set the clock in the BIOS/UEFI setup or through the BMC. You cannot set it from an OS, because the install disk is wiped. Keep the hardware clock on UTC.
- Compare the clocks of the hosts with each other. The difference across the hosts of one cluster must stay within 10 seconds.
- After the nodes are
Ready, confirm the time withtimedatectlandchronyc trackingon each node.
A Day-2 chrony MachineConfig, as in Configuring the Chrony Time Service, does not replace these steps, because it configures only running nodes.
Network in the Live ISO
If a host gets no DHCP address in the live ISO, configure it from the host console before you wait for registration:
arm64 Hosts
An arm64 host must provide SMBIOS data. An arm64 machine without SMBIOS cannot register.
Boot the Hosts
Boot each host from the ISO of its OS and architecture. The ISO is built on the global cluster as described in Create the Registration and the ISO. Download the ISO from the download URL and verify it as described in Verify the ISO. If the URL is empty or has expired, rebuild the ISO as described in Rebuild the ISO. To see the registrations, the ISO image that each one is built from, and the current download URL, run:
The tag in BASE names the OS, the architecture, and the ACP version of the ISO.
Each host registers as a MachineInventory named <name>-<system-uuid>, where <name> is the name of the registration. The host then reports its disks and waits in the live environment until you select its system disk. If the host gets no DHCP address in the live ISO, configure the network as described in Network in the Live ISO.
Select the System Disk
Every host waits until you select its system disk, even a host with only one disk. List the hosts, and the disks that a waiting host reports:
A waiting host shows AwaitingTarget. IP is the address that the host uses to reach the global cluster, so that you can match an inventory to a host. Each candidate line prints these values:
- The disk ID.
- Whether the disk can be selected.
- The device path of the disk in the live environment.
- The size of the disk in bytes.
- The reasons why the disk cannot be selected, if any.
Identify the system disk by its size and path. Select it by its ID while the host is still in the live environment:
- Select a disk that shows
true, using its ID exactly as printed. - The phase changes to
Installing, and the host installs Alauda OS to that disk and reboots. The selection cannot be changed after that. - If the annotation is rejected because the host was not seen recently, make sure that the host is still running the ISO, and run the command again.
- Selecting a disk needs
patchonmachineinventoriesandupdateonmachineinventories/installtargetincpaas-system.
Confirm the Registration
List the hosts with the command in Available Hosts. Use a host only when it:
- Shows
READYTrue,PHASEInstalled, and aPLANother than<none>. - Shows in
ARCHandOSthe values of theos.baremetal.alauda.io/archandos.baremetal.alauda.io/idlabels that the registration sets. A host without these labels is treated asamd64with Alauda OS M55. - Has a
spec.observedNetworkthat matches the expected NIC of the host, when the host must keep its install-time IP each time it is reinstalled.
Record the exact MachineInventory names for the pools. When a host does not meet these conditions, see Troubleshooting.
Troubleshooting
Next Steps
- Create a Cluster from available hosts.
- Add nodes or a worker node group to a cluster: Manage Nodes on Bare Metal.