WO2022024277A1

WO2022024277A1 - Information distribution device, information distribution method, and program

Info

Publication number: WO2022024277A1
Application number: PCT/JP2020/029135
Authority: WO
Inventors: 亮太片柳; 謙輔高橋; 悟近藤
Original assignee: 日本電信電話株式会社
Priority date: 2020-07-29
Filing date: 2020-07-29
Publication date: 2022-02-03
Also published as: JP7456507B2; JPWO2022024277A1

Abstract

This information distribution device comprises: an acquisition unit that acquires, upon construction of a coordination service achieved through coordination among a plurality of sub-systems, first information including parameters determined according to construction of the sub-systems; a first transmission unit that transmits, for respective pieces of the first information acquired by the acquisition unit and to the respective sub-systems corresponding to the first information, second information including parameters included in the first information; a reception unit that receives third information which is transmitted from the sub-systems having received the second information and which includes the second information and information necessary for maintenance of the sub-systems; and a second transmission unit that, upon reception by the reception unit of the third information from all the sub-systems, transmits a prescribed message to a maintenance unit for performing maintenance operation for the plurality of sub-systems. Accordingly, distributability of information necessary for maintenance of the coordination service can be improved.

Description

Information distribution equipment, information distribution methods and programs

The present invention relates to an information distribution device, an information distribution method and a program.

With the spread of B2B2X services, the importance of linked services in which multiple types of services are linked is increasing, and in a short period of time and at low cost in response to the appearance of new services related to linked services and changes in the specifications of existing services. It has come to be required to deal with.

Conventionally, in order to respond to such changes, a technology has been devised in which service specifications and API specifications are loosely coupled as a catalog management unit and an adapter function unit, and the cost of responding to changes in specifications of new services and existing services is suppressed. (Patent Document 1).

In addition, a technique has been devised in which the maintenance work process is made into parts, and the process execution is autonomously determined based on the message distributed via the connected message bus to realize the maintenance work execution (Non-Patent Document 1). ..

On the other hand, in recent cloud-based service operations, IP addresses are dynamically assigned to service instances such as VMs (Virtual Machines) and containers at the time of construction, so clients use the IP address of the service instance as a service. Sometimes it needs to be detected in real time. As a mechanism for finding out where (host, port) the application deployed in this way exists, there is an architecture called Service Discovery (Non-Patent Document 2).

FIG. 1 is a diagram for explaining the Service Discovery architecture. As shown in FIG. 1, in the Service Discovery architecture, the configuration information is registered in the "Service Registry" from the "Self Registry (Agent)" on the service instance ("APL1", "APL2"). When using the service, the client inquires about the location of APL from "Service Registry" and sends a request to APL based on the response result.

Japanese Unexamined Patent Publication No. 2018-206050

By applying Service Discovery, it is possible to collect and manage system configuration information, not just IP addresses. That is, using the Service Discovery architecture, it is possible to register the configuration information of the system converted into metadata in a predetermined Service Registry via the network.

However, in order to apply the Service Discovery architecture to a system that aims to automate the construction, operation, and maintenance of linked services, the following issues exist.

First, the configuration information needs to be described on the file of the subsystem before registration to the Service Registry. Moreover, since each subsystem may be reused by a plurality of linked services, it is difficult to determine all the service configurations before construction. Therefore, it is necessary for the maintenance person to intervene and describe the parameters to be determined after the construction of the subsystem on the file of the subsystem after the construction of the subsystem.

More specifically, examples of the configuration information of the linked service include "service information", "server information", "server IF information", "SSH information", and "curl test information". Some of these information are determined before the construction of the subsystem (at the time of service configuration design) and can be set in advance, while others are not confirmed until after the construction of the subsystem.

FIG. 2 is a diagram showing an example of configuration information of the linked service. FIG. 2 shows that "service information", "server information" and "server IF information" cannot be preset, and "SSH information" and "curl test information" can be preset. Has been done. Therefore, in the example of FIG. 2, the "service information", "server information", and "server IF information" need to be described in the file of the subsystem by the maintainer after the construction of the subsystem.

