This installation procedure creates a Regional Controller on a new bare metal server. The bare metal server which will become the RC is termed the 'target RC' or just 'target' server in this guide.

The Build Server remotely installs the Linux OS and SW , Network Cloud specific and other software packages on the target server to create the 'Regional Controller ' (i.e. the Bare Metal server becomes the Regional Controller'). Once the RC is build it is used to subsequently deploy either Rover or Unicycle pods. After the Build Server has completed the creation of the Regional Controller, the Build Server has no further role in any Network Cloud Rover or Unicycle Pod deployment. 

...

Preflight requirements

Networking

The target RC has multiple physical ND VLAN interfaces. The build server uses different interfaces during the different stages of its creation of a RC on the target server. A very detailed description of the entire networking setup can be found in the Network Architecture section of this release documentation <INSERT LINK>. In addition the networking configuration used in the validation labs is contained in the Validation Labs section of this release documentation <INSERT LINK>. 

The target server must have connectivity to the internet to be able to download the necessary repos and packages during installation.The build server must have IP connectivity to the target server's dedicated BMC port using ports 80 (http) <is 80 actually used?> and 443 (https) in order to issue Redfish commands to configure the target server's BIOS settings. The target server's BMC IP address is denoted as <SRV_OOB_IP> in this guide. The target server's BMC must be manually preconfigured with the <SRV_OOB_IP> address.

After setting the target server's BIOS, the build server will then (usually) act as the DHCP server for the initial target server's boot process. The target server will be automatically configured by the Redfish API commands to send its initial DHCP Request from one of its main NICs via the VLAN tagged 'host' network. Thus the target server's 'host' interface and the build server's DHCP server interface must be in the same broadcast domain so that the DHCP Request broadcast frame will can reach the build server. It is possible to remove the need for the build server and target server to be on the same L2 domain using features such as using  DHCP relay/helper functionality in the TOR to relay the target server's DHCP requests across an IP routed network, however this has not been verified in the R1 release and this guide assumes the build and target servers to be on the same L2 broadcast domain as described in the detailed networking section.

During the layer stages of the installation the target server's 'host' interface must have connectivity to the internet to be able to download the necessary repos and packages.

Software

When the RC is installed on a new bare metal server no software is required on the target server. All software will be installed from the build server and/or external repos via the internet.

Preflight checks

To verify the necessary networking IP connectivity from the build server to the target server's BMC confirm from the build server that at least port 443 is open to the target server'  iDRAC/iLO BMC IP address <SRV_OOB_IP> : <INSERT_IP ADDRESS BELOW> 

...

...