A case study why Zoominfo uses Terraform Cloud in high-scale environment.
0 likes159 views
The document discusses Terraform, a tool for building and managing infrastructure as code through a high-level configuration language. It outlines the benefits of using Terraform for microservice-heavy environments, emphasizing automation, collaboration, and security compliance among DevOps teams. The document also mentions integration with version control systems, team management, audit logging, and policy enforcement to streamline infrastructure provisioning and management.
A case study why Zoominfo uses Terraform Cloud in high-scale environment.
- 2. Tal Hibner o Proud owner of this gentleman o Geek o Maccabi Tel Aviv Basketball fan o Master Scuba Diver o Former Medical Science student in HUJI o B.Sc in Computer Science, Ben Gurion University o Formerly Software Developer o Currently Devops Engineer at Zoominfo
- 3. Go To Market Intelligently Get B2B intelligence that businesses rely on to identify, engage, and close ideal buyers.
- 4. Agenda 1. What is Terraform? 2. The Problem 3. Discussion 4. Why Terraform Cloud? 5. Demo
- 5. What is ?
- 6. Terraform is a tool for building, changing, and versioning infrastructure safely and efficiently.
- 7. 1. Infrastructure is described using a high-level configuration syntax.(HCL) 2. This allows a blueprint of your application (or your entire datacenter) to be versioned and treated as you would any other code. 3. Additionally, infrastructure can be shared and re-used. Infrastructure as code
- 8. 1. Terraform has a "planning" step where it generates an execution plan. 2. The execution plan shows what Terraform will do to reach the desired state, and then executes it to build the described infrastructure. 3. You know exactly what Terraform will change and in what order, avoiding many possible human errors. 4. As the configuration changes, Terraform is able to determine what changed and create incremental execution plans which can be applied. Execution Plans & Automation
- 12. 1. Terraform helps you being both cloud-agnostic and enabling multiple providers and services to be combined and composed. 2. This enables Terraform to represent and manage the entire infrastructure with its supporting services, instead of only the subset that exists within a single provider. 3. Terraform is a universal tool to manage anything that has an API: https://registry.terraform.io/browse/providers
- 14. ● We want a solution that will improve Development and Devops’ lives, high scale of 200+ microservices and 280+ developers. ● We want to run Terraform remotely and collaborate on infrastructure with 25+ Devops Engineers. ● We want the teams remain secure and compliant every time they make a change to infrastructure. ● We want to integrate Terraform into our existing CI/CD pipeline. ● We want the developers to be able to create certain components via a self-service capability.(TBD) The Problem
- 15. ● We need an option for a simple config layer, something that writes Terraform automatically on the backend, etc. (self-service) ● Every in-house PAAS solution will increase the overhead for fixing devs mistakes and to maintain some complex logics. It won’t scale! ● Most of the 3rd party solutions, don’t give us a full end-to-end solution. ● Should your engineers be working on reinventing something that infrastructure tooling specialists at HashiCorp have spent years researching and developing? ● Partners and 1200+ Terreform community members create and contribute to the vast updates to Terraform core and providers. Discussion
- 17. Why ?
- 18. Module Registry A library of community modules from partners, contributors, and HashiCorp. Private registry of customized modules versioned, validated, and approved for internal use by the organization. https://registry.terraform.io/
- 19. VCS Integration Write, version, review, and collaborate on Terraform code using your preferred version control system. Integrate with Terraform Cloud to automatically validate configuration changes and trigger Terraform. Link changes made with Terraform to the associated changes in version control.
- 20. Rich REST API Leverage the Terraform API to integrate the provisioning workflow into an existing CI/CD pipeline or custom automation tooling.
- 21. Team Management & SSO Use GUI-based team management workflows and SSO to granulary enable and manage an organization of separate business units, teams, and users with role based access controls.
- 22. Team Management & SSO Use GUI-based team management workflows and SSO to granulary enable and manage an organization of separate business units, teams, and users with role based access controls.
- 23. Audit Logging Audit logs provide a central system of record to track all provisioned infrastructure.
- 24. Policy as Code Sentinel is a policy as code framework to automate multi-cloud governance. Require every provisioning run to enforce security, compliance, and operational best practices. Avoid manual code review which reduces agility and is error prone.
- 25. Configuration Designer A GUI-based workflow to combine modules and define variables for users to provision infrastructures without having to write infrastructure as code.
- 26. Cost Estimation View an estimated cost of infrastructure changes to a workspace following the Terraform plan and before provisioning.
- 27. DEMO
- 28. o Grant the project's default compute engine service account access to Google Container Registry o Create firewall rules to allow traffic from the internal LB checks o Create 2 proxy instances each in a different zone o Reserve the newly-created external IP addresses o Create 2 unmanaged instance groups (one per zone) o Assign the proxy instances to the 2 new instance groups o Create an internal load balancer, using the 2 instance groups as the backend
- 44. Create Firewall Rule for Allowing internal Google LB Checks
- 45. Create 2 proxy instances each in a different zone
- 46. Create Firewall Rule for Allowing internal Google LB Checks
- 47. Create 2 unmanaged instance groups (one per zone)
- 48. Create Internal Google Load Balancer
- 49. Thank You