RPC Outer (rpco)
Description
A service role that enables server-to-server communication between sites without a direct connection of type full-mesh. It also solves the problem of lack of direct visibility of address spaces by each other’s sites. Each node within the system has an rpco client to make such requests. Roles-servers are configured in the configuration rpco.
Reserved in Active-Active mode, but preferentially applies the first available instance.
Code |
|
Mode of operation |
|
Backup mode |
|
Types of sites |
|
Layer |
|
Placement |
|
Saving and restoring state on reboot |
|
appendix |
|
Limitations
-
Present in the initial configuration.
-
Must be present at all sites.
-
Must reside on those site servers that have access to subnets that address role instances on other sites, otherwise it is not possible for sites to interact and have one multiple domain distributed service on them.
-
If the rpco role addresses of another site cannot be reached directly, an attempt is made to reach through instances in the master site.
Parameters
Configuration example
The configuration is managed in an application available to master domain administrators. The application hides the full content of the configuration, but it is nevertheless accessible via the API.
The configuration contains a section to describe all instances of all roles. Parameters are defined for each specific role instance.
{
"name": "rpco1",
"roletype": "rpco",
"iface": "eth0"
}