RPC Inner (rpci)

Table of Contents

Description
Limitations
Parameters
Configuration example
See also

Description

Service role that provides registration of active role instances reserved in the mode Active-Passive. Each node within the system has an rpci client to make such requests. The configuration configures rpci server roles for each site. The rpci service provides the output of microservice addresses within a site.

Reserved in Active-Active mode, but preferentially applies the first available instance.

Table 1. System Characteristics

Code	`rpci`
Mode of operation	`Service, storage`
Backup mode	`Active-Active`
Types of sites	`All of them`
Layer	`Configuration`
Placement	`Internal`
Saving and restoring state on reboot	`Yes`
appendix	`era_rpci`
Own storage	`RAM-table`

Limitations

Present in the initial configuration.
Must be present at all sites.

Parameters

Description of columns in the table

Table 2. Parameters
Name	Type	Default	Description
`name`	`str`	required	Name. May consist of Latin letters and numbers, must begin with a letter.
`roletype`	`str`	required	Role Type. Possible values: `"rpci"`.
`iface`	`str`	required	The alias of the server network interface on which the roles will interact internally with each other.
`ext`	`json`	empty	Additional role options. Contains a json object or list.
`enabled`	`bool`	empty	Role activity flag. When set to false, the role does not participate in validation and is not started.

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.

Example node

{
  "name": "rpci1",
  "roletype": "rpci",
  "iface": "eth0"
}

RPC Inner (rpci)

Description

Limitations

Parameters

Configuration example

See also