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

Consider adding support for native redis cluster #3998

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

Originally created by @gedia on GitHub (Aug 19, 2020).

Proposed Functionality

Support native redis clusters by migrating to https://github.com/Grokzen/redis-py-cluster which is supposed to be a (mostly) drop-in replacement for redis-py. Functionality should include honouring MOVED responses and auto-discovery of redis cluster nodes if not explicitly provided in netbox configuration.

Use Case

For installations where there is already a functioning redis cluster deployment, it would be useful to support its use by netbox as well instead of having to deploy a local redis instance just for netbox.

Database Changes

None that I'm aware of

External Dependencies

https://github.com/Grokzen/redis-py-cluster

Originally created by @gedia on GitHub (Aug 19, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. 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. --> ### Proposed Functionality Support native redis clusters by migrating to https://github.com/Grokzen/redis-py-cluster which is supposed to be a (mostly) drop-in replacement for redis-py. Functionality should include honouring MOVED responses and auto-discovery of redis cluster nodes if not explicitly provided in netbox configuration. <!-- 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 For installations where there is already a functioning redis cluster deployment, it would be useful to support its use by netbox as well instead of having to deploy a local redis instance just for netbox. <!-- 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 None that I'm aware of <!-- 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 https://github.com/Grokzen/redis-py-cluster
adam added the pending closure label 2025-12-29 18:32:32 +01:00
adam closed this issue 2025-12-29 18:32:32 +01:00
adam commented 2025-12-29 18:32:33 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Aug 25, 2020):

This does not appear to be a trivial change, nor is it a "drop in" for redis-py (you need specific configuration and utilization for it). We currently use django-cacheops and not redis-py directly, this is also not supported in django-cacheops. You will need to raise this upstream in django-cacheops (looks like it might be at Suor/django-cacheops#35)

@DanSheps commented on GitHub (Aug 25, 2020): This does not appear to be a trivial change, nor is it a "drop in" for redis-py (you need specific configuration and utilization for it). We currently use django-cacheops and not redis-py directly, this is also not supported in django-cacheops. You will need to raise this upstream in django-cacheops (looks like it might be at Suor/django-cacheops#35)
adam commented 2025-12-29 18:32:33 +01:00
Author
Owner
Copy Link

@gedia commented on GitHub (Aug 25, 2020):

Got it. Thanks!

@gedia commented on GitHub (Aug 25, 2020): Got it. Thanks!
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
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#3998
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?