Cross-Service Network PaaS Side Configuration

Note: The Cross-Service Network feature is available starting with the Virtuozzo Application Management 8.6.2 version.

In order to set up a Cross-Service Network from the PaaS side, follow the next steps:

1. Go to the admin pane’s Regions section, select a region to add the cross-service network, and click the Edit button. In the opened wizard, tick the Attach Region to Cross-Service Network checkbox and provide the following data:

  • Dedicated Subnet – dedicated subnets for the region from the shared private cross-service network (e.g., 100.65.0.0/16)
  • Container Mask – global mask for containers (e.g., /15)

Attach Region to Cross Network

Save the changes.

2. You can switch to the IP Pool > Cross-Service IPv4 section to view all cross-service addresses in use for all users.

  • The Cross-Service IPv4 tab shows all IPs from the cross-service network.

Cross Network IP Pool

  • The Access Control tab manages access control lists from Virtuozzo Infrastructure to Application Management.

Cross Network IP Access Control

You can Add an access control rule to allow connection between the environments:

  • External IP Address – external IP from Virtuozzo Infrastructure (router)
  • Scope – isolation level (user account or environment group)
  • User – target user account

Add Cross Network Access

3. To allow end users to utilize the Cross-Service Network feature, you need to enable the dedicated cross.service.network.enabled quota.

Cross Network Quota

4. You can assign cross-service IPs to the environments via the dedicated Cross-Service Network API Methods. However, the first 50 IPs are reserved for internal services, so the allocation starts from the 51st. The assigned cross-service IPs are displayed alongside the regular ones in the end-user dashboard.

Dashboard Cross Network IP Address

Note: Environment migration is disabled for end users while cross-service IP is attached. To perform the migration, it should be disconnected from the wizard and reconnected after the migration process.

Also, when cross-service IP is connected to the environment, the user can refer to that container as usual by using the cross. prefix.

1
ping cross.cp.my_env.platform.domain

Note: Such approach (using the cross. prefix) only works from the external networks (e.g., Virtuozzo Infrastructure) and is not applicable for internal communication between containers within the same region.

What’s next?