W E K A
4.0
4.0
  • WEKA v4.0 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 WekaFS
    • Getting started with Weka REST API
  • Planning & Installation
    • Prerequisites for installation
    • Weka installation on bare metal
      • Planning a Weka System Installation
      • Prepare the system for Weka installation
        • SR-IOV enablement
      • 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
  • Performance
    • Weka performance tests
      • Test environment details
  • WekaFS 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
  • Additional Protocols
    • NFS
      • Manage NFS networking using the GUI
      • Manage NFS networking using the CLI
    • SMB
      • Manage SMB using the GUI
      • Manage SMB using the CLI
    • S3
      • 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 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
      • Expand and shrink overview
      • Workflow: Add a backend host
      • Expansion of specific resources
      • 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
      • Collect and upload diagnostics data
    • 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 Weka-mon external monitoring
    • Set up the SnapTool external snapshots manager
  • REST API Reference Guide
Powered by GitBook
On this page
  • About client hosts
  • Add stateless clients
  • Add stateful clients which are always part of the cluster
  • Stage 1: Install the Weka software
  • Stage 2: Join the cluster
  • Stage 3: Configure the host as a client
  • Stage 4: Configure client networking
  • Stage 5: Apply the host configuration
  1. Planning & Installation
  2. Weka installation on bare metal

Add clients

This page describes how to add clients to a bare-metal cluster.

PreviousWEKA legacy system installation processNextWeka installation on AWS

Last updated 2 years ago

About client hosts

Client hosts are used to running applications that need to access the Weka filesystems. They do not contribute CPUs or drives to the cluster and only connect to the cluster to use its filesystems.

Add stateless clients

To use the Weka filesystems from a client host, all that is needed is to call the mount command. The mount command automatically installs the software version, and there is no need to join the client to the cluster.

To mount a filesystem in this manner, first, install the Weka agent from one of the backend instances and then mount the filesystem. For example:

# Agent Installation (one time)
curl http://Backend-1:14000/dist/v1/install | sh

# Creating a mount point (one time)
mkdir -p /mnt/weka

# Mounting a filesystem
mount -t wekafs Backend-1/my_fs /mnt/weka

For the first mount, this will install the Weka software and automatically configure the client. For more information on mount and configuration options, refer to .

It is possible to configure the client OS to automatically mount the filesystem at boot time. For more information refer to or .

Note: Clients can be deployed on . They can use RAM for Weka client software and NFS mount for the traces. For more information, contact the Weka Support Team.

Note: The different clients must have a unique IP and FQDN.

Add stateful clients which are always part of the cluster

Note: It is possible to add instances that do not contribute resources to the cluster but are used for mounting filesystems. It is recommended to use the previously described method for adding client instances for mounting purposes. However, in some cases it could be useful to permanently add them to the cluster, e.g., to use these instances as NFS/SMB servers which are always expected to be up.

Stage 1: Install the Weka software

Note: All hosts (clients and backends) in a Weka system cluster must use the same software version. If attempts are made to mix multiple versions, the new hosts will fail to join the cluster.

Stage 2: Join the cluster

Command: weka cluster host add

Once the client host is in the stem mode (this is the mode defined immediately after running the install.shcommand), use the following command line on the client host to add it to the cluster:

weka -H <backend-hostname> cluster host add <client-hostname>

Parameters in command line

Name

Type

Value

Limitations

Mandatory

Default

backend-hostname

String

IP/hostname of one of the existing backend instances in the cluster

Existing backend IP/FQDN

Yes

client-hostname

String

IP/hostname of the client currently being added

Unique IP/FQDN

Yes

Note: On completion of this stage, the host-ID of the newly added host will be received. Make a note of it for the next steps.

Stage 3: Configure the host as a client

Command: weka cluster host cores

To configure the new host as a client, run the following command:

weka cluster host cores <host-id> <cores> --frontend-dedicated-cores=<frontend-dedicated-cores>

Parameters in command line

Name

Type

Value

Limitations

Mandatory

Default

host-id

String

Identifier of the host to be added to the cluster

Must be a valid host identifier

Yes

cores

Number

Number of physical cores to be allocated to the Weka client

Maximum 19 cores

Yes

frontend-dedicated-cores

Number

Number of physical cores to be dedicated to FrontEnd processes

For clients, the number of total cores and frontend-dedicated-cores must be equal

Yes, in order to configure a host as a client

Stage 4: Configure client networking

Command: weka cluster host net add

Note: If the new client is to communicate with the Weka system cluster over the kernel UDP stack, it is not necessary to run this command.

If a high-performance client is required and the appropriate network NIC is available, use the following command to configure the networking interface used by the client to communicate with the Weka system cluster hosts:

weka cluster host net add <host-id> <device> --ips=<ips> --netmask=<netmask> --gateway=<gateway>

Parameters in command line

Name

Type

Value

Limitations

Mandatory

Default

host-id

String

Identifier of the host to be added to the cluster

Must be a valid host identifier

Yes

device

String

Network interface device name e.g., eth1

Must be a valid network device name

Yes

ips

IP address

The IP address of the new interface

Must be a valid IP address

Yes

gateway

IP address

The IP address of the default routing gateway

The gateway must reside within the same IP network of ips (as described by netmask).

Not relevant for IB / L2 non-routable networks.

No

netmask

Number

Number of bits in the netmask, e.g., the netmask of 255.255.0.0 has 16 netmask bits

Describes the number of bits that identify a network ID (also known as CIDR).

No

Note: When configuring an InfiniBand client, do not pass the --ips, --netmask and --gateway parameters.

Note: InfiniBand/Ethernet clients can only join a cluster with the same network technology connectivity. It is possible to mix InfiniBand and Ethernet clients in the same cluster as long as the cluster backends are connected to both network technologies.

Stage 5: Apply the host configuration

Command: weka cluster host apply

After successfully configuring the host and its network device, run the following command to finalize the configuration by activating the host:

weka cluster host apply <host-id> [--force]

Parameters in command line

Name

Type

Value

Limitations

Mandatory

Default

host-id

Comma-separated string

Identifier of the host to be added to the cluster

Must be a valid host identifier

Yes

force

Boolean

Do not prompt for confirmation

No

Off

Verify that the Weka software is installed on the client host according to the installation instructions. For further information, see and

diskless-servers
Obtaining the Weka Install File
Stage 1 in Weka System Installation Process.
Mounting Filesystems Using the Stateless Clients Feature
Mounting Filesystems Using fstab
Mounting Filesystems Using autofs