Traffic Distributor Installation

Objective

This guide explains how to use Traffic Distributor Installation on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.

Before you begin

• Sign in with an account permitted to manage the relevant environment.
• Confirm the target environment, region and resources before saving changes.
• Create a backup or rollback plan before changing a production system.

Installation stepsTraffic Distributoris quite simple - which is specially added inMarketplaceYou can create it with just a few clicks and start working in just a few minutes. Excellent solution configurability So let's take a look at the installation steps below to learn about all the available functionality and hidden nuances.

More:The flow described is suitable for installation from scratch, for example if you want to route traffic for a new environment to deploy to a running application and load a production application. You can follow the guide.Inject Traffic Distributor into Running ProjectThis is possible.

1. Click the buttonMarketplaceat the top of the dashboard

2. Within the Apps Marketplace tab, go to the “Apps Marketplace” section.Dev & Admin Toolsto search for packagesTraffic Distributor(or search in the box at the top) and click the button.Install

3. In the first installation You will see a brief overview and key benefits of this solution.

Tips:Place a check mark on the Don't show this message again box to skip this page next time.

ClickOKto carry out

4. On the installation page, you can modify parameters to configure the Traffic Distributor topology and set the desired routing for the backends.

Specify the following information:

• Entrypoint- Shared Load Balancer or Public IP
• Balancers- Number of NGINX instances to be added to the Traffic Distributor topology.
• Routing Method- SelectThere are three types of traffic distribution.: Round Robin, Sticky Sessions and Failover
• Traffic Ratio- Set the weight of the backend (by priority) to control the distribution of requests -request
• HTTPS- Enable this option if the backends serve traffic over HTTPS.
• Backends- Choose 2 environments to balance each other. Either from a list automatically retrieved from the available environments from your account or type in the IP address or domain name of your choice. (for custom hosts)

Note:Ruk-Com Cloud cannot identifyendpointURLs are the backends for distributing traffic because they are assumed to function through external public ports, while interactions within the confines of a single platform are built using private ports.

In this case you need to manually configure port redirection for your backends by switching to the "Redirection" section.Upstreamof files/etc/nginx/nginx-jelastic.confWithin the server's load balancer Traffic Distributor environment



You must add the required local container port numbers to the appropriate backend IP addresses. Additionally, define parameters to monitor health.

• Environment- The domain name for your environment (e.g.traffic-distributor)
• Display Name- (Not required)aliasto be displayed for the environment (Traffic Distributor by default)
• Region- Dropdown list ofenvironment regionsexisting
  
  

When all the necessary information is specified, click the button.InstallThe platform will do everything automatically.

5. After 2-3 minutes you will see a successful installation window with instructions on using Traffic Distributor.

Note:Since the Traffic Distributor load depends only on the number of incoming requests, it does not require a lot of resources. Therefore, the default value of 1 cloudlet can be scaled vertically (up to 16 cloudlets) to handle large numbers of concurrent requests.

Click on the following link to learn more:

• UsageBlue-Green Deploy
• UsageFailover Protection
• doingA/B Testing
• DistributionGo in and run the project.
• TheBind domaincustomized
• ActivationCustom SSL

Defining a new traffic distributor

After installing Traffic Distributor, you will receive an environment that comes with NGINX load balancer(s) and special add-ons attached to ensure quick and easy reconfiguration of this solution and provide additional accessibility options:

1. Hover over the NGINX instance in your Traffic Distributor environment and click the Add-On button to open the relevant tab.

2. To change the settings for the add-on, click the button.ConfigureOr click on the option from the top right corner menu.

Tips:Reload configuration option Manual configuration of the Traffic Distributor configuration file is required. without restarting the node (i.e. no downtime)

3. You can configure new values on this page. You can configure new Traffic Distributor options as during the installation process:

Available options for configuration:

• Entrypoint- Shared Load Balancer or Public IP
• Balancers- Number of NGINX instances to be added to the Traffic Distributor topology.
• Routing Method- SelectThere are three types of traffic distribution.: Round Robin, Sticky Sessions and Failover
• Traffic Ratio- Set the weight of the backend (by priority) to control the distribution of requests -request
• HTTPS- Enable this option if the backends serve traffic over HTTPS.
• Backends- Choose 2 environments to balance each other. Either from a list automatically retrieved from the available environments from your account or type in the IP address or domain name of your choice. (for custom hosts)

Tips:Using the buttonSwap backends weightsSee in the image above you can quickly exchange server throughput ratio values.

Confirm changes by clicking the button.Apply

4. Wait a moment, you will see a notification that the configuration was successfully saved in the top right corner of the dashboard.

Here you can click the button.Show Logsto open a specific file

5. On the pagetraffic-distributorlog You can find information about the execution time used for the add-on and the current traffic distribution values:

You can access this log file manually at any time.

Therefore, you can make changes to Traffic Distributor and track them through logging easily by following the steps described.