-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OEM Specific Sensor data not available #135
Comments
We really do need to solve this soon. The OEM data is a bit of a pain since it's so free form. Handling that in a strongly typed language is a challenge. I've tried a couple different approaches to handling it and they all seemed a little too hacky to me. I have some rough ideas of how to treat that. I'll try to spend a little more time on it soon and get something implemented. Ideally vendors just wouldn't use OEM specific data in the API, but that's just wishful thinking. ;) |
Yes. I was thinking the same. But we stumbled upon a case wherein Lenovo uses this OEM specific data for reading their |
Hey @sanverm2 - thinking about this a little today. If it's possible for you, it would be great if you could comment here with the output from curl of your Lenovo OEM data. Then I can use that in testing to make sure whatever we end up with works right with their specific OEM data. If not possible, no worries. Just thought I'd ask so there's real world data to work against. |
Sure, sending you complete details shortly. I can also test your code against Lenovo. |
@stmcginnis here it it, right from chassis.
|
Hi Sean,
I am curious if you plan to put OEM specific sensor data .
"/redfish/v1/Chassis/1/Oem/Lenovo/Sensors"
Do you plan to implement? Please let us know we can try that out and contribute back.
The text was updated successfully, but these errors were encountered: