Uyuni for Retail uses a layered architecture:
The first layer contains the Uyuni Server.
The second layer contains one or more branch servers to provide local network and boot services. It also contains one or more build hosts.
The final layer contains any number of deployed point-of-service terminals.
Branch servers should be physically located close to point-of-service terminals, such as in an individual store or branch office. We recommend you have a fast network connection between the branch server and its terminals. Branch servers provide services for PXE boot, and act as an image cache, Salt broker, and proxy for software components (RPM packages). The branch servers can also manage local networking, and provide DHCP and DNS services.
Uyuni for Retail Branch Servers are implemented as enhanced Uyuni Proxies. For technical background information on Uyuni Proxies, see Install Uyuni Proxy with openSUSE Leap.
You can use branch servers in different network configurations, depending on your installation requirements.
The branch servers are in the same network as the Uyuni Server, and terminals use an isolated branch network. In this configuration, the branch servers are in the corporate network, and provide all DHCP, DNS, PXE, FTP, and TFTP services to the terminals in the branch networks.
The branch servers are in separate branch networks, along with the terminals they manage. In this configuration, external routers provide DHCP and DNS services to the branch servers and the terminals, and the branch server provides PXE, FTP, and TFTP services to the terminals in their branch network.
The branch server and the terminals are connected to the same network as the Uyuni Server. In this configuration, external routers provide DHCP and DNS services to the branch servers and the terminals, and the branch server provides PXE, FTP, and TFTP services to the terminals in their branch network.
For more information about network administration on Uyuni for Retail, see Network Administration.