You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

This installation procedure creates a Regional Controller on a new bare metal server. The bare metal server is termed the 'target' server in this guide.

The Build Server remotely installs the OS and SW 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. 

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 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 BMC port and the 'host' network. 

The build server will usually act as the DHCP server for initial RC boot process thus must be in the same broadcast domain as the target RC. 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 DHCP relay/helper functionality 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.

A 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>.

Software

Before starting to clone upstream repos and packages the build server must have the following pre-installed

  • Ubuntu Release 16.04
  • Latest version of the following apt packages:
    • docker    (used to run dhcp and web containers)
    • python    (used for redfish api calls to bare metal server)
    • python-requests    (used for redfish api calls to bare metal server)
    • python-pip    (used to install hpe redfish tools)
    • sshpass    (used to copy keys to new server)
    • xorriso    (used to extract Ubuntu files to web server)
    • make    (used to build custom ipxe efi file used during bare metal server boot)
    • gcc    (used to build custom ipxe efi file used during bare metal server boot)

Preflight checks

  • No labels