JPH10334020A - Constitution changing system for large scale open system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To suppress the asynchronization of constitutional changes and to improve the reliability of the whole system in constitution management on a large scale open system. SOLUTION: An action description file 8 is prepared from the contents of a mater DB 3 and entered in a serial distribution control queue 5 or the like for an agent 10. The file 8 is distributed to respective agents 10, 12, 14 by a FIFO method. A master DB managing server 2 enters an action execution file 8 into a serial distribution control queue 4 at timing arriving at previously set time to distribute the file 9 to respective agents 10, 12, 14. The server 2 checks the completion of distribution of the file 9 to all the agents 10, 12, 14. Respective agents 10, 12, 14 analyze the file and reflect constitutional information in respective distributed DBs 11, 13, 15.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a configuration change method for a large-scale open system, and in particular, processes a large amount of configuration changes between a plurality of agents so that the synchronization of configuration information does not shift between machines. The present invention relates to a large-scale open system configuration change method.

[0002]

2. Description of the Related Art As a conventional configuration change method of a large-scale open system, there is a technique described in Japanese Patent Application Laid-Open No. 6-124262. In this technique, a manager creates a difference of data required by each agent as a configuration information file for an agent affected by performing a configuration change. The created file is distributed to each agent in advance. At the timing when the set application time is reached, the manager issues an instruction to change the configuration of the distributed configuration file to each of the agents, and the agents change the configuration all at once.

[0003]

A first problem of the above-mentioned prior art is that, when the configuration is changed by time, the synchronization of the configuration information between the agents may be shifted, or the configuration may not be changed. It is that there is a nature. The reason is that when a line failure occurs, the configuration information file is not delivered to the required agent, the set application time is reached, and the configuration change processing of all related agents is performed It is. Therefore, if a failure occurs during the change time, the change in the configuration information may not be reflected in the agent in which the line failure or the like has occurred.

[0004] The second problem is that when the amount of configuration change is large and the number of related agents is large, the amount of data to be distributed is large. The reason for this is that the capacity of the file is increased because the changed configuration information is directly written as data in the file.

According to the present invention, in the configuration management on a large-scale open system, when performing a configuration change process, instead of instructing a configuration change at a set time, an "action execution file" is distributed. When the distribution of the "action execution file" is completed between the related agents, the configuration is changed and the "action description file"
It is an object of the present invention to manage delivery of an "action execution file" to a target agent in order so as not to cause jumping, to suppress a synchronization shift of a configuration change, and to improve the reliability of the entire system.

[0006]

According to a first large-scale open system configuration change method of the present invention, a master database management server having a master database including entire data, one or more agents including a distributed database, A configuration change method for a large-scale open system including the master database management server and a network connecting the agent, wherein the master database management server describes configuration information necessary for the configuration change as a change operation. And distribute the action description file to the agent in order, and then distribute the action execution file instructing the start of execution of the content of the action description file to each agent in order. The agent is Upon receiving the action executable to implement configuration changes based on the contents of the action description file.

A second configuration change method for a large-scale open system according to the present invention is a configuration change method for the first large-scale open system, wherein the master database management server is configured to execute the action description file and the action execution. A file is registered in a queue for each of the agents in order, and is delivered to the agents in order.

A third large-scale open system configuration change method according to the present invention is the second large-scale open system configuration change method, wherein the queue is managed on a first-in first-out basis.

A fourth aspect of the present invention is a configuration change method for a large-scale open system, comprising: a terminal on which an operation is performed; a master database management server for managing a database; a network; A configuration change method for a large-scale open system having one or more connected agents, wherein the master database management server has a master database as a database and a serial delivery control queue having an order, Has a distributed database is a database, the master database management server, in the serial delivery control queue based on the master database, first register an action description file describing configuration information necessary for configuration change as a change operation, Registering an action execution file instructing the start of execution of the contents of the action description file at a preset time, distributing the action description file and the action execution file to each of the agents in order, When each of the agents receives the action execution file, the agent changes the distributed database based on the contents of the action description file and changes the configuration.

A fifth large-scale open system configuration change method according to the present invention is the fourth large-scale open system configuration change method, wherein the serial distribution control queue exists for each agent.

