System management device, system management method, and system management program

JP2024166739APending Publication Date: 2024-11-29ALLEGROSMART INC
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2023083054
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-19
Publication Date
2024-11-29

Smart Images

  • Figure 2024166739000001_ABST
    Figure 2024166739000001_ABST
Patent Text Reader

Abstract

To provide a system management device capable of easily linking and operating applications even if a user has no coding skill.SOLUTION: A system management device is provided for linking a first application and a second application and making them work together in the system where a first server equipped with the virtualized first application and a first monitoring engine monitoring the communication of the first application and a second server equipped with the virtualized second application are connected by a network. The system management device has the function to notify the first monitoring engine of a domain assigned to the second application and the function to transmit the first application output transmitted to the domain via the first monitoring engine to the second application by resolving the domain. A system management method and a system management program to execute similar processes are provided.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a system management device, a system management method, and a system management program. [Background technology]

[0002] For example, applications are commonly virtualized using techniques such as containerization. A container is a software structure that logically encapsulates and defines application software, and Docker (registered trademark) containers are known as examples of such container management systems for managing the deployment and scaling of a large number of containers, such as Kubernetes (registered trademark). Technologies relating to such containers and container management systems are described in, for example, Patent Document 1, Patent Document 2, and Patent Document 3. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-10129 [Patent Document 2] JP 2022-177712 A [Patent Document 3] JP 2023-38906 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, conventional container management systems such as Kubernetes (registered trademark) require coding of configuration files, etc., making it difficult for users without coding skills, for example, to freely operate applications together to use the services they desire.

[0005] SUMMARY OF THE PRESENT EMBODIMENTS An object of the present invention is to provide a system management device, a system management method, and a system management program that enable a user without coding skills to easily make applications work together. [Means for solving the problem]

[0006] According to an aspect of the present invention, there is provided a system management device for interoperating a first application and a second application in a system in which a first server in which a virtualized first application and a first monitoring engine that monitors communication of the first application are implemented and a second server in which a virtualized second application is implemented are connected via a network. The system management device has a function of notifying the first monitoring engine of a domain assigned to the second application, and a function of resolving the domain and transmitting the output of the first application transmitted to the domain via the first monitoring engine to the second application.

[0007] According to the above configuration, the monitoring engine determines the domain of the destination of the application's output, so that the applications can work together even if they do not recognize the destination of the output. Because the destination of the application's output is dynamically changed by the function of the monitoring engine, there is no need to rewrite the configuration file that defines the destination of the output, and applications can easily work together without coding skills.

[0008] The above system management device may notify the first monitoring engine of the domain when an instruction to operate the first application and the second application in cooperation with each other is obtained, and the domain may be determined when the instruction to operate the first application and the second application in cooperation with each other is obtained.

[0009] In the above system management device, an instruction to make the first application and the second application operate in a coordinated manner may be obtained by connecting the first node and the second node with a link in a GUI in which the first application and the second application are displayed as a first node and a second node, respectively, allowing a user to operate the applications in a coordinated manner through an intuitive operation on the GUI.

[0010] In the GUI, at least one of an input terminal and an output terminal may be displayed on a node, and a link may connect an output terminal of a first node to an input terminal of a second node. In this case, in the GUI, multiple input terminals or multiple output terminals may be displayed on a single node, and multiple output terminals may be connected to a single input terminal by multiple links, and a single output terminal may be connected to multiple input terminals by multiple links.

[0011] According to another aspect of the present invention, there is provided a system management method for coordinating operation of a first application and a second application in a system in which a first server in which a virtualized first application and a first monitoring engine that monitors communication of the first application are implemented and a second server in which a virtualized second application is implemented are connected via a network. The system management method includes a step of notifying the first monitoring engine of a domain assigned to the second application, and a step of resolving the domain and transmitting an output of the first application transmitted to the domain via the first monitoring engine to the second application.

[0012] According to yet another aspect of the present invention, there is provided a system management program for interoperating a first application and a second application in a system in which a first server in which a virtualized first application and a first monitoring engine that monitors communication of the first application are implemented and a second server in which a virtualized second application is implemented are connected via a network. The system management program causes a computer to execute a function of notifying the first monitoring engine of a domain assigned to the second application, and a function of resolving the domain and transmitting the output of the first application transmitted to the domain via the first monitoring engine to the second application. [Brief description of the drawings]

