[openstack/archer] Refactor Archer network agent config and harden SLO alert - #12490
Merged
Conversation
notandy
force-pushed
the
archer-linuxbridge-agent-config
branch
from
August 6, 2026 11:02
843d11e to
87f200f
Compare
notandy
force-pushed
the
archer-linuxbridge-agent-config
branch
from
August 6, 2026 16:51
87f200f to
26d070d
Compare
notandy
changed the title
ronchi-oss
approved these changes
Aug 7, 2026
m-kratochvil
approved these changes
Aug 7, 2026
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
3 participants
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.
Refactors Archer's network-agent chart wiring around the embedded Neutron linuxbridge agent and removes the old CP seed path. Adds dedicated linuxbridge secrets/config, reduces noisy Neutron logger output, and adjusts the sidecar capability set so privsep can start successfully.
Also replaces the single-window
archer-slo-error-budget-burnalert with multi-window, multi-burn-rate alerts (fast 14.4x on 1h/5m, slow 6x on 6h/30m). The old alert fired on a single 5xx because a lone error stays in the 1h rate() window for a full hour; requiring a short window to also be hot means the alert clears as soon as errors stop.