W E K A
4.1
4.1
  • WEKA v4.1 documentation
  • WEKA System Overview
    • About the WEKA system
    • SSD capacity management
    • Filesystems, object stores, and filesystem groups
    • WEKA networking
    • Data lifecycle management
    • WEKA client and mount modes
    • WEKA containers architecture overview
    • Glossary
  • Getting Started with WEKA
    • Quick installation guide
    • Manage the system using the WEKA CLI
    • Manage the system using the WEKA GUI
    • Run first IOs with WEKA filesystem
    • Getting started with WEKA REST API
  • Planning and Installation
    • Prerequisites for installation
    • WEKA installation on bare metal
      • Plan the WEKA system Installation
      • Prepare the system for WEKA software installation
        • Enable the SR-IOV
      • Obtain the WEKA software installation package
      • WEKA cluster installation
        • WEKA legacy system installation process
      • Add clients
    • WEKA installation on AWS
      • Self-service portal
      • CloudFormation template generator
      • Deployment types
      • AWS outposts deployment
      • Supported EC2 instance types
      • Add clients
      • Auto scaling group
      • Troubleshooting
    • WEKA installation on Azure
    • WEKA installation on GCP
      • WEKA project description
      • Deployment on GCP using Terraform
      • GCP Terraform package description
      • Required services and supported regions
      • Supported machine types and storage
      • Auto-scale instances in GCP
      • Add clients
      • Troubleshooting
  • 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
    • 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
    • Quota management
      • Manage quotas using the GUI
      • Manage quotas using the CLI
  • Additional Protocols
    • Manage the NFS protocol
      • Supported NFS client mount options
      • Manage NFS networking using the GUI
      • Manage NFS networking using the CLI
    • Manage the SMB protocol
      • Manage SMB using the GUI
      • Manage SMB 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 rules information lifecycle management (ILM)
        • 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
      • S3 supported APIs and limitations
      • S3 examples using boto3
  • 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
    • System congestion
    • Security management
      • Obtain authentication tokens
      • KMS management
        • Manage KMS using the GUI
        • Manage KMS using the CLI
      • TLS certificate management
        • Manage the TLS certificate using the GUI
        • Manage the TLS certificate using the CLI
      • CA certificate management
        • Manage the CA certificate using the GUI
        • Manage the CA certificate using the CLI
      • Account lockout threshold policy management
        • Manage the account lockout threshold policy using GUI
        • Manage the account lockout threshold policy using CLI
      • Manage the login banner
        • Manage the login banner using the GUI
        • Manage the login banner using the CLI
    • 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 in a multiple containers architecture
      • Add a backend server in a legacy architecture
      • Expand specific resources of a container
      • Shrink a cluster
    • Background tasks
    • Upgrade WEKA versions
  • Billing & Licensing
    • License overview
    • Classic license
    • Pay-As-You-Go license
  • Support
    • Prerequisites and compatibility
    • 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
    • Weka Home - The WEKA support cloud
      • Local Weka Home overview
      • Local Weka Home deployment
      • Set the Local Weka Home to send alerts or events
      • Download the Usage Report or Analytics
  • Appendix
    • WEKA CSI Plugin
    • Set up the WEKAmon external monitoring
    • Set up the SnapTool external snapshots manager
  • REST API Reference Guide
Powered by GitBook
On this page
  • Prerequisites
  • Quick installation for a multi-container backend architecture
  • Install the WEKA software
  • Remove the default container
  • Generate resource files
  • Configuration
  • Post configuration
  1. Getting Started with WEKA

Quick installation guide

PreviousGlossaryNextManage the system using the WEKA CLI

Last updated 1 year ago

This is a quick installation guide. For a complete installation, refer to the following pages:

WEKA installation on bare metal

WEKA installation on AWS

Prerequisites

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.

Quick installation for a multi-container backend architecture

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 the WEKA software

  1. Install WEKA software on all servers:

