The Rundeck community tells us that they love using Rundeck and Ansible together. Like Rundeck, Ansible's straightforward design and learning curve make it Ops friendly.
What does Rundeck do for Ansible users? Rundeck gives them a great GUI front-end experience and ties together their Ansible automation alongside different tools used by other groups. Rundeck's powerful access control capabilities can be used to safely provide other users and teams with self-service access to run automation (including Ansible playbooks).
Watch the video below for a demo of an Ansible plugin for Rundeck. Keep reading below for more information. Also, we'd love your feedback, so please see the form at the end of this page.
All enterprises of sufficient size will have multiple versions and multiple generations of tools, technologies, platforms, and skills. Different teams will want to use different tools or languages (with various levels of interest in Ansible).
Rundeck makes it easy to create procedures that orchestrate and schedule across any silos you may encounter. Rundeck makes it easy to embrace the old while doing the new.
Operations is under increased pressure to safely provide self-service access to operations procedures. Whether it be for improving organizational capacity or implementing new DevOps lifecycles, Operations needs to empower people who sit outside of the boundaries of what would traditionally be considered an Operations team. Ansible users can leverage Rundeck's fine-grain access controls and easy-to-use UI to both setup and keep tight control over self-service capabilities.
Our favorite plugin to integrate Ansible with Rundeck is from the rundeck-ansible-plugin project. This lets you work in either of these useful ways:
Ansible's inventory data is returned to Rundeck as Nodes.
Grab the latest release from Github, drop it into your Rundeck's 'libext' folder, and get these great features right out of the box:
And special thanks to the team from Batix Software GmbH that created this awesome integration!