Add tenancy to Cluster #2827

Closed
opened 2025-12-29 18:22:33 +01:00 by adam · 0 comments
Owner

Originally created by @Grokzen on GitHub (Aug 27, 2019).

Environment

  • Python version: 3.7.x
  • NetBox version: 2.5.13

Proposed Functionality

  • Add tenancy to Cluster model.
  • Add nested serializer to API for Cluster model.
  • Add filter option for Cluster in list view.
  • Add badge for number of clusters in tenant detail view.

Use Case

When you have a case where you are a provider of both your own clusters and clusters that you host for customers (co-location for example) you want to provide a way to mark each cluster with a owner if you own it yourself or if the customer you host it for owns it.

Database Changes

Add tenant field relation to Cluster model.

External Dependencies

None

Originally created by @Grokzen on GitHub (Aug 27, 2019). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.7.x <!-- Example: 3.5.4 --> * NetBox version: 2.5.13 <!-- Example: 2.3.6 --> <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality - Add tenancy to Cluster model. - Add nested serializer to API for Cluster model. - Add filter option for Cluster in list view. - Add badge for number of clusters in tenant detail view. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case When you have a case where you are a provider of both your own clusters and clusters that you host for customers (co-location for example) you want to provide a way to mark each cluster with a owner if you own it yourself or if the customer you host it for owns it. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes Add tenant field relation to Cluster model. <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 18:22:33 +01:00
adam closed this issue 2025-12-29 18:22:33 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2827