[2017.04] Meetup #12] [TALK] André Bação - Terraform your Cloud

An introduction to the power of managed infrastructure with Terraform. In this talk we will see how to start using Terraform from the ground up and how to achieve a cloud infrastructure by code.

André Bação: Linux Lover by choice, Open-source supporter by mind and DevOps by profession.

GitHub rep: https://github.com/abacao/devopslx-terraform

1. Welcome “Terraform your Cloud” André Bação
2. Bio • André Bação • Prod Father • Linux Advocate • Devops Engineer @ Marionete
3. What is Terraform ?
4. It is an open source tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed and versioned.
5. Terraform syntax and interpolation are part of a open source language and specification called HCL – Hashicorp Configuration Language. * HCL is written in Go and looks a bit like NGINX
6. Terraform enables you to safely and predictably create, change and improve production infrastructure.
7. Advantages of Terraform?
8. Advantages of Terraform? Hashicorp Terraform AWS CloudFormation Open source VS Closed Source
9. Advantages of Terraform? Hashicorp Terraform AWS CloudFormation Open source VS Closed Source Multi Cloud VS Amazon only
10. Advantages of Terraform? Hashicorp Terraform AWS CloudFormation Open source VS Closed Source Multi Cloud VS Amazon only HCL VS JSON or YAML
11. Advantages of Terraform? Hashicorp Terraform AWS CloudFormation Open source VS Closed Source Multi Cloud VS Amazon only HCL VS JSON or YAML Managing States VS No States
12. .: Some Concepts :.
13. Provider A abstraction of the API/service provider such as:
14. Provider A abstraction of the API/service provider such as:
15. Provider A abstraction of the API/service provider such as:
16. Provider A abstraction of the API/service provider such as:
17. Provider A abstraction of the API/service provider such as:
18. Provider A abstraction of the API/service provider such as:
19. Resource It represents a component of a given provider such as:
20. Resource It represents a component of a given provider such as: • AWS Instance
21. Resource It represents a component of a given provider such as: • AWS Instance • Bitbucket Repository
22. Resource It represents a component of a given provider such as: • AWS Instance • Bitbucket Repository • Cloudflare Record
23. Resource It represents a component of a given provider such as: • AWS Instance • Bitbucket Repository • Cloudflare Record • DigitalOcean Volume
24. Resource It represents a component of a given provider such as: • AWS Instance • Bitbucket Repository • Cloudflare Record • DigitalOcean Volume • Azure SQL Server
25. Resource Resources have both: • Arguments (inputs) • Attributes (outputs) These are specific to each resource. Resources also have meta-parameters such as count and lifecycle.
26. (Resource) Argument The resource “aws_instance” accepts as input: • ami • associate_public_ip_address • availability_zone • volume_size
27. (Resource) Attribute This is an output or a computed value only available after the resource creation. For example: public_ip
28. Terraform Folder . └── terraform ├── main.tf ├── output.tf └── variables.tf
29. DigitalOcean Provider Example: provider "digitalocean" { token = "${var.do_token}" } resource "digitalocean_droplet" "devops" { image = "ubuntu-16-04-x64" region = "fra1" size = "512mb" name = "devops-tf-1" }
30. AWS Provider Example: provider "aws" { access_key = "${var.aws_access_key}" secret_key = "${var.aws_secret_key}" region = "${var.aws_region}" } resource "aws_instance" "master" { instance_type = "t2.micro" ami = "ami-e4c63e8b" }
31. Variables File: variable "aws_accesskey" { description = <<DESCRIPTION Insert your AccessKey: DESCRIPTION } variable "aws_region" { description = <<DESCRIPTION Your Favourite Region: DESCRIPTION default = "eu-central-1" }
32. Output File: output "ip" { value = "${aws_instance.master.public_ip}" }
33. + +
35. Q & A
36. Thank you andre@bacao.pt linkedin.com/in/andrebacao