mirror of
https://github.com/netbox-community/netbox.git
synced 2024-05-10 07:54:54 +00:00
Add hyperlinks to Mermaid graphs
This commit is contained in:
@ -7,6 +7,12 @@ flowchart TD
|
||||
ASN --> Provider
|
||||
Provider --> ProviderNetwork & Circuit
|
||||
CircuitType --> Circuit
|
||||
|
||||
click ASN "../../models/circuits/asn/"
|
||||
click Circuit "../../models/circuits/circuit/"
|
||||
click CircuitType "../../models/circuits/circuittype/"
|
||||
click Provider "../../models/circuits/provider/"
|
||||
click ProviderNetwork "../../models/circuits/providernetwork/"
|
||||
```
|
||||
|
||||
## Providers
|
||||
|
@ -7,6 +7,10 @@ flowchart TD
|
||||
ContactGroup --> ContactGroup & Contact
|
||||
ContactRole & Contact --> assignment([Assignment])
|
||||
assignment --> Object
|
||||
|
||||
click Contact "../../models/tenancy/contact/"
|
||||
click ContactGroup "../../models/tenancy/contactgroup/"
|
||||
click ContactRole "../../models/tenancy/contactrole/"
|
||||
```
|
||||
|
||||
## Contact Groups
|
||||
|
@ -11,6 +11,14 @@ flowchart TD
|
||||
DeviceRole & Platform & DeviceType --> Device
|
||||
Device & ModuleType ---> Module
|
||||
Device & Module --> Interface & ConsolePort & PowerPort & ...
|
||||
|
||||
click Device "../../models/dcim/device/"
|
||||
click DeviceRole "../../models/dcim/devicerole/"
|
||||
click DeviceType "../../models/dcim/devicetype/"
|
||||
click Manufacturer "../../models/dcim/manufacturer/"
|
||||
click Module "../../models/dcim/module/"
|
||||
click ModuleType "../../models/dcim/moduletype/"
|
||||
click Platform "../../models/dcim/platform/"
|
||||
```
|
||||
|
||||
## Manufacturers
|
||||
|
@ -13,6 +13,14 @@ flowchart TD
|
||||
Rack --> Device
|
||||
Site --> Rack
|
||||
RackRole --> Rack
|
||||
|
||||
click Device "../../models/dcim/device/"
|
||||
click Location "../../models/dcim/location/"
|
||||
click Rack "../../models/dcim/rack/"
|
||||
click RackRole "../../models/dcim/rackrole/"
|
||||
click Region "../../models/dcim/region/"
|
||||
click Site "../../models/dcim/site/"
|
||||
click SiteGroup "../../models/dcim/sitegroup/"
|
||||
```
|
||||
|
||||
## Regions
|
||||
|
@ -17,8 +17,15 @@ flowchart TD
|
||||
Aggregate & Role --> Prefix
|
||||
Prefix --> Prefix
|
||||
Prefix --> IPRange & IPAddress
|
||||
|
||||
click Aggregate "../../models/ipam/aggregate/"
|
||||
click IPAddress "../../models/ipam/ipaddress/"
|
||||
click IPRange "../../models/ipam/iprange/"
|
||||
click Prefix "../../models/ipam/prefix/"
|
||||
click RIR "../../models/ipam/rir/"
|
||||
click Role "../../models/ipam/role/"
|
||||
```
|
||||
|
||||
|
||||
!!! tip "Automatic Hierarchies"
|
||||
IP objects in NetBox never need to be manually assigned to the parent objects. The construction of hierarchies is handled automatically by the application according to the inherent rules of IP addressing.
|
||||
|
||||
|
@ -6,6 +6,9 @@ Most core objects within NetBox's data model support _tenancy_. This is the asso
|
||||
flowchart TD
|
||||
TenantGroup --> TenantGroup & Tenant
|
||||
Tenant --> Site & Device & Prefix & Circuit & ...
|
||||
|
||||
click Tenant "../../models/tenancy/tenant/"
|
||||
click TenantGroup "../../models/tenancy/tenantgroup/"
|
||||
```
|
||||
|
||||
## Tenant Groups
|
||||
|
@ -5,6 +5,10 @@ Complementing its IPAM capabilities, NetBox also tracks VLAN information to assi
|
||||
```mermaid
|
||||
flowchart TD
|
||||
VLANGroup & Role --> VLAN
|
||||
|
||||
click Role "../../models/ipam/role/"
|
||||
click VLAN "../../models/ipam/vlan/"
|
||||
click VLANGroup "../../models/ipam/vlangroup/"
|
||||
```
|
||||
|
||||
## VLAN Groups
|
||||
|
@ -7,6 +7,9 @@ Just as NetBox provides robust modeling for physical cable plants, it also suppo
|
||||
```mermaid
|
||||
flowchart TD
|
||||
WirelessLANGroup --> WirelessLANGroup & WirelessLAN
|
||||
|
||||
click WirelessLAN "../../models/wireless/wirelesslan/"
|
||||
click WirelessLANGroup "../../models/wireless/wirelesslangroup/"
|
||||
```
|
||||
|
||||
A wireless LAN is a multi-access network shared by multiple wireless clients, identified by a common service set identifier (SSID) and authentication parameters. Wireless LANs can be organized into self-nesting groups, and each wireless LAN may optionally be bound to a particular VLAN. This allows easily mapping wireless networks to their wired counterparts.
|
||||
|
Reference in New Issue
Block a user