Understanding multi-tenancy
Multi-tenant architecture provides companies, such as application service providers (ASPs), the ability to support more than one customers' services on a single server, but still keep them logically separate.
In an HNAS server implementation, this architecture is sometimes called real EVS separation.
NoteThe ASP has the responsibility of managing the storage, file systems, shares, and exports to which each tenant has access.
HNAS multi-tenancy configuration mode provides enhancements to the previous stand-alone mode in the following ways:
- Supports tenant configurations in logically separate serving environments on a single physical server or cluster.
- Extends HNAS individual security mode to provide true separation by maintaining per-EVS variables and connection states.
- Supports serving environments for tenants with single or multiple EVSs, configured separately and possibly sharing file serving interfaces.
- Provides per-EVS IP routing and networking settings to support duplicate or overlapping server IP addresses. Includes support for both IPv4 and IPv6.
- Helps detect and prevent EVS crosstalk that can occur when duplicate IP ranges are used. EVS crosstalk can lead to server unresponsiveness.
- Provides CLI EVS context usability improvements.
See the following example of an HNAS multi-tenancy setup:
