Weka system installation process using the CLI
This page describes the stages in the installation process when using the CLI.
Run the untar command and
install.shcommand, according to the instructions, on each host.
On completion of this stage in the installation process, the Weka software is installed on all the allocated hosts and running in the stem mode i.e., no cluster is attached and the Weka system is awaiting instructions.
weka cluster create
This stage involves the formation of a cluster from the allocated hosts. It is performed using the following command line:
weka cluster create <hostnames> [--host-ips <ips | ip+ip+ip+ip>]
On successful completion of the formation of the cluster, every host receives a host ID. Use of the command line
weka cluster hostwill display a list of the hosts and IDs.
weka cluster update
This command is used to give the cluster a name. Although this is optional, it is highly recommended, because the name enables cloud event notification and increases the ability of the Weka Support Team to resolve any issues that may occur. To perform this operation, use the following command line:
weka cluster update --cluster-name=<cluster-name>
weka cloud enable
This command enables cloud event notification (via Weka Home), which increases the ability of the Weka Support Team to resolve any issues that may occur.
In closed environments, such as dark sites and private VPCs, it is possible to install a private instance of Weka Home.
weka cloud enable --cloud-url=http://<weka-home-ip>:<weka-home-port>
This command enables the use of a private instance of Weka Home.
weka cluster host dedicate
It is possible to set the host as dedicated to the Weka cluster. By setting the host to dedicated, no other application is expected to run on it, and the Weka system optimizes it for performance and stability. For example, the host can be rebooted by the system at need, and all the host's memory is allocatable by the Weka processes.
weka cluster host net add
When PKEYs are used, the device name for InfiniBand should follow the name.PKEY convention.
The networking type can be either Ethernet (direct over DPDK) or InfiniBand (IB), and can be mixed in the same host (by running multiple
cluster host net addcommands for the same host). A physical network device must be specified for both types. This can be a device dedicated to the Weka system or a device that is also being used for other purposes in parallel. For IP over DPDK, the standard routing parameters can be specified for routed networks.
To perform this operation, the
cluster host net addcommand must be run for each host. The commands can run from one host configuring another host, so they can all run on a single host. The IP addresses specified using this command are the data plane IPs allocated in the planning stage. To perform this operation, use the following command line:
weka cluster host net add <host-id> <device> [--ips-type=<POOL|USER>] [--ips=<ips>]... [--gateway=<gateway>] [--netmask=<netmask>] [--label=<label>]
weka cluster default-net set
Instead of explicit IP address configuration per each network device, dynamic IP address allocation is supported. Weka supports adding a range of IP addresses to a dynamic pool, from which the IP addresses can be automatically allocated on demand.
weka cluster default-net set --range <range> [--gateway=<gateway>] [--netmask-bits=<netmask-bits>]
To view the current default data networking settings use the command
weka cluster default-net.
If a default data networking was previously configured on a cluster and is no longer needed, it is possible to remove it using the command
weka cluster default-net reset.
weka cluster drive add
This stage in the installation process is used to add a local SSD to be used by a Weka filesystem. The same command can be used for adding multiple drive paths. To perform this operation, use the following command line:
weka cluster drive add <host-id> <device-paths>
weka cluster host cores
This stage in the installation process is used to configure the number of CPU resources, which are physical rather than logical cores. To perform this operation, use the following command line:
weka cluster host cores <host-id> <cores> [--frontend-dedicated-cores <frontend-dedicated-cores>] [--drives-dedicated-cores <drives-dedicated-cores>] [--cores-ids <cores-ids>] [--compute-dedicated-cores <compute-dedicated-cores>] [--only-drives-cores] [--only-compute-cores] [--only-frontend-cores]
weka cluster host memory
As defined in the memory requirements, the fixed memory per host and the per compute/SSD cores memory are automatically calculated by the Weka system. By default, 1.4 GB is allocated per compute-core, out of which 0.4 GB is left for the capacity-oriented memory. If the host is set as dedicated, all the memory left after reductions, as described in Memory Resource Planning, is automatically allocated for the Weka system.
If capacity requirements mandate more memory, the following command should be used:
weka cluster host memory <host-id> <capacity-memory>
weka cluster host failure-domain
This optional stage in the installation process is used to assign a host to a failure domain. If the specified failure domain does not exist, it will be created by this command. If the host is assigned to another failure domain, it will be reassigned by this command.
This operation is performed using the following command line:
weka cluster host failure-domain <host-id> [--name <name>] | [--auto]
weka cluster update
To configure the Weka system protection scheme, use the following command line:
weka cluster update [--data-drives=<data-drives>] [--parity-drives=<parity-drives>]
weka cluster hot-spare
To configure the Weka system hot spare, use the following command line:
weka cluster hot-spare <count>
weka cluster host apply
This command is used to apply the Weka system cluster hosts' configuration. In the install phase, all hosts need to be added, so the
--allparameter can be used.
To activate the cluster hosts, use the following command line:
weka cluster host apply [--all] [<host-ids>...] [--force]
weka cluster host applycommand completes, verify that the operation is successful. Check the alerts and verify that the
ResourcesNotAppliedalertalert does not show.
weka cluster license set / payg
At this point, you've finished configuring and deploying the cluster. To run IOs against the cluster, you need to deploy a license. Follow the steps in obtaining a license section to obtain a valid license and deploy it to the Weka cluster.
weka cluster start-io
To start the system IO and exit from the initialization phase, use the following command line:
weka cluster start-io
After successful completion of this command, the system exits the initialization state and accepts IOs from the user applications.