Quick installation guide
Last updated
Last updated
This is a quick installation guide. For a complete installation, refer to the following pages:
WEKA installation on bare metal
For a complete prerequisite list, refer to the section.
In the examples provided, the deployment consists of 8 identical servers. To simplify the installation process, Mellanox or Intel E810 NICs are used, allowing for streamlined installation commands. For instance, only a single IP address is required for data, eliminating the need to expose VFs, determine the interface netmask, and configure the default routing gateway. If the deployment varies, the installation commands may differ slightly.
Once the WEKA system is successfully installed, you can learn how to navigate, manage, and operate it using either the graphical user interface (GUI) or the command-line interface (CLI). Additionally, you can perform initial input/output (IO) operations on a WEKA filesystem.
The WEKA system supports a RESTful API, enabling the automation of interactions with the WEKA system. This facilitates seamless integration into your existing workflows and monitoring systems.
It is assumed that the servers are ready for the WEKA software installation. In this example, there are 8 servers. Each server has over 20 cores, 6 NVME drives, and a single Mellanox NIC.
To run the commands on all containers in parallel, we use pdsh
as an example only.
Install WEKA software on all servers:
Remove the single default container created on each server in the cluster:
Get the resource generator to your local server:
Copy the resource generator from your local server to all servers in the cluster:
3. To enable execution, change the mode of the resource generator on all servers in the cluster:
4. Run resource generator on all servers in the cluster:
The resource generator generates three resource files on each server in the /tmp
directory: drives0.json
, compute0.json
, and frontend0.json
.
Create the drive containers from the resource generator output file drives0.json
. Run the following command on all servers in the cluster:
Connect to one of the servers, create the cluster, and set the cluster name.
Using bash, you can provide a compact list of containers cluster-name{n..m}. Otherwise, specify the complete list of all containers. For example: weka cluster create weka0-0 weka0-1 weka0-2 weka0-3 weka0-7
.
It is assumed that the DNS is set up. Otherwise, specify the explicit IPs in the weka cluster create
command.
Add a drive to each server in the cluster. Run the following command from one of the servers:
Create the compute containers from the resource generator output file compute0.json
. Run the following command on all servers in the cluster:
Enable event notifications to the cloud for support purposes. From one of the servers, run the following command:
Set the license. From one of the servers, run the following command:
Start the cluster IO service. From one of the servers, run the following command:
Create the frontend containers from the resource generator output file frontend0.json
. This step is required to mount from the server or set one of the additional protocols on the server, which requires a frontend process.
Run the following command on all servers in the cluster:
Check the resources per server (such as NICs and cores), drives, and configuration status:
Output example for a multiple container architecture:
2. Change the default admin password and ensure no other alerts exist.
Related topics
WEKA installation on bare metal
Manage the system using the WEKA CLI
Manage the system using the WEKA GUI
To get the download link with the token, see the topic.
For more details about the resource generator, see the procedure in the WEKA system installation with multiple containers topic.
Obtain a classic or PAYG license from .