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, Network Cloud specific and other software packages on the 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 server:

• Modify the BIOS including DHCP and PXE boot configuration by issuing Redfish API commands to the target 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 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 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 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  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 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> 

build_server# #nmap -sS <SRV_OOB_IP>

build_server# nmap -sS <INSERT_IP ADDRESS>


Starting Nmap 7.01 ( https://nmap.org ) at 2018-07-10 13:55 UTC Nmap scan report for <INSERT_IP ADDRESS> Host is up (0.00085s latency). Not shown: 996 closed ports PORT STATE SERVICE 22/tcp open ssh 80/tcp open http 443/tcp open https 5900/tcp open vnc Nmap done: 1 IP address (1 host up) scanned in 1.77 seconds

<IS THIS NEXT STEP REALLY NECESSARY - DOESN:T THE INSTALL SCRIPT FORMAT THE SERVER BY DEFAULT?>

Next, use nmap to check for a "clean slate" Bare Metal Server. The results will show the host as being down (due to no OS).

# nmap -sS <SRV_HOST_ADDRESS>

# nmap -sS <INSERT HOST ADDRESS>
 
Starting Nmap 7.01 ( https://nmap.org ) at 2018-07-10 13:55 UTC
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 0.63 seconds

Preflight Input Data 

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 installation a generic template called serverrc.template was created on the build server in /opt/akraino/redfish/. This template should be used to create the deployment specific input file for the new RC.   <INSERT NODE NAME BELOW>

root@build-server# mkdir -p /opt/akraino/server-config

root@build-server# #cp /opt/akraino/redfish/serverrc.template /opt/akraino/server-config/<new_RC_nodename>

root@build-server# cp /opt/akraino/redfish/serverrc.template /opt/akraino/server-config/<INSERT NODE NAME>

root@build-server# #vi /opt/akraino/server-config/<new_RC_nodename>

root@build-server# vi /opt/akraino/server-config/<INSERT NODE NAME>

Deploying the RC 

Elevate yourself to root:

user@build_server:/# sudo -i

Copy the Bare Metal Server configuration template into/opt/akraino/server-config/AKRAINO_NODE_RC, where AKRAINO_NODE_RC is the Bare Metal Server name followed by rc. On the Build Server:

A sample configuration file for the Regional Controller follows. Ensure the following: