Auto-update blog content from Obsidian: 2026-02-09 09:36:32
All checks were successful
Blog Deployment / Check-Rebuild (push) Successful in 7s
Blog Deployment / Build (push) Has been skipped
Blog Deployment / Deploy-Staging (push) Successful in 9s
Blog Deployment / Test-Staging (push) Successful in 1s
Blog Deployment / Merge (push) Successful in 6s
Blog Deployment / Deploy-Production (push) Successful in 9s
Blog Deployment / Test-Production (push) Successful in 3s
Blog Deployment / Clean (push) Has been skipped
Blog Deployment / Notify (push) Successful in 3s
All checks were successful
Blog Deployment / Check-Rebuild (push) Successful in 7s
Blog Deployment / Build (push) Has been skipped
Blog Deployment / Deploy-Staging (push) Successful in 9s
Blog Deployment / Test-Staging (push) Successful in 1s
Blog Deployment / Merge (push) Successful in 6s
Blog Deployment / Deploy-Production (push) Successful in 9s
Blog Deployment / Test-Production (push) Successful in 3s
Blog Deployment / Clean (push) Has been skipped
Blog Deployment / Notify (push) Successful in 3s
This commit is contained in:
@@ -11,10 +11,11 @@ tags:
|
||||
- proxmox
|
||||
- docker
|
||||
categories:
|
||||
- homelab
|
||||
---
|
||||
## Intro
|
||||
|
||||
In my homelab, I like to play with tools like Ansible and Terraform. The primary interface is the CLI, which I love, but sometimes a fancy web UI is nicer.
|
||||
In my homelab, I like to play with tools like Ansible and Terraform. The primary interface is the CLI, which I love, but sometimes a fancy web UI is just nice.
|
||||
|
||||
After setting up my OPNsense cluster, I wanted a way to keep it up to date on a schedule. Automation means Ansible to me, but how do you automate and schedule playbooks?
|
||||
|
||||
@@ -108,25 +109,23 @@ With Semaphore running, let’s take a quick tour of the UI and wire it up to a
|
||||
## Discovery
|
||||
|
||||
After starting the stack, I can reach the login page at the URL:
|
||||

|
||||

|
||||
|
||||
To log in, I use the credentials defined by `SEMAPHORE_ADMIN_NAME`/`SEMAPHORE_ADMIN_PASSWORD`.
|
||||
|
||||
On first login, Semaphore prompt me to create a project. I created the Homelab project:
|
||||

|
||||

|
||||
|
||||
The first thing I want to do is to add my *homelab* repository (you can find its mirror on Github [here](https://github.com/Vezpi/homelab)). In `Repository`, I click the `New Repository` button, and add the repo URL. I don't specify credentials because the repo is public:
|
||||

|
||||

|
||||
|
||||
ℹ️ Before continue, I deploy 3 VMs for testing purpose: `sem01`, `sem02` and `sem03`. I created them using Terraform with [this project](https://github.com/Vezpi/Homelab/tree/main/terraform/projects/semaphore-vms).
|
||||
|
||||
To interact with these VMs I need to configure credentials. In the the `Key Store`, I add the first credential, a SSH key for my user:
|
||||

|
||||

|
||||
|
||||
Then I create a new `Inventory`. I'm using the Ansible inventory format (the only one available). I select the SSH key previously created and select the type as `Static`. In the fields I enter the 3 hosts created with their FQDN:
|
||||

|
||||
|
||||

|
||||

|
||||
|
||||
✅ With a project, repo, credentials, and inventory in place, I can move forward and test to run an Ansible playbook.
|
||||
|
||||
@@ -173,26 +172,25 @@ I want to test something simple, install a web server with a custom page on thes
|
||||
```
|
||||
|
||||
In Semaphore UI, I can now create my first `Task Template` for Ansible playbook. I give it a name, the playbook path (from the root folder of the repo), the repository and its branch:
|
||||

|
||||

|
||||
|
||||
Time to launch the playbook! In the task templates list, I click on the ▶️ button:
|
||||

|
||||

|
||||
|
||||
The playbook launches and I can follow the output in real time:
|
||||

|
||||
|
||||
I can also review previous runs:
|
||||

|
||||

|
||||
|
||||
|
||||
✅ Finally I can confirm the job is done by checking the URL on port 80 (http):
|
||||

|
||||

|
||||
|
||||
Managing Ansible playbooks in Semaphore UI is pretty simple and really convenient. The interface is really sleek.
|
||||
|
||||
There are also a lot of customization available when setting the task template up. I can use variables in a survey, specify limit or tags. I really like it.
|
||||
|
||||
|
||||
---
|
||||
## Deploy with Terraform
|
||||
|
||||
@@ -205,7 +203,7 @@ I told myself it was a good opportunity to use Ansible to create a dedicated Pro
|
||||
Unable to encrypt nor hash, passlib must be installed. No module named 'passlib'
|
||||
```
|
||||
|
||||
This is apparently a known issue with Semaphore’s Python environment. As a workaround, I installed `passlib` directly in the container
|
||||
This is apparently a known issue with Semaphore’s Python environment. As a workaround, I installed `passlib` directly in the container:
|
||||
```bash
|
||||
docker exec -it semaphore_ui pip install passlib
|
||||
```
|
||||
@@ -235,19 +233,19 @@ With that in place, the playbook succeeded and I could create the user:
|
||||
```
|
||||
|
||||
Next I create a variable group `pve_vm`. A variable group let me define multiple variables and secrets together:
|
||||

|
||||

|
||||
|
||||
Then I create a new task template, this time with the kind Terraform Code. I give it a name, the path of the terraform [project](https://github.com/Vezpi/Homelab/tree/main/terraform/projects/semaphore-vms), a workspace, the repository along with its branch and. the variable group:
|
||||

|
||||

|
||||
|
||||
Running the template gives me some additional options related to Terraform:
|
||||

|
||||

|
||||
|
||||
After the Terraform plan, I'm proposed to apply, cancel or stop:
|
||||

|
||||

|
||||
|
||||
Finally after hitting ✅ to apply, I could watch Terraform build the VMs, just like using the CLI. At the end, the VMs were successfully deployed on Proxmox:
|
||||

|
||||

|
||||
|
||||
---
|
||||
## Conclusion
|
||||
|
||||
Reference in New Issue
Block a user