JP2011238073A - Server group integrated management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a server group integrated management system capable of improving convenience of a user who uses services offered by a plurality of servers.SOLUTION: A server group integrated management system 30 connected to a plurality of virtual servers 11 which constitute a server group 10 and a terminal device 20 comprises: a storage section 42 to store compatible information between a specific environment which is an input/output environment specific to each of the plurality of the virtual servers 11 and a common environment which is a common input/output environment to use each virtual server 11 at a terminal device 20; and a control section 41 to mutually convert an input/output of each of the plurality of the virtual servers 11 and the input/output at the terminal device based on the compatible information stored in the storage section 42.

Description

  The present invention relates to a server group integrated management system for managing a user's usage environment for a server group composed of a plurality of servers.

  In recent years, cloud computing that can use various services via a network has been rapidly spreading. In this cloud computing, users can use various services without spending time and money building a server, and easily change the type and amount of various services according to their needs. can do.

  Along with the spread of such cloud computing, many operators have started to provide various types of cloud computing servers for a fee, and users can select their own needs from these various servers. A server that matches the budget or the like can be selected to use the service (for example, paragraph 0023 and FIG. 1 of Patent Document 1). Alternatively, some users have a cloud computing server in their company, and this server is used in various departments within the company.

JP 2010-050988 A

  However, since there is no standard for uniformly managing cloud computing specifications and service contents, the servers provided by the operators and the servers and users provided by these operators are not Services are provided through different interfaces between the servers provided in. Therefore, when the same user wants to use the services provided by the plurality of servers, it is necessary to use the servers via a plurality of interfaces that are different for each server.

  This invention is made in view of the above, Comprising: It aims at providing the server group integrated management system which can improve the convenience of the user who utilizes the service provided by several servers. .

  In order to solve the above-described problems and achieve the object, the server group integrated management system according to claim 1 includes a plurality of servers constituting the server group and a network provided by each of the plurality of servers. A server group integrated management system that is communicably connected via a network to a terminal device for using a service, and a unique environment that is an input / output environment unique to each of the plurality of servers; Compatibility information storage means for storing compatibility information regarding compatibility with a common environment, which is a common input / output environment for using each of the plurality of servers in the terminal device, and each of the plurality of servers Conversion means for mutually converting the input / output and the input / output in the terminal device based on the compatibility information stored in the compatibility information storage means When the input / output from the terminal device to any one of the plurality of servers is performed in the common input / output environment, the conversion unit converts the compatibility information stored in the compatibility information storage unit into the compatibility information. Based on this, the input / output from the terminal device is converted into the input / output in the input / output environment specific to the server where the input / output is performed, and the converted input / output is the server from which the input / output from the terminal device is performed The compatibility information stored in the compatibility information storage means when input / output from any of the plurality of servers to the terminal device is performed in an input / output environment unique to the server. The input / output from the server is converted into the input / output in the common input / output environment, and the converted input / output is transmitted to the terminal device.

  According to the server group integrated management system of claim 1, since input / output in each of the plurality of servers and input / output in the terminal device are mutually converted, services of the plurality of servers are used via the terminal device. Users can use the service through the common environment without being aware of the unique environments of these multiple servers, so the user has to learn the knowledge about the unique environment of each server. Can be omitted, and the convenience of users using cloud computing can be greatly improved.

1 is a block diagram functionally conceptually showing a network system including a server group integrated management system according to the present invention. It is a figure which shows the structural example of user basic information. It is a figure which shows the structural example of cloud basic information. It is a figure which shows the structural example of utilization condition information. It is a figure which shows the structural example of input / output information. It is a flowchart of a virtual server starting process. It is a figure which illustrates the server page of UI for a user information display. It is a figure which illustrates the service page of UI for a user information display. It is a figure which illustrates UI for a server addition request. It is a figure which illustrates UI for a service addition request. It is a flowchart of a virtual server utilization process. It is a flowchart of a virtual server stop process. It is a flowchart of a virtual server restart process. It is a flowchart of a virtual server monitoring process.

  Embodiments of a server group integrated management system according to the present invention will be described below in detail with reference to the accompanying drawings. First, after describing the configuration of the present embodiment, the processing of the present embodiment will be described, and finally, a modified example of the present embodiment will be described. However, the present invention is not limited by the present embodiment.

(Constitution)
First, the configuration of the network system including the server group integrated management system according to the present embodiment will be described. FIG. 1 is a functional block diagram showing a network system including a server group integrated management system according to the present embodiment. The network system 1 includes a server group 10, a terminal device 20, a server group integrated management system 30, and a communication network 100. The terminal device 20 and the server group integrated management system 30 are mutually connected via the communication network 100. The servers included in the server group 10 and the server group integrated management system 30 are communicably connected to each other.

