Share This:

I recently wrote an article about the response of CAL-Fire fighters and the importance of operational preparedness in software.

In this post, I want to highlight the importance of selecting the right tooling for your operational needs. For Helix, we selected Ansible to develop our DevOps toolset.

Rationale for Ansible Selection

  • Push mechanism
  • Flexible playbooks
  • Jenkins Tie-In
  • Configuration management for Infrastructure

Push Mechanism

Ansible leverages a push mechanism for managing the infrastructure greatly simplifying the operational cost of managing multiple servers.

Flexible Playbooks

Ansible has a flexible mechanism when it comes to choosing the playbooks for execution depending on the use case.

For ex. we created multiple playbooks for migration of Remedy on-Prem customers to Helix and depending on the Remedy components that are installed at a customer site, the appropriate playbooks are selected for execution.

Jenkins Tie-In

R&D teams manage their CI/CD pipelines with Jenkins, Ansible has a module for Jenkins allowing the R&D teams to seamlessly extend the same development framework and process to cover DevOps tooling.

Configuration management for Infrastructure

Ansible helps maintain the configuration state of the infrastructure.

More on this in a future article

Call to Action

Let us know if you have any questions on migrating your Remedy on-prem instances to Helix with our Ansible toolset