Deployment Prerequisites

Operating System

Supported RHEL binary-compatible Linux distributions are given below.

7.x family: RHEL 7 or CentOS 7
8.x family: RHEL 8, CentOS 8, AlmaLinux 8, Rocky Linux 8, Oracle Linux 8
9.x family: RHEL 9, AlmaLinux 9, Rocky Linux 9, Oracle Linux 9

All virtual machines should have the same Linux distribution and version (e.g. all should be Oracle Linux 9 or AlmaLinux 9).

Partitioning

• Disk partitioning should ensure that a minimum of 95% of the required disk space is available on the / (root) partition.
• /opt and /var folders should not be on a separate partition.

Network

• All servers should be reachable from the Origin Server via SSH.
• All servers should have static IP addresses.
• Origin Server should be able to reach https://nexus.sestek.com and https://docker.sestek.com during installation.
• All communication should be allowed between the cluster nodes.
• VRRP packets should be allowed between servers.
• Network interface name of the servers should be given by the customer.

Credentials

Credentials provided by customers should follow the following practices:

Linux:

• Should have sudo privileges.
• Should be the same for all servers.

Windows:

• Should have local administrator privileges.

Load Balancer

• Customers should reserve a virtual IP for the load balancer. This IP should be reachable from the end user machines.
• Virtual IP should not be assigned to any server.

DNS

• A DNS name should be reserved for the base domain name (e.g. knovvu.mycompany.com).
• DNS name and all of its subdomains (e.g. *.xyz.knovvu.mycompany.com) should be assigned to the virtual IP of the load balancer.

Certificate

There are two options for the certificate:

1. Customer resolves the SSL via an external load balancer using customer certificates.

2. Customer wants Sestek to handle the SSL termination. In this case, again there are two options:

   1. Customer provides a certificate. In this case, Sestek will use the provided certificate.
   2. Customer doesn't provide a certificate. In this case, Sestek will generate a self-signed certificate. This certificate should be trusted by the end user machines.

SMTP

Alerting related emails should be able to be sent from the Origin server to two different email addresses using the SMTP protocol on port 25.

• devopsalerts@sestek.com (smtp.office365.com)
• {customer-name}@sestek.heartbeat.opsgenie.net

Other

• The date/time of all machines must be set correctly using UTC +0. This configuration must be ensured also if date/time is controlled by the hypervisor.

Information expected from the customer

• Base domain name

Customers should choose a base domain name that Sestek applications will use (e.g. knovvu.mycompany.com). Changing the domain address later in the deployment process requires additional actions, that might delay the installation process.

• Preferred database (Microsoft SQL Server or PostgreSQL). Version should be verified based on the product being deployed.
• Database server's IP, port, DNS (if exist) and credentials with dbowner privileges.
• Virtual IP address reserved for the load balancer
• Host names, IP addresses and credentials(username, password, etc.) of all the servers.