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

Cluster usage fields #7413

New Issue
Closed
opened 2025-12-29 20:23:05 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:23:05 +01:00
Owner
Copy Link

Originally created by @abhi1693 on GitHub (Dec 22, 2022).

NetBox version

v3.4.0

Feature type

Data model extension

Proposed functionality

Add new fields for CPU, memory, and disk to the cluster model. When a user views the cluster page, they should see the current usage vs total allocated in human-readable form. The usage fields can be cached fields or computed fields and should not be editable directly by a human.

Similar information should be provided over the API (maybe using bytes?).

The fields can remain optional to provide backward functionality.

Use case

When clusters are created for virtualization, they need to be planned with the what devices they will contain and how much total capacity is required. When the cluster is put into use, over time the capacity starts to deplete based on the virtual machines deployed within the said cluster. It will be helpful from the perspective of capacity planning to get the current usage vs total usage in both the UI and the API.

Database changes

vcpus - positive integer, optional, help_text=total allocated vcpu
memory - positive decimal, optional, help_text=total allocated memory
disk - positive decimal, optional, help_text=total allocated disk

External dependencies

No response

Originally created by @abhi1693 on GitHub (Dec 22, 2022). ### NetBox version v3.4.0 ### Feature type Data model extension ### Proposed functionality Add new fields for CPU, memory, and disk to the cluster model. When a user views the cluster page, they should see the current usage vs total allocated in human-readable form. The usage fields can be cached fields or computed fields and should not be editable directly by a human. Similar information should be provided over the API (maybe using bytes?). The fields can remain optional to provide backward functionality. ### Use case When clusters are created for virtualization, they need to be planned with the what devices they will contain and how much total capacity is required. When the cluster is put into use, over time the capacity starts to deplete based on the virtual machines deployed within the said cluster. It will be helpful from the perspective of capacity planning to get the current usage vs total usage in both the UI and the API. ### Database changes `vcpus` - positive integer, optional, help_text=total allocated vcpu `memory` - positive decimal, optional, help_text=total allocated memory `disk` - positive decimal, optional, help_text=total allocated disk ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 20:23:05 +01:00
adam closed this issue 2025-12-29 20:23:05 +01:00
adam commented 2025-12-29 20:23:06 +01:00
Author
Owner
Copy Link

@zmaster7 commented on GitHub (Dec 29, 2022):

I would almost say having cpu, memory, disk as fields on a device level would make more sense, and have it calculate the totals at the cluster level as hosts are added/removed from the cluster. However, it seems adding these fields have been brought up before under #6743, and it was determined that it wouldn't apply to all devices.

@zmaster7 commented on GitHub (Dec 29, 2022): I would almost say having cpu, memory, disk as fields on a device level would make more sense, and have it calculate the totals at the cluster level as hosts are added/removed from the cluster. However, it seems adding these fields have been brought up before under #6743, and it was determined that it wouldn't apply to all devices.
adam commented 2025-12-29 20:23:06 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 30, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Mar 30, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:23:06 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 30, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Apr 30, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure type: feature
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#7413
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?