Install the WEKA cluster using the WMS with WSA
Last updated
Last updated
The WEKA Management Station (WMS) is an install kit similar to an OS install disk that simplifies the installation and configuration of the WEKA cluster in an on-premises environment by deploying the WEKA Software Appliance (WSA) package on bare metal servers. The WMS installs the WEKA OS, drivers, and WEKA software automatically and unattended.
The WMS is also used for installing the monitoring tools: Local WEKA Home (LWH), WEKAmon, and SnapTool (for details, see Deploy monitoring tools using the WEKA Management Station (WMS).
WEKA releases WMS and WSA updates addressing critical security issues found in the underlying Linux distribution within five days of discovery and availability. Customers can update their WMS/WSA instance from the repository where these updates are provided. WEKA notifies customers when updates are available, enabling timely updates to minimize potential risks. For any questions, contact the Customer Success Team.
For the update procedure, see Update WMS and WSA.
Using the WMS with WSA to install a WEKA cluster requires a physical server (or VM) that meets the following requirements:
Boot drives: One or two identical boot drives as an installation target.
A system with two identical boot drives has the OS installed on mirrored partitions (LVM).
A system with one drive has a simple partition.
Minimum boot drive capacity:
If not configuring LWH: SSD 141 GB (131 GiB).
If configuring LWH: See the SSD-backed storage requirements section in #1.-verify-prerequisites.
Boot type: UEFI boot.
Cores and RAM:
If not configuring LWH: minimum 4 cores and 16 GiB.
If configuring LWH, see the Server minimum CPU and RAM requirements section in #1.-verify-prerequisites.
Network interface: 1 Gbps.
Target servers must be Dell, HPE, Supermicro, or Lenovo. Other servers are not supported.
The interface must be installed, enabled, and licensed for all target servers.
The WMS must be able to connect over Ethernet to the following servers’ interfaces:
OS management interface, typically 1 Gbps. It must be connected to a switch.
Base Management Controller (BMC), such as , , or interfaces. The BMC interface must be configured with an IP address.
All the servers' interfaces must be connected to the switches.
The bare metal servers must conform to the Prerequisites and compatibility.
The bare metal servers must have an OS management network interface for administering the servers.
The boot type must be set to UEFI boot.
For cluster configurations exceeding 25 servers, it’s advisable to equip the WMS with an ETH interface of superior speed, such as 10/25/50 Gbps, during the installation phase. As an alternative, you could bond two or more 1 Gbps interfaces to increase the bandwidth. Once the installation phase is completed, a bandwidth of 1 Gbps is sufficient.
Before deploying the WMS, adhere to the following:
Obtain the WMS package. For details, see Obtain the WEKA installation packages.
The root password is WekaService
The WEKA user password is weka.io123
If errors occur during installation and the installation halts (no error messages appear), use the system console to review the logs in /tmp. The primary log is /tmp/ks-pre.log.
To get a command prompt from the Installation GUI, do one of the following:
On macOS, type ctrl+option+f2
On Windows, type ctrl+alt+f2.
Boot the server from the WMS image. The following are some options to do that:
Copy the WEKA Management Station ISO image to an appropriate location so the server’s BMC (Baseboard Management Controller) can mount it or be served through a PXE (Preboot Execution Environment).
Once you boot the server, the WEKA Management Station installs the WEKA OS (Rocky Linux), drivers, and WEKA software automatically and unattended (no human interaction required).
Depending on network speed, this can take about 10-60 mins (or more) per server.
Once the WMS installation is complete and rebooted, configure the WMS.
Run the OS using one of the following options:
Run the OS through the BMC’s Console. See the specific manufacturer’s BMC documentation.
Browse to the WMS Admin UI using the following URL:
http://<WMS-hostname-or-ip>:8501
Enter username and password (default: admin/admin), and select Login. The Landing Page appears.
Download the latest release of the WSA package from get.weka.io dashboard.
Copy the WSA package to /home/weka .
For example: scp <wsa.iso> weka@<wms-server>:
Go to the WMS Admin UI (landing page) and select Deploy a WEKA Custer.
The WSA setup page opens.
Open Step 1 - Choose source ISO, select the WSA package (ISO) you intend to deploy, and click Next.
The WSA packages that appear in the list are taken from /home/weka. You can have more than one in the directory. If none are displayed, click Refresh ISO List. If none are displayed after that, copy a WSA package to /home/weka and click Refresh ISO List again. Once you select a WSA ISO, click Next.
In Step 2 - Load values from, select one of the following options:
Option 1: Enter environment data: Click Go directly to forms to enter data.
Option 2: Import CSV file: If you have the environment data in a CSV file, click Upload a CSV file to pre-populate data. Step 3 - CSV File Upload section opens.
Drag or click to upload the CSV file, and click Next.
CSV template example
You can prepare a CSV file with the columns as specified in the following example:
In Step 4 - Number of servers to deploy, enter a Server Count (default is 8), and click Next.
In the following steps, if you uploaded a CSV file, the data is pre-populated. You can review the data and if no editing is necessary, select Next.
In the IPMI First IP, enter the IPMI IP address of the first server. It requires a consecutive set of IP addresses for the servers (typical).
In the IPMI user and IPMI password, modify the login credentials for the IPMI, iLO, or iDRAC according to your choice.
Click Fill IPMI IPs to calculate the IP addresses for the number of servers specified in Step 4.
You can edit the IP addresses, Usernames, and Passwords as needed if the servers aren’t consecutive or require different credentials.
If you edited the table, click Verify IPMI IPs to verify that the WMS can log into the BMCs and detect the manufacturer (Brand column).
Verify that all is correct, and then click Next.
In Step 6 - Operating System network information, do the following:
In the OS First IP, enter the IP address of the OS 1 Gbit management interface. It requires a consecutive set of IP addresses for the servers (typical).
In the remaining networking fields, fill in the networking details.
Click Fill OS Table to populate the table. The WMS automatically generates names and IPs.
Verify that the OS IP settings are correct. You can repeatedly click Fill OS Table to make adjustments.
Verify that all is correct, and then click Next.
In Step 7 - Dataplane settings, do the following:
Set the number of interfaces in the Dataplane Interface Count slider.
In the remaining dataplane fields, fill in the details.
Click Update Dataplanes. The WMS automatically populates the data.
You can repeatedly click Update Dataplanes to make adjustments.
Verify that all is correct, and then click Next.
In Step 8 - Save configuration files and inventory, click Save Files to save the configuration files, and then click Next.
In Step 9 - Prepare ISO for installation, click Prepare ISO for install. The WMS updates the kickstart on the ISO to match the WMS deployment data (it takes about 30 seconds).
When the ISO preparation is completed, the output is displayed. Verify that no errors appear. Then, click Next.
In Step 10 - Start Installation, click Install OS on Servers. The WMS loads the WSA on the servers previously defined and starts the installation. The installation can take several minutes and displays output when complete. Verify that no errors appear.
The installation process takes about 30 minutes, depending on several factors, such as network speed. Verify that the server’s BMC completed the restart.
In Step 11 - Run OS and Dataplane Configuration Scripts, click Run post-install scripts. This action runs scripts to configure the servers with the specified dataplane IPs and perform additional tasks, such as populating /etc/hosts.
Alternative OS and dataplane configuration
These commands only need to be run if you did not follow step 11 above.
Connect to one of the cluster servers to run the post-install scripts. The tools are in the same location: /opt/tools/install on the WSA as they are on the WMS.
When prompted, enter the password WekaService
Change the directory to /opt/ansible-install by running the following command:
Run the post-install script:
Example:
Ensure the DNS is operational, or copy the /etc/hosts entries from one of the cluster servers to the WMS.
