JP2011081579A - System operation management method and system for virtual resource in it system virtualization - Google Patents

Abstract

PROBLEM TO BE SOLVED: To manually check the contents of a configuration change to a physical device for a reserved virtual resource and create a check list regarding the configuration change in advance in operation management of a conventional IT system. There was a risk of human error due to manual work.
SOLUTION: One or more computers capable of setting a virtual computer, one or more storage devices capable of setting a virtual storage, and a fiber channel switch capable of setting a virtual SAN by connecting the computer and the storage In a system comprising a device and a management computer connected to the computer, the storage device, and the Fiber Channel switch via a network capable of setting a virtual network, the management computer includes virtual resource configuration management information, It has resource configuration management information, searches for operations of virtual resources and physical resources at a specified time, and dynamically outputs the search results as a check list.
[Selection] Figure 17

Description

  The present invention relates to reservation management of virtualized IT resources allocated to physical IT devices by application of server virtualization technology.

  In recent years, with the spread of server virtualization technology, the spread of cloud computing and the like that handles the entire IT system in a virtual manner has been promoted. In such IT system virtualization, in system operation management, in addition to conventional management of physical IT devices (physical resources), virtualized IT resources (virtual resources) and physical resources held by them The correspondence will be further managed. In addition, since IT system virtualization is used to improve the utilization efficiency of physical resources, management of enormous virtual resources is performed more than management of physical resources.

  At this time, since many virtual resources share a physical resource, there is a high risk that an erroneous operation on the virtual resource affects other virtual resources. In general, a virtual resource has a characteristic that it cannot be physically confirmed directly by human perception, and it is indispensable to support IT technology in order to prevent erroneous operation and to perform safe management and operation.

  Generally, in system operation management, a database management system is used as resource management, and a list of IT resources to be managed, configuration information (connection information between IT resources to be managed), and monitoring results of each IT resource are retained. And manage. The IT resource here refers to a server device, a network switch device, a fiber channel switch device (FC switch device), a storage device, and the like. In the IT system virtualization, management targets such as a virtual server device, a virtual network (VLAN), a virtual SAN, and a virtual storage device are further added.

  Patent Document 1 discloses that an IT system that provides a work environment from broadcasting station video production to on-air manages video data held in a storage device as a virtual resource called a virtual video tape, and has a video input / output interface. A program that records and plays back video data on the server device manages the process being executed as a virtual resource called a virtual video deck device, and provides the operator with the same functions and operations as using a physical video deck. Techniques for providing methods are disclosed. This technology allows management of virtual resources and operations on physical resources necessary for the operations. Non-Patent Document 1 discloses information management technology for handling a time period in a database management system. With this technology, it is disclosed that reservation management of resources can be performed by a relational database.

JP-A-10-011339

