Ansible Tower - Task Integration

Share this post:
Integrations /
Jenkins Task-Level Integration
Integrations /
Jenkins Task-Level Integration

Related content:

Ansible Tower - Task Integration
Extend the value of your IT Service Management Solution...
Cutover integrations: Slack
Cutover integrations: Agile and DevOps tools
Cutover integrations: Collaboration tools
Ansible Tower - Task Integration
Extend the value of your IT Service Management Solution...
Cutover integrations: Slack
Cutover integrations: Agile and DevOps tools
Cutover integrations: Collaboration tools
Cutover for Resilience Testing
Cutover for Mergers, Acquisitions, and Divestitures

Cutover

May 10, 2021

Automate more with the Cutover Ansible integration

With Ansible you can automate configuration of almost any part of your estate. The challenge with Ansible that it’s hard to get visibility of that configuration across teams and align configuration with other release activities.

What can the Ansible Tower integration do?

In Cutover, you can start an Ansible Playbook as part of your release without direct access to Ansible Tower. There is a specific tasks type associated with starting an Ansible Playbook. This is identified in Cutover by the Ansible Icon associated with the task. The Playbook URL and and Server details can be viewed in the tasks detail panel.Ansible TowerEnter the key details to set up the task

When the task is started the status of the Ansible Playbook is updated in real-time from with Cutover, meaning that a Cutover user can be kept informed of progress without going into Ansible Tower. You can also send additional variables as needed, such as hostname, or asset ID.

What information does it need from a user?

It’s as simple as inputting the Ansible Playbook URL you want to start and any Server Details.

Prerequisites and Setup Requirements

You only need to set up the installation with Ansible once (this takes 5 minutes). In order to use the Ansible integration for Cutover, you need to create a Job Template Webhook. Once this is done you need to provide the Webhook URL, Server Details, and API Key to Cutover.

What is the architecture?

Cutover will send a message directly to your Ansible Tower Instance using Ansible Tower’s Browsable API.

FAQs

Is it secure? 

This Cutover service can connect directly to Ansible Tower. If needed, individual user tokens can be used. 

How can we prevent a large amount of ungoverned Ansible Tower Tasks?

Your Cutover CSM can create new task types within Cutover associated with an integration to limit this. We can then map to Cutover task types so the user is not presented with so many tasks that they may struggle to use them, or may create governance issues if used unexpectedly. It is also advised that playbooks are kept in separate playbooks rather than being heavily configuration driven.

Who can run an Ansible Tower Task?

Cutover can run Ansible playbooks as a service account or as an identified Cutover user. Using a Service Account is only recommended for non-destructive actions. Destructive actions or provisioning actions should be run as an identified user.

Does this integration run in rehearsal?

This integration does not run in rehearsal by default.

Learn more about how Cutover integrations can help you extend the value of your existing tools.

Share this post:
Webinar /
You're in the Cloud. Now what?
Webinar /
Solving migration challenges with automation, governance, and controls
Operational resilience /
Can surgical scrutiny save us from Fastly outages?