22 lines
1.0 KiB
Markdown
22 lines
1.0 KiB
Markdown
# 03 - Execution
|
|
|
|
Ensure you are operating within the `ansible/` directory inside the DevContainer.
|
|
|
|
## 1. Test Connectivity
|
|
Verify SSH access to the nodes before triggering the pipeline. Because SSH keys are not yet distributed, Ansible must prompt for the root password (`-k`).
|
|
|
|
```bash
|
|
ansible all -i inventories/<customer_name>/hosts.yml -m ping -u root -k
|
|
```
|
|
|
|
## 2. Execute the Playbook
|
|
Run the converged deployment playbook. You will be prompted for the SSH password once.
|
|
|
|
```bash
|
|
ansible-playbook -i inventories/<customer_name>/hosts.yml deploy.yml -u root -k
|
|
```
|
|
|
|
## Expected Behavior
|
|
* **Idempotency:** The playbook is declarative. If execution fails due to a transient network issue, re-running the exact command will bypass successful tasks and resume from the failure point.
|
|
* **Reboots:** If Phase 2 upgrades the running PVE kernel, the playbook forces a synchronized node reboot to ensure DRBD module compatibility against the active kernel headers. Ansible will pause and wait for the nodes to return online.
|