A sixth aspect of the present invention is a configuration change method for a large-scale open system, wherein the serial distribution control queue is first-in first-out. Is managed by

[0012]

Next, an embodiment of the present invention will be described in detail with reference to FIG. Hereinafter, the database is referred to as DB. Further, the master DB is a database including all configuration information, and the distributed DB is a database including configuration information necessary for each agent. FIG.
FIG. 1 is a block diagram showing an embodiment of the present invention. Referring to FIG. 1, a first embodiment of the present invention includes a terminal 1 on which an operation is performed, a master DB management server 2 for managing a database, a network 17, and a network 17.
And the agents 10, 12, and 14 connected to the master DB management server 2. Master D
The B management server 2 includes a master DB 3 that is a database and a serial distribution control queue 4. Agents 10, 12, and 14 are distributed DBs 11, which are databases.
13 and 15 are included. Also, the serial distribution control queue 4
Is the serial delivery control queue 5 for the agent 10
And serial distribution control queue 6 for agent 12
And a serial distribution control queue 7 for the agent 14. The configuration change is, for example, an IP change.
It means changing system information such as addresses.

Next, the operation of the embodiment of the present invention will be described with reference to FIG.

First, the change information registered by the change registration instruction 1-1 from the terminal 1 is stored in the master DB 3.
When the distribution instruction 1-2 is issued from the terminal 1, the master DB 3
The action description file 8 is created from
3), serial delivery control queue 5 for agent 10, serial delivery control queue 6 for agent 12,
An entry is made in the serial distribution control queue 7 for the agent 14 (1-4 in FIG. 1).

Next, the action description file 8 contains the FI
It is distributed to each of the agents 10, 12, and 14 by the FO method (1-5 in FIG. 1).

Next, the master DB management server 2 enters the action execution file 9 into the serial distribution control queue 4 at the time when a preset time has been reached (1-6 in FIG. 1), and the agents 10, 12 , 14
Deliver to. The master DB management server 2 notifies the completion of the distribution of the action execution file 9 to all the agents 10, 12, and 14 by notifying the serial distribution control queue 5 for the agent 10, the serial distribution control queue 6 for the agent 12, and the agent 14 The serial distribution control queue 7 is checked for confirmation (1-7 in FIG. 1).

Each of the agents 10, 12, and 14 analyzes the action description file 8 and stores the configuration information in a distributed DB.
11, 13, and 15 (1-8 in FIG. 1).

Next, a case where a line failure occurs will be described with reference to FIG. FIG. 2 is a block diagram showing an operation at the time of a line failure. A case where a line failure has occurred for the agent 14 will be described. Line failure (1 in FIG. 2)
When -8) occurs and there is an agent for which a file has not arrived (16 in FIG. 2), all the configuration change processing is awaited. Referring to FIG. 2, a line failure (1 in FIG. 2)
-8), the action description file 8 is not distributed to the agent 14 (16 in FIG. 2). Since the files are delivered in order, the action execution file 9 is also not delivered to the agent 14, and all configuration changes are queued. Then, a line failure (1 in FIG. 2)
-8) and the like are restored, and when it is confirmed that the action description file 8 and the action execution file 9 have been delivered to the agent 14, each of the agents 10, 12,
At 14, the configuration is changed, and the configuration information is reflected on the distributed DBs 11, 13, and 15.

Next, an embodiment of the present invention will be described in detail with reference to FIG. FIG. 3 is a block diagram illustrating a configuration change example of the network configuration management system. Referring to FIG. 3, in this embodiment, a center includes a terminal 1 for registering configuration information and a center server 2a, and a client 10a installed under a server 12a connected to the center server 2a via a network 17. It has a server configuration. A configuration change is performed to add a new client 13a under the server 12a. The center server 2a includes a master DB 3, a distributed DB 11, and a serial distribution control queue 4. The serial distribution control queue 4 includes a serial distribution control queue 5a for the center server 2a and a serial distribution control queue 6a for the server 12a.

