Table of Contents |
---|
...
Import the OVA file into your ESXi/vSphere environment. During the import process, add any network interfaces and configure as necessary.
Info title Private subnet To support a private subnet for Storage and Elasticsearch nodes, the Platform server needs both public and private network interfaces (like the dual-network CSN).
Important: With nodes on a private subnet, you must complete Deploying a Proxy to provide access to the health report server and other network resources, such as replication feed targets, NTP servers, and DNS. Without an interface into that private network, the Swarm UI cannot be accessed by an external browser.
Once the OVA is imported and booted for the first time, configure the networking as necessary within the OS. You can ssh into the Platform server using the following username/password:
caringoadmin/caringo
Once the networking configuration completes and validates, run the following command where
STORAGE_NIC_IP
is the static IP of the NIC connected to the storage network:Code Block language bash sudo /opt/reinit.sh -i STORAGE_NIC_IP
Info title Offline mode If the server cannot access the Internet, use Offline mode by adding the
-o
flag when runningreinit.sh
.Info title Important If you enter the wrong IP address in the above command, the bootstrap command will be caught waiting and not return. See "Bootstrap Command Hangs" in Platform Troubleshooting /wiki/spaces/KBI/pages/2443828226.
When the
reinit.sh
script has finished, reboot the Platform Server.
...
Info |
---|
RequiredThis process requires that you already have a running Ubuntu system with all the networking configuration done setup and working. For a private network for the Swarm storage cluster, verify two separate network interfaces exist on your Platform server: one for the private subnet and one for the publicly available subnet. |
SSH into the Platform server.
If the system is missing unzip capability, install it before proceeding:
Code Block sudo apt-get install unzip
Unzip the package into an empty non-temporary directory and change directories into it:
Code Block language bash unzip caringo-platform-VERSION.zip cd caringo-platform-VERSION
Run the self-extracting installation script as a user with root privileges. For the following commands, use the interface name (such as
ens192
) that you found in step 2 of the Installation Checklist, above.
For Run as follows for physical hardware or within a container, run as follows:Code Block language bash sudo ./installplatform.sh -i INTERFACE_NAME
For Add the
-e
flag for VMware ESXi virtual machines, add the-e
flag:Code Block language bash sudo ./installplatform.sh -i INTERFACE_NAME -e
Info title Offline mode If the server cannot access the Internet, use Offline mode by adding the
-o
flag when runninginstallplatform.sh
.For the complete command help, run the script without arguments:
./installplatform.sh
Code Block Usage: installplatform.sh [-v|b|e|s] -i INTERFACE Install the Caringo Platform server software. -h display help and exit -i the interface to manage for the storage network -v this server is a VMWare Desktop/Fusion VM -b this server is running in VirtualBox VM -e this server is running in ESXi -s this server is running on bare metal on in a container (default) -r install as rack server pointing to region controller -o offline installation
Once installation completes, the CLI binary is installed, and it can be run from anywhere.
Initialize the Platform Server
Unless you are installing in offline mode, verify that there is at least 300 MB space available to run the bootstrap command, which downloads updates from the Internet.
Once you have the interface name, you can list all of the available CIDR (Classless Inter-Domain Routing, or supernetting) network addresses:
Code Block language bash platform list subnets --all
Run the bootstrap command for the Swarm Platform environment, which includes preparing Swarm Storage for deployment to managed nodes.
Code Block language bash platform bootstrap -i PATH_TO_STORAGE_ZIP -v VERSION -t DHCP_SUBNET -a STARTING_IP_RANGE -z ENDING_IP_RANGE
Path — The Swarm Storage ZIP file for this command is located in the \Storage folder within the
Swarm-VERSION-DATE.zip
download. The filename has this form:storage-VERSION-x86_64.zip
. You may change the version of Swarm Storage at any point after the bootstrap completes.Version — Version of Swarm Storage, in the form
#.#.#
.DHCP Subnet — The DHCP subnet CIDR calculated above. The
platform list subnets
command provides the proper format:Example
Code Block language bash $ platform list subnets --all Subnet: 10.1.1.0/24 Subnet: 172.17.0.0/16 Subnet: 192.168.68.0/24
If the storage subnet is 192.168.68.x, then use 192.168.68.0/24
Dynamic Range — Use the dynamic range IPs you found in step 4 of the Installation Checklist, above.
Info title Caution The Dynamic Range specified in the bootstrap command must contain at least 10 IP addresses and also cover less than 25% of the total address space for the subnet. Taking up more than 25% of the addresses could result in too few IP addresses to boot Storage chassis. You can use a
--force
flag to force use of a range that violates these rules, but do so with caution.Info title Caution The DHCP range is necessarily contiguous based on the STARTING_IP_RANGE and ENDING_IP_RANGE. The IP ranges allocated for Storage nodes can be non-contiguous by reserving IPs with the "platform add iprange" command as shown below. Be careful not to define a DHCP range that includes your Platform server's Swarm-managed network interface.
Create a reserved IP range so the IP addresses cannot be allocated for Storage nodes if there are other IP addresses on the same network not managed by Swarm Platform:
Code Block language bash platform add iprange -a STARTING_IP_RESERVED -z ENDING_IP_RESERVED
...
5. Upload a valid license in order for Swarm to boot successfully before deploying Swarm.
...