JP2020154659A - Information processing system, unified management server, management method, and program - Google Patents

Abstract

To reassign management target devices and reset connection destinations of the management target devices in correspondence with data processing execution servers the number of which has been reduced.SOLUTION: An information processing system having: an unified management server which manages assignment of one or more management target devices to one or more data processing execution servers; and a management tool which increases or decreases the number of data processing execution servers solves the aforementioned problem by including, in the management tool, scale processing execution means for, based on a request for processing of increasing or decreasing the number of data processing execution servers, increasing or decreasing the number of data processing execution servers and transmitting a result of the number increased or decreased to the unified management server, and by including, in the unified management server, function execution means for reassigning the management target devices to the data processing execution servers the number of which has increased or decreased based on the result of the number increased or decreased and transmitting a result of the reassignment of the management target devices to the data processing execution servers to update connection destinations of the management target devices based on the result of the reassignment of the management target devices.SELECTED DRAWING: Figure 10

Description

The present invention relates to an information processing system, a centralized management server, a management method and a program.

In recent years, with the rise of cloud computing, it is required to efficiently process and retain a large amount of data. Therefore, a distributed processing technology that realizes efficient processing by coordinating a plurality of servers has been developed. When performing distributed processing, it is necessary to distribute the data of the processing target (managed target) to each server (hereinafter, also referred to as "cluster member" or "member") constituting the cluster.

For example, in order to appropriately distribute the load to each server that composes the cluster and suppress the cost increase of server expansion, the load determination unit appropriately uses rebalancing and scale-out together to configure each cluster. A technique for appropriately distributing the load on a server and suppressing an increase in the cost of adding a server has been conventionally known (see, for example, Patent Document 1).

Conventionally, there is a mechanism for providing a cloud service by installing software on a VM (Virtual Machine) instance of Infrastructure as a Service (IAAS) on a cloud platform.

As such a cloud service configuration, one centralized management server VM and one or more job execution server VMs are connected to each customer via a network so that they can flexibly support small to large-scale operations. was there. For example, the number of job execution server VMs can be increased or decreased by an autoscale mechanism according to the number of managed devices and the system load such as the number of users / jobs.

However, the conventional autoscale mechanism does not consider reallocating managed devices and resetting the connection destination of managed devices in response to the increase or decrease in the number of job execution server VMs. There was a problem. In addition, Patent Document 1 does not describe the above-mentioned problems.

An embodiment of the present invention provides an information processing system capable of reallocating managed devices and resetting the connection destination of managed devices in correspondence with an increased or decreased number of data processing execution servers. With the goal.

In order to achieve the above object, an embodiment of the present invention includes a centralized management server that manages the allocation of one or more managed devices to one or more data processing execution servers, and management that increases or decreases the number of the data processing execution servers. An information processing system including a tool, wherein the management tool increases or decreases the number of the data processing execution servers based on a processing request for increasing or decreasing the number of the data processing execution servers, and the data processing execution server of the data processing execution server. The centralized management server has a scale processing execution means for transmitting the result of an increase or decrease in the number to the centralized management server, and the centralized management server increases or decreases the number of the data processing based on the result of the increase or decrease in the number of the data processing execution servers. The managed device is reassigned to the execution server, the result of the reassignment of the managed device is transmitted to the data processing execution server, and the connection destination setting of the managed device is reassigned to the managed device. It is characterized by having a function execution means for updating based on the result of.

It is possible to reallocate the managed device and reset the connection destination of the managed device according to the data processing execution server whose number has been increased or decreased.

It is a block diagram of an example of an information processing system which concerns on this embodiment. It is a hardware block diagram of an example of the computer which concerns on this embodiment. It is a functional block diagram of an example of the service management tool which concerns on this embodiment. It is a functional block diagram of an example of the centralized management server which concerns on this embodiment. It is a functional block diagram of an example of the job execution server which concerns on this embodiment. It is a functional block diagram of an example of the device which concerns on this embodiment. It is a figure explaining an example of management data managed by the data management part of a centralized management server. It is a figure explaining an example of the management data managed by the data management part of a job execution server. It is a figure explaining an example of the management data managed by the data management part of a device. It is a processing schematic diagram of an example of an information processing system which concerns on this embodiment. It is a sequence diagram of an example of the process until the scale-out process request is sent to the service management tool at the time of executing the scale-out process. It is a sequence diagram of an example of the process until the scale-out process request is sent to the service management tool at the time of executing the scale-out process. It is a sequence diagram of an example of the process until the service management tool returns the result of the scale-out process to the centralized management server at the time of executing the scale-out process. It is a sequence diagram of an example of the process until the result of the scale-out process is returned to the job execution server at the time of executing the scale-out process. It is a flowchart of an example of the process until the setting of the job execution server of the connection destination of a device is updated at the time of execution of scale-out process. It is a sequence diagram of an example of the process of updating the setting of the connection destination of a device triggered by the job process request from the device side to the job execution server. It is a sequence diagram of an example of the process until the scale-in process request is transmitted to the service management tool at the time of executing the scale-in process. It is a sequence diagram of an example of the process until the service management tool performs the scale-in process at the time of executing the scale-in process. It is a sequence diagram of an example of the process of updating the setting of the connection destination of a device triggered by the job process request from the device side to the job execution server.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In this embodiment, job processing as an example of data processing will be described, but the present embodiment is not limited to job processing.

