Regions

Hardware Regions

Open Regions from the Cluster section of the admin panel to review the platform’s hardware structure.

  • Regions (hardware regions) are independent hardware sets located in different data centers. A region may contain several host groups.
  • Host Groups (environment regions) are separate server sets inside a particular region, with their own options, performance characteristics, and resource-charging rules.
!

Note: Hardware regions are not displayed to end users. The user dashboard works with host groups, and each host group’s availability can be configured separately.

PaaS hardware regions
Hardware regions and host groups in the Regions section.

The Regions table displays the following key information:

  • Name of the hardware region or included host group.
  • Domain assigned to the region.
  • SSL certificate configuration for the hardware region.
  • Subnet allocated to the region.
  • Migration availability for moving user environments to or from the region.
  • Status of the region or host group: ACTIVE or MAINTENANCE.
  • Comment containing optional region or host-group information.
  • Docker Host address of the hardware region.
✓

Tip: Before configuring multiple regions, review the documentation for Regions List Management and Multi-Region Configurations.

The tools above the regions list can be used to:

  • Add a new region.
  • Add a new host group.
  • Edit a region or host group.
  • Remove an unnecessary region or host group.

Selecting a region also opens its detailed information and domain-name management options.

Add New Region

Follow these steps to add a new hardware region to the PaaS cluster.

!

Before adding a region, confirm the following prerequisites:

  • The hosts meet the applicable hardware requirements.
  • At least two internal and two external IP addresses are reserved for shared load balancers (resolvers).
  • The new region domain is delegated to those IP addresses according to the DNS zone delegation requirements.
  • The firewall is checked and configured where necessary.
  • The internal and external interfaces on each server are isolated from each other, either through separate physical switches or separate VLANs.
  • All internal interfaces in the region use the same data-center network segment, and all external interfaces use another common segment without interconnection between them.
1

Click Add Region in the toolbar at the top of the Regions section.

Add Region button
Open the Add Region dialog from the Regions toolbar.

Complete the required information in the opened Add Region frame.

2

In the Region Setting section, specify the region details.

Unique NameEnter a unique region identifier. This value cannot be changed later.
Display NameEnter the editable region alias displayed in JCA. The maximum length is 10 characters.
DomainSpecify the hostname assigned to the new region.
StatusSet the initial state to MAINTENANCE to prevent false monitoring alerts while the region is being added.
SubnetDefine the dedicated internal subnet used by user nodes and for traffic routing between hardware regions.
Start and End IPSpecify the container IP-address range for the region. The range must remain within the selected subnet.
CommentAdd optional short information about the hardware region for display in the admin panel.
Allow migration from/to regionsEnable this option to allow end users to migrate environments to and from the region.
i

Domain requirement

The required domain name must be purchased in advance from a preferred domain registrar.

i

Migration setting

This option controls migration between different hardware regions. Transfers between host groups belonging to the same hardware region cannot be disabled through this setting.

3

In the Name Servers section, provide one or more pairs of Public IPv4 and Internal IPv4 addresses.

These addresses are used by shared load balancers as the region entry point and also operate as the internal and external DNS servers.

4

Use the Docker Host Settings section to configure a separate Docker Engine module for the hardware region.

HostEnter the domain name or IP address of the Docker Host.
SSH and TCP PortSpecify the connection ports for the corresponding protocols.
Login and PasswordProvide the access credentials for the Docker Host.

After all settings are specified, click Add to create the region.

Add New Host Group

Use the following procedure to add a new host group.

1

Click Add Host Group at the top of the Regions panel.

2

In the Add Host Group dialog, complete the fields on the required Basic Data tab.

Unique NameUnique host-group identifier that cannot be modified later.
Display NameEditable host-group name shown in the admin panel and the end-user dashboard. Maximum length: 10 characters.
StatusInitial host-group status after creation: ACTIVE or MAINTENANCE.
CommentOptional short host-group information displayed in the admin panel.
RegionThe hardware region to which the host group will belong. Select an existing region or open the Add Region dialog.
Virtual Network Group (VNG)A value used to group virtual networks. Host groups using the same VNG receive the same configurations.

For example, when infrastructure containers and user applications are placed in two regions located in the same physical data center, assigning the same Virtual Network Group (VNG) value to every host group causes the virtual-network configurations to be generated as though the host groups belong to one region.

Add host group basic data
Basic Data settings for a new host group.

Additional information can be supplied on the optional Advanced Settings tab.

Datacenter

  • Country – select the data center country.
  • City – enter the data center city.
  • Geo Coordinates – provide latitude and longitude in WGS84 decimal-degree format.
  • Vendor – enter the data center vendor name.

Dashboard Settings

  • Icon 16×16 – enter a URL or use Browse to select an image from the platform resources folder. When no icon is supplied, the selected country’s flag is used.
  • Short Description – provide a single-line description.
  • Description (Markdown) – add a detailed host-group description.
✓

Tip: These descriptions are displayed in the dashboard when the localization files do not contain dedicated host-group records.

Add host group advanced settings
Advanced Settings for the new host group.

Click Add to continue.

3

Configure internal routing between regions according to the linked procedure. Skip this step when routing is already configured.

4

Add a host to the newly created host group.

4.1. Check /etc/vz/vz.conf

When VE_ROUTE_SRC_DEV is commented out or references the wrong device, correct the parameter and save the file. It must specify the server’s internal-network interface.

4.2. Update /etc/yum.conf when required

When DOCKER_HOST is located on the Docker Engine host and a Virtuozzo 7 host is being deployed, add the following line:

echo 'exclude=docker-ce' >> /etc/yum.conf

4.3. Check routes

Verify routes from the new region to infrastructure and user hosts in the same and other regions. The BIRD daemon may configure these routes automatically.

4.4. Start host installation

Start the host installation through JCA.

5

Configure shared load balancers (SLB).

5.1. Add the region network

Add the region network to the jelastic.net.subnetworks system setting in JCA.

5.2. Add SLB IP addresses

Add the external and internal SLB addresses to jelastic.isolation.infra.ips and jelastic.isolation.infra.ips.all. When platform isolation is enabled, disable and enable it again so the new values are applied.

5.3. Open the system environment

Find the jelastic system environment in the admin panel and sign in to the dashboard as its owner, usually UID 2.

System environment
The jelastic system environment in the admin panel.
Sign in as system user
Sign in as the system-environment owner.

5.4. Install Create Resolver

Click Marketplace, open the System section, and install the Create Resolver package.

Create Resolver package
Create Resolver package in the System Marketplace section.

5.5. Configure Create Resolver

Progress fileuse continues from the failed step and skips completed steps; ignore clears the saved progress and starts again from the first step.
Docker RegistrySelect the production registry, which is recommended, or the development registry.
Name indexSpecify the next shared-load-balancer index.
CTIDProvide an unused Virtuozzo container ID for the shared load balancer.
External IPProvide a public SLB address outside IP Pool > Public IPv4.
Internal IPProvide an internal SLB address outside the region’s User Containers IP Range.
VersionVerify the automatically detected Virtuozzo Application Management version.
HardnodeSelect the destination host.
Add monitoringEnable this recommended option to register the SLB with platform monitoring.
  • 3xx – default region CTIDs.
  • 401, 402, etc. – second-region CTIDs.
  • 501, 502, etc. – third-region CTIDs, with the pattern continuing for later regions.

IP setup example:

  • Network: 10.100.0.0/16
  • User Containers IP Range: 10.100.2.1 – 10.100.255.254
  • Range used by region’s hosts: 10.100.0.1 – 10.100.0.254
  • Range available for SLBs and other infrastructure components: 10.100.1.1 – 10.100.1.254

Infrastructure CTIDs can be reviewed in the topology of the jelastic system environment.

Create Resolver dialog
Create Resolver configuration fields.

Click Install. The platform applies the required configuration automatically. Wait until the success notification confirms that the new shared load balancer has been created.

6

Provide Let’s Encrypt SSL certificates through JCA.

7

Apply customizations and run J-Runner tests for the new region when required.

8

Assign the host group to the appropriate user groups through the Regions & Pricing tab.

Host groups availability
Host-group availability for user groups.

The host group then appears in the Dev dashboard topology wizard as a new environment region.