JP2014146352A - Computer system and management method therefor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable a server administrator to configure a computer system and change configuration of the computer system by himself/herself.SOLUTION: An administrative server acquires communication destination interface identifiers set for respective external devices to store the interface identifiers in a first table, acquires specifications of respective server computers and identifiers of the respective server computers to store the specifications and the identifiers in a second table, acquires specifications of the respective external devices to store the specifications in the first table, in response to reception of a profile to be deployed in a server computer, acquires the server computer satisfying the profile from the second table, acquires the external device satisfying the profile from the first table to acquire the interface identifier of a connection destination from the first table, and notifies the server computer acquired from the second table of the acquired interface identifier. The server computer updates an interface identifier of an interface by the received interface identifier.

Description

  The present invention relates to a computer system, and more particularly to a configuration management method for managing connection between a server, a network, and a storage.

  The computer system is configured by physically connecting a server, a network, and a storage. However, in order to operate the computer system flexibly, it is desirable that the connection between the server, the network, and the storage can be flexibly changed.

  As conventional techniques for realizing this, there are a technique for constructing a virtual network group (for example, MAC-based VLAN) in a network and a technique for constructing a logical disk from a disk array provided in a storage device (for example, Patent Document 1). By using these technologies, the connection relationship between the server, the network, and the storage can be flexibly changed.

JP 2003-15915 A

  However, even when using the above conventional method, when building and changing the configuration of a computer system, the server administrator notifies the network administrator and storage administrator of the network and storage requirements to be connected, and conforms to the requirements. It was necessary to perform network and storage configuration work. For this reason, a great amount of man-hours and time have been required to construct and change the configuration of the computer system.

  The above becomes a serious problem when it is desired to quickly construct an execution environment for an OS or an application, such as a rapid load increase for a business operating on a computer system. That is, in a data center or the like, when the server administrator changes the server configuration, the server administrator requests the network administrator to change the network configuration (for example, routing), and the server administrator configures the storage configuration. It is necessary for the server administrator to wait for a change of (for example, path) to the storage administrator until each administrator completes the change according to the request of the server administrator. For this reason, there has been a problem that it is difficult for the server administrator to quickly change the configuration of the server.

  The problem to be solved by the present invention is that the server administrator manages the connection between the server, the network and the storage related to the construction and configuration change of the computer system, so that the construction and configuration change of the computer system can be performed only by the server administrator. It is possible.

  The present invention is a management method for a computer system comprising a server, a management server for managing the server, and one or more storage devices, wherein the one or more storage devices have one or more logical units. And managing one or more identifiers permitted to access the one or more logical units from the set interface when the interface is set, and the management server has a capacity of the one or more logical units. Storage pool information for managing the one or more identifiers and information indicating whether or not the one or more identifiers are in use by the server, and the management method includes: Receiving a request for the capacity of a logical unit accessed from a virtual server generated on the server, and the storage pool information by the management server. The first logical unit satisfying the capacity requirement is selected from the one or more logical units, and the management server sets the interface to be set based on the storage pool information. Obtaining a first identifier that is permitted to be accessed from the interface to the first logical unit and not being used by the server; and generating the virtual server by the management server and generating the virtual A step of transmitting to the server a request to set the acquired first identifier in an interface of the server; a step of generating the virtual server having the first interface by the server; And setting the identifier of the first interface to the first identifier. That.

  According to the present invention, in constructing and changing the configuration of a computer system, the intervention of an administrator (for example, a storage administrator) or a management device (for example, a storage management server) of an external device connected to the server computer is not required. Man-hours and time for system construction and configuration change can be reduced.

