JP6016831B2 - Storage control device and storage control program - Google Patents

Description

  The present invention relates to a storage control device that controls different types of storage devices.

A storage device (auxiliary storage device) is a storage device that stores data and programs used by a computer. However, since a data protection policy regarding a storage device is different for each manufacturer, a management structure is different for each product of the manufacturer. .
Therefore, conventionally, a storage device and a virtual machine that uses the storage device are manually set using a tool dedicated to each product. According to this method, there is a problem that as the scale of the storage apparatus increases, the construction time takes longer, and setting errors increase as the work amount increases.

FIG. 26 is a diagram showing that the management structure is different for each product. In the product a, storage media are created by collecting storage media. A data protection policy is set for each storage pool, and a volume is set above the storage pool. In the product b, a storage group is created by collecting storage media, a storage pool is set above the storage group, and a volume is set above the storage pool. A data protection policy is set for each storage pool. In the product c, a storage pool is created by collecting storage media, a volume is set in the storage pool, and one or more volumes are defined in a volume group. A data protection policy is set for each volume.
Even if only an example is described in this way, the products a, b, and c have different storage device management structures, and the administrator needs to make settings in accordance with the management structures of the individual storage devices.
Japanese Patent Laid-Open No. 2003-316522 discloses a method of providing a logical medium provided by a storage device system as a virtual volume to a host computer. However, the control method disclosed in Patent Document 1 has the following problems as described above.
(1) When storage device manufacturers are different, storage devices having different management structures cannot be collectively controlled.
(2) Although a method for providing a logical medium (volume) to a virtual host computer is disclosed, management of a lower layer of the volume cannot be performed.

JP 2003-316522 A

  An object of the present invention is to construct a control apparatus that centrally manages different types of storage apparatuses.

  A storage control device according to the present invention is a storage control device connected to a storage device and a client terminal via a network, and includes operation template information that is a template for an operation instruction and setting information for each management unit of the storage device. By storing the storage means, the control device transmission / reception unit that receives the control information related to the storage device from the client terminal as communication data, and collating the communication data with the setting information, the item information including at least the storage type in the setting information is extracted. The control unit common processing unit that generates the operation procedure information corresponding to the control information by specifying the storage type from the extracted item information and replacing the template item of the operation template information with the value of the item information, and the common control device Based on the storage type specified by the processing unit, processing to the specified storage device Determines the individual processing unit for executing the determined pass operation procedure information to the individual processing unit, characterized in that a separate processing caller.

  The individual processing unit of the storage control device is provided according to the storage type, and executes processing for the storage device that matches the storage type specified in the operation procedure information and matches the storage name included in the control information. It is characterized by doing.

  The operation template information of the storage control device is stored according to the storage type, and the control device common processing unit identifies the storage type of the storage device to be processed by collating the communication data with the setting information, and this storage The operation template information corresponding to the type is selected.

  In addition, the control device common processing unit of the storage control device replaces the template item of the selected operation template information with the value of the item information, so that the operation procedure information for calling the individual processing unit and passing the parameters to the individual processing unit is obtained. It is characterized by generating.

  In addition, the control information related to the storage device is information that requests any one of the setting information for each management unit to be registered, changed, deleted, or referenced. Further, based on the control information, the corresponding setting information On the other hand, a repository management unit that performs any of registration, change, deletion, or reference processing is provided.

  In addition, the setting information for each management unit is configured to be associated with each included ID, and the repository management unit refers to the corresponding item information by sequentially referring to the ID included in the setting information. Features.

  In addition, the repository management unit of the storage control device refers to the storage type correspondence information storing the management configuration for each storage type, so that the ID of the setting information corresponding to the management unit determined to have no corresponding storage type. Is characterized in that the same value as the ID of the upper or lower setting information is set so that the upper setting information and the lower setting information of the setting information are associated with each other.

  A computer program according to the present invention causes a computer to function as a storage control device.

  According to the storage control device of the present invention, it is possible to centrally manage storage devices of different types with different management structures.

1 is a system configuration diagram according to Embodiment 1. FIG. 2 is a configuration diagram of a client terminal 100 according to Embodiment 1. FIG. 2 is a configuration diagram of a control device 200 and a storage 400 in Embodiment 1. FIG. 6 is a diagram illustrating an example of a data configuration of setting information used in Embodiment 1. FIG. FIG. 3 is a diagram showing a flow of overall processing in the first embodiment. FIG. 10 is a diagram showing a flow of processing for information registration in the storage 400 according to the first embodiment. 3 is a diagram illustrating an example of a data configuration of communication data used in Embodiment 1. FIG. 3 is a diagram illustrating an example of a data configuration of communication data used in Embodiment 1. FIG. 3 is a diagram illustrating an example of a data configuration of communication data used in Embodiment 1. FIG. 6 is a diagram illustrating an example of a data configuration of communication data regarding information registration in a storage 400 used in Embodiment 1. FIG. 3 is a diagram illustrating an example of a configuration of storage information 27 according to Embodiment 1. FIG. 4 is a flowchart showing a flow of processing for requesting registration information of a storage 400 in the first embodiment. 6 is a diagram illustrating an example of a configuration of repository temporary storage information 13 in Embodiment 1. FIG. 6 is a diagram showing an example of a display screen when creating a volume 44 in the first embodiment. FIG. 6 is a diagram showing an example of a display screen when creating a volume 44 in the first embodiment. FIG. 6 is a diagram showing an example of a display screen when creating a volume 44 in the first embodiment. FIG. 4 is a flowchart showing a flow of volume 44 creation processing in the first embodiment. 6 is a diagram illustrating a data configuration example of control information related to creation of a volume 44 in the first embodiment. FIG. 6 is a diagram illustrating a configuration example of operation template information 34 according to Embodiment 1. FIG. 6 is a diagram illustrating a configuration example of calling of an individual processing unit 26 and operation procedure information 36 in the first embodiment. FIG. 6 is a diagram showing an example of a screen for changing a host group 45 corresponding to a volume 44 in the first embodiment. FIG. 6 is a diagram showing an example of a screen for changing a host group 45 corresponding to a volume 44 in the first embodiment. FIG. 6 is a diagram showing an example of a screen for changing a host group 45 corresponding to a volume 44 in the first embodiment. FIG. 4 is a flowchart showing a flow of processing for changing a host group 45 corresponding to a volume 44 in the first embodiment. It is a figure which shows an example of the hardware resource of the client terminal 100 used by each embodiment, and the control apparatus 200. It is a figure explaining the problem in the conventional system.

