W E K A
4.2
4.2
  • WEKA v4.2 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
      • Perform post-configuration procedures
      • Add clients
    • 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
        • Auto scaling group
        • Troubleshooting
    • WEKA installation on Azure
    • 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
      • Troubleshooting
  • 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
    • 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 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
    • Manage the SMB protocol
      • Manage SMB using the GUI
      • Manage SMB using the CLI
  • 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
    • 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
      • Expand specific resources of a container
      • Shrink a cluster
    • Background tasks
      • Manage background tasks using the GUI
      • Manage background tasks using the CLI
    • Upgrade WEKA versions
  • Billing & Licensing
    • License overview
    • Classic license
  • 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 and statistics
      • Manage alerts and integrations
      • Enforce security and compliance
      • Optimize support and data management
    • Set up the WEKAmon external monitoring
    • Set up the SnapTool external snapshots manager
  • 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
  • Best Practice Guides
    • WEKA and Slurm integration
      • Avoid conflicting CPU allocations
    • Storage expansion best practice
  • 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
Powered by GitBook
On this page
  • CPU
  • Memory
  • Operating system
  • WEKA installation directory
  • Networking
  • Supported network adapters
  • Ethernet drivers and configurations
  • InfiniBand drivers and configurations
  • Required ports
  • HA
  • SSDs
  • Object store
  • Certified object stores
  • Virtual Machines
  • KMS
  1. Planning and Installation

Prerequisites and compatibility

This page describes the prerequisites and compatibility for the installation of the WEKA system.

PreviousGlossaryNextWEKA cluster installation on bare metal servers

Last updated 1 month ago

Important: The versions mentioned on the prerequisites and compatibility page are applicable to the WEKA system's latest minor version (4.2.X). For information on new features and supported prerequisites released with each minor version, refer to the relevant release notes available at .

Check the release notes for details about any updates or changes accompanying the latest releases.

In certain instances, WEKA collaborates with Strategic Server Partners to conduct platform qualifications alongside complementary components. Contact your designated WEKA representative with any inquiries.

CPU

  • 2013 Intel® Core™ processor family (formerly Haswell) and later (dual-socket)

  • AMD EPYC™ processor families 2nd (Rome), 3rd (Milan-X), and 4th (Genoa) Generations (Backends: single-socket; Clients: single-socket and dual-socket)

Intel processor families SandyBridge (2011) and IvyBridge (2012) have been deprecated, and support for these processors will be discontinued in version 4.3.

Ensure the BIOS settings meet the following requirements:

  • AES must be enabled.

  • Secure Boot must be disabled.

Memory

  • Sufficient memory to support the WEKA system needs as described in .

  • More memory support for the OS kernel or any other application.

Operating system

WEKA will support upcoming releases of the operating systems in the lists within one quarter (three months) of their respective General Availability (GA) dates.

  • RHEL:

    • 9.4, 9.3, 9.2, 9.1, 9.0

    • 8.10, 8.9, 8.8, 8.7, 8.6, 8.5, 8.4, 8.3, 8.2, 8.1, 8.0

    • 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3, 7.2

  • Rocky Linux:

    • 9.4, 9.3, 9.2, 9.1, 9.0

    • 8.10, 8.9, 8.8, 8.7, 8.6

  • CentOS:

    • 8.5, 8.4, 8.3, 8.2, 8.1, 8.0

    • 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3, 7.2

  • Ubuntu:

    • 22.04

    • 20.04

    • 18.04

  • Amazon Linux:

    • AMI 2018.03

    • AMI 2017.09

  • Amazon Linux 2 LTS (formerly Amazon Linux 2 LTS 17.12)

    • Latest update package that was tested: 5.10.176-157.645.amzn2.x86_64

  • RHEL:

    • 9.4, 9.3, 9.2, 9.1, 9.0

    • 8.10, 8.9, 8.8, 8.7, 8.6, 8.5, 8.4, 8.3, 8.2, 8.1, 8.0

    • 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3, 7.2

  • Rocky Linux:

    • 9.4, 9.3, 9.2, 9.1, 9.0

    • 8.10, 8.9, 8.8, 8.7, 8.6

  • CentOS:

    • 8.5, 8.4, 8.3, 8.2, 8.1, 8.0

    • 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3, 7.2

  • Ubuntu:

    • 22.04

    • 20.04

    • 18.04

  • Amazon Linux:

    • AMI 2018.03

    • AMI 2017.09

  • Amazon Linux 2 LTS (formerly Amazon Linux 2 LTS 17.12)

    • Latest update package that was tested: 5.10.176-157.645.amzn2.x86_64

  • SLES:

    • 15 SP5

    • 15 SP4

    • 15 SP2

    • 12 SP5

  • Oracle Linux:

    • 9

  • Debian:

    • 12

  • AlmaLinux OS:

    • 9.4

    • 8.10

