Ansible Training – 11. Event Driven Ansible

Docs: 11.1 Event Driven Ansible - Basics

Mon, 01 Jan 0001 00:00:00 +0000

In this lab we are going to learn how to use Event Driven Ansible. For the following tasks, server node1 and node2 act as webservers. You can use Lab 4.0 as a guideline.

Task 1

Point your webbrowser to the official documentation of ansible-rulebook.
Install and configure everything needed to run ansible-rulebook and source plugins.
Check the version of ansible-rulebook

Solution Task 1

https://ansible-rulebook.readthedocs.io/

Fedora 36+:

1
2
3
4


sudo dnf --assumeyes install java-17-openjdk python3-pip
export JAVA_HOME=/usr/lib/jvm/jre-17-openjdk
pip install ansible ansible-rulebook
ansible-galaxy collection install ansible.eda

Enterprise Linux 9:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13


sudo dnf install java-17-openjdk
export JAVA_HOME=/usr/lib/jvm/jre-17-openjdk
sudo dnf install python3-pip
python3 -m venv ~/python
. ~/python/bin/activate
pip install --upgrade pip
pip install ansible ansible-rulebook

ansible-galaxy collection install ansible.eda

sudo dnf install systemd-devel gcc python3-devel

pip install -r ~/.ansible/collections/ansible_collections/ansible/eda/requirements.txt

1

ansible-rulebook --version

Output on EL9:

1
2
3
4
5
6


version__ = '1.0.0'
Executable location = /home/ansible/python/bin/ansible-rulebook
Drools_jpy version = 0.3.4
Java home = /usr/lib/jvm/java-17-openjdk-17.0.7.0.7-3.el9.x86_64
Java version = 17.0.7
Python version = 3.9.16 (main, Dec 8 2022, 00:00:00) [GCC 11.3.1 20221121 (Red Hat 11.3.1-4)]

Task 2

Write a playbook webserver.yml that installs the servers in group web as webservers. See Lab 4.0 for guidelines.
Ensure that the playbook also sets a webpage at /var/www/html/index.html.
Ensure that the inventory file hosts in the folder inventory has the group web with node1 and node2 as members.
Run the playbook webserver.yml and check that the webservers are up and running.

Solution Task 2

1

cat webserver.yml

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33


---
- hosts: web
 become: true
 tasks:
 - name: install httpd
 ansible.builtin.dnf:
 name:
 - httpd
 - firewalld
 state: installed
 - name: start and enable httpd
 ansible.builtin.systemd_service:
 name: httpd
 state: started
 enabled: true
 - name: put default webpage
 ansible.builtin.copy:
 content: "Ansible Labs by Puzzle ITC"
 dest: /var/www/html/index.html
 owner: root
 group: root
 mode: "0644"
 - name: start and enable firewalld
 ansible.builtin.systemd_service:
 name: firewalld
 state: started
 enabled: true
 - name: open firewall for http
 ansible.posix.firewalld:
 service: http
 state: enabled
 permanent: true
 immediate: true

1

cat inventory/hosts

1
2
3
4
5
6


[controller]
control0 ansible_host=<ip-of-control0>

[web]
node1 ansible_host=<ip-of-node1>
node2 ansible_host=<ip-of-node2>

1
2
3
4


ansible-playbook -i inventory/hosts webserver.yml
sudo dnf install -y lynx
lynx http://<ip-of-node1>
lynx http://<ip-of-node2>

Task 3

Write a rulebook webserver_rulebook.yml that checks if the webpages on node1 and node2 are up and running.
If the webpages are not available anymore, the webserver.yml playbook should be re-run.
Use url_check from the ansible.eda collection as the source plugin in your rulebook.
Check the availability of the websites every 8 seconds.

Note

If you don’t have the ansible.eda collection installed yet, ansible-rulebook would start, but fail because the url_check source plugin cannot be found.

Solution Task 3

1

cat webserver_rulebook.yml

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16


---
- name: rebuild webservers if site down
 hosts: web
 sources:
 - name: check webserver
 ansible.eda.url_check:
 urls:
 - http://<ip-of-node1>:80/
 - http://<ip-of-node2>:80/
 delay: 8
 rules:
 - name: check if site down and rebuild
 condition: event.url_check.status == "down"
 action:
 run_playbook:
 name: webserver.yml