In the present embodiment, description will be made on the assumption that processing is performed in the management unit indicated by product b in FIG.
FIG. 1 is a system configuration diagram according to the present embodiment. A client terminal 100 that receives input from a system administrator (hereinafter referred to as an administrator), a control device (storage control device) 200, and a storage (storage device) 400 in which an environment is constructed and updated by the control device 200 is connected to the network 300. Connected through. A plurality of storages 400 (400a, 400b,...) Can be installed, and some of them have different manufacturers and management structures. Hereinafter, storages with different manufacturers and management structures are referred to as “storages with different storage types”. In addition, the control device 200 performs mapping (assignment) of the storage 400 to the host group 500 (virtual machines 500a, 500b...).

As shown in FIG. 2, the client terminal 100 includes a transmission / reception unit 11, a processing unit 12, repository temporary storage information 13, and storage type screen information 14.
The transmission / reception unit 11 transmits / receives data to / from the control device 200, and the processing unit 12 controls input of control information at the client terminal 100 and output of processing results at the control device 200. Further, the processing unit 12 stores information regarding the storage 400 received from the control device 200 in the repository temporary storage information 13. In addition, the storage type screen information 14 stores a screen configuration and input items for each predetermined storage type. The repository temporary storage information 13 and the storage type screen information 14 are stored in a storage device 929 (described later with reference to FIG. 25).
The communication data transmitted by the transmission / reception unit 11 is control information related to the storage 400 based on an input from the administrator. The control information includes a management unit of the storage 400 and a processing request (registration, change, deletion, or reference processing). Request).

  FIG. 3 is a diagram showing details of the control device 200 and the storage 400. The control device 200 includes a transmission / reception unit 21, a common processing unit 22, a repository management unit 23, a job management unit 24, an individual processing call unit 25, an individual processing unit 26, and a repository 35.

The repository 35 is data stored in the storage device 929, and includes setting information (storage information 27, storage group information 28, storage pool information 29, volume information 30, volume host group information 31, and the like for each management unit of the storage 400. Host group information 32 and host information 33) and operation template information 34 which is a template for operation instructions are stored. A plurality of operation template information 34 is prepared according to the storage type of the storage 400.
Further, the storage type correspondence information 38 stores a management unit for each storage type of the storage 400 handled by the control device 200. For example, the management unit of the product a in FIG. 26 has a management configuration of the storage medium 41, the storage pool 43, and the volume 44 from the lower level to the upper level, and the management unit of the product b from the lower level to the higher level. 42, the management configuration of the storage pool 43 and the volume 44 is stored. The storage type correspondence information 35 may be held as temporary data that is directly referred to by the common processing unit 22 instead of data stored in the storage device 929.

  The transmission / reception unit (control device transmission / reception unit) 21 receives control information for the storage 400 from the client terminal 100 as communication data, and transmits a processing result based on the control information to the client terminal 100.

The common processing unit (control device common processing unit) 22 determines control information included in the communication data received from the client terminal 100, and is a processing request (registration, change, deletion, or reference) for which management unit. To identify.
Next, the common processing unit 22 identifies the relevant storage type and information related to the storage 400 by collating the communication data with the setting information in the repository 35. Subsequently, when the processing request from the client terminal 100 is specified as a registration, change, or deletion request for any management unit, the common processing unit 22 selects the operation template information 34 corresponding to the specified storage type, and the repository 35 The item information including at least the storage type is extracted from the setting information in the information, and the extracted item information is embedded in the selected operation template information 34, thereby generating the operation procedure information 36 corresponding to the type of the storage 400.

Based on the control information, the repository management unit 23 performs registration, change, deletion, or reference processing on the item information of the corresponding management unit in the repository 35.
The individual processing calling unit 25 identifies the corresponding individual processing unit 26 based on the storage type identified by the common processing unit 22, and passes the operation procedure information 36 to the identified individual processing unit 26. Based on the procedure information 36, registration, change, or deletion processing is executed for the corresponding storage device. Alternatively, the individual processing unit 26 receives the processing result in the storage 400 as the processing result information 37. The individual processing unit 26 is provided for each storage type and for each process to each management unit, and is a processing unit that performs a corresponding process according to the storage type.
A series of processing flow shown in the present embodiment is executed interactively based on control information from the client terminal 100, but the job management unit 24 sends a request from the client terminal 100 to the control device 200. The request of the client terminal 100 is managed as a job so as to be processed in the client. The job management unit 24 receives the control information from the common processing unit 22 and conversely activates the common processing unit 22 based on the control information.

The storage 400 includes a storage medium 41 (41a, 41b ...), a storage group 42 (42a, 42b ...), a storage pool 43 (43a, 43b ...), and a volume 44 (44a, 44b ...). It is composed of management units. The storage medium 41 is a storage medium that physically exists inside the storage 400, the storage group 42 manages one or more storage media 41 together, and the storage pool 43 manages one or more storage groups 42 together. To do. The volume 44 designates a specific storage area of the storage pool 43, and the volume host group 45 (45a, 45b...) Defines one or more volumes 44 as a group. 500 (virtual machines 500a, 500b,...) Is a management unit referred to as a storage area in which a data file exists.
A plurality of storage 400 having different storage types may be installed.

