W E K A
4.4
4.4
  • WEKA v4.4 documentation
    • Documentation revision history
  • WEKA System Overview
    • Introduction
      • WEKA system functionality features
      • Converged WEKA system deployment
      • Optimize redundancy in WEKA deployments
    • SSD capacity management
    • Filesystems, object stores, and filesystem groups
    • WEKA networking
    • Data lifecycle management
    • WEKA client and mount modes
    • WEKA containers architecture overview
    • Glossary
  • Planning and Installation
    • Prerequisites and compatibility
    • WEKA cluster installation on bare metal servers
      • Plan the WEKA system hardware requirements
      • Obtain the WEKA installation packages
      • Install the WEKA cluster using the WMS with WSA
      • Install the WEKA cluster using the WSA
      • Manually install OS and WEKA on servers
      • Manually prepare the system for WEKA configuration
        • Broadcom adapter setup for WEKA system
        • Enable the SR-IOV
      • Configure the WEKA cluster using the WEKA Configurator
      • Manually configure the WEKA cluster using the resources generator
        • VLAN tagging in the WEKA system
      • Perform post-configuration procedures
      • Add clients to an on-premises WEKA cluster
    • WEKA Cloud Deployment Manager Web (CDM Web) User Guide
    • WEKA Cloud Deployment Manager Local (CDM Local) User Guide
    • WEKA installation on AWS
      • WEKA installation on AWS using Terraform
        • Terraform-AWS-WEKA module description
        • Deployment on AWS using Terraform
        • Required services and supported regions
        • Supported EC2 instance types using Terraform
        • WEKA cluster auto-scaling in AWS
        • Detailed deployment tutorial: WEKA on AWS using Terraform
      • WEKA installation on AWS using the Cloud Formation
        • Self-service portal
        • CloudFormation template generator
        • Deployment types
        • AWS Outposts deployment
        • Supported EC2 instance types using Cloud Formation
        • Add clients to a WEKA cluster on AWS
        • Auto scaling group
        • Troubleshooting
    • WEKA installation on Azure
      • Azure-WEKA deployment Terraform package description
      • Deployment on Azure using Terraform
      • Required services and supported regions
      • Supported virtual machine types
      • Auto-scale virtual machines in Azure
      • Add clients to a WEKA cluster on Azure
      • Troubleshooting
      • Detailed deployment tutorial: WEKA on Azure using Terraform
    • WEKA installation on GCP
      • WEKA project description
      • GCP-WEKA deployment Terraform package description
      • Deployment on GCP using Terraform
      • Required services and supported regions
      • Supported machine types and storage
      • Auto-scale instances in GCP
      • Add clients to a WEKA cluster on GCP
      • Troubleshooting
      • Detailed deployment tutorial: WEKA on GCP using Terraform
      • Google Kubernetes Engine and WEKA over POSIX deployment
    • WEKA installation on OCI
  • Getting Started with WEKA
    • Manage the system using the WEKA GUI
    • Manage the system using the WEKA CLI
      • WEKA CLI hierarchy
      • CLI reference guide
    • Run first IOs with WEKA filesystem
    • Getting started with WEKA REST API
    • WEKA REST API and equivalent CLI commands
  • Performance
    • WEKA performance tests
      • Test environment details
  • WEKA Filesystems & Object Stores
    • Manage object stores
      • Manage object stores using the GUI
      • Manage object stores using the CLI
    • Manage filesystem groups
      • Manage filesystem groups using the GUI
      • Manage filesystem groups using the CLI
    • Manage filesystems
      • Manage filesystems using the GUI
      • Manage filesystems using the CLI
    • Attach or detach object store buckets
      • Attach or detach object store bucket using the GUI
      • Attach or detach object store buckets using the CLI
    • Advanced data lifecycle management
      • Advanced time-based policies for data storage location
      • Data management in tiered filesystems
      • Transition between tiered and SSD-only filesystems
      • Manual fetch and release of data
    • Mount filesystems
      • Mount filesystems from Single Client to Multiple Clusters (SCMC)
      • Manage authentication across multiple clusters with connection profiles
    • Snapshots
      • Manage snapshots using the GUI
      • Manage snapshots using the CLI
    • Snap-To-Object
      • Manage Snap-To-Object using the GUI
      • Manage Snap-To-Object using the CLI
    • Snapshot policies
      • Manage snapshot policies using the GUI
      • Manage snapshot policies using the CLI
    • Quota management
      • Manage quotas using the GUI
      • Manage quotas using the CLI
  • Additional Protocols
    • Additional protocol containers
    • Manage the NFS protocol
      • Supported NFS client mount parameters
      • Manage NFS networking using the GUI
      • Manage NFS networking using the CLI
    • Manage the S3 protocol
      • S3 cluster management
        • Manage the S3 service using the GUI
        • Manage the S3 service using the CLI
      • S3 buckets management
        • Manage S3 buckets using the GUI
        • Manage S3 buckets using the CLI
      • S3 users and authentication
        • Manage S3 users and authentication using the CLI
        • Manage S3 service accounts using the CLI
      • S3 lifecycle rules management
        • Manage S3 lifecycle rules using the GUI
        • Manage S3 lifecycle rules using the CLI
      • Audit S3 APIs
        • Configure audit webhook using the GUI
        • Configure audit webhook using the CLI
        • Example: How to use Splunk to audit S3
        • Example: How to use S3 audit events for tracking and security
      • S3 supported APIs and limitations
      • S3 examples using boto3
      • Configure and use AWS CLI with WEKA S3 storage
    • Manage the SMB protocol
      • Manage SMB using the GUI
      • Manage SMB using the CLI
  • Security
    • WEKA security overview
    • Obtain authentication tokens
    • Manage token expiration
    • Manage account lockout threshold policy
    • Manage KMS
      • Manage KMS using GUI
      • Manage KMS using CLI
    • Manage TLS certificates
      • Manage TLS certificates using GUI
      • Manage TLS certificates using CLI
    • Manage Cross-Origin Resource Sharing
    • Manage CIDR-based security policies
    • Manage login banner
  • Secure cluster membership with join secret authentication
  • Licensing
    • License overview
    • Classic license
  • Operation Guide
    • Alerts
      • Manage alerts using the GUI
      • Manage alerts using the CLI
      • List of alerts and corrective actions
    • Events
      • Manage events using the GUI
      • Manage events using the CLI
      • List of events
    • Statistics
      • Manage statistics using the GUI
      • Manage statistics using the CLI
      • List of statistics
    • Insights
    • System congestion
    • User management
      • Manage users using the GUI
      • Manage users using the CLI
    • Organizations management
      • Manage organizations using the GUI
      • Manage organizations using the CLI
      • Mount authentication for organization filesystems
    • Expand and shrink cluster resources
      • Add a backend server
      • Expand specific resources of a container
      • Shrink a cluster
    • Background tasks
      • Set up a Data Services container for background tasks
      • Manage background tasks using the GUI
      • Manage background tasks using the CLI
    • Upgrade WEKA versions
    • Manage WEKA drivers
  • Monitor the WEKA Cluster
    • Deploy monitoring tools using the WEKA Management Station (WMS)
    • WEKA Home - The WEKA support cloud
      • Local WEKA Home overview
      • Deploy Local WEKA Home v3.0 or higher
      • Deploy Local WEKA Home v2.x
      • Explore cluster insights
      • Explore performance statistics in Grafana
      • Manage alerts and integrations
      • Enforce security and compliance
      • Optimize support and data management
      • Export cluster metrics to Prometheus
    • Set up WEKAmon for external monitoring
    • Set up the SnapTool external snapshots manager
  • Kubernetes
    • Composable clusters for multi-tenancy in Kubernetes
    • WEKA Operator deployment
    • WEKA Operator day-2 operations
  • WEKApod
    • WEKApod Data Platform Appliance overview
    • WEKApod servers overview
    • Rack installation
    • WEKApod initial system setup and configuration
    • WEKApod support process
  • AWS Solutions
    • Amazon SageMaker HyperPod and WEKA Integrations
      • Deploy a new Amazon SageMaker HyperPod cluster with WEKA
      • Add WEKA to an existing Amazon SageMaker HyperPod cluster
    • AWS ParallelCluster and WEKA Integration
  • Azure Solutions
    • Azure CycleCloud for SLURM and WEKA Integration
  • Best Practice Guides
    • WEKA and Slurm integration
      • Avoid conflicting CPU allocations
    • Storage expansion best practice
  • Support
    • Get support for your WEKA system
    • Diagnostics management
      • Traces management
        • Manage traces using the GUI
        • Manage traces using the CLI
      • Protocols debug level management
        • Manage protocols debug level using the GUI
        • Manage protocols debug level using the CLI
      • Diagnostics data management
  • Appendices
    • WEKA CSI Plugin
      • Deployment
      • Storage class configurations
      • Tailor your storage class configuration with mount options
      • Dynamic and static provisioning
      • Launch an application using WEKA as the POD's storage
      • Add SELinux support
      • NFS transport failback
      • Upgrade legacy persistent volumes for capacity enforcement
      • Troubleshooting
    • Convert cluster to multi-container backend
    • Create a client image
    • Update WMS and WSA
    • BIOS tool
