<NETWORKING ARCHITECTURE, L1, L2, L3 and BGP>

DHCP, HTTP PXE and PXE Booting

Network Cloud family blueprint deployments involves a number of different DHCP servers and http pxe  and pxe booting procedures during the automatic deployment process.

Regional Controller Deployment

The RC makes DHCP Requests which must be Responded to by the Build Server via the 'host' network L2 domain. 

The RC is configured by the Redfish API calls issued by the Build Server to HTTP PXE boot from the Build Server over the 'host' network.

Rover Deployment

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.

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 genesis node is configured by the Redfish API calls issued by the RC to HTTP PXE boot from the RC over the 'host' network.

Unicycle masters and workers (all unicycle nodes other than genesis), make DHCP Requests via the edge site's local 'pxe' network's L2 broadcast domain which must be Responded to by the genesis node's MaaS 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.