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
  • License Metrics
  • Cluster Licensing Status
  • Obtaining a License
  1. Billing & Licensing

License Overview

This page describes how licensing works in a Weka system cluster.

License Metrics

A Weka system license measures usage at the cluster level and contains the following properties:

  1. Cluster GUID (created at the time of installation)

  2. Expiry date

  3. Raw or usable hot-tier (SSD) capacity

  4. Object store capacity

When applied, the cluster verifies that the license is valid by comparing these properties and actual cluster usage.

To be able to start-io in a newly configured cluster, a valid license must be set (either a classic or a PAYG license).

Cluster Licensing Status

To view the cluster licensing status, run the weka status command:

# weka status
Weka v3.1.7.2 (CLI build 2.5.3)
...
       license: OK, valid thru 2018-07-31T07:14:05Z
...

In the example status above, it is possible to see that the cluster has a valid license which is due to expire on July 31st 2018. If the cluster does not have a valid license, the licensing status will appear as follows:

# weka status
Weka v3.1.7.2 (CLI build 2.5.3)
...
       license: Unlicensed
...

The system includes cluster alerts which also indicate if the cluster does not have an assigned license. Cluster alerts can be viewed by running the weka alerts command:

# weka alerts
...
No License Assigned
This cluster does not have a license assigned, please go to https://get.weka.io to obtain your license

Obtaining a License

There are two ways to obtain a license for your cluster:

PreviousUpgrading Weka VersionsNextClassic License

Last updated 3 years ago

Classic Licensing: In this method, payment is for a predetermined period of time, e.g., 1 year. See for information more about this method.

Pay-As-You-Go (PAYG) Licensing: In this method, payment is according to hourly usage. See for more information about this method.

Classic Licensing
Pay As You Go