...
The instructions below skip most of this and directly invoke the SEBA Deployer from the BMC, iLO or iDRAC of a physical server. The basic workflow of the SEBA deployer is to copy a base image to the first controller in the cluster and then read the contents of a configuration file (typically called user_config.yaml) to deploy the base OS and all additional software to the rest of the nodes in the cluster.
| Note |
|---|
The manual installation procedure described below does not result in the installation of the SEBA application. Fully automated installation of the SEBA application will not be complete until sometime after Akraino Release 2. The SEBA application components may be installed manually as described in the last section of this WIKI document. |
Pre-Installation Requirements for SEBA Cluster - NEEDS UPDATES
...
SEBA is a fully integrated stack from the hardware up to and including the application, so for best results , it is necessary to use one of the tested hardware configurations. Although SEBA is intended to run on a variety of different hardware platforms, it includes a hardware detector component that customizes each installation based on the hardware present and will need (possibly minor) changes to run on additional hardware configurations. Preliminary support is present in Akraino Release 2 for SEBA for HP DL380 generation 9 and 10, Dell R740xd and Nokia Open Edge servers, but the The primary focus of Akraino Release 2 testing for the SEBA blueprint is the Nokia Open Edge servers, so some issues may be encountered with other server types.
...
Recent builds can be obtained from the Akraino Nexus server. Choose either "latest" or a specific build number from the release images directory and download the file install.iso. Build number 185 is the Akraino Release 1 image from the 4th of October, 2019 and was used for the initial validation of the SEBA blueprint. Note that build number 9 is known to NOT work on Dell servers or any of the ARM options listed below. If attempting to install on Dell servers, it is suggested to use builds from no earlier than June 10th. Options for booting the ISO on your target hardware include NFS, HTTP, or USB memory stick. You must place the ISO in a suitable location (e.g., NFS server, HTTP(S) server or USB memory stick) before starting the boot process. The file bootcd.iso, which is also in the same directory, is used only when deploying via the Akraino Regional Controller using the Telco Appliance Remote Installer. You can ignore bootcd.iso when following the manual procedure below.
...