FIG. 4 shows setting information (storage information 27, storage group information 28, storage pool information 29, volume information 30, volume host group information 31, host group information 32, host information 33) and operation templates for each management unit of the storage 400. It is the figure which showed the structure of the information.
The data structure of FIG. 4 matches the management unit of the storage 400 shown in FIG. In the storage information 27, the storage ID, the storage name, the IP address, etc. for specifying the storage 400 are stored as item information such as the storage type. The item information from the storage group information 28 to the host information 33 is as shown in FIG. 4, but other than that shown in FIG. 4, necessary item information can be arbitrarily added, and the configuration shown in FIG. It is not limited to.

  Each setting information is associated with data by each ID. For example, the storage information 27 and the storage group information 28 are linked by a storage ID. The storage group information 28 and the storage pool information 29 are linked by a pool ID. The storage information 27 and the storage pool information 29 are linked by a storage ID. The storage pool information 29 and the volume information 30 are linked by a pool ID. The volume information 30 and the volume host group information 31 are linked by a volume ID. The volume host group information 31 and the host group information 32 are linked by a host group ID. The host group information 32 and the host information 33 are linked by a host ID.

One or more pieces of operation template information 34 are registered according to the processing request information for each management unit information for each storage type, and a template item related to the processing request information is set.
As will be described later with reference to FIG. 19, the operation template information 34 is described in a script format (a series of command statements written in a script language) including a call to the corresponding individual processing unit 26.
The operation procedure information 36 is described in a script format similarly to the operation template information 34, but the operation template information 34 and the operation procedure information 36 may be configured in a format other than the script format.
By referring to the setting information in the repository 35, if the control information includes information for specifying one of the management units of the storage 400, information for replacing the template item of the operation template information 34 can be specified. The operation procedure information 36 corresponding to the storage type can be generated.

The operation template information 34 may be configured as a separate file for each storage type and for each processing request information to the management unit, or may be configured as one file. Or you may comprise for every storage type. When configuring as separate files, if the file name is configured so that the processing request information for each storage type and management unit can be determined, the operation template information 34 corresponding to the corresponding processing request is obtained by searching the file name. Can be identified. When configured as a single file, a comment is inserted in the script template so that the processing request information for each storage type and management unit can be identified, and the corresponding processing request is searched by searching for the comment. The operation template information 34 corresponding to can be specified. In addition, when configuring a file for each storage type, configure the file name so that the storage type is known, and insert a comment in the script template so that the processing request information for each management unit can be identified. For example, the storage type can be specified by searching the file name, and the operation template information 34 corresponding to the processing request information for each management unit can be specified by searching the comment.
As described above, the setting information for each management unit is associated with each key ID, so that if any ID of the management unit is specified in the control information, the setting information can be referred to sequentially. it can. Therefore, the values of items necessary for generating the operation procedure information 36 can be referred to.

  The management unit of the storage 400 shown in FIGS. 3 and 4 has a general-purpose configuration that can correspond to any management unit of the products a to c shown in FIG. That is, it is the structure which piled up the structure of the products ac.

  FIG. 5 is a diagram showing an overall processing flow according to the present embodiment. As shown in FIG. 5, the processing is started, and the common processing unit 22 of the control device 200 registers information of the storage 400 (step S1), creates the storage group 42 (step S2), and creates the storage pool 43. (Step S3), the volume 44 is created (Step S4), the volume host group 45 is created (Step S5), and the volume group 500 is created (Step S6). The processing in step S6 includes registration of host (virtual machines 500a, 500b...) Information. FIG. 5 shows the flow of processing performed in the initial stage, but the creation, change, and deletion processing of each management unit can be executed at an arbitrary timing.

  The common processing unit 22 can confirm that the management unit of the product b does not have the volume host group 45 by referring to the storage type correspondence information 38. Therefore, in the overall flow, the common processing unit 22 performs a process of registering a key ID in the volume host group information 31 corresponding to step S5 when executing the process of step S4 or S6. . As described above, the common processing unit 22 performs only the process of registering a key ID in the corresponding setting information for the process of creating a management unit that does not exist.

FIG. 6 is a flowchart showing the flow of processing for information registration in the storage 400 shown in step S1 of FIG.
The processing is started, and the processing unit 12 displays the processing screen 500 on the display device 901 (described later with reference to FIG. 25) (step S11). Although not shown, the processing screen 500 is an initial screen for receiving a processing request from the administrator regarding which processing is to be performed. The processing unit 12 receives each piece of information corresponding to the item information of the storage information 27 by an input from the administrator through the processing screen 500 (step S11), and the transmission / reception unit 11 uses the input information about the storage 400 as predetermined control information. Is transmitted to the control device 200 in the programming interface format (step S13). The predetermined programming interface format is, for example, an API format.

The transmission / reception unit 21 of the control device 200 receives control information from the client terminal 100 (step S14), and the common processing unit 22 receives the processing request included in the control information passed from the transmission / reception unit 21 as “storage information registration”. In this case, the storage type is specified with reference to the setting information of the repository 35. Next, in order to perform “access confirmation to storage” by selecting operation template information 34 matching the specified storage type and replacing each template item of the operation template information 34 with the setting information value of the repository 35. Operation procedure information is generated (step S15). The method of selecting the operation template information 34 and specifying the template information is as described above with reference to FIG.
When it is determined in step S15 that the processing request included in the control information is other than “registration of storage information”, the processing after step S15 shown in FIG. 6 is not performed, and other processing described later is executed. .

The individual processing calling unit 25 identifies the individual processing unit 26 that matches the storage type identified in step S15, and the individual processing unit 26 uses the operation procedure information generated in step S15 to the storage 400. The access confirmation is executed (step S16) , and the storage 400 returns the access result (step S17).

When it is confirmed in step S17 that the storage is normally accessed, the repository management unit 23 registers the control information in the storage information 27 based on the request from the common processing unit 22 (step S18). The repository management unit 23 passes the storage information 27 registration availability to the common processing unit 22 (step S19), and the common processing unit 22 returns “storage information registration availability information” to the client terminal 100 via the transmission / reception unit 21. (Step S20). In the client terminal 100, when the transmission / reception unit 11 receives the message, the processing unit 12 displays an arbitrary message indicating “storage information registration permission / inhibition information” on the processing screen 500 (step S21), and the processing ends.
Although not shown in FIG. 6, when the access result to the storage 400 is NG in step S17, the control information received from the client terminal 100 may be wrong, that is, the administrator's input may be wrong. Therefore, the common processing unit 22 replies to the client terminal 100 via the transmission / reception unit 21 that “storage information could not be registered”. In the client terminal 100, when the transmission / reception unit 11 receives the message, the processing unit 12 displays a message stating that “storage information could not be registered” on the processing screen 500 and ends the processing.

  7 to 9 show the data format communicated between the client terminal 100 and the control device 200 as an example in the format of API communication. 7 to 8 illustrate the correspondence between the configuration of the control information (request) transmitted from the client terminal 100 and the processing result (response) from the control device 200. FIG. List display, creation, change, or deletion operations are communicated as API communication requests for storage units, storage groups, storage pools, volumes, or host groups that are management units. Each information and each ID in the request is based on the input data input from the administrator using the processing screen 500.

  FIG. 9 is a diagram showing an example of a response. In the case of an execution result, an error code (Errorcode, error code is specified at the time of error) and an error message (indicating error code) Error message (error content is specified at the time of error) is configured as communication data. When the control information is a list display, information referring to the repository 35 is returned from the control device 200. For example, the storage list is configured with reference to storage information 27, the storage pool list with reference to storage pool information 29, the volume list with reference to volume information 30, and the host group list with reference to host group information 32.

FIG. 10 is a diagram illustrating a data configuration example of API communication related to the information registration processing of the storage 400 illustrated in FIG. FIG. 11 is a diagram showing the configuration of the storage information 27 after registering information regarding the storage 400 in response to a request from the client terminal 100. A plurality of storage information 27 is configured based on a registration request from the client terminal 100.
10 and 11, the storage type is indicated by a number as illustrated, but the processing unit 12 converts data (including characters) input to the processing screen 500 according to a predetermined conversion rule. And configured as API communication data. Also, in FIG. 10, storage information items are shown in English to show the data structure of API communication, and in FIG. 11, the storage information in the storage device 929 is shown in Japanese for simplicity, but FIG. 10 and FIG. The item 11 corresponds in order from the top.

FIG. 12 is a flowchart showing a flow of processing for requesting registration information of the storage 400. The process shown in FIG. 12 is a process performed as a pre-process of the process shown in steps S2 to S6 in FIG.
The processing is started, and the processing unit 12 displays the processing screen 500 on the display device 901 (step S31). The processing unit 12 accepts a processing request (information request for the storage 400) from the administrator via the processing screen 500 (step S32), and the transmission / reception unit 11 receives control information based on the processing request in a predetermined programming interface format. It transmits to the control apparatus 200 (step S33).

The transmission / reception unit 21 of the control device 200 receives the control information from the client terminal 100 (step S34), and the common processing unit 22 determines that the control information delivered from the transmission / reception unit 21 is “information request for storage 400”. Determination is made and information on the storage 400 is requested to the repository management unit 23 (step S35).
The repository management unit 23 refers to the setting information in the repository 35, configures storage information and related information of the storage 400 that can be sequentially referred to from the corresponding storage 400 (step S36), and stores the configured storage information in the common processing unit 22. Deliver (step S37). The common processing unit 22 transmits storage information to the client terminal 100 via the transmission / reception unit 21 (step S38).

The transmission / reception unit 11 of the client terminal 100 receives the storage information, and the processing unit 12 displays the storage information on the processing screen 500. In addition, the processing unit 12 stores the storage information as the repository temporary storage information 13 and prepares for the subsequent processing (step S39).
When it is determined in step S35 that the processing request included in the control information is other than “information request for storage 400”, the processing after step S35 shown in FIG. 12 is not performed.
FIG. 13 is an example showing the configuration of the repository temporary storage information 13 after the process of step S39, and shows that three data have been acquired for the storage 400.

  Although not shown in FIG. 13, various setting information that is sequentially referenced from the storage IDs of the three storages 400 is also stored. In addition, information that may be associated with the storage information 27 referred to by the host group information 32 is also stored as appropriate.

  The flow of volume creation processing will be described with reference to FIGS. 14 to 16 are diagrams showing examples of screens related to volume creation processing. FIG. 14 shows a volume creation screen 501 displayed when the administrator selects volume creation processing. The processing unit 12 displays the information of the temporary repository storage information 13 in order to accept the selection of the storage 400 for creating the volume on the volume creation screen 501. Based on the correspondence data (not shown) between the registration information of the repository temporary storage information 13 stored in the storage device 929 and the display items displayed on the volume creation screen 501, the processing unit 12 displays each volume creation screen 501. Display items. For example, by referring to the corresponding data, the storage type “0” in the temporary repository storage information 13 is displayed as “type A” and “1” is replaced with “type C”.

When the administrator selects one of the storages on the volume creation screen 501, the processing unit 12 refers to the storage type screen information 14 and displays the volume creation detail screen 502 shown in FIG. 15 according to the selected storage type. Information related to the storage 400 stored in the temporary storage information 13 is displayed. Accepts input from the administrator regarding the volume to be created. The volume name to be created is designated in “Volume name”, the size (virtual size and physical size) of the volume to be created in “Capacity”, and the storage pool ID in which the volume is created is designated in “Storage pool ID”. The storage pool ID is input by selecting one of the storage pool IDs associated with the selected storage ID. As shown in FIG. 15, when an existing host group is selected, mapping with the created host group is performed when the volume is created. If no host group is selected, only volume creation is performed.
For example, when the administrator selects a storage type for which no storage pool exists, the processing unit 12 does not display the storage pool input screen on the volume creation detail screen 502 based on the registered content of the storage type screen information 14.
When the administrator designates the creation of a plurality of volumes at the same time, he presses the “Continue designation” button to designate information relating to the next volume creation. When you have finished entering the volume information to be specified, press the “Create” button to request volume creation.

  FIG. 16 is a volume creation result screen 503 showing the volume creation result. As shown in FIG. 16, the creation result (creation success or creation failure) is displayed for each designated volume name. By pressing the “Continue” button on the volume creation details screen 502, a plurality of volume creations can be designated at the same time. In this case, creation results for a plurality of volumes are displayed on the volume creation result screen 503. The