(Configuration-Server group)
The server group 10 provides services to the terminal device 20 via the communication network 100. A typical form of this service corresponds to what is called a cloud service. Cloud services include what are called SaaS (Software as a Service), PaaS (Platform as a Service), and IaaS (Infrastructure as a Service). However, services provided by the server group 10 are not limited to services called cloud services, and services provided by various computer systems such as on-demand computing, utility computing, or ubiquitous computing. Including. Hereinafter, a cloud computing system for providing a cloud service is simply referred to as a cloud.

  The server group 10 includes a plurality of cloud servers (physical servers) constituting a plurality of clouds, and a virtual server (VM: Virtual Machine, instance) 11 is configured on the cloud server. As a cloud that provides a cloud server, there are a cloud provided by a person different from the user (hereinafter referred to as a public cloud) and a cloud provided by the user himself (hereinafter referred to as a private cloud). The cloud server provided by both of them is configured. That is, the server group integrated management system 30 provides a higher-order cloud (hybrid cloud) configured by integrating a public cloud and a private cloud. However, the cloud may be configured from a cloud server provided by only one of the public cloud and the private cloud.

  Each virtual server 11 includes an application application control client (hereinafter referred to as application control client) 12, an application application monitoring client (hereinafter referred to as application monitoring client) 13, a plurality of applications 14, and a plurality of application dedicated data areas (hereinafter referred to as dedicated data areas). ) 15.

  The application control client 12 defines and maintains the state of the virtual server 11 in which the application control client 12 is installed. The application control client 12 installs and sets each application 14 in the virtual server 11, adds and deletes users, and Control updates. As the application control client 12, a client (for example, a PPP client) in a known system management tool (for example, a PPP) can be used.

  The application monitoring client 13 monitors the status of the virtual server 11 on which the application monitoring client 13 is installed and the applications 14 installed on the virtual server 11, and collects information on the virtual server 11 and each application 14. , Anomaly detection, and failure and recovery notification. As the application monitoring client 13, a client (for example, Zabbix client) in a known system monitoring tool (for example, Zabbix) can be used.

  The plurality of applications 14 are applications provided in a so-called cloud application layer, and are used for creating Web server construction, business system and electronic commerce server construction, and database server construction application office document creation. Various applications provided for various purposes such as applications and applications for software development are applicable.

  The dedicated data area 15 is an area for storing data related to each application 14, and here is a virtual disk constructed on a recording area of a physical server. In particular, the dedicated data area 15 is set as a dedicated data area for each application 14.

(Configuration-terminal device)
The terminal device 20 is a device that communicates with the server group integrated management system 30 via the communication network 100 in order to use a service provided by each virtual server 11 of the server group 10. The terminal device 20 performs communication with the server group integrated management system 30, and therefore displays a browser for transmitting and receiving information using a predetermined communication protocol (here, http and https) and various information. Monitor, an input unit for inputting various information, and a network interface (hereinafter referred to as network IF). However, since the terminal device 20 can be configured as a known personal computer, a detailed description thereof will be omitted.

(Configuration-Server group integrated management system)
The server group integrated management system 30 is a system that manages the servers of the server group 10. In particular, the server group integrated management system 30 includes a plurality of input / output environments (hereinafter referred to as unique environments) unique to each virtual server 11 of the server group 10 and a plurality of terminal devices 20. This system performs compatibility processing with a common input / output environment (hereinafter referred to as a common environment) for using each of the virtual servers 11. Here, the input / output environment is a so-called interface, and includes a software interface related to an information input / output procedure and format, and a user interface related to an information input / output display method.

  The server group integrated management system 30 includes a main control server 40, an application control server (hereinafter referred to as an application control server) 50, an application monitoring server (hereinafter referred to as an application monitoring server) 60, and a DNS server (Domain Name System server) 70. .

