Consensus Enterprises Adopts Pure Ansible Infrastructure to Reduce Complexity

Staff Reporter

Consensus Enterprises has announced a shift in its Infrastructure-as-Code (IaC) approach, opting for a simpler, more cost-effective model by adopting a pure Ansible infrastructure. Previously, the company employed a dual-tool system using both Terraform and Ansible to manage cloud provisioning and configuration, but this approach introduced unnecessary complexity. By consolidating to Ansible and leveraging DigitalOcean’s services instead of OpenStack, Consensus reduced operational costs and eliminated the need for "null_resource" provisioners and variable-passing challenges between Terraform and Ansible.

The move also included adopting Tailscale for VPN management, replacing manual Wireguard server setups with a streamlined user onboarding process. Additionally, the company separated its IaC repositories into dedicated "dev" and "prod" environments, reducing the risk of accidental operations on production systems. To support this transition, Consensus Enterprises published several Ansible Galaxy collections and provided an illustrative GitLab project called "Example Aegir3 Infrastructure" to demonstrate their new approach. This update is part of their "Pure Ansible Infrastructure" blog series, with the article "Toward Infrastructure Simplicity" first appearing on the Consensus Enterprises blog.

Reference: Toward infrastructure simplicity, Consensus Enterprises (27 November 2024)

Disclosure: This content is produced with the assistance of AI.

Disclaimer: The opinions expressed in this story do not necessarily represent that of TheDropTimes. We regularly share third-party blog posts that feature Drupal in good faith. TDT recommends Reader's discretion while consuming such content, as the veracity/authenticity of the story depends on the blogger and their motives.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.