tally-openstack-simulator

command
v0.6.0 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Oct 8, 2026 License: Apache-2.0 Imports: 11 Imported by: 0

Documentation

Overview

Command tally-openstack-simulator publishes one simulated month of OpenStack notifications.

The run subcommand generates the month from --seed and --period and publishes it onto the broker TALLY_SIM_AMQP_URL names, at --factor virtual seconds per wall second. With --out it writes the month to notifications.jsonl, events.jsonl and oracle.json instead, and to held-back.jsonl beside them when a switch holds notifications back; with both it does both. With --faults it turns fault switches on, each of which changes what the bus carries and never the month the oracle states; the run help names the six. With --register-projects the run registers the month's tenants, its two Gardener projects and their infrastructure_tenant relations with the Reporting API TALLY_SIM_REPORTING_URL names before it writes or publishes anything. The replay subcommand publishes a notifications.jsonl an earlier run wrote, which puts the same month on a bus again without the generator behind it. The compare subcommand reads the oracle a run wrote, an engine export of the month and the pricing model the run rated with, and lists every resource whose metered intervals or quantities differ from the oracle; it exits 1 when anything differs.

A run pushes the month's traffic counters and inventory gauges to the OTLP/HTTP endpoint TALLY_SIM_OTLP_URL names when it is set, on the same clock the notifications go out under and on the --metrics-interval grid, and it serves the inventory on GET /metrics of the control listener unless TALLY_METRICS_ENABLED is false. A replay does neither: a recorded file holds notifications and no oracle to read a metric off.

The control endpoint on TALLY_SIM_HTTP_PORT changes the factor while a run publishes, so a month that is going out too slowly is sped up without being started over. POST /release on it publishes the notifications a run with the held-back fault switch kept back.

SIGINT and SIGTERM stop a run cleanly: what went out stays out, and the process ends with exit status 0. Every other failure exits 1.

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL