From 0893d326656bec0bce1ef79c8004e5c797040b94 Mon Sep 17 00:00:00 2001 From: Jeremy Stretch Date: Wed, 15 Jan 2020 13:27:46 -0500 Subject: [PATCH] Clarify naming constraints related to rack groups --- docs/core-functionality/sites-and-racks.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/core-functionality/sites-and-racks.md b/docs/core-functionality/sites-and-racks.md index bf3c473fd..f86e24b3e 100644 --- a/docs/core-functionality/sites-and-racks.md +++ b/docs/core-functionality/sites-and-racks.md @@ -40,6 +40,8 @@ Racks can be arranged into groups. As with sites, how you choose to designate ra Each rack group must be assigned to a parent site. Hierarchical recursion of rack groups is not currently supported. +The name and facility ID of each rack within a group must be unique. (Racks not assigned to the same rack group may have identical names and/or facility IDs.) + ## Rack Roles Each rack can optionally be assigned a functional role. For example, you might designate a rack for compute or storage resources, or to house colocated customer devices. Rack roles are fully customizable.