[First Embodiment]
<System configuration>
First, the system configuration of the information processing system 1 according to the present embodiment will be described with reference to FIG. FIG. 1 is a configuration diagram of an example of an information processing system 1 according to the present embodiment. In the information processing system 1 of FIG. 1, the cloud environment 10 and the on-premises environment 20 are connected to each other via a network 40 such as the Internet so that data communication is possible. Further, an administrator terminal 30 operated by the administrator is connected to the network 40 so that data communication is possible.

The cloud environment 10 is an example of a computing environment that provides computer resources in the form of a service via a network 40. The cloud environment 10 has a resource management API 12, a service management tool 14, a centralized management server 16, and a job execution server 18. The name of the service management tool 14 is an example, and may be the name of a service management server, or may be constructed by one or more servers.

The resource management API 12 is, for example, a public API (Application Programming Interface) of IaaS on a cloud platform, and creates or destroys an instance of a job execution server 18. The service management tool 14 executes the scale-out or scale-in of the job execution server 18 by using the resource management API 12 based on the scale-out or scale-in request from the centralized management server 16.

The centralized management server 16 is provided for each customer, for example. The centralized management server 16 performs processes such as configuration management, orchestration, and master data management of the information processing system 1 for each customer, for example. Further, the centralized management server 16 manages the job execution server 18 to be managed. The job execution server 18 manages and monitors the allocated device 22 (an example of a managed device), executes a job request from the device 22, and performs other processes. Execution of the job request from the device 22 includes user authentication, scan document distribution, and the like. The number of managed job execution servers 18 managed by one centralized management server 16 increases or decreases depending on the autoscale mechanism. In the present embodiment, "increase / decrease" includes not only increasing / decreasing the number of units but also increasing or decreasing the number of units.

The on-premises environment 20 is an example of a computing environment operated by a user. In the on-premises environment 20, equipment 22 such as an image forming apparatus is installed so that data communication is possible via the network 40. The image forming apparatus is an MFP (Multifunction Peripheral), a printer, a scanner, a facsimile, or the like.

The image forming apparatus is an example of the device 22. The device 22 is not limited to an image forming device, for example, an output device such as a PJ (Projector: projector), an IWB (Interactive White Board: a white board having an electronic whiteboard function capable of intercommunication), a digital signage, and a HUD (Head). It may be an Up Display) device, an industrial machine, an imaging device, a sound collecting device, a medical device, a network home appliance, a car (Connected Car), or the like. The administrator terminal 30 is realized by an information processing device such as a PC, a mobile phone, a smartphone, a tablet terminal, a game machine, or a PDA, and is operated by a user such as an administrator.

The configuration of the information processing system 1 shown in FIG. 1 is an example. For example, the information processing system 1 shown in FIG. 1 is only one of a plurality of computing environments for implementing the embodiments disclosed in the present specification.

In certain embodiments, the centralized management server 16 or job execution server 18 includes a plurality of computing devices, such as a server cluster. The plurality of computing devices are configured to communicate with each other over any type of communication link, including networks, shared memory, and the like, and perform the processes disclosed herein. Each element of the centralized management server 16 or the job execution server 18 may be integrated into one information processing device, or may be divided into a plurality of information processing devices.

<Hardware configuration>
"Computer"
The resource management API 12, the service management tool 14, the centralized management server 16, and the job execution server 18 are realized by, for example, the computer 500 having the hardware configuration shown in FIG. Further, when the administrator terminal 30 is a PC which is an example of an information processing terminal, it is realized by, for example, a computer 500 having a hardware configuration shown in FIG.

FIG. 2 is a hardware configuration diagram of an example of the computer 500 according to the present embodiment. As shown in FIG. 2, the computer 500 includes a CPU 501, a ROM 502, a RAM 503, an HD 504, an HDD (Hard Disk Drive) controller 505, a display 506, an external device connection I / F (Interface) 508, a network I / F 509, and data. It includes a bus 510, a keyboard 511, a pointing device 512, a DVD-RW (Digital Versatile Disk Rewritable) drive 514, and a media I / F 516.

Of these, the CPU 501 controls the operation of the entire computer 500. The ROM 502 stores a program used to drive the CPU 501 such as an IPL. The RAM 503 is used as a work area of the CPU 501. The HD504 stores various data such as programs. The HDD controller 505 controls reading or writing of various data to the HD 504 according to the control of the CPU 501.

The display 506 displays various information such as cursors, menus, windows, characters, or images. The external device connection I / F 508 is an interface for connecting various external devices. The external device in this case is, for example, a USB (Universal Serial Bus) memory, a printer, or the like.

Further, the network I / F 509 is an interface for performing data communication using the network. The data bus 510 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 501.

Further, the keyboard 511 is a kind of input means including a plurality of keys for inputting characters, numerical values, various instructions and the like. The pointing device 512 is a kind of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, and the like. The DVD-RW drive 514 controls reading or writing of various data to the DVD-RW 513 as an example of the removable recording medium. In addition, it is not limited to DVD-RW, and may be DVD-R or the like. The media I / F 516 controls reading or writing (storage) of data to a recording medium 515 such as a flash memory.

<Functional configuration>
FIG. 3 is a functional configuration diagram of an example of the service management tool 14 according to the present embodiment. The service management tool 14 of FIG. 3 has a scale processing execution unit 50 and a communication unit 52. The scale processing execution unit 50 and the communication unit 52 are realized by processing one or more programs installed in the service management tool 14 to be executed by the CPU 501.

The scale processing execution unit 50 executes scale-out or scale-in of the job execution server 18 by using the resource management API 12 based on the request from the centralized management server 16. The communication unit 52 communicates with the centralized management server 16 or the resource management API 12.

FIG. 4 is a functional configuration diagram of an example of the centralized management server 16 according to the present embodiment. The centralized management server 16 in FIG. 4 has a function execution unit 60, a data management unit 62, a notification unit 64, an input unit 66, a monitoring unit 68, a communication unit 70, and a management data holding unit 72. In the function execution unit 60, the data management unit 62, the notification unit 64, the input unit 66, the monitoring unit 68, the communication unit 70, and the management data holding unit 72, one or more programs installed on the centralized management server 16 are installed in the CPU 501. It is realized by the process to be executed.

The function execution unit 60 executes various functions of the centralized management server 16. The data management unit 62 reads data from a database (hereinafter referred to as DB) held by the management data holding unit 72 or writes data to the DB. The notification unit 64 transmits a notification (for example, an e-mail notification) to the administrator terminal 30. The input unit 66 accepts an operation (for example, a browser operation) from the administrator.

The monitoring unit 68 monitors the state of the entire managed system of the centralized management server 16 (loads and errors such as the number of devices 22 that are managed devices and the number of jobs). The communication unit 70 communicates with the service management tool 14 or the job execution server 18. The management data holding unit 72 holds a DB that stores master data necessary for the operation of the system to be managed by the centralized management server 16.

FIG. 5 is a functional configuration diagram of an example of the job execution server 18 according to the present embodiment. The job execution server 18 shown in FIG. 5 includes a function execution unit 80, a data management unit 82, a monitoring unit 84, a communication unit 86, and a management data holding unit 88. The function execution unit 80, the data management unit 82, the monitoring unit 84, the communication unit 86, and the management data holding unit 88 are realized by processing one or more programs installed in the job execution server 18 to be executed by the CPU 501.

The function execution unit 80 executes various functions of the job execution server 18. The data management unit 82 reads data from the DB held by the management data holding unit 88 or writes data to the DB. The monitoring unit 84 monitors the status of the job execution server 18 (loads and errors such as the number of devices 22 that are managed devices and the number of jobs). The communication unit 86 communicates with the centralized management server 16 or the device 22. The management data holding unit 88 holds a DB that stores data necessary for the operation of the job execution server 18.

FIG. 6 is a functional configuration diagram of an example of the device 22 according to the present embodiment. The device 22 of FIG. 6 has a function execution unit 90, a data management unit 92, a communication unit 94, and a management data holding unit 96. The function execution unit 90, the data management unit 92, the communication unit 94, and the management data holding unit 96 are realized by a process of causing the CPU to execute one or more programs installed in the device 22.

The function execution unit 90 executes various functions of the device 22. The data management unit 92 reads data from the DB held by the management data holding unit 96 or writes data to the DB. The communication unit 94 communicates with the job execution server 18. The management data holding unit 96 holds a DB that stores data necessary for the operation of the device 22.

FIG. 7 is a diagram illustrating an example of management data managed by the data management unit 62 of the centralized management server 16. The centralized management server 16 holds job execution server information, managed device information, and job log information as management data.

The job execution server information is information about one or more job execution servers 18 managed by each centralized management server 16. The job execution server information includes a job execution server ID, an IP address, a host name, a version, a customer ID, a region ID, and a subnet ID as items.

