How a Top European Cloud Provider Migrated to TFE Horacio Gonzalez 2022-06-22

Who are we? Introducing myself and introducing OVHcloud

Horacio Gonzalez @LostInBrittany Spaniard lost in Brittany, developer, dreamer and all-around geek Flutter

OVHcloud: A global leader Web Cloud & Telcom 35 Data Centers in 12 locations 1 Million+ Servers produced since 1999 Private Cloud 34 Points of Presence on a 20 TBPS Bandwidth Network 1.5 Million Customers across 132 countries Public Cloud 2200 Employees worldwide 3.8 Million Websites hosting Storage 115K Private Cloud VMS running 1.5 Billion Euros Invested since 2016 300K Public Cloud instances running P.U.E. 1.09 Energy efficiency indicator 380K Physical Servers running in our data centers 20+ Years in Business Disrupting since 1999 Network & Security

OVHcloud: an industrial history From Roubaix to the World

OVHcloud began with hardware We assembly our own bare metal servers

Looking for maximum efficiency We build our own (horizontal) racks

From components to datacenters

We master the industrial value chain

Wait, why is this relevant? This is a talk about Terraform Enterprise, isn’t it?

An industrial culture All around the company, from hardware to software

A strong build it ourselves culture And a deep commitment to Open Source

Let’s travel back to 2014 How can we industrialize deployment ?

In 2015 we built DaaS Deployment as a Service

Rise and fall of DaaS A four years kingdom

DaaS: API and web UI entry points

Hierarchical support

DaaS: clusters, groups & backends

Based on API calls, not IaC

A small team for a big project

2017 - DaaS creators leave the team

2019: a new unit arrives, GIS

Analyse: 3 main problems

Looking for a solution Terraform to the rescue!

We can do DaaS V2, can’t we?

What should we do now?

Enter Terraform

Better suited for the original goal

But Terraform alone isn’t enough

What about using CDS?

What about Terraform Cloud?

Discussing with HashiCorp

Let’s do a TFE workshop!

Terraform Enterprise From POC to Prod

A structured growth

Some numbers…

Extensively used by the teams

What’s next for us? Let’s continue step by step

A TFE training during onboarding And adding more guides

Developing some tooling To simplify bare metal deployment with our API

Providers, resources and agents To deal more smoothly with our infrastructure

What do the teams think of it? Spoiler: they are quite happy!

Teams currently using TFE ● ● ● ● ● ● ● ● Core Observability Core Observability US Critical Databases Data Convergence GIS Network GIS Systems GIS Tools Machine Learning & AI ● ● ● ● ● ● ● PCI PU Data PU Enablers Storage VOIP Web Cloud Database Webhosting

GIS Systems

Data Convergence

Webhosting

That’s all, folks! Thank you all!