(Configuration-Server group integrated management system-Main control server)
First, the configuration of the main control server 40 will be described. The main control server 40 is a server that provides a central function of compatibility processing between the specific environment and the common environment. In terms of functional concept, the control unit 41, the storage unit 42, and the network IF 43 are connected via a bus. Connected and configured.

  The control unit 41 is a conversion unit that converts the input / output in each of the plurality of servers and the input / output in the terminal device 20 based on the compatibility information stored in the storage unit 42. The control unit 41 is functionally conceptually configured to include a start processing unit 41a, a use processing unit 41b, a stop processing unit 41c, a restart processing unit 41d, and a monitoring processing unit 41e. The activation processing unit 41a is an activation processing unit that controls virtual server activation processing to be described later. The usage processing unit 41b is usage processing means for controlling virtual server usage processing, which will be described later. The stop processing unit 41c is a stop processing unit that controls virtual server stop processing to be described later. The restart processing unit 41d is restart processing means for controlling virtual server restart processing to be described later. The monitoring processing unit 41e is monitoring processing means for controlling virtual server monitoring processing to be described later. The function of each unit will be described together with each process.

  Specifically, the control unit 41 includes a CPU (Central Processing Unit) and various programs interpreted on the CPU (control programs such as OS, various processing procedures, and the like. For example, J2EE. And a cache memory for storing required programs and required data. The various programs interpreted and executed on the CPU include a server group management program. The server group management program is stored in an arbitrary storage medium including a CD-ROM and a DVD, and then installed and stored. The substantial function of the control unit 41 is configured by being stored in the unit 42 in a nonvolatile manner and being interpreted and executed by the CPU.

  The storage unit 42 includes a mutual environment between a unique environment that is an input / output environment unique to each of the plurality of servers and a common environment that is a common input / output environment for using each of the plurality of servers in the terminal device 20. It is a compatibility information storage means for storing compatibility information regarding compatibility. The storage unit 42 is a storage unit that stores information and parameters necessary for various processes in a nonvolatile manner, and is configured by, for example, an HD (Hard Disk). The storage unit 42 includes a user basic information DB 42a, a cloud basic information DB 42b, a usage status information DB 42c, and an input / output information DB 42d in terms of functional concept.

  The user basic information DB 42a in FIG. 1 is user basic information storage means for storing basic information about users (hereinafter referred to as user basic information). The user basic information includes, for example, an item “user ID”, an item “user name”, and an item “password”, as shown in the configuration example of FIG. 2, and associates information corresponding to these items with each other. It is configured. Information corresponding to the item “user ID” is user identification information for uniquely identifying a user. The information corresponding to the item “user name” is the name or name of the user. Information corresponding to the item “password” is a password for authentication when the user logs in to the server group integrated management system 30. The basic user information is registered by an administrator of the system when the user registers for use in the server group integrated management system 30.

  The cloud basic information DB 42b in FIG. 1 is a cloud basic information storage unit that stores basic information about the cloud (hereinafter referred to as cloud basic information). For example, as shown in the configuration example of FIG. 3, the cloud basic information includes an item “cloud ID”, an item “cloud name”, an item “IP address”, an item “server type”, and an item “cloud side service name”. And information corresponding to these items are associated with each other. Information corresponding to the item “cloud ID” is cloud identification information for uniquely identifying each cloud. The information corresponding to the item “cloud name” is the name of each cloud. The information corresponding to the item “IP address” is an IP address for accessing each cloud when the cloud is first used. The information corresponding to the item “server type” is the type of server that can be used in each cloud. The information corresponding to the item “cloud side service name” is a name of a service that can be used in each cloud, and is a name given on the cloud side. The basic cloud information is registered by an administrator of the system when registering a cloud that can be used by the server group integrated management system 30.

  The usage status information DB 42c in FIG. 1 is usage status information storage means for storing information (hereinafter referred to as usage status information) regarding usage status by each user of a server provided by each cloud. For example, as shown in the configuration example of FIG. 4, the usage status information includes an item “user ID”, an item “cloud ID”, an item “cloud server name”, an item “user server name”, and an item “IP address”. ”,“ Server type ”,“ Cloud service name ”,“ User service name ”,“ Disk size ”, and“ Status ”, and the information corresponding to each of these items It is configured. The information corresponding to the item “user ID”, the item “cloud ID”, the item “server type”, and the item “cloud side service name” is the same as the information corresponding to the same item name in the user basic information or the cloud basic information. is there. The information corresponding to the item “cloud-side server name” is the name of the virtual server 11 built in the cloud and the name (host name) assigned on the cloud side. The information corresponding to the item “user-side server name” is the name of the virtual server 11 built in the cloud, and is a name given on the user side. The item “IP address” is an IP address assigned on the cloud side to the virtual server 11 constructed in the cloud. Information corresponding to the item “user-side service name” is a name of a service that can be used in each cloud, and is a name given by the user. Information corresponding to the item “disk size” is the size of the dedicated data area 15 allocated to the service provided by each cloud. The information corresponding to the item “status” is the current usage status (status) of the server. The basic cloud information is registered in a virtual server start process and a virtual server restart process described later, and updated as necessary in a virtual server use process, a virtual server stop process, or a virtual server monitoring process described later.

  The input / output information DB 42d shown in FIG. 1 stores input / output information for storing information on input / output formats and contents in a common environment and information on input / output formats and contents in a specific environment (hereinafter referred to as input / output information) Means. This input / output information includes, for example, an item “cloud ID”, an item “user side input / output”, and an item “cloud side input / output” as shown in the configuration example of FIG. Are related to each other. The information corresponding to the item “cloud ID” is the same as the information corresponding to the same item name in the cloud basic information. Information corresponding to the item “user-side input / output” is information regarding the format and contents of input / output in the common environment, such as “start”, “stop”, “delete”, and the like of the virtual server 11 and application 14. The information corresponding to the item “cloud side input / output” is information related to the format and contents of input / output in the specific environment, for example, to execute “start”, “stop”, “delete”, etc. of the virtual server 11 or the application 14. This is information for specifying the Web API. These pieces of input / output information are registered by an administrator of the system when registering a cloud that can be used by the server group integrated management system 30.

  The network IF 43 in FIG. 1 is a communication unit for performing communication via a network, and is configured as a network board, for example.

(Configuration-Server group integrated management system-Application control server)
Next, the configuration of the application control server 50 in FIG. 1 will be described. The application control server 50 defines and maintains the state of the virtual server 11, and is an application control unit that controls installation, setting, addition and deletion of users, and update of each application 14 with respect to the virtual server 11. is there. For this application control, known application control software (for example, Puppet) can be used. In addition, unless otherwise specified, the application control server 50 can be configured in the same manner as a normal Web server, and thus description thereof is omitted.

(Configuration-Server group integrated management system-Application monitoring server)
Next, the configuration of the application monitoring server 60 in FIG. 1 will be described. The application monitoring server 60 monitors the status of the virtual server 11 and each application 14 installed in the virtual server 11, collects information on the virtual server 11 and each application 14, detects an abnormality, and troubles and recovery It is an application monitoring means for performing notification. For this application monitoring, known application monitoring software (for example, Zabbix) can be used. In addition, unless otherwise specified, the application monitoring server 60 can be configured in the same manner as a normal Web server, and thus the description thereof is omitted.

(Configuration-Server group integrated management system-DNS server)
Next, the configuration of the DNS server 70 in FIG. 1 will be described. The DNS server 70 is name resolution means for performing name resolution. The DNS server 70 includes a database configured by associating a server IP address assigned on the cloud side with a URL (Uniform Resource Locator) of the server. Except as otherwise noted, the DNS server 70 can be configured in the same manner as a normal DNS server, and thus the description thereof is omitted.

(Configuration-communication network)
The communication network 100 in FIG. 1 is a WAN (Wide Area Network), which is typically the Internet, but may include a dedicated communication line or a LAN (Local Area Network).

(processing)
Next, various processes performed in the network system 1 configured as described above will be described. This process is roughly divided into a virtual server start process, a virtual server use process, a virtual server stop process, a virtual server restart process, and a virtual server monitoring process. Hereinafter, each process will be described sequentially. However, in the following description, it is assumed that each process is performed at an arbitrary timing except for a specially described timing, and the process is performed by the control unit 41 except for a subject to be specifically described. “Step” is abbreviated as “S”.

(Processing-Virtual server startup processing)
First, the virtual server activation process will be described. FIG. 6 is a flowchart of the virtual server activation process. In this process, the user accesses the main control server 40 by designating a predetermined URL assigned to the main control server 40 in the terminal device 20, and performs a login process using the user ID and password by a known method. To log in (SA1). The control unit 41 of the main control server 40 refers to the user basic information stored in the user basic information DB 42 and performs the login process (SA2), and then uses the usage status information corresponding to the user ID from the usage status information DB 42c. Acquire and generate Web page data for displaying a part of the information included in the acquired usage status information on a predetermined UI (User Interface) in the common environment (for example, a Web application framework such as Vaadin) And the generated web page data is transmitted to the terminal device 20 (SA2). The browser of the terminal device 20 displays the UI on the monitor using the transmitted Web page data (SA3) (hereinafter, the terminal device 20 and the main control server 40 also control the main control between the terminal device 20 and the main control server 40). Every time a request is made to the server 40, the main control server 40 generates Web page data and transmits it to the terminal device 20).

  As shown in FIGS. 7 and 8, the user information display UI is configured such that two pages of “server” and “service” can be switched to each other by tags. The user starts and stops the server on the “server” page, and then adds and deletes the service on the “service” page.

  As shown in FIG. 7, the “server” page is a page for displaying a list of information about servers used by the user, starting and stopping the server, and a display area for displaying a server list. And a server addition button for adding a new server. The server list includes an item “user-side server name”, an item “IP address”, an item “status”, an item “user-side service name”, and an item “use”. Configured in association. The information corresponding to the item “user side server name”, the item “IP address”, the item “status”, and the item “user side service name” is the same as the information corresponding to the same item name of the usage status information. In the item “use”, an operation button for using the service is displayed. By viewing such a “server” page, the user can centrally grasp the virtual servers 11 activated in different clouds.

  Here, when the user selects a server addition button on the “server” page via the input unit of the terminal device 20, a server addition request is transmitted to the main control server 40 (SA3), and the main control server 40 transmits the terminal device. 20 transmits Web page data for displaying the server addition request information on a predetermined UI in the common environment (SA4), and the terminal device 20 displays the UI on the monitor (SA5). As illustrated in FIG. 9, the server addition request UI includes a server name setting area, a cloud selection area, a server type selection area, and a server addition button. The server name setting area is an area for inputting a user-side server name of a server to be added through the UI, and the user inputs a desired server name to the server name setting area. The cloud selection area is an area for selecting a cloud to be used. Here, the cloud names are displayed in a list format, and the user selects a desired cloud name from the displayed cloud names. The server type selection area is an area for displaying the type of server that can be provided by the cloud selected in the cloud selection area. Here, the server type is displayed in a list format, and the displayed type The user selects a desired type from the list.

  In this UI, when a user selects or adds a server after inputting or selecting information, a server addition request including the input or selected information is transmitted to the main control server 40 (SA5). The activation processing unit 41a of the main control server 40 acquires the IP address corresponding to the cloud name included in the server addition request transmitted from the terminal device 20 from the cloud basic information DB 42b, and performs server processing for the acquired IP address. An activation request for activating the virtual server 11 that matches the server type included in the addition request is transmitted (SA6).

  Based on this activation request, the cloud server activates the virtual server 11, dynamically assigns the cloud-side server name, IP address, and domain name to the activated virtual server 11, and the assigned cloud-side server name, etc. Is sent to the main control server 40 (SA7). The activation processing unit 41a is transmitted from the cloud, the user ID input during the login process, the cloud ID acquired from the cloud basic information as corresponding to the cloud name included in the server addition request transmitted from the terminal device 20, and The server name and IP address of the cloud side and the server type and user server name included in the server addition request transmitted from the terminal device 20 are associated with each other and stored in the usage status information DB 42c as usage status information ( SA8). In addition, the activation processing unit 41a registers the IP address and domain name transmitted from the cloud in association with each other in the DNS server 70 (SA8). By performing such processing, it is possible to perform name resolution of the activated virtual server 11 via the DNS server 70.

  As shown in FIG. 8, the “service” page is a page for displaying a list of information on services used by the user, and for adding and deleting services, and a display area for displaying a service list And a service addition button for adding a new service. The service list includes an item “user-side service name”, an item “user-side server name”, an item “IP address”, an item “status”, and an item “usage”. Configured in association. The information corresponding to these items is the same as the information corresponding to the same item name on the “server” page of FIG. By viewing such a “service” page, the user can centrally grasp the services used in different clouds.

  Here, when the user selects a service addition button on the “service” page via the input unit of the terminal device 20, a service addition request is transmitted to the main control server 40 (SA9), and the main control server 40 transmits the terminal device. 20 transmits Web page data for displaying information for service addition request on a predetermined UI in the common environment (SA10), and the terminal device 20 displays the UI on the monitor (SA11).

  As illustrated in FIG. 10, the service addition request UI includes a service name setting area, a service selection area, a disk size setting area, a server selection area, and a service addition button. The service name setting area is an area for inputting a user side service name of a service to be added through the UI, and the user inputs a desired service name to the service name setting area. The service selection area is an area for selecting a service that can be used in the server selected in the server selection area. Here, the service name on the cloud side is displayed in a list format, and the service name of the displayed service name is displayed. The user selects a service name corresponding to a desired service from among them. The disk size setting area is an area for setting the size of the dedicated data area 15 to be allocated to the service added by the UI, and the user inputs a desired size to the disk size setting area. The server selection area is an area for selecting the virtual server 11 that provides a desired service to be added through the UI, and is configured to include a pair of left and right areas, and either one (here, the left side in the figure). ) Displays the server name on the user side of the virtual server 11 activated on the “Server” page in a list format. A desired server is selected from these virtual servers 11 and either one (here) Then, the user selects a desired server by moving to the area on the right side of the figure. Each time a server is selected in this way, the control unit 41 acquires a cloud-side service name of a service that can be used in the selected server from the cloud basic information DB 42b, and puts the acquired service in a service selection area. Display.

  In this UI, when the user inputs or selects information and then selects a service addition button, a service addition request including the input or selected information is transmitted to the main control server 40 (SA11). The activation processing unit 41a of the main control server 40 acquires the IP address corresponding to the user-side server name included in the service addition request transmitted from the terminal device 20 from the usage status information DB 42c, and performs the operation on the acquired IP address. Based on the service and disk size included in the service addition request, an installation request for the application 14, the application control client 12, and the application monitoring client 13 for providing the service, and a setting request for the dedicated data area 15 are made (SA12). ).

  Based on these requests, the virtual server 11 installs the application 14, the application control client 12, and the application monitoring client 13, sets the dedicated data area 15 based on the size set in the disk size setting area, and completes the setting. The report is transmitted to the main control server 40 (SA13). The activation processing unit 41a includes the user ID input during the login process, the user server name included in the service addition request transmitted from the terminal device 20, among the records included in the usage status information of the usage status information DB 42c. For the record including the combination of, the user-side service name input in the service name setting area, the disk size set in the disk size setting area, and the status (currently active) are further stored in association with each other. (SA14).

  In addition, the activation processing unit 41a creates an application definition file (hereinafter referred to as a manifest) of the virtual server 11 for operating the application 14 corresponding to the service selected in the service selection area (SA14). This manifest includes the type of application 14 to be activated, the signature, the size of the data disk, etc., and uses the default prepared for each type of cloud server or service, or one of them. It is possible to modify and create only a part based on user basic information, cloud basic information, usage status information, or information input in the UI of FIGS. Then, the activation processing unit 41a transmits and registers the created manifest to the application control server 50 (SA14).

  Next, the activation processing unit 41a activates the application control client 12 installed in the activated virtual server 11 (SA14). Specifically, the activation processing unit 41a transmits an activation command (for example, puppet kick) to the application control client 12 by executing a client activation program (for example, puppetrun). The application control client 12 activated in this way acquires the manifest set for itself from the application control server 50 by a known method, and acquires the application file, sets the application file, and data based on the acquired manifest. Preparation of a disk for use and activation of the application 14. By performing such processing, the user can activate each application 14 without performing setting operation individually for each application 14 of each virtual server 11.

  Next, the activation processing unit 41a registers the activated virtual server 11 and application 14 in the application monitoring server 60 (SA14). Specifically, the activation processing unit 41 a registers the IP address of the activated virtual server 11 and the type of the application 14 installed in the activated virtual server 11 in the application monitoring server 60. By performing this registration, the status of the application 14 can be monitored in a virtual server monitoring process described later.

  In addition, the activation processing unit 41a records the expected status of the activated virtual server 11 in the status corresponding to the IP address of the virtual server 11 in the usage status information DB 42c (SA14). This completes the startup process of the virtual server 11.