The job execution server ID is an example of identification information that identifies the job execution server 18. The IP address is the IP address of the job execution server 18. The host name is the host name of the job execution server 18. The version is the version of the job execution server 18. The customer ID is an example of customer identification information that uses the job execution server 18. The region ID is, for example, an example of identification information of an area (region) in which a data center of a cloud environment 10 is installed. The subnet ID is an example of subnet identification information.

The customer ID, region ID, and subnet ID are information for identifying which subnet in which region in which customer account of IaaS on the cloud platform each job execution server 18 belongs to. The customer ID, region ID, and subnet ID are used to determine an appropriate group of job execution servers 18 during autoscaling.

The managed device information is information about one or more devices 22 managed by the managed job execution server 18. The managed device information includes a job execution server ID, a device ID, a serial number, an IP address, a MAC address, a model name, and a registration date and time as items.

The device ID is an example of identification information that identifies the device 22. The serial number is the serial number of the device 22. The IP address is the IP address of the device 22. The MAC address is the MAC address of the device 22. The model name is the model name of the device 22. The registration date and time is the date and time when the device 22 is registered in the centralized management server 16 as a managed device.

Further, the job log information is information related to the job log of one or more devices 22 managed by the management target job execution server 18. The job log information includes a job execution server ID, a device ID, a job ID, a start time, and an end time as items. The job ID is an example of identification information that identifies a job executed by the device 22. The start time is the start time of the job executed by the device 22. The end time is the end time of the job executed by the device 22.

As shown in FIG. 7, the centralized management server 16 holds job execution server information of all managed job execution servers 18 and managed device information of all devices 22 managed by the managed job execution server 18. To do. The mapping information of the job execution server 18 and the device 22 is represented by the job execution server information and the managed device information. The mapping information of the job execution server 18 and the device 22 is information indicating which job of the device 22 should be executed by which job execution server 18.

FIG. 8 is a diagram illustrating an example of management data managed by the data management unit 82 of the job execution server 18. As shown in FIG. 8, the job execution server 18 holds the managed device information, the device-job execution server mapping information, and the job log information as management data.

The managed device information is information about one or more devices 22 managed by the job execution server 18. The managed device information includes a device ID, a serial number, an IP address, a MAC address, a model name, and a registration date and time as items. The job log information is information related to the job log of one or more devices 22 managed by the job execution server 18.

Further, the device-job execution server mapping information is mapping information representing the device 22 assigned to all the job execution servers 18 managed by one centralized management server 16. The device-job execution server mapping information has a device serial number, a job execution server IP address, a job execution server host name, and a priority as items.

The device serial number is the serial number of the device 22. The job execution server IP address is the IP address of the job execution server 18 to which the device is allocated. The job execution server host name is the host name of the job execution server 18 to which the device is allocated. The priority is the priority of the mapping information.

As shown in FIG. 8, the job execution server 18 includes the managed device information of the device 22 which is the managed device managed by itself, and all the job execution servers 18 and the device 22 managed by the same centralized management server 16. Holds the mapping information of.

Further, FIG. 9 is a diagram illustrating an example of management data managed by the data management unit 92 of the device 22. As shown in FIG. 9, the device 22 holds the connection destination job execution server information as management data. The connection-destination job execution server information holds the job execution server IP address, the job execution server host name, and the priority.

The job execution server IP address is the IP address of the job execution server 18 to which the device 22 is assigned. The job execution server host name is the host name of the job execution server 18 to which the device 22 is assigned. The job execution server IP address and the job execution server host name are examples of connection destination settings indicating the job execution server 18 to which the device 22 is connected. The priority is the priority of the setting of the connection destination.

<Processing>
Next, the processing of the information processing system 1 according to the present embodiment will be described. FIG. 10 is a processing schematic diagram of an example of the information processing system according to the present embodiment. The centralized management server 16 is arranged for each customer. Further, as shown in FIG. 10, the job execution server 18 to be managed by one centralized management server 16 can be arranged across a plurality of regions. In the example of FIG. 10, "Job execution server A1" and "Job execution server A2" are arranged in "Region 1", and "Job execution server A3" is arranged in "Region 2".

In addition, since the customer virtual networks of the region (for example, between “Region 1 Customer A Env.” And “Region 2 Customer A Env.” In FIG. 10) are connected by VPN (Virtual Private Network), they are bidirectional. Communication is possible. Further, since the customer virtual network of the region and the customer's on-premises environment 20 are also connected by VPN, bidirectional communication is possible.

As shown in FIG. 10, the entire managed system of the centralized management server 16 arranged for each customer is managed by the service management tool 14. The service management tool 14 is equipped with various functions related to life-and-death monitoring of services, automation of service operations, and efficiency improvement. In this embodiment, the service management tool 14 is responsible for the autoscale orchestration of the job execution server 18.

The service management tool 14 calls the resource management API 12 to provision / deprovision the job execution server 18 when auto-scaling such as scale-out or scale-in of the job execution server 18 is required.