Next, the operation of the embodiment of the present invention will be described with reference to FIG. The configuration information of the client 13a newly added under the server 12a is registered in the master DB 3 from the configuration information registration terminal 1 in the center (1-1 in FIG. 3). Delivery instruction from terminal 1 (1- in FIG. 3)
When 2) is issued, an action description file 8 having the content "add client 13a" is created.
-3), an entry is made in the serial distribution control queue 4 (1-4 in FIG. 3). This action description file 8
It is distributed to the center server 2a itself and the server 12a (1-5 in FIG. 3). Client 13a is the server 12
When it is time to install the server under a, the action execution file 9 is distributed to the center server 2a and the server 12a.
The center server 2a includes the center server 2a and the server 12a.
When the action execution file 9 is received, the action analysis file 8 is analyzed, and the respective distributed DBs 11 and
13 is reflected with the configuration information (1-8 in FIG. 3).

[0021]

The first effect of the present invention is that the synchronization deviation of the configuration change between a plurality of agents can be eliminated. The reason is that the "action execution file" is delivered to each agent and the delivery of the file is confirmed to all agents, and then the configuration is changed.If the file has not arrived due to a line failure, the configuration change Because they can meet.

The second effect is that traffic can be distributed. The reason for this is that instead of having the information necessary for the configuration change as data as a batch in the distribution file, the actions that occur due to the change are divided into files for each type of change as an "action description file". This is because when retransmitting a file, retransmission from a file whose distribution has failed at the time of a line failure may be performed, so that the retransmission amount of the distribution file is reduced as a whole.

The third effect is that for each agent,
That is, the intended configuration change is surely performed. The reason is that, due to the difference in the amount of stored data between the “action description file” and the “action execution file”, serial transfer control does not cause file transfer skipping and can reliably deliver the desired configuration change information. It is. As described above, the configuration change in the serial distribution control and the file distribution completion management eliminates the synchronization deviation of the configuration information between the agents, thereby improving the reliability of the entire system.

[Brief description of the drawings]

FIG. 1 is a block diagram showing an embodiment of the present invention.

FIG. 2 is a block diagram showing an operation at the time of a line failure.

FIG. 3 is a block diagram illustrating a configuration change example of a network configuration management system.

[Explanation of symbols]

 1 Terminal 2 Master DB Management Server 2a Center Server 3 Master DB 4 Serial Distribution Control Queue 5 Serial Distribution Control Queue for Agent 10 5a Serial Distribution Control Queue for Center Server 2a 6 Serial Distribution Control Queue for Agent 12 6a Serial Distribution Control for Server 12a Queue 7 Serial delivery control queue for agent 14 8 Action description file 9 Action execution file 10, 12, 14 Agent 10a Client 12a Server 13a Client 11, 13, 15 Distributed DB 17 Network

Claims (6)

[Claims] 1. A large-scale open system comprising a master database management server having a master database including entire data, one or more agents including a distributed database, and a network connecting the master database management server and the agents. In the configuration change method, the master database management server creates an action description file describing configuration information necessary for the configuration change as a change operation, and distributes the action description file to the agent in order, An action execution file instructing the start of execution of the content of the action description file is delivered to each of the agents in order, and when the agent receives the action execution file, the content of the action description file is added. A configuration change method for a large-scale open system, wherein a configuration change is performed based on the configuration change. 2. The method according to claim 1, wherein the master database management server comprises:
2. The system according to claim 1, wherein the action description file and the action execution file are registered in a queue for each of the agents in order, and are distributed to the agents in order. . 3. The configuration change method for a large-scale open system according to claim 2, wherein the queue is managed on a first-in first-out basis. 4. A large-scale open system including a terminal on which an operation is performed, a master database management server for managing a database, a network, and one or more agents connected to the master database management server via the network. Wherein the master database management server has a master database which is a database and a serial delivery control queue having an order, each agent has a distributed database which is a database, and the master database management server Registers an action description file describing configuration information necessary for configuration change as a change operation in the serial distribution control queue based on the master database, and then starts execution of the content of the action description file. finger Registering the action execution file to be shown at a preset time, delivering the action description file and the action execution file to each of the agents with order, and receiving each of the agents, A configuration change method for a large-scale open system, wherein the configuration is changed by changing the distributed database based on the contents of the action description file. 5. The large-scale open system configuration change method according to claim 4, wherein said serial distribution control queue exists for each agent. 6. The configuration change method for a large-scale open system according to claim 4, wherein the serial distribution control queue is managed on a first-in first-out basis.