Hello 👋
First of all, thank you for the great work on lancache-manager. It has been extremely useful and well designed.
I would like to propose a feature request to support a region-based architecture for managing multiple LAN cache servers across different locations.
Problem / Motivation
Currently, lancache-manager assumes a relatively flat structure where cache servers are managed without a higher-level grouping.
In larger deployments (ISPs, universities, enterprises, or geographically distributed networks), it is common to operate multiple cache servers across different regions or sites.
Managing these servers would be significantly easier if they could be grouped logically by region, rather than handled individually.
Proposed Concept
Introduce a new logical object called Region, which acts as a container for multiple cache nodes.
Example structure:
Region
Name (e.g. EU-West, US-East, Middle East)
Optional metadata (location, description, etc.)
One or more LAN cache servers (nodes)
Suggested Features
Ability to:
Create, edit, and delete regions
Assign one or more cache servers to a region
UI option to:
Switch between regions
View region-level status (aggregate usage, health, traffic, etc.)
Region-scoped views:
Cache statistics per region
Per-node breakdown inside each region
Optional future enhancements:
Region-specific configuration overrides
Traffic comparison between regions
Benefits
Scales better for multi-site deployments
Cleaner organization of cache infrastructure
Easier monitoring and troubleshooting
Opens the door for future enterprise-level features
I believe this abstraction would significantly improve usability for larger environments while remaining optional for smaller setups.
Thank you for considering this request, and I’d be happy to provide more input or examples if needed.
Hello 👋
First of all, thank you for the great work on lancache-manager. It has been extremely useful and well designed.
I would like to propose a feature request to support a region-based architecture for managing multiple LAN cache servers across different locations.
Problem / Motivation
Currently, lancache-manager assumes a relatively flat structure where cache servers are managed without a higher-level grouping.
In larger deployments (ISPs, universities, enterprises, or geographically distributed networks), it is common to operate multiple cache servers across different regions or sites.
Managing these servers would be significantly easier if they could be grouped logically by region, rather than handled individually.
Proposed Concept
Introduce a new logical object called Region, which acts as a container for multiple cache nodes.
Example structure:
Region
Name (e.g. EU-West, US-East, Middle East)
Optional metadata (location, description, etc.)
One or more LAN cache servers (nodes)
Suggested Features
Ability to:
Create, edit, and delete regions
Assign one or more cache servers to a region
UI option to:
Switch between regions
View region-level status (aggregate usage, health, traffic, etc.)
Region-scoped views:
Cache statistics per region
Per-node breakdown inside each region
Optional future enhancements:
Region-specific configuration overrides
Traffic comparison between regions
Benefits
Scales better for multi-site deployments
Cleaner organization of cache infrastructure
Easier monitoring and troubleshooting
Opens the door for future enterprise-level features
I believe this abstraction would significantly improve usability for larger environments while remaining optional for smaller setups.
Thank you for considering this request, and I’d be happy to provide more input or examples if needed.