(Processing-Virtual server usage processing)
Next, virtual server utilization processing will be described. FIG. 11 is a flowchart of the virtual server use process. In this process, the user displays the “service” page of the UI of FIG. 8 on the terminal device 20 in the same procedure as the virtual server activation process described above (SB1-SB3), and then uses the “service” page. From the use buttons displayed in the item “use” corresponding to the user-side service name and user-side server name to be selected, a use button that matches the desired use content is selected.

  When the user selects the use button, a service use request is transmitted from the terminal device 20 to the main control server 40 (SB3). The usage processing unit 41b of the main control server 40 acquires an IP address corresponding to the user-side service name included in the service usage request from the usage status information DB 42c, and based on the service usage request for the acquired IP address. A use request is made (SB4). Specifically, the usage processing unit 41b acquires a cloud ID corresponding to the user-side server name included in the service usage request from the usage status information DB 42c, and the acquired cloud ID and usage content included in the service usage request. Cloud-side input / output corresponding to (user-side input / output) is acquired from the input-output information DB 42d, and a usage request is made based on the acquired cloud-side input / output. For example, when usage content = data addition, a Web API indicating the addition of data, and a Web API that matches the virtual server 11 specified by the IP address corresponding to the user-side service name included in the service usage request Request for use. In addition, the usage processing unit 41b records the status expected as a result of the usage request in the status corresponding to the cloud ID in the usage status information DB 42c (SB6), and stores this status in the item “status” in the UI. "(SB7). On the other hand, the application 14 of the virtual server 11 that has received the usage request performs usage processing based on the transmitted usage request (SB5).

  Thereafter, similarly, by displaying the usage request to the virtual server 11 and displaying the processing result, the service provided by the application 14 of the virtual server 11 can be used. By performing such processing, the user can use each virtual server 11 by performing only the use operation in the common environment without being aware of the unique environment of each virtual server 11. This completes the virtual server use process.