The following kernel versions are supported:

  • 6.0 to 6.5

  • 5.3 to 5.19

  • 4.4.0-1106 to 4.19

  • 3.10

  • Kernels 5.15 and higher are not supported with Amazon Linux operating systems.

  • It is recommended to turn off auto kernel updates, so it will not get upgraded to an unsupported version.

  • Confirm that both the kernel version and the operating system version are listed as supported, as these are distinct components with their own compatibility considerations.

  • For clarity, the range of supported versions is inclusive.

General

  • All WEKA servers must be synchronized in date/time (NTP recommended)

SELinux

  • SELinux is supported in both permissive and enforcing modes.

    • The targeted policy is supported.

    • The mls policy is not supported yet.

  • To set the SELinux security context for files, use the -o acl in the mount command, and define the wekafs to use extended attributes in the SELinux policy configuration (fs_use_xattr).

  • The maximum size for the Extended Attributes (xattr) is limited to 1024. This attribute is crucial in supporting Access Control Lists (ACL) and Alternate Data Streams (ADS) in SMB. Given its finite capacity, exercise caution when using ACLs and ADS on a filesystem using SELinux.

cgroups

  • WEKA backends and clients that serve protocols must be deployed on a supported OS with cgroups V1 (legacy).

WEKA installation directory

  • WEKA installation directory: /opt/weka

    • /opt/weka must be a direct path. Do not use a symbolic link (symlink).

  • Boot drive minimum requirements:

    • Capacity: NVMe SSD with 960 GB capacity

    • Durability: 1 DWPD (Drive Writes Per Day)

    • Write throughput: 1 GB/s

  • Boot drive considerations:

    • Do not share the boot drive.

    • Do not mount using NFS.

    • Do not use a RAM drive remotely.

    • If two boot drives are available:

      • It is recommended to dedicate one boot drive for the OS and the other for the /opt/weka directory.

      • Do not use software RAID to have two boot drives.

  • Software required space:

    • Ensure that at least 26 GB is available for the WEKA system installation.

    • Allocate an additional 10 GB per core used by WEKA.

  • Filesystem requirement:

    • Set a separate filesystem on a separate partition for /opt/weka.

Networking

Adhere to the following considerations when choosing the adapters:

  • : LACP is supported when bonding ports from dual-port Mellanox NICs into a single Mellanox device but is not compatible when using Virtual Functions (VFs).

  • Intel E810:

    • The ice Linux Base Driver version 1.9.11 and firmware version 4.0.0 are required.

  • : It is recommended to set the MTU to at least 4k on the NICs of WEKA cluster servers and the connected switches.

  • : If any network connection, irrespective of whether it’s InfiniBand or Ethernet, on a given backend possess the capability to transmit frames exceeding 4 KB in size, it is mandatory for all network connections used directly by WEKA on that same backend to have the ability to transmit frames of at least 4 KB.

  • support: WEKA automatically detects and enables IOMMU for the server and PCI devices. Manual enablement is not required.

  • Shared networking Also known as single IP, allows a single IP address to be assigned to the Physical Function (PF) and shared across multiple Virtual Functions (VFs).

  • Mixed networks: A mixed network configuration refers to a setup where a WEKA cluster connects to both InfiniBand and Ethernet networks. RDMA is not supported in mixed networks.

  • IP Addressing for dataplane NICs: Exclusively use static IP addressing. DHCP is not supported for dataplane NICs.

  • WEKA peer connectivity requires NAT-free networking WEKA requires visibility and connectivity to all peers, without interference from networking technologies like network address translation, or NAT.

Supported network adapters

The following table provides the supported network adapters along with their supported features for backends and clients, and clients-only.

For more information about the supported features, see WEKA networking.

Supported network adapters for backends and clients

Adapter
Protocol
Supported features

Amazon ENA

Ethernet

  • SRIOV VF

Broadcom BCM957508-P2100G dual port

Ethernet

  • Shared networking

  • SRIOV VF

  • HA

  • Routed network

Intel E810 2CQDA2

Ethernet

  • Shared networking

  • HA

  • Routed network

NVIDIA Mellanox CX-7 single port

InfiniBand

  • Shared networking

  • rx interrupts

  • RDMA

  • HA

  • PKEY

  • IOMMU

NVIDIA Mellanox CX-7 dual port

InfiniBand

  • Shared networking

  • rx interrupts

  • RDMA

  • HA

  • PKEY

  • IOMMU

