...
Regional Controller Deployment
The RC makes DHCP Requests which must be Responded to When installed on a bare metal server, the RC is configured by the Redfish API calls issued by the Build Server via the to make DHCP Requests and then HTTP PXE boot over its vlan tagged 'host' network L2 domaininterface.
The RC is configured by the Redfish API calls issued by the Build Server to acts as the DHCP and HTTP PXE boot from server for the RC via its own 'host' network interface.
The 'host' network spans between the RC and the Build Server over .
In R1 the 'host' network is verified as a single L2 broadcast domain.
| draw.io Diagram | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Rover Deployment
<UPDATE>
Rover servers makes DHCP Requests over the WAN spanning between the edge site and the RC's more centralized location which must be Responded to by the RC via the 'host' L2 domain. In the R1 release the 'host' network is a single L2 broadcast domain. It is possible to split the WAN host network into multiple routed L2 domains using functionality such as DHCP helper/relay but this is unverified in R1.
Rover servers are configured by the Redfish API calls issued by the RC to HTTP PXE boot from the RC over the 'host' network.
| draw.io Diagram | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Unicycle Pod Deployment
Unicycle genesis nodes makes DHCP Requests over the WAN spanning between the edge site and the RC's more centralized location which must be Responded to by the RC via the 'host' L2 domain.
The Unicycle 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 from the RC over over its vlan tagged 'host' network interface.
The RC acts as the DHCP and HTTP PXE boot server for the Unicycle genesis node via its own tagged 'host' network interface.
The 'host' network spans the WAN between the Unicycle pods's edge site and the RC in a more centralized location.
In R1 the 'host' network is verified as a single L2 broadcast domain.
Unicycle masters and workers (all unicycle nodes other than genesis), make DHCP Requests via on the edge site's local 'pxe' network's L2 broadcast domain which must be Responded to by the . The genesis node's MaaS acts as the DHCP server.
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.
...