(Processing-Virtual server stop processing)
Next, the virtual server stop process will be described. FIG. 12 is a flowchart of the virtual server stop process. In this process, the user displays the “server” page of the UI of FIG. 7 on the terminal device 20 in the same procedure as the virtual server activation process described above (SC1-SC3), and then uses the “server” page on the “server” page. Select the server deletion button while the user-side server name of the server you want to stop is selected.

  When the user selects the server deletion button, a server stop request is transmitted from the terminal device 20 to the main control server 40 (SC3). The stop processing unit 41c of the main control server 40 acquires an IP address corresponding to the user-side server name included in the server stop request from the usage status information DB 42c, and issues a server stop request to the acquired IP address. (SC5). In addition, prior to the server stop request, the stop processing unit 41c requests the IP address to transmit the server configuration information at that time and the contents stored in each dedicated data area 15 of each activated application 14 The server configuration information transmitted from the virtual server 11 based on this transmission request and the storage contents of the dedicated data area 15 are stored in the storage unit 42 in association with the user ID and the user-side server name (SC4). In addition, the stop processing unit 41c records a status predicted as a result of the server stop request in a status corresponding to the cloud ID in the usage status information DB 42c (SC7), and this status is an item “ "Status" is displayed (SC8). On the other hand, the virtual server 11 that has received the server stop request stops the operation of the virtual server 11 based on the server stop request, and deletes the server configuration information and the contents stored in the dedicated data area 15 (SC6). This terminates the virtual server stop process.

