Ansible Playbook and Inventory Generator

Build a useful ansible management lab on Ubuntu 24.04 LTS amd64, unless the target installer or embedded board requires its explicitly selected OS.

Use a controller, two managed Linux nodes and a versioned baseline playbook. Include only the components this workload needs. Use synthetic sample data and placeholders for site-specific domains, authorized SSH public keys and external integration credentials. Create a non-root operator and keep administrative access private. Never put real credentials, patient records or customer data in the image.

Acceptance checks: run syntax and inventory checks, apply the baseline and confirm a second playbook run reports no unintended changes. Boot the actual artifact and repeat relevant health, persistence and access checks after reboot. Keep hardware-dependent checks pending until the specified equipment is attached.

Deliver the bootable image or reproducible deployment recipe, the software inventory and a test report that separates successful assembly from runtime verification. Ask for missing hardware, storage and access details before making irreversible deployment choices. Do not deploy into production or erase an existing disk without an explicit target.