Second, in the existing technology, the registration status of the configuration information is basically managed in each subsystem. Therefore, even if the existing technology is simply used, there is no way to manage the registration status of the configuration information for each linked service. If the maintenance system is activated when the registration completion notification of each subsystem configuration information is triggered, there is a possibility that the information registration of the entire linked service has not been completed, so problems such as an unnecessary alarm being issued when the test is conducted. There is a risk of occurrence.

The present invention has been made in view of the above points, and an object of the present invention is to improve the distribution of information necessary for the maintenance of linked services.

Therefore, in order to solve the above-mentioned problem, the information distribution device is the first one including parameters determined according to the construction of each of the above-mentioned subsystems when the cooperation service realized by the cooperation of a plurality of subsystems is constructed. For each acquisition unit that acquires information and the first information acquired by the acquisition unit, the second information including the parameters included in the first information is combined with the sub that corresponds to the first information. A third information including a first transmission unit to be transmitted to the system, the second information transmitted from each of the subsystems having received the second information, and information necessary for the maintenance of the subsystem. When the third information is received from all the subsystems by the receiving unit and the receiving unit, a predetermined message is transmitted to the maintenance unit that performs the maintenance work of the plurality of subsystems. It has a transmitter.

It is possible to improve the distribution of information necessary for the maintenance of linked services.

It is a figure for demonstrating the Service Discovery architecture. It is a figure which shows an example of the configuration information of the cooperation service. It is a figure which shows the configuration example of the cooperation service management system 1 in embodiment of this invention. It is a figure which shows the hardware configuration example of the information distribution apparatus 10 in embodiment of this invention. It is a sequence diagram for demonstrating an example of the processing procedure executed in the cooperation service management system 1. It is a figure which shows the structural example of construction information. It is a figure which shows an example of the construction information after conversion.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 3 is a diagram showing a configuration example of the cooperative service management system 1 according to the embodiment of the present invention. In FIG. 3, the cooperative service management system 1 includes an information distribution device 10, a construction system 30, a maintenance system 40, a cooperative service providing system 20, and the like. The information distribution device 10 is connected to each of the construction system 30, the maintenance system 40, and the cooperation service providing system 20 via a network.

The cooperation service providing system 20 is one or more computers that provide a cooperation service realized by cooperation of a plurality of subsystems 21 to a terminal or the like (not shown). In the example of FIG. 3, when the cooperative service providing system 20 does not distinguish between the subsystem 21A that provides the service A and the subsystem 21B that provides the service B (hereinafter, each of the

subsystems

21A and 21B, etc., the "subsystem 21" is used. An example including) and the like is shown. That is, the linked service is realized by linking service A, service B, and the like. Each subsystem 21 includes a configuration information management client 211, a configuration information file 212, and the like, in addition to functional units (service A, service B, etc.) that realize each service. The configuration information file 212 is information that can be set before the construction of the subsystem 21 (service), and is information required for the maintenance work of the subsystem 21 (service) (in the example of FIG. 2, SSH (Secure Shell)). ) Information, Curl test information, etc.) is described in this file. The configuration information management client 211 will be described later. It is assumed that the configuration information management client 211 and the configuration information file 212 have already been introduced and deployed in the construction materials (instance image, etc.) of each subsystem 21.

The construction system 30 is one or more computers that construct a cooperation service by constructing each subsystem 21 in the cooperation service providing system 20. The construction of the subsystem 21 or the service means a process including installation of the system or a program constituting the service, activation of the program, and the like. However, the installation of the program may be executed in advance. When the construction system 30 constructs each subsystem 21, the values of the parameter group (hereinafter referred to as "construction information") determined or determined at the time of construction among the parameter group of the configuration information of each subsystem 21 are used. Allocate or set, and manage (store) the configuration information of each subsystem 21 constructed by the construction system 30. In the example of FIG. 2, the parameters constituting the service information, the server information, or the server IF (Interface) information correspond to the construction information. The construction system 30 may be realized by using the technique disclosed in Patent Document 1.

