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

The Build Server remotely installs the Linux OSoperating system, Network Cloud specific and other software packages on the target server Target Server to create 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. 

The installation procedure is executed from the Build Server and automatically performs all the following on the target serverTarget Server:

• Modify the BIOS including DHCP and PXE boot configuration by issuing Redfish API commands to the target serverTarget Server's iDRAC or iLO BMC 
• Install and update an Ubuntu 16.04 operating system
• Install Network Cloud Regional Controller specific software including
  • PostgreSQL DB
  • Camunda Workflow and Decision Engine
  • Akraino Web Portal
  • LDAP configuration
• Install a number of supporting supplementary software components including
  • OpenStack Tempest tests
  • YAML builds
  • ONAP scripts
  • Sample VNFs

Preflight requirements

Networking

The target Target RC has multiple physical ND VLAN interfaces. The build server Build Server uses different interfaces during the different stages of its creation of a RC on the target serverTarget 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 build server Build Server must have IP connectivity to the target serverTarget 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 serverTarget Server's BIOS settings. The target serverTarget Server's BMC IP address is denoted as <SRV_OOB_IP> in this guide. The target serverTarget Server's BMC must be manually preconfigured with the <SRV_OOB_IP> address.

After setting the target serverTarget Server's BIOS, the build server Build Server will then (usually) act as the DHCP server for the initial target serverTarget Server's boot process. The target server 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 serverTarget Server's 'host' interface and the build serverBuild Server's DHCP server interface must be in the same broadcast domain so that the DHCP Request broadcast frame can reach the build serverBuild Server. It is possible to remove the need for the build server and target server Build Server and Target Server to be on the same L2 domain using  DHCP relay/helper functionality in the TOR to relay the target serverTarget 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 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 serverTarget Server's 'host' interface must have connectivity to the internet to be able to download the necessary repos and packages.

...

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

...

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

...

The automated deployment process configures the new RC based on a set of user defined values. These values must be created and stored in a yaml configuration file before the RC deployment process can be started.

During the previous build server Build Server installation a generic template called serverrc.template was created on the build server Build Server in /opt/akraino/redfish/. This template should be used to create the deployment specific input file for the new RC. The example below is for a RC called aknode29.   

...

The RC is deployed in two stages, first the bare metal and Linux OS installation occurs then the Network Cloud specific software is installed on the target Target RC server.

Elevate yourself to root:

...

During the installation the progress can be monitored by viewing the following logfile on the build server Build Server <INSERT CODE SHOWING LOG FILE>

The BIOS configuration and Linus installation results in numerous reboots of the target server Target Server which each take many minutes. In addition software packages are transferred and updated on the target Target RC server resulting in a total installation time of <INSERT BALL  PARK FIGURE>. The actual time will vary depending on the time taken to retrieve packages from their external repos.

...

During the second stage of the RC deployment process the build server Build Server will <SSH into?> use the target Target RC server's 'host' address. The RC's planned 'host' address must be manually configured in a file on the build called akrainrc in /opt/akraino/region/.

...