Master Infrastructure Controller (mic)

Description

Manages changes to the entire system infrastructure, manages the distribution and synchronization of configurations and the upgrade process.

Reserved in Active-Passive mode. Not scalable.

If the role is unavailable, the system continues to function properly, eliminating the ability to change the configuration and upgrade the system. The zone from which the master site is inaccessible remains without configuration changes or updates until it is connected. The system can be broken up into several zones, each of which continues to perform its functions separately.

Table 1. System Characteristics

Code

mic

Mode of operation

Service

Backup mode

Active-Passive

Types of sites

Master

Layer

Configuration

Placement

Internal

Saving and restoring state on reboot

No

appendix

era_mc

Limitations

  • Present in the initial configuration.

  • May be located on the master site only.

  • Not available to move to another server in 1 step by changing the configuration.

Parameters

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: "mic".

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.

group

int

required

Group Number.
Horizontal scaling within a site is not supported. All role instances on the site must have the same value.
Integer from 1 to 9999999.

order

int

required

The order of a role instance within a group.
Defines in what order the flow in the mode will take place Active-Passive.

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": "mic1",
  "roletype": "mic",
  "iface": "eth0",

  "group": 11140,
  "order": 1
}

See also