(Processing-Virtual server restart processing)
Next, the virtual server restart process will be described. This process is a process for starting the virtual server 11 again in the virtual server starting process, starting the virtual server 11 again after stopping the virtual server 11 in the virtual server stopping process. In general, when the virtual server 11 is stopped, the configuration information of the virtual server 11 is deleted, so that it is difficult to start (recover) the same virtual server 11 again. In order to solve this problem, in this embodiment, the configuration information of the virtual server 11 is saved, and the virtual server 11 can be restarted using this configuration information. FIG. 13 is a flowchart of the virtual server restart process.

  In this process, basically, similarly to the virtual server activation process described above, the virtual server 11 is activated, the application 14 is set, the application is registered in the application monitoring server 60, and the status is recorded (SD1-SD8). And SD12-SD17). However, in this process, the restart processing unit 41d of the main control server 40 transmits a server addition request to the cloud server to start the virtual server 11, and then the virtual server 11 that is the same as the started virtual server 11 is It is determined whether the same user has been activated and stopped in the past (SD9). Here, the user ID and user-side server name specified by the user in the restart process are stored in the storage unit 42 together with the server configuration information and the stored contents of the dedicated data area 15 in the virtual server stop process described above. If the ID and the user-side server name match, it is determined that the same virtual server 11 as the activated virtual server 11 has been activated and stopped in the past. When the same virtual server 11 has been activated and stopped in the past (SD9, Yes), the server configuration information stored in the storage unit 42 and the storage contents of the dedicated data area 15 are activated by the restart process. It transmits to the virtual server 11 (SD10). The virtual server 11 updates the server configuration information of the virtual server 11 with the server configuration information transmitted from the main control server 40, and the dedicated data area 15 of the virtual server 11 is transmitted from the main control server 40. It is updated with the stored contents of the area 15 (SD11). This makes it possible to restart (recover) the virtual server 11 that has been started and stopped in the past.

  Here, for clarity of explanation, the virtual server restart process and the virtual server restart process have been described as different processes. However, the virtual server restart process may be integrated into the virtual server start process. Each time the virtual server activation processing is performed, it is determined whether or not the same virtual server 11 as the activated virtual server 11 has been activated and stopped in the past by the same user. The server configuration information and the contents stored in the dedicated data area 15 are updated only when the server is started and stopped. In this case, the restart processing unit 41d can be omitted.

