|
Post by sunitha on Feb 14, 2019 9:51:25 GMT
Hi,
I have a use case - Redfish server needs to store some files which are to be managed by the redfish client. And the client should get the file operation interfaces to those files. Is there any standard way of doing the file read-write (complete & partial as well) ?
|
|
|
Post by sunitha on Dec 11, 2017 5:08:49 GMT
Sure. I will work on that ! Thanks a lot
|
|
|
Post by sunitha on Dec 8, 2017 10:25:49 GMT
Thank you for the clarification. As per the schema Event.1.2.0.json, for an event the MessageId is a mandatory parameter for an EventRecord. So if i don't describe an OEM for each record and just provide the eventId and other related descriptions, it will make my server in-complient to the DMTF standards.
My next question is - Is it possible to remove this MessageId from the mandatory parameter from this json until the standard registries are available.
|
|
|
Post by sunitha on Dec 5, 2017 6:35:28 GMT
Hi, I was mapping my product's asynchronous events to the message ids at the DSP8011_2017. I found some of the async message mappings but i need some inputs on the below use cases which my product has. Say, the firmware is code updated. The action can be either successful/failure. We generate an async event upon any result. Please let me know what will be the message id for this in the RegistryName.MajorVersion.MinorVersion.MessageKey format ? I am not able to find any Message property in the MessageRegistry for this.
|
|
|
Post by sunitha on Nov 30, 2017 13:53:40 GMT
Thank you. If i am not wrong ; during the event subscription, the message id if passed, it must be of the below pattern. Please confirm
RegistryName.MajorVersion.MinorVersion.MessageKey
|
|
|
Post by sunitha on Nov 30, 2017 10:40:40 GMT
Thanks mraineri. I will consider the approach suggested by you. I have another question in the same line. Can you please give some hints on how the MessageId must be used in the event subscription?
|
|
|
Post by sunitha on Nov 23, 2017 6:36:21 GMT
Any thoughts from anyone ?
|
|
|
Post by sunitha on Nov 8, 2017 9:30:31 GMT
As per the EventDestination schema, while subscribing for the events, the client can send Destination, EventTypes, MessageIds and OriginResources. Here the EventTypes, MessageIds and OriginResources are the arrays.
My question is : If there are 3 members in each of these parameters, then there is 27 combinations of the event-message-resource need to be taken care. How does the server behave, if some of them are not supported. Should it respond as the subscription was a complete failure ? or report a partial failure by marking the failed combinations in the response?
|
|