It is a block diagram which shows the structure of the computer system of the 1st Embodiment of this invention. It is a block diagram which shows 1st Embodiment and shows the structure of a server. It is a block diagram which shows 1st Embodiment and shows the structure of a network. 1 is a block diagram illustrating a configuration of a storage apparatus according to a first embodiment. It is explanatory drawing which shows 1st Embodiment and shows the structure of an identifier pool table. It is explanatory drawing which shows 1st Embodiment and shows the structure of a server pool table. It is explanatory drawing which shows 1st Embodiment and shows the structure of a network pool table. It is explanatory drawing which shows 1st Embodiment and shows the structure of a storage pool table. It is explanatory drawing which shows 3rd Embodiment and shows the structure of a group table. It is a flowchart which shows 1st Embodiment and shows an example of the process performed by the acquisition part. It is a screen image which shows a 1st embodiment and shows an example of GUI which inputs a profile. It is explanatory drawing which shows 1st Embodiment and shows the structure of a profile database. It is a flowchart which shows 1st Embodiment and shows an example of the process performed in a definition part. It is a screen image which shows 1st Embodiment and shows an example of GUI which arrange | positions a profile. It is a flowchart which shows 1st Embodiment and shows an example of the process performed in a deployment part. It is a screen image which shows a 1st embodiment and shows an example of GUI which selects a storage candidate. It is a flowchart which shows 1st Embodiment and shows an example of the process performed in the determination part. 18 is a flowchart illustrating an example of network pool candidate search processing performed in step 2401 of FIG. 17 according to the first embodiment. 18 is a flowchart illustrating an example of a storage pool candidate search process performed in step 2411 in FIG. 17 according to the first embodiment. It is a flowchart which shows 1st Embodiment and shows an example of the process performed in the application part. It is a flowchart which shows 1st Embodiment and shows an example of the process performed in the cancellation | release part. It is a flowchart which shows 2nd Embodiment and shows an example of the network pool candidate search process performed by step 2401 of FIG. 18 is a flowchart illustrating an example of a storage pool candidate search process performed in step 2411 of FIG. 17 according to the second embodiment. 18 is a flowchart illustrating an example of network pool candidate search processing performed in Step 2401 of FIG. 17 according to the third embodiment. 18 is a flowchart illustrating an example of storage pool candidate search processing performed in step 2411 of FIG. 17 according to the third embodiment. It is a screen image which shows a 4th embodiment and shows an example of GUI which sets a shared storage. It is a flowchart which shows 4th Embodiment and shows an example of the process performed in a definition part. 18 is a flowchart illustrating an example of a storage pool candidate search process performed in step 2411 of FIG. 17 according to the fourth embodiment. It is a block diagram which shows 5th Embodiment and shows the structure of a server. It is a flowchart which shows 5th Embodiment and shows an example of the process performed in the application part. It is a block diagram which shows 6th Embodiment and shows the structure of a server.

  Hereinafter, an embodiment of the present invention will be described with reference to the accompanying drawings.

  FIG. 1 shows the configuration of the computer system of the first embodiment. The computer system of this embodiment includes a management server 10, an input device 15, an output device 16, a management network 51, one or more servers 60, one or more networks 70, one or more storage devices 80, a server 60, and storage. It has a SAN (Storage Area Network) 71 to which the device 80 is connected. In addition, the storage apparatus 80 includes one or more LU (Logical Unit) 90. Here, the LU 90 is a logical disk. The management server 10 holds the configuration management program 20, the table group 30, and the profile DB 40 in the memory 11. The communication path of the network 70 is managed by the network management server 170. Access paths of the SAN 71 and the storage device 80 are managed by the storage management server 180.

  The management server 10 includes a NIC 13 (Network Interface Card) connected to the management network 51 and is connected to each server 60 via the management network 51.

  In the present embodiment, the configuration management program 20 is described as a program executed by the CPU (or processor) 12. However, the configuration management program 20 may be implemented by hardware or firmware installed in the management server 10 or a combination thereof. . The configuration management program 20 is stored in the LU 90 as a storage medium, and is loaded into the memory 11 at the time of execution and then executed by the CPU 12.

  The management server 10 has an auxiliary storage device such as a hard disk or a flash memory inside, or is connected to an external storage device system via the I / O interface 14 to assist the table group 30 and the profile DB 40. You may hold | maintain in a memory | storage device or a memory | storage device system.

  The input device 15 is a mouse or a keyboard, and the output device 16 is a display device such as a display. Information is used for input / output between the management server 10 and a user (or a server administrator).

  The network 70 indicates one or more network devices and a network system configured by connecting them to each other. The network devices are specifically network switches, routers, load balancers, firewalls, and the like.

  The storage device 80 indicates a storage device system such as one or more RAID (Redundant Arrays of Inexpensive Disks) systems.

  The configuration management program 20 includes an acquisition unit 21 that acquires configuration information and the like of the server 60, the network 70, and the storage device 80, a definition unit 22 that defines a profile that is a requirement definition of the server 60, the network 70, and the storage device 80, and a profile. The deployment unit 23 deployed in the server 60, the determination unit 24 that determines the connection configuration between the network 70 and the storage device 80 from the profile, the application unit 25 that applies the determined connection configuration between the network 70 and the storage device 80, and the server 60 and the network 70. And a release unit 26 for releasing the connection configuration of the storage apparatus 80.

  The table group 30 includes an identifier pool table 31 that holds a list of interface identifiers of the network 70 and the storage device 80 that are pre-pooled, a server pool table 32 that holds a list of pooled servers 60, and a pooled network 70. The network pool table 33 holds a list, and the storage pool table 34 holds a list of pooled storage devices 80. The profile DB holds a list of defined profiles. The profile is specification information or software information for defining the execution environment of the OS or application.

  FIG. 2 shows the configuration of the server 60. The server 60 includes a memory 611, a CPU 612, a management NIC (Network Interface Card) 614, one or more HBAs (Host Bus Adapter) 615, and one or more NICs 616. The server 60 may include an auxiliary storage device such as a hard disk or a flash memory. The management NIC 614 is connected to the management network 51. The HBA 615 is connected to the storage device 80 via the SAN 71. The NIC 616 is connected to the network 70. A plurality of HBAs and NICs may be mounted. The memory 611 holds an identifier rewriting program. In this embodiment, the identifier rewriting program is described as a program executed by the CPU 612. However, the identifier rewriting program may be implemented by hardware or firmware installed in the server 60, or a combination thereof. Note that the HBA 615 and the NIC 616 function as an I / O interface for the server 60 to communicate with an external device or device (network 70 or storage device 80). The I / O interface of the server 60 includes an HBA 615 and a NIC 616 as a first interface whose communication path with an external device is determined by an interface identifier, and communicates with the input device 15 and the output device 16 through a fixed communication path. The I / O interface 14 of FIG. 1 is included as a second interface for performing the above. In the following description, the generic name of the first interface HBA 615 and NIC 616 is simply referred to as an I / O interface. In addition, although the example of HBA615 and NIC616 was shown as a 1st interface, what is necessary is just an I / O interface in which a communication path and a connection destination apparatus (or apparatus) are decided by an interface identifier.

  The identifier rewriting program 620 rewrites the network interface identifier of the NIC 616 and the storage interface identifier of the HBA 615 according to an instruction from the configuration management program 20. Here, the network interface identifier is specifically a MAC address. Specifically, the storage interface identifier is a WWN (World Wide Name). However, when the connection between the server 60 and the storage device 80 uses an IP-SAN such as iSCSI, the storage interface identifier may be an iSCSI name.

  Activation or deactivation of each server 60 is controlled by a command from the management server 10. The server 60 is started upon receiving a start command (for example, Wake on LAN) from the management server 10. The server 60 loads the identifier rewriting program 620 into the memory 611 at the time of activation, and is executed by the CPU 612. The identifier rewriting program 620 can be stored in the ROM (not shown) of the server 60 or can be downloaded from the management server 10.

  In the server 60 that has been activated, an identifier unique to the NIC 616 is set as the interface identifier of the NIC 616. In addition, in the server 60 that has been activated, an identifier unique to the HBA 615 is set as the interface identifier of the NBA 616. The server 60 that has been started up executes the identifier rewriting program 620 and waits for an identifier change command from the management server 10.

  FIG. 3 shows the configuration of the network 70. The network 70 includes a network device 701, and the network device 701 includes a virtual network management unit 702. The virtual network management unit 702 manages the configuration of the virtual network. Here, the virtual network is specifically a VLAN (Virtual Local Area Network), and in this embodiment, a MAC-based VLAN is particularly shown. FIG. 3 shows an example in which the virtual network VLAN1 (721), VLAN2 (722), and VLAN3 (723) are configured by the server 60 connected to the network device 701 and another network.

  The virtual network management unit 702 has a communication path set in advance by the network management server 170 in FIG. 1, and holds a VLAN identifier corresponding to the MAC address. Therefore, the identifier rewriting program 620 can select the communication path of the desired VLAN identifier by changing the MAC address of the NIC 616 according to the command of the management server 10, and the connection destination network 70 or server 60 according to the use of the server 60 can be selected. Etc. can be selected.

  FIG. 4 shows the configuration of the storage apparatus 80. The storage device 80 includes an LU mapping management unit 802 and one or more LUs 90. In FIG. 4, as an example of the LU 90, the storage apparatus 80 includes LU1 (901), LU2 (902), and LU3 (903). The LU mapping management unit 802 manages the mapping between the LU 90 and the storage interface identifier. By mapping the LU 90 and the storage interface identifier, the corresponding LU 90 can be accessed only from the HBA holding the corresponding storage interface identifier. FIG. 4 shows an example in which WWN1 (811) and LU1 (901) are mapped by mapping 821. Note that a plurality of WWNs can be mapped as shown in the mapping 822. Similarly, a plurality of LU 90 can be mapped.

  The LU mapping management unit 802 has an access path set in advance by the storage management server 180 of FIG. 1, and holds an access path (path from the HBA 615 to the LU 90) according to the WWN. Therefore, when the identifier rewriting program 620 changes the WWN of the HBA 615 of the server 60 according to the command of the management server 10, a desired LU 90 to be accessed by the server 60 can be selected, and the LU 90 corresponding to the use of the server 60 is connected. be able to.

  FIG. 5 shows an example of the identifier pool table 31. The identifier pool table 31 holds a list of interface identifiers of the network 70 and the storage device 80 pooled in advance. That is, the identifier pool table 31 stores an interface identifier set as a connection destination between the network 70 (network device 701) as a device external to the server 60 and the storage device 80. The interface identifier is specifically a MAC address held by the NIC 616 of the server 60 or a WWN held by the HBA 615. A column 311 indicates the classification of the interface identifier. That is, the type of I / O interface provided in the server 60 is stored in the column 311. A column 312 indicates an interface identifier. Specifically, the column 311 is “network” if the interface identifier in the column 312 is a MAC address, and “storage” if the interface identifier is WWN. A column 313 indicates whether the interface identifier in the column 312 is in use or unused (pool state).

  FIG. 6 shows an example of the server pool table 32. A column 321 is an identifier for identifying the server 60. Specifically, it is a UUID (Universally Unique Identifier) or serial number, or a blade chassis or mounting slot number for a blade server, or a name defined by a user (or server administrator). A column 322 indicates whether the server 60 in the column 321 is in use or in a pool (unused) state. A column 323 indicates specification information of the server 60 in the column 321. Specifically, the architecture, type, operating frequency, number of cores, installed memory capacity, installed NIC type and number, and installed HBA type and number of installed CPU. In the figure, the specification of “Server 1” in column 321 is that the CPU type is “Xeon”, the operating frequency is “3.0 GHz”, the number of cores is “2”, the installed memory capacity is “4 GB”, and NIC. It shows that one HBA is installed. A column 325 stores user group identifiers.

  As described above, the server pool table 32 stores information on the resources (calculation capacity or storage capacity) of the server 60 that is managed by the management server 10.

  FIG. 7 shows an example of the network pool table 33. A column 331 indicates a network interface identifier. Specifically, it is a MAC address. A column 332 indicates whether the network interface identifier in the column 331 is in use or in a pool (unused) state. A column 333 indicates the network 70 to which the network interface identifier of the column 331 belongs. Specifically, it is information for identifying a network device such as a network switch. A column 334 indicates a virtual network to which the network interface identifier of the column 331 is connected. A column 335 stores an identifier of a group of users who use the server 60.

  FIG. 8 shows an example of the storage pool table 34. A column 341 indicates a storage interface identifier. Specifically, it is WWN. A column 342 indicates whether the storage interface identifier in the column 341 is in use or in a pool (unused) state. A column 343 indicates a storage to which the storage interface identifier of the column 341 belongs. Specifically, it is information for identifying the storage apparatus 80. A column 344 shows the identifier of the LU mapped with the storage interface identifier of the column 341. A column 345 indicates the capacity of the LU indicated in the column 344. A column 346 shows attribute information of the storage interface identifier in the column 341. The attribute information specifically indicates restrictions and functions related to the use of the storage device 80. For example, it is suitable for use in a specific OS such as Windows (registered trademark) or Linux (registered trademark) (in the figure, “for Windows” or “for Linux”), or suitable for operations such as HA (high availability) cluster. Case ("cluster" in the figure). The column 347 stores information indicating whether or not the corresponding LU 90 can be shared. In FIG. 8, “○” is described when the LU 90 is sharable. A column 335 stores identifiers of user groups.

  The user (or server administrator) selects a storage interface identifier (WWN) from the storage pool table 34 according to the type and data of the OS to be executed by the server 60, and the configuration management program 20 sets the interface identifier of the HBA 615. By changing, it is possible to connect to a desired LU 90 and execute a desired OS on an arbitrary server 60.

  Below, an example of operation | movement of the configuration management program 20 in the management server 10 of this embodiment is shown.

  FIG. 10 shows a flowchart of processing performed by the acquisition unit 21 of the configuration management program 20. The acquisition unit 21 is executed in a predetermined cycle or according to an instruction from the administrator, and acquires configuration information of the computer system (step 211). The configuration information acquired here is information for creating and updating the server pool table 32, the network pool table 33, and the storage pool table 34. Information acquisition methods include, for example, a device that holds configuration information of the server 60 (not shown), a virtual network management unit 702 of a network device, a device that holds configuration information of the network 70 (network management server 170), and a storage device 80. LU mapping management unit 802, a device that holds configuration information of the storage device 80 (storage management server 180), software that manages the configuration information of the computer system, etc. For example, a method using CLI (Command Line Interface), a user input, a file acquisition, and the like.

  In particular, since the network 70 and the storage device 80 cannot be directly accessed from the management server 10, when the network management server 170 or the storage management server 180 is connected to the management network 51, the network from these management servers 70 configuration information and storage device 80 configuration information may be acquired. On the other hand, when the management server 10 cannot access the network management server 170 or the storage management server 180, the configuration information from each management server is stored in a file, and when the management server 10 reads the file, the configuration information of the network 70, The configuration information of the storage device 80 is acquired. Since each server 60 can be directly accessed from the management server 10 via the management network 51, the management server 10 may be a device that holds the configuration information of the server 60 described above.

  Next, of the acquired information, information that does not exist in the list of interface identifiers of the network 70 and the storage device 80 held in the identifier pool table 31 is filtered (step 212). That is, by this filtering, only the devices or devices to be managed by the configuration management program 20 of the management server 10 are extracted from the plurality of networks 70 and the plurality of storage devices 80 in the computer system. Then, the server pool table 32, the network pool table 33, and the storage pool table 34 are created and updated using the filtered information (step 213).

  Next, connection confirmation is performed for the network 70 and the storage device 80 held in the network pool table 33 and the storage pool table 34 (step 214). Since the management server 10 cannot directly access the network 70 and the storage device 80, the management server 10 requests the server 60 to confirm the connection. The connection confirmation of the network 70 is a process of confirming the reachable range of the network 70 by sending and receiving a packet such as ping to a specific VLAN, for example. The connection confirmation of the storage apparatus 80 is a process of accessing the LU 90 of the storage apparatus 80 and confirming the capacity of the corresponding LU 90 and the presence of retained data, for example. If data is stored in the LU 90, the user can select whether to automatically delete the data in this step (step 214) (perform processing such as formatting) or leave the data untouched. And

  Through the above processing, the acquisition unit 21 of the configuration management program 20 updates the server pool table 32, the network pool table 33, and the storage pool table 34.

  FIG. 11 shows an example of a GUI (Graphical User Interface) as an example of a UI (User Interface) that the configuration management program 20 provides to a user to input a profile or update a profile. This GUI is displayed on the output device 16 connected to the management server 10 or the display device of another terminal connected to the management server 10 via the management network 51 using a browser, a dedicated program, text, or the like. .

  The user (or server administrator) sets the requirements (profile) of the server 60 necessary for the computer system from this UI.

  A window 1601 indicates a browser or program window. A window 1601 displays profile information, buttons for operation, and the like. The user inputs a profile name in a profile name input box 1602. In the OS selection frame 1603, the type of OS to be operated is selected. In the example of FIG. 11, selection by pull-down is possible. In the CPU input frame 1604, the CPU type, operating frequency, and number of cores are input. In the memory input frame 1605, the memory capacity is input. In the network input frame 1606, a virtual network to be connected is input. By clicking the add network button 1607, the number of connected networks 70 can be increased, and the number of lines in the network input frame 1606 is increased. In the storage input frame 1608, the capacity of the storage device 80 to be connected is input. By clicking the add button 1610 of the storage device 80, the number of storage devices 80 to be connected can be increased, and the number of rows in the storage input frame 1608 is increased. When profile input and update are completed, a profile definition button 1611 is clicked, and when canceling, a cancel button 1612 is clicked.

  The profile of the server 60 set by the UI is stored in the profile DB 40 of the management server 10.

  FIG. 12 shows an example of information (profile) held in the profile DB 40. A column 401 holds the name of the profile. The column 402 holds the OS type of the corresponding profile (profile indicated by the column 401). Specifically, the OS name and version information. A column 403 shows specification information. Specifically, the CPU type, operating frequency, number of cores, memory capacity, connection destination virtual network, and connection destination storage capacity. A column 404 indicates an identifier of the server 60 where the corresponding profile is deployed. When the profile is not deployed (operated) in the server 60, “undeployed” is described. Columns 405 and 406 are information held only when the corresponding profile is deployed in the server 60. A column 405 indicates the determined network interface identifier. A column 406 shows the determined storage interface identifier. Specifically, the interface identifiers (MAC address and WWN) shown in the columns 405 and 406 are applied as the MAC address of the NIC 616 and the WWN of the HBA 615 installed in the server 60 shown in the column 404, respectively.

  FIG. 13 shows a flowchart of an example of processing performed by the definition unit 22 of the configuration management program 20. The definition unit 22 is executed according to a user instruction, and displays the profile input UI shown in FIG. 11 (step 222). An example of the UI displayed here is the content described in FIG. When the user completes input of the profile input UI, the contents of the next input profile are stored in the profile DB 40 (step 223).

  FIG. 14 shows an example of a GUI (Graphical User Interface) as an example of a UI (User Interface) provided to the user in order for the configuration management program 20 to select a server 60 as a profile deployment destination. The GUI is displayed on the output device 16 connected to the management server 10 or a display device of another terminal connected to the management server 10 via the network 70 using a browser, a dedicated program, text, and the like. A window 1640 shows a browser or a program window.

  A window 1640 displays a list of candidates for the server 60 that is a profile deployment destination, buttons for operation, and the like. The user selects a profile to be deployed in the profile selection frame 1641. In the example of FIG. 14, selection by pull-down is possible. When a profile is selected, spec information defined in the profile is displayed in the spec frame 1642. Specifically, the CPU type, frequency, number of cores, memory capacity, number of network connections, and number of storage connections. As a deployment destination server candidate list, a deployment candidate list frame 1643 displays a list of servers 60 that are deployment destination candidates and their specification information. The evaluation frame 1644 displays guide information that is helpful when the user selects a deployment destination server. In the example of FIG. 14, guide information is displayed in five stages using five stars. When the server 60 in the deployment candidate list frame 1643 is clicked, the server 60 is selected as a profile deployment destination (hatched portion in FIG. 14). When the profile deployment button 1645 is clicked with the server 60 selected, the profile is deployed to the server 60. To cancel, click Cancel 1646.