(Processing-Virtual server monitoring processing)
Finally, the virtual server monitoring process will be described. FIG. 14 is a flowchart of the virtual server monitoring process. The application monitoring server 60 starts the virtual server monitoring process every time a virtual server start process, a virtual server use process, a virtual server stop process, or a virtual server restart process is performed, or at a predetermined interval or a predetermined timing. .

  Specifically, the application monitoring server 60 transmits a status report request to the IP address of the virtual server 11 registered in the application monitoring server 60 by the virtual server activation process or the virtual server restart process (SE1). . Upon receiving the status report request, the application monitoring client 13 of the virtual server 11 acquires the current status of each application 14 specified by the type of the application 14 included in the status report request, and a status report including the acquired status Is transmitted to the application monitoring server 60 (SE2). The application monitoring server 60 transmits this status report to the main control server 40 (SE3).

The monitoring processing unit 41e of the main control server 40 identifies a record including the IP address included in the status report from each record of the usage status information in the usage status information DB 42c, and displays the status of the identified record as a status report. (SE4). As a result, even if the actual status of the virtual server 11 is different from the status expected by the main control server 40, the actual status can be reflected in the usage status information, and the user matches the actual status. Information can be presented.
This completes the virtual server monitoring process.

(effect)
As described above, according to the present embodiment, since input / output in each of the plurality of servers and input / output in the terminal device 20 are mutually converted, a user who uses the services of the plurality of servers via the terminal device 20 Can use services through a common environment without being aware of the unique environments of these multiple servers, saving the user time and effort to acquire knowledge about the unique environments of each server. It is possible to greatly improve the convenience of users using cloud computing.

  In addition, since the server name on the server side and the server name on the server side are converted to each other, or the service name on the server side and the service name on the server side are converted to each other, Even if a name is given, the user can specify a server using a user-side server name or user-side service name that is easy for the user to remember, which further enhances the convenience of users using cloud computing. Can be improved.

  In addition, since the application definition file is automatically created and set in the application 14, it is possible to save the user from setting each application 14 and further improve the convenience of the user who uses cloud computing. Can be made.

  In addition, since the expected server status is updated with the actual server status, even if the expected status differs from the actual status due to some reason, the server status is based on the actual status. Can be used and managed.

  In addition, since the server can be restarted based on the configuration information of the server acquired when the server is stopped, a cloud in which the configuration information is immediately deleted when the server is stopped. Even if it is used, the server can be restored easily and quickly.

(Modification)
Although the embodiments of the present invention have been described above, the specific configuration and means of the present invention can be arbitrarily modified and improved within the scope of the technical idea of each invention described in the claims. Can do. Hereinafter, such a modification will be described.

(About problems to be solved and effects of the invention)
First, the problems to be solved by the invention and the effects of the invention are not limited to the above-described contents, and the present invention solves the problems not described above or has the effects not described above. There are also cases where only some of the described problems are solved or only some of the described effects are achieved.

(About distribution and integration)
Further, each of the electrical components described above is functionally conceptual and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each part is not limited to the one shown in the figure, and all or a part thereof may be functionally or physically distributed / integrated in arbitrary units according to various loads and usage conditions. Can be configured. For example, the functions of the application control server 50 and the application monitoring server 60 can be integrated into the main control server 40. Further, each DB stored in the storage unit 42 can be arbitrarily distributed and integrated.

