Post by sunnysriavstava on Feb 5, 2021 6:47:11 GMT
We want to publish inventory property like location code for USB ports, Display port, CXP port via redfish schema. What we can figure out is we can make use of port schema for that, but Port schema is tied up to PortCollection schema which in turn is tied up tp some adapters and controllers for example fabric adapters, media controllers, Network adapters etc.
My query was about how to figure out under which category of adapters or controllers we can model USB ports, Display ports and CXP ports. Also if there is any other way we can publish property for these items apart from port?
We talked about this today, and you've hit an area that it's time we address. What we don't want to do is to just model the physical connector without any way to provide linkage to the device(s) behind it - which is why we avoided having a simple "Ports" collection under Chassis.
So we're going to approach this by defining something for USB devices and display adapters (we knew that would come up eventually) - so that there's a place to land those "Ports". The CXP port can be modeled today using the recently-added Infiniband support in NetworkDeviceFunction.
This will probably take a bit of time to finalize - if you're in a hurry for this, an OEM solution is probably best for the short term. But at least you can get an idea of where we'll take this. If you have any input on the USB controller/device model or display adapter, let us know.
Post by sunnysriavstava on Feb 19, 2021 7:39:28 GMT
The requirement is to control an LED placed near CXP port, Hence I was looking at publishing location code of CXP port via Redfish. Now, Infiniband under NetworkDeviceFunction does not has property Location. Is it correct if we model them as fabric adapters and link them back to computer system schema? Or is there a better way we can achieve that?