|
Post by ratagupt on Sept 7, 2021 11:19:31 GMT
Hi Team, Do we have any plan to add the interfaces for the backup and restore redfish configuration? We could have two ways: 1) Redfish provides a specific endpoint for back up and restore of the configuration with the links of the resource. Backup: -> Client will fire get request on the backup and restore services -> Gets the link of the resources where the backup is required -> Client will fire multiple GET request to the redfish endpoints. -> Save it at client side in the form of a file etc. Restore: -> Client parse this file and fire PATCH/POST request to update the redfish endpoints. eg: gerrit.openbmc-project.xyz/c/openbmc/docs/+/181632) We can create actions in manager schema Backup: parameters("Resource List") This function returns the json file. Restore: Parameters(Json File) Ratan
|
|
|
Post by dkodihalli on Sept 7, 2021 17:53:11 GMT
A potential issue I see with 1) is, there is an assumption that everything to be backed up is an exposed property in some Redfish schema. That may not always be the case.
|
|
|
Post by ratagupt on Sept 7, 2021 18:08:05 GMT
A potential issue I see with 1) is, there is an assumption that everything to be backed up is an exposed property in some Redfish schema. That may not always be the case. I am hoping you are mentioning that if some property is not exposed in standard redfish and it requires to be configurable/readable property then we can define the oem properties in respective redfish resources.
|
|
|
Post by ratagupt on Sept 10, 2021 4:13:43 GMT
Any inputs here? What is/should be the correct approach?
|
|
|
Post by mraineri on Sept 14, 2021 17:30:17 GMT
There is nothing today in Redfish that supports this and we don't have any guidance in this area. However, we're open to reviewing proposal for it. dkodihalli does raise a good point we'd need to be careful about though.
|
|