[0013] [Figure 1] 1 is a block diagram showing an example of a system including a management device according to an embodiment of the present invention. [Diagram 2] 2 is a flowchart showing a process of a management device in the system shown in FIG. 1. [Diagram 3] FIG. 4 is a diagram illustrating an example of a GUI according to an embodiment of the present invention. [Figure 4] FIG. 4 is a diagram illustrating an example of a GUI according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] FIG. 1 is a block diagram showing an example of a system including a management device according to an embodiment of the present invention. A computer 110, servers 120A, 120B, and 120C, and databases 130A and 130B constituting the system 100 are connected to each other by a network 150. The computer 110 functions as a management device, either alone or in cooperation with other devices such as a server on the network. The computer 110 provides a GUI (Graphical User Interface) for system management, for example, as described below. The computer 110 is, for example, a desktop computer, a laptop computer, a smartphone, or a tablet computer. The function of the management device is illustrated as a management application 111. The management application 111 is implemented by a processor of the computer 110 (and other devices such as a server) operating according to a program 112 stored in a memory. The program 112 and data 113 used by the management application 111 are stored in the memory or storage of the computer 110.

[0015] In the servers 120A, 120B, and 120C (hereinafter collectively referred to as the servers 120), applications 121A, 121B, and 121C (hereinafter collectively referred to as the applications 121) and monitoring engines 122A, 122B, and 122C (hereinafter collectively referred to as the monitoring engines 122) are implemented. Each server 120 may be, for example, a plurality of servers installed in the same data center, a plurality of servers installed in different data centers, or a server installed in a company or the like other than the data center. Each application 121 is containerized, for example, using Docker (registered trademark). The monitoring engine 122 monitors the communication of the application 121 (container) running in each server 120. The monitoring engine 122 sets a domain to which the output of the application 121 is sent, for example, as described below.

[0016] The databases 130A, 130B are implemented in one or more storage devices, and store data used by the application 121. The network 150 is implemented by various wired or wireless communication links such as the Internet, a LAN (Local Area Network), or a WAN (Wide Area Network). Note that the numbers of the servers 120A, 120B, and 120C and the databases 130A and 130B shown in Fig. 1 are merely illustrative and are not particularly limited.

[0017] In the above-described system 100, a user uses a service provided by the application 121, for example, by accessing from another terminal device connected to the network 150. The applications 121 can be made to operate in cooperation with each other. For example, the output of the application 121A may be sent to the application 121B, and the output of the application 121B may be provided to the user as a service. Alternatively, the output of the application 121A may be sent to both the applications 121B and 121C, or the outputs of both the applications 121A and 121B may be sent to the application 121C. An example of the cooperation between the applications 121 is also shown by an example of a GUI, which will be described later.

[0018] Fig. 2 is a flowchart showing the processing of the management device in the system shown in Fig. 1. Note that the management device according to the embodiment of the present invention can use a platform or system such as Kubernetes (registered trademark) for processing other than that described below, and therefore detailed description thereof will be omitted.

[0019] In the illustrated example, step S101 is executed to execute an operation to connect nodes with a link on the GUI, step S102 (optional) is executed to assign a URL to a container corresponding to the link destination node, and step S103 is executed to notify the URL to the monitoring engine of the container corresponding to the link source node. Note that the "container" here means a container that implements application 121 in system 100 shown in Fig. 1. Each step will be further explained below.

[0020] In step S101, a user performs an operation using a GUI, for example, as described below. In the GUI, each container is displayed as a node, and applications can be made to operate in cooperation with each other by connecting the nodes with links. That is, in the system 100 shown in FIG. 1, an operation of connecting nodes with links on the GUI of the management application 111 is interpreted as an instruction to make the applications operate in cooperation with each other. As described above, between applications that operate in cooperation with each other, the output of one application is sent to another application.

[0021] In step S102, the management application 111 that has received the operation in step S101 assigns a URL to the container corresponding to the link destination node. Here, the URL is an example of a domain. For example, as in the example of a GUI described later, an input terminal and an output terminal may be displayed on each node, and the node to which the link is connected to the output terminal may be identified as the link source, and the node to which the link is connected to the input terminal may be identified as the link destination. As another example, the link source node and the link destination node may be determined, for example, by which node the operation to extend the link is executed as the starting point. In this case, the input terminal and the output terminal may not be displayed on the node.

