{"id":27752,"date":"2023-09-15T12:41:16","date_gmt":"2023-09-15T10:41:16","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=27752"},"modified":"2023-09-15T12:41:18","modified_gmt":"2023-09-15T10:41:18","slug":"ansible-automates-event-driven-lightspeed","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/ansible-automates-event-driven-lightspeed\/","title":{"rendered":"Ansible Automates \u2013 Event Driven & Lightspeed"},"content":{"rendered":"\n

It was a pleasure to attend the Ansible Automates Roadshow in Geneva this year with my colleague Chay Te. There were several topics and sessions covered during the full day. It was a learning opportunity about the vision and strategy around Ansible by Red Hat.<\/p>\n\n\n\n

The Welcome and Event Introduction was held by Sylvan Merli, Sales Manager from Red Hat. Thanks to him for the welcome and the introduction. All was well organized, and it was great to be able to discuss and socialize with other Ansible fanatics.<\/p>\n\n\n\n

\n
\"\"<\/figure>\n<\/figure>\n\n\n\n

The goal of this blog is to share some interesting information I learned. Have you ever heard of Event Driven Ansible and the Ansible Lightspeed?<\/p>\n\n\n\n

The Event Driven Ansible:<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The Event Driven Ansible is the way of executing actions (tasks) triggered by listening to a source event, where decision is made based on defined rules. The Ansible Rulebook is now available for that purpose.<\/p>\n\n\n\n

As a use case, I am just summarizing what was explained during the session:<\/p>\n\n\n\n

Let\u2019s think about a mission-critical system with piquet over the night. IT support people need to wake up almost every night to resolve an incident at 2 am by only restarting a service\/server. The time the root cause of the problem is found, why not having something that can detect the incident from a source, determines which decision need to be taken depending on the rule and execute actions to perform automation task such as restarting the failing service\/server without human intervention. That would be great, no? That\u2019s were come in the Event Driven Ansible. You can now then breathe and have automated tasks listening to defined source events where the system will decide by himself if a restart of the failing service\/server needs to be performed.<\/p>\n\n\n\n

There are a lot of use cases behind this new capability. <\/p>\n\n\n\n

The main objective behind this concept is to add observability and remediation by using Ansible. In my opinion, that\u2019s something that was missing in Ansible and which might be a very useful feature. Ansible is now able to do predication and execute tasks on his own. That\u2019s a cool feature, isn\u2019t it?<\/p>\n\n\n\n

If you\u2019re wondering what could be the source defined in the Ansible Rulebooks:  <\/p>\n\n\n\n

There are partner source plugins in roadmap.<\/p>\n\n\n\n