Sys-lock Role¶
Description: Locking mechanism for gating maintenance tasks until critical services stop, with configurable retry and timeout
Variables¶
author: Kevin Veen-Birkenbach
description: Locking mechanism for gating maintenance tasks until critical services stop, with configurable retry and timeout
license: Infinito.Nexus Community License (Non-Commercial)
company: Kevin Veen-Birkenbach https://www.veen.world
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’]}]
galaxy_tags: [‘maintenance’, ‘lock’, ‘system’, ‘administration’]
issue_tracker_url: https://s.infinito.nexus/issues
README¶
System Maintenance Lock¶
Description¶
This role provides a locking mechanism to ensure that critical services are not interrupted during maintenance activities such as updates, backups, or patch applications. It waits for specified services to stop and prevents conflicting operations.
Overview¶
The role performs the following:
Blocks execution until specified services have stopped.
Implements retry logic with a configurable timeout.
Ensures that maintenance tasks are executed only when the system is in a safe state.
Cosmos¶
The diagram places System Maintenance Lock 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-lock 💻]
svc_lock["lock"]
endSolid 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.
Purpose¶
The primary purpose of this role is to safeguard system stability during maintenance by preventing conflicts with running services. It ensures that maintenance operations proceed only when the environment is ready.
Features¶
Service Locking: Blocks maintenance tasks until critical services are stopped.
Timeout and Retry Logic: Configurable wait times and maximum attempts.
Conflict Avoidance: Prevents interference between maintenance operations and running services.
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).