FIG. 17 is a flowchart showing the flow of the process for creating the volume 44 shown in step S4 of FIG.
The processing is started, and the processing unit 12 displays the processing screen 500 on the display device 901 (step S41). When receiving a volume creation request from the administrator, the processing unit 12 refers to the repository temporary storage information 13 and displays a volume creation screen 501 and a volume creation detail screen 502. The processing unit 12 configures control information based on the input volume creation request (step S42). The transmission / reception unit 11 transmits the control information to the control device 200 in a predetermined programming interface format (step S43).

The transmission / reception unit 21 of the control device 200 receives control information from the client terminal 100 (step S44), and the common processing unit 22 receives the repository 35 when the control information delivered from the transmission / reception unit 21 is “volume creation request”. Referring to the setting information, specify the storage type. Next, operation procedure information for performing “volume creation” by selecting operation template information 34 that matches the specified storage type and replacing the template item of the operation template information 34 with the setting information value of the repository 35. 36 is generated (step S45). The method of selecting the operation template information 34 and specifying the template information is as described above with reference to FIG.
If it is determined in step S45 that the processing request included in the control information is other than “volume creation request”, the processing from step S45 shown in FIG. 17 is not executed.

  The individual processing calling unit 25 identifies the individual processing unit 26 that matches the storage type identified in step S45, and the individual processing unit 26 specifies the control information using the operation procedure information 36 generated in step S45. The volume creation is executed for the storage 400 that has been made (step S46), and the storage 400 returns the volume creation result (step S47).

  If it is confirmed in step S47 that the volume 44 has been created normally, the repository management unit 23 registers the control information in the storage information 27 based on the request from the common processing unit 22 (step S48). Further, when the host group ID corresponding to the created volume 44 is specified in the control information, the repository management unit 23 registers the setting information so as to associate the host group ID with the created volume 44. The repository management unit 23 refers to the storage type information 38, so that the volume host group 45 shown in FIG. 3 does not exist in the management unit of the product b, and the information registered in the volume host group information 31 shown in FIG. It is determined that they do not exist, the volume ID and host group ID are registered in the volume host group information 31, and the host group ID is registered in the host group information 32. By processing in this way, even if the storage type is the product b in which the volume host group 45 does not exist, the necessary information (in this case, the volume ID and the host group is obtained via the volume host group information 31). ID) can be linked.

  That is, the common processing unit 22 determines the management unit of the specified storage type by referring to the storage type correspondence information 38, and determines whether there is a management unit that does not exist. As a result of the determination, the repository management unit 23 does not need to register detailed information for the setting information corresponding to the management unit determined not to exist. Therefore, the setting information ID is set to the same value as the ID of the upper or lower setting information.

According to the example shown in step S48, the volume ID and host group ID are registered in the volume host group information 31, but the volume ID is information referenced from the lower volume information 30, and the host group ID is included in the control information. Information.
The repository management unit 23 passes the availability of creation of the volume 44 to the common processing unit 22 (step S49), and the common processing unit 22 returns a response “execution result” to the client terminal 100 via the transmission / reception unit 21 (step S50). ). In the client terminal 100, when the transmission / reception unit 11 receives the message, the processing unit 12 displays the volume creation availability information on the volume creation result screen 503 (step S51) and ends the process.
Although not shown in FIG. 17, if the creation result of the volume 44 is NG in step S47, there is a possibility that the control information received from the client terminal 100 is wrong, that is, the administrator's input is wrong. Therefore, the common processing unit 22 replies to the client terminal 100 via the transmission / reception unit 21 that “volume could not be created”. In the client terminal 100, when the transmission / reception unit 11 receives the message, the processing unit 12 displays the creation NG result on the volume creation detail screen 502, and the processing is terminated.

FIG. 18 is a diagram showing a data configuration example of control information related to creation of the volume 44 transmitted in step S43 shown in FIG. The volume information (portion surrounded by {}) is matched to the configuration of the volume information 30, but if the data configuration association between the processing unit 12 and the common processing unit 22 is ruled, The data configuration of the control information and the configuration of the volume information 30 do not necessarily match.
FIG. 19 is a diagram showing an example of the operation template information 34. FIG. 19 shows volume creation template information with a storage type of type A and type C volume creation template information when configured with one file. . Described at the top of the command statement is the name of the individual processing unit 26, and an item name starting with “$” indicates a template item.