The provisioning in this embodiment is, for example, to generate an instance of the job execution server 18. Deprovisioning is to restore what was provisioned, for example, to destroy an instance of the job execution server 18.

<< Scale-out processing >>
FIG. 11 is a sequence diagram of an example of processing until a scale-out processing request is transmitted to the service management tool 14 when the scale-out processing is executed.

The sequence diagram shown in FIG. 11 shows an example in which the job execution server 18 detects the match of the scale-out processing conditions. For example, the monitoring unit 84 of the job execution server 18 "when the number of jobs per unit time is larger / less than xxx", "when the number of devices 22 is larger / less than xxx", and "time required for user authentication is xxx". Scale-out / scale-in processing conditions such as "when larger / less" and "when CPU and memory consumption are larger / less than xxx" can be set.

The monitoring unit 84 of the job execution server 18 that has detected the match of the scale-out processing condition in step S10 notifies the data management unit 82 that the match of the scale-out processing condition has been detected. Further, in step S12, the monitoring unit 84 requests the function execution unit 80 for scale-out processing.

In steps S14 to S18, a scale-out processing request is made from the function execution unit 80 of the job execution server 18 to the function execution unit 60 of the centralized management server 16. In step S20, the function execution unit 60 acquires the job execution server information of the scale-out target job execution server 18 for which the scale-out processing request has been made from the data management unit 62.

The job execution server information acquired in step S20 includes the customer ID, region ID, and subnet ID of the job execution server 18 to be scaled out. In steps S22 to S24, the function execution unit 60 specifies a customer ID, a region ID, and a subnet ID, and makes a scale-out processing request to the service management tool 14.

As a result, the service management tool 14 can receive the scale-out processing request for creating an instance of the new job execution server 18 as a resource of the customer ID, the region ID, and the subnet ID specified in the scale-out processing request.

The sequence diagram shown in FIG. 11 shows an example in which the job execution server 18 detects the match of the scale-out processing conditions. However, as shown in the sequence diagram of FIG. 12, the centralized management server 16 detects the match of the scale-out processing conditions. You may do so. FIG. 12 is a sequence diagram of an example of processing until a scale-out processing request is transmitted to the service management tool 14 when the scale-out processing is executed.

The monitoring unit 68 of the centralized management server 16 that detects the match of the scale-out processing condition in step S30 notifies the data management unit 62 that the match of the scale-out processing condition has been detected. Further, in step S31, the monitoring unit 68 notifies the administrator terminal 30 to confirm whether or not the scale-out process is executed. The administrator who receives the notification can instruct whether or not the scale-out process is executed.

Proceeding to step S32, the monitoring unit 68 receives an instruction from the administrator terminal 30 to execute the scale-out process OK / NG by the administrator. Upon receiving the instruction of the administrator to execute the scale-out process OK, the monitoring unit 68 performs the process after step S33. When the administrator receives an instruction of NG to execute the scale-out process, the monitoring unit 68 does not perform the process after step S33. FIG. 12 shows an example in which the administrator has received an instruction to execute the scale-out process.

Upon receiving the instruction of OK to execute the scale-out process by the administrator, the monitoring unit 68 proceeds to step S33 and requests the function execution unit 60 for the scale-out process. In step S34, the function execution unit 60 acquires the job execution server information of the scale-out target job execution server 18 for which the scale-out processing request has been made from the data management unit 62.

The job execution server information acquired in step S34 includes the customer ID, region ID, and subnet ID of the job execution server 18 to be scaled out. In steps S35 to S36, the function execution unit 60 specifies a customer ID, a region ID, and a subnet ID, and requests the service management tool 14 for scale-out processing.

As a result, the service management tool 14 can send a scale-out processing request for creating an instance of the new job execution server 18 as a resource of the customer ID, the region ID, and the subnet ID specified in the scale-out processing request. In addition, since the administrator is instructed whether or not to execute the scale-out process, it is possible to prevent the system cost from rising unacceptably due to the scale-out. Furthermore, in a state where the load is temporarily increased / decreased by chance (such as when the load is temporarily increased / decreased due to the influence of a system failure), auto-scaling that should not be performed originally It can be suppressed from occurring.

The processing of steps S31 to S32 in FIG. 12 is not essential, and after detecting the matching of the scale-out processing conditions in step S30 as shown in the sequence diagram of FIG. 11, the scale-out processing to the function execution unit 60 in step S33. You may make a request.

Further, the scale-out processing request in step S12 of FIG. 11 and the scale-out processing request in step S33 of FIG. 12 are the number of instances of the job execution server 18 (jobs to be expanded) generated according to the content of the scale-out processing conditions and the degree of matching. The number of execution servers 18) may be specified.

FIG. 13 is a sequence diagram of an example of processing until the service management tool 14 returns the result of the scale-out processing to the centralized management server 16 when the scale-out processing is executed.