[0022] The assigned URL is generated randomly, for example, by the management application 111. Note that, for example, if the container corresponding to the linked node is already working in conjunction with another container, the process of step S102 may be omitted since a URL has already been assigned to the linked node at the time the operation of step S101 is executed. Alternatively, even if the container corresponding to the linked node is already working in conjunction with another container, the management application 111 may assign a new URL to the container and resolve multiple different URLs as references to the same container.

[0023] In step S103, the management application 111 notifies the monitoring engine 122 of the container corresponding to the link source node of the URL assigned in step S102. Upon receiving the notification from the management application 111, the monitoring engine 122 designates the notified URL as the destination when the application 121 implemented in the container corresponding to the link source node sends an output. If the application 121 has multiple outputs, a different URL may be assigned to each output.

[0024] After the above steps S101 to S103 are executed, the management application 111 resolves the URL of the output of the application 121A sent to the assigned URL via the monitoring engine 122A, for example, and sends it to the application 121B. For this process, the management application 111 operates as a DNS (Domain Name System).

[0025] In the embodiment of the present invention, the applications 121 operating on different servers 120 can be easily made to cooperate with each other by the above-described processing, and a desired service can be used. This is also called, for example, construction of a microservice system, construction of a mesh, or construction of an orchestration. By implementing the monitoring engine 122 together with the containerized application 121 in each server 120 and having the monitoring engine 122 determine the URL of the output destination of the application 121, the applications can cooperate with each other even if the application 121 does not recognize the output destination. Since the output destination of the application 121 is dynamically changed by the function of the monitoring engine 122, for example, a procedure of rewriting the configuration file of the container that defines the output destination is not required, and applications can be easily cooperated without coding skills.

[0026] 3 and 4 are diagrams showing examples of GUIs in the embodiment of the present invention. Each diagram shows an example of a canvas 500 displayed on a display of the computer 110 of the system 100 shown in FIG. 1. The canvas 500 displays nodes 501 (including, for example, nodes 501A, 501B, and a node group 501C) representing containerized applications 121 and links 502 connecting the nodes 501 to each other. As shown in FIG. 3, the canvas 500 may be displayed together with a detail window 600, which will be described later. The detail window 600 displays, for example, URL information 601 assigned to an application corresponding to the selected node 501, input setting information 602, and output setting information 603. The user places a new node 501 at an arbitrary position in the canvas 500 by, for example, selecting it from a list. The placed node 501 can be freely moved within the canvas 500 using, for example, a pointing device such as a touch panel or a mouse.

[0027] An output terminal 503 indicating the output of the application and an input terminal 504 indicating the input of the application are displayed on a node 501. When two or more nodes 501 are arranged, the output terminal 503 of any node 501 can be connected to the input terminal 504 of another node 501 with a link 502. The link 502 is generated, for example, by a drag operation using a pointing device. As already mentioned, the operation of connecting nodes on the GUI with a link is interpreted as an instruction to cause applications to operate in cooperation with each other.

[0028] 3, output terminal 503 of node 501A and input terminal 504 of node 501B are connected by link 502, thereby allowing applications corresponding to nodes 501A and 501B to operate in cooperation with each other. Specifically, the output of the application corresponding to node 501A is transmitted to the application corresponding to node 501B. As already explained, when the connection by link 502 is executed, a URL is notified to the monitoring engine of the application corresponding to node 501A, so that the operation on the GUI is completed with the generation of link 502.

[0029] For example, like node 501B shown in Fig. 3, a single node 501 may have multiple output terminals 503 displayed thereon and multiple input terminals 504 displayed thereon. This corresponds to multiple outputs or inputs being defined in the application corresponding to node 501. As shown in the figure, the multiple output terminals 503 and the multiple input terminals 504 are distinguished from one another by, for example, names or numbers.

[0030] Also, like node group 501C shown in FIG. 4, it may be possible to connect multiple output terminals 503 to a single input terminal 504 by link 502. In this case, the output of each link source application is input to the linked application. Also, it may be possible to connect a single output terminal 503 to multiple input terminals 504 by link 502. In this case, the output of the link source application is duplicated and input to each linked application according to a definition within the application, or is input to one of the linked applications according to a conditional branch. In this way, it is also possible to link applications in a network like node group 501C.