Task 4

Start webserver_rulebook.yml in verbose mode.
Stop the httpd service on node1 with ansible from another terminal on control0 and see how the playbook webserver.yml is re-run. (You could also just stop the service directly on node1.)

Solution Task 4

1
2
3


ansible-rulebook --rulebook webserver_rulebook.yml -i inventory/hosts --verbose

ansible node1 -i inventory/hosts -b -m ansible.builtin.systemd_service -a "name=httpd state=stopped"

Task 5

Write the rulebook webhook_rulebook.yml that opens a webhook on port 5000 of the control node control0.
The rulebook should re-run the playbook webserver.yml if the webhook receives a message matching exactly the string “webservers down”.
Use webhook from the ansible.eda collection as the source plugin in your rulebook.

Solution Task 5

1

cat webhook_rulebook.yml

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14


---
- name: rebuild webserver if webhook receives message that matches rule condition
 hosts: web
 sources:
 - name: start webhook and listen for messages
 ansible.eda.webhook:
 host: 0.0.0.0
 port: 5000
 rules:
 - name: rebuild webserver if monitoring tool sends alert
 condition: event.payload.message == "webservers down"
 action:
 run_playbook:
 name: webserver.yml

Task 6

Run the rulebook webhook_rulebook.yml in verbose mode.
Send the string “webservers running” to the webhook.
You can do this by issuing: curl -H 'Content-Type: application/json' -d "{\"message\": \"webservers running\"}" 127.0.0.1:5000/endpoint
See how the message is received, processed, but no actions are taken since the message doesn’t match the condition defined.
Now send the message “webservers down” to the webhook. See how the playbook webserver.yml is run.

Solution Task 6

1

ansible-rulebook --rulebook webhook_rulebook.yml -i inventory/hosts --verbose

1

curl -H 'Content-Type: application/json' -d "{\"message\": \"webservers running\"}" 127.0.0.1:5000/endpoint

1

curl -H 'Content-Type: application/json' -d "{\"message\": \"webservers down\"}" 127.0.0.1:5000/endpoint

Task 7

Write the rulebook complex_rulebook.yml. It has to meet the following requirements:
It should check for three things:
- check if the website on one of the two webservers is down. (Same as Task 3 above)
- check if the message matches exactly the string “webservers down” (Same as Task 5 above)
- check if the message contains the string “ERROR” or “error”
If one of the criteria above are met, do two things:
1. run the ansible shell module to print the string “WEBSERVER ISSUES, REMEDIATION IN PROGRESS.” into the journald log. (Use the command systemd-cat echo "WEBSERVER ISSUES, REMEDIATION IN PROGRESS.")
2. run playbook webservers.yml
Start the rulebook complex_rulebook.yml and send the message “webservers down” to the webhook again.

Solution Task 7

1

cat complex_rulebook.yml

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28


---
- name: rebuild webserver if webhook receives message that matches rule condition
 hosts: web
 sources:
 - name: check webserver
 ansible.eda.url_check:
 urls:
 - http://<ip-of-node1>:80/
 - http://<ip-of-node2>:80/
 delay: 8
 - name: start webhook and listen for messages
 ansible.eda.webhook:
 host: 0.0.0.0
 port: 5000
 rules:
 - name: rebuild webserver if any source reports an alert
 condition:
 any:
 - event.url_check.status == "down"
 - event.payload.message == "webservers down"
 - event.payload.message is search("ERROR",ignorecase=true)
 actions:
 - run_module:
 name: ansible.builtin.shell
 module_args:
 cmd: "systemd-cat echo \"WEBSERVER ISSUES, REMEDIATION IN PROGRESS.\""
 - run_playbook:
 name: webserver.yml

1

ansible-rulebook --rulebook complex_rulebook.yml -i inventory/hosts --verbose

1

curl -H 'Content-Type: application/json' -d "{\"message\": \"webservers down\"}" 127.0.0.1:5000/endpoint

Note, that you would have to open port 5000 on the firewall if the curl command is not sent from the controller itself.

Task 8

