Home /Modules/server-edition/README.md

README.md

server-edition/participation/README.md · 51 line(s) · markdown

<img align="right" src="https://github.com/mearvk/SLeeLa/blob/master/images/debian/debian-logo.png" width="75" height="75" alt="SLeeLa">

<img src="https://github.com/mearvk/SLeeLa/blob/master/images/sleela/sleela-logo-004.jpg" alt="SLeeLa">

SLeeLa Server Participation

Each SLeeLa Server Edition may participate in a fast regroup round one or a few times per day.

Behavior

  1. Read the explicitly configured known SLeeLa servers from known-servers.conf.
  2. Send a small SLEELA-MESH/1 HELLO message to all configured peers concurrently.
  3. Wait for each configured peer's bounded response window.
  4. Record response/no-response status without retaining peer IP addresses in the participation record.
  5. Regroup after the round and continue normal server operation.
  6. Repeat according to SLEELA_MESH_INTERVAL_SECONDS; the default is every 8 hours (three rounds per day).

The participation layer is bounded and explicit. It does not discover or scan arbitrary Internet addresses. A peer must be placed in the known-server configuration before it is contacted.

Transport

The default participation port is TCP 22221. This is separate from:

The participation layer does not change the existing SLeeLa logical HTTP port namespace.

Message and regroup

The initial message contains only protocol/version, configured node identifier, UTC time, and participation port. Responses are bounded to the configured timeout.

This is a coordination mechanism, not an authority mechanism. A participation response does not by itself establish legal, governmental, diplomatic, financial, identity, or safety authority.

Configuration

Environment variables:

round performs one immediate round. start runs repeated rounds. stop stops the participation daemon.