• learn.spidernet.pl
  • Support
  • FAQ
    Community

    Introduction to Event-Driven Ansible

    • Table of Contents
    • Course
    • Lab Environment
    Preface A: Introduction
    Section A.1: Introduction to Event-Driven Ansible
    Section A.2: Orientation to the Classroom Environment
    Section A.3: Performing Lab Exercises
    Chapter 1: Getting Started with Event-Driven Ansible
    Section 1.1: Introduction to Event-Driven Ansible
    Section 1.2: Quiz: Introduction to Event-Driven Ansible
    Section 1.3: Creating and Testing Ansible Rulebooks
    Section 1.4: Guided Exercise: Acting on Webhook Events
    Section 1.5: Guided Exercise: Acting on System Journal Events
    Section 1.6: Guided Exercise: Acting on Results from the URL Check Plug-in
    Section 1.7: Summary
    Chapter 2: Getting Started with Event-Driven Ansible Controller
    Section 2.1: Installing Event-Driven Ansible Controller
    Section 2.2: Quiz: Installing Event-Driven Ansible Controller
    Section 2.3: Configuring Event-Driven Ansible Controller to Run Ansible Rulebooks
    Section 2.4: Guided Exercise: Configuring Event-Driven Ansible Controller to Run Ansible Rulebooks
    Section 2.5: Summary
    Chapter 3: Example Use Cases for Event-Driven Ansible
    Section 3.1: GitOps with Event-Driven Ansible
    Section 3.2: Guided Exercise: GitOps with Event-Driven Ansible
    Section 3.3: Event-Driven Ansible and NetOps
    Section 3.4: Guided Exercise: Event-Driven Ansible and NetOps
    Section 3.5: Guided Exercise: Event-Driven Ansible and Automated Notifications
    Section 3.6: Guided Exercise: Triggering Event-Driven Ansible from a Chat Room
    SectionSection 3.7: Summary
    Bookmark this page
    P123
    PreviousNext

    Summary

    • You can configure Event-Driven Ansible controller to listen for webhooks and to run a specific rulebook when it receives a specific webhook.

    • You can configure a rulebook in Event-Driven Ansible controller to run a playbook that sends a webhook to an application, perhaps to report that an event occurred.

    • GitLab actions such as pushing to a specific branch, or creating a merge request can send a webhook that causes Event-Driven Ansible controller to trigger continuous integration jobs in automation controller.

    • Event-Driven Ansible controller can listen for events that then trigger rulebooks to run playbooks that perform network device operations, such as bringing up downed ports and performing back ups on network devices.

    • When specific administrative tasks have been completed and Event-Driven Ansible controller is notified, it can trigger job templates to send informative messages to administrators in chat rooms.

    • Administrators can send messages in a chat room that trigger webhooks, which can cause Event-Driven Ansible controller to run a job template in automation controller.

    PreviousNext
    Revision: do274-2.4-65daa25

    Lab Controls

    Click CREATE to build all of the virtual machines needed for the classroom lab environment. This may take several minutes to complete. Once created the environment can then be stopped and restarted to pause your experience.

    If you DELETE your lab, you will remove all of the virtual machines in your classroom and lose all of your progress.


    Course Bookmarks
    No bookmarks have been added. Try adding one by clicking the icon next to a page title in the Course.
    Red Hat Training + Certification logo
    • Privacy Policy
    • Red Hat Training Policies
    • Terms of Use
    • All policies and guidelines
    • Release Notes
    • Cookie preferences