Infrastructure Controller (ic)
Description
Manages infrastructure changes within the site, distributes and synchronizes configurations, and supports the system update process within the site. Receives the configuration from mic and passes it to servers within the site. Synchronizes dynamic configuration with other sites: server availability states. Provides site statistics data.
Made redundant in Active-Passive mode on each site. Not scaled.
If the role is unavailable, the system within the site continues to operate normally, except for the ability to apply a new configuration to the site, update it, or synchronize server states with other sites. The system may split into several zones, each continuing to perform its functions independently.
Code |
|
Operation mode |
|
Redundancy mode |
|
Site types |
|
Layer |
|
Placement |
|
State preservation and recovery on restart |
|
Application |
|
Limitations
-
Must be located on every site.
-
Cannot be moved to another server in 1 step by changing the configuration.
Parameters
| Name | Type | Default | Description |
|---|---|---|---|
|
|
required |
Name. May consist of Latin letters and digits and must start with a letter. |
|
|
required |
Role type. Possible values: |
|
|
empty |
Additional role options. Contains a JSON object or list. |
|
|
empty |
Role activity flag. When set to false, the role does not participate in validation and is not started. |
|
|
empty |
Limit on the number of CPU logical cores used. Default: 0 - unlimited. |
|
|
empty |
Default logging level set specifically for the role instance (microservice type). More |
|
|
|
Flag allowing parameter differences in roles of the same group. Default: false - not allowed. |
|
|
empty |
Group number. |
|
|
required |
Order of the role instance within the group. |
|
|
|
Site statistics refresh interval in seconds. |
|
|
global |
Takeover mode switch.
|
Configuration example
Configuration management is performed in an application available to master domain administrators. The application hides the full configuration content, but it is still available through the API.
The configuration contains a section describing all instances of all roles. Parameters are defined for each specific role instance.
{
"name": "ic2",
"roletype": "ic",
"group": "11130",
"order": "1",
"refreshinterval": "60"
}