Uploaded byJeeva Chelladhurai
Building Repeatable Infrastructure using Terraform
This document discusses using Terraform to build repeatable infrastructure. Terraform allows infrastructure to be defined code and treated as code. It is declarative, provider-agnostic, and allows infrastructure to be version controlled. Terraform reads configuration files, builds a dependency graph, and executes changes to infrastructure in a planned, repeatable way. It is open source software for building, changing, and versioning infrastructure safely and efficiently.
More Related Content
Similar to Building Repeatable Infrastructure using Terraform
Building Repeatable Infrastructure using Terraform
- 1. Build Repeatable Infrastructure usingTerraform Jeeva S.Chelladhurai Founder, Comorin Consulting Services https://www.linkedin.com/in/jeevachelladhurai/
- 2. IT.then ■ Manual ■ Downtime ■People Dependent ■ Misconfiguration ■ Not Repeatable
- 3. IT.now ■ Automated ■ VersionControlled ■ CI/CD ■ Infrastructure as Code ■ Repeatable
- 4. ■ Why – Declarative –Provider-agnostic – Codify the Infrastructure (IaC) – Plan before execute – Resource Graph – Change Automation ■ What – Open Source – Started in 2014 – Written in Go – Pluggable
- 5.
- 6. ARCHITECTURE • Read configuration •Build dependency graph • https://github.com/hashicorp/terraform
- 7. ARCHITECTURE • External Staticbinaries • RPC -> Between Core and Plugin • Provider comes as plugins • Implements Provider’s CRUD
- 8. Install ■ Download appropriatezip from https://www.terraform.io/downloads.html ■ Unzip the downloaded file, move the file terraform to any path of your choice ■ Verify installation by launching terraform from a terminal
- 9. TerraformConfiguration ■ Terraform Formator JSON – HCL – Hashicorp Configuration Language (recommended) – Extension .tf – .tf.json for JSON (only if produced by machines) ■ Text file, can be version controlled ■ Human readable format ■ Describes the Infrastructure ■ Declarative
- 10.
- 11. Provider Configuration ■ Managethe life-cycle of resources (CRUD) ■ Provider configuration – Keys / Password – Endpoint address ■ Resources are prefixed with providers – aws_instance, vsphere_virtual_machine ■ Initialize to download provider plugging provider "aws" { access_key = “xxxx" secret_key = “zzzzz" region = "us-east-1" }
- 12. Output Configuration ■ Responsevalues to be highlighted to the user
- 13.
- 14.
- 15. Thanks Jeeva S. Chelladhurai jeeva@comorin.co ComorinConsulting Service BlockChain, MicroService Architecture, Machine Learning, DevOps, Automation https://www.linkedin.com/in/jeevachelladhurai/