What source plugins are available in the ansible.eda collection? Search the content of event-driven-ansible on GitHub.com.

Solution Task 8

Event Driven Ansible on GitHub

All done?

Docs: 11.2. Event Driven Ansible - Events and Facts

Mon, 01 Jan 0001 00:00:00 +0000

In this lab we will have a closer look at events and facts.

Task 1

Copy the rulebook from Lab 11.2 Task 3 to a new one with the name debug_event_rulebook.yml.
Substitute the run_playbook action with a debug action.
That debug action should print out all information from the event.
Stop the httpd service on node1.
Run the rulebook in verbose mode. The debug action should show all information about the event.

Solution Task 1

1

cat debug_event_rulebook.yml

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16


---
- name: show event json if site down
 hosts: web
 sources:
 - name: check webserver
 ansible.eda.url_check:
 urls:
 - http://<ip-of-node1>:80/
 - http://<ip-of-node2>:80/
 delay: 8
 rules:
 - name: check if site down and debug
 condition: event.url_check.status == "down"
 action:
 debug:
 var: event

1

ansible node1 -i inventory/hosts -b -m ansible.builtin.systemd_service -a "name=httpd state=stopped"

1

ansible-rulebook --rulebook debug_event_rulebook.yml -i inventory/hosts -vv

1
2
3
4
5
6


...
2023-06-26 15:04:55,381 - ansible_rulebook.rule_set_runner - INFO - call_action debug
2023-06-26 15:04:55,381 - ansible_rulebook.rule_set_runner - INFO - substitute_variables [{'var': 'event'}] [{'event': {'url_check': {'error_msg': "Cannot connect to host 5.102.146.223:80 ssl:default [Connect call failed ('5.102.146.223', 80)]", 'url': 'http://5.102.146.223/', 'status': 'down'}, 'meta': {'received_at': '2023-06-26T13:04:55.379428Z', 'source': {'name': 'check webserver', 'type': 'ansible.eda.url_check'}, 'uuid': '6710f9a8-c489-4699-a804-8e796855e290'}}}]
2023-06-26 15:04:55,381 - ansible_rulebook.rule_set_runner - INFO - action args: {'var': 'event'}
{'url_check': {'error_msg': "Cannot connect to host 5.102.146.223:80 ssl:default [Connect call failed ('5.102.146.223', 80)]", 'url': 'http://5.102.146.223/', 'status': 'down'}, 'meta': {'received_at': '2023-06-26T13:04:55.379428Z', 'source': {'name': 'check webserver', 'type': 'ansible.eda.url_check'}, 'uuid': '6710f9a8-c489-4699-a804-8e796855e290'}}
...

Task 2

Rewrite the rulebook debug_event_rulebook.yml:
Use a run_playbook action to start a playbook named sos.yml
The playbook sos.yml should create an unattended sos report labeled with the fully qualified collection name of the source plugin used. Be sure to install the appropriate packages so that the sos report can be created.
The name of the source plugin should be taken from the json output as a variable.
The creation of the sos report takes quite some time.
Ensure that the condition is throttled to run the action once within 5 minutes at most.
The delay of the source check should stay at 8 seconds.
Run the rulebook debug_event_rulebook.yml and ensure the sos reports on the webservers have the needed label.

Note

There are good onlinetools to convert one-line json to multiline json as well as json to yaml converters. Note: The json copied from the output has sometimes single quotes, RFC 8259 demands double quotes. Be sure that your converter fixes this as well. These converters can come in handy for easier reading of the output.

Solution Task 2

See the documentation on how to throttle event storms.

1

cat debug_event_rulebook.yml

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20


---
- name: run sos playbook if site down
 hosts: web
 sources:
 - name: check webserver
 ansible.eda.url_check:
 urls:
 - http://<ip-of-node1>:80/
 - http://<ip-of-node2>:80/
 delay: 8
 rules:
 - name: check if site down and rebuild
 condition: event.url_check.status == "down"
 throttle:
 once_within: 5 minutes
 group_by_attributes:
 - event.meta.source.type
 action:
 run_playbook:
 name: sos.yml

1

cat sos.yml

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13


