Docs menu
MENU

Technical Configuration

SMTP Configuration

The platform requires a properly configured SMTP (Simple Mail Transfer Protocol) server to notify users about various platform events and provide additional information (registration, environment creation, database credentials, etc.).

1. To configure the SMTP server for the platform, go to the admin panel and open the System Settings section.

2. Search for the smtp settings and adjust the following parameters (i.e. ones related to the main SMTP server):

  • smtp.mail.host - domain name or IP of the main SMTP server
  • smtp.mail.port - a port to access the main SMTP server
  • smtp.mail.user - a username to authenticate on the main SMTP server
  • smtp.mail.password - a password to authenticate on the main SMTP server
  • smtp.mail.ssl - a secure protocol for notifications sent via the main SMTP server
    • NONE - to apply no additional security protocol
    • STARTTLS - to access the main SMTP server without encryption and initialize a secured connection after the starttls command
    • SSMTP - to access the main SMTP server over a secure SMTP (SSL) connection
  • smtp.mail.from - a sender email address for the system notifications that are sent via the main SMTP server
  • smtp.mail.type - the type of email messages for the main SMTP server
    • NULL - to forbid all notifications
    • SIMPLE - to use plaintext messages
    • MULTIPART - to provide multipart MIME messages

SMTP settings

3. Next, enable Expert Mode in the top-right corner to see more settings. Find and set the smtp.mail.relay.available parameter as true.

SMTP relay setting

4. Do not forget to Apply the performed changes.

apply settings

That’s the minimum requirement. Additionally, you can configure the backup SMTP server and SMTP relay. Learn more at the dedicated SMTP Configuration guide.

External IPs Range Configuration

You can add a range of external IP addresses (both IPv4 and IPv6) that can be used by end-user environments. The provided range should be reserved for the PaaS in the VHI cluster and routed to the appropriate hosts.

IPv4

1. Open the IP Pool > Public IPv4 section of the admin panel and click the Add IP Range button at the toolbar.

public IPv4 panel

2. In the opened Add IP Range dialog frame, type the Start and End IP and tick the required hardware Regions from the list.

add IPv4 range

Click Add to make the specified addresses available for the selected regions.

IPv6

1. Before adding a new IPv6 address set, it should be preliminarily routed to the appropriate hosts.

Adjust the following configuration files (you can access them via SSH or VHI console):

  • /etc/sysconfig/network
1
2
3
4
5

NETWORKING_IPV6=yes
IPV6FORWARDING=yes
IPV6_DEFAULTDEV=eth0
IPV6_DEFAULTGW=aaaa:bbbb:a01a::1
IPV6_AUTOCONF=no
  • /etc/sysconfig/network-scripts/ifcfg-ethX (where X is your interface number)
1
2

IPV6INIT=yes
IPV6ADDR=aaaa:bbbb:cccc:0000:0100::1/ddd
  • /etc/sysctl.conf
1
2
3

net.ipv6.conf.default.forwarding = 1
net.ipv6.conf.all.forwarding = 1
net.ipv6.conf.all.proxy_ndp = 1

2. Go to the admin panel’s IP Pool > Public IPv6 > Networks section. Click the Add button in the tools panel.

public IPv6 panel

3. In the opened Add IPv6 Network frame, type your Network with the appropriate prefix being specified after the “/” character (e.g. 0000:0000:0000:0000:0000:0000:0000:0000/80). Next, tick the required hardware Regions within the list below (for these addresses to be available).

add IPv6 network

Click Add to confirm the creation of the specified network.

4. Next, you should configure the IPv6 subnet (i.e. the number of addresses provided to the user per environment). Navigate to the System Settings (Expert Mode) section and search for the jelastic.ip.v6.subnet.prefix setting, which is used to slice the whole network into subnets for environments.

IPv6 subnet setting

For example, the prefix 118 means the last 10 bits of the IPv6 address (i.e. a total of 128 bits minus the specified 118) will be used for the subnet, which is equal to 210 = 1024 addresses.

public IPv6 subnets

Edit the value and Apply changes to set the required IPv6 subnet prefix.

A Docker Hub account with an extended number of pulls is required to ensure that end-users won’t be restricted by the download rate limit (i.e. based on the number of containers created on the platform).

1. Get a Docker Hub billing account. Any paid plan gives up to 5000 pulls per day, which should be suitable for most cases.

Tip: If needed, this number can be increased later with the Enhanced Service Account add-on.

2. Go to the Templates > Docker Registries tab in the admin panel and click Add on the tools panel.

docker registries panel

3. Within the Add Registry window, provide the following data:

  • Name – type any custom name
  • URL/IP - leave blank to work with the Docker Hub registry
  • Credentials – tick the checkbox and specify Login and Password of the account created in the first step

add docker registry

Click Add to save the registry data.

4. Next, select the record in the list and set it as default using the appropriate button in the tools panel.

set default docker registry

Uploader Access Configuration

The Uploader component is responsible for uploading user application archives and placing them within Uploader Storage.

1. Configure shared storage for Uploader.

We recommend having the Uploader Storage as a separate component mounted to the external NFS Share to avoid any tampering with uploaded files and packages.

2. Add the following line to the /etc/fstab file in the Uploader container:

1

IP_storage:/vz/uploader /home/hivext/uploader_data nfs defaults,_netdev,timeo=120,retrans=3,soft,nolock 0 0

3. Use the command below to mount the Uploader storage:

1

mount /home/hivext/uploader_data

4. Set the correct rights to the data in the storage:

1

chown -r tomcat:tomcat /home/hivext/uploader_data

5. Restart the tomcat service to ensure the changes are applied.

1

service restart tomcat

6. Verify the Uploader’s correct functionality by logging in to the user dashboard and trying uploading/downloading files via Deployment and File Managers.

Monitoring Configuration

Zabbix Monitoring Solution is an optional component that tracks the main parameters of the platform infrastructure and cluster components such as user/infra hosts and containers. Other services (e.g. backup servers) can be included in the monitoring system on demand.

Zabbix also provides monitoring of numerous network parameters, server health, and integrity. In addition, Zabbix uses a flexible notification mechanism for events. It allows cluster admins to configure preferred delivery methods (email, SMS, Jabber, or custom scripts), which ensures the fastest reaction to platform-related issues.

You can choose to add Zabbix server automatically during the platform installation with the corresponding toggle within the web installer.

add Zabbix monitoring

In this case, you can access the monitoring right after the installation by following the link:

https://zabbix.{platformDomain}

Alternatively, you can set up your own monitoring server manually. Refer to the documentation for some guidance:

Backuper Configuration

Platform Backuper is an additional platform infrastructure component that controls the backup processes on hosts.

After the PaaS deployment, you need to configure the pre-installed Backuper container for it to work correctly. Follow the steps in the linked guide or, if needed, contact your TAM/onboard manager for additional configurations.

What’s next?