FIG. 15 shows a flowchart of processing performed by the deployment unit 23 of the configuration management program 20. The deployment unit 23 is executed based on an instruction from the user, and displays a profile deployment UI (step 231). An example of the UI displayed here is the content described in FIG. When the user selects a profile to be deployed in the profile deployment UI (step 232), the deployment unit 23 searches for candidates for the server 60 to which the selected profile is deployed (step 233). Here, the search of the server 60 uses the specification information (performance information) of the profile selected in the UI of FIG. 14, and among the servers 60 in the server pool table 32, the server 60 in the pool state (profile is not deployed). The deployment unit 23 lists servers 60 that satisfy the profile specification information. Specifically, satisfying the specification means that the CPU type specified by the UI in FIG. 14 matches, and the CPU frequency, the number of cores, the memory capacity, and the number of NIC and HBA ports satisfy the following conditions. To meet.
Value of profile specification information ≤ Value of specification information of server 60 (Equation 1)
The deployment unit 23 deploys a profile of the pooled server 60 in which the CPU operating frequency value, the number of cores, the memory capacity value, and the number of ports of the NIC 616 and the HBA 615 satisfy the above expression (1). Extract as previous candidate.

  Next, the deployment server candidates listed in step 233 are evaluated (step 234). The result of this evaluation is information displayed in the evaluation frame 1644 shown in FIG. Here, the evaluation performed by the deployment unit 23 specifically increases the number of stars as the value of the spec information of the profile compared in the above formula (1) is closer to the value of the spec information of the server 60, and the farther it is, Such as reducing the number of stars.

  In addition, the server 60 which does not satisfy | fill said Formula 1 may be left as a candidate in step 233, and the said server 60 may make the evaluation which makes the number of stars zero in step 234. Next, the server 60 listed in step 233 and the evaluation result of each server 60 in step 234 are displayed on the profile deployment UI (step 235).

  Thereby, the server list of the deployment candidate list frame 1643 and the evaluation frame 1644 of each server 60 shown in FIG. 14 are displayed on the profile deployment UI. When the user operates the UI shown in FIG. 14 to complete the selection of the server 60 as the profile deployment destination (step 236), the selected server 60 and the profile state are updated. Specifically, the deployment unit 23 updates the state (column 322) of the server 60 selected in step 236 in the server pool table 32 to “in use” and deploys the profile deployment server ( Update the column 404) to hold the identifier of the selected server 60.

  Next, the deployment unit 23 calls the determination unit 24 to deliver the profile to be deployed to the determination unit 24 and the selected server 60 (step 238).

  FIG. 16 shows an example of a GUI (Graphical User Interface) as an example of a UI (User Interface) provided for the configuration management program 20 to select a storage device 80 candidate for the user. The GUI is displayed on the output device 16 connected to the management server 10 or a display device of another terminal connected to the management server 10 via the network 70 using a browser, a dedicated program, text, and the like. A window 1660 indicates a browser or a program window. The window 1660 displays a list of storage candidates and buttons for operation. In the storage information frame 1661, the capacity of the desired storage device 80 is displayed. The storage candidate list 1662 displays LU information 1663, capacity 1664, and evaluation 1665 of the storage apparatus 80 as a list of candidate storage apparatuses 80. The LU information 1663 displays the storage device identifier and LU number of the relevant storage device 80. In the capacity, the capacity of the storage device 80 is displayed. In the evaluation 1665, guide information that is helpful when the user selects the deployment destination server 60 is displayed. In the illustrated example, guide information is displayed in five stages using five stars. The user clicks a button 1666 to select the storage device 80. The selected button 1666 indicates a double circle in the illustrated example. When the confirmation button 1667 is clicked while the storage device 80 is selected, the selection of the storage device 80 is confirmed. To cancel, click Cancel 1668.

  FIG. 17 shows a flowchart of processing performed by the determination unit 24 of the configuration management program 20. The determination unit 24 uses the profile to be deployed acquired from the deployment unit 23 and the information of the server 60 selected in step 236 to list the network 70 candidates from the network pool table 33 (step 2401). The detailed processing flow of step 2401 is described in FIG. Next, the determination unit 24 evaluates candidates for the network 70 (step 2402). Here, the evaluation of the network 70 specifically increases the number of stars as the performance (transmission speed) of the network 70 increases, and increases the number of added values such as QoS (Quality of Service) as the number of stars. Increase.

  Next, the determination unit 24 displays a network candidate selection UI (step 2403). The network candidate selection UI is a UI for selecting a candidate for the network 70 in the same manner as the selection UI of the storage apparatus 80 shown in FIG. 16, and is not shown in FIG. Specifically, the connection destination virtual network number of the network 70 requested by the profile, a list of candidates for the network 70, the network devices constituting the network 70, the performance and QoS settings of the network 70, and the corresponding This is a UI for displaying the evaluation shown in Step 2402 of the network 70 and allowing the user to select the network 70 from those candidates.

  When the user completes selection of a network using the network candidate selection UI, the determination unit 24 acquires a network interface identifier corresponding to the selected network 70 (step 2404). Specifically, the network interface identifier corresponding to the selected network 70 is acquired from the network pool table 33, and the status (column 332) of the network interface identification in the network pool table 33 is updated to “in use”. The in-use flag (column 313) of the corresponding network interface identifier in the identifier pool table 31 is updated to “in use”. Further, the acquired network interface identifier is added to the network (column 405) of the profile DB 40. Next, it is confirmed whether the network interface identifiers of all the networks 70 of the profile to be deployed have been acquired. If yes, go to step 2411; if no, go to step 2401.

  Next, the determination unit 24 lists storage candidates from the storage pool table 34 using the profile to be deployed acquired from the deployment unit 23 and the information of the selected server 60 (step 2411). The detailed processing flow of step 2411 is described in FIG. Next, the determination unit 24 evaluates the storage candidate (step 2412). Here, the evaluation of the candidates for the storage device 80 is specifically performed by increasing the number of stars as the capacity of the storage device 80 in the specification information of the profile is closer to the capacity of the storage candidate, and decreasing the number of stars as it is further away. Next, the determination unit 24 displays the storage candidate selection UI (step 2413). Here, an example of the UI displayed by the determination unit 24 is the content described in FIG. When the user completes the selection of the storage device 80 from the storage candidate selection UI candidates, the determination unit 24 acquires a storage interface identifier corresponding to the selected storage device 80 (step 2414). Specifically, the determination unit 24 acquires the storage interface identifier corresponding to the storage device 80 selected by the UI of FIG. 16 from the storage pool table 34, and the corresponding network interface identification state (column) in the storage pool table 34. 342) is updated to “in use”, and the in-use flag (column 313) of the corresponding storage interface identifier in the identifier pool table 31 is updated to “in use”. Further, the acquired storage interface identifier is added to the storage (column 406) of the profile DB 40.

  Next, the determination unit 24 confirms whether the storage interface identifiers of all the storage apparatuses 80 of the profile to be deployed to the set server 60 have been acquired. If yes, go to step 2416; if no, go to step 2411. In step 2416, the application unit 25 is called, and the identifier of the server 60 that deploys the profile, the acquired list of network interface identifiers, and the acquired list of storage interface identifiers are transferred to the application unit 25.

  FIG. 18 shows a detailed flowchart of the process of listing candidates for the network 70 performed in step 2401 of FIG. In step 2422, the determination unit 24 filters (excludes) the network 70 in use from the network pool table 33. Specifically, the column 332 in the network pool table 33 remains in the “pool” state, and the “in use” state is excluded. Next, in step 2424, the determination unit 24 searches for network 70 candidates that satisfy the specifications of the network 70 of the profile to be deployed in the server 60 and have not been filtered. Specifically, a network interface identifier (MAC address) connectable to the virtual network (VLAN number) defined in the profile to be deployed is searched from the network pool table 33 and listed. In step 2425, it is confirmed in step 2424 whether there is a candidate for the network 70. If yes, the process ends, and if no, the user is notified of the lack of a network pool (step 2426). Specifically, this notification is a display on a UI or the like. In step 2426, the process may wait until the process of increasing the pool of the network 70 is performed, or another program may be called to perform the process of automatically increasing the pool of the network 70.

  FIG. 19 shows a detailed flowchart of the processing for listing storage candidates performed in step 2411 of FIG. In step 2434, the determination unit 24 filters (excludes) the storage device 80 in use from the storage pool table 34. Specifically, the column 342 in the storage pool table 34 remains in the “pool” state and the “in use” state is excluded. Next, in step 2436, the determination unit 24 filters (excludes) storage devices 80 that are incompatible with the attributes of the storage device 80. Here, the storage device 80 that does not match the attribute information in the definition of the profile to be deployed is filtered using the information shown in the attribute information (column 346) of the storage pool table 34. For example, in the profile definition, the OS is “Windows” (registered trademark), but if the attribute information of the storage device 80 is “OS: for Linux”, the storage device 80 is filtered (excluded).

