From 4bd36f0ea9f2402aa7ce121a310563ce1900f0d6 Mon Sep 17 00:00:00 2001 From: Jeremy Stretch Date: Thu, 5 Jul 2018 12:02:32 -0400 Subject: [PATCH] Closes #2062: Added a note about parent/child device type role --- docs/data-model/dcim.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/data-model/dcim.md b/docs/data-model/dcim.md index 3cb3ed13e..5c9097569 100644 --- a/docs/data-model/dcim.md +++ b/docs/data-model/dcim.md @@ -42,6 +42,8 @@ A device type represents a particular hardware model that exists in the real wor Device types are instantiated as devices installed within racks. For example, you might define a device type to represent a Juniper EX4300-48T network switch with 48 Ethernet interfaces. You can then create multiple devices of this type named "switch1," "switch2," and so on. Each device will inherit the components (such as interfaces) of its device type. +A device type can be a parent, child, or neither. Parent devices house child devices in device bays. This relationship is used to model things like blade servers, where child devices function independently but share physical resources like rack space and power. Note that this is **not** intended to model chassis-based devices, wherein child members share a common control plane. + ### Manufacturers Each device type belongs to one manufacturer; e.g. Cisco, Opengear, or APC. The model number of a device type must be unique to its manufacturer.