RESOURCE FENCING FOR VLAN MULTI-TENANT SYSTEMS

• US 20150296016A1
• Filed: 02/27/2013
• Published: 10/15/2015
• Est. Priority Date: 02/27/2013
• Status: Active Grant

• Current Assignee: Hitachi Vantara, LLC (Hitachi, Ltd.)
• Original Assignee: Hitachi Data Systems Corporation (Hitachi, Ltd.)
• Inventors: Manjanatha, Sowmya, Bennett, Charles C. Jr., Curry, Clayton Alan
• Granted Patent: US 9,954,947 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 61/5007 Internet protocol [IP] addresses
• CPC Class Codes: H04L 63/104 Grouping of entities
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

A storage system has a plurality of nodes which are grouped into a plurality of cluster systems each having multiple nodes, each cluster system being logically partitioned into a plurality of namespaces, each namespace including a collection of data objects, each cluster system having multiple tenants, each tenant being a grouping of namespaces, each cluster system having a plurality of capabilities, at least some of the capabilities being bound to the tenants. A node in the cluster system comprises: a memory, and a controller operable to bind each capability to one of a plurality of IP networks so that each capability is bound to only one of the IP networks and has a destination IP address of the IP network to which the capability is bound. It is permissible for one or more capabilities to be bound to the same IP network. Each IP network has one corresponding network interface.

Claims

1. In a storage system having a plurality of nodes, the nodes being grouped into a plurality of cluster systems each having multiple nodes, each cluster system being logically partitioned into a plurality of namespaces, each namespace including a collection of data objects, each cluster system having multiple tenants, each tenant being a grouping of namespaces, each cluster system having a plurality of capabilities, at least some of the capabilities being bound to the tenants, a node in the cluster system comprising:

a memory, and

a controller operable to bind each capability to one of a plurality of IP networks so that each capability is bound to only one of the IP networks and has a destination IP address of the IP network to which the capability is bound;

wherein it is permissible for one or more capabilities to be bound to the same IP network; and

wherein each IP network has one corresponding network interface.

2. The node according to claim 1,

wherein each capability is a resource that is bound to one of (i) the cluster system or (ii) a replication interface of the cluster system or (iii) one of the tenants of the cluster system.

3. The node according to claim 1,

wherein the IP networks include a plurality of physical and virtual LAN segments.

4. The node according to claim 1, wherein the capabilities comprise one or more of:

management resource of the cluster system;

data resource of the cluster system;

replication resource;

management resources of the tenants;

or

data resources of the tenants.

5. The node according to claim 1, wherein the controller is operable, in response to a request for a capability received via the corresponding network interface of one of the IP networks, to:

find an IP network which is bound to the capability being requested by the request and determine whether an IP address of the IP network at which the request is received is in an address range allocated to the found IP network;

if the IP address of the IP network at which the request is received is in an address range allocated to the found IP network, grant access by the request to the requested capability; and

if the IP address of the IP network at which the request is received is not in an address range allocated to the found IP network, deny access by the request to the requested capability.

6. The node according to claim 1, wherein the controller is operable, in response to a request for a capability received via the corresponding network interface of one of the IP networks, to:

determine whether the capability being requested by the request is bound to a tenant and, if yes, find an IP network which is bound to the capability being requested by the request and determine whether the found IP network has an IP network alias entry;

if it is determined that the found IP network does not have an IP network alias entry, determine whether an IP address of the IP network at which the request is received is in an address range allocated to the found IP network and, if yes, grant access by the request to the requested capability and, if no, deny access by the request to the requested capability; and

if it is determined that the found IP network has an alias entry, look up an alias IP network based on the IP network alias entry, and determine whether an IP address of the IP network at which the request is received is in an address range allocated to the alias IP network and, if yes, grant access by the request to the requested capability and, if no, deny access by the request to the requested capability.

7. A method for managing access to capabilities, in a storage system having a plurality of independent nodes, the nodes being grouped into a plurality of cluster systems each having multiple nodes, each cluster system being logically partitioned into a plurality of namespaces, each namespace including a collection of data objects, each cluster system having multiple tenants, each tenant being a grouping of namespaces, each cluster system having a plurality of capabilities, at least some of the capabilities being bound to the tenants, a node in the cluster system including a memory and a controller, the method comprising:

binding each capability to one of a plurality of IP networks so that each capability is bound to only one of the IP networks and have a destination IP address of the IP network to which the capability is bound;

wherein it is permissible for one or more capabilities to be bound to the same IP network; and

wherein each IP network has one corresponding network interface.

8. The method according to claim 7,

wherein each capability is a resource that is bound to one of (i) the cluster system or (ii) a replication interface of the cluster system or (iii) one of the tenants of the cluster system.

9. The method according to claim 7,

wherein the IP networks include a plurality of physical and virtual LAN segments.

10. The method according to claim 7, wherein the capabilities comprise one or more of:

management resource of the cluster system;

data resource of the cluster system;

replication resource;

management resources of the tenants;

or

data resources of the tenants.

11. The method according to claim 7, further comprising, in response to a request for a capability received via the corresponding network interface of one of the IP networks:

finding an IP network which is bound to the capability being requested by the request and determining whether an IP address of the IP network at which the request is received is in an address range allocated to the found IP network;

if the IP address of the IP network at which the request is received is in an address range allocated to the found IP network, granting access by the request to the requested capability; and

if the IP address of the IP network at which the request is received is not in an address range allocated to the found IP network, denying access by the request to the requested capability.

12. The method according to claim 7, further comprising, in response to a request for a capability received via the corresponding network interface of one of the IP networks:

determining whether the capability being requested by the request is bound to a tenant and, if yes, finding an IP network which is bound to the capability being requested by the request and determining whether the found IP network has an IP network alias entry;

if it is determined that the found IP network does not have an IP network alias entry, determining whether an IP address of the IP network at which the request is received is in an address range allocated to the found IP network and, if yes, granting access by the request to the requested capability and, if no, denying access by the request to the requested capability; and

if it is determined that the found IP network has an alias entry, looking up an alias IP network based on the IP network alias entry, and determining whether an IP address of the IP network at which the request is received is in an address range allocated to the alias IP network and, if yes, granting access by the request to the requested capability and, if no, denying access by the request to the requested capability.

13. The method according to claim 7, further comprising:

for a capability which is bound to a tenant which has no dedicated network resources and is inaccessible, finding an IP network which is bound to the capability and assigning an IP network alias entry of an alias IP network to the found IP network so as to map the capability via the IP network alias entry to the alias IP network;

wherein the alias IP network provides network access to the capability which is bound to the tenant.