Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPBaselineHardwareManagement DNS settings may be reversed #37

Open
pjonason opened this issue Jan 31, 2022 · 2 comments
Open

OCPBaselineHardwareManagement DNS settings may be reversed #37

pjonason opened this issue Jan 31, 2022 · 2 comments
Assignees
Labels
Approved Approved - can be assigned profile-hw_baseline

Comments

@pjonason
Copy link

Baseline profile, under the EthernetInterface resource, has

"NameServers": {
"ReadRequirement": "Recommended",
"ConditionalRequirements": [{
"SubordinateToResource": ["Manager", "EthernetInterfaceCollection"],
"ReadRequirement": "Mandatory",
"WriteRequirement": "Mandatory"
}]

and

"StaticNameServers": {
"ReadRequirement": "Recommended"
}

But according to the spec document pp. 402-403, and this forum discussion, it should be StaticNameServers that are writable, and NameServers should be read-only.

@jcleung5549
Copy link
Contributor

From the 'forum discussion'...

"Use the property StaticNameServers, which is read-write, to allow users to specify a set of name servers. The NameServers array contains the ones actually in use by the interface, which could be obtained via DHCP or from the StaticNameServers, depending on the interface configuration."

@jcleung5549
Copy link
Contributor

Propose change

"StaticNameServers": {
   "ReadRequirement": "Mandatory",
   "WriteRequirement": "Mandatory"
}

@jcleung5549 jcleung5549 added the Approved Approved - can be assigned label Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Approved Approved - can be assigned profile-hw_baseline
Projects
None yet
Development

No branches or pull requests

2 participants