The maintenance system 40 is one or more computers that execute processing related to maintenance work of the cooperation service (each of the subsystems 21 constituting the cooperation service). The maintenance work refers to a work known as a maintenance work, such as a cooperation confirmation test between subsystems 21, ssh connection to the subsystem 21, and operation of the subsystem. The maintenance system 40 may be realized by using the technique disclosed in Non-Patent Document 2.

The information distribution device 10 is one or more computers that execute a process for automatically distributing the configuration information of the cooperation service required for the maintenance work of the cooperation service to the maintenance service. In FIG. 3, the information distribution device 10 has a distribution control unit 11 and a configuration information management unit 12. Each of these parts may operate on the same computer or may operate on different computers.

The configuration information management unit 12 of the information distribution device 10 and the configuration information management client 211 of each subsystem 21 may be realized by using the Service Discovery architecture disclosed in Non-Patent Document 3. Specifically, the configuration information management unit 12 may be implemented as the "Service Registry" in FIG. The configuration information management client 211 may be implemented as the "SelfRegister (Agent)" in FIG.

Further, the information distribution device 10 may serve as either or both of the construction system 30 and the maintenance system 40.

FIG. 4 is a diagram showing a hardware configuration example of the information distribution device 10 according to the embodiment of the present invention. The information distribution device 10 of FIG. 4 has a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, an interface device 105, and the like, which are connected to each other by a bus B, respectively.

The program that realizes the processing in the information distribution device 10 is provided by a recording medium 101 such as a CD-ROM. When the recording medium 101 storing the program is set in the drive device 100, the program is installed in the auxiliary storage device 102 from the recording medium 101 via the drive device 100. However, the program does not necessarily have to be installed from the recording medium 101, and may be downloaded from another computer via the network. The auxiliary storage device 102 stores the installed program and also stores necessary files, data, and the like.

The memory device 103 reads a program from the auxiliary storage device 102 and stores it when there is an instruction to start the program. The CPU 104 executes the function related to the information distribution device 10 according to the program stored in the memory device 103. The interface device 105 is used as an interface for connecting to a network.

The distribution control unit 11 and the configuration information management unit 12 in FIG. 3 are realized by a process of causing the CPU 104 to execute one or more programs installed in the information distribution device 10. Further, each computer constituting the construction system 30, the maintenance system 40, and the cooperation service providing system 20 may also have the hardware as shown in FIG.

Hereinafter, the processing procedure executed in the linked service management system 1 will be described. FIG. 5 is a sequence diagram for explaining an example of a processing procedure executed in the cooperative service management system 1.

When a new construction order is input to the construction system 30, the construction system 30 constructs a cooperation service (S101). Specifically, the construction system 30 starts each service of each subsystem 21 constituting the cooperation service, and constructs the cooperation between the services of each subsystem 21. When constructing the linked service, the construction system 30 sets the values of parameters (for example, service information, server information, server IF information, etc. in FIG. 2) that can be determined only at the time of construction among the configuration information of the linked service. Assign or configure to system 21. The construction system 30 generates construction information including these parameters and stores the construction information.

FIG. 6 is a diagram showing a configuration example of construction information. FIG. 6 shows an example of construction information generated for one linked service. In the construction information, the description d11 is information about the cooperation service. For example, the parameter "serviceId" is the identification information of the linked service.

Descriptions d12 to d14 are construction information for each subsystem 21 constituting the linked service. Each of these construction information includes, for example, service information, server information, server IF information, and the like of the subsystem 21.

Subsequently, the construction system 30 starts the configuration information management client 211 of each subsystem 21 in order (S102). However, in step S101, the configuration information management client 211 of each subsystem 21 may be started at the same time as the service of each subsystem 21 is started. In this case, step S102 does not need to be executed again.

