NeoAnd/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2025-12-18 11:22:25 -06:00
Code Issues Actions 10 Packages Projects Releases Wiki Activity

Update virtualization documentation

Browse Source
This commit is contained in:
Jeremy Stretch
2020-07-30 13:48:05 -04:00
parent fe56276f75
commit 59ad61c7a4
5 changed files with 14 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/models/virtualization/virtualmachine.md
View File

@@ -1,11 +1,14 @@
# Virtual Machines
A virtual machine represents a virtual compute instance hosted within a cluster. Each VM must be associated with exactly one cluster.
A virtual machine represents a virtual compute instance hosted within a cluster. Each VM must be assigned to exactly one cluster.
Like devices, each VM can be assigned a platform and have interfaces created on it. VM interfaces behave similarly to device interfaces, and can be assigned IP addresses, VLANs, and services. However, given their virtual nature, they cannot be connected to other interfaces. Unlike physical devices, VMs cannot be assigned console or power ports, device bays, or inventory items.
Like devices, each VM can be assigned a platform and/or functional role, and must have one of the following operational statuses assigned to it:
The following resources can be defined for each VM:
* Active
* Offline
* Planned
* Staged
* Failed
* Decommissioning
* vCPU count
* Memory (MB)
* Disk space (GB)
Additional fields are available for annotating the vCPU count, memory (GB), and disk (GB) allocated to each VM. Each VM may optionally be assigned to a tenant. Virtual machines may have virtual interfaces assigned to them, but do not support any physical component.