|
Post by oakhillcoder on Feb 9, 2021 4:47:49 GMT
I'm just starting out with Redfish. Right now I'm trying to learn how the relationships between devices, services, their physical / virtual locations, etc. are setup. Or, rather, I need a clue about the nature of the mechanism / service / manager that populates the resources that allow end user clients to see those relationships. But I haven't found the right way to search for those setup / initialization details. I'd love it if someone would point me to a document, reference, earlier answer, etc. that describes something basic like what steps a facilities manager typically takes to establish the Redfish resource relationships of, say, a new server to its row / rack / offset / facility (or any other detail about added equipment that is unknown prior to its installation). Thanks, Mark
|
|
|
Post by jautor on Feb 9, 2021 23:21:26 GMT
From the facilities standpoint, we're at the beginning of the automation curve for all those relationships. Redfish defined the Facility schema (in late 2019) to first provide the definitions and the methods to show the relationships between facilities and the "equipment" that live inside. The next step will be for implementations of that schema to allow end users to manually enter the various properties to establish those relationships. Then client software can start to utilize that information, as well as provide the means to start automating the population of that data.
In terms of client software that currently does any of this, we're at the very beginning of the standardization cycle - the standard has been defined, and it will take some time to see implementations show up in the real world. The best way for this to happen is to apply pressure to your choice of vendors to enable the functionality. I'm not aware of any software available yet that will allow you to manage the Facility or Location relationships. But that said, I'll bring the issue up with the DMTF tools group as we could easily craft some simple tools to allow setup of those properties.
Jeff
|
|