| Table of Contents |
|---|
| Child pages (Children Display) | ||
|---|---|---|
|
Introduction
| Drawio | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
- 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
Server iDRAC/iLO provisioning
The RC's iDRAC/iLO IP address and subnet must be manually provisioned into the server before installation begins.
Networking
The Target RC has multiple physical and 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 the Network Architecture section section of this release documentation <INSERT LINK>. In In addition the networking configuration with example vlaues as used in the validation labs values similar to that used during validation testing is contained in the Validation Labs section of this release documentation Ericsson Unicycle OVS-DPDK Validation HW, Networking and IP plan.
The Build Server must have IP connectivity to the Target Server's dedicated BMC port using ports 80 (http) <is 80 actually used?> and 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.
...
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.
The RC's iDRAC/iLO IP address and subnet must be manually provisioned into the server before installation begins.
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.
...
Note: The enumerated IP shown (10.51.35.146) is the an example iDRAC address for a RC deployed in a specific validation lab.
Preflight RC Region Specific Input Data
...
Note: The enumerated IP shown (10.51.34.230) is the an example 'host' address for a RC deployed in a specific validation lab.
Once this has been set and the file saved export the value using
...
Note: The enumerated IP shown (10.51.34.230) is the an example'host' address for a RC deployed in a specific validation lab.
The final step installs the Regional Controller software:
...
Note: The enumerated IP shown (10.51.34.230) is the an example 'host' address for a RC deployed in a specific validation lab.
The Regional Controller Node installation is now complete.
...
Upon successful login, the Akraino Portal home page will appear.
Parameter Naming
...
RC's host name: NEW_RC_SRV_NAME
...
Regional Controller Region Specific Input File
...
This section includes a sample includes an example input file similar to that was used in the Ericsson during Ericsson Validation Lab testing to build a Regional Controller .
This file is the /opt/akraino/redfish/server-config/aknode29rc
...
| language | yml |
|---|
...
for the R1 release. Being region specific the enumerated values will differ for RCs in different regions. Full details of the relevant validation lab setup that should be referenced when looking at these files is contained in the Ericsson Validation Labs section of this documentation.
| Child pages (Children Display) | ||
|---|---|---|
|