TerraformExtensibleProviderArchitecture.pdf

Slide 1

Slide 1 text

Slide 2

Slide 2 text

Clint (@catsby) Provider Team Lead, Terraform

Slide 3

Slide 3 text

Slide 4

Slide 4 text

Slide 5

Slide 5 text

Slide 6

Slide 6 text

Copyright © 2017 HashiCorp Terraform ▪ Write, Plan, and Create Infrastructure as Code ▪ Provision on any infrastructure / service / cloud !6 Goals Amazon GitHub DigitalOcean Fastly Microsoft Azure Packet Heroku DNSimple Librato Google Cloud Docker VMWare Sphere Many more…

Slide 7

Slide 7 text

Copyright © 2017 HashiCorp Terraform ▪ Unified view of infrastructure ▪ Easily compose multiple tiers/services (IaaS to PaaS to SaaS) ▪ Safely change/iterate infrastructure over time ▪ Manage anything with an API ▪ One workflow, many clouds !7 Write, Plan, and Create Infrastructure as Code

Slide 8

Slide 8 text

Copyright © 2017 HashiCorp Terraform ▪ Open Source! ▪ HCL: human readable, machine editable JSON ▪ Dependency graph ▪ terraform plan shows you changes ▪ terraform apply executes those changes in order ▪ Collaboration, history, audit trail [Enterprise] !8 Key Features

Slide 9

Slide 9 text

Slide 10

Slide 10 text

Copyright © 2017 HashiCorp Terraform ▪ Single binary written in Go, support for *nix, Windows ▪ Provider/Provisioner Plugins over RPC ▪ Split into Terraform Core and Terraform Providers (as of v0.10.0) ▪ Directed Acyclic Graph (DAG) !10 Architecture

Slide 11

Slide 11 text

Slide 12

Slide 12 text

Copyright © 2017 HashiCorp Terraform ▪ Configuration, State ▪ Interpolation, translating configuration into a Dependency Graph ▪ Discovery, communication with Plugins ▪ plan and apply !12 Core Responsibilities

Slide 13

Slide 13 text

Slide 14

Slide 14 text

Slide 15

Slide 15 text

Slide 16

Slide 16 text

Slide 17

Slide 17 text

Slide 18

Slide 18 text

Copyright © 2017 HashiCorp Provider Architecture ▪ Write, Plan, and Create Infrastructure as Code ▪ Provision on any infrastructure / service / cloud !18 Goals Amazon GitHub DigitalOcean Fastly Microsoft Azure Packet Heroku DNSimple Librato Google Cloud Docker VMWare Sphere Many more…

Slide 19

Slide 19 text

Copyright © 2017 HashiCorp Provider Architecture ▪ Detailed knowledge of the specific Provider (API, SDK, Authentication) ▪ Define Resources that map to specific Services ▪ Resource: abstraction/lifecycle management for cloud units/ resources !19 Provider Responsibilities

Slide 20

Slide 20 text

Slide 21

Slide 21 text

Slide 22

Slide 22 text

Copyright © 2017 HashiCorp Provider Architecture ▪ Providers are binary plugins ▪ Automatically discovered by Core ▪ Uses terraform/helper/schema framework to define lifecycle !22 Provider Architecture

Slide 23

Slide 23 text

Copyright © 2017 HashiCorp Provider Architecture !23 Provider layout - terraform-provider-supercloud/ ⌙ main.go ⌙ provider.go ⌙ resource_supercloud_instance.go ⌙ data_source_supercloud_instance.go ⌙ [...]

Slide 24

Slide 24 text

Copyright © 2017 HashiCorp Provider Architecture !24 Provider layout: provider.go package supercloud import ( "github.com/hashicorp/terraform/helper/schema" ) func Provider() *schema.Provider { return &schema.Provider{ Schema: map[string]*schema.Schema{ "access_key": { Type: schema.TypeString, Optional: true, Description: descriptions["access_key"], }, ResourcesMap: map[string]*schema.Resource{ "sc_cloud_instance": resourceSupercloudInstance(), }, }, } }

Slide 25

Slide 25 text

Copyright © 2017 HashiCorp Provider Architecture !25 Provider layout: resource_supercloud_instance.go package supercloud import ( "github.com/hashicorp/terraform/helper/schema" "github.com/supercloud/supercloud-sdk-go/supercloud" ) func resourceSupercloudInstance() *schema.Resource { return &schema.Resource{ Create: resourceSupercloudInstanceCreate, Read: resourceSupercloudInstanceRead, Update: resourceSupercloudInstanceUpdate, Delete: resourceSupercloudInstanceDelete, } }

Slide 26

Slide 26 text

Copyright © 2017 HashiCorp Provider Architecture !26 Provider layout: data_source_supercloud_instance.go package supercloud import ( "github.com/aws/aws-sdk-go/aws" "github.com/hashicorp/terraform/helper/schema" ) func dataSourceSupercloudInstance() *schema.Resource { return &schema.Resource{ Read: dataSourceSupercloudInstanceRead, Schema: map[string]*schema.Schema{ "id": { Type: schema.TypeString, }, }, } }

Slide 27

Slide 27 text

Copyright © 2017 HashiCorp Provider Architecture !27 Provider layout: main.go package main import ( "github.com/hashicorp/terraform/plugin" "github.com/hashicorp/terraform/terraform" ) func main() { plugin.Serve(&plugin.ServeOpts{ ProviderFunc: func() terraform.ResourceProvider { return supercloud.Provider() }, }) }

Slide 28

Slide 28 text

Slide 29

Slide 29 text

Slide 30

Slide 30 text

Slide 31

Slide 31 text

Slide 32

Slide 32 text

Slide 33

Slide 33 text

Copyright © 2017 HashiCorp v0.10.0 ▪ Separate core and provider versioning and release ▪ Enable the Provider community ▪ Per-project plugin management, version locking ▪ Minimal change to users !33 The Core/Provider split: Benefits

Slide 34

Slide 34 text

Copyright © 2017 HashiCorp Extending Terraform ▪ Users of Terraform are able to write new plugins in order to support new functionality in Terraform ▪ If it has an API, it can (probably) be managed by Terraform !34 Plugins

Slide 35

Slide 35 text

Slide 36

Slide 36 text

Slide 37

Slide 37 text

Slide 38

Slide 38 text

Copyright © 2017 HashiCorp Demo ▪ I already wrote the Heroku app ▪ I already wrote the Lambda function ▪ Other things were already written (I’ll explain soon enough) ▪ Code is proof of concept, not production ready ▪ Live demos always contain dragons !38 DISCLAIMERS

Slide 39

Slide 39 text

Copyright © 2017 HashiCorp Demo ▪ Setup a Heroku app ▪ Setup a Lambda function ▪ Wrote a new Provider ▪ With 2 data sources ▪ Extended an existing Provider ▪ Added a new resource ▪ Installed locally ▪ Integrated and clicked a physical button (hopefully it worked) !39 What did we do..