Introduction au FinOps avec Google Cloud - Cloud Alpes

Slide 1

Slide 1 text

💻 + 🚀 + ☁ = 💸 Introduction au FinOps avec Google Cloud

Slide 2

Slide 2 text

Julien Landuré CTO GDG & DevFest Nantes Organizer GDE Cloud jlandure.dev @jlandure

Slide 3

Slide 3 text

Back to the future

Slide 4

Slide 4 text

Elasticité rapide Accès libre aux capacités de calcul Mutualisation des ressources Accès via des mécanismes réseaux standards Mesure fine des usages Le Cloud ?

Slide 5

Slide 5 text

5 stratégies de déploiement Rehost Replatform Refactor Rebuild Replace

Slide 6

Slide 6 text

IaaS SaaS PaaS Servers VM instances Clusters Cluster management Serverless, autoscaling Google Cloud Platform products and services Compute Engine Kubernetes Engine Cloud Run Cloud Functions App Engine Compute Spectrum

Slide 7

Slide 7 text

Proprietary + Confidential IaaS Pay for what they allocate PaaS Pay for what they use Payment models

Slide 8

Slide 8 text

Ce qui existe en standard… “Pay-as-you-go” model

Slide 9

Slide 9 text

VM World Virtual machine Kernel Dependencies Application Code Hardware + hypervisor Dedicated server Kernel Dependencies Application Code Hardware Container Kernel + Container Runtime Dependencies Application Code Hardware Deployment ~mins (sec) Portable Very Eﬃcient Deployment ~months Not portable Low utilization Deployment ~days (mins) Hypervisor speciﬁc Low isolation, Tied to OS

Slide 10

Slide 10 text

Container World (Kubernetes) Virtual machine Kernel Dependencies Application Code Hardware + hypervisor Dedicated server Kernel Dependencies Application Code Hardware Container Kernel + Container Runtime Dependencies Application Code Hardware Deployment ~mins (sec) Portable Very Eﬃcient Deployment ~months Not portable Low utilization Deployment ~days (mins) Hypervisor speciﬁc Low isolation, Tied to OS Master Nodes

Slide 11

Slide 11 text

Proprietary + Confidential Google Compute products are billed per-second

Slide 12

Slide 12 text

Per VM max: ● 416 vCPUs, 12 TB of RAM, GPUs, TPUs ● Independently configurable, including disk! Start quickly, ~20 seconds to user code running Pre-built images, or create your own ● Debian, CentOS, CoreOS, Ubuntu, RHEL, SUSE ● Windows Server Datacenter: 2008, 2012 R2, 2016 , 2019 What is IaaS / Compute Engine?

Slide 13

Slide 13 text

Disk Persistent Disk ● Network based ● Configure size (to 64 TB) ● Disk or SSD ● Independent of VM ○ Global Snapshots ○ Multi-VM RO mount ● Larger disks == more throughput Local SSD ● Lowest latency ● 375 GB per disk (up to 8) ● Tied to VM lifecycle

Slide 14

Slide 14 text

GCE Machine Types

Slide 15

Slide 15 text

Custom Machine feature ● Flexible configurations ● Create a machine type with 1 vCPU and up to 96 vCPUs ● Extended Memory enables higher Mem:vCPU ratios ● Sizing recommendation // CREATE INSTANCE WITH 6 vCPUs and 5 GB MEMORY gcloud compute instances create my-vm --custom-cpu 6 --custom-memory 5 Config your own custom machine, with average 19% savings

Slide 16

Slide 16 text

#1 Rightsizing

Slide 17

Slide 17 text

Preemptible / Spot VMs Short lived, low cost virtual machines. ● Can run up to 24 hours ● Might be preempted at any time with 30 seconds notification ● Much lower price (up to 80% cheaper) than regular instances ● Offers the same machine types and options as regular VM instances ● Best for running non-urgent fault-tolerant jobs or short-lived tasks, like genomics, media transcoding, etc.

Slide 18

Slide 18 text

#2 Spot VM

Slide 19

Slide 19 text

Confidential + Proprietary Pet VS Cattle

Slide 20

Slide 20 text

Managed instance groups (MIGs) ● Instance group can be resized ● Manager ensures all instances are RUNNING ● Typically used with autoscaler ● Can be single zone or regional ● Supports autohealing A collection of identical VM instances that you control as a single entity, using an instance template.

