Expansion of specific resources
Guidelines provided for the expansion processes that only involve the addition of specific resources.
Dynamic modifications using the CLI
Most modifications to host configurations can be performed dynamically, without deactivating the host. Such configurations include the addition or removal of memory and network resources, changing IPs, extending network subnets and limiting the Content Software for File system bandwidth on the host.
All these changes can be performed using the relevant weka cluster host
command. Once this command is used with a specific host-id
selected, it will be staged for update on the cluster. To view the un-applied configuration, use the weka cluster host resources <host-id>
command. To apply the changes, use the weka cluster host apply <host-ids>
command. You can also apply these changes locally using the weka local resources apply
command.
The last local configuration (of a host that successfully joined a cluster) is saved. If a failure/problem occurs with the new configuration, the host will automatically revert to the last known good configuration. To view this configuration, use the weka cluster host resources <host-id> --stable
command.
Memory modifications
To dynamically change the memory configuration, use the steps described for the configuration of memory on an active host, followed by the weka cluster host apply command.
For example: to change host-id 0 memory to 1.5 GB, run the following commands:
weka cluster host memory 0 1.5GB weka cluster host apply 0
Network modifications
To dynamically change the network configuration, use the steps described for the Configuration of networking section in the Content Software for File User Guide on an active host, followed by the weka cluster host apply command.
weka cluster host net add 0 --device=eth2 weka cluster host apply 0
For additional information, contact customer support.
Host IPs modifications
To dynamically change the host’s management IPs, you can use the management-ips resource editing command.
weka cluster host management-ips 192.168.1.10 192.168.1.20 weka cluster host apply 0
Local resources editing commands using the CLI
It is also possible to run modification commands locally on the host by connecting to the desired host and running a local resources command equivalent to its weka cluster host counterpart. These local commands have the same semantics of their remote counterparts only that they don't receive the host-id as the first parameter and operate instead on the local host. Commands that can be performed dynamically on an Active host:
weka local resources [--stable] weka local resources apply weka local resources net weka local resources net add weka local resources net remove weka local resources memory weka local resources bandwidth weka local resources management-ips weka local resources dedicate
The following commands cannot be performed on an Active host and require deactivating the host first using weka cluster host deactivate:
weka local resources failure-domain weka local resources cores