Support migration windows for BIND9 - #1428
Open
beagles wants to merge 4 commits into
Open
Conversation
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
beagles
force-pushed
the
designate-staged-migration
branch
2 times, most recently
from
June 30, 2026 12:11
47dadc6 to
70fa108
Compare
beagles
marked this pull request as ready for review
June 30, 2026 12:12
|
Build failed (check pipeline). Post ✔️ noop SUCCESS in 0s |
jistr
reviewed
Jul 2, 2026
jistr
left a comment
jistr
left a comment
Contributor
There was a problem hiding this comment.
LGTM, adding Katie for docs
klgill
requested changes
Jul 2, 2026
klgill
left a comment
klgill
left a comment
Contributor
There was a problem hiding this comment.
Let me know if you have any questions on my edits. Thanks!
The IPs for the BIND9 servers may be in external registries or in other DNS configuration for zone delegation via glue records. This change is part of a series to verify the steps to maintaining records in both the RHOSO system and the legacy system to allow a staged migration of DNS infrastructure. Documentation is enhanced to: - Update the procedure for maintaining a migration window with legacy BIND9 servers, including a reference to additional steps after the standard adoption. - Add tasks to configure and enable the Designate service, including creating a LoadBalancer service for mDNS zone transfers. - Refine task names for clarity and removed unnecessary steps related to external binds secret verification. - Improve the patch file creation process for Designate CR to include necessary configurations for legacy BIND9 integration. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
beagles
force-pushed
the
designate-staged-migration
branch
from
July 14, 2026 11:10
b4162ac to
6d67b8f
Compare
|
Build failed (check pipeline). Post ✔️ noop SUCCESS in 0s |
The IPs for the BIND9 servers may be in external registries or in other DNS configuration for zone delegation via glue records. This change is part of a series to verify the steps to maintaining records in both the RHOSO system and the legacy system to allow a staged migration of DNS infrastructure. Documentation is enhanced to: - Update the procedure for maintaining a migration window with legacy BIND9 servers, including a reference to additional steps after the standard adoption. - Add tasks to configure and enable the Designate service, including creating a LoadBalancer service for mDNS zone transfers. - Refine task names for clarity and removed unnecessary steps related to external binds secret verification. - Improve the patch file creation process for Designate CR to include necessary configurations for legacy BIND9 integration. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Move "Maintaining a migration window with legacy BIND9 servers" and "Completing the BIND9 migration" out of proc_adopting-the-dns-service.adoc and into their own PROCEDURE modules, following the modular-docs procedure template instead of embedding them as sub-headings in another procedure. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…rification test - Fix 'desginate' typo in systemctl restart command in migration-window doc - Use plural CRD name (designates.designate.openstack.org) in docs to match tests - Add missing -i flag to sed command in designate_external_binds.yaml - Add RNDC connectivity verification task to designate_external_migrate.yaml Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
klgill
requested changes
Jul 27, 2026
klgill
left a comment
klgill
left a comment
Contributor
There was a problem hiding this comment.
Thanks for restructuring. I fixed some formatting issues and updated the short description of one of the procedures.
| = Maintaining a migration window with legacy BIND9 servers | ||
|
|
||
| [role="_abstract"] | ||
| A complete immediate switchover of all DNS servers to {rhos_long} requires all DNS clients to be updated with the new addresses of the DNS servers. This may be DNS registry entries, `glue records` in other DNS zone tables or configuration in OpenStack servers. In deployments where this cannot be done immediately, this procedure configures the existing DNS servers to be used and updated until all references to them can be migrated to the {rhos_long} DNS services. |
Contributor
There was a problem hiding this comment.
Suggested change
| A complete immediate switchover of all DNS servers to {rhos_long} requires all DNS clients to be updated with the new addresses of the DNS servers. This may be DNS registry entries, `glue records` in other DNS zone tables or configuration in OpenStack servers. In deployments where this cannot be done immediately, this procedure configures the existing DNS servers to be used and updated until all references to them can be migrated to the {rhos_long} DNS services. | |
| Transition to {rhos_long} DNS services gradually when a complete, immediate switchover isn't possible. This keeps existing DNS servers active and updated while you migrate external references, registry entries, and client configurations over time. |
| [role="_abstract"] | ||
| A complete immediate switchover of all DNS servers to {rhos_long} requires all DNS clients to be updated with the new addresses of the DNS servers. This may be DNS registry entries, `glue records` in other DNS zone tables or configuration in OpenStack servers. In deployments where this cannot be done immediately, this procedure configures the existing DNS servers to be used and updated until all references to them can be migrated to the {rhos_long} DNS services. | ||
|
|
||
| If your {rhos_prev_long} deployment uses BIND9 servers that should continue serving DNS during adoption, follow this procedure after completing the standard {dns_service} adoption. The designate worker sends RNDC commands and DNS NOTIFY messages to the legacy servers, which pull zone data from the mDNS service through AXFR on port 5354. |
Contributor
There was a problem hiding this comment.
Suggested change
| If your {rhos_prev_long} deployment uses BIND9 servers that should continue serving DNS during adoption, follow this procedure after completing the standard {dns_service} adoption. The designate worker sends RNDC commands and DNS NOTIFY messages to the legacy servers, which pull zone data from the mDNS service through AXFR on port 5354. | |
| If your {rhos_prev_long} deployment uses BIND9 servers that need to stay active during adoption, follow these steps after completing the standard {dns_service} adoption. The Designate worker sends RNDC commands and DNS NOTIFY messages to your legacy servers, which then fetch zone updates from the mDNS service via AXFR on port 5354. |
| fi | ||
| ---- | ||
| + | ||
| where: |
Contributor
There was a problem hiding this comment.
Suggested change
| where: | |
| where: | |
| ---- | ||
| + | ||
| where: | ||
| `CONTROLLER1_SSH`, `CONTROLLER2_SSH`, and `CONTROLLER3_SSH`:: |
Contributor
There was a problem hiding this comment.
Suggested change
| `CONTROLLER1_SSH`, `CONTROLLER2_SSH`, and `CONTROLLER3_SSH`:: | |
| `CONTROLLER1_SSH`, `CONTROLLER2_SSH`, and `CONTROLLER3_SSH`:: |
| ==== | ||
|
|
||
| + | ||
| Reload the BIND9 configuration: |
Contributor
There was a problem hiding this comment.
Suggested change
| Reload the BIND9 configuration: | |
| . Reload the BIND9 configuration: |
| The `sed` commands in the shell script example are directed at default deployments. If customizations are made to the deployment, either modify these commands or perform the modifications directly. | ||
| ==== | ||
|
|
||
| + |
|
|
||
| . Create a LoadBalancer service to expose the mDNS service on the internalapi | ||
| network so that the legacy BIND9 servers can perform AXFR zone transfers: | ||
| + |
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.
The IPs for the BIND9 servers may be in external registries or in other DNS configuration for zone delegation via glue records.
This change is part of a series to verify the steps to maintaining records in both the RHOSO system and the legacy system to allow a staged migration of DNS infrastructure.
Documentation is enhanced to: