DeployHub Uses the Ansible IT Engine for Server Configuration.
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 and includes the ability to call an IT engine to manage the IT stack. DeployHub also 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. Components 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. No extra work required. It is all done for you. The new Component is defined to your Application, making your continuous deployment efforts easier.
The result is you get a ‘super package’ that includes calls to Ansible as an IT Engine for configuration management.
DeployHub 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 an Continuous Deployment solution to manage your application level changes. DeployHub allows you to do both easily with its integration capabilities.