wltu
Minnow
Posts: 3
|
Post by wltu on Jul 12, 2022 18:01:21 GMT
Hi all, I am wondering if we should still use ServiceLabel and LocaltionType to indicate that the device is connected to slot or embedded. Or is that outdated. Do we need to link to the specific resource to indicate that connection. Like a Drive link to a slot to let people know that's how it is connected. Context: gerrit.openbmc.org/c/openbmc/bmcweb/+/50016Thanks, Willy Tu
|
|
|
Post by mraineri on Jul 12, 2022 20:19:38 GMT
ServiceLabel and LocationType are certainly not outdated. While a client can follow the resource link to get additional information about the device, ServiceLabel and LocationType are important if you need to convey to a human where they need to physically inspect the system for service. That's really the jumping point for how to transition from the abstract data model to something concrete in the real world.
|
|
wltu
Minnow
Posts: 3
|
Post by wltu on Jul 19, 2022 20:23:51 GMT
Thanks mraineri, that make sense.
I have a more specific question that I should probably ask in the github instead of here and move the discuss there.
See: [MOD: removed link to private GitHub repo that won't work for forum users]
|
|
|
Post by jautor on Jul 21, 2022 17:36:11 GMT
Yes, the combination of LocationType and ServiceLabel is intended for humans to be able to physically locate the "thing" in question.
If you think about offering instructions to a service technician to "Look for a <LocationType> labeled '<ServiceLabel>'...", it may help explain the usage. e.g. "Look for a Slot labeled 'PCI 3'..."
|
|