You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 8
Next »
<NETWORKING ARCHITECTURE, L1, L2, L3 and BGP>
DHCP
Network Cloud family blueprint deployments involves a number of different DHCP servers.
Regional Controller Deployment
The RC makes a DHCP Request which must be Responded to by the Build Server via the 'host' network L2 domain.
eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IkFuZHJldyBXaWxraW5zb24iLCJvdXRwdXRUeXBlIjoiYmxvY2siLCJsYXN0TW9kaWZpZXJOYW1lIjoiQW5kcmV3IFdpbGtpbnNvbiIsImxhbmd1YWdlIjoiZW4iLCJkaWFncmFtRGlzcGxheU5hbWUiOiIiLCJzRmlsZUlkIjoiIiwiYXR0SWQiOiIxMTk5NDQxOCIsImRpYWdyYW1OYW1lIjoiREhDUCAtIFBYRSBSQyBhbmQgUm92ZXIiLCJhc3BlY3QiOiIiLCJsaW5rcyI6ImF1dG8iLCJjZW9OYW1lIjoiTmV0d29yayBBcmNoaXRlY3R1cmUiLCJ0YnN0eWxlIjoidG9wIiwiY2FuQ29tbWVudCI6ZmFsc2UsImRpYWdyYW1VcmwiOiIiLCJjc3ZGaWxlVXJsIjoiIiwiYm9yZGVyIjp0cnVlLCJtYXhTY2FsZSI6IjEiLCJvd25pbmdQYWdlSWQiOjExOTkzOTA0LCJlZGl0YWJsZSI6ZmFsc2UsImNlb0lkIjoxMTk5NDQzMywicGFnZUlkIjoiIiwibGJveCI6dHJ1ZSwic2VydmVyQ29uZmlnIjp7ImVtYWlscHJldmlldyI6IjEifSwib2RyaXZlSWQiOiIiLCJyZXZpc2lvbiI6MywibWFjcm9JZCI6ImZmMDk0Y2MxLTJmNTktNDAwOC1iYjFkLWNmY2ZhN2NmMTM4ZiIsInByZXZpZXdOYW1lIjoiREhDUCAtIFBYRSBSQyBhbmQgUm92ZXIucG5nIiwibGljZW5zZVN0YXR1cyI6Ik9LIiwic2VydmljZSI6IiIsImlzVGVtcGxhdGUiOiIiLCJ3aWR0aCI6IjQxMSIsInNpbXBsZVZpZXdlciI6ZmFsc2UsImxhc3RNb2RpZmllZCI6MTU1ODgyNTAzMzAwMCwiZXhjZWVkUGFnZVdpZHRoIjpmYWxzZSwib0NsaWVudElkIjoiIn0=
Rover Deployment
Rover servers make 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.
eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IkFuZHJldyBXaWxraW5zb24iLCJvdXRwdXRUeXBlIjoiYmxvY2siLCJsYXN0TW9kaWZpZXJOYW1lIjoiQW5kcmV3IFdpbGtpbnNvbiIsImxhbmd1YWdlIjoiZW4iLCJkaWFncmFtRGlzcGxheU5hbWUiOiIiLCJzRmlsZUlkIjoiIiwiYXR0SWQiOiIxMTk5NDQyMiIsImRpYWdyYW1OYW1lIjoiREhDUCAtIFBYRSBSQyIsImFzcGVjdCI6IiIsImxpbmtzIjoiYXV0byIsImNlb05hbWUiOiJOZXR3b3JrIEFyY2hpdGVjdHVyZSIsInRic3R5bGUiOiJ0b3AiLCJjYW5Db21tZW50IjpmYWxzZSwiZGlhZ3JhbVVybCI6IiIsImNzdkZpbGVVcmwiOiIiLCJib3JkZXIiOnRydWUsIm1heFNjYWxlIjoiMSIsIm93bmluZ1BhZ2VJZCI6MTE5OTM5MDQsImVkaXRhYmxlIjpmYWxzZSwiY2VvSWQiOjExOTk0NDMzLCJwYWdlSWQiOiIiLCJsYm94Ijp0cnVlLCJzZXJ2ZXJDb25maWciOnsiZW1haWxwcmV2aWV3IjoiMSJ9LCJvZHJpdmVJZCI6IiIsInJldmlzaW9uIjoyLCJtYWNyb0lkIjoiODVlNTQ4NGEtYzQxZC00NDE3LTgwNTQtZDVhN2U0YTAxNmVhIiwicHJldmlld05hbWUiOiJESENQIC0gUFhFIFJDLnBuZyIsImxpY2Vuc2VTdGF0dXMiOiJPSyIsInNlcnZpY2UiOiIiLCJpc1RlbXBsYXRlIjoiIiwid2lkdGgiOiI2OTUiLCJzaW1wbGVWaWV3ZXIiOmZhbHNlLCJsYXN0TW9kaWZpZWQiOjE1NTg4MjUwMDgwMDAsImV4Y2VlZFBhZ2VXaWR0aCI6ZmFsc2UsIm9DbGllbnRJZCI6IiJ9
Unicycle Pod Deployment
Unicycle genesis nodes make 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.
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 .
eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IkFuZHJldyBXaWxraW5zb24iLCJvdXRwdXRUeXBlIjoiYmxvY2siLCJsYXN0TW9kaWZpZXJOYW1lIjoiQW5kcmV3IFdpbGtpbnNvbiIsImxhbmd1YWdlIjoiZW4iLCJkaWFncmFtRGlzcGxheU5hbWUiOiIiLCJzRmlsZUlkIjoiIiwiYXR0SWQiOiIxMTk5NDQyOCIsImRpYWdyYW1OYW1lIjoiVW5pY3ljbGUgRGVwbG95bWVudCIsImFzcGVjdCI6IiIsImxpbmtzIjoiYXV0byIsImNlb05hbWUiOiJOZXR3b3JrIEFyY2hpdGVjdHVyZSIsInRic3R5bGUiOiJ0b3AiLCJjYW5Db21tZW50IjpmYWxzZSwiZGlhZ3JhbVVybCI6IiIsImNzdkZpbGVVcmwiOiIiLCJib3JkZXIiOnRydWUsIm1heFNjYWxlIjoiMSIsIm93bmluZ1BhZ2VJZCI6MTE5OTM5MDQsImVkaXRhYmxlIjpmYWxzZSwiY2VvSWQiOjExOTk0NDMzLCJwYWdlSWQiOiIiLCJsYm94Ijp0cnVlLCJzZXJ2ZXJDb25maWciOnsiZW1haWxwcmV2aWV3IjoiMSJ9LCJvZHJpdmVJZCI6IiIsInJldmlzaW9uIjoyLCJtYWNyb0lkIjoiYzEzNTMwNTQtZDdjZi00NjBhLTg4M2EtMzgwZTcyNmRlNWYwIiwicHJldmlld05hbWUiOiJVbmljeWNsZSBEZXBsb3ltZW50LnBuZyIsImxpY2Vuc2VTdGF0dXMiOiJPSyIsInNlcnZpY2UiOiIiLCJpc1RlbXBsYXRlIjoiIiwid2lkdGgiOiI5NzQiLCJzaW1wbGVWaWV3ZXIiOmZhbHNlLCJsYXN0TW9kaWZpZWQiOjE1NTg4MjU1MjcwMDAsImV4Y2VlZFBhZ2VXaWR0aCI6ZmFsc2UsIm9DbGllbnRJZCI6IiJ9
HTTP PXE / PXE Booting
During deployment
- The RC are configured by the Redfish API calls issued by the Build Server to HTTP PXE boot from the Build Server over the 'host' network.
- Rover servers and Unicycle genesis nodes are 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), are configured by the MaaS server running on the genesis node to PXE boot over the remote sites 'pxe' network.