Powered by GitBook
On this page
  • WMS deployment prerequisites
  • Prerequisites for the target bare metal servers
  • Before you begin
  • WMS deployment workflow
  • 1. Install the WMS
  • 2. Configure the WMS
  • 3. Add the WSA package to the WMS
  • 4. Install a WEKA Cluster
  • What to do next?
  1. Planning and Installation
  2. WEKA cluster installation on bare metal servers

Install the WEKA cluster using the WMS with WSA

PreviousObtain the WEKA installation packagesNextInstall the WEKA cluster using the WSA

Last updated 5 months ago

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.

WMS deployment prerequisites

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

  • Boot type: UEFI boot.

  • Cores and RAM:

    • If not configuring LWH: minimum 4 cores and 16 GiB.

  • Network interface: 1 Gbps.

Prerequisites for the target bare metal servers

  • 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 you begin

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.

WMS deployment workflow

1. Install the WMS

  1. 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).

Depending on the server manufacturer, consult the documentation for the server’s BMC (for example, iLO, iDRAC, and IPMI) for detailed instructions on mounting and booting from a bootable ISO image, such as:

  • A workstation or laptop sent to the BMC through the web browser.

  • An SMB share in a Windows server or a Samba server.

  • An NFS share.

To use PXE boot, use the WEKA Management Station as any other Operating System ISO image and configure accordingly.