FIG. 20 is a diagram illustrating an example of the operation procedure information 36. For the operation procedure information 36a, the common processing unit 22 calls “makevolume”, which is the individual processing unit 26, based on the operation template information 34, and performs an individual process on the operation procedure for creating a volume for the storage 400 of type A storage type. It is shown as a parameter to the unit 26.
For the operation procedure information 36b, the common processing unit 22 calls “mkvolune”, which is the individual processing unit 26, based on the operation template information 34, and performs an individual process on the operation procedure for creating a volume for the storage 400 of type C storage type. It is shown as a parameter to the unit 26. The operation procedure information 36a shows an example in which a template item starting with “$” in the command statement is replaced with the value of the item information of the setting information. Further, the operation procedure information 36b shows an example in which the command item is not rewritten, and the template item starting with “$” is a parameter indicating that the item information value of the setting information. The common processing unit 22 “replaces the template item with the value of the item information” specifies the method of directly rewriting the template item indicated by the operation procedure information 36a with the value and the template item in the operation procedure indicated by 36b as the parameter value. Although a method is conceivable, the common processing unit 22 can replace the template item with the value of the setting item by any other method.

  The processes in steps S45 to S46 will be described with reference to FIGS. The control information delivered from the transmission / reception unit 21 has the configuration shown in FIG. 18 and will be described using the volume information of the portion surrounded by the first {}. After determining that the control information is “Volume creation request”, the common processing unit 22 sets the volume ID (volumeid) to “vol001”, the volume name (volumename) to “vol01”, and the pool ID (Poolid) to “ Confirm that "pool001" is specified. Subsequently, the common processing unit 22 refers to the storage group information 28 positioned below the storage pool information 29 with the pool ID (Poolid) being “pool001” as a key, and when the pool ID is “pool001” The storage ID value of is specified. Next, the storage information 27 is referred to, and the storage type corresponding to the specified storage ID is specified. As described above, the common processing unit 22 identifies the storage type by sequentially referring to the setting information using the value of any item information included in the control information as a key. At this time, it is assumed that “type A” is specified.

  Subsequently, in order to select the operation template information 34 in which the identified storage type is “typeA” and the processing request is “volume creation request”, the common processing unit 22 sets the storage type to “comment” starting with “#”. Search for a comment line that is “type A” and whose processing request is “volume creation request”. When the corresponding comment line is retrieved, the command statement next to the comment part starting with “#” becomes the operation template information 34. As shown in FIG. 19, the operation template information 34a is a corresponding portion.

Next, the common processing unit 22 specifies the setting information in order to refer to the value of the setting information that replaces the template item of the operation template information 34a. For example, “$ storage pool name” is “storage pool name” when “pool ID” of the storage pool information 29 is “pool001”, and “$ virtual size” and “$ physical size” have volume IDs. It is “virtual size” when “vol001” and “physical size”. Thus, by sequentially searching from the setting information specified by the control information, the value of the setting information for replacing the template item can be specified, and the operation procedure information 36 can be configured.
In step S46, the individual processing calling unit 25 calls the individual processing unit 26. FIG. 20 displays the calling of the individual processing unit 26 and the operation procedure information 36 delivered to the individual processing unit 26 as parameters.
In the example shown in FIG. 18, there are two pieces of volume information (portion surrounded by {}), which is control information for simultaneously requesting the creation of two volumes. Although not shown in FIGS. 15 and 18, when requesting the creation of two or more volumes, the designation of the processing order can be received from the administrator. In that case, processing order information for specifying the received processing order is included in the volume information. The operation procedure information 36 shown in step S45 is generated in any order. However, the individual procedure calling unit 25 shown in step S46 transfers the operation procedure information 36 to the individual processing unit 26, that is, calls the individual processing unit 26. Perform sequentially based on the order information. As a result, when there is a reference relationship in the volume 44 to be created, it is possible to execute processing so that inconsistency does not occur.
The process flow of the volume 44 creation process shown in step S4 of FIG. 5 has been described above, but the generation of other management information is similarly executed. Regarding the creation processing, when the processing order information is specified in the control information, as described above, the individual processing calling unit 25 delivers the operation procedure information 36 to the individual processing unit 26 based on the processing order information. After confirming that the processing has been completed normally based on the processing order information, it is configured to generate the next management information, or without confirming whether it has been completed normally, the next management information You may comprise so that a production | generation process may be performed.

FIG. 21 to FIG. 23 are diagrams showing examples of screens related to the volume-corresponding host group change processing. FIG. 21 is a change volume selection screen 504 that is displayed when the administrator selects the volume change processing. The processing unit 12 requests the control device 200 for the volume information 30 and the volume host group information 31 in order to accept the selection of the volume 44 whose host group associated with the changed volume selection screen 504 is changed. The transferred information is stored in the temporary repository storage information 13. The processing unit 12 displays each item on the change volume selection screen 504 based on the temporary repository storage information 13 stored in the storage device 929. The flow of the information request process for the volume information 30 and the volume host group information 31 is the same as the information request process for the storage 400 shown in FIG.
When the administrator selects any volume on the change volume selection screen 504, the processing unit 12 displays the host group change screen 505 in FIG. 22 and accepts an input of a host group to be newly assigned to the volume selected by the administrator. .

FIG. 23 is a volume change result screen 506 showing the allocation change result. As shown in FIG. 23, a creation result (creation success or creation failure) is displayed for each designated volume name.
FIG. 24 is a flowchart showing the flow of processing for changing a volume-corresponding host group. The host group 45 creation process shown in step S6 of FIG. 5 is a change process.

  The processing is started, and the processing unit 12 displays the processing screen 500 on the display device 901 (step S61). When receiving a volume-corresponding host group change request from the administrator, the processing unit 12 refers to the repository temporary storage information 13 and displays a change volume selection screen 504 and a host group selection screen 502. The processing unit 12 configures control information including the input changed volume information and a host group ID that is newly allocated to the corresponding volume (step S62). The transmission / reception unit 11 transmits the control information to the control device 200 in a predetermined programming interface format (step S63).

The transmission / reception unit 21 of the control device 200 receives control information from the client terminal 100 (step S64), and the control information received from the transmission / reception unit 21 of the common processing unit 22 is a “volume-corresponding host group change request”. At that time, the storage type is specified with reference to the setting information of the repository 35. Next, by selecting the operation template information 34 that matches the specified storage type and replacing the template item of the operation template information 34 with the setting information value of the repository 35, a “volume-corresponding host group change request” is performed. Operation procedure information 36 is generated (step S65). The method of selecting the operation template information 34 and specifying the template information is as described above with reference to FIG.
If it is determined in step S65 that the processing request included in the control information is other than “volume-corresponding host group change processing”, the processing after step S65 shown in FIG. 24 is not executed.

  The individual processing calling unit 25 identifies the individual processing unit 26 that matches the storage type identified in step S65, and the individual processing unit 26 specifies the control information using the operation procedure information 36 generated in step S65. The host group changing process corresponding to the volume 44 is executed for the storage 400 that has been changed (step S66), and the storage 400 returns the result of the changing process (step S67).

