...
| draw.io Diagram | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Rover Deployment
<UPDATE>
...
The Rover server 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.
The RC acts as the DHCP and HTTP PXE boot server for the Rover server via its own tagged 'host' network interface.
The 'host' network spans the WAN between the Rover edge site and the RC
...
in a more centralized location
...
.
In R1 the 'host' network is verified as a single L2 broadcast domain.
It is possible to split the WAN 'host' network spanning the WAN 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 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 R1.
| draw.io Diagram | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...