---
- hosts: web
 become: true
 tasks:
 - name: install sos package
 ansible.builtin.dnf:
 name:
 - sos
 state: installed

 - name: create a sos report unattended containing no sensitive information
 ansible.builtin.command:
 cmd: "sos report --clean --batch --label {{ ansible_eda.event.meta.source.type }}"

1

ansible-rulebook --rulebook debug_event_rulebook.yml -i inventory/hosts -vv

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24


...
2023-06-28 11:15:53,766 - ansible_rulebook.builtin - INFO - ruleset: show event \
 json if site down, rule: check if site down and rebuild
2023-06-28 11:15:53,766 - ansible_rulebook.builtin - INFO - Calling Ansible runner

PLAY [web] *********************************************************************

TASK [Gathering Facts] *********************************************************
ok: [node1]

TASK [install sos package] *****************************************************
ok: [node1]

TASK [create a sos report unattended containing no sensitive information] ******
changed: [node1]
...
PLAY RECAP *********************************************************************
node1 : ok=3 changed=1 unreachable=0 failed=0
skipped=0 rescued=0 ignored=0
2023-06-28 11:17:59,741 - ansible_rulebook.builtin - INFO - Ansible Runner \
 Queue task cancelled
2023-06-28 11:17:59,742 - ansible_rulebook.builtin - INFO - Playbook rc: 0, \ 
 status: successful
...

All done?

Preview of AAP EDA-Controller GUI

Docs: 11.3. EDA-Server

Mon, 01 Jan 0001 00:00:00 +0000

In this lab we will learn how to use EDA-Server to run our rulebooks. Some tasks have to be done on Ascender.

Task 1

To connect your EDA-Server to your Ansible Controller, you have to create an access token on Ascender and add it to EDA-Server

On Ascender, create an access token for the user Ansible. Be sure to choose the write scope
On EDA-Server add this controller token to the user Ansible

Solution Task 1

Go to the Ascender Web-GUI

On the left hand side, chose Access, then Users
Click on user ansible, then chose the tab Tokens and click on the blue button Add
Leave the Application field empty, add a description and chose the write scope.
Click the Save button. Copy the Token from the popup window. This token is shown only once, so remember it.

Go to the EDA-Server Web-GUI

On the left-hand side, chose User Access and then Users
On the right, chose user ansible
Now to the tab Controller Tokens
Click on the button Create controller token. If you created already one, you have to delete it first to be able to create a new one.
Enter a name, a description and paste in the token from Ascender in the Token field

Task 2

Now we add a git repository with our rulebooks as a project to EDA-Server

Be sure, your ansible rulebooks are residing in a top level folder “rulebooks” inside your git repository
Add a Project to EDA-Server pointing to your git repository

Note

After creation the status of the project will be failed as long as you don’t have a directory extensions/eda/rulebooks or rulebooks (relative to the root of the repository) present.

Solution Task 2