Subsequently, the construction system 30 transmits a notification of completion of new construction of the linked service to the distribution control unit 11 (S103). Upon receiving the completion notification, the distribution control unit 11 acquires the construction information (FIG. 6) of the cooperation service related to the completion notification from the construction system 30 (S104). For example, the distribution control unit 11 transmits a construction information acquisition request to the construction system 30, and the construction system 30 returns the construction request in response to the acquisition request, so that the distribution control unit 11 acquires the construction information.

Subsequently, the distribution control unit 11 converts the information (construction information) of each subsystem 21 included in the construction information into a format corresponding to each subsystem 21 (S105).

FIG. 7 is a diagram showing an example of the construction information after conversion. In FIG. 7, the description d21 is the conversion result of the description d11 in FIG. Description d22 is a conversion result of description d12 of FIG. The description d23 is the conversion result of the description d13 of FIG. Description d24 is a conversion result of description d14 of FIG.

Although FIG. 7 is described in more detail than FIG. 6, basically, the content included in the converted construction information is included in the conversion source construction information. If the construction information generated by the construction system 30 has a format corresponding to each subsystem 21 from the beginning, the conversion process in step S105 may not be executed.

Subsequently, the distribution control unit 11 uses the API of the configuration information management client 211 of each subsystem 21 of the linkage service to the configuration information management client 211 of each subsystem 21 with the construction information (after conversion) of the subsystem 21. Construction information) is transmitted (S106). Subsequently, the distribution control unit 11 requests reading (validation) of the transmitted construction information using the API of the configuration information management client 211 of each subsystem 21 (S107).

Subsequent steps S108 to S111 are loop processes executed for each subsystem 21. However, steps S108 to S111 do not necessarily have to be executed in series for each of the subsystems 21, and may be executed in parallel. Hereinafter, the subsystem 21 that is the processing target in the loop processing is referred to as “target subsystem 21”.

When the configuration information management client 211 of the target subsystem 21 reads the construction information in response to the request in step S107, the construction information and the information contained in the configuration information file 212 of the target subsystem 21 (for example, FIG. 2). In the example of, the registration request of the configuration information including the SSH information and the Curl test information) is transmitted to the configuration information management unit 12 (S108). The registration request includes the configuration information. Upon receiving the registration request, the configuration information management unit 12 saves the configuration information included in the registration request in the auxiliary storage device 102 or the like (for example, a repository) (S109). Subsequently, the configuration information management unit 12 transmits a registration completion notification of the configuration information to the distribution control unit 11 (S110). The registration completion notification includes the configuration information or a parameter corresponding to the identification information (for example, the value of "serverId") of the subsystem 21 in the configuration information. Upon receiving the registration completion notification, the distribution control unit 11 includes the identification information of the subsystem 21 included in the construction information acquired in step S104 or the converted construction information in step S105, and the registration completion notification. By collating with the identification information of the subsystem 21, the subsystem 21 for which the registration of the configuration information has been completed is identified among the subsystems 21 related to the construction information, and the progress status of the registration of the configuration information (registration completion notification is notified). Information indicating the received subsystem 21 and the non-received subsystem 21) is updated (S111). When the distribution control unit 11 detects that the registration of the configuration information for all the subsystems 21 related to the construction information is completed as a result of updating the progress status in step S111, the process proceeds to step S112.

In step S112, the distribution control unit 11 transmits a predetermined message indicating the completion of new construction (completion of registration of the configuration information of the subsystem) to the maintenance system 40. The message includes identification information of the linked service for which the new construction has been completed (that is, the registration of the configuration information for all the subsystems 21 has been completed). The identification information can be obtained from the pre-conversion or post-conversion construction information.

When the maintenance system 40 receives the message, the maintenance system 40 uses the configuration information stored in the configuration information management unit 12 for each subsystem 21 of the linkage service related to the identification information included in the message, and the API of the configuration information management unit 12. Obtained via (S113). Subsequently, the maintenance system 40 starts the operation and maintenance work of the cooperative service based on the acquired configuration information (S114).

