...
The Network Cloud blueprints deploy Rover and unicycle Unicycle pods at multiple edge locations driven by a regional controller. As such the networking architecture spans the WAN between the RC and edge pods as well as the edge sites themselves.
...
The RC (when installed on bare metal, Rover and Unicycle genesis 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.
...
Unicycle Pod Deployment
A Unicycle pod's genesis 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.
The RC acts as the DHCP and HTTP PXE boot server for the Unicycle genesis Genesis node via its own tagged 'host' network interface.
...
Unicycle masters and workers (all unicycle Unicycle nodes other than genesisGenesis), make DHCP Requests on the edge site's local 'pxe' network's L2 broadcast domain. The genesis Genesis node's MaaS acts as the DHCP server.
Unicycle masters and workers (all unicycle Unicycle nodes other than genesisGenesis) are configured by the MaaS server running on the genesis Genesis node to PXE boot over the remote site's 'pxe' network.
The unicycle Unicycle DHCP/HTTP PXE/PXE process flow is summarized below.
...
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 Genesis TOR but this is unverified in R1. Note: this is not applicable to the other nodes in the unicycle Unicycle pod as the DHCP and PXE boot process is supported over the local 'pxe' network.
...