mirror/netbox-community-netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2024-05-10 07:54:54 +00:00
Code Activity

Finish refreshing DCIM models documentation

Browse Source
This commit is contained in:
jeremystretch
2022-08-15 15:16:02 -04:00
parent f76ce172e0
commit 4307f078ed
28 changed files with 547 additions and 70 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
docs/models/dcim/location.md
View File

@@ -1,5 +1,28 @@
# Locations
Racks and devices can be grouped by location within a site. A location may represent a floor, room, cage, or similar organizational unit. Locations can be nested to form a hierarchy. For example, you may have floors within a site, and rooms within a floor.
[Racks](./rack.md) and [devices](./device.md) can be grouped by location within a [site](./site.md). A location may represent a floor, room, cage, or similar organizational unit. Locations can be nested to form a hierarchy. For example, you may have floors within a site, and rooms within a floor.
Each location must have a name that is unique within its parent site and location, if any, and must be assigned an operational status. (The set of available statuses is configurable.)
## Fields
### Site
The parent [site](./site.md) to which this location belongs.
### Parent
The parent location of which this location is a child (optional).
### Name
A unique human-friendly name.
### Slug
A unique URL-friendly identifier. (This value can be used for filtering.)
### Status
The location's operational status.
!!! tip
Additional statuses may be defined by setting `Location.status` under the [`FIELD_CHOICES`](../../configuration/data-validation.md#field_choices) configuration parameter.