Richard T. Snodgrass, "Developing Time-Oriented Database Applications in SQL", Morgan Kaufmann Publishers, 2000. (http://www.cs.arizona.edu/people/rts/tdbbook.pdf) pages 10 to 23

  Since the configuration of the IT system differs depending on the user, different virtual systems will coexist with physical resources even when virtualized. In such a usage mode, when building a virtual system, make sure that the necessary virtual resources are available on the spot, and that there is no problem with the configuration change to the physical resources that occurs at that time. It becomes difficult to confirm.

  For this reason, prior to the construction of the virtual system, necessary virtual resources are reserved in the management ledger or the like in advance. Then, the contents of the configuration change to the physical device for the reserved virtual resource are manually checked, and a check list regarding the configuration change is manually created in advance. Then, based on a check list created in advance by hand, the administrator's approval is obtained, and the virtual system is actually constructed.

  However, in general, the construction of a plurality of virtual systems occurs at the same time, so even if a configuration change to a physical device related to the construction of each virtual system is manually examined, It is also difficult to confirm that no malfunction occurs as a whole operation. For example, if 1000 virtual servers are repeatedly built and disassembled every month, the calculation will require 30 or more configuration changes per day, which will require a lot of manpower and the risk of frequent human errors. Increases the nature. In addition, after performing operations on the device, it is not enough to check the status of the physical resource, and it is not enough to check the status of the physical resource, and it is necessary to check the status of the virtual resource. The danger such as becomes high.

  In other words, it is very difficult to manually create a checklist in the IT resource reservation management of the conventional method, and the checklist created manually is not necessarily reliable. There was a problem.

  In order to solve the above-described problems, a system and a system operation management method according to the present invention include one or more computers that can set a virtual computer, one or more storage devices that can set a virtual storage, and the computer. A fiber channel switch device capable of setting a virtual SAN by connecting the storage and the storage, and a management computer connected to the computer, the storage device and the fiber channel switch via a network capable of setting a virtual network. It is assumed that the system is equipped.

  The management computer includes at least one arithmetic device and a storage unit, and manages the virtual computer, the virtual network, the storage, and the virtual SAN as virtual resources, and the computer, the network, The storage device and the fiber channel switch device are managed as physical resources. The storage unit of the management computer has a first configuration having attribute information of the virtual resource, configuration information that holds a correspondence relationship between the virtual resource and the physical resource, and management information of a reservation time of the virtual resource Management information, attribute information of the physical resource, operation contents to be developed on the physical resource, and second configuration management information that holds a schedule thereof are held.

  Then, the management computer searches the first configuration management information, determines whether or not there is a reservation time of the virtual resource included in the specified time, and has a reservation time of the virtual resource included in the specified time A physical resource corresponding to the virtual resource is specified, the second configuration management information is searched, an operation content at the specified time of the specified physical resource is acquired, and the acquired operation content is It is characterized by outputting.

  According to the present invention, the system operation management server automatically creates a pre-check list of the configuration change operation on the device based on the reserved virtual system configuration information. Occurrence can be prevented.

Overall configuration of physical system of this embodiment Internal configuration of server device of this embodiment Memory of server device of this embodiment Internal configuration of storage device of this embodiment Internal configuration of the system operation management server device of this embodiment Memory of the system operation management server of this embodiment Internal configuration of the system operation management agent server device of this embodiment Memory of the system operation management agent server device of this embodiment Configuration example of virtual system of this embodiment Internal configuration of the virtual server device of this embodiment Example of allocation of virtual system of this embodiment to physical system Overview of configuration information reservation management database of this embodiment (1) Outline of configuration information reservation management database of this embodiment (2) Overview of configuration information reservation management database of this embodiment (3) Overview of configuration information reservation management database of this embodiment (4) Overview of configuration information reservation management database of this embodiment (5) Overview of reservation management of this embodiment Macro procedure of virtual system construction of this embodiment Configuration of the table “reservation management” of this embodiment Configuration of group reservation management table group of this embodiment Configuration of element reservation management table group of this embodiment (1) Configuration of element reservation management table group of the present embodiment (2) Configuration of group history management table group of this embodiment Configuration of element history management table group of this embodiment (1) Configuration of element history management table group of this embodiment (2) Configuration of the system operation management agent configuration management database of this embodiment (1) Configuration of system operation management agent configuration management database of this embodiment (2) Configuration of system operation management agent configuration management database according to the present embodiment (3) Operation of virtual system construction of this embodiment Operation of configuration information reservation management database operation of this embodiment Operation for creating a pre-configuration change checklist for device operation of this embodiment System inspection operation of this embodiment System monitoring operation of this embodiment Operation of automatic execution base of device operation of this embodiment Operation of DBMS of this embodiment Operation of the system operation management agent server device of this embodiment Output example of pre-configuration change checklist of this embodiment

  An outline of a system operation management server device to which the present invention is applied will be described. The system operation management server device to which the present invention is applied includes, for example, a connector management table that holds physical resource attribute information in a database record (DB record), virtual resource attribute information, and a physical resource that holds the virtual resource. Configuration management table, an element management table that holds a reservation period of use start date and time and use end date and time as a DB record, and a group management table that holds identification information of virtual resources constituting the IT system as a DB record It has an information reservation management database, and in the DB record of the connector management table, it holds a list of operations for physical resources and details of operations that occur to physical devices. When making a virtual system construction reservation, the configuration information reservation management database Reserve virtual resources to use When creating a pre-check list for configuration change, search the configuration information reservation management database for the DB record of the virtual resource with the specified start date or end date using the specified date as the search key. Then, the physical resource corresponding to the virtual resource is obtained from the search result, the connector management table is further searched from the physical resource identification information, the operation content to the device is acquired, and the operation is output to the operator. The system operation management server device is characterized in that:

  The system operation management server apparatus to which the present invention is applied includes, for example, a connector management table that holds physical resource attribute information as a database record (DB record), virtual resource attribute information, and a physical resource that holds the virtual resource. Resource correspondence information, an element management table that holds reservation dates of use start date and time and use end date and time as DB records, and a group management table that holds identification information of virtual resources constituting the IT system as DB records It has a configuration information reservation management database, and holds a list of operations for physical resources and operation contents that occur for physical devices in the DB record of the connector management table. Reserve virtual resources for use in the database When the virtual system construction is executed, the designated date is used as a search key from the configuration information reservation management database, and the virtual resource DB record having the same use start or end date is searched, The physical resource corresponding to the virtual resource is obtained from the search result, the connector management table is further searched from the physical resource identification information, the operation content to the device is acquired, and the operation is instructed to the device. Is a system operation management server device characterized by

  The system operation management server device to which the present invention is applied includes, for example, a connector management table that holds physical resource attribute information as a database record (DB record), virtual resource attribute information, and a physical resource that holds the virtual resource. Resource correspondence information, an element management table that holds reservation dates of use start date and time and use end date and time as DB records, and a group management table that holds identification information of virtual resources constituting the IT system as DB records A configuration information reservation management database, a virtual resource and a physical resource obtained by system monitoring, and a configuration information history management database that holds the configuration information in the same table format as the configuration information reservation management database are provided. In the virtual system inspection, the above configuration Compared with broadcast management database contents of the configuration information history management database, what is a difference, to the operator, a system management server apparatus characterized by operative to notify.

  Embodiments to which the present invention is applied will be specifically described below with reference to the drawings. First, the physical system configuration of this embodiment will be described with reference to FIGS. As shown in FIG. 1, this system has a central operation management site 101, one or more data center sites 102, a management WAN 105, and the Internet / WAN 111.

  The central operation management site 101 includes one or more system operation management server devices 103, and the system operation management server device 103 is connected to the management WAN 105 through a data path 113.

  The management WAN 105 may use a dark fiber connection service, a leased line service, or a VPN connection service on the Internet provided by a telephone / communication company.

  The data center site 102 includes a system operation management agent server device 104, a management network 106, one or more network switch devices 107, one or more server devices 108, and one or more fiber channel switch devices (FC switch devices) 109. One or more storage apparatuses 110 and a backbone network 112 are included.

  The system operation management agent server device 104 is connected to the management WAN 105 via the data path 114 and is connected to the management network 106 via the data path 115.

  The management network 106 may be a communication network that performs IP communication. The backbone network 112 may be a communication network that performs IP communication. The backbone network 112 is connected to the Internet / WAN 111 by a data path 120 and is connected to the network switch device 107 by a data path 121.

The network switch device 107 may be any device that supports IP communication, has a VLAN function, and can change settings via the management network. However, depending on the model, there is an instruction to the switch device via the server device that operates the management software provided by the switch manufacturer. In this case, from the management network via this server device, Replace with a configuration that issues operation instructions to the device. The network switch device 107 is connected to the server device 108 by the data path 122. Further, in order to receive a setting change operation instruction, it is connected to the management network 106 through a data path 116.
The server device 108 is connected to the management network 106 via the data path 117, and is connected to the FC switch device 109 via the data path 123. Details of the server device 108 will be described later with reference to FIG.

  The FC switch device 109 is a fiber channel switch device that constitutes a storage area network (SAN) that connects a server device and a storage device to a fiber channel, has a virtual SAN function, and can change settings via a management network. Anything is fine. Virtual SANs have different implementation methods and names depending on the switch manufacturer. For example, Brocede in the United States is called LSAN (Logical SAN), and provides a method for group management of WWN (World Wide Name) which is identification information of HBA. In addition, the Cisco company, USA, is referred to as VSAN (Virtual SAN), which is defined by the ANSI / T11 standard and provides a method for attaching an identification tag to a data frame during data transfer. Although there is no data connection compatibility with each other, there is commonality in device operations such as addition and deletion of members to and from the virtual SAN, and they can be handled in the same form in terms of operation management.

  However, depending on the model, there is an instruction for operating the switch device via the server device in which the management software provided by the FS switch device manufacturer is operated. In this case, from the management network, this server device is used. Then, it is read as a configuration that issues an operation instruction to the apparatus. The FC switch device 109 is connected to the server device 108 via the data path 123 and is connected to the storage device 110 via the data path 124. Further, in order to receive a setting change operation instruction, it is connected to the management network 106 through a data path 118.

  FIG. 2 shows the internal configuration of the server apparatus 108. The server apparatus 108 includes an MPU 201, a memory 202, a P-NIC 203, a P-HBA 204, and a data bus 205 that connects them.

  The MPU 201 may be a general microprocessor. The memory 202 may be a semiconductor memory or a storage device.

  The P-NIC 203 indicates a physical network interface card (NIC). The P-NIC 203 is connected to the network switch device 107 by the data path 122 and is connected to the management network 106 by the data path 177. Also, when using a NIC having one port, two NICs may be used.

  The P-HBA 204 may be a physical Fiber Channel host bus adapter (HBA) that supports “N Port ID Vitalization” (NPIV), which is a standard defined by ANSI / T11. By the NPIV function, a virtual server device that can be specified by WWN and has a virtual HBA is provided. The P-HBA 204 is connected to the FC switch device 109 via the data path 123.

  FIG. 3 shows the configuration of the memory 202 of the server apparatus 108. The memory 202 holds a hypervisor program 301 and one or more virtual server device information 302.

  The hypervisor program 301 is basic software for realizing one or more virtual servers on the server device. For example, the hypervisor program 301 may be a product “VMware ESX Server” manufactured by US VMware, a product “Virtage” manufactured by Hitachi, Ltd. Note that the hypervisor program 301 only needs to have a function of receiving an operation instruction for generating or deleting a virtual server or changing a configuration through communication via the management network 106 and executing the instruction.

  The virtual server device information 302 is a storage area that holds configuration information of a virtual server device operated on the server device, and is used by the hypervisor program 301 and the virtual server device associated with the virtual server device information 302. The

  FIG. 4 shows the internal configuration of the storage apparatus 110. The storage device 110 has a disk controller 401 and one or more HDs 402. The disk controller 401 is connected to one or more HDs 402 by one or more data paths 124. The data path 124 is connected to the FC switch device 109 and transmits / receives data of the storage device. The data path 119 is connected to the management network 106, and the disk controller 401 receives an operation instruction to the apparatus through IP communication. Depending on the model, an operation instruction may be sent directly from the management network 106 via a server device that operates management software provided by the storage manufacturer without receiving an operation instruction.

  In this case, it may be replaced with this server device. As an operation instruction to the storage apparatus, LU (Logical Unit) can be created, deleted, and set. As for the setting, it is only necessary to include setting of LUN (Logical Unit Number) masking. Here, the LUN masking function is a function that restricts the HBA on the server apparatus side that can generally access the LU of the specified LUN. At this time, both the physical HBA and the virtual HBA specify WWN (World Wide Name) as identification information.

  FIG. 5 shows the internal configuration of the system operation management server apparatus 103. The system operation management server apparatus 103 includes an MPU 501, a memory 502, a NIC 503, a user IF 504, and a data bus 505 that connects them.

  The MPU 501 may generally be a microprocessor. The memory 502 may be a semiconductor memory or a storage device.

  The NIC 503 may be a network interface card. The data path 113 connects to the management WAN 105.

  The user IF 504 may be an interface card for connecting and using a display device 506, a keyboard device 507, and a pointing device 508 such as a mouse device. Through these devices, information is displayed to the operator and instructions are received. It should be noted that the system operation management server apparatus 103 is equipped with a Web server program and an operation instruction or information display is performed from an external Web browser terminal. This will be described in this form.

  FIG. 6 shows the configuration of the memory 502 of the system operation management server apparatus 103. The memory 502 includes a virtual system construction program 601, a configuration information reservation management database operation program 602, a pre-check list creation program 603, an automatic execution base program 604, a system monitoring program 605, a system inspection program 606, one or more virtual system construction templates 607, DBMS program 608, configuration information reservation management database 609, configuration information history management database 610, system operation management agent management database 611, and work area 612. The operator executes each program as necessary. The operation of each program and the contents of the data area such as the database will be described later.

  FIG. 7 shows the internal configuration of the system operation management agent server device 104. The system management agent server apparatus 104 includes an MPU 701, a memory 701, a NIC 703, a user IF 704, and a data bus 705 that connects them.

  The MPU 701 may be a general microprocessor. The memory 702 may be a semiconductor memory or a storage device.

  The NIC 703 may be a network interface card (NIC). The NIC 703 is connected to the management network 106 by the data path 115 and is connected to the management WAN 105 by the data path 114. When using a 1-port NIC, it is possible to use a single NIC.

  The user IF 704 may be an interface card for connecting and using a pointing device 708 such as a display device 706, a keyboard device 707, and a mouse device. Through these devices, information is displayed to the operator and instructions are received. It should be noted that the system operation management agent server device 104 is equipped with a Web server program, and an operation instruction and information display can be performed from an external Web browser terminal. This will be described in this form.

FIG. 8 shows the configuration of the memory 702 of the system operation management agent server device 104.
The memory 702 includes a system operation management agent program 801, a server connector program 802, a storage connector program 803, a network connector program 804, and a SAN connector program 805. Each of the server connector program 802, the storage connector program 803, the network connector program 804, and the SAN connector program 805 operates to convert an operation instruction from the system operation management server device into an operation instruction unique to the device. As a plug-in software for each device, a program form that can be dynamically installed may be used. The operation of the program will be described later.

  FIG. 9 shows a configuration example of a virtual system realized on the physical IT system described above. This is an example for simplifying the description, and implementation of the present invention may be carried out other than this configuration.

  The virtual system includes a virtual network A 901, a virtual firewall (virtual FW) 902, a virtual network B 903, one or more virtual servers 904, a virtual server 905, a virtual SAN 906, and one or more LU 907 and LU 908. The data path 909 connects the virtual network A 901 and the virtual FW 902. The data path 910 connects the virtual FW 902 and the virtual network B 903. The data path 911 connects the virtual network B 903 and the virtual server 904, and the data path 912 connects the virtual network B 903 and the virtual server 905. The data path 913 connects the virtual server 904 and the virtual SAN 906, and the data path 914 connects the virtual server 905 and the virtual SAN 906. The data path 915 connects the virtual SAN 906 and the LU 907, and the data path 916 connects the virtual SAN 906 and the LU 908. This is a configuration that cannot be distinguished as one of general IT systems if it is configured with physical resources instead of virtual resources.

  The virtual FW 902 is a virtual firewall device that operates to connect virtual networks and selectively communicate data with each other. In this embodiment, it is assumed that firewall software is installed and used in a virtual server, and handled as different types of virtual servers.

  FIG. 10 shows the internal configuration of the virtual server 904. The virtual server 904 includes a v-MPU 1001, a v-memory 1002, a v-NIC 1003, a v-HBA 1004, and a data bus 1005 connecting them. The v-NIC 1003 is connected to the virtual network B 903 via the data path 911. The v-HBA 1004 is connected to the virtual SAN 906 through the data path 913. Other virtual servers 905 also have the same internal configuration.

  The v-MPU 1001 indicates a virtual microprocessor. The v-memory 1002 indicates a virtual memory. The v-NIC 1003 indicates a virtual network interface card, and the v-HBA 1004 indicates a virtual Fiber Channel host bus adapter. These are all virtual resources realized by the operation of the hypervisor program 301.

FIG. 11 shows a configuration example in which the virtual resources constituting the virtual system are allocated to the physical resources constituting the physical system. This is a configuration example for simplifying the description, and the present invention may be implemented in other configurations.
The network switch device 107 includes a virtual network A 901 and a virtual network B 903.

  The server device 108 has a virtual server 904. The server device 1101 includes a virtual server 905 and a virtual firewall 902.

  The FC switch device 109 has a virtual SAN 906.

  The storage device 110 has an LU 907. The storage apparatus 1102 has an LU 908. Taking the above assignment as an example, an outline of the configuration information reservation management database 609 will be described below.

  An outline of the table of the configuration information reservation management database 609 will be described with reference to FIGS.

  The tables held in the configuration information reservation management database 609 are classified into three: a reservation management table group 1201, a group management table group 1214, and an element management table group 1401.

  The reservation management table group 1201 includes a reservation management table 1202 for registering records in units of reservation contracts from users.

  The group management table group 1214 includes a table “system level logical partition reservation management” 1203 that holds a record that summarizes the configuration of the virtual system, a table “NW logical partition reservation management” 1204 that holds a record that summarizes the member configuration of the virtual network, It has a table “SAN / storage logical partition reservation management” 1205 that holds records that summarize SAN member configurations. Since the records in these tables hold the connection relationships 1210, 1211, 1212, and 1213 between virtual resources, each record holds the identification information of the connection destination record as column information.

  In addition, when using a relational database management system for database management, the number of connection relationships cannot be fixed, so the maximum number of columns that indicate connection relationships in the record definition is assumed. However, there may be a method in which the connection relation is divided into a predetermined number of records by a record having a predetermined number of connection relation columns. Hereinafter, in the table definition to be described, one connection relationship is held in one record, which will be described.

  The element management table group 1401 includes a table “virtual FW reservation management” 1402 that holds records that summarize the attributes of the virtual firewall device, a table “virtual server reservation management” 1403 that summarizes the attributes of the virtual server, and a record that summarizes the attributes of the virtual SAN. A table “virtual SAN reservation management” 1404 holding a record, a table “virtual NW reservation management” 1405 holding a record summarizing the attributes of the virtual network, and a table “LU reservation management” 1416 holding a record summarizing the attributes of the LU. .

  In FIG. 13, a record 1206 of a table “system level logical partition reservation management” 1203, a table “NW logical partition reservation management” 1204, a table “SAN / storage logical partition reservation management” 1205, a table “virtual FW reservation management” 1402, a table A connection relationship of records held by “virtual server reservation management” 1403 is shown. For example, the record 1207 holds the member configuration of the virtual network B 903. A record 1208 holds the member configuration of the virtual network A 901. A record 1209 holds the member configuration of the virtual SAN 906. A record 1407 holds virtual firewall device attribute information. Records 1408 and 1409 respectively hold virtual server attributes. The definition of each table will be described later.

  FIG. 14 shows a connection relationship of records held in the table “NW logical partition reservation management” 1204, the table “virtual FW reservation management”, the table “virtual NW reservation management” 1405, and the table “virtual server reservation management” 1403. Each record 1207, 1208 of the table “NW logical partition reservation management” 1204 holds the attribute of the virtual network, and holds members of the respective virtual networks as connection relationships 1501 to 1506.

  FIG. 15 shows the connection relationship of records held in the table “SAN / storage logical partition reservation management” 1205, the table “virtual server reservation management” 1403, the table “virtual SAN reservation management” 1401, and the table “LU reservation management” 1406. . A record 1209 of the table “SAN / storage logical partition reservation management” 1205 holds the connection relationships 1601 to 1605 as member configurations of the virtual SAN 906.

  In the following, an outline of management of the correspondence between each virtual resource and the physical resource holding it will be described with reference to FIG.

  The system operation management agent management database 611 has a connector management table group 2801. The connector management table group 2801 includes a table “NW connector management” 1702 that holds a record that summarizes the attributes and operation contents of the network switch device, and a table “server connector management” 1703 that holds a record that summarizes the attributes and operation contents of the server device. There is a table “SAN connector management” 1704 that holds a record that summarizes the attributes and operation details of the FC switch device, and a table “storage connector management 1705” that holds a record that summarizes the attributes and operation details of the storage device. Records in each table are registered corresponding to each device. Here, the attribute is, in particular, information on a connection destination via the management network. Further, the operation content here means the operation content (script or the like) based on the specifications of each device with respect to a predetermined request from the system operation management server.

  The records in the element management table group 1401 in the configuration information reservation management database 609 correspond to virtual resources, and these records hold correspondence relationships 1710 to 1717 with corresponding physical resources, respectively, as connection relationships. To do.

The outline of the configuration information reservation management database 609 and the system operation management agent management database 611 has been described above by taking the above-described virtual system as an example.
Next, an outline of reservation management will be described with reference to FIG.

  FIG. 17 shows a group management table group 1214 in which the record 1205 of the table “reservation management” 1202 is read as a reservation record (Z) and the reservation record (Z) is the target range 1801, and records in the element management table group 1401 , And a reservation record (Z), a state in which reservations of necessary virtual resources are entered is shown. Here, the registration of records in each table may be a method of holding only records that hold a reserved period, but in the following description, a description will be given on the premise that a period of no reservation is registered as a record. This makes it possible to improve the search time and simplify the explanation regarding the search processing for virtual resources without reservation.

  FIG. 18 shows a macro procedure when constructing a virtual system. It consists of 5 steps.

  In the first step 1904, based on the configuration of the virtual system, the record registration shown in FIGS. 12 to 15 is executed, and the configuration information is registered in the configuration information reservation database 609. At this time, the configuration of the virtual system may be prepared in advance as a virtual system template 1903. In the following description, it is assumed that a template is prepared in advance for easy explanation.

  In the second step 1905, from the configuration information registered in the configuration information reservation management database 609, the use start date is designated, the table of the element reservation management table group is searched, and from each search result, Trace the records in the connector management table group and collect the operation details. The pre-checklist is created by classifying / sorting the collected operation contents.

  In the third step 1906, the operation contents collected in the second step 1905 are registered in a schedule to be automatically executed so that they are designated and executed at another date and time.

  In the fourth step 1907, the registered operation content is executed based on the schedule to be automatically executed.

  In a fifth step 1908, a system check is performed to determine whether or not a planned state is obtained as a result of the operation content executed in the fourth step 1907. As described above, the virtual system is constructed by the five steps.

  Hereinafter, with reference to FIG. 19 to FIG. The table definition of each database is explained. First, the table definition of the configuration information reservation management database 609 will be described with reference to FIGS.

  The table “reservation management” 1202 illustrated in FIG. 19 includes a column “start date / time” 2002, a column “end date / time” 2003, a column “identification information” 2004, a column “customer identification information” 2005, and a column “reservation target group identification information”. 2006.

  A column “start date / time” 2002 is information on the start date / time of the reservation. The column “end date and time” 2003 is information on the end date and time of the reservation. The date / time information may be defined by separating the date and time as separate columns. The column “identification information” 2004 may be information identifying a reservation. You can use a serial number or a string that does not overlap.

  The column “customer identification information” 2005 may be information identifying a customer such as a customer management number and character string information such as a customer name. This is a column for enabling the same customer to distinguish reservations for a plurality of virtual elementary systems over time.

  The column “reservation target group identification information” 2006 holds the identification information of the record of the system level logical partition corresponding to the virtual system to be reserved. Hereinafter, “identification information” in any table definition will be described on the premise that serial numbers without duplication hold character strings.

  19 and 20, table definitions of the table “system level logical partition reservation management” 1203, the table “NW logical partition reservation management” 1204, and the table “SAN / storage logical partition reservation management” 1205 will be described.

  The table “system level logical partition reservation management” 1203 includes a column “start date / time” 2103, a column “end date / time” 2104, a column “reservation identification information” 2105, a column “identification information” 2106, a column “member type” 2107, a column “Member identification information” 2108.

  A column “reservation identification information” 2105 holds identification information of a reservation for which the system level logical division is to be reserved. As the identification information of the reservation, the identification information held in the table “reservation management” is used. If the reservation is not indicated, the reservation identification number is set to a predetermined value (for example, -1). In addition, regarding the unreserved record, the column “end date and time” is set to the maximum value, and it will be described below that it is not reserved from the column “start date and time” to the end date.

  A column “identification information” 2106 is identification information for specifying a system level logical partition.

  The column “member type” 2107 holds information for specifying which type the member belongs to since there are several types of members constituting the system level logical partitioning. This type includes virtual FW (firewall), VM (virtual server), NW logical partition, SS logical partition (SAN / storage logical partition), and the like. A column “member type” 2107 holds values for specifying these.

  A column “member identification information” 2108 holds identification information of members constituting the system level logical partitioning.

  The table “NW logical partition reservation management” 1204 includes a column “start date and time” 2111, a column “end date and time” 2112, a column “reservation identification information” 2113, a column “identification information” 2114, a column “identification information of upper group” 2115, A column “member type” 2116 and a column “member identification information” 2117;

  The table “SAN / storage logical partition reservation management” 1205 includes a column “start date and time” 2119, a column “end date and time” 2120, a column “reservation identification information” 2121, a column “identification information” 2122, and a column “identification information of upper group”. 2123, a column “member type” 2124, and a column “member identification information” 2125.

  The table “NW logical partition reservation management” 1204 and the table “SAN / storage logical partition reservation management” 1205 are the same as the table “system level logical partition reservation management” 1203, and the configuration and definition of the columns are the same.

  A table “virtual NW routing reservation management” 2126 is a table that holds configuration information when two or more virtual networks are connected to each other. This is realized, for example, by combining a plurality of VLANs so that communication can be performed between a plurality of virtual systems or a limitation of the specifications of the network switch device, which is essentially limited to one virtual network. Use when necessary.

  The table “virtual NW routing reservation management” 2126 includes a column “start date and time” 2172, a column “end date and time” 2128, a column “reservation identification information” 2129, a column “identification information” 2130, and a column “identification information of the upper group”. 2131, column “virtual NW identification information A” 2132, and column “virtual NW identification information B” 2133.

  The column “start date and time” 2172, the column “end date and time” 2128, the column “reservation identification information” 2129, and the column “upper group identification information” 2131 have the same definitions as the table “system level logical partition reservation management” 1203.

  The column “identification information” 2130 is virtual network routing identification information managed by this record, and may be a serial number without duplication or a character string without duplication.

  A column “virtual NW identification information A” 2132 and a column “virtual NW identification information B” 2133 are columns holding the identification information of the two virtual networks to be routed managed by this record. By following the identification information held in the columns 2132 and 2133, it is possible to specify the network switch device for which this routing setting is performed.

  The table “virtual SAN routing reservation management” 2134 is a table that holds configuration information when two or more virtual SANs are connected to each other. This is realized, for example, by a combination of a plurality of VSANs or the like that enables communication between a plurality of virtual systems, or a limitation of the specifications of the FC switch device, which originally only requires one virtual SAN. Use when necessary.

The table “virtual SAN routing reservation management” 2134 includes a column “start date and time” 2135, a column “end date and time” 2136, a column “reservation identification information” 2137, a column “identification information” 2138, and a column “identification information of an upper group”. 2139, column “virtual SAN identification information A” 2140, and column “virtual SAN identification information B” 2141.
The column “start date / time” 2135, the column “end date / time” 2136, the column “reservation identification information” 2137, and the column “higher level group identification information” 2139 have the same definitions as the table “system level logical partition reservation management” 1203.

  The column “identification information” 2138 is virtual network routing identification information managed by this record, and may be a serial number without duplication or a character string without duplication.

  A column “virtual SAN identification information A” 2140 and a column “virtual SAN identification information B” 2141 are columns holding identification information of two virtual networks to be routed managed by this record. By following the identification information held in the columns 2140 and 2141, it is possible to specify the FC switch device for which this routing setting is performed.

  The definition of each table of the element reservation management table group 2225 will be described with reference to FIGS.

  The table “virtual server reservation management” 1403, the table “virtual FM reservation management” 1402, the table “LU reservation management” 1416, the table “virtual NW reservation management” 1405, and the table “virtual SAN reservation management” 1404 are all columns having the same definition. In the following, only the definition of the column “virtual server reservation management” 1403 will be described for the common column definition, and only the definition of the non-common column will be described.

  The table “virtual server reservation management” 1403 includes a column “start date / time” 2202, a column “end date / time” 2203, a column “reservation identification information” 2204, a column “identification information” 2205, a column “upper group identification information” 2206, a column It has “server connector identification information” 2207 and a column “VM property information” 2208.

  The column “identification information” 2205 is identification information of a virtual server managed by this record, and may be a serial number without duplication or a character string without duplication.

  A column “server connector identification information” 2207 is information for specifying a physical server device holding a virtual server managed by this record, and this value is a column “system operation management agent configuration management” 2702 described later. The value of “connector identification information” 2703 is used.

  A column “VM property information” 2208 holds virtual server attribute values, and holds values such as CPU type and memory capacity, for example. Further, as described above, in addition to a method of holding a plurality of attribute values as one structure data in one column, it is possible to implement the present invention by providing separate columns.

  The table “virtual FM reservation management” 1402 includes a column “FW property information” 2216 in addition to the common columns described above.

  A column “virtual FM reservation management” 2216 holds a virtual firewall attribute value managed by this record, and holds values such as a list of protocols to be filtered as firewall setting information, for example. Further, as described above, in addition to a method of holding a plurality of attribute values as one structure data in one column, it is possible to implement the present invention by providing separate columns.

  The table “LU reservation management” 1416 holds a column “storage connector identification information” 2223 and a column “LU property information” 2224 in addition to the common columns described above.

  A column “storage connector identification information” 2223 is identification information for specifying a storage apparatus that holds the LU for record management, and is held in a column “connector identification information” 2703 of a table “system operation management agent configuration management” 2702 described later. Value to use.

  The column “LU property information” 2224 holds LU attribute information managed by this record, and holds values such as storage capacity and volume attribute, for example. Further, as described above, in addition to a method of holding a plurality of attribute values as one structure data in one column, it is possible to implement the present invention by providing separate columns.

  The table “virtual NW reservation management” 1405 illustrated in FIG. 22 includes a column “network connector identification information” 2307 and a column “VLAN property information” 2308 in addition to the common columns described above.

  A column “network connector identification information” 2307 is identification information for specifying a network switch device that holds a virtual network managed by this record. A column “connector identification information” 2703 of a table “system operation management agent configuration management” 2702 described later. Use the value held in.

  The column “VLAN property information” 2308 is a column that holds the attribute value of the virtual network managed by this record, and holds, for example, the tag number of the tag VLAN. Further, as described above, in addition to a method of holding a plurality of attribute values as one structure data in one column, it is possible to implement the present invention by providing separate columns.

  The table “virtual SAN reservation management” 1404 includes a column “SAN connector identification information” 2315 and a column “virtual SAN property information” 2316 in addition to the common columns described above.

  The column “SAN connector identification information” 2315 is identification information for identifying the FC switch device that holds the virtual SAN managed by this record. The column “connector identification information” 2703 of the table “system operation management agent configuration management” 2702 described later. Use the value held by.

  The column “virtual SAN property information” 2316 holds virtual SAN attribute information managed by this record, and holds, for example, a tag number assigned to a VSAN data frame. Further, as described above, in addition to a method of holding a plurality of attribute values as one structure data in one column, it is possible to implement the present invention by providing separate columns. The configuration and definition of the table held in the configuration information reservation management database 609 have been described above.

  Hereinafter, the configuration and definition of the table held in the configuration information history management database 610 will be described with reference to FIGS. These tables are similar in definition to the tables held in the configuration information reservation management database 609, and only the differences will be described below.

  The configuration information history management database 610 includes a table “NW logical partition history management” 2402, a table “SAN / storage logical partition history management” 2409, a table “virtual NW routing history management” 2416, a table “virtual SAN routing history management” 2424, A table “virtual server history management” 2502, a table “virtual FW history management” 2509, a table “LU history management” 2515, a table “virtual NW history management” 2601, and a table “virtual SAN history management” 2607.

  The configuration information reservation management database 609 is used for managing reservations of virtual resources. The configuration information history management database 610 is a history of virtual resource states based on actual configuration information collected by system monitoring or the like. It is a database used for recording. Therefore, since the same column can be used for holding the configuration information in each table, in this embodiment, in order to simplify the description, an example using the same type of table will be described below. To do.

  In the configuration information history management database 610, the column “start date / time” of each table of the configuration information reservation management database 609 is replaced with the column “confirmation date / time”, and the column “end date / time” is replaced with the column “valid date / time”. . The column “confirmation date / time” is a column that holds the date / time when the configuration information of the record is acquired by system monitoring. The column “valid date and time” is a column that holds the date and time when the configuration information is updated and the contents of the record become invalid due to the next system monitoring cycle.

  The table “NW logical partition history management” 2402 includes a column “start date and time” 2111 and a column “end date and time” 2112 and a column “confirmation date and time” 2403 and a column “valid date and time” in the table “NW logical partition reservation management” 1204, respectively. "2404" is replaced with the definition.

  The table “SAN / storage logical partition history management” 2409 includes a column “start date / time” 2119 and a column “end date / time” 2120 in the table “SAN / storage logical partition reservation management” 1205, respectively, and a column “confirmation date / time” 2410. The definition is replaced with the column “valid date” 2411.

  The table “virtual NW routing history management” 2416 includes a column “start date and time” 2127 and a column “end date and time” 2128 and a column “confirmation date and time” 2417 and a column “valid date and time” in the table “virtual NW routing reservation management” 2126, respectively. "Definition replaced with 2418.

  The table “virtual SAN routing history management” 2424 includes a column “start date and time” 2135 and a column “end date and time” 2136 in the table “virtual SAN routing reservation management” 2134, respectively, a column “confirmation date and time” 2425, and a column “effective date and time”. “2426”.

  A table “virtual server history management” 2502 includes a column “start date and time” 2202 and a column “end date and time” 2203 in a table “virtual server reservation management” 1403, a column “confirmation date and time” 2503, and a column “effective date and time” 2504, respectively. The definition is replaced with.

  The table “virtual FW history management” 2509 includes a column “start date / time” 2210 and a column “end date / time” 2211 in a table “virtual FW reservation management” 1402, respectively, a column “confirmation date / time” 2510 and a column “valid date / time” 2511. The definition is replaced with.

  The table “LU history management” 2515 replaces the column “start date and time” 2218 and the column “end date and time” 2219 with the column “confirmation date and time” 2515 and the column “valid date and time” 2516 in the table “LU reservation management” 1416, respectively. Definition.

  In the table “virtual NW history management” 2601, in the table “virtual NW reservation management” 1405, the column “start date and time” 2302 and the column “end date and time” 2303, respectively, the column “confirmation date and time” 2602 and the column “valid date and time” 2603 The definition is replaced with.

  In the table “virtual SAN history management” 2607 and the table “virtual SAN reservation management” 1404, the column “start date / time” 2310 and the column “end date / time” 2311 are changed to the column “confirmation date / time” 2608 and the column “valid date / time” 2609, respectively. This is the replaced definition.

  The configuration and definition of the table held by the configuration information history management database 610 has been described above.

  Next, the configuration and definition of the table held in the system operation management agent management database 611 will be described with reference to FIGS.

  The system operation management agent management database 611 includes a table “system operation management agent configuration management” 2702, a table “device operation automatic execution schedule management” 2706, a table “server connector configuration management” 2802, a table “storage connector configuration management” 2809, A table “network connector configuration management” 2902 and a table “SAN connector configuration management” 2910 are included.

  The system operation management agent management database 611 is a table “system operation management agent configuration management” 2702 that holds connection destinations when operations are performed on each physical device from the system operation management server device 103 via the management network 106. A table “automatic operation execution schedule management” 2706 that holds schedule information for automatic execution of operations on each device, and a table that belongs to a connector management table group 2801 that holds specific operation contents to be expanded to each device A “server connector configuration management” 2802, a table “storage connector configuration management” 2809, a table “network connector configuration management” 2902, and a table “SAN connector configuration management” 2910 are held.

  26, the table “system operation management agent configuration management” 2702 includes a column “connector identification number” 2703, a column “connector type” 2704, and a column “agent repository information” 2705.

  A column “connector identification number” 2703 is identification information for specifying this record, and may be a serial number without duplication or a character string without duplication.

  The column “connector type” 2704 may be a number specifying which table in the connector management table group 2801 corresponds to which table, or a character string of a table name. In the present embodiment, for example, this number may be a sequential number that identifies one of the four tables 2802, 2809, 2902, and 2910.

  The column “agent repository information” 2705 is a connection destination for communicating from the system operation management server device 103 via the management WAN 105 to the system operation management agent server device managing the physical resource or device managed by this record. For example, a host name or an IP address may be used.

  The table “schedule management for automatic operation of apparatus operation” 2706 includes a column “execution date and time” 2707, a column “reservation identification number” 2708, a column “status” 2709, and a column “identification information of target system logical partitioning” 2710.

  A column “execution date and time” 2707 is a column that holds the scheduled date and time when the automatic execution platform program 604 executes the contents of this record.

  A column “reservation identification number” 2708 is a column that holds identification information of a reservation in which the apparatus operation targeted by this record is registered. As the reservation identification information, a value held in the column “identification information” 2004 of the table “reservation management” 1202 is used.

  The column “status” 2709 holds one of the values “unapproved”, value “approved”, value “executed”, and the like. Note that the value “unapproved” means that the registration of the virtual resource to be reserved in the configuration information reservation management database 609 has been completed. The value “approved” means that the administrator has approved the operation content to the device obtained from the registration of the virtual resource to be reserved in the configuration information reservation management database 609. The value “executed” means that the operation contents registered in this record are executed and completed by the automatic execution platform program 604.

  Column “Identification information of target system logical partition” 2710 is a column that holds identification information of stem logical partition corresponding to the operation performed in this record.

  The configuration and definition of tables included in the connector management table group 2801 will be described below with reference to FIGS. These tables mainly hold information for translating and deploying instructions (virtual system construction, virtual system deletion, etc.) from the system operation management server apparatus into instructions according to the specifications of the individual apparatuses.

  The table “server connector configuration management” 2802 includes a column “connector identification information” 2803, a column “construction operation” 2804, a column “deletion operation” 2805, a column “setting operation” 2806, a column “inspection operation” 2807, and a column “list operation”. 2808.

  The column “connector identification information” 2803 is identification information for specifying this record, and may be a serial number without duplication or a character string without duplication. In the following table definitions, “connector identification information” has the same definition, and thus the description thereof is omitted.

  The column “construction operation” 2804 is a column that retains the operation content to be executed in the virtual system construction work for the server device managed by this record, and retains the operation content for creating a virtual server, for example.

  In the present embodiment, for the sake of simplicity of explanation, this operation content will be described below as a script program in a text format. Furthermore, this operation content is not a parameter required for the operation, but a script program in which information held in the column “VM property information” 2208 of the table “virtual server reservation management” 1403 is applied as a parameter. Is assumed to be implemented on the device. This assumption is also assumed in the other table “storage connector configuration management” 2809, table “network connector configuration management” 2902, and table “SAN connector configuration management” 2903.

  Note that if the operation content is an executable binary format program, the operation content cannot be read and understood directly by humans.Therefore, a column for holding data representing the operation content in a text format is provided separately. When creating the advance checklist, the operation contents in the text format are acquired. Thereafter, the executable binary format program is handled in the same manner.

  A column “deletion operation” 2805 is a column that holds operation contents to be executed in the virtual system deletion work for the server apparatus managed by this record, and holds operation contents for deleting a virtual server, for example.

  A column “setting operation” 2806 is a column for holding operation contents executed in the virtual system setting operation for the server apparatus managed by this record, and holds operation contents for setting a virtual server, for example.

  A column “inspection operation” 2807 is a column for holding operation contents executed in the virtual system inspection work for the server apparatus managed by this record, and holds, for example, operation contents for inspecting the virtual server.

  Column “list operation” 2808 is a column that holds the operation contents to be executed in the virtual system list work for the server apparatus managed by this record. For example, the operation contents for acquiring a list of virtual servers are held. .

  As described above, the table “server connector management” 2802 is a table for associating work items executed by the system operation management server apparatus 103 with operation contents associated with the apparatus. The table “storage connector configuration management” 2809, the table “network connector configuration management” 2902, the table “SAN connector configuration management” 2910, and the table “server connector configuration management” 2801 are used for the same purpose.

  The table “storage connector configuration management” 2809 includes a column “connector identification information” 2810, a column “construction operation” 2811, a column “delete operation” 2812, a column “setting operation” 2813, a column “inspection operation” 2814, and a column “list operation”. ”2815.

  The column “construction operation” 2811 is a column that holds the contents of the operation to be executed in the virtual system construction work for the storage device managed by this record. This operation content is, for example, a series of operations for creating an LU and setting LUN masking, or a series of operations for making a dynamic allocation volume available to a LUN and setting LUN masking. Such an operation is held as a script program expressed by a command that matches the specifications of the storage device.

A column “deletion operation” 2812 is a column that holds the operation content to be executed in the virtual system deletion operation for the storage apparatus managed by this record.
This operation content is, for example, an operation such as LU deletion or invisibility setting by LUN masking.

The column “setting operation” 2813 is a column that holds the operation content to be executed in the virtual system setting operation for the storage device managed by this record.
This operation content is, for example, an LU configuration setting operation. For example, a setting operation for volume multiplexing.

  The column “inspection operation” 2814 is a column that holds the operation content to be executed in the virtual system inspection operation for the storage device managed by this record.

  A column “list operation” 2815 is a column that holds the operation content to be executed in the virtual system list work for the storage device managed by this record.

  The table “network connector configuration management” 2902 includes a column “connector identification information” 2903, a column “construction operation” 2904, a column “deletion operation” 2905, a column “setting operation” 2919, a column “inspection operation” 2908, and a column “list operation”. 2909, a column “member addition operation” 2906, and a column “member deletion operation” 2907.

  The column “construction operation” 2904 is a column that holds the operation content to be executed in the virtual system construction work for the network switching device managed by this record. This operation content is, for example, an operation for creating a VLAN or an operation for making the VLAN usable.

  A column “deletion operation” 2905 is a column that holds the operation content to be executed at the time of virtual system deletion work for the network switching device managed by this record. This operation content is, for example, an operation for deleting a VLAN or an operation for invalidating a VLAN.

  The column “setting operation” 2919 is a column that holds the operation content to be executed in the virtual system setting operation for the network switch device managed by this record. This operation content is, for example, a VLAN setting operation.

  A column “inspection operation” 2908 is a column that holds operation contents to be executed at the time of virtual system inspection work for the network switch device managed by this record. This operation content is, for example, setting information acquisition operation.

  A column “list operation” 2909 is a column that holds the operation contents to be executed in the virtual system list work for the network switch device managed by this record. This operation content includes an operation for acquiring a list of VLANs.

  A column “member addition operation” 2906 is a column that holds the contents of an operation to be executed when a member is added to the virtual network for the network switch device managed by this record. This operation content is, for example, an operation of adding a member to the VLAN.

  A column “member deletion operation” 2907 is a column that holds the operation content to be executed when a member is added to the virtual network for the storage apparatus managed by this record. This operation content is, for example, an operation for deleting a member from the VLAN.

  The table “SAN connector configuration management” 2910 includes a column “connector identification information” 2911, a column “construction operation” 2912, a column “deletion operation” 2913, a column “setting operation” 2914, a column “inspection operation” 2915, and a column “list operation”. ”2916, a column“ member addition operation ”2917, and a column“ member deletion operation ”2918.

  The column “construction operation” 2912 is a column that holds the operation content executed in the virtual system construction work for the FC switch device managed by this record. This operation content is, for example, an operation for creating a VSAN or LSAN, or an operation for making it available.

  A column “deletion operation” 2913 is a column that holds the operation content to be executed in the virtual system deletion work for the FC switch device managed by this record. This operation content is, for example, an operation for deleting or invalidating a VSAN or LSAN.

  The column “setting operation” 2914 is a column that holds the operation content to be executed in the virtual system setting work for the FC switch device managed by this record. This operation content is, for example, a VSAN or LSAN setting operation.

  The column “inspection operation” 2915 is a column for holding the operation content to be executed in the virtual system inspection work for the FC switch device managed by this record. This operation content is, for example, an operation for acquiring VSAN or LSAN configuration information.

  The column “list operation” 2916 is a column that holds the operation content to be executed in the virtual system list work for the FC switch device managed by this record. This operation content is, for example, an operation for acquiring a list of VSAN and LSAN.

  The column “member addition operation” 2917 is a column that holds the operation content executed in the virtual system construction work for the FC switch device managed by this record. This operation content is, for example, an operation of adding a member to VSAN or LASN.

  The column “member deletion operation” 2918 is a column that holds the operation content executed in the virtual system construction work for the FC switch device managed by this record. This operation content is, for example, an operation for deleting a member from VSAN or LSAN.

  The configuration and definition of various tables held in the configuration information reservation management database 609, the configuration information history management database 610, and the system operation management agent management database 661 of the present embodiment have been described above.

  Hereinafter, as shown in FIG. 6, a virtual system construction program 601, a configuration information reservation management database operation program 602, a pre-checklist creation program 603, an automatic execution platform program 604, which are held in the memory 502 of the system operation management server device 103, Operations of the system monitoring program 605, the system inspection program 606, one or more virtual system construction templates 607, and the DBMS program 608 will be described with reference to FIGS.

  36, the system operation management agent program 801, the server connector program 802, the storage connector 803, the network connector program 804, and the SAN connector program 805 stored in the memory 702 of the system operation management agent server device 104 will be described. .

  29, the operation of the virtual system construction program 601 and the virtual system construction template 607 that operates in conjunction therewith will be described. First, in the operation block 3001, a new reservation record is created in the table “reservation management”. At this time, values are input to the column “start date / time” 2002, the column “end date / time” 2003, the column “identification information” 2004, and the column “customer identification information” 2005. Since the column “reservation target group identification information” 2006 has not yet been created at this time, a default value (for example, −1) corresponding to indefinite is input. In the following description, it is assumed that a default value is similarly input to a column whose value is not determined. Next, the operation of the operation block 3002 is performed.

  In operation block 3002, the virtual system construction template selected by the operator is called from one or more virtual system construction templates 607. In the present embodiment, a description will be made on the premise that the virtual system construction template is not structured data representing the system configuration, but is stored as a crypto program in the configuration information reservation management database 609. The embodiment of the present invention is a procedure for storing a virtual system construction template as structure data representing a system configuration and registering the configuration information in the configuration information reservation management database 609 based on the structure data. However, there is no problem. Next, the operation of the operation block 3003 of the selected virtual system construction template 607 is performed.

  According to the operation of the virtual system construction template 607, first, the virtual resources are reserved, and then the configuration information of the virtual system is obtained through a two-step operation of registering the connection relations based on the reserved virtual resources. Register in the configuration information reservation management database 609. In the following description, the operation of registering each record described with reference to FIGS. 12 to 15 is taken as an example.

  In the operation block 3003, the table “virtual server reservation management” is executed under the condition that the value of the column “reservation identification information” 2204 is not reserved during the period of the start date and time and the end date and time input to the reservation record. Search 1403 and search for unreserved virtual servers. This search is performed via the DBMS program 608. Next, the operation of the operation block 3004 is performed.

  In operation block 3004, the number of virtual servers designated by the operator is selected from the unreserved virtual servers obtained in the operation block. This selection may be an unattended method based on the order of search results and a method for selecting a specified number of devices, or a method for displaying and selecting a list of unreserved virtual servers to the operator. The reservation of one or more selected virtual servers is registered in the table “virtual server reservation management” 1403. This reserved virtual server corresponds to the virtual server 904 and the virtual server 905.

  In this embodiment, as shown in FIG. 17, this reservation does not simply add one record for the reservation period, but replaces the retrieved records indicating unreserved records before and after the reservation period. The basic procedure is to divide and add records for the reservation period. Hereinafter, the reservation procedure in the configuration information reservation management database 609 is the same, and the description is omitted. Next, the operation of the operation block 3005 is performed.

  In the operation block 3005, in the condition that the value of the column “reservation identification information” 2212 is unreserved in the period of the start date and time and the end date and time input to the reservation record of the table “virtual FW reservation management” 1402, The table “virtual FW reservation management” 1402 is searched, and an unreserved virtual firewall (virtual FW) is searched. This search is performed via the DBMS program 608. Next, the operation of the operation block 3006 is performed.

  In operation block 3006, one unit is selected from the unreserved virtual FW obtained in the operation block. This selection may be an unattended method based on the order of search results, or a method of selecting one server and a method of displaying and selecting a list of unreserved virtual servers to the operator. The reservation of the selected virtual FW is registered in the table “virtual FW reservation management” 1402. Next, the operation of the operation block 3007 is performed.

  In the operation block 3007, in the condition that the value of the column “reservation identification information” 2304 is unreserved in the period of the start date and time and the end date and time input to the reservation record of the table “virtual NW reservation management” 1405, The table “virtual NW reservation management” 1405 is searched to search for unreserved virtual networks. Next, the operation of the operation block 3008 is performed.

  In operation block 3008, two are selected from the unreserved virtual networks obtained in the operation block. This selection may be an unattended method based on the order of search results, or a method of selecting two, or a method of displaying and selecting a list of unreserved virtual servers to the operator. The reservation of the selected virtual network is registered in the table “virtual NW reservation management” 1405. These two virtual networks correspond to the virtual network A 901 and the virtual network B 903. Next, the operation of the operation block 3009 is performed.

  In the operation block 3009, in the condition that the value of the column “reservation identification information” 2312 is unreserved in the period of the start date and time and the end date and time input to the reservation record of the table “virtual SAN reservation management” 1404, The table “virtual SAN reservation management” 1404 is searched to search for an unreserved virtual SAN. Next, the operation of the operation block 3010 is performed.

  In operation block 3010, one is selected from the unreserved virtual SANs obtained in the operation block. This selection may be a method of selecting one unattended based on the order of search results, or a method of displaying a list of unreserved virtual servers to the operator and selecting one. The reservation of the selected virtual SAN is registered in the table “virtual SAN reservation management” 1404. Next, the operation of the operation block 3011 is performed.

  Under the condition that the value of the column “reservation identification information” 2220 is unreserved during the start date / time and end date / time input to the above-mentioned reservation record of the table “LU reservation management” 1416 in the operation block 3011 “LU reservation management” 1416 is searched to search for unreserved LUs. Next, the operation of the operation block 3012 is performed.

  In the operation block 3012, the required number is selected from the unreserved LUs obtained in the operation block. This selection may be a method of obtaining the required number from the operator and selecting it unattended based on the order of search results, or a method of displaying a list of unreserved virtual servers to the operator and selecting the required number. The reservation of the selected LU is registered in the table “LU reservation management” 1416. This reserved LU corresponds to LU907 and LU908. Next, the operation of the operation block 3013 is performed. Next, the operation of the operation block 3013 is performed.

  The virtual resource reservation is completed as described above, and the connection relations are registered in subsequent operation blocks 3013, 3014, and 3015.

  In operation block 3013, NW logical partitioning is registered. Since this template has two virtual network A 901 and virtual network B 903, records corresponding to NW logical partition A 909 and NW logical partition B 910 are registered for each member in table “NW logical partition reservation management” 1204. To do. Note that there are two members of the NW logical partition A909, the virtual network A901 and the virtual FW. The members of the NW logical partition B 910 are a virtual network B 903, a virtual server 904, a virtual server 905, and the like. Next, the operation of the operation block 3014 is performed.

  In the operation block 3014, one SAN / storage logical partition 911 is registered. A record is registered for each member in the table “SAN / storage logical partition reservation management” 1205. Members of the SAN / storage logical partition 911 are virtual servers 904 and 905 and LUs 907 and 908. Next, the operation of the operation block 3015 is performed.

  In operation block 3015, registration of the system level logical partition 912 is registered in the table “system level logical partition reservation management” 1203. The members of the system level logical partition 912 are the aforementioned NW logical partition A 909, NW logical partition B 910, SAN / storage logical partition 911, virtual FW 902, and virtual servers 904 and 905. Next, returning from the operation of the template, the operation is performed to the operation block 3016.

  In operation block 3016, the value of the column “reservation target group identification information” that has not been confirmed in operation block 3001 is updated to the identification information of the system level logical partitioning 912 registered above. Next, the operation of the operation block 3017 is executed. As described above, the registration of the configuration information of the virtual system shown in FIG. 9 in the configuration information reservation management database 609 is completed.

  In the operation block 3016, the reservation record in which the column “status” 2709 is “unapproved” is registered in the table “device operation automatic execution schedule management” 2706, and the process returns from the operation of the virtual system construction program 601. The operation of the virtual system construction program 601 has been described above.

The operation of the configuration information reservation management database operation program 602 will be described with reference to FIG.
First, in an operation block 3101, a search condition for selecting an update target is received from the operator.

  Next, the operation of the operation block 3102 is executed. In operation block 3102, the DBMS program 608 is used to search with the received conditional expression, and the search result is displayed. Next, operation block 3103 is executed.

  In operation block 3103, the update content is received from the operator and reflected in the target record using the DBMS program 608. Note that if only the search result is browsed without updating, the process ends without reflecting the target record.

  In this embodiment, the configuration information reservation management database operation program 602 registers a new virtual resource associated with the installation or expansion of a device, and registers the connection relationship between the virtual resource and the physical resource described with reference to FIG. This will be described on the assumption. In addition to manual registration, this registration method may be used by providing a mechanism for automatic registration by a tool program or the like, and there is no problem in implementing the present invention.

  The operation of the advance checklist creation program 603 will be described with reference to FIG. The pre-checklist creation program 603 collects the operation contents for the devices scheduled on the specified date based on the configuration information reserved in the configuration information reservation management database 609, and displays the results of classification / sorting as the operator. Is a program to output to.

  First, in operation block 3201, a designated date to be pre-checked is received from the operator.

  Next, the operation of the operation block 3202 is performed. In the operation block 3202, the DBMS program 608 is used to search for a record in which the value of either the column “start date / time” 2202 or the column “end date / time” 2203 of the table “virtual server reservation management” 1403 is the specified date. The search result is held in the work area 612 of the memory 502. Further, a record including the specified date in the period indicated by the value of the column “end date / time” 2203 to the column “end date / time” 2203 in the table “virtual server reservation management” 1403 (but not including the start date / time) is searched. The search result is held in the work area 612 of the memory 502.

  Next, the operation of the operation block 3203 is performed. In the operation block 3203, the DBMS program 608 is used to search for a record in which the value of either the column “start date / time” 2210 or the column “end date / time” 2211 of the table “virtual FW reservation management” 1402 is the specified date. The search result is held in the work area 612 of the memory 502. Further, a record including the specified date is searched for in the period (not including the start date / time) indicated by the value of the column “end date / time” 2211 from the column “start date / time” 2210 of the table “virtual FW reservation management” 1402. The search result is held in the work area 612 of the memory 502.

  Next, the operation of the operation block 3204 is performed. In the operation block 3204, the DBMS program 608 is used to search for a record in which the value of either the column “start date / time” 2302 or the column “end date / time” 2303 of the table “virtual NW reservation management” 1405 is the specified date. The search result is held in the work area 612 of the memory 502. Further, a record including the specified date in the period indicated by the value of the column “start date and time” 2302 to the column “end date and time” 2303 (not including the start date and time) of the table “virtual NW reservation management” 1405 is searched. The search result is held in the work area 612 of the memory 502.

  Next, the operation of the operation block 3205 is performed. In the operation block 3205, the DBMS program 608 is used to search for a record in which the value of either the column “start date / time” 2310 or the column “end date / time” 2311 of the table “virtual SAN reservation management” 1404 is the specified date. The search result is held in the work area 612 of the memory 502. Further, a record including the specified date in the period (however, the start date / time is not included) indicated by the value of the column “start date / time” 2310 to the column “end date / time” 2311 of the table “virtual SAN reservation management” 1404 is searched. The search result is held in the work area 612 of the memory 502.

  Next, the operation of the operation block 3206 is performed. In the operation block 3206, the DBMS program 608 is used to search for a record in which the value of either the column “start date / time” 2218 or the column “end date / time” 2219 of the table “LU reservation management” 1416 is the specified date. The search result is held in the work area 612 of the memory 502. Further, the table “LU reservation management” 1416 is searched for a code that includes the specified date in the period (not including the start date and time) indicated by the value of the column “start date and time” 2219 from the column “start date and time” 2219, The search result is held in the work area 612 of the memory 502.

  Next, the operation of the operation block 3207 is performed. In the operation block 3207, among the records of the search results held in the work area 612 of the memory 502, for each record whose start date and time is the same as the specified date, for each of the connector identification information held by it, The table “system operation management agent configuration management” 2702 is searched to identify the corresponding connector management table. Here, the specification of the connector management table refers to the table “server connector configuration management” 2802, the table “storage connector configuration management” 2809, the table “network connector configuration management” 2902, the table “SAN connector configuration management” 2910, and the like. It means to specify one of them.

  In the specified connector configuration management table, a record holding the same connector identification information is searched, and the operation content that is the value of the column “construction operation” of the record of the search result is acquired and held in the work area 612.

  Next, the operation of the operation block 3208 is performed. In the operation block 3208, for each record whose end date and time is the same as the specified date among the search result records held in the work area 612 of the memory 502, from each connector identification information held by each The table “system operation management agent configuration management” 2702 is searched to identify the corresponding connector management table.

  Here, the specification of the connector management table refers to the table “server connector configuration management” 2802, the table “storage connector configuration management” 2809, the table “network connector configuration management” 2902, the table “SAN connector configuration management” 2910, and the like. It means to specify one of them. In the specified connector configuration management table, a record holding the same connector identification information is searched, the operation content that is the value of the column “delete operation” of the record of the search result is acquired, and the operation content held in the operation step 3207 At the same time, the work area 612 is held.

  Next, the operation of the operation block 3209 is performed. In an operation block 3209, the work contents held in the work area 612 in the operation blocks 3207 and 3208 are classified, sorted, and tabulated, and the results are displayed or output to the operator as a pre-check list.

  A display example of this pre-check list is shown in FIG. Since the operation content obtained in the operation block 3207 is an operation executed after the operation content obtained in the operation block 3208, the state before the configuration change on the specified date is obtained in the operation block 3208. The operation contents are obtained by classifying, sorting, and summing up, and the state after the configuration change is obtained by classifying, sorting, and summing up the operation contents obtained in the operation block 3207.

  Next, the operation of the operation block 3210 is performed. In operation block 3210, confirmation regarding the pre-check list displayed in operation block 3209 is received from the operator, and the column “state” 2709 of the record of the corresponding reservation in table “device operation automatic execution schedule management” 2706 is received. Is updated to the value “approved”, and the process returns from the pre-check list creation program 603. The advance checklist creation program 603 has been described above.

  Next, the operation of the system inspection program 606 will be described with reference to FIG.

  First, in operation block 3301, a date and time for system inspection is received from the operator. Next, the operation of the operation block 3302 is performed.

  In operation block 3302, a record including the specified date and time is searched between each of the various tables of the configuration information reservation management database 609 between the column “start date and time” and the column “end date and time”. The next operation block 3303 is performed.

  In operation block 3303, a record including the specified date and time is searched between each of the various tables of the configuration information history management database 610 between the column “start date and time” and the column “end date and time”. The next operation block 3304 is operated.

  In the operation block 3304, the search results of the operation block 3302 and the operation block 3303 are combined to detect a difference, displayed or output to the operator, and the system check program 606 returns. The system inspection program 606 has been described above.

  The operation of the system monitoring program 605 will be described with reference to FIG. The system monitoring program 605 may be automatically executed periodically by the operator in addition to being arbitrarily executed. First, the operation of the operation block 3401 is performed.

  In operation block 3401, the current date and time are obtained from the clock. Next, the operation of the operation block 3402 is performed. The clock mentioned here may be a clock function provided by basic software such as an OS in addition to a clock function installed in a general computer.

  In the operation block 3402, the resource state and configuration information at that time are collected by the capture result of the SNMP trap and the operation contents of the column “inspection operation” of the connector configuration management table. Next, the operation of the operation block 3403 is performed.

  In the operation block 3403, the status information and the configuration information collected in the operation block 3402 are reflected in the configuration information history management database 610 and the system monitoring program 605 returns. In addition, regarding the reflection to the configuration information history management database 610, the existing record is not overwritten, but the existing record is updated with the value of the column “valid date” to the check date obtained in the operation block 3401. In the configuration information obtained in the previous operation block 3402, the column “confirmation date / time” is registered as the inspection date / time, and the column “valid date / time” is registered as the default value (eg, maximum value) for the entire day. The system monitoring program 605 has been described above.

  The operation of the automatic execution platform program 604 will be described with reference to FIG. The automatic execution platform program 604 may be executed arbitrarily by the operator in addition to being executed periodically. First, the operation of the operation block 3501 is performed.

  In operation block 3501, the current date and time are obtained from the clock. Next, the operation of the operation block 3502 is performed.

  In the operation block 3502, the value of the column “execution date / time” 2707 in the record of the table “device operation automatic execution schedule management” 2706 is earlier than the date and time acquired in the previous step, and the column “status”. A search is made for a value 2709 that has been approved. Next, the operation of the operation block 3503 is performed.

  In operation block 3503, the operation of each device is executed from the contents of each record of the search result in operation block 3502 via the system operation management agent server. Specifically, based on the value of the column “target system logical partition identification information” 2710 of the retrieved record and the value of the column “execution date and time” 2707, the members of the target system level logical partition (for example, The start date or the end date of the record of the virtual server, virtual FW, LU, virtual network, virtual SAN, NW logical partition, SAN / storage logical partition) is included in the execution date. As a result, the connector management table is specified for the obtained record, each operation content is acquired, and the system “operation management agent configuration management” 2702 is used to specify the system operation management agent server device. Operate the device. Next, the operation of the operation block 3504 is performed.

  In the operation block 3504, among the records in the table “device operation automatic execution schedule management” 2706, those for which device operation has been completed are updated from “approved” to “performed” in the column “state” Return from the automatic execution platform program 604. The automatic execution platform program 604 has been described above.

  The operation of the DBMS program 608 will be described with reference to FIG. In this embodiment, general relational database system software is assumed. First, the operation of the operation block 3701 is performed.

  At operation block 3701, a search request is received. This receipt may be input from another program in addition to input from the operator. Next, the operation of the operation block 3702 is performed.

In operation block 3702, the specified search condition is searched for the specified table in response to the search request. Next, the operation of the operation block 3703 is performed.
In operation block 3703, the search result is returned to the request source, and the process returns from the DBMS program 608.

  In addition to the relational database system software, the object-oriented database system software may be used as the DBMS program to implement the present invention. The DBMS program 608 has been described above.

  Next, in FIG. 36, a system operation management agent program 801 held in the memory 702 of the system operation management agent server device 104, a server connector program 802, a storage connector 803, a network connector program 804, and a SAN operating in conjunction therewith. The operation of the connector program 805 will be described.

  First, when receiving an operation request from the system operation management server device, the system operation management agent server device 104 executes the system operation management agent program 801. The system operation management agent program 801 first performs the operation of the operation block 3601.

  In an operation block 3601, an operation target and an operation request are received from the system operation management server apparatus 103.

  In the operation block 3602, the connector program 802 to be operated is called. Here, a case where the server connector program 802 is called will be described as an example.

  In an operation block 3603, a return from the connector program 802 or the like is awaited.

  In operation block 3604, the operation result of the operation request is notified to the system operation management server apparatus 103 (request source), and the system operation management agent program 801 is returned.

  The server connector program 802 issues an operation instruction to the server device via the management network 106, acquires the operation result, and returns. When the other storage connector program 803, network connector program 804, and SAN connector program 805 are called, the operation may be the same as that of the server connector program 802 except that the target device is different, and an individual description is omitted.

  The operations of the system operation management server device 103 and the system operation management agent server device 104 have been described above. Of the tables held in the table “system operation management agent management database” 611, a connector management table group 2801, for example, a table “server connector configuration management” 2802, a table “storage connector configuration management” 2809, and a table “network connector configuration”. The “management” 2902 and the table “SAN connector configuration management” 2910 may be held in the memory 702 of the system operation management agent server device 104. In this case, the system operation management server device may perform the operation of acquiring the operation content of the device via the management WAN 105, and there is no problem in implementing the present invention.

FIG. 37 shows an output example of the configuration check prior check list.
This is an output example of the advance checklist generated by the advance checklist creation program 603. The pre-check list display 3801 includes a column “creation date” 3802, a column “scheduled date” 3803, a column “physical server” 3804, a column “storage device” 3805, a column “network switch device” 3806, and a column “FC switch device”. 3807.

A column “creation date” 3802 is a column for displaying the date on which this pre-check list was created. A column “scheduled date for implementation” 3803 is a column for displaying a date on which a configuration change is scheduled to be performed. A column “physical server” 3804 is a column for displaying information related to the server device among the operation contents to the device. In this column, the operation contents may be classified and displayed for each server device. A column “storage device” 3805 is a column for displaying information related to the storage device among the operation contents to the device. In this column, the operation contents may be classified and displayed for each storage device. A column “network switch device” 3806 is a column for displaying information related to the network switch device among the operation contents to the device. In this column, the operation contents for each individual network switch device may be further classified and displayed. A column “FC switch device” 3807 is a column for displaying information related to the FC switch device among the operation contents to the device. In this column, the operation contents for each FC switch device may be further classified and displayed.
Next, the operation performed in the operation block 3209 of the pre-check list creation program 603 shown in FIG.

A column “creation date” 3802 is a column for displaying the date on which this pre-check list was created. This date may be the date when the pre-check list creation program 603 is executed, and may be obtained from the general clock function of the system operation management server device 103 on which this program operates. Also, it can be input by the operator.
A column “scheduled date for implementation” 3803 is a column for displaying a date on which a configuration change is scheduled to be performed. This date may be the date acquired from the operator in the operation block 3201.
A column “physical server” 3804 is a column for displaying information related to the server device among the operation contents to the device. In this column, the operation contents may be classified and displayed for each server device.

  First, in the search result in the operation block 3202, the number of records including the specified date and time in the period is the original number of “reserved VMs” described in the column “physical server” in FIG. Then 180 units).

  Of the search results in the action block 3202, the number of records narrowed down in the action block 3208 from the records whose start date and time or end date and time are the same as the specified date and time is the number of virtual servers to be deleted, and is narrowed down in the action block 3207. The number of recorded records will increase the number of virtual servers. Therefore, for example, the number of “reserved VMs” described in the column “Physical Server” in FIG. 37 is changed by subtracting the number of decreasing servers from the original number and adding the number of increasing servers. (For example, 200 in the figure) is displayed. Other display contents can be output in the same manner by quoting or processing the contents of the search result record.

  In the following, display contents can be created in the same manner for the column “storage device” 3805, the column “network switch device” 3806, and the column “FC switch device” 3807, so that the individual description is omitted.

  By creating the above-mentioned pre-check list 3801, it becomes possible to perform a pre-check individually for each device administrator such as a server device, a storage device, a network device, and an FC switch device. Furthermore, by displaying together the number of virtual servers on each server device, the number of reserved LUs in the storage device, and the like, it is possible to confirm in advance the placement of virtual resources. For example, in the present system shown in FIG. 1, in order to save power, it is possible to confirm in advance that the number of virtual servers on one or more server devices is not made uniform, but are shifted to each other.