In steps S40 to S42, the scale processing execution unit 50 of the service management tool 14 receives the scale-out processing request from the centralized management server 16. The scale processing execution unit 50 uses the resource management API 12 to generate an instance of a new job execution server 18 having the same customer ID, region ID, and subnet ID as the job execution server 18 to be scaled out.

Proceeding to step S46, the scale processing execution unit 50 acquires the job execution server information of the new job execution server 18 by using the resource management API 12. In steps S48 to S50, the centralized management server 16 is notified by the service management tool 14 of old and new job execution server information before and after autoscale.

FIG. 14 is a sequence diagram of an example of processing until the result of the scale-out processing is returned to the job execution server 18 at the time of executing the scale-out processing.

In steps S60 to S62, the function execution unit 60 of the centralized management server 16 is notified of the old and new job execution server information before and after the autoscale from the service management tool 14. In step S64, the device 22 that is the managed device is divided between the job execution server 18 to be scaled out and the new job execution server 18, and reallocation is performed.

The reassignment of the device 22 performed in step S64 may be performed according to the allocation rule of the managed device set by the administrator. The administrator can set the following allocation rules for managed devices according to the operation of the system.

As an example of the allocation rule of the managed device, it is conceivable to aggregate the job log information of the job execution server 18 so that the device 22 that generates a job having a long required time is not centrally allocated. Further, as an example of the allocation rule of the managed device, it is conceivable to allocate the device 22 so that the number of each model is about the same. Further, as an example of the allocation rule of the managed device, it is conceivable to preferentially replace the device 22 having a new registration date and time. By the process of step S64, the management data of FIG. 7 is updated based on the result of reallocation.

In steps S66 to S68, the job execution server 18 is notified from the centralized management server 16 of the managed device information as shown in FIG. 8 and the device-job execution server mapping information. The job execution server 18 notified of the managed device information as shown in FIG. 8 and the device-job execution server mapping information from the centralized management server 16 executes the processing of the flowchart as shown in FIG. 15, for example.

FIG. 15 is a flowchart of an example of processing until the setting of the job execution server 18 to which the device 22 is connected is updated when the scale-out processing is executed. In step S70, the function execution unit 80 of the job execution server 18 receives the managed device information as shown in FIG. 8 and the device-job execution server mapping information from the centralized management server 16.

Proceeding to step S71, the function execution unit 80 compares the existing managed device information read from the management data holding unit 88 with the new managed device information received from the centralized management server 16, and has a new managed device. Judge whether or not. If there is a new managed device, the function execution unit 80 proceeds to step S72 and notifies the device 22, which is the new managed device, of the connection destination job execution server information of FIG. As a result, the setting of the connection destination of the device 22 is updated to the reassigned job execution server 18. If there is no new managed device, the function execution unit 80 skips the process of step S72.

In step S73, the function execution unit 80 updates the management data managed by the data management unit 82 with new managed device information received from the centralized management server 16 and device-job execution server mapping information.

In case the notification to the device 22 fails in step S72, for example, as shown in FIG. 6, the connection destination of the device 22 is set by triggering the job processing request from the device 22 side to the job execution server 18. You may try to update.

FIG. 16 is a sequence diagram of an example of a process of updating the connection destination setting of the device 22 triggered by a job processing request from the device 22 side to the job execution server 18. In the sequence diagram of FIG. 16, the connection destination of the device 22 before reallocation is the job execution server 18, and the connection destination of the device 22 after reassignment is the job execution server 18a. It is assumed that the management data of the job execution server 18 is updated based on the result of reallocation.

In steps S80 to S82, the function execution unit 80 of the job execution server 18 receives the job processing request from the device 22. Proceeding to step S84, the function execution unit 80 refers to the managed device information of FIG. 8, and if the device 22 that made the job processing request is included in its own managed device, performs processing according to the job processing request. .. Note that FIG. 16 shows an example in which the device 22 that made the job processing request is not included in the own managed device.

Proceeding to step S86, the function execution unit 80 refers to the device-job execution server mapping information of FIG. 8 and reads out the new connection destination job execution server information of the device 22 that has made the job processing request. In steps S88 to S92, the function execution unit 80 transmits new connection destination job execution server information to the device 22 that has made the job processing request.

In step S94, the function execution unit 90 updates the management data managed by the data management unit 92 with the new connection destination job execution server information received from the job execution server 18. As a result, the setting of the connection destination of the device 22 is updated to the reassigned job execution server 18a. Proceeding to step S96, the device 22 can send a job processing request to the reassigned job execution server 18a based on the updated connection destination setting.

<< Scale-in processing >>
FIG. 17 is a sequence diagram of an example of processing until a scale-in processing request is transmitted to the service management tool 14 when the scale-in processing is executed.

