A new parameter in HttpPushUriOptions for config update

vikrambreddy
Minnow

Posts: 6

A new parameter in HttpPushUriOptions for config update Feb 18, 2020 17:12:20 GMT

Quote

Post by vikrambreddy on Feb 18, 2020 17:12:20 GMT

We would need to have new parameter under "HttpPushUriOptions" object for specifying whether there needs to be a firmware configuration update along with when the firmware update is applied.
This parameter requirement is to be considered as similar as the existing "HttpPushUriApplyTime" object under "HttpPushUriOptions" which is used to specify the time at which the firmware update to be applied.

Most of the firmware targets (like BIOS etc.,) needs its firmware configuration also to be cleared or erased along with its firmware update. Currently the UpdateService schema doesn't specify and provide any object or parameter that can be used to pass this along with other firmware update attributes (like Applytime), also UpdateService schema doesn't provide any OEM parameter which OEM impelementers can make use of it for this purpose.

It needs to be as a boolean or string parameter such as "ClearConfig" under "HttpPushUriOptions" along with HttpPushUriApplyTime.

Please review this and let me know your feedback on this to include it in UpdateService Schema.

jautor
Administrator

Posts: 519

A new parameter in HttpPushUriOptions for config update Feb 19, 2020 5:38:29 GMT

Quote

Post by jautor on Feb 19, 2020 5:38:29 GMT

This doesn't appear to be a user "option" for most implementations - if the user settings are reset/altered due to a firmware update, the user has no choice in that matter. Rather it would be a side effect of an update. But as an option, this seems like an OEM setting.

And yes, the UpdateParameters definition was updated in the 2019.4 release (UpdateServce v1.8.0) to add the missing OEM object, so this can be accomplished with OEM data...

Jeff

vikrambreddy
Minnow

Posts: 6

A new parameter in HttpPushUriOptions for config update Feb 19, 2020 17:49:17 GMT

Quote

Post by vikrambreddy on Feb 19, 2020 17:49:17 GMT

Thanks for the reply, for BIOS firmware updates its a mandatory option that to be set to Yes or No (i.e. yes indicates to clear firmware config along with with firmware update). The firmware configurations that is referred here is not the user settings or user configurations, its firmware related configurations/settings that are specific to the platform HW which are allowed to be enhanced to a different configuration or to a different format from a particular firmware release so that it complies with the updated firmware. In BIOS terms its called NVRAM region configurations. This is common across several OEMs and which is predominantly used by all computing platform OEMs.
The user settings reset/update are dealt differently with other methods such as "FactoryDefaults or RestoreDefaults" etc., which resets the user configurations. Its not the same as firmware configurations.

So this requirement for having a standard property in the Schema to specify the "ClearConfig" parameter during firmware updates is a mandatory need for computing platform's.

I would request to review this requirement considering BIOS firmware as a common and generic component across all computing platforms. All the while we did have OEM specific utilities or interfaces that was supporting it, now that all OEMs are moving to redfish based firmware update support we need to have this as a standard parameter in Schema instead of having it as an OEM property.

Last Edit: Feb 19, 2020 17:50:36 GMT by vikrambreddy

jautor
Administrator

Posts: 519

A new parameter in HttpPushUriOptions for config update Feb 27, 2020 16:37:11 GMT

Quote

Post by jautor on Feb 27, 2020 16:37:11 GMT

Ah, I misunderstood where you were requesting this. For the standard we're recommending vendors move to the new Multipart Push Update standard method, and therefore we're not expecting to further enhance the HttpPushUriOptions (as we don't expect new implementations). So an OEM property is appropriate for solving this for existing implementations - especially since the mechanisms behind the "push" method were not expected to be standardized.

Jeff

mraineri
Administrator

Posts: 1,125

A new parameter in HttpPushUriOptions for config update Feb 28, 2020 14:14:15 GMT

Quote

Post by mraineri on Feb 28, 2020 14:14:15 GMT

However, if usage of the existing HttpPushUri property is needed, you should be able to add properties to the "Oem" object at the root level of the resource to add additional parameters not specified by "HttpPushUriOptions".