|
|
Post by fanlufan on Feb 7, 2020 22:27:31 GMT
Hi, I need to represent the system/subsystem hierarchy as below in Redfish or Swordfish. The top level computer system can be an individual computer or contain multiple subsystems; each subsystem can be an individual computer or contain another layer of subsystems. Please kindly advise, thanks!  |
|
|
|
Post by gericson on Feb 7, 2020 22:32:51 GMT
See ComputerSystem/Links/ConsumingComputerSystems and ComputerSystem/Links/SupplyingComputerSystems.
|
|
|
|
Post by fanlufan on Feb 11, 2020 18:58:07 GMT
Thanks for the reply!
So as I understand, there is no such thing as
/redfish/v1/Systems/Subsystem1/Subsystem1.1
/redfish/v1/Systems/Subsystem2/Subsystem2.1/Subsystem2.1.n
In Redfish, all systems/subsystems are represented flat under /redfish/v1/Systems like this:
/redfish/v1/Systems/Subsystem1
/redfish/v1/Systems/Subsystem1.1
/redfish/v1/Systems/Subsystem2
/redfish/v1/Systems/Subsystem2.1
/redfish/v1/Systems/Subsystem2.1.n
Their parent/child relationship is represented through the Consuming/SupplyingComputerSystems within each entity.
Please correct me if I am wrong.
I have one more question: Is there any limit on the length of the path?
For example,/redfish/v1/Systems/Subsystem<uuid>_SomeOther<nqn>_SomethingElse......
|
|
|
|
Post by j2hilland on Feb 11, 2020 19:33:55 GMT
ConsumingComputerSystems and SupplyingComputerSystems were put in for Composition model and were intended for Partitioned systems, where a larger ComputerSystems are composed from smaller ComputerSystems. Keep this in mind in what you are doing as generic clients may expect this usage.
We have a containment heirarchy in Chassis but not really in ComputerSystem.
There is no URI limit specified in Redfish. There are URI limits in the RFCs, but also limits in implementations and there are buffer limits in smaller environments.
We are advising against using strings like "System" or "Subsystem" but using UUIDs and other unique qualifiers for collection members is advisable. General advice is to keep it as small as possible as the URI is not really meant to be human parsable (but the Name property could be).
Can you describe your use case? If this is, for example, aggregation, then this is not how we would advise to represent the system.
|
|
|
|
Post by fanlufan on Feb 11, 2020 21:04:53 GMT
|
|
