Repository navigation
Free-form hostname support for OpenCHAMI DNS configuration - #5806
Draft
VrindaMarwah wants to merge 1 commit into
Draft
VrindaMarwah wants to merge 1 commit into
VrindaMarwah wants to merge 1 commit into
Conversation
Signed-off-by: Vrinda_Marwah <Vrinda.Marwah@dell.com>
This branch has not been deployed
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
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.
Description of the Solution
This PR adds support for human-readable custom hostnames (e.g.,
gpu-worker-01,login-server) alongside the standard nid format (nid001-nid999) whendns_enabled: truein orchestrator_config.yml. The system auto-detects the hostname format from the PXE mapping file and configures DHCP (CoreDHCP) and DNS (CoreDNS) accordingly, following the OpenCHAMI custom hostname management approach to keep DHCP, DNS, and cloud-init in agreement.Related Issue
Changes
Documentation (
src/orchestrator/docs/)Configuration (
src/orchestrator/input/orchestrator_config.yml)Validation (
src/orchestrator/plugins/module_utils/orchestrator_validation/)OpenCHAMI Deployment (
src/orchestrator/roles/deploy_openchami/)Files Changed
src/orchestrator/docs/contracts/input-contract.mdsrc/orchestrator/docs/custom-hostnames.mdsrc/orchestrator/input/orchestrator_config.ymlsrc/orchestrator/plugins/module_utils/orchestrator_validation/messages/orchestrator_messages.pysrc/orchestrator/plugins/module_utils/orchestrator_validation/validators/pxe_mapping_validator.pysrc/orchestrator/roles/deploy_openchami/tasks/configs/ochami.ymlsrc/orchestrator/roles/deploy_openchami/tasks/refresh_openchami_configs.ymlsrc/orchestrator/roles/deploy_openchami/templates/coredhcp/coredhcp.yaml.j2src/orchestrator/roles/deploy_openchami/templates/coredns/Corefile.j2Testing
journalctl -u dhclient, query DNS withdig @<oim-ip> <hostname>.<domain> A +short, and confirm hostname is set on the node after cloud-init.Backward Compatibility