...
The RC (when installed on bare metal, Rover and Unicycle genesis nodes boot via their VLAN tagged 'host' interfaces which are pre-provisioned on the serving TOR switches with LAG bonding. Since booting occurs before the linux kernel can bring up its LAC-P signaling the TOR switches must be configured to pass traffic on their primary (first) link before the LAG bundle is up.
...
The 'host' network interfaces on all DHCP clients and servers must be located on the same L2 network so that the DHCP Request messages broadcast from the client reach the server and vice versa. Alternatively DHCP helper/relay functionality may be implemented on the TOR to which the DHCP clients are attached to allow inter subnet DHCP operation between DHCP client and server.
<Update to show RC, Rover, Genesis as Clients and Build server and RC as servers>
DHCP, HTTP PXE and PXE Booting
...
In R1 the 'host' network has been verified as a single L2 broadcast domain.
The RC DHCP/HTTP PXE process flow is summarized below.
| draw.io Diagram | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
In R1 the 'host' network has been verified as a single L2 broadcast domain. It is possible to split the 'host' network spanning the WAN into multiple routed L2 domains using DHCP helper/relay functionality on the Rover's TOR but this is unverified in R1
The Rover DHCP/HTTP PXE process flow is summarized below.
| draw.io Diagram | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
It is possible to split the 'host' network spanning the WAN into multiple routed L2 domains using DHCP helper/relay functionality on the Rover's TOR but this is unverified in R1.
Unicycle Pod Deployment
A Unicycle pod's genesis node is configured by the Redfish API calls issued by the RC to make DHCP Requests and then HTTP PXE boot over its vlan tagged 'host' network interface.
...
Unicycle masters and workers (all unicycle nodes other than genesis) are configured by the MaaS server running on the genesis node to PXE boot over the remote site's 'pxe' network.
It is possible to split the 'host' network spanning the WAN into multiple routed L2 domains using functionality such as DHCP helper/relay but this is unverified in R1The unicycle DHCP/HTTP PXE/PXE process flow is summarized below.
| draw.io Diagram | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
It is possible to split the 'host' network spanning the WAN into multiple routed L2 domains using functionality such as DHCP helper/relay on the Unicycle genesis TOR but this is unverified in R1. Note: this is not applicable to the other nodes in the unicycle pod as the DHCP and PXE boot process is supported over the local 'pxe' network.