fish
Guppy
Posts: 65
|
Post by fish on Jan 16, 2018 13:04:10 GMT
Hi,
Some questions related to ComputerSystem property SystemType = PhysicallyPartitioned.
This seems to be used for ComputerSystems in Resource – blocks when composing them into ComputerSystem with SystemType = Composed. (Looking e.g. at mockup “Bladed Partitions” in Redfish developer hub.) The Mockup describes the blade ComputeBlock (with SystemType PhysicallyPartitioned) as “represents PhysicallyPartitionedSystem ResourceBlock, from which System can be Composed”. But computerSystem schema LongDescription of enum PhysicallyPartitioned is “A SystemType of PhysicallyPartition is typically used when representating a single system constructed from one or more physical systems via a firmware or hardware-based service.", which indicates that rather the constructed (same as “composed”?) system should have system type “PhysicallyPartitioned”, which seems strange. Shouldn’t the composed system have systemType “composed”.. ? Can I assume that this enum LongDescription is a bit misleading, and should maybe be updated?
How and when should the following new ComputerSystem properties be used?
- “ConsumingComputerSystems” ("An array of references to ComputerSystems that are realized, in whole or in part, from this ComputerSystem."),
- “SupplyingComputerSystems” ("An array of references to ComputerSystems that contribute, in whole or in part, to the implementation of this ComputerSystem.").
And is there any dependency to the SystemTypes of involved ComputerSystems?
To me it sounds very similar to the use case for composed systems including “PhysicallyPartitioned” and “Composed” system types, but this use case uses Links properties of type ResourceBlock (from the Composed system) and Link ComputerSystem (from the ResourceBlock) according to Mockup “Bladed system”.
Is there any tutorial, mockup or other description for “SupplyingComputerSystems” and “ConsumingComputerSystems”?
|
|
|
|
Post by mraineri on Jan 16, 2018 14:46:07 GMT
The concept of "ConsumingComputerSystems" and "SupplyingComputerSystems" works above the Composability level. Effectively the output of composing a ComputerSystem out of ResourceBlocks would result in a single ComputerSystem that behaves like a standalone unit, and there's typically some lower level hardware aspects at play for how these ComputerSystems are composed.
Unfortunately we don't currently have mockups for this, but the "ConsumingComputerSystems" and "SupplyingComputerSystems" links start coming into play in scenarios like having a cluster, distributed system, or distributed application, and you need to express which standalone systems are playing a role in the application. This concept is really a more logical aspect of utilizing systems.
|
|
fish
Guppy
Posts: 65
|
Post by fish on Jan 16, 2018 15:54:14 GMT
The concept of "ConsumingComputerSystems" and "SupplyingComputerSystems" works above the Composability level. Effectively the output of composing a ComputerSystem out of ResourceBlocks would result in a single ComputerSystem that behaves like a standalone unit, and there's typically some lower level hardware aspects at play for how these ComputerSystems are composed. Unfortunately we don't currently have mockups for this, but the "ConsumingComputerSystems" and "SupplyingComputerSystems" links start coming into play in scenarios like having a cluster, distributed system, or distributed application, and you need to express which standalone systems are playing a role in the application. This concept is really a more logical aspect of utilizing systems. OK, thanks. Then I would assume that both "Supplying" and "Consuming" systems can have systemType set to "Physical"? But then the only thing separating the "logical" / "consuming" system from a "supplying"/"non-logical" system will be the none-empty SupplyingComputerSystems Link. Do you know if it was ever discussed to introduce separate SystemType for such "logical" systems? E.g. systemType "logical"? Or could this maybe be candidate for future release? Would you agree on that this could be valuable for clarification and give easier separation of "logical" system constructs from ordinary physical systems? |
|
|
|
Post by mraineri on Jan 16, 2018 18:53:41 GMT
The Supplying and Consuming systems don't necessarily have to be Physical; it's possible a client created Composed systems out of ResourceBlocks, and then installed software on those systems to create a distributed system that utilizes the Supplying and Consuming relationship. But, in general, they're most likely going to either be Physical, PhysicallyPartitioned, or Composed. I think the "Logical" concept was discussed in the past, but it never gained traction. We can bring it up as a discussion point again, especially now that we have these Supplying and Consuming relationships in the model.
|
|
fish
Guppy
Posts: 65
|
Post by fish on Jan 17, 2018 7:34:44 GMT
OK, thanks!
|
|