Next, in step 2437, the determination unit 24 searches and lists storage candidates that satisfy the capacity of the storage device 80 defined by the profile to be deployed and that are not filtered. Here, satisfying the capacity (spec) satisfies the following conditions:
Storage capacity of profile ≦ Storage capacity of storage pool table 34
......... (Formula 2)
In step 2438, the determination unit 24 checks in step 2437 whether or not there is a storage candidate. If yes, the process ends, and if no, the user is notified of a storage pool shortage (step 2439). Specifically, display on a UI or the like. In step 2439, the process may wait until the process of increasing the pool of the storage device 80 is performed, or another program may be called to perform the process of automatically increasing the pool of the storage apparatus 80. .

  FIG. 20 shows a flowchart of processing performed by the application unit 25 of the configuration management program 20. The application unit 25 acquires an interface identifier of an I / O interface (NIC 616 and HBA 615) connected to an external device or apparatus from the determination unit 24, and transmits an I / O interface to the server 60 as a profile deployment destination. An instruction is given to rewrite the interface identifier of the face (step 251). Here, the identifier rewriting program 620 (shown in FIG. 2) on the server 60 side receives the instruction from the application unit 25, and rewrites the network interface identifier of the NIC 616 of the server 60 and the storage interface identifier of the HBA 615, respectively. The identifier rewriting program 620 may be distributed to the server 60 by the application unit 25 when step 251 is executed. As a delivery method, for example, delivery is performed by network boot such as PXE boot.

  When the identifier rewriting program 620 of the server 60 completes rewriting of the interface identifier of the I / O interface, it confirms whether the server 60 can connect to the network 70 and the storage device 80 defined in the profile (step 252). Specifically, the application unit 25 distributes a test program for connection to the server 60, and the corresponding test program sends a packet to the network 70 and accesses the storage device 80. The test program of the server 60 confirms the success of the connection from the I / O interface to the connection destination (external device or apparatus) (step 253). If the connection is successful, the process proceeds to step 254, and if it fails, the process proceeds to step 255. In step 254, the user is notified of the completion of connection of the server 60 where the profile is deployed. Specifically, this notification is a display on the UI. In step 255, the user is notified that the connection has failed. Here, retry may be performed from step 251.

  FIG. 21 shows a flowchart of processing performed by the cancellation unit 26 of the configuration management program 20. The canceling unit 26 acquires a request for canceling profile deployment in operation on the server 60 based on an instruction from the user (step 261). This request is accepted from the UI of the configuration management program 20 or the like. Next, the cancellation unit 26 inquires whether or not the resource is initialized (step 262). Specifically, the user is inquired about whether to initialize the network 70 and the storage device 80 using a UI or the like, and acquires whether or not initialization is necessary. It is confirmed whether or not resource initialization is necessary (step 263). If necessary, the process proceeds to step 264. If not necessary, the process proceeds to step 267.

  In step 264, the canceling unit 26 confirms the state of the server 60 whose profile deployment is cancelled. Here, the state of the server 60 is a power supply state, presence / absence of a failure, or the like. If the server 60 is in an active state, a UI prompting the user to stop is displayed and the user 60 waits until the user stops, or the server 60 is automatically shut down and stopped. In step 265, the network 70 is initialized. Specifically, the cancellation unit 26 distributes the initialization program to the server 60 and sends an initialization packet of the ARP table to a part or all of the network 70. In step 265, the storage apparatus 80 is initialized. Specifically, the release unit 26 delivers an initialization program to the server 60 and clears data for a part or all of the storage device 80. Since the initialization program may be the same as the program sent in step 265, it may be distributed once. Further, it is not always necessary to perform both step 265 and step 266.

  In step 267, the canceling unit 26 notifies the server 60 of a request to cancel the interface identifier being used by the server 60 that cancels the profile deployment. Release of the interface identifier in use returns, for example, the interface identifiers of NIC 616 and HBA 615 installed in server 60 to the default interface identifiers of NIC 616 and HBA 615. In step 268, profile release processing is performed. Here, the interface identifier described in the network (column 405) and storage device (column 406) is acquired for the profile to be canceled in the profile DB 40, and the in-use flag (column) of the corresponding interface identifier in the identifier pool table 31 is acquired. 313) is updated to “unused”, the state of the corresponding interface identifier in the network pool table 33 (column 332) is updated to “pool”, and the state of the corresponding interface identifier in the storage pool table 34 (column 342) is updated. Update to "Pool". Further, the canceling unit 26 updates the state (column 322) of the server 60 that cancels the deployment of the profile in the server pool table 32 to “pool”, and the profile deployment server (column 404) that cancels the profile DB 40 “undeployed”. And the network (column 405) and storage (column 406) are cleared.

  According to the present embodiment, the connection between the server 60, the network 70, and external devices such as the storage device 80 related to the construction or configuration change of the computer system can be performed only by changing the interface identifier on the server 60 side. it can. Thus, in a computer system including the network 70 managed by the network management server 170, the storage device 80 managed by the storage management server 180, and the server 60 managed by the server administrator, the server administrator operates the management server 10. By simply changing the network interface identifier and storage interface identifier of the server 60, it becomes possible to easily and quickly change the configuration of an external device or apparatus connected to the I / O interface of the server 60. . In this way, by simply changing the interface identifier of the I / O interface for connecting the server 60 to an external device or apparatus, the external device or apparatus that communicates with the I / O interface can be selected. Can do. Thereby, the user (or server administrator) of the management server 10 requests the administrator of the network management server 170 or the administrator of the storage management server 180 to change the communication path or access path as in the conventional example. The communication path and access path according to the profile of the server 60 can be quickly set.