Note that, for example, when a new subsystem 21 is added to the linked service (that is, when the linked service is changed), the processing procedure of FIG. 5 may be executed for the subsystem 21.

As described above, according to the present embodiment, the configuration information of each subsystem 21 constituting the linked service is automatically distributed to the maintenance system 40 when the linked service is constructed or changed. Therefore, it is possible to improve the distribution of information necessary for the maintenance of the cooperation system. As a result, for example, it is possible to contribute to reduction and automation of work costs for construction, operation, and maintenance of linked services.

Further, since a predetermined message is sent to the maintenance system 40 after the registration of the configuration information of all the subsystems 21 constituting the cooperation service is completed, the operation of the maintenance system 40 is started in the state where the registration is not completed. Can be avoided.

In the present embodiment, the distribution control unit 11 is an example of an acquisition unit, a first transmission unit, a reception unit, and a second transmission unit. The construction information before conversion is an example of the first information. The converted construction information is an example of the second information. The configuration information is an example of the third information. The maintenance system 40 is an example of the maintenance unit.

Although the embodiments of the present invention have been described in detail above, the present invention is not limited to such specific embodiments, and various modifications are made within the scope of the gist of the present invention described in the claims.・ Can be changed.

1 Cooperative service management system 10 Information distribution device 11 Distribution control unit 12 Configuration information management unit 20 Cooperative service provision system 21A Subsystem 21B Subsystem 30 Construction system 40 Maintenance system 100 Drive device 101 Recording medium 102 Auxiliary storage device 103 Memory device 104 CPU
105 Interface device 211 Configuration information management client 212 Configuration information file B bus

Claims

When a cooperation service realized by cooperation of a plurality of subsystems is constructed, an acquisition unit that acquires first information including parameters determined according to the construction of each of the above subsystems, and an acquisition unit.
For each of the first information acquired by the acquisition unit, the second information including the parameters included in the first information is transmitted to the subsystem corresponding to the first information. Department and
A receiving unit that receives the third information transmitted from each of the subsystems that has received the second information, including the second information and the information necessary for the maintenance of the subsystem.
When the third information is received from all the subsystems by the receiving unit, the second transmitting unit that transmits a predetermined message to the maintenance unit that performs the maintenance work of the plurality of subsystems.
An information distribution device characterized by having.
The second transmitting unit collates the identification information of the subsystem included in the first information acquired by the acquisition unit with the identification information of the subsystem included in the third information. Then, among all the above-mentioned subsystems, the subsystem in which the above-mentioned third information is received is specified.
The information distribution device according to claim 1, wherein the information distribution device is characterized by the above.
The first transmitter converts the first information into the second information having a format corresponding to the subsystem.
The information distribution device according to claim 1 or 2, wherein the information distribution device is characterized by the above.
When a cooperation service realized by cooperation of a plurality of subsystems is constructed, an acquisition procedure for acquiring first information including parameters determined according to the construction of each of the above-mentioned subsystems, and an acquisition procedure.
For each of the first information acquired by the acquisition procedure, the second information including the parameters included in the first information is transmitted to the subsystem corresponding to the first information. Procedure and
A receiving procedure for receiving a third information transmitted from each of the subsystems having received the second information, including the second information and information necessary for the maintenance of the subsystem, and a receiving procedure for receiving the third information.
When the third information is received from all the subsystems by the reception procedure, a second transmission procedure for transmitting a predetermined message to the maintenance unit performing maintenance work of the plurality of subsystems, and a second transmission procedure.
An information distribution method characterized by a computer executing.
The second transmission procedure collates the identification information of the subsystem included in the first information acquired by the acquisition procedure with the identification information of the subsystem included in the third information. Then, among all the above-mentioned subsystems, the subsystem in which the above-mentioned third information is received is specified.
The information distribution method according to claim 4, wherein the information is distributed.
The first transmission procedure converts the first information into the second information having a format corresponding to the subsystem.
The information distribution method according to claim 4 or 5, characterized in that.
A program characterized by having a computer execute the information distribution method according to any one of claims 4 to 6.