NameServers in EthernetInterface.v1_5_0 | Redfish Specification Forum

AMI_Mani
Tuna

AMI

Posts: 175

NameServers in EthernetInterface.v1_5_0 Apr 9, 2020 11:41:21 GMT

Quote

Post by AMI_Mani on Apr 9, 2020 11:41:21 GMT

Hi,
As per EthernetInterface.v1_5_0, NameServers attribute is readonly

"NameServers": {
"description": "This represents DNS name servers that are currently in use on this interface.",
"items": {
"type": "string"
},
"longDescription": "The value of this property shall be the DNS name servers used on this interface.",
"readonly": true,
"type": "array"
}

Our service supports modifying the value, can we make it read-write? I'm seeing clause in Redfish specification mentioning

"A service may implement a writable property as read-only."

But not mentioned about changing read-only to Writable. Can we modify writable in our service or needs to use OEM attribute for supporting write operation which will duplicate NameServers attribute?

Thanks,
Mani

jautor
Administrator

Posts: 502

NameServers in EthernetInterface.v1_5_0 Apr 14, 2020 4:22:35 GMT

Quote

Post by jautor on Apr 14, 2020 4:22:35 GMT

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.

It may be worth adding some language to the property descriptions to better explain the tie between them.

Jeff

Last Edit: Apr 14, 2020 4:23:39 GMT by jautor

jautor
Administrator

Posts: 502

NameServers in EthernetInterface.v1_5_0 Apr 14, 2020 4:31:27 GMT

Quote

Post by jautor on Apr 14, 2020 4:31:27 GMT

Apr 9, 2020 11:41:21 GMT AMI_Mani said:

"A service may implement a writable property as read-only."

But not mentioned about changing read-only to Writable. Can we modify writable in our service or needs to use OEM attribute for supporting write operation which will duplicate NameServers attribute?

Thanks,
Mani

No, a property marked as read-only in the schema cannot be made read-write by an implementation - that would be a violation of the specification.

But as you have done here, the correct method to handle any desire to provide read-write behavior on a read-only property in the standard schema is to ask us. There may already be a solution (as was the case here), or it may be a use case that we overlooked. In that case, we can revise schema to add read-write capabilities without breaking compatibility - as long as the functionality is appropriate and not solely an single OEM's function. The DMTF has a very streamlined process to publish standards - a simple revision to schema will almost certainly get picked up in the next release (we do 3-4 releases per year) - and can generally happen in less than 60 days.

Jeff

AMI_Mani
Tuna

AMI

Posts: 175

NameServers in EthernetInterface.v1_5_0 Apr 14, 2020 17:42:59 GMT

Quote

Post by AMI_Mani on Apr 14, 2020 17:42:59 GMT

Hi Jeff,
Thanks for details
I will use StaticNameServers which can solve my purpose.
I will never change read-only to write in our implementation which can break schema as you suggested.
If any requirements come for changing read-only to write, I will raise a thread in forum and wait for schema to have that updated

Thanks,
Mani