MULTI-TENANCY INFORMATION PROCESSING SYSTEM, MANAGEMENT SERVER, AND CONFIGURATION MANAGEMENT METHOD

• US 20130227097A1
• Filed: 07/12/2011
• Published: 08/29/2013
• Est. Priority Date: 09/14/2010
• Status: Active Grant

• Current Assignee: Hitachi, Ltd.
• Original Assignee: Hitachi, Ltd.
• Inventors: Yasuda, Yoshiko, Moriki, Toshiomi, Takase, Susumu
• Granted Patent: US 9,397,886 B2
• Time in Patent Office: Days
• US Class Current: 709/222
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0813 characterised by the conditions triggering a change of settings
• CPC Class Codes: H04L 41/0895 Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• 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

In a multi-tenancy information processing system, a necessary setting change item and a target NW device are specified at the time of changing a configuration of a virtual machine of a tenant. A management server 116 includes a device management table 352 for each tenant and each segment, in which an NW setting item set for a network (NW) device is stored for each of the NW devices corresponding to the segment of the tenant, in advance. The management server 116 receives a configuration change request including type information on a request representing addition, deletion, or movement of the virtual machine, an identifier of a target tenant, and an identifier of a target segment.

Claims

1. A management server in a multi-tenancy information processing system having plural types of network devices, a server device, and the management server, configuring a tenant which is a virtual network system including a desired network device of the network devices and a virtual machine configured by the server device for each client, in which the tenant has a plurality of segments, the management server comprising:

a device management table for storing, for each tenant and each segment, network setting items set for a network device in correspondence with an identifier of the network device corresponding to the segment of the tenant in advance; and

a tenant configuration changing unit that specifies the network setting items to be set and the network devices being a setting target at the time of changing the configuration of the virtual machine,

wherein the tenant configuration changing unit

receives, from a management console, a configuration change request including type information on a request representing any one of addition, deletion, and movement of the virtual machine, a tenant identifier of a target tenant, and a segment identifier of a target segment,

determines whether or not the virtual machine is present in the target segment of the target tenant after changing the configuration, and/or whether or not the target segment of the target tenant is existing,

specifies one or a plurality of the network setting items on the basis of the type information on the request included in the configuration change request, and both or either determination results of whether or not the virtual machine is present in the target segment after changing the configuration, and determination results of whether or not the target segment is existing, and

specifies one or plurality of the network devices corresponding to one or the plurality of specified network setting items, with reference to the device management table.

2. The management server according to claim 1,

wherein the tenant configuration changing unit generates setting information for setting specified network setting item for specified network device.

3. The management server according to claim 1,

wherein the network setting item includes at least two of filtering, routing, and virtual network setting.

4. The management server according to claim 1,

wherein the tenant configuration changing unit,

if the type information on the configuration change request represents the addition of the virtual machine, determines whether or not the target segment of the target tenant to which the virtual machine is added is existing,

if the target segment is existing, selects the filtering as the network setting item, and

if the target segment is not existing, selects the filtering, the routing, and the virtual network setting as the network setting items.

5. The management server according to claim 1,

wherein the tenant configuration changing unit,

if the type information on the configuration change request represents the deletion of the virtual machine, determines whether or not another virtual machine is present in the target segment of the target tenant after deleting the virtual machine, and

if another virtual machine is present, selects the filtering as the network setting item, and

if another virtual machine is not present, selects the filtering, the routing, and the virtual network setting as the network setting items.

6. The management server according to claim 1,

wherein the type information on the configuration change request represents the movement of the virtual machine, and the segment identifier included in the configuration change request includes a segment identifier of a source segment, and a segment identifier of the target segment,

wherein the tenant configuration changing unit,

if the type information on the configuration change request represents the movement of the virtual machine, determines, for each of the source segment and each of the target segment, whether or not the segments are existing, and determines whether or not the virtual machine is existing after moving the virtual machine, or not, and

specifies the network setting item of the source segment and the network setting item of the target segment according to determination results, respectively.

7. The management server according to claim 1, further comprising a segment management table for storing the number of virtual machines within the segment in correspondence with the segment identifier for identifying the segment within the tenant, for each of the tenants,

wherein the tenant configuration changing unit

determines whether or not the virtual machine is present in the target segment of the target tenant after changing the configuration, on the basis of the number of corresponding virtual machines, with reference to the segment management table on the basis of the tenant identifier and the segment identifier included in the configuration change request.

8. The management server according to claim 1, further comprising a segment management table for storing the segment identifier for identifying the segment within the tenant therein, for each of the tenants,

wherein the tenant configuration changing unit,

determines, with reference to the segment management table on the basis of the tenant identifier and the segment identifier included in the configuration change request, that the target segment of the target tenant is existing if the segment identifier is stored corresponding to the tenant,

determines that the target segment of the target tenant is not existing if the segment identifier is not stored.

9. The management server according to claim 1, further comprising a segment management table for storing use case information of the virtual machine in correspondence with the segment identifier for identifying the segment within the tenant, for each of the tenants,

wherein the configuration change request further includes use case information of the virtual machine, and

wherein the tenant configuration changing unit,

selects, with reference to the segment management table on the basis of the tenant identifier and the use case information of the virtual machine included in the configuration change request, one of the segment identifiers having identical use case information on the virtual machine in the tenant if the number of segments is to be increased after changing the configuration, and

specifies corresponding network device with reference to the device management table corresponding to selected segment identifier.

10. The management server according to claim 1, further comprising a setting items specifying table for storing the network setting item in correspondence with the type information on the configuration change request, state information representing whether or not the target segment is existing, and presence or absence information on the virtual machine in the target segment after changing the configuration, in advance,

wherein the tenant configuration changing unit specifies corresponding network setting item with reference to the setting items specifying table on the basis of the type information on the request included in the configuration change request, determination results of whether or not the target segment is existing, and/or determination results of whether or not the virtual machine is existing in the target segment after changing the configuration.

11. The management server according to claim 10, further comprising:

a virtual network management table that manages correspondence of an identifier of the virtual network, the tenant identifier, and the segment identifier in the multi-tenancy information processing system; and

a route management table that manages route information among the plurality of segments configuring the multi-tenancy information processing system,

wherein the setting items specifying table further includes a setting type representing whether the setting is to be added or deleted, and change information representing a change in the number of segments after changing the configuration, and

wherein the tenant configuration changing unit further specifies, from the setting items specifying table, the setting type and the change information corresponding to the type information on the request included in the configuration change request, and both or either the determination results of whether or not the target segment is existing and the determination results of whether or not the virtual machine is existing in the target segment after changing the configuration, and

generates one or more setting commands including virtual network setting and routing, with the use of the virtual network management table and the route management table, according to the setting type and the change information, with respect to the specified network device, after specifying the target network device.

12. The management server according to claim 1, wherein the management server receives the configuration change request including the type information on the configuration change request input from a configuration management interface of the management console, the tenant identifier, and the segment identifier of the target segment.

13. A multi-tenancy information processing system comprising:

plural types of network devices;

a server device; and

a management server, the system configuring a tenant which is a virtual network system including a desired network device of the network devices and a virtual machine configured by the server device for each client, in which the tenant has a plurality of segments,

wherein the management server comprising;

a device management table for storing, for each tenant and each segment, network setting items set for a network device in correspondence with an identifier of the network device corresponding to the segment of the tenant in advance; and

a tenant configuration changing unit that specifies the network setting items to be set and the network devices being a setting target at the time of changing the configuration of the virtual machine,

wherein the tenant configuration changing unit

receives, from a management console, a configuration change request including type information on a request representing any one of addition, deletion, and movement of the virtual machine, a tenant identifier of a target tenant, and a segment identifier of a target segment,

determines whether or not the virtual machine is present in the target segment of the target tenant after changing the configuration, and/or whether or not the target segment of the target tenant is existing,

specifies one or a plurality of the network setting items on the basis of the type information on the request included in the configuration change request, and both or either determination results of whether or not the virtual machine is present in the target segment after changing the configuration, and determination results of whether or not the target segment is existing, and

specifies one or plurality of the network devices corresponding to one or the plurality of specified network setting items, with reference to the device management table.

14. The multi-tenancy information processing system according to claim 13, wherein

the tenant configuration changing unit generates setting information for setting specified network setting item for specified network device, and

the network device changes the setting according to generated setting information.

15. A configuration management method in a multi-tenancy information processing system having plural types of network devices, a server device, and a management server, configuring a tenant which is a virtual network system including a desired network device of the network devices and a virtual machine configured by the server device for each client, in which the tenant has a plurality of segments, for specifying network setting items to be set and network devices being a setting target at the time of changing configuration of a virtual machine, the configuration management method comprising:

receiving by the management server, from a management console, a configuration change request including type information on a request representing any one of addition, deletion, and movement of the virtual machine, a tenant identifier of a target tenant, and a segment identifier of a target segment,

determining by the management server, whether or not the virtual machine is present in the target segment of the target tenant after changing the configuration, and/or whether or not the target segment of the target tenant is existing,

specifying by the management server, one or a plurality of the network setting items on the basis of the type information on the request included in the configuration change request, and both or either determination results of whether or not the virtual machine is present in the target segment after changing the configuration, and determination results of whether or not the target segment is existing, and

specifying by the management server, one or plurality of the network devices corresponding to one or the plurality of specified network setting items, with reference to a device management table for storing, for each tenant and each segment, network setting items set for a network device in correspondence with an identifier of the network device corresponding to the segment of the tenant in advance.

16. The configuration management method according to claim 15,

wherein the management server generates setting information for setting specified network setting item for specified network device.