vRack - 3-AZ Failover priorities#9365
Open
SlimJ4 wants to merge 8 commits into
Open
Conversation
Added a section about managing 3-AZ failover priorities, detailing the benefits of doing so and the ways to manage these new mechanics.
SlimJ4
added
the
Offer: Network
jslocinski
reviewed
May 7, 2026
Fixed incorrect button naming following access to a staging environment.
- Fix UI slot inconsistency in ipv6 EN-GB ("First failover" → "Secondary Zone")
- Remove duplicate primary callout in ip-block FR-FR
- Fix "au dessus" → "au-dessus" (compound preposition) in both FR files
- FR: "Tableau de bord" → "espace client" (CP terminology), inside the new section
- EN/FR rewording: tighter phrasing in the new section (Validate → Confirm, drop spatial filler, "expose pour" → "attribue à", etc.)
- Bump `updated:` to 2026-05-26 in all 4 files — this update must not be merged before that date
Suggestion (not applied — needs verification against the live CP / Manager sidebar):
The new section uses two naming styles for the same AZ priority slots within the same guide:
EN (ipv6 + ip-block):
- Prose description: "Primary Availability Zone" (long form)
- Panel slot list: "Primary Zone, Secondary Zone, Last resort Zone" (short form)
FR (ipv6 + ip-block):
- Prose description: "Zone de disponibilité principale", "Zone de disponibilité secondaire", "Zone de dernier recours"
- Panel slot list: "Zone principale, Zone secondaire, Zone de dernier recours" (short form)
Both languages mix long-form labels in prose with short-form labels in the panel
slot list. Worth aligning them once the actual NM panel labels are confirmed:
either standardise on the short form everywhere (preferred — matches the UI),
or keep the long form in prose only where it clarifies the concept and use the
exact UI label in the panel-slot list. Same fix applies symmetrically to EN and
FR so the localisations stay in sync.
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.
What type of Pull Request is this?
Description
Added a section in Additional IPv4/6 for vRack guides, talking about managing 3-AZ failover priorities, detailing the benefits of doing so and the ways to manage these new mechanics.
Mandatory information
The translations in this Pull Request have been done using: