Cluster relations for Devices (HA) #1655

New Issue

MrUnknownDE · 2026-04-06T05:57:40+02:00

MrUnknownDE commented

2026-04-06 05:57:40 +02:00

Originally created by @PieterL75 on 7/11/2025

NetBox version

v4.2.9

Feature type

New functionality

Proposed functionality

Provide a relation between dcim.devices that can contain 'shared' resources.
The current 'virtualization.cluster' is very limited in functionality and lacking ways to assign shared resources between clustered devices.

This FR is a request to create a dcim.cluster object that can contain

cluster type
dcim.devices
ipam.ipaddress
grouped interfaces (a grouping of interfaces of the existing dcim.devices members interfaces)
MAC address for the grouped.interfaces (to document the 'virtual' MAC addresses some solutions create)
tags
custom fields
related virtual.cluster

This is rough idea of what is needed, more fleshout will be required.
This is an addition to the "Virtual Device Contexts" and "Virtual Chassis"

(The VirtualChassis is a very specific implementation of a cluster, with master/slave relation, single mgmt plane. This proposal is for devices that have their own management plane, but share logical services like)

Use case

We have several devices that form an HA cluster (A/S, A/A, Scaleset).
Those clusters typically have multiple shared and dedicated resources (IP, interfaces, cluster type)
The dedicated resources will be assigned to the nodes themself (node ip, interfaces, serial, ...)
The key are the shared resources.
A Cluster has one or more 'floating' ip addresses that live on the 'active' device. This FR will enable us to assign those floating IPs to a dedicated device, rather than to 'a' device.
By the ability of 'grouping' interfaces on the cluster, we can remain the relationship between the interface of the nodes and the ip addresses assigned to those interfaces. The setting of this 'grouped' interface (for ex vlan mode and list) are pushed to the member interfaces, so that they are always aligned.

This could also be used to document the relation between interfaces when using MLAG/vPC/Multihoming.

Another usecase is to keep the configuration of clustered physical devices in sync. ex: all ESXi hosts of a vCenter cluster must have the same vlans/mtu. This FR can be used to link all ports of one portprofile of all ESXi hosts and provide a single place to configure these settings. It would be mandatory that this cluster can be related to virtual clusters.

Database changes

create a dcim.cluster object that can contain

cluster type
dcim.devices
ipam.ipaddress
grouped interfaces (a grouping of interfaces of the existing dcim.devices members interfaces)
tags
custom fields
related virtual.cluster

External dependencies

No response

*Originally created by @PieterL75 on 7/11/2025* ### NetBox version v4.2.9 ### Feature type New functionality ### Proposed functionality Provide a relation between dcim.devices that can contain 'shared' resources. The current 'virtualization.cluster' is very limited in functionality and lacking ways to assign shared resources between clustered devices. This FR is a request to create a dcim.cluster object that can contain - cluster type - dcim.devices - ipam.ipaddress - grouped interfaces (a grouping of interfaces of the existing dcim.devices members interfaces) - MAC address for the grouped.interfaces (to document the 'virtual' MAC addresses some solutions create) - tags - custom fields - related virtual.cluster This is rough idea of what is needed, more fleshout will be required. This is an addition to the "Virtual Device Contexts" and "Virtual Chassis" (The VirtualChassis is a very specific implementation of a cluster, with master/slave relation, single mgmt plane. This proposal is for devices that have their own management plane, but share logical services like) ### Use case We have several devices that form an HA cluster (A/S, A/A, Scaleset). Those clusters typically have multiple shared and dedicated resources (IP, interfaces, cluster type) The dedicated resources will be assigned to the nodes themself (node ip, interfaces, serial, ...) The key are the shared resources. A Cluster has one or more 'floating' ip addresses that live on the 'active' device. This FR will enable us to assign those floating IPs to a dedicated device, rather than to 'a' device. By the ability of 'grouping' interfaces on the cluster, we can remain the relationship between the interface of the nodes and the ip addresses assigned to those interfaces. The setting of this 'grouped' interface (for ex vlan mode and list) are pushed to the member interfaces, so that they are always aligned. This could also be used to document the relation between interfaces when using MLAG/vPC/Multihoming. Another usecase is to keep the configuration of clustered physical devices in sync. ex: all ESXi hosts of a vCenter cluster must have the same vlans/mtu. This FR can be used to link all ports of one portprofile of all ESXi hosts and provide a single place to configure these settings. It would be mandatory that this cluster can be related to virtual clusters. ### Database changes create a dcim.cluster object that can contain - cluster type - dcim.devices - ipam.ipaddress - grouped interfaces (a grouping of interfaces of the existing dcim.devices members interfaces) - tags - custom fields - related virtual.cluster ### External dependencies _No response_

MrUnknownDE closed this issue

2026-04-06 05:57:40 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#1655