NVIDIA Mellanox CX-7-ETH single port

Ethernet

  • Shared networking

  • HA

  • Routed network (ETH only)

  • IOMMU

NVIDIA Mellanox CX-7-ETH dual port

Ethernet

  • LACP

  • Shared networking

  • HA

  • Routed network (ETH only)

  • IOMMU

NVIDIA Mellanox CX-6 LX

Ethernet

  • Shared networking

  • rx interrupts

  • HA

  • Routed network (ETH only)

  • IOMMU

NVIDIA Mellanox CX-6 DX

Ethernet

  • LACP

  • Shared networking

  • rx interrupts

  • RDMA

  • HA

  • Routed network (ETH only)

  • IOMMU

NVIDIA Mellanox CX-6

Ethernet InfiniBand

  • Mixed networks

  • Shared networking

  • rx interrupts

  • RDMA (IB only)

  • HA

  • IOMMU

NVIDIA Mellanox CX-5 EX

Ethernet InfiniBand

  • Mixed networks

  • RDMA (IB only)

  • HA

  • PKEY (IB only)

  • IOMMU

NVIDIA Mellanox CX-5 BF

Ethernet

  • Mixed networks

  • HA

  • IOMMU

NVIDIA Mellanox CX-5

Ethernet InfiniBand

  • Mixed networks

  • rx interrupts

  • RDMA (IB only)

  • HA

  • PKEY (IB only)

  • Routed network (ETH only)

  • IOMMU

NVIDIA Mellanox CX-4 LX

Ethernet InfiniBand

  • Mixed networks

  • rx interrupts

  • HA

  • Routed network (ETH only)

  • IOMMU

NVIDIA Mellanox CX-4

Ethernet InfiniBand

  • Mixed networks

  • rx interrupts

  • HA

  • Routed network (ETH only)

  • IOMMU

Supported network adapters for clients-only

The following network adapters support Ethernet and SRIOV VF for clients only:

  • Intel X540

  • Intel X550-T1

  • Intel X710

  • Intel X710-DA2

  • Intel XL710

  • Intel XL710-Q2

  • Intel XXV710

  • Intel 82599ES

  • Intel 82599

Avoid using the Intel X550-T1 adapter in a single client connected to multiple clusters.

Ethernet drivers and configurations

  • Supported Mellanox OFED versions for the Ethernet NICs:

    • 23.10-0.5.5.0

    • 23.04-1.1.3.0

    • 5.9-0.5.6.0

    • 5.8-3.0.7.0

    • 5.8-1.1.2.1 LTS

    • 5.7-1.0.2.0

    • 5.6-2.0.9.0

    • 5.6-1.0.3.3

    • 5.4-3.5.8.0 LTS

    • 5.4-3.4.0.0 LTS

    • 5.1-2.6.2.0

    • 5.1-2.5.8.0

    Note: Subsequent OFED minor versions are expected to be compatible with Nvidia hardware due to Nvidia's commitment to backwards compatibility.

  • Supported ENA drivers:

    • 1.0.2 - 2.0.2

    • A current driver from an official OS repository is recommended

  • Supported ixgbevf drivers:

    • 3.2.2 - 4.1.2

    • A current driver from an official OS repository is recommended

  • Supported Intel 40 drivers:

    • 3.0.1-k - 4.1.0

    • A current driver from an official OS repository is recommended

  • Supported ice drivers:

    • 1.9.11

  • Supported Broadcom drivers:

    • 228

  • Ethernet speeds:

    • 400 GbE / 200 GbE / 100 GbE / 50GbE / 40 GbE / 25 GbE / 10 GbE.

  • NICs bonding:

    • Supports bonding dual ports on the same NVIDIA Mellanox NIC using mode 4 (LACP) to enhance redundancy and performance.

  • IEEE 802.1Q VLAN encapsulation:

    • Tagged VLANs are not supported.

  • VXLAN:

    • Virtual Extensible LANs are not supported.

  • DPDK backends and clients using NICs supporting shared networking (single IP):

    • Require one IP address per client for both management and data plane.

    • SR-IOV enabled is not required.

  • DPDK backends clients using NICs supporting non-shared networking:

    • IP address for management: One per NIC (configured before WEKA installation).

      • Ensure the device supports a maximum number of VFs greater than the number of physical cores on the server.

      • Set the number of VFs to match the cores you intend to dedicate to WEKA.

      • Note that some BIOS configurations may be necessary.

    • SR-IOV: Enabled in BIOS.

  • UDP clients:

    • Use a single IP address for all purposes.

