cost: automate the cost snapshot and refresh the worked example #469
Etiketter
Inga etiketter
area/backups
area/ci
area/control-panel
area/identity
area/infra
area/observability
area/payments
area/security
area/storage
area/web
blocked
needs-info
needs-triage
ready-for-implementation
type
bug
type
chore
type
docs
type
epic
type
feature
type
task
wontfix
Ingen milstolpe
Inget projekt
Inga tilldelade
1 deltagare
Notiser
Förfallodatum
Inget förfallodatum satt.
Beroenden
Inga beroenden satta
Referens
bitborg/bitborg-infra#469
Läser in…
Hänvisa till i nytt ärende
Ingen beskrivning angiven.
Ta bort grenen "%!s()"
Borttagning av en gren är permanent. Även om den borttagna grenen kan fortsätta existera en kort tid innan den faktiskt tas bort, kan det INTE ångras i de flesta fall. Vill du fortsätta?
cost/data/samples.jsonlholds three records from 2026-06-10 describing one VM and one 40 GB volume. Today's declared estate is two VMs, five volumes and two floating IPs.cost/README.mdstill uses the old single-node example, andcost/prices.ymlwas last verified against Bahnhof's calculator on 2026-07-12.Schedule
scripts/openstack-cost.py snapshotfrom the operator machine (the README already suggests a cron), refresh the README example to the current shape, and re-verify the prices.