We ship with a lot of relationship types in our baseline and also quite some suggested relationships. For the most of them these make perfect sense to me.
Lately I have come across some I am not quite sure, like Powers / Powered By.
Take an example. We have a Blade Server, sitting in a Rack (via an Enclosure usually) and the Rack is hooked to some power circuit. In the CMDB we would get the following relations:
DatabaseServer 1 --> contained in --> NY-01-01
NY-01-01 --> powered by --> Circuit 1
This seems correct, but the circuit is an upstream relation to the rack. In the BSM from the Rack this looks like this:
I thought the Circuit should be downstream. Basically saying if my circuit fails, the rack will have an issue. Isn't that the intention of an upstream relation?
Same with the DatabaseServer, if the rack has an issue, my server is obviously affected. But certainly the Circuit should not be affected if my Rack has an issue.
I believe some of the demo data has the parent/child relationship backwards for DC/Room/Zone/Rack relationships. If you delete the demo data from the cmdb_rel_ci table and rebuild it manually, you should end up with a more reasonable map.
Thanks
Brian
