|
Post by asmithakr on Mar 22, 2024 7:52:15 GMT
Current Design: CollectDiagnosticData method is defined in LogService schema and the parameters to this method are defined in LogEntry schema: DiagnosticDataType, OEMDiagnosticDataType, Password, TargetURI, TransferProtocol, UserName.
Requirement: For user-initiated dumps, there is an IBM-specific requirement that gets the resource name and password from the user to collect diagnostic data for any particular resource.
Proposal: In order to meet this requirement, there can be a property called "AdditionalArgs" or "OemAdditionalArgs" that is a list of additional parameters to this method. The redfish request for user-initiated dump looks like the below with the proposed property: ``` POST https://${bmc}/redfish/v1/Managers/bmc/LogServices/Dump/Actions/LogService.CollectDiagnosticData -d '{"DiagnosticDataType":"OEM", "OEMDiagnosticDataType":"<DiagnosticDataType>", "OemAdditionalArgs":["arg1", "arg2", ..., "argn"]}' ```
Things that needs clarification: * Can this list have multiple data types, although current requirement is for strings? * If it can be extended to DiagnosticDataType other than OEM, can we rename it as "AdditionalArgs"?
|
|
|
Post by mraineri on Mar 24, 2024 19:50:23 GMT
If you're getting into that level of control for collecting diagnostic data, then you should be making an OEM action for supplying all of the details you need. It looks like you're outgrowing the simplistic intent of having "OEMDiagnosticDataType" as an easy-button way to specify vendor-specific diagnostic data. I'd be very hesitant on adding more OEM parameters to standard actions at this time.
|
|
|
Post by asmithakr on Mar 25, 2024 18:43:29 GMT
I Understand.
The reason for this proposal is, there was a requirement where a user had to collect diagnostic data for a particular resource and needs to provide a password to authenticate the user to access that resource. Just like we have "OEMDiagnosticDataType", if we have one other property, it might look better to have followed the Redfish standard. And since this will be a list, I suspect if there will be any more requirement for this collectDiagnosticData action. This property can be put as an optional parameter.
Your thoughts, please?
|
|