Versions Compared

Old Version 3

changes.mady.by.user Andrew Wilkinson

Saved on

compared with

New Version 4

changes.mady.by.user Andrew Wilkinson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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



DHCP

Network Cloud family blueprint deployments involves a number of different DHCP servers.

The RC makes a DHCP Request which must be Replied to by the Build Server via the 'host' network L2 domain. 

Rover servers and Unicycle genesis nodes make DHCP Requests which must be Replied to by the RC over the WAN spanning between the edge site and the RC's more centralized location 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. 

Unicycle non genesis nodes , masters and workers, make DHCP Requests which must be Replied to by the genesis node's MaaS DHCP server via the edge site's local 'pxe' network's L2 broadcast domain.


PXE Booting



<DHCP FLOWS FOR RC → BUILD SERVER; ROVER/GENESIS →RC; UNICYCLE MASTER2/3 →GENESIS(MAAS)>

...