Depreciate PATCH support for HostName at NetworkProtocol

[raviteja bailapudi]

Hi Gunnar

yes. there was an issue opened for the same
https://github.com/openbmc/bmcweb/issues/44
I remember adding  patch support to fix this issue.. I think we had
discussed about hostname property in
ethernet vs network protocol , it has been long back don't remember exactly.

Thanks
Raviteja

On Mon, Dec 14, 2020 at 11:57 PM Gunnar Mills <gmills at linux.vnet.ibm.com>
wrote:

> Hi Ravi,
>
> I believe you implemented PATCH support for HostName at
> /redfish/v1/Managers/bmc/NetworkProtocol
>
>
> https://github.com/openbmc/bmcweb/commit/501be32b4230dfa2730467985c6306f15fe7af61
>
> Looking for some background around the commit. Do you know why this was
> added? Do you know if any clients are PATCHing HostName here?
>
> HostName at /redfish/v1/Managers/bmc/NetworkProtocol is a read-only
> property and PATCH support here violates the Redfish spec.
>
> HostName at /redfish/v1/Managers/bmc/EthernetInterfaces/<str> is a
> read-write property and can be PATCHed. This is what webui-vue uses.
>
> Still discussion on how we would depreciate this PATCH support on
> https://gerrit.openbmc-project.xyz/c/openbmc/bmcweb/+/38475
>
> Does anyone know of a client PATCHing HostName at the NetworkProtocol
> resource?
>
> https://redfish.dmtf.org/schemas/v1/ManagerNetworkProtocol.v1_6_1.json
> https://redfish.dmtf.org/schemas/v1/EthernetInterface.v1_6_2.json
>
>
> Thanks,
> Gunnar
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20201215/cc09ffc9/attachment.htm>