Note:
- When installing a multi-instance system, make sure you specify the same list of master instance IP addresses on every instance that you are installing.
- When entering IP address lists, do not separate IP addresses with spaces. For example, the following is correct:
sudo install_path/hci/bin/setup ‑i 192.0.2.4 ‑m 192.0.2.0,192.0.2.1,192.0.2.3
On each server or virtual machine that is to be a system instance:
Run the script setup with the applicable options:
| Option | Description |
|---|---|
| -i | The external network IP address for the instance on which you're running the script. |
| -I | The internal network IP address for the instance on which you're running the script. |
| -m | Comma-separated list of external network IP addresses of each master instance. |
| -M | Comma-separated list of internal network IP addresses of each master instance. |
| -i IPADDRESS | Displays the external instance IP address. If not specified, this value is discovered automatically. |
| -I IPADDRESS | Displays the internal instance IP address. If not specified, this value is the same as the external IP address. |
| -d | Attempts to automatically discover the real master list from the provided masters. |
| –-hci_uid UID | Allows you to set the desired user ID (UID) for the HCI USER at install time only. Important: This value needs to be greater than 1000, less than or equal to 65533, and the same on all nodes in a cluster.
|
| --hci_gid GID | Allows you to set the desired group ID (GID) for the HCI GROUP at install time only. Important: This value needs to be greater than 1000, less than or equal to 65533, and the same on all nodes in a cluster.
|
| --mesos_uid UID | Allows you to set the desired user UID for the MESOS USER at install time only. Important: This value needs to be greater than 1000, less than or equal to 65533, and the same on all nodes in a cluster.
|
| --mesos_gid GID | Allows you to set the desired GID for the MESOS GROUP at install time only. Important: This value needs to be greater than 1000, less than or equal to 65533, and the same on all nodes in a cluster.
|
| --haproxy_uid UID | Allows you to set the desired UID for the HAPROXY USER at install time only. Important: This value needs to be greater than 1000, less than or equal to 65533, and the same on all nodes in a cluster.
|
| --haproxy_gid GID | Allows you to set the desired GID for the HAPROXY GROUP at install time only. Important: This value needs to be greater than 1000, less than or equal to 65533, and the same on all nodes in a cluster.
|
| --zk_uid UID | Allows you to set the desired UID for the ZOOKEEPER USER at install time only. Important: This value needs to be greater than 1000, less than or equal to 65533, and the same on all nodes in a cluster.
|
| --zk_gid GID | Allows you to set the desired GID for the ZOOKEEPER GROUP at install time only. Important: This value needs to be greater than 1000, less than or equal to 65533, and the same on all nodes in a cluster.
|
Use the following table to determine which options to use:
| Number of instances in the system | Network type usage | Options to use |
|---|---|---|
| Multiple | Single network type for all services | Either: -i and -m or -I and -M |
| Multiple | Internal for some services, external for others | All of these: -i, -I, -m, -M |
| Single | Single network type for all services | Either -i or -I |
| Single | Internal for some services, external for others | Both -i and -I |
Note: If the terminal displays Docker errors when you run the setup script, ensure that Docker is running.
The following example sets up a single-instance system that uses only one network type for all services:
sudo install_path/hci/bin/setup -i 192.0.2.4
To set up a multi-instance system that uses both internal and external networks, type the command in this format:
sudo install_path/hci/bin/setup ‑i external_instance_ip ‑I internal_instance_ip ‑m external_master_ips_list ‑M internal_master_ips_list
For example:
sudo install_path/hci/bin/setup ‑i 192.0.2.4 ‑I 10.236.1.0 ‑m 192.0.2.0,192.0.2.1,192.0.2.3 ‑M 10.236.1.1,10.236.1.2,10.236.1.3
The following table shows sample commands to create a four-instance system. Each command is entered on a different server or virtual machine that is to be a system instance. The resulting system contains three master instances and one worker instance and uses both internal and external networks.
| Instance internal IP | Instance external IP | Master or worker | Command |
|---|---|---|---|
| 192.0.2.1 | 10.236.1.1 | Master | sudo install_path/hci/bin/setup ‑I 192.0.2.1 ‑i 10.236.1.1 ‑M 192.0.2.1,192.0.2.2,192.0.2.3 ‑m 10.236.1.1,10.236.1.2,10.236.1.3 |
| 192.0.2.2 | 10.236.1.2 | Master | sudo install_path/hci/bin/setup ‑I 192.0.2.2 ‑i 10.236.1.2 ‑M 192.0.2.1,192.0.2.2,192.0.2.3 ‑m 10.236.1.1,10.236.1.2,10.236.1.3 |
| 192.0.2.3 | 10.236.1.3 | Master | sudo install_path/hci/bin/setup ‑I 192.0.2.3 ‑i 10.236.1.3 ‑M 192.0.2.1,192.0.2.2,192.0.2.3 ‑m 10.236.1.1,10.236.1.2,10.236.1.3 |
| 192.0.2.4 | 10.236.1.4 | Worker | sudo install_path/hci/bin/setup ‑I 192.0.2.4 ‑i 10.236.1.4 ‑M 192.0.2.1,192.0.2.2,192.0.2.3 ‑m 10.236.1.1,10.236.1.2,10.236.1.3 |