File Server (fs)

Description

A service role used for redundant long-term storage of files on the system’s servers. Can be configured as an attachment store for collections in a dynamic data model (DMS).

Each file is hosted simultaneously on all servers in the site where the role is active.

Table 1. System Characteristics

Code

fs

Mode of operation

Service

Backup mode

Active-Active

Types of sites

All of them

Layer

Configuration

Placement

Internal

Saving and restoring state on reboot

Yes

appendix

era_fs

Limitations

  • Does not perform delayed periodic synchronization. (TODO)

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

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.

roleid

int

required

Role ID.
Unique for the entire system, regardless of the site or server. Cannot be changed.
Integer from 1 to 9999.

separate

bool

required

An indication that the role has been allocated to a separate node.

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
{
  "iface": "eth0",
  "name": "fs1",
  "roleid": 11350,
  "roletype": "fs",
  "separate": true
}

See also