To run IOs against the cluster, a valid license must be applied. Obtain a valid license and apply it to the WEKA cluster. For details, see License overview.
3. Start the cluster IO service
Command:weka cluster start-io
To start the system IO and exit from the initialization state, use the following command line:
weka cluster start-io
4. Check the cluster configuration
Check the cluster container
Command:weka cluster container
Use this command to display the list of containers and their details.
Use this command to check all drives in the cluster.
Example
$wekaclusterdriveDISK ID UUID HOSTNAME NODE ID SIZE STATUS LIFETIME % USED ATTACHMENT DRIVE STATUS
0d3d000d4-a76b-405d-a226-c40dcd8d622cav299-487399.99GiBACTIVE0OKOK1c68cf47a-f91d-499f-83c8-69aa06ed37d4av299-7143399.99GiBACTIVE0OKOK2c97f83b5-b9e3-4ccd-bfb8-d78537fa8a6fav299-123399.99GiBACTIVE0OKOK3908dadc5-740c-4e08-9cc2-290b4b311f81av299-07399.99GiBACTIVE0OKOK...681c4c4d54-6553-44b2-bc61-0f0e946919fbav299-484399.99GiBACTIVE0OKOK69969d3521-9057-4db9-8304-157f50719683av299-362399.99GiBACTIVE0OKOK
Check the Weka cluster status
Command:weka status
The weka status command displays the overall status of the WEKA cluster.
5. Bypass the proxy server (optional)
If the WEKA cluster is deployed in an environment with a proxy server, a WEKA client trying to mount or download the client installation from the WEKA cluster may be blocked by the proxy server. You can disable the proxy for specific URLs using the shell no_proxy environment variable.
Procedure
Connect to one of the WEKA backend servers (configuration changes made on this server are synchronized with all other servers in the cluster).
Open the /etc/wekaio/service.conf file.
In the [downloads_proxy] section, add to the no_proxy parameter a comma-separated list of IP addresses or qualified domain names of your WEKA clients and cluster backend servers. Do not use wildcards (*).
[downloads_proxy]force_no_proxy=trueproxy=no_proxy=<comma-separated list of IPs or domains>
Restart the agent service using the command:
serviceweka-agentrestart
6. Configure default data networking (optional)
Command:weka cluster default-net set
Instead of individually configuring IP addresses for each network device, WEKA supports dynamic IP address allocation. Users can define a range of IP addresses to create a dynamic pool, and these addresses can be automatically allocated on demand.
Mixed approach for Ethernet networking: For Ethernet networking, a mixed approach is supported. Administrators can explicitly assign IP addresses for specific network devices, while others in the cluster can receive automatic allocations from the specified IP range. This feature is particularly useful in environments with automated client spawning.
Use the following command to configure default data networking:
weka cluster default-net set --range <range> [--gateway=<gateway>] [--netmask-bits=<netmask-bits>]
Parameters
Parameter
Description
range*
A range of IP addresses reserved for dynamic allocation across the entire cluster..
Format: A.B.C.D-E
Example: 10.10.0.1-100
netmask-bits*
Number of bits in the netmask that define a network ID in CIDR notation.
gateway
The IP address assigned to the default routing gateway. It is imperative that the gateway resides within the same IP network as defined by the specified range and netmask-bits.
This parameter is not applicable to InfiniBand (IB) or Layer 2 (L2) non-routable networks.
View current settings: To view the current default data networking settings, use the command:
weka cluster default-net
Remove default data networking: If a default data networking configuration was previously set up on a cluster and is no longer needed, you can remove it using the command:
weka cluster default-net reset
End of the installation and configuration for all workflow paths
