|
|
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 j2hilland on Dec 7, 2017 21:31:54 GMT
The Message Registry in 8011 is currently intended for ErrorInfo messages returned in a response body from a PUT/POST/PATCH operation. It's not really intended for use with Events. That being said, we are looking at a couple of approaches for standard messages that could be used for Events. The Current Event types are under discussion as well as the traditional Alert (IPMI-ish) or LifeCycle (CIM-ish) are being looked at as well in light of a new registry. So there isn't anything standard available at this point for Events. Right now, most OEMs are creating their own message registry and you are certainly welcome to do so. With luck, we might have an eventing approach available in early 2018.
|
|
|
|
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 j2hilland on Dec 8, 2017 16:08:05 GMT
We can't make required properties into optional - that's not a backwards compatible change. If you're going through the trouble of creating messages and an OEM messageID, you might as well just create a messageRegistry. You can use the Registry collection off of the service root to inform clients of where to get it.
|
|
|
|
Post by sunitha on Dec 11, 2017 5:08:49 GMT
Sure. I will work on that ! Thanks a lot
|
|
