W E K A
3.14
3.14
  • WEKA v3.14 Documentation
  • Weka System Overview
    • About the WEKA System
    • SSD Capacity Management
    • Filesystems, Object Stores & Filesystem Groups
    • Weka Networking
    • Data Lifecycle Management
    • Weka Client & Mount Modes
    • Glossary
  • Getting Started with Weka
    • Quick Install Guide
    • Managing the Weka System
    • CLI Overview
    • GUI Overview
    • Serving IOs with WekaFS
  • Planning & Installation
    • Prerequisites for Installation
    • Bare Metal Installation
      • Planning a Weka System Installation
      • Setting Up the Hosts
        • SR-IOV Enablement
      • Obtaining the Weka Install File
      • Weka System Installation Process Using the CLI
      • Adding Clients
    • AWS Installation
      • Self-Service Portal
      • CloudFormation Template Generator
      • Deployment Types
      • AWS Outposts Deployment
      • Supported EC2 Instance Types
      • Adding Clients
      • Auto Scaling Group
      • Troubleshooting
  • Performance
    • Testing Weka Performance
      • Test Environment Details
  • WekaFS Filesystems
    • Managing Filesystems, Object Stores & Filesystem Groups
      • Managing Object Stores
      • Managing Filesystem Groups
      • Managing Filesystems
      • Attaching/Detaching Object Stores to/from Filesystems
      • KMS Management
    • 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
    • Mounting Filesystems
    • Snapshots
    • Snap-To-Object
    • Quota Management
  • Additional Protocols
    • NFS
    • SMB
      • SMB Management Using CLIs
      • SMB Management Using the GUI
    • S3
      • S3 Cluster Management
      • S3 Buckets Management
      • S3 Users and Authentication
      • S3 Information Lifecycle Management
      • Audit S3 APIs
      • S3 Limitations
      • S3 Examples using boto3
  • Operation Guide
    • Alerts
      • List of Alerts
    • Events
      • List of Events
    • Statistics
      • List of Statistics
    • System Congestion
    • Security
      • User Management
      • Organizations
    • Expanding & Shrinking Cluster Resources
      • Expand & Shrink Overview
      • Stages in Adding a Backend Host
      • Expansion of Specific Resources
      • Shrinking a Cluster
    • Background Tasks
    • Upgrading Weka Versions
  • Billing & Licensing
    • License Overview
    • Classic License
    • Pay-As-You-Go License
  • Support
    • Prerequisites and Compatibility
    • Getting Support for Your Weka System
    • The Weka Support Cloud
    • Diagnostics CLI Command
  • Appendix
    • Weka CSI Plugin
    • External Monitoring
    • Snapshot Management
  • REST API
Powered by GitBook
On this page
  • Prerequisites
  • Installation
  • Configuration
  1. Getting Started with Weka

Quick Install Guide

PreviousGlossaryNextManaging the Weka System

Last updated 3 years ago

For a complete installation guide, as well as the self-service portal on AWS refer to the following pages:

Prerequisites

For a complete prerequisite list, refer to section.

We'll consider an example of architecture with 8 identical hosts (named weka01 to weka08). Each host has more than 20 cores, 6 NVME drives, and a single Mellanox NIC.

Using Mellanox NICs simplifies the installation commands (e.g., only single IP for data is required, no need to expose VFs, identification of the interface netmask, and default routing gateway).

If the architecture is different, the installation commands should be slightly changed accordingly.

For a full command set, refer to section.

Installation

Install Weka software on each host:

# deploy the software on all hosts
pdsh -w weka0[1-8] "curl https://[GET.WEKA.IO-TOKEN]@get.weka.io/dist/v1/install/3.8.0/3.8.0 | sudo sh"

Configuration

From one of the servers, form the cluster, set the cluster name, stripe width, and protection scheme, and enable cloud monitoring (DNS is assumed to be set up, otherwise explicit IPs should be used in the cluster create command):

# connect to one of the servers and run the rest of the configuration from there
ssh weka01

# form the cluster and set basic stuff
# using bash, you can provide a compact list of hosts; otherwise, a full list of all hosts should be supplied
# weka cluster create weka01 weka02 weka03 weka04 weka05 weka06 weka07 weka08
weka cluster create weka0{1..8}
weka cluster update --cluster-name=WekaProd
weka cloud enable

Configure the network, drives, and CPUs per host:

# configure network, drives, and cores per host
# replace network, drives, and cores configuration with your actual data

for i in {0..7}
do
    weka cluster host dedicate $i on
    
    # add network NICs
    # e.g., weka cluster host net add $i eth1
    weka cluster host net add $i NETDEV
    
    # add the nvme drives; e.g., /dev/nvme0n1, etc.
    weka cluster drive add $i /dev/nvme0n1 /dev/nvme1n1 /dev/nvme2n1 /dev/nvme3n1 /dev/nvme4n1 /dev/nvme5n1
    
    # set host cores
    weka cluster host cores $i 19 --frontend-dedicated-cores 1 --drives-dedicated-cores 6
done

Check the configuration:

# show hosts info (net, cores, etc.)
for i in {0..7}
do
    weka cluster host resources $i
done

# show drives info
weka cluster drive

# show configuration status
weka status

If satisfied, apply the configuration:

# initialize the hosts
weka cluster host apply --all --force

Set a valid license and start the cluster:

# set a license (classic or payg), as obtained from get.weka.io
weka cluster license set LICENSE_TEXT_OBTAINED_FROM_GET_WEKA_IO

# start the cluster
weka cluster start-io

Check the status:

# show cluster info and status
weka status

You would see a similar output to the following example:

WekaIO v3.10.0 (CLI build 3.10.0)

       cluster: WekaProd (00569cef-5679-4e1d-afe5-7e82748887de)
        status: OK (8 backends UP, 48 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

Lastly, change the default admin password, and make sure there are no other alerts in the system.

The Weka system is now installed. Now let's learn how to view, manage, and operate it using either the or the and to a WekaFS filesystem.

AWS Installation
Bare Metal Installation
Prerequisites for Installation
Weka System Installation Process Using the CLI
perform the first IO
CLI
GUI
OFED is installed
NIC devices are configured properly
NTP is set up