Skip to main content

Ansible IT Engine

DeployHub uses Ansible Galaxy Roles to incorporate server configuration management in your continuous deployment. DeployHub allows you to manage both the application stack and server configuration as a complete ‘super package.’ IT Engines such as Ansible, Puppet, or Chef are designed to perform server configuration management, but do not focus on managing the higher level application stack. DeployHub is designed to coordinate the application stack across the continuous deployment pipeline. It also includes the ability to call an IT engine to manage the IT stack. DeployHub supports database updates, version jumping, deployment version control, auditing and reporting.

DeployHub leverages the Ansible Galaxy roles from inside the Blueprint Designer. On start-up, DeployHub loads all available roles into the DeployHub database from the Ansible community site. These roles are defined to DeployHub as Components with Actions. release automation and Ansible Galaxy roles and continuous deploymentComponents are assigned to an Application and are versioned. With the roles immediately available, it is very easy to add the installation or update of Tomcat, WebSphere or Oracle. The new Component is defined to your Application, making your continuous deployment efforts easier with no extra steps.


This ‘super package’ includes calls to Ansible as an IT Engine for configuration management.
IT engine packageDeployHub provides the application stack management.  A similar process can be done with Chef and Puppet.  However, Chef and Puppet requires endpoint agents.  For this reason, you include a call to Chef and Puppet as a Workflow Action instead of creating an Ansible Application Component.

The lesson is to use the right DevOps tool for performing continuous deployment.  Use an IT Engine to manage your server configuration management and a Continuous Deployment solution to manage your application level changes. DeployHub allows you to do both easily with its integration capabilities.

How and Why to Use Deployment Workflows