<Embodiment 2>
In the first embodiment, a case has been described in which any network 70 and any storage device 80 can be connected from the server 60 constituting the computer system. In the second embodiment, a case will be described in which there are a network 70 and a storage device 80 that cannot be connected from the server 60 constituting the computer system.

  In the present embodiment, the server connection destination information shown in the column 324 is required in the server pool table 32 shown in FIG. A column 324 holds information on the network 70 and the storage device 80 to which the server 60 shown in the column 321 can be connected. For example, if the storage apparatus 80 that can be connected from the HBA 1 is the storage apparatus 1 and the storage apparatus 2, “HBA 1: storage apparatus 1, storage apparatus 2” is described.

  FIG. 22 shows a flowchart of processing performed in the network pool candidate search 2401 of this embodiment. FIG. 22 shows processing for replacing the network pool candidate search 2401 of the determination unit 24 shown in FIG. 18 of the first embodiment. 22 is different from the first embodiment in that step 2423 is added.

  In step 2423, the determination unit 24 filters (excludes) the network 70 to which the profile deployment server 60 cannot be connected. Specifically, the determination unit 24 uses the connection destination (column 324) of the server pool table 32 and the affiliation (column 333) of the network pool table 33, and belongs to the network device 701 that cannot be connected from the deployment destination server 60. Filter (exclude) the network 70.

  FIG. 23 shows a flowchart of processing performed in the storage pool candidate search 2411 of this embodiment. FIG. 23 shows processing for replacing the storage pool candidate search 2411 of the determination unit 24 shown in FIG. 19 of the first embodiment. FIG. 23 is different from the first embodiment in that step 2435 is added. In step 2435, the storage apparatus 80 to which the server 60 as the profile deployment destination cannot be connected is filtered (excluded). Specifically, the determination unit 24 uses the connection destination (column 324) of the server pool table 32 and the affiliation (column 343) of the storage pool table 34 to store the storage belonging to the storage device 80 that cannot be connected from the deployment destination server ( LU90).

  According to this embodiment, even when there is a network 70 and a storage device 80 that cannot be connected from the server 60, the configuration of the computer system is configured using the network 70 and the storage device 80 that can be connected from the server 60. Can change.

<Embodiment 3>
In the first embodiment and the second embodiment, the case where the computer system is configured for all the servers 60, the network 70, and the storage device 80 that configure the computer system has been described. In the third embodiment, a case will be described in which the configuration of a computer system is changed for a part of servers 60, a network 70, and a storage device 80 constituting the computer system according to a user.

  In this embodiment, the table group 30 shown in FIG. 1 needs to have the group table 35 shown in FIG. 9 that holds user and group information.

  In this embodiment, the group information shown in the column 325 is required in the server pool table 32 shown in FIG. A column 325 holds a group identifier to which the server 60 shown in the column 321 belongs. One server 60 may belong to a plurality of groups. In that case, a plurality of group identifiers are held in the column 325.

  In this embodiment, the group information shown in the column 335 is required in the network pool table 33 shown in FIG. A column 335 holds a group identifier to which the network 70 belongs. One network 70 may belong to a plurality of groups. In that case, a plurality of group identifiers are held in the column 335.

  In this embodiment, the group information shown in the column 348 is required in the storage pool table 34 shown in FIG. A column 348 holds a group identifier to which the storage device 80 belongs. One storage device 80 may belong to a plurality of groups. In that case, a plurality of group identifiers are held in the column 348.

  FIG. 9 shows an example of the group table 35. A column 351 holds user identifiers. A column 352 holds an identifier of a group that can be used by the user in the column 351. Here, when the user can use a plurality of groups, a plurality of group identifiers are held.

  In this embodiment, as a method of acquiring group information of the server pool table 32, the network pool table 33, and the storage pool table 34, for example, the acquisition unit 21 displays a UI for setting group information after the table is created. Let the user input. The creation of the group table 35 is the same.

  In this embodiment, before displaying the profile deployment UI described in the deployment unit 23, a login screen for authenticating the user is displayed on the UI, the user is identified, and the group that can be used by the user Is obtained from the group table 35. Furthermore, in step 233 (FIG. 15) of the deployment unit 23 shown in the first embodiment, only the server 60 of the group that can be used by the user is selected as a candidate using the group (column 325) of the server pool table 32.

  FIG. 24 shows a flowchart of processing performed in the network pool candidate search 2401 of this embodiment. 24 differs from the second embodiment in that step 2421 is added. In step 2421, the determination unit 24 filters (excludes) the network 70 of the group that cannot be used by the user. Specifically, the network 70 that does not match the group identifier that can be used by the logged-in user is filtered (excluded) using the group (column 335) of the network pool table 33.

  FIG. 25 shows a flowchart of processing performed in the storage pool candidate search 2411 of this embodiment. FIG. 25 is different from the second embodiment in that step 2433 is added. In step 2433, the determination unit 24 filters the storage devices 80 of the group that cannot be used by the user. Specifically, the storage device 80 that does not match the group identifier that can be used by the logged-in user is filtered using the group (column 348) of the storage pool table 34.

  According to the present embodiment, when a plurality of users share and use the same computer system, the range of the server 60, the network 70, and the storage device 80 that can be used by each user can be limited.

<Embodiment 4>
In the first embodiment, the case where the server 60 occupies the storage apparatus 80 has been described. In the fourth embodiment, a case where the storage apparatus 80 is shared by a plurality of servers 60 will be described.

  In this embodiment, the shared information shown in the column 347 is required in the storage pool table 34 shown in FIG. A column 347 indicates whether or not the corresponding storage device 80 can be shared. In the figure, “○” is indicated when sharing is possible.

  In the present embodiment, the UI provided for inputting and updating the profile shown in FIG. 11 has a sharing setting button 1609. By clicking the share setting button 1609, a UI for performing the share setting of the storage apparatus 80 is displayed. An example of a UI for performing sharing settings for the storage apparatus 80 is shown in FIG.

  In the present embodiment, in the profile DB 40 shown in FIG. 12, the sharing setting of the storage apparatus 80 is held as information on the specification (column 403). Specifically, when sharing is not necessary, “not-share” is held for the information in the storage device 80, and when sharing is necessary, “share: LU2” is used as LU information to be shared. Describe. Note that information about the storage apparatus 80 to which the LU belongs may be held as LU information.

  FIG. 26 shows an example of a GUI as an example of the UI that the configuration management program 20 provides the user with the sharing setting. The GUI is displayed on a display device 15 connected to the management server 10 or a display device of another terminal connected to the management server 10 via the network 70 using a browser, a dedicated program, text, and the like. A window 1680 indicates a browser or a program window. The window 1680 displays a list of sharable storage device 80 candidates, buttons for operation, and the like. The sharable storage list frame 1681 displays LU information 1682, capacity 1683, sharable remaining number 1684, and shared server 1685 of the storage device 80 as a list of candidate storage devices 80. The LU information 1682 displays the storage device identifier and LU number of the storage device 80. In the capacity 1683, the capacity of the storage device 80 is displayed. The remaining shareable number 1684 displays the remaining number that can be shared by the storage device 80. This value is calculated from the remaining number of storage interface identifiers that can be connected to the storage device 80. The shared server 1685 displays the identifier of the server 60 to which the relevant storage device 80 is currently assigned. The user clicks a button 1686 to select the storage device 80. The selected button 1686 indicates a double circle in the example of the figure. When the OK button 1687 is clicked with the storage device 80 selected, the selection of the storage device 80 is confirmed. To cancel, click Cancel 1688.

  FIG. 27 shows a flowchart of processing performed by the definition unit 22 of the present embodiment. 27 differs from the third embodiment in that step 221 is added. In step 221, the definition unit 22 searches for sharable storage device 80 candidates. More specifically, the definition unit 22 lists the storage pool table 34 whose sharing information (column 347) is “◯”. The storage devices 80 listed here are displayed in the sharing setting UI shown in FIG.

  FIG. 28 shows a flowchart of processing performed in the storage pool candidate search 2411 of this embodiment. 28 differs from the third embodiment in that step 2431 and step 2432 are added. In step 2431, the determination unit 24 confirms whether the shared storage device is set in the profile. If there is a shared storage device setting, the process proceeds to step 2432. Here, the setting of the shared storage in the profile is specifically a case where there is a storage device 80 having information “share” as information of the specification (column 403) of the profile DB 40. In step 2432, candidates are narrowed down to the designated storage device 80. Specifically, the LU information described in the information of the specification (column 403) of the profile DB 40 is narrowed down to the storage apparatus 80 that can be connected to the corresponding LU 90.

  According to this embodiment, it is possible to construct a computer system that shares a single storage device 80 among a plurality of servers 60 and uses it as a shared storage device.