Although the sequence diagram shown in FIG. 17 shows an example in which the job execution server 18 detects the match of the scale-in processing conditions, the centralized management server 16 may detect the match of the scale-in processing conditions. ..

The monitoring unit 84 of the job execution server 18 that has detected the match of the scale-in processing condition in step S100 notifies the data management unit 82 that the match of the scale-in processing condition has been detected. Further, in step S102, the monitoring unit 84 requests the function execution unit 80 for scale-in processing.

In steps S104 to S108, a scale-in processing request is made from the function execution unit 80 of the job execution server 18 to the function execution unit 60 of the centralized management server 16. In step S110, the function execution unit 60 acquires the job execution server information of the scale-in target job execution server 18 that has made the scale-in processing request from the data management unit 62.

The job execution server information acquired in step S110 includes the customer ID, region ID, and subnet ID of the job execution server 18 to be scaled in. In step S112, the managed device of the scale-in target job execution server 18 is integrated with the managed device of the job execution server having the same customer ID, region ID, and subnet ID as the scale-in target job execution server 18. The management data of FIG. 7 is updated based on the result. In steps S114 to S116, the centralized management server 16 notifies each job execution server 18 of new managed device information and device-job execution server mapping information.

The job execution server 18 notified of the new managed device information and the device-job execution server mapping information from the centralized management server 16 receives the management data managed by the data management unit 82 from the centralized management server 16 as a new management target. Update with device information and device-job execution server mapping information. Further, the job execution server 18 notifies the device 22, which is a new managed device, of the connection destination job execution server information of FIG. As a result, the setting of the connection destination of the device 22 is updated to the reassigned (integrated) job execution server 18.

In steps S118 to S120, the function execution unit 60 specifies the job execution server 18 to be scaled in and makes a scale-in processing request to the service management tool 14. As a result, the service management tool 14 can receive the scale-in processing request for destroying the instance of the job execution server 18 to be scaled-in.

FIG. 18 is a sequence diagram of an example of processing until the service management tool 14 performs the scale-in processing when the scale-in processing is executed.

In steps S140 to S142, the scale processing execution unit 50 of the service management tool 14 receives the scale-in processing request from the centralized management server 16. The scale processing execution unit 50 uses the resource management API 12 to destroy the instance of the job execution server 18 to be scaled in. In this way, the instance of the job execution server 18 to be scaled in can be destroyed.

In case the notification to the device 22 fails, for example, as shown in FIG. 19, the setting of the connection destination of the device 22 is updated by triggering the job processing request from the device 22 side to the job execution server 18. It may be.

FIG. 19 is a sequence diagram of an example of processing for updating the setting of the connection destination of the device 22 triggered by a job processing request from the device 22 side to the job execution server 18. In the sequence diagram of FIG. 19, the connection destination of the device 22 before reassignment is the job execution server 18, and the connection destination of the device 22 after reallocation is the job execution server 18b. It is assumed that the instance of the job execution server 18 has been destroyed by the scale-in process. Further, it is assumed that the management data of the job execution server 18b is updated based on the result of reallocation.

In step S180, the device 22 tries to send the job processing request to the job execution server 18, but fails because the job execution server 18 does not exist. In step S182, the device 22 refers to the connection destination job execution server information of FIG. 9 and transmits a job processing request to the job execution server 18b having the next priority.

In steps S182 to S184, the function execution unit 80 of the job execution server 18b receives the job processing request for which the priority of the second or lower rank is specified from the device 22. Proceeding to step S186, the function execution unit 80 confirms the managed device information of FIG. Further, in step S188, the function execution unit 80 refers to the device-job execution server mapping information in FIG. 8 and reads out the new connection destination job execution server information of the device 22 that has made the job processing request. In steps S190 to S194, the function execution unit 80 transmits new connection destination job execution server information to the device 22 that has made the job processing request.

Proceeding to step S196, the function execution unit 90 updates the management data managed by the data management unit 92 with the new connection destination job execution server information received from the job execution server 18b. As a result, the setting of the connection destination of the device 22 is updated to the reassigned job execution server 18b. Proceeding to step S198, the device 22 can send a job processing request to the reassigned job execution server 18b based on the updated connection destination setting.

Although FIG. 19 shows an example in which the job processing request in steps S182 and S198 is executed on the same job execution server 18b, the job processing request in step S198 is based on the updated connection destination setting. It may be performed in addition to 18b.

<Summary>
According to the information processing system 1 according to the present embodiment, in the processing at the time of auto-scaling of the job execution server to which the management target device is assigned, the management target device is reassigned to the job execution server and the connection destination of the management target device. Can be reset and done.

The present invention is not limited to the above-described embodiment disclosed in detail, and various modifications and modifications can be made without departing from the scope of claims. Each function of the present embodiment described above can be realized by one or more processing circuits. Here, the "processing circuit" in the present specification is a processor programmed to execute each function by software such as a processor implemented by an electronic circuit, or a processor designed to execute each function described above. It shall include devices such as ASIC (Application Specific Integrated Circuit), DSP (digital signal processor), FPGA (field programmable gate array) and conventional circuit modules.