If it is confirmed in step S67 that the host group 45 change process has been performed normally, based on a request from the common processing unit 22, the repository management unit 23 registers the control information in the storage information 27 (step S68). ).
Specifically, based on the host group (hostgroup_id) specified in the control information, the corresponding host group information stored in the volume host group information 31 is identified, and the registered volume ID (Volumeid) is deleted. The volume ID newly designated by the control information is registered. Thereby, the volume corresponding to the volume host group 45 can be changed.
As described above, the product b is a storage type that does not have the volume host group 45, but the setting item of the volume host group information 31 is used to link the volume information 30 and the host group information 32. By replacing the setting items of the volume host group information 31, the host group 500 corresponding to the volume 44 can be changed.

  The repository management unit 23 passes the host group change permission / inhibition to the common processing unit 22 (step S69), and the common processing unit 22 returns a response “execution result” to the client terminal 100 via the transmission / reception unit 21 (step S70). . In the client terminal 100, when the transmission / reception unit 11 receives the message, the processing unit 12 displays the host group change permission / inhibition information on the volume creation result screen 503 (step S71), and ends the process.

  Although not shown in FIG. 24, when the host group change processing result is NG in step S67, there is a possibility that the control information received from the client terminal 100 is wrong, that is, the administrator's input is wrong. Therefore, the common processing unit 22 replies to the client terminal 100 via the transmitting / receiving unit 21 that “the host group change processing corresponding to the volume could not be performed”. In the client terminal 100, when the transmission / reception unit 11 receives the message, the processing unit 12 displays the result of the creation NG on the volume change result screen 506, and ends the process. The flow of processing for creating the operation procedure information 36 in step S65 is as described above with reference to FIGS.

Although the flow of processing for changing a volume-corresponding host group has been described with reference to FIGS. 21 to 24, other management information change, deletion, and reference processing are similarly performed. Further, the change and deletion processes can be configured such that the control information includes the processing order information. In this case, the individual processing section 26 is called by the individual processing calling section 25 based on the processing order information.
In step S15 in FIG. 6, step S35 in FIG. 12, step S45 in FIG. 17, and step S65 in FIG. 24, processing for confirming the request content requested by the control information is performed. Alternatively, it may be configured to execute processing according to the corresponding request content.

As described above, according to the present embodiment, the control device 200 can collectively manage a plurality of storages 400 having different storage types.
The storage device 929 of the control device 200 includes operation template information 34 that is a template for operation instructions, and setting information (a management unit included in the repository 35) for each management unit of the storage 400 (unit that configures the storage 400 from lower to higher). Is stored). The transmission / reception unit 21 receives control information regarding the storage 400 from the client terminal 100 as communication data.
Further, the common processing unit 22 extracts item information including at least the storage type in the setting information by comparing the communication data with the setting information, and specifies the storage type of the storage 400 to be processed based on the extracted item information. . Thereafter, by replacing the template item of the operation template information 34 with the value of the item information, the common processing unit 22 generates the operation procedure information 36 corresponding to the control information and corresponding to the specified storage type.
Based on the storage type specified by the common processing unit 22, the individual processing calling unit 25 determines the corresponding individual processing unit 26 from one or more individual processing units 26 that execute processing on the predetermined storage 400. The operation procedure information 36 is transferred to the individual processing unit 26. Further, the individual processing unit 26 executes processing in a predetermined storage 400 based on the operation procedure information.

The processing information can be included in the control information, and when the common processing unit 22 determines that the processing order information is included in the communication data (control information), the processing order information is transferred to the individual processing calling unit 25 and the individual processing is performed. The calling unit 25 delivers the operation procedure information 36 to the individual processing unit 26 based on the processing order information.
The individual processing unit 22 is provided with one or more according to the storage type, and executes processing for the storage 400 that matches the storage type specified in the operation procedure information 36 and matches the storage name included in the control information. .

  The operation template information 34 is stored according to the storage type, and the common processing unit 22 specifies the storage type of the storage 400 to be processed by collating the communication data with the setting information, and the operation corresponding to this storage type. Template information 34 is selected. The operation template information 34 is composed of one or more files as described above.

  The common processing unit 22 generates operation procedure information 36 that calls the individual processing unit 26 and delivers parameters to the individual processing unit 26 by replacing the template item of the selected operation template information 34 with the value of the item information. . The parameter constitutes a command statement of processing executed by the individual processing unit 26.

  The control information related to the storage 400 is information requesting any one of registration, change, deletion or reference processing to any setting information for each management unit. Based on this control information, the repository management unit 23 performs any of registration, change, deletion, or reference processing on the corresponding setting information.

  The setting information for each management unit is configured to be associated with each included ID, and the repository management unit 23 refers to the corresponding item information by sequentially referring to the ID included in the setting information.

The repository management unit 23 refers to the storage type correspondence information in which the management configuration for each storage type is stored, and this setting information ID corresponding to the management unit determined to have no corresponding storage type is set to this setting. The same value as the ID of the upper or lower setting information is set so that the higher setting information and the lower setting information are associated with each other.
By operating in this manner, depending on the storage type, even if there is a management unit that does not exist, necessary setting information can be referred to and a processing request according to the control information can be made.