Slide 21

Slide 21 text

Kubernetes (GKE)

Slide 22

Slide 22 text

#3 Autoscaling

Slide 23

Slide 23 text

Usage Level (% of month) % at which incremental is charged 0% - 25% 100% of base rate 25% - 50% 80% of base rate 50% - 75% 60% of base rate 75% - 100% 40% of base rate Up to 30% net discount for instances that run the entire month. Sustained use discounts

Slide 24

Slide 24 text

#4 Automatic Discounts

Slide 25

Slide 25 text

Ce qui existe en standard… “Pay-as-you-use” model

Slide 26

Slide 26 text

Serverless Deploy and scale applications fast and securely in a fully managed environment No Infra Management Auto-scaling

Slide 27

Slide 27 text

#3 Autoscaling

Slide 28

Slide 28 text

Pay per use CPU / Memory / Requests 100ms Pay per use

Slide 29

Slide 29 text

Cloud Run – Billable container instance time

Slide 30

Slide 30 text

#5 Serverless Pricing Model

Slide 31

Slide 31 text

Ce qui existe en standard… Pour mesurer et comprendre

Slide 32

Slide 32 text

Google Cloud Pricing Calculator Search for product you are interested in Estimate Instances cloud.google.com/products/calculator

Slide 33

Slide 33 text

Billing tools help to budget and monitor usage Budgets Alerts Reports Quotas

Slide 34

Slide 34 text

Ce qui existe en standard… Free tiers

Slide 35

Slide 35 text

Free tier https://cloud.google.com/free

Slide 36

Slide 36 text

Point d’étape

Slide 37

Slide 37 text

FinOps https:/ /www.ﬁnops.org

Slide 38

Slide 38 text

📈 Trends

Slide 39

Slide 39 text

2022 FinOps Principles by FinOps Foundation - FinOps Foundation under the ccby4.0 license

Slide 40

Slide 40 text

🌐 Identiﬁed FinOps practitioners

Slide 41

Slide 41 text

📝 Deﬁnition L'approche FinOps, contraction des termes de finance et d’opérations, vise au monitoring et à l’optimisation des coûts en matière de cloud computing. Il est question, dans le même esprit que la stratégie DevOps, d’encourager la coopération et l’assimilation des moyens IT par les métiers. De ce fait, les pratiques FinOps ajoutent une dimension financière dans la gestion des coûts du Cloud.

Slide 42

Slide 42 text

DevOps ❌ a standard ❌ a certification ❌ a goal ✅ a culture ✅ a philosophy ✅ a journey

Slide 43

Slide 43 text

1. Teams need to collaborate 2. Everyone takes ownership for their cloud usage 3. A centralized team drives FinOps 4. Reports should be accessible and timely 5. Decisions are driven by business value of cloud 6. Take advantage of the variable cost model of the cloud. 📌 Key principles in FinOps

Slide 44

Slide 44 text

Cloud FinOps is an evolving cloud ﬁnancial management discipline and cultural practice that: to collaborate on data-driven spending decisions enables organizations to get maximum business value by helping engineering, ﬁnance and business teams FinOps.org FinOps Principles by FinOps Foundation - FinOps Foundation under the ccby4.0 license

Slide 45

Slide 45 text

FinOps Principles by FinOps Foundation - FinOps Foundation under the ccby4.0 license

Slide 46

Slide 46 text

💬 Ecosystem

Slide 47

Slide 47 text

No content

Slide 48

Slide 48 text

No content

Slide 49

Slide 49 text

💰 25 Premier Members & 51 general members

Slide 50

Slide 50 text

💪 Upskilling

Slide 51

Slide 51 text

👤 FinOps Personas

Slide 52

Slide 52 text

52 FinOps Principles by FinOps Foundation - FinOps Foundation under the ccby4.0 license 🎓 Training & Certiﬁcation

Slide 53

Slide 53 text

53 💚 Community

Slide 54

Slide 54 text

📆 Events

Slide 55

Slide 55 text

💡 Capabilities Accelerate / State of DevOps Report

Slide 56

Slide 56 text

⚙ Domain & Capabilities

Slide 57

Slide 57 text

🚧 Tooling

Slide 58

Slide 58 text

No content