The job execution server 18 is an example of the data processing execution server described in the claims. The service management tool 14 is an example of a management tool. The scale processing execution unit 50 is an example of a scale processing execution means. The function execution unit 60 is an example of a function execution means. The data management unit 62 is an example of data management means. The monitoring unit 68 is an example of monitoring means.

1 Information processing system 10 Cloud environment 12 Resource management API
14 Service management tool 16 Centralized management server 18 Job execution server 20 On-premises environment 22 Equipment 30 Administrator terminal 40 Network

Japanese Unexamined Patent Publication No. 2015-162066

Claims (10)

An information processing system having a centralized management server that manages the allocation of one or more managed devices to one or more data processing execution servers, and a management tool that increases or decreases the number of the data processing execution servers.
The management tool
Scale processing execution means that increases or decreases the number of data processing execution servers based on a processing request for increasing or decreasing the number of data processing execution servers, and transmits the result of the increase or decrease in the number of data processing execution servers to the centralized management server. ,
Have,
The centralized management server
Based on the result of the increase / decrease in the number of the data processing execution servers, the managed device is reassigned to the data processing execution server whose number has been increased / decreased, and the result of the reallocation of the managed device is the data processing execution server. A function execution means for updating the connection destination setting of the managed device based on the result of reallocation of the managed device.
Information processing system with. The centralized management server further
A data management means for managing a group of data processing execution servers,
Have,
The information processing system according to claim 1, wherein the function executing means reallocates the managed device to the data processing execution server in the same group as the data processing execution server whose number has been increased or decreased. The centralized management server further
A monitoring means that monitors the matching of processing conditions that increase or decrease the number of data processing execution servers, and when it detects the matching of the processing conditions, requests the function executing means for processing that increases or decreases the number of data processing execution servers.
Have,
When the monitoring means detects that the processing conditions are met, the monitoring means notifies the administrator terminal, and according to an instruction from the administrator from the administrator terminal, requests for processing to increase or decrease the number of the data processing execution servers. The information processing system according to claim 1 or 2, wherein the processing performed by the executing means and the processing not performed are switched. The information processing system according to claim 3, wherein the function executing means reallocates the managed device according to an allocation rule of the managed device set by the administrator. The information processing system according to claim 3 or 4, wherein the monitoring means performs the monitoring in accordance with processing conditions for increasing or decreasing the number of the data processing execution servers set by the administrator. The function executing means transmits the result of reallocating the managed device to all the data processing execution servers managed by the centralized management server to each of the data processing execution servers managed by the centralized management server. The information processing system according to any one of claims 1 to 5, wherein the information processing system is characterized by the above. The data processing execution server is the management target before reassignment based on the result of reallocating the managed device to all the data processing execution servers managed by the centralized management server received from the centralized management server. The information processing system according to claim 6, wherein the device is notified of the connection destination of the data processing execution server after reallocating. A centralized management server that manages the allocation of one or more managed devices to one or more data processing execution servers.
The number was increased or decreased based on the result of the increase or decrease in the number of the data processing execution servers received from the management tool for increasing or decreasing the number of the data processing execution servers based on the processing request for increasing or decreasing the number of the data processing execution servers. The management target device is reassigned to the data processing execution server, the result of the reassignment of the management target device is transmitted to the data processing execution server, and the connection destination setting of the management target device is set by the management target device. Function execution means to update based on the result of reallocation of
Centralized management server with. There is a management method executed by a centralized management server that manages the allocation of one or more managed devices to one or more data processing execution servers.
A step of receiving the result of increasing / decreasing the number of the data processing execution servers from the management tool for increasing / decreasing the number of the data processing execution servers based on the processing request for increasing / decreasing the number of the data processing execution servers.
Based on the result of the increase / decrease in the number of data processing execution servers, the step of reallocating the managed device to the data processing execution server whose number has been increased / decreased, and
A step of transmitting the result of reallocating the managed device to the data processing execution server and updating the setting of the connection destination of the managed device based on the result of reallocating the managed device.
Management method with. To a centralized management server that manages the allocation of one or more managed devices to one or more data processing execution servers
A step of receiving the result of increasing or decreasing the number of data processing execution servers from a management tool for increasing or decreasing the number of data processing execution servers based on a processing request for increasing or decreasing the number of data processing execution servers.
A step of reallocating the managed device to the data processing execution server whose number has been increased or decreased based on the result of the increase or decrease in the number of data processing execution servers.
A step of transmitting the result of reallocating the managed device to the data processing execution server and updating the setting of the connection destination of the managed device based on the result of reallocating the managed device.
A program to execute.

Images