FIG. 25 is a diagram illustrating an example of hardware resources of the client terminal 100 and the control device 200 used in the present embodiment.
In FIG. 25, the computer includes a system unit (not shown), a display device 901 having a display screen of CRT (Cathode Ray Tube) or LCD (Liquid Crystal Display), a keyboard 902 (K / B), a mouse 903, and an FDD 904. Hardware resources such as (Flexible Disk Drive) and CDD905 (Compact Disk Drive) are provided, and these are connected by cables and signal lines. The system unit is a computer and is connected to a LAN.

  Each computer includes a CPU 911 (also referred to as “arithmetic unit”, “microprocessor”, “microcomputer”, or “processor”) that executes a program. The CPU 911 is a processing device that is used to perform calculation, processing, reading, writing, and the like of data and information in each processing unit (to means) shown in FIGS. The CPU 911 includes a ROM 913 (Read / Only / Memory), a RAM 914 (Random / Access / Memory), a communication board 915, a display device 901, a keyboard 902, a mouse 903, an FDD904, a CDD905, a scanner device 906, and a magnetic disk. It is connected to the device 920 and controls these hardware devices. Instead of the magnetic disk device 920, a storage medium such as an optical disk device or a memory card reader / writer may be used.

  The RAM 914 is an example of a volatile memory. The storage media of the ROM 913, the FDD 904, the CDD 905, and the magnetic disk device 920 are an example of a nonvolatile memory. These are examples of the storage device (storage unit) 929 used by each computer. A communication board 915, a keyboard 902, a mouse 903, an FDD 904, a CDD 905, a scanner 906, and the like are examples of an input device (not shown). The communication board 915, the display device 901, and the like are examples of an output device (not shown).

The communication board 915 is connected to the network 300. The network 300 is not limited to a LAN, and may be configured by the Internet, a WAN, or the like.
The storage device (magnetic disk device) 920 stores an operating system 921 (OS), a window system 922, a program group 923, and a file group 924. The programs in the program group 923 are executed by the CPU 911, the operating system 921, and the window system 922. The program group 923 stores programs that execute the functions described as “to means” in the description of the present embodiment. The program is read and executed by the CPU 911. The file group 924 includes data and information described as “˜data”, “˜information”, “˜ID (IDentifier)”, “˜flag”, and “˜result” in the description of each embodiment. Signal values, variable values, and parameters are stored as items of “˜file”, “˜database”, and “˜table”. The “˜file”, “˜database”, and “˜table” are stored in a storage medium such as a disk or a memory. Data, information, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit, and extracted, searched, referenced, compared, and calculated. Used for processing (operation) of the CPU 911 such as calculation / control / output / printing / display. Data, information, signal values, variable values, and parameters are temporarily stored in the main memory, cache memory, and buffer memory during processing of the CPU 911 such as extraction, search, reference, comparison, calculation, control, output, printing, and display. Is remembered.

  In the block diagrams and flowcharts described in the description of each embodiment, arrows and portions mainly indicate data and signal input / output. Data and signals are stored in a memory such as a RAM 914, a flexible disk (FD) of the FDD 904, and a CDD 905. Recording is performed on a recording medium such as a compact disk (CD), a magnetic disk of the magnetic disk device 920, other optical disks, a mini disk (MD), and a DVD (Digital Versatile Disc). Data and signals are transmitted by a bus 912, a signal line, a cable, and other transmission media.

  In addition, what is described as “to means” in the description of each embodiment may be “to part”, “to circuit”, “to device”, and “to device”, and “to step”. , “˜step”, “˜procedure”, and “˜treatment”. That is, what is described as “˜means” may be realized by firmware stored in the ROM 913. Alternatively, it may be realized only by software, or only by hardware such as an element, a device, a board, and wiring, or a combination of software and hardware, and further by a combination of firmware. Firmware and software are stored as programs in a recording medium such as a magnetic disk, flexible disk, optical disk, compact disk, minidisk, or DVD. This program is read by the CPU 911 and executed by the CPU 911. That is, the program causes the computer to function as “to means” described in the description of each embodiment. Alternatively, the procedure or method of “means” described in the description of each embodiment is executed by a computer.

  21 transmission / reception unit (control device transmission / reception unit), 22 common processing unit (control device common processing unit), 23 repository management unit, 25 individual processing call unit, 26 individual processing unit, 27 to 33 setting information for each management unit (27 storage Information, 28 storage group information, 29 storage pool information, 30 volume information, 31 volume host group information, 32 host group information, 33 host information), 34 operation template information, 36 operation procedure information, 100 client terminal, 200 control device ( Storage control device), 300 network, 400 storage (storage device), 929 storage device.

Claims (7)

A storage control device connected to a storage device and a client terminal via a network,
Storage means for storing operation template information, which is a template of operation instructions according to the storage type, and setting information for each management unit of the storage device;
A control device transmission / reception unit that receives control information related to the storage device from the client terminal as communication data;
The matching between the communication data and the setting information, extracts the item information including at least the storage type in the setting information, the extracted item information, selects the operation template information corresponding to the storage type, the operation By replacing the template item of the template information with the value of the item information, it is possible to call the individual processing unit corresponding to the control information and execute processing to a predetermined storage device, and to pass the parameter to the individual processing unit. A control device common processing unit for generating operation procedure information to be performed ;
Based on the operation procedure information, an individual process calling unit that calls a predetermined individual processing unit and delivers the operation procedure information as a parameter to the individual processing unit;
A storage control device.   The individual processing unit is provided according to the storage type, and executes processing for a storage device that matches the storage type specified in the operation procedure information and matches the storage name included in the control information. The storage control device according to claim 1. When it is determined that the communication data includes processing order information, the control device common processing unit passes the processing order information to the individual processing calling unit,
3. The storage control apparatus according to claim 1, wherein the individual processing calling unit sequentially calls the individual processing units based on the received processing order information. The control information related to the storage device is information for requesting any one of registration, change, deletion or reference processing to any setting information for each management unit,
Furthermore, the repository management part which performs any one process of registration, a change, deletion, or a reference with respect to applicable setting information based on the said control information is provided. The storage control device described. The setting information for each management unit is configured to be associated with each included ID,
5. The storage control apparatus according to claim 4, wherein the repository management unit refers to corresponding item information by sequentially referring to IDs included in the setting information. The repository management department
By referring to the storage type correspondence information storing the management configuration for each storage type, the setting information ID corresponding to the management unit that is determined not to have the corresponding storage type is set to the upper setting of this setting information. 6. The storage control apparatus according to claim 4, wherein the same value as the ID of the upper or lower setting information is set so that the information and the lower setting information are associated with each other. A storage control program that causes a computer to function as the storage control device according to any one of claims 1 to 6.

Images