| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Outside of multi-tenancy environments, tenants are useful for grouping similar storage areas in a cluster.
Single
...
Tenant and Wildcard DNS
Here is a top-level structure:
...
| Info |
|---|
TipUse wildcards so there is no need to add DNS records for every new domain as they are created. This allows users to create separate domains, and DNS resolution happens automatically as long as the domains are created with a similar naming structure. |
One Domain per Department and Employee
Create a wildcard DNS record for the gateway's address: *.cloud.example.com
...
Employees can create as many buckets as they wish within separate domains, to further subdivide content.
One Tenant per Division
It may make sense to have more than one top-level tenant for an organization. Provide each corporate division a separate tenant so it can create and control separate departmental and employee domains. This provides an additional level of organization and authorization to work with.
...
Namespace | Strategy for mapping file systems to objects (discussed above) What FQDN (fully qualified domain name) and DNS setup to use for Gateway (see Content Gateway Implementation) |
|---|---|
Networking | Work out, down to each port (see Setting up Up the Swarm Network), how all Swarm components integrate, to surface design issues List required applications and verify they can access storage regardless of network segment Evaluate need for HTTP versus HTTPS (see also Replicating Replication Feeds over Untrusted Networks) Whether to use front-end load balancing or round robin |
Authentication | Is LDAP or Active Directory integration being used? How does the current ACL structure map to Gateway ACLs? (see Content Gateway Authentication and Setting Tokens) |
Swarm Clients |
|