<Embodiment 5>
In the first embodiment, the case where one OS is executed for one server 60 has been described. In the present embodiment, a case where a plurality of virtual servers of one server 60 are operated and the OS can be executed for each virtual server will be described.

  FIG. 29 shows the configuration of the server 60 of this embodiment. The difference from the first embodiment is that the memory 611 holds the virtualization unit 630 and the virtual server 631. The virtualization unit 630 is a hypervisor (also referred to as a virtual machine monitor) that manages the execution of the virtual server 631 on the server 60, and each of the virtual servers 631 causes the OS to execute.

  In this embodiment, the evaluation method of the server 60 in step 234 of FIG. 15 of the first embodiment is different, and the number of stars is increased as the value of the spec information of the profile is smaller than the value of the spec information of the server 60. The larger the number, the less the number of stars.

  FIG. 30 shows a flowchart of processing performed by the application unit 30 of this embodiment. The difference from the first embodiment is that step 256 and the virtualization unit 630 are added, and step 251 and step 252 are deleted. In step 256, the application unit 30 requests the virtualization unit 630 to construct the virtual server 60 according to the profile. Here, the application unit 25 requests the virtualization unit 630 to set the interface identifier of the virtual NIC and virtual HBA created for the virtual server to the interface identifier acquired from the determination unit 24. The virtualization unit 630 creates the requested virtual server and sets the interface identifiers of the virtual NIC and virtual HBA of the corresponding virtual server.

  According to the present embodiment, a computer system in which the virtual server 631 operates on the server 60 can be constructed.

<Embodiment 6>
In the first embodiment, the case where the server 60 includes the NIC 616 and the HBA 615 in a fixed manner has been described. In the present embodiment, a case where the NIC and HBA of the server 60 can be changed will be described.

  FIG. 31 shows the configuration of the server 60 of this embodiment. The difference from the first embodiment is that the server 60 does not have the identifier rewriting program 620 and is connected to the I / O switch 640 via the connection unit 617. The I / O switch 640 includes a management NIC 614, a connection unit 617, and an I / O allocation unit 641, and one or more downstream via the I / O allocation unit 641 (interface side) via a port (not shown). HBA 615 and one or more NICs 616 are connected. The I / O allocation unit can change the allocation between the server 60 and the HBAs 615 and NICs 616 according to a command from the management NIC 614 of the server 60.

  In the present embodiment, the application unit 25 notifies the I / O allocation unit 641 of the interface identifier acquired from the determination unit 24 in step 251 of FIG. 20 described in the first embodiment. The I / O allocation unit 641 allocates the HBA 615 and NIC 616 having the acquired interface identifier to the server 60.

  In the present embodiment, the release unit 26 releases the NIC and HBA assignments assigned to the server 60 in step 267 of FIG. 21 shown in the first embodiment.

  According to the present embodiment, it is possible to construct a computer system even when the server 60 does not have interface identifier rewriting means.

<Supplement>
In the server computer configuration management method according to claim 1, one of the interface identifiers is a WWN.

  In the server computer configuration management method according to claim 1, one of the interface identifiers is a MAC address.

  The server computer configuration management method according to claim 1, wherein the network identifier is a virtual network (VLAN) number.

<1>
A server computer having an interface; a management server that manages the plurality of server computers; and a communication path in which an external device that performs communication corresponding to the interface identifier set in the interface is set. And managing the configuration of the plurality of server computers,
Whether the management server acquires each of the plurality of interface identifiers set as connection destinations of the plurality of external devices, and whether the acquired interface identifier is being used by any of the server computers Storing information indicating ??? in the first table;
The management server respectively acquiring specifications of the plurality of external devices and storing them in the first table;
The management server accepting a profile;
A first interface indicating that the management server is set as a connection destination of a first external device satisfying the profile and information indicating whether or not the server computer is in use is not in use. Obtaining a face identifier from the first table;
Updating the information indicating whether or not the acquired first interface identifier is being used in any of the server computers in the first table;
The management server transmitting an instruction to rewrite the interface identifier of the first interface of the first server computer to the acquired first interface identifier to the first server computer;
The first server computer receives the instruction, and rewrites the interface identifier of the first interface with the first interface identifier. .

<2>
The external device includes a network device and a storage device,
The interface includes a storage interface that communicates with the storage device;
The interface identifier includes a storage interface identifier set for the storage interface,
The first table is:
A storage pool table that holds the relationship between the storage interface identifier set in the storage device and the disk capacity;
The management server obtains each of the interface identifiers set as connection destinations of the plurality of external devices, and stores them in the first table,
Obtaining the relationship between the storage interface identifier and disk capacity and storing it in the storage pool table;
The management server obtains a first interface identifier set as a connection destination of a first external device satisfying the profile from the first table,
Obtaining a storage device having a capacity satisfying the profile from the storage pool table, and obtaining a storage interface identifier corresponding to the obtained storage device. The server computer according to <1>, Configuration management method.

<3>
The management server receiving a request to cancel the deployment of the profile;
The management server updates the information indicating whether or not the first table is being used with respect to the interface identifier of the server computer that has received the release request;
The server computer configuration management method according to <1>, further comprising:

<4>
The management server includes a group table that holds a relationship between an identifier of a user and a group identifier of a group that can be used by the user,
The first table stores a group identifier to which the external device belongs,
The management server identifies a user who uses the server computer, specifies a group identifier of a group available to the user from the group table,
The management server obtains a first interface identifier set as a connection destination of a first external device satisfying the profile from the first table,
In the first table, among the plurality of external devices satisfying the profile, the first group device is set as the connection destination of the first external device whose group identifier belongs to the specified group identifier. <1> The configuration management method for a server computer according to <1>, wherein the interface identifier is acquired.

<5>
The storage pool table holds a flag indicating that the storage device can be shared from the plurality of server computers,
The management server accepting the profile includes:
Receiving information on whether or not to share the storage device,
Acquiring a storage device having a capacity satisfying the profile from the storage pool table, and acquiring a storage interface identifier corresponding to the acquired storage device,
When the accepted profile shares a storage device, it indicates that the flag of the storage pool table is sharable, and obtains a storage device having a capacity specified by the profile from the storage pool table. <2> The server computer configuration management method according to <2>.

<6>
A plurality of server computers having interfaces;
A management server for managing a plurality of the server computers;
In a computer system comprising: a communication path in which an external device that performs communication corresponding to an interface identifier set in the interface is set;
The management server
A first table storing information indicating whether or not a plurality of the interface identifiers set as connection destinations of the plurality of external devices are being used by any of the server computers;
The management server acquires each of the interface identifiers and specifications set as connection destinations of the plurality of external devices, and stores them in the first table;
A definition part that accepts a profile;
A first interface identifier that is set as a connection destination of a first external device that satisfies the profile and that indicates that information indicating whether or not the server computer is being used is not being used; From the first table,
In the first table, a confirmation unit that updates information indicating whether or not the acquired first interface identifier is being used by any of the server computers;
An application unit that transmits an instruction to rewrite the interface identifier of the first interface included in the first server computer to the acquired first interface identifier to the first server computer;
The computer system, wherein the first server computer receives the instruction and rewrites the interface identifier of the first interface with the first interface identifier.

<7>
The external device includes a network device and a storage device,
The interface includes a storage interface that communicates with the storage device;
The interface identifier includes a storage interface identifier set for the storage interface,
The first table is:
A storage pool table that holds the relationship between the storage interface identifier set in the storage device and the disk capacity;
The acquisition unit
Obtaining the relationship between the storage interface identifier and disk capacity and storing it in the storage pool table;
The determination unit is
The computer system according to <6>, wherein a storage apparatus having a capacity satisfying the profile is acquired from the storage pool table, and a storage interface identifier corresponding to the acquired storage apparatus is acquired.

