The cosmos generator linked a consumer to its provider only through an '<role>' in group_names reference or an explicit provides: name. A hard dependency has neither -- pinning the provider on unconditionally is exactly what removes the Jinja reference the generator was reading -- so web-svc-asset's bond to web-svc-file vanished from the diagram the moment it became binding. Match a service key against the provider's own primary key from the registry, in both directions. Services the role turns off drew a solid 1:1 edge, claiming a mandatory relationship for something that carries nothing at deploy time. They now render as a red 0..0 edge; edge merging gained a real precedence so a provider consumed through two keys stays live when only one is off. Named colour, not hex: a '#' opens an entity code in the mermaid lexer and turns the whole diagram into a parse error on GitHub. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2.5 KiB
sys-service
Description
Role to manage systemd service units for Infinito.Nexus software stacks. It installs or removes unit files, configures runtime behavior, and ensures services are properly deployed.
Overview
- Resets service units by removing old or obsolete definitions.
- Deploys new service unit files and service scripts.
- Optionally sets up timers linked to the services.
- Ensures correct reload/restart behavior across the stack.
- Provides the shared
files/debug.shSPOT for reusable service-failure diagnostics. - Exposes
tasks/utils/debug.ymlas the canonical Ansible wrapper around that script.
Cosmos
The diagram places sys-service 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 role [sys-service 💻]
svc_service["service"]
end
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
- Unit Cleanup: Automated removal of old service units.
- Custom Templates: Supports both
systemctl.service.j2andsystemctl@.service.j2. - Timers: Integrates with
sys-timerfor scheduled execution. - Runtime Limits: Configurable
RuntimeMaxSecper service. - Handlers: Automatic reload/restart of services when definitions change.
- Shared Diagnostics: Centralized
systemctl/journalctl/unit-file diagnostics viafiles/debug.sh. - Wrapper Task: Reusable Ansible include in
tasks/utils/debug.ymlfor calling and printing the shared diagnostics.
Further Resources
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).