When assigning a network device to the WEKA system, no other application can create VFs on that device.

InfiniBand drivers and configurations

WEKA supports the following Mellanox OFED versions for the InfiniBand adapters:

  • 23.10-0.5.5.0

  • 23.04-1.1.3.0

  • 5.9-0.5.6.0

  • 5.8-3.0.7.0

  • 5.8-1.1.2.1 LTS

  • 5.7-1.0.2.0

  • 5.6-2.0.9.0

  • 5.6-1.0.3.3

  • 5.4-3.5.8.0 LTS

  • 5.4-3.4.0.0 LTS

  • 5.1-2.6.2.0

  • 5.1-2.5.8.0

Note: Subsequent OFED minor versions are expected to be compatible with Nvidia hardware due to Nvidia's commitment to backwards compatibility.

WEKA supports the following InfiniBand configurations:

  • InfiniBand speeds: Determined by the InfiniBand adapter supported speeds (FDR / EDR / HDR / NDR).

  • Subnet manager: Configured to 4092.

  • One WEKA system IP address for management and data plane.

  • PKEYs: One partition key is supported by WEKA.

  • Redundant InfiniBand ports can be used for both HA and higher bandwidth.

Required ports

When configuring firewall ingress and egress rules, the following access must be allowed.

Right-scroll the table to view all columns.

Purpose
Source
Target
Target Ports
Protocol
Comments

WEKA server traffic for bare-metal deployments

All WEKA backend IPs

All WEKA backend IPs

14000-14100 (drives) 14200-14300 (frontend) 14300-14400 (compute)

TCP and UDP TCP and UDP TCP and UDP

These ports are the default for the Resources Generator for the first three containers. You can customize the ports.

WEKA client traffic

Client host IPs

All WEKA backend IPs

14000-14100 (drives) 14300-14400 (compute)

TCP and UDP TCP and UDP

These ports are the default. You can customize the ports.

WEKA backend to client traffic

All WEKA backend IPs

Client host IPs

14000-14100 (frontend)

TCP and UDP

These ports are the default. You can customize the ports.

WEKA SSH management traffic

All WEKA backend IPs

All WEKA backend IPs

22

TCP

WEKA server traffic for cloud deployments

All WEKA backend IPs

All WEKA backend IPs

14000-14100 (drives)

15000-15100 (compute)

16000-16100 (frontend)

TCP and UDP TCP and UDP TCP and UDP

These ports are the default. You can customize the ports.

WEKA client traffic (on cloud)

Client host IPs

All WEKA backend IPs

14000-14100 (drives)

15000-15100 (compute)

TCP and UDP TCP and UDP

These ports are the default. You can customize the ports.

WEKA backend to client traffic (on cloud)

All WEKA backend IPs

Client host IPs

14000-14100 (frontend)

TCP and UDP

These ports are the default. You can customize the ports.

WEKA GUI access

All WEKA management IPs

14000

TCP

User web browser IP

NFS

NFS client IPs

WEKA NFS backend IPs

2049 <mountd port>

TCP and UDP TCP and UDP

You can set the mountd port using the command: weka nfs global-config set --mountd-port

SMB/SMB-W

SMB client IPs

WEKA SMB backend IPs

139 445

TCP TCP

SMB-W

WEKA SMB backend IPs

2224

TCP

This port is required for internal clustering processes.

SMB/SMB-W

WEKA SMB backend IPs

All Domain Controllers for the selected Active Directory Domain

88

389 464 636 3268 3269

TCP and UDP TCP and UDP TCP and UDP TCP and UDP TCP and UDP TCP and UDP

These ports are required for SMB/SMB-W to use Active Directory as the identity source. Furthermore, every Domain Controller within the selected AD domain must be accessible from the WEKA SMB servers.

SMB/SMB-W

WEKA SMB backend IPs

DNS servers

53

TCP and UDP

S3

S3 client IPs

WEKA S3 backend IPs

9000

TCP

This port is the default. You can customize the port.

wekatester

All WEKA backend IPs

All WEKA backend IPs

8501 9090

TCP TCP

Port 8501 is used by wekanetperf.

WEKA Management Station

User web browser IP

WEKA Management Station IP

80 <LWH>

443 <LWH>

3000 <mon>

7860 <admin UI>

8760 <deploy>

8090 <snap>

8501 <mgmt> 9090 <mgmt>

9091 <mon> 9093 <alerts>

HTTP

HTTPS

TCP

TCP

TCP

TCP TCP

TCP TCP

Cloud WEKA Home, Local WEKA Home

All WEKA backend IPs

Cloud WEKA Home or Local WEKA Home

80 443