Burn the WMS image to a DVD and boot it from the physical DVD. However, most modern servers do not have DVD readers anymore.

A bootable USB drive should work (follow online directions for creating a bootable USB drive) but has not been tested yet.

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.

2. Configure the WMS

Once the WMS installation is complete and rebooted, configure the WMS.

  1. Run the OS using one of the following options:

Run the OS through the BMC’s Console. See the specific manufacturer’s BMC documentation.

Run the OS through the Cockpit Web Interface on port 9090 of the OS management network.

If you don’t know the WMS hostname or IP address, go to the console and press the Return key a couple of times until it prompts the URL of the WMS OS Web Console (Cockpit) on port 9090.

Change the port from 9090 to 8051, which is the WMS Admin port.

  1. Configure a local time server: If the WMS does not have access to the Internet, ensure that your local network includes a time server.

    1. Update the configuration file /etc/chrony.conf to point to the local time server.

    2. Refer to the Chrony documentation for detailed instructions on configuring this file.

  2. Browse to the WMS Admin UI using the following URL: http://<WMS-hostname-or-ip>:8501

  1. Enter username and password (default: admin/admin), and select Login. The Landing Page appears.

3. Add the WSA package to the WMS

  1. Copy the WSA package to /home/weka . For example: scp <wsa.iso> weka@<wms-server>:

4. Install a WEKA Cluster

  1. Go to the WMS Admin UI (landing page) and select Deploy a WEKA Custer.

