Svc-swarm-manager Role¶

Description: Marker role tagging a host as the Docker Swarm manager node, with the init logic delegated to svc-swarm-node

Variables¶

author: Kevin Veen-Birkenbach
description: Marker role tagging a host as the Docker Swarm manager node, with the init logic delegated to svc-swarm-node
license: Infinito.Nexus Community License (Non-Commercial)
company: Kevin Veen-Birkenbach https://www.veen.world
galaxy_tags: [‘swarm’, ‘docker’, ‘cluster’]
issue_tracker_url: https://s.infinito.nexus/issues
min_ansible_version: 2.9
platforms: [{‘name’: ‘ArchLinux’, ‘versions’: [‘all’]}, {‘name’: ‘Debian’, ‘versions’: [‘all’]}, {‘name’: ‘EL’, ‘versions’: [‘all’]}, {‘name’: ‘Fedora’, ‘versions’: [‘all’]}, {‘name’: ‘Ubuntu’, ‘versions’: [‘all’]}]

README¶

Docker Swarm Manager¶

Description¶

Docker Swarm groups Docker hosts into a single virtual host. A swarm has exactly one manager node in v1; managers run the Raft store and accept service-API calls.

Overview¶

This role is a group-name tag. It exists so the project’s inventory validator accepts svc-swarm-manager as a legitimate application_id. The actual swarm-init logic lives in svc-swarm-node and dispatches on 'svc-swarm-manager' in group_names.

Cosmos¶

The diagram places Docker Swarm Manager in the Infinito.Nexus cosmos: the components it deploys (capabilities), the central services it consumes (dependencies), and its outward reach (federation and bridged external networks).

flowchart LR
    subgraph deps [Dependencies]
        dep_svc_swarm_node["svc-swarm-node 💻"]
    end
    subgraph role [svc-swarm-manager 💻]
        svc_node["node"]
        svc_manager["manager"]
    end
    dep_svc_swarm_node -. "0..1" .-> svc_node

Solid 1:1 edges are fixed relationships; dashed 0..1 edges are conditional (enabled only in matching deployments); red 0..0 edges are turned off in this role. Node markers show the role’s deploy modes (💻 host, 🐳 compose, 🐝 swarm); ❌ marks a service that is explicitly turned off, and ⚙️ an Ansible role dependency declared in meta/main.yml.

Features¶

Marker role: Carries no tasks; selects which svc-swarm-node member runs the manager-init flow.

Quick Setup¶

Development¶

Clone, set up the workstation, and deploy Docker Swarm Manager onto the local stack:

git clone https://github.com/infinito-nexus/core.git
cd core
make onboard
make compose-deploy mode=reinstall apps=svc-swarm-manager full_cycle=false

Production¶

Install Docker Swarm Manager directly onto the target machine: clone the repository, install the OS prerequisites and the repository toolchain, then deploy against localhost over a local connection (no SSH, no container):

git clone https://github.com/infinito-nexus/core.git
cd core
bash scripts/install/package.sh
make install
source scripts/meta/env/load.sh

APP=svc-swarm-manager
DOMAIN=<your-domain>
TLS_MODE=self_signed
SSH_PUBLIC_KEY="<your-ssh-public-key>"
INVENTORY=inventories/production
infinito administration inventory provision "$INVENTORY" \
  --inventory-file "$INVENTORY/devices.yml" \
  --host localhost \
  --include "$APP" \
  --vars "{\"TLS_MODE\": \"$TLS_MODE\", \"DOMAIN_PRIMARY\": \"$DOMAIN\", \"users\": {\"administrator\": {\"authorized_keys\": [\"$SSH_PUBLIC_KEY\"]}}}"
infinito administration deploy dedicated "$INVENTORY/devices.yml" \
  --password-file "$INVENTORY/.password" \
  --diff -vv

Credits¶

Implemented by Kevin Veen-Birkenbach. Part of the Infinito.Nexus Project and maintained by Kevin Veen-Birkenbach. Licensed under the Infinito.Nexus Community License (Non-Commercial).