pdsh -R ssh -w "weka0-[0-7]" "curl https://[GET.WEKA.IO-TOKEN]@get.weka.io/dist/v1/install/4.1.0/4.1.0 | sudo sh"

Remove the default container

  1. Remove the single default container created on each server in the cluster:

pdsh -R ssh -w "weka0-[0-7]" 'weka local stop default && weka local rm -f default'

Generate resource files

  1. Get the resource generator to your local server:

wget 
https://raw.githubusercontent.com/weka/tools/master/install/resources_generator.py
  1. Copy the resource generator from your local server to all servers in the cluster:

for i in {0..7}; do scp resources_generator.py weka0-$i:/tmp/resources_generator.py; done

3. To enable execution, change the mode of the resource generator on all servers in the cluster:

pdsh -R ssh -w "weka0-[0-7]" 'chmod +x /tmp/resources_generator.py'

4. Run resource generator on all servers in the cluster:

pdsh -R ssh -w "weka0-[0-7]" '/tmp/resources_generator.py  --path /tmp --net ens{5..7}'

The resource generator generates three resource files on each server in the /tmp directory: drives0.json, compute0.json, and frontend0.json.

Configuration

Create the drive containers

  1. Create the drive containers from the resource generator output file drives0.json. Run the following command on all servers in the cluster:

pdsh -R ssh -w "weka0-[0-7]" 'weka local setup container --resources-path /tmp/drives0.json'

Create a cluster

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

ssh weka0-1
weka cluster create weka0-{0..7}
weka cluster update --cluster-name=WekaProd

Add a drive to the cluster

  1. Add a drive to each server in the cluster. Run the following command from one of the servers:

for i in {0..7} ; do weka cluster drive add $i /dev/nvme0n1 /dev/nvme1n1 /dev/nvme2n1 /dev/nvme3n1 /dev/nvme4n1 /dev/nvme5n1 ; done

Create compute containers

  1. Create the compute containers from the resource generator output file compute0.json. Run the following command on all servers in the cluster:

pdsh -R ssh -w "weka0-[0-7]" 'weka local setup container --resources-path /tmp/compute0.json --join-ips $(hostname -i)'

Name the cluster and enable event notifications to the cloud

  1. Enable event notifications to the cloud for support purposes. From one of the servers, run the following command:

weka cluster update --cluster-name=WekaProd
weka cloud enable

Set the license

  1. Set the license. From one of the servers, run the following command:

weka cluster license set LICENSE_TEXT_OBTAINED_FROM_GET_WEKA_IO

Start the cluster IO service

  1. Start the cluster IO service. From one of the servers, run the following command:

weka cluster start-io

Create frontend containers

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

 pdsh -R ssh -w "weka0-[0-7]" 'weka local setup container --resources-path /tmp/frontend0.json --join-ips  $(hostname -i)'

Post configuration

Check the cluster configuration

  1. Check the resources per server (such as NICs and cores), drives, and configuration status:

do
    weka cluster container resources $i
done

weka cluster drive

weka status

Output example for a multiple container architecture:

WekaIO v4.1.0 (CLI build 4.1.0)

       cluster: WekaProd (00569cef-5679-4e1d-afe5-7e82748887de)
        status: OK (8 backends UP, 6 drives UP)
    protection: 6+2
     hot spare: 1 failure domains
 drive storage: 82.94 TiB total, 82.94 TiB unprovisioned
         cloud: connected
       license: Unlicensed

     io status: STARTED 7 seconds ago (96 io-nodes UP, 750 buckets UP)
    link layer: Ethernet
       clients: 0 connected
         reads: 0 B/s (0 IO/s)
        writes: 0 B/s (0 IO/s)
    operations: 0 ops/s
        alerts: 1 active alert, use `weka alerts` to list it

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

Run first IOs with WEKA filesystem

Getting started with WEKA REST API

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 .

Obtain the Weka software installation package
get.weka.io
Prerequisites for Installation
#3.-generate-the-resource-files
OFED is installed
NIC devices are configured properly
NTP is set up