The WSA setup page opens.

  1. Select Standard Install/Reset.

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

  1. In Step 2 - Value entry method, select one of the following options:

    • Option 1: Manually enter values: Click this option and go to Step 4 to enter the number of servers to deploy.

    • Option 2: Upload CSV file to pre-populate data: If you have the environment data in a CSV file, click this option. 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:

IPMI_IP,Username,Password,OS_Mgmt_IP,Hostname,OS_Netmask,OS_Gateway,MTU,DNS,Hostname_Pattern,Hostname_Startnum,Server_Count,Data1_IP,Data1_Type,Data1_Netmask,Data1_MTU,Data1_Gateway,Data2_IP,Data2_Type,Data2_Netmask,Data2_MTU,Data2_Gateway
172.29.1.63,ADMIN,ADMIN,10.10.20.11,weka01,24,10.10.20.1,1500,8.8.8.8,weka%02d,1,7,10.100.10.11,Ethernet,16,9000,,10.100.20.11,Ethernet,16,9000,
172.29.1.64,ADMIN,ADMIN,10.10.20.12,weka02,24,10.10.20.1,1500,8.8.8.8,weka%02d,1,7,10.100.10.12,Ethernet,16,9000,,10.100.20.12,Ethernet,16,9000,
172.29.1.65,ADMIN,ADMIN,10.10.20.13,weka03,24,10.10.20.1,1500,8.8.8.8,weka%02d,1,7,10.100.10.13,Ethernet,16,9000,,10.100.20.13,Ethernet,16,9000,
172.29.1.66,ADMIN,ADMIN,10.10.20.14,weka04,24,10.10.20.1,1500,8.8.8.8,weka%02d,1,7,10.100.10.14,Ethernet,16,9000,,10.100.20.14,Ethernet,16,9000,
172.29.1.67,ADMIN,ADMIN,10.10.20.15,weka05,24,10.10.20.1,1500,8.8.8.8,weka%02d,1,7,10.100.10.15,Ethernet,16,9000,,10.100.20.15,Ethernet,16,9000,
172.29.1.68,ADMIN,ADMIN,10.10.20.16,weka06,24,10.10.20.1,1500,8.8.8.8,weka%02d,1,7,10.100.10.16,Ethernet,16,9000,,10.100.20.16,Ethernet,16,9000,
172.29.1.69,ADMIN,ADMIN,10.10.20.17,weka07,24,10.10.20.1,1500,8.8.8.8,weka%02d,1,7,10.100.10.17,Ethernet,16,9000,,10.100.20.17,Ethernet,16,9000,
  1. 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.

  1. In Step 5 - IPMI information, do the following:

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

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

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

  2. In Step 8 - Save configuration files and inventory, click Save Files to save the configuration files, and then click Next.

  3. In Step 9 - Prepare WSA ISO for installation, click Prepare WSA ISO for install. The WMS updates the kickstart on the ISO to match the WMS deployment data (it takes about 30 seconds).

When the WSA ISO preparation is completed, the output is displayed. Verify that no errors appear. Then, click Next.

  1. In Step 10 - Start Installation, do the following:

    1. Select Confirm overwrite of all boot drive OS and data on hosts.

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

  2. In Step 11 - Run OS and Dataplane Configuration Scripts, click Run system configuration scripts. This action runs scripts to configure the servers with the specified dataplane IPs and perform additional tasks, such as populating /etc/hosts.

What to do next?

Configure the WEKA cluster using the WEKA Configurator

If configuring LWH: See the SSD-backed storage requirements section in .

If configuring LWH, see the Server minimum CPU and RAM requirements section in .

Download the latest release of the WSA package from dashboard.

get.weka.io
Install the WMS
Configure the WMS
Add the WSA package to the WMS
Install a WEKA Cluster
#1.-verify-prerequisites
#1.-verify-prerequisites
Install the WEKA cluster using the WMS with WSA
WMS installation progress
Cockpit URL (IP address of this WMS is 172.29.7.152)
WMS Admin UI: Login Page
WMS Landing Pag
WSA Setup