MTL-1980 - Configure a bonded HSN connection on an NCN #300
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 and Scope
Ansible role to configure a bonded HSN interface on NCNs.
This role is not enabled by default as it requires values that have to be supplied by the Slingshot administrator.
Issues and Related PRs
Testing
Tested on:
surtur
Test description:
Rebuilt ncn-w005 with Playbook enabled with the following settings
Verified bond was configured as expected.
Rebooted ncn-w005, verified bond came up before CFS ran and that the Ansible playbook didn't perform any unnecessary configuration actions.
Risks and Mitigations
Pull Request Checklist