<8>
The management server
Receiving the request for canceling the deployment of the profile, for the interface identifier of the server computer that has received the cancel request, the information indicating whether or not the first table is being used is updated to unused. The computer system according to <6>, further including a release unit.

<9>
The management server further includes a group table that holds a relationship between a user identifier and a group identifier of a group available to the user,
The first table stores a group identifier to which the external device belongs,
The management server identifies a user who uses the server computer, specifies a group identifier of a group available to the user from the group table,
The determination unit is
In the first table, among the plurality of external devices satisfying the profile, the first group device is set as the connection destination of the first external device whose group identifier belongs to the specified group identifier. <5> The computer system according to <6>, wherein the interface identifier is acquired.

<10>
The storage pool table holds a flag indicating that the storage device can be shared from the plurality of server computers,
The definition part is:
Receiving information on whether to share the storage device used by the server computer;
The determination unit is
When the accepted profile shares a storage device, it indicates that the flag of the storage pool table is sharable, and obtains a storage device having a capacity specified by the profile from the storage pool table. <7> The computer system as described above.

  As described above, the present invention provides a plurality of servers managed by the management server, an external device in which a communication path is set in advance, a plurality of servers managed by the management server, and an external device provided in the server. The present invention can be applied to a computer system having an I / O interface that communicates with a device, and in particular, can be applied to a management server or a management program that manages a plurality of servers.

10 management server 11 memory 12 CPU
13 NIC
DESCRIPTION OF SYMBOLS 14 I / O interface 15 Input device 16 Output device 20 Configuration management program 21 Acquisition part 22 Definition part 23 Deployment part 24 Determination part 25 Application part 26 Release part 30 Table group 31 Identifier pool table 32 Server pool table 33 Network pool table 34 Storage pool table 35 Group table 40 Profile DB
51 Management network 60 Server 70 Network 80 Storage device 90 LU

Claims (12)

A computer system management method comprising a server, a management server that manages the server, and one or more storage devices,
The one or more storage apparatuses have one or more logical units, and when set to an interface, manage one or more identifiers that are permitted to access the one or more logical units from the set interface. And
The management server stores storage pool information for managing the capacity of the one or more logical units, the one or more identifiers, and information indicating whether the one or more identifiers are being used by the server. Have
The management method is:
Receiving a request for a capacity of a logical unit accessed from a virtual server generated in the server by the management server;
Selecting, from the one or more logical units, a first logical unit satisfying the capacity requirement by the management server based on the storage pool information;
When the management server sets an interface based on the storage pool information, access from the set interface to the first logical unit is permitted, and a first identifier that is not being used by the server is set. A step to obtain,
Transmitting, by the management server, a request for generating the virtual server and setting the acquired first identifier in an interface of the generated virtual server;
Generating the virtual server having a first interface by the server;
Setting the identifier of the first interface to the first identifier by the server;
A computer system management method comprising the steps of: The management method according to claim 1,
The management server includes a step of updating information indicating whether or not the first identifier is being used in the server among the storage pool information to information indicating that the server is being used. Management method. The management method according to claim 2,
Receiving a request to cancel deployment of the first logical unit to the virtual server by the management server;
Notifying the server of a request to stop using the first identifier by the management server;
Updating, by the management server, information indicating whether or not the first identifier of the storage pool information is being used by the server, to information indicating that the server is not being used;
The management method characterized by having. The management method according to claim 1,
The management server has group information for managing one or more user identifiers for identifying one or more users and one or more group identifiers for identifying one or more groups to which the one or more users belong,
The storage pool information includes a capacity of the one or more logical units, the one or more identifiers, information indicating whether the one or more identifiers are being used by the server, and the one or more group identifiers. And manage
The management method is:
Receiving a first user identifier for identifying a first user by the management server;
Obtaining a first group identifier for identifying a first group to which the first user belongs from the group information by the management server;
Selecting the first logical unit that satisfies the capacity requirement and is associated with the first group identifier from the one or more logical units based on the storage pool information by the management server;
The management method characterized by having. A computer system having a server, a management server that manages the server, and one or more storage devices,
The one or more storage apparatuses have one or more logical units, and when set to an interface, manage one or more identifiers that are permitted to access the one or more logical units from the set interface. And
The management server stores storage pool information for managing the capacity of the one or more logical units, the one or more identifiers, and information indicating whether the one or more identifiers are being used by the server. Have
When receiving a request for the capacity of the logical unit accessed from the virtual server generated in the server,
Based on the storage pool information, a first logical unit that satisfies the capacity requirement is selected from the one or more logical units;
When set to an interface, access to the first logical unit from the set interface is permitted, and a first identifier that is not in use by the server is acquired.
A request for setting the acquired first identifier to the interface of the generated virtual server by generating the virtual server is transmitted to the server,
The computer system generates the virtual server having a first interface, and sets the identifier of the first interface as the first identifier. The computer system according to claim 5,
The management server updates information indicating whether or not the first identifier is being used by the server among the storage pool information to information indicating that the server is being used. system. A computer system according to claim 6, wherein
The management server accepts a request to undeploy the first logical unit on the virtual server;
Notifying the server of a request to stop using the first identifier;
Of the storage pool information, the computer system updates information indicating whether or not the first identifier is being used by the server to information indicating that the server is not being used. The computer system according to claim 5,
The management server
Group information for managing one or more user identifiers for identifying one or more users and one or more group identifiers for identifying one or more groups to which the one or more users belong;
Managing the capacity of the one or more logical units, the one or more identifiers, information indicating whether the one or more identifiers are being used in the server, and the one or more group identifiers Have storage pool information,
Accepting a first user identifier identifying a first user;
Obtaining a first group identifier for identifying a first group to which the first user belongs from the group information;
A computer system that selects the first logical unit that satisfies the capacity requirement and is associated with the first group identifier from the one or more logical units based on the storage pool information. A computer system comprising a server, a management server that manages the server, and one or more network devices,
The one or more network devices manage one or more virtual networks, and when set as an interface, manage one or more identifiers that enable connection of the set interface and the one or more virtual networks. ,
The management server includes network pool information for managing the specifications of the one or more virtual networks, the one or more identifiers, and information indicating whether the one or more identifiers are being used by the server. Have
When receiving a request for the specification of a virtual network accessed from a virtual server generated in the server,
Based on the network pool information, select a first virtual network that satisfies the requirements of the specification from the one or more virtual networks,
When the interface is set, the set interface and the first virtual network can be connected to obtain a first identifier that is not being used by the server;
A request for setting the acquired first identifier to the interface of the generated virtual server by generating the virtual server is transmitted to the server,
The computer system generates the virtual server having a first interface, and sets the identifier of the first interface as the first identifier. A computer system according to claim 9, wherein
The management server updates information indicating whether or not the first identifier is being used in the server among the network pool information to information indicating that the server is being used. system. A computer system according to claim 10, wherein
The management server accepts a request to cancel the deployment of the first virtual network to the virtual server,
Notifying the server of a request to stop using the first identifier;
A computer system that updates information indicating whether or not the first identifier is being used by the server in the network pool information to information indicating that the server is not being used. A computer system according to claim 9, wherein
The management server
Group information for managing one or more user identifiers for identifying one or more users and one or more group identifiers for identifying one or more groups to which the one or more users belong;
Managing the one or more virtual network specifications, the one or more identifiers, information indicating whether the one or more identifiers are being used by the server, and the one or more group identifiers Network pool information,
Accepting a first user identifier identifying a first user;
Obtaining a first group identifier for identifying a first group to which the first user belongs from the group information;
A computer system that selects, based on the network pool information, the first virtual network that satisfies the specification requirement and is associated with the first group identifier from the one or more virtual networks.