Reduce Stemcell Distribution Egress Costs via Cloudflare CDN

Abierto
#676 4 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
google-cloud

Línea de trabajo

Comienza revisando la migración relacionada en cloudfoundry/community#926 y las referencias de automatización de releases a bosh-io/stemcells-index y a la UI/API de bosh.io. Define el trabajo de infraestructura, mapeo de URL, despliegue gradual y compatibilidad hacia atrás a lo largo de las fases indicadas; se considera terminado cuando se cumplen los criterios de éxito sin romper las URL de GCS existentes.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Summary

Stemcell downloads from https://storage.googleapis.com/bosh-aws-light-stemcells/...
(and equivalent GCS buckets for other IaaS) generate significant GCP egress costs (~2K $ per month).
We can drastically reduce these costs by fronting the GCS buckets with Cloudflare CDN under a community-owned domain such as stemcells.cloudfoundry.org.

Related migration: cloudfoundry/community#926

Motivation

  • Stemcells are immutable, versioned, large artifacts — ideal CDN cache candidates.
  • Current GCS egress is billed at ~$0.12/GB; Cloudflare egress to end users is free.
  • A single cached version is fetched from origin once, then served from edge globally.
  • Improves download speed and reliability for the community.

Proposed Architecture

User → https://stemcells.cloudfoundry.org/<iaas>/<version>/<file>.tgz
         │
         └── Cloudflare CDN (cached at edge)
                │  (cache miss only)
                └── storage.googleapis.com/bosh-<iaas>-light-stemcells/...

Example URL mapping:

  • Before: https://storage.googleapis.com/bosh-aws-light-stemcells/1.425/light-bosh-stemcell-1.425-aws-xen-hvm-ubuntu-noble.tgz
  • After: https://stemcells.cloudfoundry.org/aws/1.425/light-bosh-stemcell-1.425-aws-xen-hvm-ubuntu-noble.tgz

Action Items

Phase 1 — Infrastructure setup
  • Create Cloudflare zone (or subdomain delegation) for stemcells.cloudfoundry.org
  • Verify stemcell file sizes vs Cloudflare cache limits (Free 512MB / Pro 1GB / Business 5GB / Enterprise unlimited with Cache Reserve)
  • Decide Cloudflare plan (or apply for Cloudflare's open-source / OSS sponsorship program)
  • Ensure GCS buckets (bosh-aws-light-stemcells, bosh-gce-light-stemcells, bosh-azure-light-stemcells, etc.) have allUsers:objectViewer
Phase 2 — Cloudflare configuration
  • Add CNAME stemcells.cloudfoundry.org → storage.googleapis.com (proxied)
  • Add Origin Rule: override Host header to storage.googleapis.com
  • Add URL Rewrite rule mapping /<iaas>/<path> → /bosh-<iaas>-light-stemcells/<path>
  • Configure Cache Rule: Edge TTL = 1 month, Browser TTL = 1 day, cache eligible
  • Enable Tiered Cache for better hit ratio
  • (Optional) Enable Cache Reserve for large objects
Phase 3 — Release automation integration
  • Update stemcell publishing pipeline (bosh-io / stemcells-index and equivalents) to:
    • Continue uploading to GCS as origin of truth
    • Issue a curl -I warm-up request after upload to pre-fill Cloudflare cache
    • Publish CDN URL (stemcells.cloudfoundry.org/...) in release metadata / bosh.io index
  • Update bosh.io UI/API to point downloads at CDN URL
  • Keep GCS URLs functional for backward compatibility (no breaking change)
Phase 4 — Monitoring & rollout
  • Add Cloudflare Analytics dashboard (cache hit ratio, bandwidth saved)
  • Compare GCP egress bill before/after (1 month baseline)
  • Document new URL pattern in BOSH / stemcell docs
  • Announce on cloudfoundry-dev mailing list & Slack #bosh
Phase 5 — Optional follow-up
  • Evaluate full migration of origin to Cloudflare R2 (zero egress, no large-file cache limits) if cost savings justify operational change

Success Criteria

  • >90% cache hit ratio after warm-up
  • Measurable reduction in GCP egress costs (target: >70%)
  • No regressions in stemcell download reliability
  • Zero breakage for existing consumers using old GCS URLs
Lenguaje dominante
Ruby
Estrellas
52
Forks
124
Merge medio
1 d 2 h
PR fusionados (30 d)
23

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de cloudfoundry/bosh-linux-stemcell-builder

Todos los issues de cloudfoundry/bosh-linux-stemcell-builder

Issues similares

Más issues de Ruby

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.