Skip to main content

Cluster creation

  1. Connect to the Cockpit GUI by using the IP address previously configured (192.168.10.10, by default). Make sure that your browser language is set to English.

  2. Open a Web browser and type « https://<IP_address>:9090/ ». You are prompted to give a login and password in the window that displays on your screen.

    Login screen

  3. Insert the following values:

    • Login as support/support.
    • Tick the "Reuse my password for privileged tasks" checkbox to execute administration commands.
    • Click Log in.

  4. On your first Login as support, you are prompted to change the default support password.

    Change it and once it is done, log out then log in again to consider the new password for further actions.

    Note

    For High Availability (HA) deployment, you must connect to the Cockpit GUI of each server to change the support password. This must be done before starting any deployment.

  5. Go to "TPE Services" menu, the following wizard will be displayed:

    Wizard

  6. Before proceeding with the installation, please be sure to have a valid license number. If you do not, the next steps will not be complete. Indeed, when asking for a license, access to the ThingPark Enterprise Installation Repository for your installation ID will be granted.

    Note

    This is required only for online installation mode.

  7. Starting TPE 6.0, the TPE cluster can be configured in Standalone or High Availability (HA) mode. Select either "Standalone" or "Highly available" following the Cluster type you want to deploy, then click on Next.

  8. Following the mode selected previously:

    • For Standalone mode: fill in the "IP address" and the "support" password of the only node that will be installed.

      Standalone configuration

    • For HA mode: fill in the "IP address" and the "support" password of the three nodes.

    HA nodes configuration

    Click on Next.

  9. Set the following fields:

    • List of NTP servers: List of hostnames or IP addresses (comma-separated values) for NTP servers.

      WARNING

      For High Availability deployment, each TPE node must be synchronized with NTP servers. Please be sure to configure at least one functional NTP server.

    • Level 3 remote access server: ssh remote server location for level 3 access ([user@]host[:port][/path]).

    • Installation repository: URL of the installation repository:

      • Leave as is if you are going to install TPE by using Actility's remote repository.
      • Or put the local repository URL if you are going to install TPE by using the local media, see Local repository installation on how to install/start the local repository and get the local repository URL.

    • Installation proxy URL: URL of the proxy server used for installation repository access, only HTTP is supported (optional).

    • Internal Subnet: By default, the subnet that the TPE platform will use internally for containers networking is 192.168.0.0/20. You can change it if needed by setting a different /20 IPV4 block. If the internal subnet is customized, the IPsec subnets may also be customized accordingly just after the cluster creation in the TPE configuration screen.

      info

      For gateways configured to use IPsec, the addresses of LRC0, LRC1, FTP0 and FTP1 must be customized by the user. The IPs to set for are:

      • LRC0: 140th address of the subnet
      • LRC1: 2nd address of the subnet (for a HA deployment)
      • FTP0: 142nd of the subnet
      • FTP1: 3rd address of the subnet (for a HA deployment)

      For instance, if you choose the subnet 10.5.16.0/20, IPs to configure on the gateways are:

      • LRC0: 10.5.16.140
      • LRC1: 10.5.16.21 (for a HA deployment)
      • FTP0: 10.5.16.142
      • FTP1: 10.5.16.32 (for a HA deployment)

      The IPs that match your deployment are displayed after the TPE instance deployment on cockpit (TPE Services -> TPE Cluster operations -> Show infra configuration))

    • Source addresses allowed to access the system monitoring SNMP (optional): An SNMP client is required to poll metrics describing nodes' system statistics. Refer to the ThingPark Enterprise Administration and Troubleshooting Guide for more information on SNMP system monitoring.

      Configuration screen

  10. Click on Next.

  11. The next step is cluster verification:

    • Ensure the node(s) connectivity.
    • Ensure the node(s) requirements.

  12. If no error is detected, click on Deploy. The Cluster creation progress is displayed:

    Cluster creation

    At this stage, TPE docker images are downloaded from the installation repository. This can take between thirty minutes and an hour (or even more), depending on network throughput.

  13. At the end of the cluster creation, if successful, you are prompted to go to "TPE Configuration".

  14. Click on Configure ThingPark Enterprise.

Copyright © 2023 Actility