(Appendix)
The following is a supplementary note showing a part of the configuration and effects of the present invention.
The server group integrated management system according to attachment 1 includes a network for each of a plurality of servers constituting the server group and a terminal device for using a network service provided by each of the plurality of servers. A server group integrated management system that is communicably connected to each other, and a unique environment that is an input / output environment unique to each of the plurality of servers, and for using each of the plurality of servers in the terminal device Compatibility information storage means for storing compatibility information regarding mutual compatibility with a common environment which is a common input / output environment, input / output in each of the plurality of servers, and input / output in the terminal device Conversion means for converting each other based on the compatibility information stored in the information storage means, and the conversion means receives the plurality of services from the terminal device. When input / output to / from any server in the server is performed in the common input / output environment, the input / output from the terminal device is performed based on the compatibility information stored in the compatibility information storage unit. The input / output is converted into input / output in the input / output environment specific to the server where the input / output is performed, and the converted input / output is transmitted to the server where the input / output from the terminal device is performed. When input / output from the server to the terminal device is performed in an input / output environment unique to the server, the input / output from the server is performed based on the compatibility information stored in the compatibility information storage unit. The input / output is converted into the input / output in the common input / output environment, and the converted input / output is transmitted to the terminal device.
The server group integrated management system according to appendix 2 is the server group integrated management system according to appendix 1, wherein the compatibility information storage means specifies the plurality of servers in the common input / output environment. Specific compatibility information configured by associating information with server-side specific information for identifying the plurality of servers in the specific input / output environment as a part of the compatibility information, When the input / output from the terminal device to the server is performed based on the user side specifying information, the converting unit is configured to specify the user side specifying based on the specific compatibility information stored in the compatibility information storing unit. Information is converted into server-side specific information, input / output based on the converted server-side specific information is transmitted to the server, and input / output from the server to the terminal device When it is performed based on the server side specific information, the server side specific information is converted into user side specific information based on the specific compatibility information stored in the compatibility information storage means, and the converted user Input / output based on the side identification information is transmitted to the terminal device.
The server group integrated management system according to appendix 3 is the server group integrated management system according to appendix 1 or 2, wherein the compatibility information storage means should be set in an application definition file for operating an application on the server The definition information is included for each server and each application, and the conversion means, when a request for starting an application in the server is made from the terminal device, the server stored in the compatibility information storage means, An application definition file is created based on the definition information corresponding to the application, and predetermined processing for setting the created application definition file in the application is performed.
The server group integrated management system according to appendix 4 is the server group integrated management system according to any one of appendices 1 to 3, further comprising status information storage means for storing status information relating to the status of the server, wherein the conversion After performing the process related to the server, the means stores status information related to the status of the server predicted by the process in the status information storage means, acquires the actual status of the server at a predetermined timing, and acquires the acquired status. Based on the actual status, the status information in the status information storage means is updated.
The server group integrated management system according to appendix 5 is the server group integrated management system according to any one of appendices 1 to 4, further comprising server configuration information storage means for storing the server configuration information, wherein the conversion means When the server is stopped, the server configuration information is acquired from the server and stored in the server configuration information storage means. When the stopped server is restarted, the server configuration information is stored. Based on the server configuration information stored in the means, the server is restarted.
According to the server group integrated management system described in appendix 1, since input / output in each of the plurality of servers and input / output in the terminal device are mutually converted, services of the plurality of servers are used via the terminal device. The user can use the service through the common environment without being aware of the unique environments of these multiple servers, so that the user can acquire the knowledge about the unique environment of each server. This can be omitted, and the convenience of users using cloud computing can be greatly improved.
According to the server group integrated management system described in appendix 2, since the user side specific information and the server side specific information are mutually converted, even when server side specific information that is difficult for the user to remember is given, Therefore, it is possible to specify a server using user-side specific information that is easy to remember, so that the convenience of a user who uses cloud computing can be further improved.
According to the server group integrated management system described in appendix 3, since the application definition file is automatically created and set in the application, it is possible to save the user from setting each application. The convenience of the user who uses can be further improved.
According to the server group integrated management system described in appendix 4, the expected server status is updated by the actual server status, so the expected status and the actual status may differ for some reason. Even in this case, the server can be used and managed based on the actual status.
According to the server group integrated management system described in Appendix 5, the server can be restarted based on the configuration information of the server acquired when the server is stopped. Even when using a cloud in which configuration information is deleted immediately, the server can be recovered easily and quickly.

DESCRIPTION OF SYMBOLS 1 Network system 10 Server group 11 Virtual server 12 Application control client 13 Application monitoring client 14 Application 15 Dedicated data area 20 Terminal device 30 Server group integrated management system 40 Main control server 41 Control part 41a Startup process part 41b Use process part 41c Stop process Unit 41d restart processing unit 41e monitoring processing unit 42 storage unit 42a user basic information DB
42b Cloud Basic Information DB
42c Usage status information DB
42d Input / output information DB
43 Network IF
50 Application control server 60 Application monitoring server 70 DNS server 100 Communication network

Claims (1)

Server group integrated management that is communicably connected via a network to each of a plurality of servers constituting the server group and a terminal device for using a network service provided by each of the plurality of servers A system,
Relating to compatibility between a unique environment that is an input / output environment unique to each of the plurality of servers and a common environment that is a common input / output environment for using each of the plurality of servers in the terminal device Compatibility information storage means for storing compatibility information;
Conversion means for mutually converting the input / output in each of the plurality of servers and the input / output in the terminal device based on the compatibility information stored in the compatibility information storage means,
The converting means includes
When input / output from the terminal device to any one of the plurality of servers is performed in the common input / output environment, the terminal is based on the compatibility information stored in the compatibility information storage unit. The input / output from the device is converted into the input / output in the input / output environment specific to the server where the input / output is performed, and the converted input / output is transmitted to the server where the input / output from the terminal device is performed.
When input / output to / from the terminal device from any one of the plurality of servers is performed in an input / output environment unique to the server, based on the compatibility information stored in the compatibility information storage unit, Converting input / output from the server into input / output in the common input / output environment, and transmitting the converted input / output to the terminal device;
Server group integrated management system.

Images