Implement Openconfig NTP provider - #517
Draft
adamtrizuljak-sap wants to merge 1 commit into
Draft
Conversation
Signed-off-by: Adam Trizuljak <adam.trizuljak@sap.com>
Merging this branch will decrease overall coverage
Coverage by fileChanged files (no unit tests)
Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code. |
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.
Work in progress
Add OpenConfig provider implementation for the NTP resource (
internal/provider/openconfig/ntp.go) and a gnmi testdata file (test/gnmi/testdata/openconfig/ntp.txt).Cisco vs Openconfig compatibility issue
NTPSpecdefines theSourceInterfaceNamefield https://github.com/ironcore-dev/network-operator/blob/main/api/core/v1alpha1/ntp_types.go#L36. Openconfig has something similarsource-addresshttps://openconfig.net/projects/models/schemadocs/yangdoc/openconfig-system.html#system-ntp-servers-server-config-source-addressA way to handle it would be to look up the interface given by SourceInterfaceName , get its IPv4 address and put it into
source-address. Does it make sense? Do you usually do such operations, or do you keep the provider code clean from reading any additional k8s resources?Other way would be to just ignore
SourceInterfaceNameand not pass it into the Openconfig struct, or even throw aapistatus.FieldViolationsaying that it's unsupportedProposed solution
Discussed with @nikatza and @rgildein
NTPSpec.SourceInterfaceNameas optionalNTPSpec.SourceAddressSourceInterfaceNameis definedSince both fields are optional, the change will be backwards-compatible with the previous NTPSpec and the generated custom resources.