101: Central operation management site, 102: Data center site, 103: System operation management server device, 104: System operation management agent server device, 105: Management WAN, 106: Management network, 107: Network switch device, 108: Server device 109: FC switch device 110: Storage device 111: Internet / WAN 112: Core network 113-124: Data path

Claims (8)

One or more computers that can be configured with virtual machines;
One or more storage devices capable of setting virtual storage; and
A Fiber Channel switch device capable of setting a virtual SAN by connecting the computer and the storage;
A management computer connected to the computer, the storage device and the fiber channel switch via a network capable of setting a virtual network;
The management computer is
Having at least one arithmetic unit and a storage unit;
Managing the virtual machine, the virtual network, the storage and the virtual SAN as virtual resources;
Managing the computer, the network, the storage device and the Fiber Channel switch device as physical resources;
The storage unit of the management computer is
First configuration management information having attribute information of the virtual resource, configuration information holding a correspondence relationship between the virtual resource and the physical resource, and management information of a reservation time of the virtual resource;
Holds the attribute information of the physical resource, the operation content to be expanded to the physical resource and the second configuration management information that holds the schedule, The management computer,
Search the first configuration management information, determine whether there is a reservation time of the virtual resource included in the specified time,
If there is a reservation time of the virtual resource included in the specified time, specify the physical resource corresponding to the virtual resource,
Search the second configuration management information, obtain the operation content of the specified physical resource at the specified time,
The acquired operation content is output. The management computer is
The system according to claim 1, wherein the acquired operation content is classified and output for each of the server device, the network, the storage device, and the Fiber Channel switch device. The management computer is
Output the acquired operation content as a checklist,
2. The server device, the network, the storage device, and the Fiber Channel switch device are caused to execute an operation according to the output checklist when the specified time is reached. The described system. Monitoring the status and configuration of the physical resource and the status and configuration of the virtual resource arranged in the physical resource, and having third configuration management information for holding the obtained configuration information in time series,
The management computer is
A list of virtual resources and physical resources for which a difference is determined by comparing the configuration information held by the first configuration management information and the third configuration management information by including the specified past date and time in the search condition The system according to claim 1, wherein: One or more computers capable of setting virtual computers, one or more storage devices capable of setting virtual storage, a fiber channel switch device capable of setting a virtual SAN by connecting the computers and the storage, and virtual A system operation management method in a system comprising a management computer connected to the computer, the storage device and the Fiber Channel switch via a network capable of setting a network,
The management computer is
At least one computing device;
First configuration management information having attribute information of the virtual resource, configuration information holding a correspondence relationship between the virtual resource and the physical resource, and management information of a reservation time of the virtual resource, and the physical resource Storage unit for holding the attribute information, the operation contents to be expanded on the physical resource, and the second configuration management information for holding the schedule,
Managing the virtual machine, the virtual network, the storage and the virtual SAN as virtual resources;
Managing the computer, the network, the storage device and the Fiber Channel switch device as physical resources;
Search the first configuration management information, determine whether there is a reservation time of the virtual resource included in the specified time,
If there is a reservation time of the virtual resource included in the specified time, specify the physical resource corresponding to the virtual resource,
Search the second configuration management information, obtain the operation content of the specified physical resource at the specified time,
The system operation management method characterized by outputting the acquired operation content. The management computer is
6. The system operation management method according to claim 5, wherein the acquired operation content is classified and output for each of the server device, the network, the storage device, and the Fiber Channel switch device. The management computer is
Output the acquired operation content as a checklist,
6. The server device, the network, the storage device, and the Fiber Channel switch device are caused to execute an operation according to the output checklist when the designated time is reached. The system operation management method described. Monitoring the status and configuration of the physical resource and the status and configuration of the virtual resource arranged in the physical resource, and having third configuration management information for holding the obtained configuration information in time series,
The management computer is
A list of virtual resources and physical resources for which a difference is determined by comparing the configuration information held by the first configuration management information and the third configuration management information by including the specified past date and time in the search condition The system operation management method according to claim 5, wherein:

Images