How alvarovaca/ansible-tfg works
Project type and purpose
• This is an Ansible-based infrastructure-as-code project whose goal is to provision a high-availability distributed file system (Ceph) managed by Pacemaker, with supporting services (DNS, common OS hardening, etc.).
• The README points to an article on “Alta disponibilidad de sistemas ficheros distribuidos” (high-availability distributed file systems), confirming that the playbooks and roles glue together Ceph, Pacemaker, DNS, and general host configuration.
File structure
• Top‐level:
• ansible.cfg ‑ Ansible configuration
• hosts ‑ inventory defining groups of managed hosts
• pre.yml / post.yml ‑ orchestration playbooks executed before/after the main run
• group_vars/all ‑ variables applied to all hosts
• roles/:
• common: basic OS setup, handlers & tasks
• dns: installs/configures BIND, serves internal zone
• ceph: deploys Ceph monitors, OSDs, keyrings
• pacemaker: configures Pacemaker cluster for resource management
• Each role has tasks/main.yml, handlers, plus any files/templates (e.g., named.conf, Jinja2 templates for DNS zones or Ceph configs).
README for additional insights
• The linked blog describes an architecture where:
• A small Ceph monitor quorum ensures cluster metadata integrity
• OSD daemons serve the distributed data
• Pacemaker provides failover and fencing for monitor and OSD instances
• DNS resolves the Ceph cluster endpoints reliably