Selector Conference Controller (sel)

Description

Provides management of selector meetings.
Is an add-on to the conf role, giving it responsibility for the communication layer.

Does not synchronize data between sites serving the domain.
Reserved Active-Passive mode within the site.

Table 1. System Characteristics

Code

sel

Mode of operation

Service, storage

Backup mode

Active-Passive

Types of sites

Any

Layer

Business logic

Placement

Internal

Saving and restoring state on reboot

Yes

appendix

era_sel

Own storage

ODB Mnesia

Limitations

  • Does not synchronize data between sites serving the domain.

  • Stores data on scheduled, active, and past selector meetings in an internal object store without storing it in the domain relational database.

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

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.
As part of horizontal scaling, a role can be divided into multiple groups on a site, with only one instance active in each group and the rest reserved.
Responsibilities between groups are shared across domain sets. Together, all groups maintain a complete domain set. All roles in the same group must have the same responsibility.
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": "sel1",
  "roletype": "sel",
  "iface": "eth0",

  "group": 11060,
  "order": 10
}

See also