starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Extend model VirtualMachine to store minimum memory #4319

New Issue
Closed
opened 2025-12-29 18:34:43 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:34:43 +01:00
Owner
Copy Link

Originally created by @xcdr on GitHub (Dec 1, 2020).

Environment

  • Python version: 3.8.6
  • NetBox version: 2.9.10

Proposed Functionality

Extend VM model for minimum memory.

Use Case

We use PROXMOX VE for hosting our VMs and we have possibility to specify base and minimal amount of memory for VM (ballooning feature).

It would be cool to store minimum memory for VM in NETBOX because We doing automatic inventory via REST API.

See chapter "10.2.6. Memory" in: https://10.222.11.44:8006/pve-docs/pve-admin-guide.html#qm_virtual_machines_settings

Database Changes

memory_min = models.PositiveIntegerField(
    blank=True,
    null=True,
    verbose_name='Minimum memory (MB)'
)
Originally created by @xcdr on GitHub (Dec 1, 2020). ### Environment * Python version: 3.8.6 * NetBox version: 2.9.10 ### Proposed Functionality Extend VM model for minimum memory. ### Use Case We use PROXMOX VE for hosting our VMs and we have possibility to specify base and minimal amount of memory for VM (ballooning feature). It would be cool to store minimum memory for VM in NETBOX because We doing automatic inventory via REST API. See chapter "10.2.6. Memory" in: https://10.222.11.44:8006/pve-docs/pve-admin-guide.html#qm_virtual_machines_settings ### Database Changes ``` memory_min = models.PositiveIntegerField( blank=True, null=True, verbose_name='Minimum memory (MB)' ) ```
adam closed this issue 2025-12-29 18:34:43 +01:00
adam commented 2025-12-29 18:34:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 1, 2020):

NetBox specifically avoids stepping too far into the realm of VM orchestration. It provides some basic fields for CPU, memory, and disk resources suitable for conveying external cloud resources but not much more, because it is assumed that anyone running an extensive VM cloud of their own already has an orchestration system in place.

However, you can always add this as a custom field for your local NetBox deployment.

@jeremystretch commented on GitHub (Dec 1, 2020): NetBox specifically avoids stepping too far into the realm of VM orchestration. It provides some basic fields for CPU, memory, and disk resources suitable for conveying external cloud resources but not much more, because it is assumed that anyone running an extensive VM cloud of their own already has an orchestration system in place. However, you can always add this as a custom field for your local NetBox deployment.
adam commented 2025-12-29 18:34:44 +01:00
Author
Owner
Copy Link

@xcdr commented on GitHub (Dec 1, 2020):

OK, but We use this rather for reporting/overview and not for orchestration.

@xcdr commented on GitHub (Dec 1, 2020): OK, but We use this rather for reporting/overview and not for orchestration.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4319
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?