It is possible to update some configurations of a running cluster using the Cluster Manager.
From the
Edit Cluster Configuration menu you can update the cluster
configuration. Where possible, the cluster manager pushes the new configurations to the
running cluster and restarts the necessary services.
Note: Configurations that can only be set
upon initial boot require relaunching the nodes in the cluster. Currently the administrator
has to terminate and launch new nodes manually.
Options Configurable on a Live Server
The following cluster configuration
options can be updated on a live cluster by editing the cluster configuration (select
Edit Cluster Configuration from the
Action)
drop-down menu), or in some cases, by using the Cluster Manager console GUI.
| Configuration |
Cluster Conf |
GUI |
| EIP pool |
X |
|
| Image ID for cluster nodes Note: Changing this setting triggers an image upgrade
by launching replacement nodes for all existing cluster nodes and phasing out old
nodes.
|
X |
|
| Authentication settings and TTL in DNS configuration |
X |
|
| Cluster timeout settings |
X |
|
| SSHD configuration |
X |
|
| Max bandwidth |
X |
|
| Use bandwidth |
X |
|
| Use buffer uitilization |
X |
|
| Auto scaling configuration |
X |
X Select the cluster and click Auto Scaling >
Edit
|
| SSL certificate |
X |
X Select the cluster and click SSL > Edit
|
| Transfer server configuration file (aspera.conf) |
X |
X Select the cluster and click Transfer Configuration >
Edit
|
Options Configurable by Relaunching Nodes
The following options can only
be set during the server boot process. The recommended method for enabling these options is to
make the desired changes by editing the cluster configuration file and then cycle the nodes
out of the cluster by terminating them one by one. The Cluster Manager will relaunch the nodes
with the new settings.
- Infrastructure settings
- Security groups
- SSH keys
- License entitlement info