counterweight
3711421af5
The four ports were the only entries in services_config.yml with a real
justification: each is read twice, by the role that deploys the service on its
own box AND by a socket-proxy or Caddy play that runs on the EDGE host and
publishes it. A role default is invisible to that second play.
But the shape was wrong in two ways. The file had to be named in vars_files: by
30 plays - opt-in configuration that someone will eventually forget - and five
role defaults silently interpolated service_settings.*, so bitcoin_knots,
fulcrum, datum_gateway and mempool were not self-contained: using any of them
without that one vars_file entry broke it.
Each port now lives in host_vars/<owning box>/main.yml:
host_vars/knots_box_local/main.yml bitcoin_p2p_port, datum_gateway_api_port,
datum_gateway_stratum_port
host_vars/fulcrum_box_local/main.yml fulcrum_ssl_port
host_vars/mempool_box_local/main.yml mempool_frontend_port
host_vars auto-loads and outranks role defaults, so the owning role picks the
value up with no vars_files at all, and the edge play reads the same single
definition as hostvars['<host>'].<name>. The role defaults keep the protocol
standard (8333, 50002, ...) so each role still works standalone, with the live
deployment's value in host_vars winning.
Also fixed a fourth copy of an inventory identity: the mempool Caddy play had
"mempool-box:{{ ... }}" hardcoded in the upstream. It now derives the host from
hostvars['mempool_box_local'].ansible_host, so inventory is the only place any
box's name is written down.
services_config.yml is deleted, with 25 more vars_files entries across 19
playbooks. Between this and the previous commit, 87 vars_files entries are gone
and every variable in the repo now comes from group_vars/all, host_vars,
inventory, a role default, or that service's own *_vars.yml.
Verification: an edge-host probe resolves all eight ports and hostnames to
byte-identical values to the ones services_config.yml used to supply. Each
owning host resolves its own port through host_vars. All 37 playbooks'
--list-tasks output is unchanged. The four edge plays that consume these values
all check-diff changed=0 - the socket-proxy and Caddy units on vipy are
byte-identical, which is the direct proof the rewiring landed on the same
values. fulcrum and datum-gateway check-diff exactly as before (ok=28/changed=1
and ok=15/changed=1, both the known timer re-arm).
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
34 lines
1.5 KiB
YAML
34 lines
1.5 KiB
YAML
---
|
|
# Bitcoin Knots: full node built from source, with PGP signature and SHA256
|
|
# verification of the release tarball. The build is guarded by a binary-exists
|
|
# check, so a converged host skips the whole 30-60 minute compile.
|
|
#
|
|
# The chain lives in bitcoin_large_data_dir (/mnt/knots_data, ~875 GB). Nothing
|
|
# here touches it; the only `state: absent` tasks target the build tree under
|
|
# /opt/bitcoin-knots and run only when the binary is missing.
|
|
- name: Build and Deploy Bitcoin Knots from Source
|
|
hosts: bitcoin
|
|
become: yes
|
|
vars:
|
|
# Preserves the push URL this check has been reporting to. The role knows
|
|
# nothing about Uptime Kuma — this is just "a URL that accepts a ping".
|
|
healthcheck_push_url: "{{ healthcheck_push_urls.bitcoin_knots | default('') }}"
|
|
roles:
|
|
- bitcoin_knots
|
|
|
|
- name: Setup public Bitcoin P2P forwarding on the edge host
|
|
hosts: edge
|
|
become: yes
|
|
tasks:
|
|
- name: Expose Bitcoin P2P through a socket proxy
|
|
ansible.builtin.include_role:
|
|
name: socket_proxy
|
|
vars:
|
|
socket_proxy_name: bitcoin-p2p
|
|
socket_proxy_description: "Bitcoin P2P"
|
|
socket_proxy_listen_port: "{{ hostvars['knots_box_local'].bitcoin_p2p_port }}"
|
|
socket_proxy_upstream_host: "{{ hostvars['knots_box_local'].ansible_host }}"
|
|
socket_proxy_documentation: "https://github.com/bitcoin/bitcoin"
|
|
socket_proxy_free_bind: true
|
|
socket_proxy_timeout_stop_sec: 5
|
|
socket_proxy_log_to_journal: true
|