Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Installation Prerequisites

 

To successfully install and deploy a Paragon Automation cluster, you must have a dedicated machine that functions as the control host and installs the distribution software on a number of cluster nodes. You can download the distribution software on the control host, and then create and configure the installation files to run the installation from the control host. You must have internet access to download the packages on the control host. You must also have internet access on the cluster nodes to download any additional software such as Docker, and OS patches.

Before you download and install the distribution software, you must preconfigure the control host and the cluster nodes as described in this topic.

Prepare the Control Host

The control host is a dedicated machine that is used to orchestrate the installation and upgrade of a Paragon Automation cluster. You must download the installer packages on the control host. The control host runs the software installer that installs the software on the cluster nodes. The control host also installs any additional packages such as optional OS packages, Docker, and ElasticSearch on the cluster nodes. The control node requires internet access to download software. All microservices, including third-party microservices, are downloaded onto the control host, and do not access any public registries during installation. The control host can be on a different broadcast domain from the cluster nodes, but needs SSH access to the nodes.

Once installation or upgrade is complete, the control host plays no role in the functioning of the cluster. You can continue to use the control host to archive configuration files. You can also use the control host to re-install a cluster in case a cluster node fails or malfunctions.

Ensure that the control host meets the following prerequisites:

  • A base OS of any Linux distribution that allows installation of Docker CE must be installed.

  • Docker CE must be installed and configured on the control host to implement the Linux container environment. To download and install Docker CE, perform the following steps:

    • On Ubuntu OS:

      The following commands install the latest stable version on x86 machines.

      # sudo apt-get install -y apt-transport-https ca-certificates curl gnupg-agent software-properties-common
      # curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
      # sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
      # sudo apt-get update
      # sudo apt-get install -y docker-ce docker-ce-cli containerd.io


      To verify that Docker is installed and running:

      # docker run hello-world


      To verify the Docker version installed:

      # docker version

      or

      # docker --version

      For full instructions and more information, see https://docs.docker.com/engine/install/ubuntu/.

    • On CentOS:

      The following commands will install the latest stable version on x86 machines.

      $ sudo yum install -y yum-utils \
      device-mapper-persistent-data \
      lvm2
      $ sudo yum-config-manager \
      --add-repo \
      https://download.docker.com/linux/centos/docker-ce.repo
      $ sudo yum install docker-ce
      $ sudo systemctl start docker


      To verify that Docker is installed and running:

      $ docker run hello-world


      To verify the Docker version installed:

      $ docker version

      or

      $ docker --version

      For full instructions and more information, see https://docs.docker.com/engine/install/centos/.

  • The installer running on the control host must be connected to the cluster nodes through SSH using the install user account.

  • The wget package must be installed. Use the wget tool to download the Paragon Automation distribution software.

    • On Ubuntu OS:

      # apt install wget
    • On CentOS:

      $ yum install wget

Prepare Cluster Nodes

Paragon Automation is installed on a Kubernetes cluster of primary and worker nodes, which are collectively called cluster nodes. Ensure that the cluster nodes meet the following prerequisites:

  • A static IP address or hostname must be configured for each cluster node. We recommend that all the nodes be in the same broadcast domain.

    The cluster nodes need not be accessible from outside the cluster. Access to the Kubernetes cluster is managed by separate virtual IP addresses.

  • A base OS of CentOS 7 or Ubuntu 18.04 or later must be installed. To verify the installed OS version, use the lsb_release -a command.

  • The install user must be a root user or have superuser (sudo) privileges.

  • An SSH server must be running on all nodes. The installer running on the control host connects to the cluster nodes through SSH using the install user account.

  • Python must be installed on the cluster nodes:

    • On Ubuntu OS:

      To install Python 2.7.

      # apt install python2.7


      To verify the Python version installed.

      # python -V

      or

      # python --version
    • On CentOS:

      To install Python 2.7.

      $ yum install -y python2


      To verify the Python version installed.

      $ python -V

      or

      $ python --version

Virtual IP Address Considerations

Access to the Paragon Automation cluster from outside the cluster is through virtual IP addresses (VIPs) that are managed by a load balancer. You require up to five virtual IP addresses for a cluster. The VIPs can be within the same broadcast domain as the cluster nodes or in a different broadcast domain. You must identify these VIPs before you install Paragon Automation.

  • In case of a multi-primary node setup, you need at least one VIP in the same broadcast domain as the cluster nodes. This IP address is used for communication between the primary and worker nodes. This IP address is referred to as the Kubernetes Master Virtual IP address in the installation wizard.

  • You also need a VIP each for the following load-balanced services:

    • Ingress controller—Paragon Automation provides a common Web server that provides access for installing applications. Access to the server is managed through the Kubernetes Ingress Controller. This VIP is used for Web access of the Paragon Automation GUI.

    • Paragon Insights services—This VIP is used for DHCP services such as SNMP, syslog, and DHCP relay.

    • Paragon Pathfinder PCE server.

  • SNMP trap receiver proxy (Optional)—You should configure a VIP for the SNMP trap receiver proxy only if this functionality is required.

DNS Server Configuration (Optional)

You can access the main Web gateway either through the ingress controller VIP or through a hostname that is configured in the DNS that resolves to the ingress controller VIP. You should configure DNS only if you want to use a hostname to access the Web gateway.

Add the hostname to DNS as A, AAAA, or CNAME record. For lab and POC setups, you can add the hostname to the /etc/hosts file on the cluster nodes.