HTTP HTTPS

Open according to the directions in the deployment scenario: - WEKA server IPs to CWH or LWH. - LWH to CWH (if forwarding data from LWH to CWH)

Troubleshooting by the Customer Success Team (CST)

All WEKA backend IPs

CST remote access

4000 4001

TCP TCP

HA

SSDs

  • The SSDs must support PLP (Power Loss Protection).

  • WEKA system storage must be dedicated, and partitioning is not supported.

  • The supported drive capacity is up to 30 TB.

Object store

  • API must be S3 compatible:

    • GET

      • Including byte-range support with expected performance gain when fetching partial objects

    • PUT

      • Supports any byte size of up to 65 MiB

    • DELETE

    • GET after a single PUT is strongly consistent

    • Multiple PUTs are eventually consistent

Certified object stores

  • Amazon S3

    • S3 Standard

    • S3 Intelligent-Tiering

    • These storage classes are ideal for remote buckets where data is written once and accessed in critical situations, such as during disaster recovery:

      • S3 Standard-IA

      • S3 One Zone-IA

      • S3 Glacier Instant Retrieval

      Remember, retrieval times, minimum storage periods, and potential charges due to object compaction may apply. If unsure, use S3 Intelligent-Tiering.

  • Azure Blob Storage

  • Google Cloud Storage (GCS)

  • Cloudian HyperStore (version 7.3)

  • Dell EMC ECS (v3.5 and higher)

  • Dell PowerScale S3 (version 9.8.0.0)

  • HCP Classic V9.2 and up (with versioned buckets only)

  • HCP for Cloud-Scale V2.x

  • IBM Cloud Object Storage System (version 3.14.7)

  • Lenovo MagnaScale (version 3.0)

  • Quantum ActiveScale (version 5.5.1)

  • Red Hat Ceph Storage (version 5.0)

  • Scality Ring (version 7.4.4.8)

  • Scality Artesca (version 1.5.2)

  • SwiftStack (version 6.30)

  • Spectra Logic BlackPearl with Vail for remote buckets (version 5.7.1)

  • WEKA S3

Virtual Machines

Virtual Machines (VMs) can be used as clients only. Ensure the following prerequisites are met for the relevant client type:

  • To avoid irregularities, crashes, and inability to handle application load, make sure there is no CPU starvation to the WEKA process by reserving the CPU in the virtual platform and dedicating a core to the WEKA client.

  • The root filesystem must handle a 3K IOPS load by the WEKA client.

  • To avoid irregularities, crashes, and inability to handle application load, make sure there is no CPU starvation to the WEKA process by reserving the CPU in the virtual platform and dedicating a core to the WEKA client.

  • The root filesystem must handle a 3K IOPS load by the WEKA client.

  • The virtual platform interoperability, such as a hypervisor, NICs, CPUs, and different versions, must support DPDK and virtual network driver.

Special note for a VMware platform
  • If using vmxnet3 devices, do not enable the SR-IOV feature (which prevents the vMotion feature). Each frontend process requires a vmxnet3 device and IP, with an additional device and IP per client VM (for the management process).

  • Using vmxnet3 is only supported with core dedication.

KMS

    • The KMS must support encryption-as-a-service (KMIP encrypt/decrypt APIs)

A watchdog driver should be installed in /dev/watchdog (hardware watchdog recommended); search the WEKA knowledge base in the for more information and how-to articles.

If using mlocate or alike, it's advisable to exclude wekafs from updatedb filesystems lists; search the WEKA knowledge base in the for more information and how-to articles.

Only supported on RHEL 8.6 and Rocky Linux 8.6. For other operating systems, consult with the .

IP address for data plane: One per in each server (applied during cluster initialization).

(VFs):

If it is necessary to change PKEYs, contact the .

See .

IOMMU mode is not supported for SSD drives. If you need to configure IOMMU on WEKA cluster servers, for instance, due to specific applications when running the WEKA cluster in converged mode, contact our for assistance.

To get the best performance, ensure is supported by the device and enabled in the operating system.

Data Consistency: :

For additional information and how-to articles, search the WEKA Knowledge Base in the or contact the .

(version 1.1.5 up to 1.14.x)

-compliant KMS (protocol version 1.2 and up)

KMIP certification has been conducted with Equinix SmartKey (powered by )

WEKA support portal
WEKA support portal
Virtual Functions
TRIM
Amazon S3 consistency model
HashiCorp Vault
KMIP
Fortanix KMS
get.weka.io
WEKA support portal
High Availability (HA)
memory requirements
WEKA core
Customer Success Team
Customer Success Team
Customer Success Team
Customer Success Team