Description
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