Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Introduction au FinOps avec Google Cloud @ Stat...

Introduction au FinOps avec Google Cloud @ Station F

Communication:
- https://www.linkedin.com/posts/googleforstartups-france_finops-activity-7166061839250886658-DS4T
- https://www.linkedin.com/posts/zenika_finops-zenika-codetheworld-activity-7166371453364342785-LU-p
- https://www.linkedin.com/posts/jlandure_finops-tech-activity-7169275570621517825-RIFE

Comment assurer une croissance durable de vos coûts Cloud ?

"FinOps" est un nouveau mot-clé apparu courant 2020 qui ne cesse de prendre de l'ampleur sur Linkedin au côtés de "Cloud" ou "SRE".

Mais c'est quoi le FinOps? (D'ailleurs, on dit peut-être la FinOps en 🇫🇷 😅 ?) Est-ce lié au fait que les devs peuvent tout déployer n'importe comment sans regarder le coût engendré ? Est-ce une nouvelle organisation dans l'entreprise ? Et toi, peux-tu devenir certifié "FinOps" ? Quelles sont les mécanismes disponibles en standard avec Google Cloud ? Peut-on facilement profiter de ces optimisations ?

En retraçant le chemin du Cloud et en étudiant la FinOps Foundation, fondation fille de la Linux Foundation, découvre ce qui se cache derrière ce buzzword! 💸

Julien Landuré

February 28, 2024
Tweet

More Decks by Julien Landuré

Other Decks in Programming

Transcript

  1. Google Cloud Team at Station F Mathilde Bachy Cloud Architect

    Program manager Mael Galite App Specialist Office Hours Daria Vlasova Cloud Architect Office Hours Tony Carnal Cloud Architect Office Hours Louis Soboul Sales & Communication
  2. Start Google Cloud & Firebase fundamentals Google Cloud Program at

    Station F Grow Office Hours & Workshops Scale Startup Credit Programs Google Cloud Platform • Monthly training with • Free tier version • $300 free trial for 90 days Firebase • Free tier version Slack: #google-cloud Office Hours: every month • Advisory on Google Cloud solutions • Architecture review Technical talks 💸Self-funded startups Up to $2,000 to use over 2 years 💸Pre-seed to Series A startups Up to $200,000 credits over 2 years for GCP & Firebase! https://cloud.google.com/startup
  3. 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 ?
  4. 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
  5. 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 Efficient Deployment ~months Not portable Low utilization Deployment ~days (mins) Hypervisor specific Low isolation, Tied to OS
  6. 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 Efficient Deployment ~months Not portable Low utilization Deployment ~days (mins) Hypervisor specific Low isolation, Tied to OS Master Nodes
  7. 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?
  8. 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
  9. 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
  10. 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.
  11. 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.
  12. 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
  13. Serverless Deploy and scale applications fast and securely in a

    fully managed environment No Infra Management Auto-scaling
  14. Google Cloud Pricing Calculator Search for product you are interested

    in Estimate Instances cloud.google.com/products/calculator
  15. 📝 Definition 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.
  16. DevOps ❌ a standard ❌ a certification ❌ a goal

    ✅ a culture ✅ a philosophy ✅ a journey
  17. 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
  18. Cloud FinOps is an evolving cloud financial management discipline and

    cultural practice that: to collaborate on data-driven spending decisions enables organizations to get maximum business value by helping engineering, finance and business teams FinOps.org FinOps Principles by FinOps Foundation - FinOps Foundation under the ccby4.0 license
  19. 65 FinOps Principles by FinOps Foundation - FinOps Foundation under

    the ccby4.0 license 🎓 Training & Certification
  20. 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
  21. 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.) Planification 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 efficaces Optimisation BigQuery Analysis Optimisation des coûts des requêtes
  22. 💡 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)
  23. • 👍 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