Slide 59

Slide 59 text

No content

Slide 60

Slide 60 text

No content

Slide 61

Slide 61 text

No content

Slide 62

Slide 62 text

💡 Examples of measurement

Slide 63

Slide 63 text

🤝 Adopt

Slide 64

Slide 64 text

⚡ What is the diﬀerence between forecasted spend and actual spend?

Slide 65

Slide 65 text

🎁 Percentage of commitment-based discounts that are estimated to go unused each month

Slide 66

Slide 66 text

No content

Slide 67

Slide 67 text

No content

Slide 68

Slide 68 text

Pourquoi s’y mettre ?

Slide 69

Slide 69 text

1. Accelerate business value realization and innovation 2. Drive financial accountability and visibility 3. Optimize cloud usage and cost efficiency 4. Enable cross-organizational trust and collaboration 5. Prevent sprawl of cloud spend 📌 Value of Cloud FinOps

Slide 70

Slide 70 text

Comment l’appliquer au monde Google Cloud ?

Slide 71

Slide 71 text

Des leviers disponibles Solutions de stockage Utiliser les différentes classes de stockage, designer le stockage Ressources préemptibles Utiliser la surcapacité de l'infrastructure Google Ressources orphelines / inutilisées Supprimer les ressources inutilisées (instances, disk, snapshots, IPs, etc.) Planiﬁcation Allumer / éteindre les ressources en fonction de leur plage d'utilisation Redimensionnement Choisir les bons types d’instances de l’utilisation réelle du système Engagement de ressources Engagement en matière de consommation de services & campagne globale de réduction Architecture Revoir l'architecture pour utiliser les services les plus efﬁcaces Optimisation BigQuery Analysis Optimisation des coûts des requêtes

Slide 72

Slide 72 text

No content

Slide 73

Slide 73 text

Oui d’accord et ?

Slide 74

Slide 74 text

Exemple 1 : Firebase

Slide 75

Slide 75 text

No content

Slide 76

Slide 76 text

No content

Slide 77

Slide 77 text

Exemple 2 : GKE

Slide 78

Slide 78 text

No content

Slide 79

Slide 79 text

No content

Slide 80

Slide 80 text

🆕 GKE Enterprise annoncé à Next

Slide 81

Slide 81 text

Exemple 3 : CUD

Slide 82

Slide 82 text

💡 Committed Use Discounts (CUDs) Spend-based CUDs Exemple: $50/hour spend in Cloud SQL (PgSQL) dans us-central1 Services pris en charge : Cloud SQL, Cloud Spanner, Cloud Run, Google Cloud VMware Engine, Google Kubernetes Engine (Mode Autopilot Resource-based CUDs Ex: 50 vCPU pour N2D dans us-central1 Services pris en charge : Compute Engine, Dataproc, Google Kubernetes Engine (Standard)

Slide 83

Slide 83 text

No content

Slide 84

Slide 84 text

Réserver un engagement de 3 ans pour économiser $164,160 sur ce projet

Slide 85

Slide 85 text

No content

Slide 86

Slide 86 text

Exemple 4 : Cloud Native Dev

Slide 87

Slide 87 text

No content

Slide 88

Slide 88 text

Développer en respectant les Cloud Patterns

Slide 89

Slide 89 text

Conclusion

Slide 90

Slide 90 text

No content

Slide 91

Slide 91 text

● 👍 Un sujet tendance avec de vrais concepts ● 🔐 Démarche essentielle comme le SRE et la Sécurité ● 💪 Une culture “FinOps” à diffuser ○ Autoscaling de 0 à N – par env (hors-prod / prod) ○ Respect de 12-Factors côté dev ○ Profiter au maximum du pricing model du Serverless ○ Choisir le bon outil pour faire la bonne chose ○ Observer, mesurer et maîtriser son architecture ○ Savoir quand se “commit” et sur quelle durée Les points à retenir

Slide 92

Slide 92 text

🚀 Next

Slide 93

Slide 93 text

💚 #GreenIT #GreenOps

Slide 94

Slide 94 text

🌱 Carbon Footprint

Slide 95

Slide 95 text

https:/ /greensoftware.foundation

Slide 96

Slide 96 text

🙌 Merci ! jlandure.dev @jlandure Introduction au FinOps avec Google Cloud ☁