Setting up the Retail Node Installer (RNI) and booting Target Devices
The Retail Node Installer (RNI) is a collection of scripts that enables network-wide PXE booting of customizable operating systems, referred to as "profiles". It has a lightweight footprint, requiring only Bash, Docker*, and Docker* Compose. Profiles can be any typical Linux* distribution, such as Rancher* OS.
The main executable to set up a device as a Retail Node Installer is
build.sh. This script will automatically build a few Docker images, download necessary files as required by profiles, prepare the PXE boot menu, and launch the following dockerized services:
dnsmasq (provides DHCP and TFTP services)
This document will guide you through the following:
The following is required:
Profile - The git URL for at least one profile is required. You will be asked to paste the URL into the configuration file in the following instructions.
Retail Node Installer - Minimum Recommended Hardware or VM with 2 CPUs, 20GB HD and 2GB of RAM, running any Linux Distro (headless is recommended) that supports Docker.
docker18.09.3 or greater
docker-composev1.23.2 or greater (use the official installation guide)
bashv4.3.48 or greater
Target or Client Device(s) - Bare Metal or Virtual Machine(s) with the necessary specifications for your use case. The profile defines what will be installed on the Target Device.
Note: The Target Devices will be wiped clean during typical usage of the Retail Node Installer.
The Retail Node Installer must have a static IPv4 address. Additionally, the Retail Node Installer must be on an isolated network and serve as the only DHCP server on the network. This means that any existing routers/gateway/switches that are acting as DHCP servers must have DHCP disabled.
Because RNI is OS-agnostic and Docker-based, the configuration of your system's network is not covered in this guide.
Target Devices will be connected on the same LAN as the Retail Node Installer. On target devices, enable PXE Boot in the BIOS if it is not enabled. Most BIOSes have a boot menu option (F12) at POST time. Typically you can press (F12) to alter the boot sequence.
Setting up the Retail Node Installer
Once the prerequisites and network setup have been completed, follow these steps to set up the Retail Node Installer:
Step 1 - Clone the Retail Node Installer repository using your git protocol of choice, and navigate into the cloned directory - use the following code snippet as an example:
git clone -b master https://github.com/intel/retail-node-installer.git retail-node-installer cd retail-node-installer
Step 2 - Copy the sample configuration file
conf/config.sample.yml to a new file titled
cp conf/config.sample.yml conf/config.yml
The config file can look something like this - please modify the values below, this is a reference and is not intended to be a working example:
--- dhcp_range_minimum: 192.168.1.100 dhcp_range_maximum: 192.168.1.250 network_broadcast_ip: 192.168.1.255 network_gateway_ip: 192.168.1.1 network_dns_secondary: 188.8.131.52 host_ip: 192.168.1.11 profiles:- git_remote_url: https://github.com/intel/rni-profile-base-rancheros.git profile_branch: master profile_base_branch: None git_username: "" git_token: "" name: rancher-profile custom_git_arguments: --depth=1
The profiles listed in this file correlate to the PXE boot menu options that the Retail Node Installer will serve to the target device. In this example file, the boot menu option on a target device will list "Clear_Linux_desktop". This example has one profile, however, you can have multiple profiles listed in this configuration file.
Make the following changes to this file to suit your needs.
- Under the profiles section, update the git remote to match the HTTPS-based git remote URL for your profile. Also update git remote branch by setting profile_branch. If it requires any base branch, then update it by setting profile_base_branch for your profile, otherwise, set profile_base_branch to None.
nameof the profile(s) will appear as boot menu option(s) on the target device's PXE menu. It can be any alphanumeric string.
- Specify a GitHub* username and token if needed (using a password is not recommended for security reasons).
- Ensure that the network configuration matches your needs. If values are not specified, Retail Node Installer will default to a
/24network with a DHCP range of
- For special situations, custom git flags can be added on the fly by setting
custom_git_arguments. It must be defined (see next bullet point), so if no custom git flags are needed, specify
- Every profile must have all values defined in the config. For example, you cannot remove
custom_git_arguments; you must specify a value. This is a known limitation.
Step 3 - Run
./build.sh as root from the root folder. This script will perform various tasks, such as downloading files for the configured profiles in
conf/config.yml, generating a PXE boot menu, etc. Depending on the profiles you've selected, the build process can take a few minutes. It is fully automated and hands-off.
Step 4 - Run
./run.sh as root. This will start the Retail Node Installer services. It is safe to press
ctrl+C to quit out of logging safely at any time.
The Retail Node Installer has now been deployed successfully! The next step is to build a target device, which is detailed in the next section.
Building Target Devices
Booting Target Devices
Make sure the Retail Node Installer (RNI) is the only active DHCP server in your LAN. If you have not already, disable DHCP on the router, switch, or any other network interface in your LAN. Connect the target device to your LAN.
Boot the target device while connected to your LAN. Make sure you boot this device from network instead of local disk or cd-rom. This will initiate the PXE boot of your target device from the Retail Node Installer.
After installation, the device will reboot. Manually select the local disk boot option in the PXE menu when it comes up.
If the terminal comes up without an error message and notification to check the error log, then it has built successfully!
You can get a list of all flags supported by running
Troubleshooting the Retail Node Installer
Log information is available in
rni.log in the root folder. To monitor the logs, run
docker-compose logs -f
If it becomes necessary to delete the Retail Node Installer containers and re-create them, run
./run.sh -f (assuming there are no target devices in your network that are attempting to boot while running this command).
You can use
./run.sh -r to restart the Retail Node Installer containers.
For any other problems that you may encounter during deployment, please consult the Known Limitations section.
Distributions including Rancher, Ubuntu, ClearLinux and Windows have been provided as a reference design as part of our current release. This section is not required for setting up a Retail Node Installer and building target devices, but it provides valuable information about profiles, templating, and file downloads that will help you build your own custom profiles.
To make use of Windows Profile certain prerequisites need to be met. For more details please see this.
Kernel arguments can be specified in a file called
conf/config.yml in the profile's repository, not in Retail Node Installer itself, like this:
--- kernel_arguments: rancher.cloud_init.datasources=[url:http://@@HOST_IP@@/profile/@@PROFILE_NAME@@/dyn-ks.yml]
Variables surrounded by
@@ symbols are handled by the templating engine in Retail Node Installer. Please read Templating for more information on this topic.
Retail Node Installer has a few essential templating capabilies that assist with profile configuration.
In a profile's
conf/config.yml, for the
kernel_arguments variable only, the following template variables are supported:
Any file with the suffix
.rnitemplate in a profile will support all of the above as well as:
File Downloads and Dependencies
A profile will likely require external files in order to boot and install. This is solved by specifying them in
conf/files.yml inside the profile repository, not in Retail Node Installer itself. For an example, please see the
files.yml.sample in the Rancher profile.
- A custom profile can be developed and used with existing base profiles.
- Base profile will have core logic of installing OS. Please see
pre.shscript in ClearLinux profile on
- Base profile will also
post.shscript for clean up activities. Please see
post.shscript in ClearLinux profile on
- Custom profile can have
profile.shto support custom features. Please see
profile.shscript in ClearLinux profile on
- Finally custom profile will have
bootstrap.shwhich will eventually call
pre.shfrom base branch,
profile.shfrom custom branch and then call
post.shfrom base branch again. Please see
bootstrap.shscript in ClearLinux profile on
- Base profile will have core logic of installing OS. Please see
- To see more details on how to change Edgebuilder configuration to use custom profile, see step 2 under Installation
conf/config.ymlfile must specify ALL values comprehensively, as shown in the
conf/config.sample.yml. Please use
""for empty values.
- IPv6 is not supported.
- Retail Node Installer must be run on a Linux-native file system, such as
ext4. Filesystems that cannot properly preserve file permissions are not supported.
- On some distributions of Linux (such as newer versions of Ubuntu 18.04),
systemd-resolvedis already running a DNS server on
localhost. This will cause the Retail Node installer to fail to start due to port binding conflicts. To fix this:
./build.shnormally. It will fail at the final deployment step.
/etc/systemd/resolved.confto include the line
- This step will cause your network connection to drop. Run
sudo systemctl daemon-reload && sudo systemctl restart systemd-resolved.service
./run.shto restart the Retail Node Installer services.
- Test that network connectivity works.
- Proceed to deploy your target devices.
- Retail Node Installer's usage of
aws-clican cause keyring issues on desktop versions of Linux. Consider disabling your distro's keyring service, or alternatively, use a headless distribution such as Ubuntu server edition to resolve the issue.
Setting up the Retail Workload Orchestrator (RWO)
RWO can be built and installed using Local Installation.