On the left side navigate to Resources and then Projects.
On the right side click on the Create project button.
Enter a name, description, leave SCM Type as Git.
As SCM URL enter the path to your git repository on your Controller node (https://<yourname>-controller.workshop.puzzle.ch:4000/ansible/techlab). Remember to use port 4000.
Leave the Credential field empty.
Clink on Create project at the bottom of the page.

Task 3

The last step needed to be able to run rulebooks is creating a Decision Environment.

Install ansible-builder with pip on your <yourname>-edaserver. Be sure to install podman as well since it’s the default container engine for ansible-builder.
Prepare a yaml file techlab-de.yml with the definition for your Decision Environment. Take the blueprint from the ansible-rulebook GitHub project as your base.
Build the Decision Environment, name the image techlab-de.yml and tag it with latest.
Push it to the container registry provided by your teacher.

Solution Task 3

1

pip3 install -y ansible-builder podman

1

cat techlab-de.yml

---
version: 3
images:
base_image:
name: 'registry.access.redhat.com/ubi9/python-311:latest'
dependencies:
galaxy:
collections:
- ansible.eda
python:
- azure-servicebus
- aiobotocore
- aiohttp
- aiokafka
- watchdog
- systemd-python
- dpath
- ansible-rulebook
ansible_core:
package_pip: ansible-core==2.14.4
ansible_runner:
package_pip: ansible-runner
system:
- java-17-openjdk-devel [platform:rpm]

1

ansible-builder build -f techlab-de.yml -t techlab-de:latest

1
2


podman login https://<registry_url> -u <username> -p <password>
podman push techlab-de:latest <registry_url>/techlab-de:latest

Task 4

Add the Decision Environment techlab-de you just created to EDA-Server

Solution Task 4

On the left side of the EDA-Server Web-GUI navigate to Resources then Decision Environments.
On the right side, click on Create decision environemnt.
Enter a name and description.
In the Image field enter the path with tag to your Decision Environment (<registry_url>/techlab-de:latest)
Leave the Credentials field empty
Click on Create decision environment at the bottom of the page.

Task 5

Now have everything ready to run an ansible-rulebook. Ensure you have a job template Provision_Webserver in the Organization Techlab of your Ascender server. See the Ascender labs to set it up.

Make the following changes to your webserver_rulebook.yml rulebook (Lab 11.1):

Change the action of the rulebook to start a job template Provision_Webserver in the organization Techlab.
Be sure to push the changes into your git repository.
On the EDA-Server create a Rulebook Activation

Solution Task 5

1

cat webserver_rulebook.yml

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17


---
- name: rebuild webservers if site down
 hosts: web
 sources:
 - name: check webserver
 ansible.eda.url_check:
 urls:
 - http://<yourname>-node1.workshop.puzzle.ch:80/
 - http://<yourname>-node2.workshop.puzzle.ch:80/
 delay: 8
 rules:
 - name: check if site down and rebuild
 condition: event.url_check.status == "down"
 action:
 run_job_template:
 name: Provision_Webserver
 organization: Techlab

On the left side of the EDA-Server GUI, navigate to Views, then Rulebook Activiations
On the right side click Create rulebook activation
Enter the name Webserver Provisioning, add a description and chose the project Techlab Repo.
Chose webserver_rulebook.yml in the Rulebook field.
(if no Rulebook shows up, sync the project)
Chose techlab-de in the Decision environment field.
Leave Restart policy set to On failure.
Click Create rulebook activation at the bottom of the page.

Task 6

After a successful creation of the Rulebook Activation you can follow its logs

Navigate to Views, then Rulebook Activations on the left side and then click on your Webserver Provisioning Rulebook Activation.
Click on the History tab.
Now click on the running instance ot the activation.
In the Output field have a look at the logs

Solution Task 6

Output filed of the activation:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16


2023-11-08 14:31:09,925 - ansible_rulebook.app - INFO - Starting worker mode
2023-11-08 14:31:09,925 - ansible_rulebook.websocket - INFO - websocket ws://edaserver-app-daphne:8001/api/eda/ws/ansible-rulebook connecting
2023-11-08 14:31:09,958 - ansible_rulebook.websocket - INFO - websocket ws://edaserver-app-daphne:8001/api/eda/ws/ansible-rulebook connected
2023-11-08 14:31:09,996 - ansible_rulebook.job_template_runner - INFO - Attempting to connect to Controller https://puzzle-ascender.workshop.puzzle.ch
2023-11-08 14:31:10,106 - ansible_rulebook.app - INFO - AAP Version 23.1.0
2023-11-08 14:31:10,106 - ansible_rulebook.app - INFO - Starting sources
2023-11-08 14:31:10,107 - ansible_rulebook.app - INFO - Starting rules
2023-11-08 14:31:10,107 - ansible_rulebook.engine - INFO - run_ruleset
2023-11-08 14:31:10,109 - drools.ruleset - INFO - Using jar: /usr/local/lib/python3.9/site-packages/drools/jars/drools-ansible-rulebook-integration-runtime-1.0.5-SNAPSHOT.jar
2023-11-08 14:31:10 669 [main] INFO org.drools.ansible.rulebook.integration.api.rulesengine.AbstractRulesEvaluator - Start automatic pseudo clock with a tick every 100 milliseconds
2023-11-08 14:31:10,673 - ansible_rulebook.engine - INFO - ruleset define: {"name": "rebuild webservers if site down", "hosts": ["web"], "sources": [{"EventSource": {"name": "check webserver", "source_name": "ansible.eda.url_check", "source_args": {"urls": ["http://puzzle-node1.workshop.puzzle.ch:80/"], "delay": 8}, "source_filters": []}}], "rules": [{"Rule": {"name": "check if site down and rebuild", "condition": {"AllCondition": [{"EqualsExpression": {"lhs": {"Event": "url_check.status"}, "rhs": {"String": "down"}}}]}, "actions": [{"Action": {"action": "run_job_template", "action_args": {"name": "Provision_Webserver", "organization": "Puzzle"}}}], "enabled": true}}]}
2023-11-08 14:31:10,690 - ansible_rulebook.engine - INFO - load source
2023-11-08 14:31:11,166 - ansible_rulebook.engine - INFO - load source filters
2023-11-08 14:31:11,167 - ansible_rulebook.engine - INFO - loading eda.builtin.insert_meta_info
2023-11-08 14:31:11,586 - ansible_rulebook.engine - INFO - Calling main in ansible.eda.url_check
2023-11-08 14:31:11,587 - ansible_rulebook.websocket - INFO - feedback websocket ws://edaserver-app-daphne:8001/api/eda/ws/ansible-rulebook connecting

Task 7

Now, we stop the webserver on node1 and see in the logs of the rulebook activation how the rule triggers the action to start the job template on ascender and rebuild the webservers.

Solution Task 7

On <yourname>-node1.workshop.puzzle.ch:

1

sudo systemctl stop httpd

In the logs on EDA-Server (see the last task to navigate there):

 1
 2
 3
 4
 5
 6
 7
 8
 9
10


...
2023-11-08 14:33:27 847 [main] INFO org.drools.ansible.rulebook.integration.api.rulesengine.RegisterOnlyAgendaFilter - Activation of effective rule "check if site down and rebuild" with facts: {m={url_check={url=http://puzzle-node1.workshop.puzzle.ch:80/, status=down, error_msg=Cannot connect to host puzzle-node1.workshop.puzzle.ch:80 ssl:default [Connect call failed ('5.102.145.36', 80)]}, meta={source={name=check webserver, type=ansible.eda.url_check}, received_at=2023-11-08T14:33:27.845005Z, uuid=65c50f85-89af-4ab3-ac25-81a1f951c469}}}
2023-11-08 14:33:27,848 - ansible_rulebook.rule_generator - INFO - calling check if site down and rebuild
2023-11-08 14:33:40,545 - ansible_rulebook.rule_set_runner - INFO - Task action::run_job_template::rebuild webservers if site down::check if site down and rebuild finished, active actions 0
2023-11-08 14:33:40,550 - ansible_rulebook.rule_set_runner - INFO - call_action run_job_template
2023-11-08 14:33:40,552 - ansible_rulebook.rule_set_runner - INFO - substitute_variables [{'name': 'Provision_Webserver', 'organization': 'Puzzle'}] [{'event': {'url_check': {'url': 'http://puzzle-node1.workshop.puzzle.ch:80/', 'status': 'down', 'error_msg': "Cannot connect to host puzzle-node1.workshop.puzzle.ch:80 ssl:default [Connect call failed ('5.102.145.36', 80)]"}, 'meta': {'source': {'name': 'check webserver', 'type': 'ansible.eda.url_check'}, 'received_at': '2023-11-08T14:33:27.845005Z', 'uuid': '65c50f85-89af-4ab3-ac25-81a1f951c469'}}}]
2023-11-08 14:33:40,552 - ansible_rulebook.rule_set_runner - INFO - action args: {'name': 'Provision_Webserver', 'organization': 'Puzzle'}
2023-11-08 14:33:40,552 - ansible_rulebook.action.run_job_template - INFO - running job template: Provision_Webserver, organization: Puzzle
2023-11-08 14:33:40,552 - ansible_rulebook.action.run_job_template - INFO - ruleset: rebuild webservers if site down, rule check if site down and rebuild
2023-11-08 14:34:01,225 - ansible_rulebook.rule_set_runner - INFO - Task action::run_job_template::rebuild webservers if site down::check if site down and rebuild finished, active actions 0

Check the webpage http://<yourname>-node1.workshop.puzzle.ch/ in your internet browser and ensure the page is available again.