Finish renaming ostester/openstack_tester to dizzy#45
Merged
Conversation
… to dizzy Complete the dizzy rebrand for the local OTEL smoke stack: the OTel instrument names (openstack_tester.* -> dizzy.*, and their derived Prometheus families), the kind cluster/namespace (ostester-otel -> dizzy-otel), and the Grafana dashboard UIDs/titles/queries. The earlier service.name rename deliberately left these metric families alone to avoid breaking in-flight dashboards; this finishes that cleanup now that the smoke stack itself is being re-provisioned. Assisted-by: Claude:claude-sonnet-5 Signed-off-by: Christian Berendt <berendt@b42labs.com>
Every resource the tool creates in OpenStack (Neutron, Cinder, Keystone) was named with an ostester-<runID>-<logical> prefix and tagged/metadata'd ostester:run=<id> / ostester:type=<kind> for cleanup discovery. Rename both to dizzy- / dizzy:run / dizzy:type throughout the client, cleanup, and executor packages, their tests, the golden report fixtures, and the remaining README sections (Neutron/Cinder/Keystone naming & cleanup docs). Also catches a stray openstack_tester.* metric-name reference in internal/neutron/telemetry_test.go missed by the OTEL rename. Note: this changes what a --reclaim-orphans sweep or monitor cleanup matches on, so resources already tagged under the old ostester-* convention will no longer be found by a cloud-wide sweep after this lands. Assisted-by: Claude:claude-sonnet-5 Signed-off-by: Christian Berendt <berendt@b42labs.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
openstack_tester.*->dizzy.*) and their derived Prometheus families, plus the kind cluster/namespace (ostester-otel->dizzy-otel) and Grafana dashboard UIDs/titles/queries. The earlier service.name rename deliberately left these alone to avoid breaking in-flight dashboards; this finishes that cleanup.ostester-<runID>-<logical>names andostester:run=<id>/ostester:type=<kind>tags/metadata becomedizzy-*/dizzy:run/dizzy:typeacross the Neutron/Cinder/Keystone client, cleanup, and executor packages, their tests, and the golden report fixtures.openstack_tester.*reference ininternal/neutron/telemetry_test.gomissed by the OTEL rename.Breaking note: resources already tagged under the old
ostester-*convention will no longer be found by a--reclaim-orphanssweep or monitor cleanup after this lands — any such leftovers need a manual one-time cleanup.Test plan
go build ./...go test ./...gofmt -lclean on touched filesmake otel-up/make testbed-monitor/make otel-grafanaagainst the local kind stack to confirm the renamed cluster/namespace/dashboards come up end to end