|
|
Post by parkar on Sept 10, 2019 12:07:27 GMT
Hi, What is the recommendation for representing things containing rows or PODs such as room, building etc? My concrete example is trying to add a room the Chassis hierarchy. Ideally I would want to model this as a Chassis with ChassisType Room but there is no such ChassisType. The two alternatives I can see is: - Don't add room as it's own resource
This means the PostalAddress (including the Room property) would have to be entered on each Row that is in the same room. Also if we want to attach further meta data to the room it would run into the same issue.
- Add room as a chassis with ChassisType Other
Weaker typing so we would probably want to either indicate sub type as a Room through Name or add an OEM extension.
Gives us a good place to attach further room related meta data.
Number 2 looks like the way to go but two questions remain. Is this an intended use of ChassisType Other or are there any other recommended way to represent a room? If this is an intended use of ChassisType Other, why does ChassisTypes stop at Row? Could you consider adding a ChassisType Room? Main argument is that it make more sense to associate a PostalAddress with a single Room Chassis than with multiple Row Chassis. |
|
|
|
Post by jautor on Sept 11, 2019 3:05:00 GMT
We stopped at the "Row" level in those enumerations as even that was really stretching the definition of a "Chassis". I wouldn't recommend using "Other" to represent larger-than-row entities. There is a preliminary new schema for a "Facility" that would be used to contain equipment, and provide a better place for Postal Address / Room Number / etc. We would add links there to show containment of many types of equipment (think anything that could fit in a room, but not necessarily including the Chassis model). The Facility schema proposal is in the DCIM work-in-progress bundle available here: www.dmtf.org/sites/default/files/standards/documents/DSP-IS0005_v0.9a.zipWould certainly like your feedback on this direction. Jeff |
|
|
|
Post by parkar on Sept 11, 2019 8:37:51 GMT
Great, thanks.
I had somehow missed this WIP bundle. Probably more questions and feedback coming after going through this.
|
|
|
|
Post by parkar on Sept 11, 2019 11:46:31 GMT
First few questions.
Is my understanding correct that the recommended way to model Rows and Racks is Chassis?
Draft schema for Facility suggests that similar to Chassis the model does not allow the creation and deletion. Are there any plans to provide mechanism for this or are you forced to create an OEM service to handle such operations?
In the Draft Facility schema updates are not allowed. Is my assumption that this is just a mistake in the draft and intention is to allow patching of location properties on Facility?
Are there any plans yet on when the DCIM bundle will be released?
|
|
|
|
Post by jautor on Sept 17, 2019 20:28:31 GMT
First few questions. Is my understanding correct that the recommended way to model Rows and Racks is Chassis?
Yes, that is the current recommendation, and I don't expect that to change, at least to the "rack" level. "Row" may be too far in that model, though, and as we further develop the Facility model, it may be more appropriate to create a "Row" type in a facility. Because we'd like to form "Power domains" and "Cooling domains" based on the Facility placement - it may make more sense there. [/span] Draft schema for Facility suggests that similar to Chassis the model does not allow the creation and deletion. Are there any plans to provide mechanism for this or are you forced to create an OEM service to handle such operations?
[/quote] Stay tuned on that one, there are a number of applications that are looking for standardization of those operations. There are many OEM services doing this now, and there's a desire for standardizing those processes. [/span] In the Draft Facility schema updates are not allowed. Is my assumption that this is just a mistake in the draft and intention is to allow patching of location properties on Facility?
Are there any plans yet on when the DCIM bundle will be released? [/quote] Yes, that's a bug and I'll get that addressed. I'm hoping to see v1.0 of the DCIM bundle soon! Stay tuned. Jeff |
|