[0031] In this manner, in the embodiment of the present invention, applications can be made to work together by connecting nodes with links on the GUI. As already mentioned, this is also called, for example, building a microservices system, building a mesh, or building an orchestration. This allows the user to make applications work together through intuitive operations on the GUI, without having to code, for example, to rewrite the configuration files of containers.

[0032] In the above embodiment, an example in which an application is containerized has been described, but in the embodiment of the present invention, the application does not necessarily have to be containerized, and may be virtualized by a method other than containerization. In this case, too, by implementing a monitoring engine in addition to the application virtualized on the server, and by having the management device notify the monitoring engine of the domain assigned to the application to be linked, the applications can be linked in the same way as in the above embodiment.

[0033] The processing of each step of the embodiment of the present invention as described above is executed by a processor operating according to a program in the computer 110 or the server 120. The processor may be, for example, a CPU (Central Processing Unit), a PLD (Programmable Logic Device) such as an FPGA (Field-Programmable Gate Array) whose circuit configuration can be changed after manufacture, or a dedicated circuit configuration such as an ASIC (Application Specific Integrated Circuit).

[0034] The program may be pre-stored (installed) in a memory such as a ROM, or may be provided in a form recorded on a recording medium such as a CD (Compact Disc), a DVD (Digital Versatile Disc), or a USB (Universal Serial Bus) memory. Alternatively, the program may be downloaded from an external device via a network. [Explanation of symbols]

[0035] 100...system, 110...computer, 111...management application, 112...program, 113...data, 120A, 120B, 120C...server, 121A, 121B, 121C...application, 122A, 122B, 122C...monitoring engine, 130A, 130B...database, 150...network, 500...canvas, 501, 501A, 501B...node, 501C...group of nodes, 502...link, 503...output terminal, 504...input terminal, 600...detail window, 601...URL information, 602...input setting information, 603...output setting information.

Claims

1. A system management device for operating a first application and a second application in a linked manner in a system in which a first server, in which a virtualized first application and a first monitoring engine that monitors communication of the first application are implemented, and a second server, in which a virtualized second application is implemented, are connected via a network, the system management device comprising: notifying the first monitoring engine of a domain assigned to the second application; a function of resolving the domain and sending the output of the first application sent to the domain via the first monitoring engine to the second application; A system management device having the above configuration.

2. 2 . The system management device according to claim 1 , further comprising: notifying said first monitoring engine of said domain when an instruction to cause said first application and said second application to operate in cooperation with each other is obtained.

3. The system management device according to claim 2 , wherein the domain is determined when an instruction to cause the first application and the second application to operate in cooperation with each other is obtained.

4. 3. The system management device of claim 2, wherein an instruction to operate the first application and the second application in cooperation with each other is obtained by connecting the first node and the second node with a link in a GUI in which the first application and the second application are displayed as a first node and a second node, respectively.

5. 5. The system management device according to claim 4, wherein said GUI displays at least one of an input terminal and an output terminal at each node, and said link connects an output terminal of said first node and an input terminal of said second node.

6. 6. The system management device according to claim 5, wherein a plurality of input terminals or a plurality of output terminals are displayed on a single node in the GUI.

7. 6. The system management device of claim 5, wherein the GUI is capable of connecting a plurality of the output terminals to a single input terminal by a plurality of the links, and of connecting a single output terminal to a plurality of the input terminals by a plurality of the links.

8. A system management method for operating a first application and a second application in a linked manner in a system in which a first server in which a virtualized first application and a first monitoring engine for monitoring communication of the first application are implemented and a second server in which a virtualized second application is implemented are connected via a network, the method comprising: notifying the first monitoring engine of a domain assigned to the second application; resolving the domain and sending the output of the first application sent to the domain via the first monitoring engine to the second application; A system management method comprising:

9. A system management program for operating a first application and a second application in a linked manner in a system in which a first server, in which a virtualized first application and a first monitoring engine that monitors communication of the first application are implemented, and a second server, in which a virtualized second application is implemented, are connected via a network, the system management program comprising: notifying the first monitoring engine of a domain assigned to the second application; a function of resolving the domain and sending the output of the first application sent to the domain via the first monitoring engine to the second application; A system management program that causes a computer to run

Citation Information

Patent Citations

  • Edge system, control method of edge system, computer program used to control edge system, and recording medium thereof

    JP2021010129A

  • Container management device and container management program

    JP2022177712A

  • Computer implemented method, system, and computer program product (new container storage system in remote pods in kubernetes)

    JP2023038906A