[go: up one dir, main page]

WO2016203580A1 - Ordinateur de gestion, procédé de gestion de déplacement de ressource et système informatique - Google Patents

Ordinateur de gestion, procédé de gestion de déplacement de ressource et système informatique Download PDF

Info

Publication number
WO2016203580A1
WO2016203580A1 PCT/JP2015/067482 JP2015067482W WO2016203580A1 WO 2016203580 A1 WO2016203580 A1 WO 2016203580A1 JP 2015067482 W JP2015067482 W JP 2015067482W WO 2016203580 A1 WO2016203580 A1 WO 2016203580A1
Authority
WO
WIPO (PCT)
Prior art keywords
virtual machine
computer
management
storage area
requirement
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2015/067482
Other languages
English (en)
Japanese (ja)
Inventor
宇洋 佐藤
翔一 楠田
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hitachi Ltd
Original Assignee
Hitachi Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hitachi Ltd filed Critical Hitachi Ltd
Priority to PCT/JP2015/067482 priority Critical patent/WO2016203580A1/fr
Publication of WO2016203580A1 publication Critical patent/WO2016203580A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]

Definitions

  • the present invention relates to a technology for controlling the movement of a resource when an SLA (Service Level Agreement) is violated.
  • SLA Service Level Agreement
  • the cloud service a platform system for each user is constructed on a computer system that provides computer resources.
  • the user operates a predetermined service using the infrastructure system.
  • the infrastructure system represents a virtual infrastructure of the user.
  • the base system includes a virtual machine, a virtual drive, a virtual machine, a path connecting the virtual drives, and the like.
  • a contract regarding a quality of service called SLA is made between the provider of the cloud service and the user.
  • SLA Service Level Agreement
  • the SLA includes a plurality of requirements for each user.
  • the provider of the cloud service needs to control the allocation of computer resources allocated to the base system so as to comply with the SLA in accordance with the failure of the computer system and the configuration change.
  • Patent Document 1 states that “a server management system has a risk of an SLA violation occurring among a plurality of systems composed of virtual machines based on information related to service levels stored in a service level management table. A system is automatically migrated to a highly available environment, specifically, when a redundant configuration is possible, a virtual machine is added to a physical server and a cluster to configure a cluster. The system moves to the FT server, and after the SLA calculation unit period, the system moved to the FT server or the redundant system is returned to the original single configuration.
  • a management device or the like changes the configuration of a device that provides computer resources to a base system in order to avoid an SLA violation
  • a device that satisfies all requirements is selected. If there is no device that satisfies all the requirements, failure cannot be handled and the infrastructure system may be stopped.
  • a base system in which continuation of service is important it is important not to stop even if it is a temporary SLA violation, for example, when I / O performance is temporarily reduced.
  • An object of the present invention is to provide a management apparatus, method, and computer system that can solve the above-described problems.
  • a typical example of the invention disclosed in the present application is as follows. That is, a management computer that manages a computer system including a plurality of computers and a plurality of storage devices, and each of the computers includes at least one virtual resource generated by logically dividing a computer resource of the computer.
  • a controller management unit for managing at least one logical storage area generated by logically dividing a plurality of storage media included in the storage device; And connecting the at least one virtual machine, the at least one logical storage area, and the at least one virtual machine and a virtual drive stored in the at least one logical storage area on the computer system.
  • a base system composed of paths is constructed, and the management computer Service quality management information for managing the service quality of the infrastructure system, including a plurality of types of requirements, is stored, and the service quality management information includes information on the plurality of requirements of the at least one virtual machine constituting the infrastructure system.
  • An information acquisition unit that includes each setting value and acquires information on performance and configuration from the plurality of computers and the plurality of storage devices, and monitoring for each path based on the information acquired by the information acquisition unit For each path, a status monitoring unit that monitors the status of the computer system corresponding to an item, a target selection unit that selects a virtual machine that does not satisfy the service quality based on the monitoring result of the status monitoring unit, Conformance determination for generating conformity state management information for managing conformance states of the plurality of requirements set in the selected virtual machine And a migration destination that selects a computer that is a migration destination of the virtual machine that satisfies at least one requirement or a logical storage area that is a migration destination of the virtual drive that satisfies at least one requirement based on the conformity management information And a selection unit.
  • the management computer can select a device or the like that satisfies at least one of the plurality of types of requirements as the destination.
  • FIG. 3 is an explanatory diagram illustrating an example of a hardware configuration of a management server according to the first embodiment.
  • FIG. 3 is an explanatory diagram illustrating an example of a hardware configuration of a physical server according to the first embodiment.
  • FIG. 3 is an explanatory diagram illustrating an example of a hardware configuration of the storage apparatus according to the first embodiment. It is explanatory drawing which shows an example of the SLA input management table of Example 1.
  • FIG. It is explanatory drawing which shows an example of the SLA management table of Example 1.
  • FIG. FIG. 6 is an explanatory diagram illustrating an example of a virtual machine arrangement management table according to the first embodiment.
  • FIG. 3 is an explanatory diagram illustrating an example of a storage management table according to the first embodiment.
  • FIG. 6 is an explanatory diagram illustrating an example of a path management table according to the first embodiment. It is explanatory drawing which shows an example of the state management table of Example 1.
  • FIG. It is explanatory drawing which shows an example of the state change management table of Example 1.
  • FIG. It is explanatory drawing which shows an example of the SLA conformity state management table of Example 1.
  • FIG. 6 is a flowchart for explaining an example of a base system construction process executed by the management server according to the first embodiment.
  • 6 is a flowchart illustrating an overview of a state monitoring process executed by the management server according to the first embodiment.
  • 6 is a flowchart illustrating an example of information acquisition processing executed by the management server according to the first embodiment.
  • 6 is a flowchart illustrating an example of an information change determination process executed by the management server according to the first embodiment.
  • 7 is a flowchart illustrating an example of a virtual machine specifying process executed by the management server according to the first embodiment.
  • 6 is a flowchart illustrating an example of a generation process of an SLA conformity state management table executed by the management server according to the first embodiment. It is a flowchart explaining an example of the SLA compatibility determination process which the management server of Example 1 performs.
  • 6 is a flowchart illustrating an example of a selection process executed by the management server according to the first embodiment.
  • 6 is a flowchart illustrating an example of a selection process executed by the management server according to the first embodiment.
  • 6 is a flowchart illustrating an example of a migration process executed by the management server according to the first embodiment.
  • FIG. 1 is a block diagram showing a configuration of a computer system according to the first embodiment of the present invention.
  • the computer system includes a management server 10, a plurality of physical servers 20, a plurality of switches 30, and a plurality of storage devices 40.
  • the management server 10 is connected to a plurality of physical servers 20 and a plurality of storage devices 40 via the network 50.
  • the network 50 may be a WAN (Wide Area Network) or a LAN (Local Area Network). Note that the present invention is not limited to the connection format of the network 50.
  • the plurality of physical servers 20 are connected to the storage apparatus 40 via a network composed of a plurality of switches 30.
  • the network can be a SAN (Storage Area Network).
  • the present invention is not limited to the network connection format.
  • the plurality of physical servers 20 form a cluster
  • the computer system includes at least one FT (Fault Tolerant) server.
  • a basic system for realizing a predetermined service is constructed using computer resources provided by the physical server 20, the switch 30, and the storage device 40.
  • the infrastructure system is a computer resource space provided to the user, and includes a virtual machine 130, a path, and a virtual drive 160.
  • the path indicates a path connecting between the physical server 20 on which the virtual machine 130 operates and the storage apparatus 40 that manages the LU (Logical Unit) 150 including the virtual drive 160.
  • the physical server 20 is a computer that provides computer resources to the virtual machine 130 constituting the infrastructure system.
  • the hypervisor 120 operates on the physical server 20, the hypervisor 120 operates.
  • the hypervisor 120 logically divides computer resources of the physical server 20 and assigns them to one or more virtual machines 130. Note that a method for assigning computer resources to the virtual machine 130 is a known method, and thus the description thereof is omitted.
  • a virtual drive 160 on the storage device 40 is assigned to the virtual machine 130.
  • the hypervisor 120 includes an I / O performance measurement unit 121 and a path management unit 122.
  • the I / O performance measurement unit 121 measures the I / O performance between the virtual machine 130 and the storage device 40 that manages the virtual drive 160.
  • the path management unit 122 manages paths.
  • the switch 30 transfers data transmitted / received between the physical server 20 and the storage device 40, between the physical servers 20, or between the storage devices 40.
  • the storage device 40 is a computer that provides a storage area (virtual drive 160) to the virtual machine 130.
  • the controller management unit 140 operates on the storage device 40.
  • the controller management unit 140 generates and manages the LU 150.
  • the controller management unit 140 controls access from the virtual machine 130 to the virtual drive 160 and the like.
  • the storage apparatus 40 generates a plurality of LUs 150 using a plurality of storage media 440 described later. A part of the storage area of the LU 150 is set as the virtual drive 160.
  • the virtual machine 130 recognizes the virtual drive 160 as a physical drive (storage medium).
  • Management server 10 manages the entire computer system.
  • the management server 10 of this embodiment manages an SLA (Service Level Agreement) of the base system.
  • SLA Service Level Agreement
  • the SLA of the infrastructure system represents the quality of service connected between an operator who provides resources for constructing the infrastructure system and a user who operates a service using the infrastructure system.
  • the SLA of the base system includes multiple types of requirements.
  • the requirements are requirements for the configuration of the computer system such as redundancy and the version of the controller 400 of the storage apparatus 40. In the following description, a case where at least one requirement is not satisfied is also described as an SLA violation.
  • a management device or the like When a management device or the like selects a device that provides computer resources to the infrastructure system in order to avoid an SLA violation, it searches for a device that satisfies all requirements. If there is no device that satisfies all the requirements, failure cannot be handled and the infrastructure system may be stopped. In the case of a infrastructure system in which continuation of service is important, it is important not to stop even if a temporary SLA violation occurs, for example, I / O performance decreases. Therefore, it is necessary to change an apparatus that satisfies the requirements as much as possible in consideration of the priority order among the requirements.
  • the migration source server and the migration destination server of the virtual machine need to be set so that the same LU 150 can be accessed. Therefore, even if there is a physical server 20 that satisfies the requirements, the physical server 20 is not selected as the migration destination physical server 20 depending on the setting of the storage device 40. Therefore, it is necessary to control the physical server 20 that does not share the LU 150 so that it can be selected as the destination server.
  • the management server 10 of this embodiment considers path redundancy as a factor for determining whether or not an SLA violation has occurred.
  • the management server 10 when there is a base system that does not satisfy the SLA, the management server 10 according to the present embodiment changes the configuration of the base system so as to satisfy at least a part of the requirements.
  • the management server 10 of this embodiment also moves the virtual drive 160 to the LU 150 accessible by the destination physical server 20.
  • an SLA requirement management unit 100 On the management server 10, an SLA requirement management unit 100, an information acquisition unit 101, a state monitoring unit 102, a target selection unit 103, an SLA suitability determination unit 104, a movement destination selection unit 105, and a movement unit 106 operate.
  • the management server 10 includes an SLA input management table 110, an SLA management table 111, a virtual machine arrangement management table 112, a storage management table 113, a path management table 114, a state management table 115, a state change management table 116, and The SLA conformity state management table 117 is held.
  • the SLA requirement management unit 100 defines the SLA of the base system based on the SLA of the virtual machine 130 and the like input from the user, and manages the SLA of the virtual machine 130 and the SLA of the base system.
  • the SLA of the virtual machine 130 is managed as the SLA input management table 110
  • the SLA of the base system is managed as the SLA management table 111.
  • the information acquisition unit 101 acquires various types of information from the physical server 20, the switch 30, and the storage device 40 that constitute the computer system.
  • the state monitoring unit 102 monitors the conformity state of the SLA of the base system based on the information acquired by the information acquisition unit 101. Further, the state monitoring unit 102 detects an event that triggers a change in the configuration of the infrastructure system based on the monitoring result.
  • the target selection unit 103 selects the target virtual machine 130. More specifically, the target selection unit 103 identifies the virtual machine 130 that is affected by the event that has occurred.
  • the SLA suitability determination unit 104 determines the suitability of the SLA related to the target virtual machine 130 for each path.
  • the movement destination selection unit 105 selects a movement target based on the determination result of the SLA suitability determination unit 104 and selects a movement destination of the movement target. In this embodiment, at least one of the virtual machine 130 and the virtual drive 160 is selected as a movement target.
  • the target selection unit 103, the SLA suitability determination unit 104, and the destination selection unit 105 cooperate with each other to change the configuration of the base system so as to satisfy at least a part of the requirements.
  • the migration unit 106 moves at least one of the target virtual machine 130 and the LU 150 to the migration destination device based on the processing results of the target selection unit 103, the SLA suitability determination unit 104, and the migration destination selection unit 105.
  • the SLA input management table 110 is information for managing the SLA of the virtual machine 130 constituting the infrastructure system. Details of the SLA input management table 110 will be described with reference to FIG.
  • the SLA management table 111 is information for managing the SLA of the base system. Details of the SLA management table 111 will be described with reference to FIG.
  • the virtual machine arrangement management table 112 is information for managing the arrangement and the like of the virtual machines 130 constituting the infrastructure system. Details of the virtual machine arrangement management table 112 will be described with reference to FIG.
  • the storage management table 113 is information for managing the state of the storage device 40. Details of the storage management table 113 will be described with reference to FIG.
  • the path management table 114 is information for managing paths. Details of the path management table 114 will be described with reference to FIG.
  • the state management table 115 is information for managing the state of the configuration of the computer system. Details of the state management table 115 will be described with reference to FIG.
  • the state change management table 116 is information for managing the compliance state of the SLA of the base system in each path. Details of the state change management table 116 will be described with reference to FIG.
  • the SLA conformity state management table 117 is information for managing the SLA compliance state of the target virtual machine 130 in each path. Details of the SLA conformity state management table 117 will be described with reference to FIG.
  • the management server 10 includes resource information for managing the resource amounts of the physical server 20, the switch 30, and the storage device 40, and topology information for managing the connection relationship between the physical server 20, the switch 30, and the storage device 40. Hold. Further, the management server 10 holds infrastructure system management information for managing the configuration of the infrastructure system.
  • the physical server 20 and the storage device 40 may include the configuration of the management server 10.
  • the computer system may not include the management server 10.
  • FIG. 2 is an explanatory diagram illustrating an example of a hardware configuration of the management server 10 according to the first embodiment.
  • the management server 10 includes a processor 200, a memory 210, and a network interface 220.
  • the management server 10 may include a storage medium such as an HDD (Hard Disk Drive) and an SSD (Solid State Drive). Further, the management server 10 may include a disk interface. The management server 10 may include an input device such as a keyboard and a mouse, and an output device such as a display.
  • a storage medium such as an HDD (Hard Disk Drive) and an SSD (Solid State Drive).
  • the management server 10 may include a disk interface.
  • the management server 10 may include an input device such as a keyboard and a mouse, and an output device such as a display.
  • the processor 200 includes one or more arithmetic cores and executes a program stored in the memory 210.
  • the functions of the management server 10 can be realized by the processor 200 executing the program. In the following description, when the program is mainly described, it indicates that the processor 200 is executing the program.
  • the memory 210 stores a program executed by the processor 200 and information necessary for executing the program.
  • the program and information stored in the memory 210 will be described later.
  • the memory 210 implements the SLA requirement management unit 100, the information acquisition unit 101, the state monitoring unit 102, the target selection unit 103, the SLA suitability determination unit 104, the movement destination selection unit 105, and the movement unit 106. Stores the program.
  • the memory 210 according to the first embodiment includes an SLA input management table 110, an SLA management table 111, a virtual machine arrangement management table 112, a storage management table 113, a path management table 114, a state management table 115, a state change management table 116, And an SLA conformity state management table 117 is stored.
  • the network interface 220 is an interface for communicating with other devices via the network 50.
  • FIG. 3 is an explanatory diagram illustrating an example of a hardware configuration of the physical server 20 according to the first embodiment.
  • the physical server 20 includes a processor 300, a memory 310, a network interface 320, and a disk interface 330.
  • the physical server 20 may include a storage medium, or may include an input device and an output device.
  • the processor 300 includes one or more arithmetic cores and executes a program stored in the memory 310.
  • the functions of the physical server 20 can be realized by the processor 300 executing the program.
  • the program when the program is mainly described, it indicates that the processor 300 is executing the program.
  • the memory 310 stores a program executed by the processor 300 and information necessary for executing the program.
  • the memory 310 according to the first embodiment stores a program that implements the hypervisor 120.
  • a part of the storage area of the memory 310 is allocated to the virtual machine 130.
  • the storage area allocated to the virtual machine 130 stores an OS (not shown) and programs such as applications.
  • the network interface 320 is an interface for communicating with other devices via the network 50.
  • the disk interface 330 is an interface for accessing the storage apparatus 40.
  • FIG. 4 is an explanatory diagram illustrating an example of a hardware configuration of the storage apparatus 40 according to the first embodiment.
  • the storage device 40 includes a plurality of controllers 400 and a plurality of storage media 440.
  • the controller 400 controls the entire storage device 40.
  • the controller 400 includes a processor 410, a memory 420, and a plurality of ports 430.
  • the processor 410 includes one or more arithmetic cores and executes a program stored in the memory 420.
  • the processor 410 executes the program, the function of the storage apparatus 40 can be realized.
  • the processor 410 indicates that the program is being executed.
  • the memory 420 stores a program executed by the processor 410 and information necessary for executing the program.
  • the memory 420 according to the first embodiment stores a program that implements the controller management unit 140.
  • the port 430 is a port for connecting to the management server 10 or the physical server 20.
  • one controller 400 includes two ports 430, but is not limited thereto.
  • One controller 400 may include two or more ports 430.
  • the storage medium 440 is a device used for providing a storage area to the physical server 20.
  • the storage medium 440 may be, for example, an HDD or an SSD.
  • a RAID is configured using a plurality of storage media 440.
  • the controller management unit 140 generates a plurality of LUs 150 by logically dividing the RAID volume.
  • the LU 150 includes an OS, a program such as an application, and a virtual drive 160 that stores various data.
  • FIG. 5 is an explanatory diagram illustrating an example of the SLA input management table 110 according to the first embodiment.
  • the management server 10 holds an SLA input management table 110 for each infrastructure system.
  • the SLA input management table 110 is SLA definition information of each virtual machine 130 constituting the infrastructure system.
  • the SLA input management table 110 includes a virtual machine ID 501, a virtual machine importance 502, a response time 503, and a performance importance 504.
  • the SLA input management table 110 shown in FIG. 5 is an example, and may include other columns.
  • the virtual machine ID 501 is an identifier for uniquely identifying the virtual machine 130 constituting the infrastructure system. It should be noted that there is no problem even if the identifiers of the virtual machines 130 constituting different infrastructure systems are duplicated.
  • the virtual machine importance 502 is information indicating the importance of the virtual machine 130 in the infrastructure system. In the virtual machine importance 502 of the present embodiment, either “0” or “1” is stored. When the virtual machine importance 502 is “0”, it indicates that the virtual machine 130 is not important, and when the virtual machine importance 502 is “1”, it indicates that the virtual machine 130 is important.
  • the virtual machine 130 is generated on the physical server 20 in the cluster configuration or the physical server 20 (FT server) in the redundant configuration.
  • the response time 503 is a time required from when the virtual machine 130 issues an I / O request to the virtual drive 160 until a response is received.
  • the performance importance level 504 is information indicating the importance level of the performance of the virtual machine 130. In the performance importance 504 of the present embodiment, either “0” or “1” is stored. When the performance importance 504 is “0”, it indicates that the performance of the virtual machine 130 is not important. When the performance importance level 504 is “1”, it indicates that the performance of the virtual machine 130 is important.
  • the virtual machine 130 when the performance of the virtual machine 130 is important, the virtual machine 130 is generated on the physical server 20 having a configuration with high I / O performance, and the virtual machine 130 is virtualized on the storage device 40 capable of high-speed access.
  • the drive 160 is set.
  • the SLA input management table 110 is generated based on input from a user who operates the infrastructure system. Note that the user can input the SLA for each element constituting the infrastructure system using a predetermined interface.
  • FIG. 6 is an explanatory diagram illustrating an example of the SLA management table 111 according to the first embodiment.
  • the management server 10 defines the requirements of the computer system that constructs the infrastructure system based on the SLA input management table 110, and manages the defined requirements as the SLA management table 111.
  • the SLA input management table 110 is information that does not depend on the configuration of the computer system.
  • the SLA management table 111 is information that depends on the configuration of the computer system.
  • the SLA management table 111 includes a virtual machine ID 601, redundancy 602, firmware version 603, and response time 604.
  • the virtual machine ID 601 is the same as the virtual machine ID 501. Redundancy 602, firmware version 603, and response time 604 correspond to the SLA requirements of the underlying system.
  • Redundancy 602 is information indicating whether the path needs to be made redundant. In the redundancy 602 of this embodiment, either “present” or “not present” is stored. When the redundancy 602 is “present”, the path needs to be made redundant. When the redundancy 602 is “none”, the path need not be made redundant.
  • attribute information “must” is set in the redundancy 602 according to the SLA set in the virtual machine 130.
  • the attribute information is information indicating that the requirement is an essential requirement.
  • “present” and “must” are set in the redundancy 602.
  • the value of the virtual machine importance 502 is “0”, only “Yes” is set in the redundancy 602.
  • Firmware version 603 is information indicating whether the firmware versions of the plurality of controllers 400 included in the storage apparatus 40 match. In the firmware version 603 of this embodiment, either “match” or “not match” is stored. When the firmware version 603 is “match”, it indicates that the firmware versions of the plurality of controllers 400 match. When the firmware version 603 is “mismatch”, the firmware versions of the plurality of controllers 400 do not match. It shows that.
  • attribute information “must” is set according to the SLA set in the virtual machine 130.
  • the value of the virtual machine importance 502 is “1” and the value of the performance importance 504 is “1”
  • the firmware versions of the plurality of controllers 400 of the storage apparatus 40 are different, the response time becomes long, resulting in a decrease in I / O performance. Therefore, “match” and “must” are set in the firmware version 603.
  • the value of the virtual machine importance 502 is “1” and the value of the performance importance is “0”, only “match” is set in the firmware version 603.
  • response time 604 a value corresponding to response time 503 is stored.
  • attribute information “must” is set according to the SLA set in the virtual machine 130.
  • the value of the virtual machine importance 502 is “1” and the value of the performance importance 504 is “1”
  • “match” and “must” are set in the firmware version 603.
  • the value of the virtual machine importance 502 is “1” and the value of the performance importance is “0”
  • only “Yes” is set in the redundancy 602.
  • the management server 10 moves the virtual machine 130 or the LU 150 to a migration destination that satisfies at least essential requirements.
  • FIG. 7 is an explanatory diagram illustrating an example of the virtual machine arrangement management table 112 according to the first embodiment.
  • the management server 10 holds a virtual machine arrangement management table 112 for each infrastructure system.
  • the virtual machine arrangement management table 112 is information relating to the arrangement of the virtual machine 130 and the arrangement of the virtual drive 160 accessed by the virtual machine 130.
  • the virtual machine arrangement management table 112 includes a virtual machine ID 701, a hypervisor ID 702, a virtual drive ID 703, an LU ID 704, and a migration destination 705.
  • the virtual machine ID 701 is the same as the virtual machine ID 501.
  • the hypervisor ID 702 is an identifier for uniquely identifying the hypervisor 120 that manages the virtual machine 130.
  • the placement of the virtual machine 130 is managed using the virtual machine ID 701 and the hypervisor ID 702.
  • the virtual drive ID 703 is an identifier for uniquely identifying the virtual drive 160 accessed by the virtual machine 130.
  • the LU ID 704 is an identifier for uniquely identifying the LU 150 including the virtual drive 160.
  • the placement of the virtual drive 160 is managed using the virtual drive ID 703 and the LU ID 704.
  • the movement destination 705 is information indicating whether or not a movement target movement destination has been determined. In the movement destination 705, either “decided” or “undecided” is stored. When the movement destination 705 is “decided”, it indicates that the movement destination is determined, and when the movement destination 705 is “undecided”, it indicates that the movement destination is not determined.
  • “determined” is stored in the destination 705 as an initial value.
  • the migration destination 705 of the entry corresponding to the virtual machine 130 is updated to “undecided”.
  • FIG. 8 is an explanatory diagram of an example of the storage management table 113 according to the first embodiment.
  • the management server 10 holds a storage management table 113 for managing the storage device 40.
  • the storage management table 113 includes a storage device ID 801, a controller ID 802, a version 803, and an LU ID 804.
  • the storage device ID 801 is an identifier for uniquely identifying the storage device 40.
  • the controller ID 802 is an identifier for uniquely identifying the controller 400 included in the storage apparatus 40.
  • the version 803 is a firmware version of the controller 400.
  • the LU ID 804 is an identifier for uniquely identifying the LU 150 managed by the storage apparatus 40.
  • the value stored in LU ID 804 is the same as the value stored in LU ID 704.
  • FIG. 9 is an explanatory diagram illustrating an example of the path management table 114 according to the first embodiment.
  • the management server 10 holds a path management table 114 for managing paths.
  • paths are managed in units of physical servers 20.
  • the path management table 114 includes a hypervisor ID 901, an address 902, a port ID 903, an LU ID 904, and a status 905.
  • the hypervisor ID 901 is the same as the hypervisor ID 702.
  • the address 902 is an identifier for uniquely identifying the disk interface 330 used when the physical server 20 accesses the LU 150.
  • the port ID 903 is an identifier for uniquely identifying the port 430 to which the physical server 20 is connected.
  • the LU ID 904 is the same as the LU ID 804.
  • the status 905 is information indicating the status of the path. In this embodiment, either “active” or “idle” is stored. When the state 905 is “active”, it indicates that a valid path is set, and when the state 905 is “idle”, it indicates that an invalid path is set.
  • FIG. 10 is an explanatory diagram illustrating an example of the state management table 115 according to the first embodiment.
  • the management server 10 holds a state management table 115 for each infrastructure system.
  • the management server 10 holds the past state management table 115 of the same base system as a history.
  • the status management table 115 is information for managing the SLA compliance status of the infrastructure system corresponding to the SLA management table 111 in each path.
  • the state management table 115 includes a hypervisor ID 1001, an LU ID 1002, and a monitoring item 1003.
  • the hypervisor ID 1001 is the same as the hypervisor ID 702.
  • the LU ID 1002 is the same as the LU ID 704.
  • the path is specified by a combination of a hypervisor ID 1001 and an LU ID 1002.
  • the monitoring item 1003 is an item to be monitored for an SLA violation of the base system.
  • the monitoring item 1003 of the present embodiment includes four items of “connection”, “redundancy”, “firmware version”, and “response time”.
  • “Connection” is an item for monitoring whether or not a path exists.
  • “Redundancy”, “firmware version”, and “response time” are items corresponding to the redundancy 602, firmware version 603, and response time 604 of the SLA management table 111.
  • connection stores either “true” or “false”. When “connection” is “true”, it indicates that a path exists. When “connection” is “false”, it indicates that no path exists.
  • Redundancy stores either “true” or “false”. When “redundancy” is “true”, it indicates that there is redundancy. When “redundancy” is “false”, it indicates that there is no redundancy.
  • “Firmware version” stores either “true” or “false”. When “firmware version” is “true”, it indicates that the firmware versions of the plurality of controllers 400 of the storage apparatus 40 managing the LU 150 match. When the “firmware version” is “false”, it indicates that the firmware versions of the plurality of controllers 400 of the storage apparatus 40 managing the LU 150 do not match.
  • response time a value corresponding to the response time 604 is stored.
  • connection is “false”
  • response time is blank.
  • this embodiment is characterized in that path redundancy is considered as an index for determining the possibility of occurrence of an SLA violation.
  • FIG. 11 is an explanatory diagram illustrating an example of the state change management table 116 according to the first embodiment.
  • the management server 10 generates the state change management table 116 by comparing the newest state management table 115 and the state management table 115 with the previous time series when executing a state monitoring process described later.
  • the management server 10 holds a state change management table 116 for each infrastructure system.
  • the state change management table 116 may be deleted after the state monitoring process is completed.
  • the state change management table 116 is information for managing whether or not the value of the monitoring item 1003 has changed. Specifically, the state change management table 116 includes a hypervisor ID 1101, an LU ID 1102, and a state change 1103.
  • the hypervisor ID 1101 and the LU ID 1102 are the same as the hypervisor ID 702 and the LU ID 704.
  • the state change 1103 is a value indicating whether or not the value of the path monitoring item 1003 has changed. In the state change 1103 of this embodiment, either “present” or “not present” is stored. When the state change 1103 is “present”, it indicates that the values of all items included in the monitoring item 1003 have not changed. When the state change 1103 is “none”, it indicates that the value of at least one of the monitoring items 1003 has changed.
  • FIG. 12 is an explanatory diagram illustrating an example of the SLA conformity state management table 117 according to the first embodiment.
  • the management server 10 generates the SLA conformity state management table 117 of the virtual machine 130 that is affected by the event. At this time, the management server 10 refers to the state management table 115 based on the entry of the target virtual machine 130 in the SLA management table 111 and generates the SLA compatible state management table 117.
  • the SLA conformity state management table 117 is information indicating whether or not the SLA required for the target virtual machine 130 is satisfied in the path. Specifically, the SLA conformity state management table 117 includes a hypervisor ID 1201, an LU ID 1202, and a requirement 1203. The hypervisor ID 1201 and the LU ID 1202 are the same as the hypervisor ID 702 and the LU ID 704.
  • Requirement 1203 is information indicating the conformity state of the SLA requirements of the base system.
  • the requirement 1203 is obtained by removing “connection” from the monitoring item 1003.
  • Either “OK” or “NG” is stored in each of “redundancy”, “firmware version”, and “response time” of requirement 1203 of the present embodiment. “OK” indicates that the corresponding requirement is satisfied. “NG” indicates that the corresponding requirement is not satisfied.
  • the management server 10 determines the movement target and the movement destination of the movement target based on the SLA conformity state management table 117 as described later.
  • FIG. 13 is a flowchart illustrating an example of the infrastructure system construction process executed by the management server 10 according to the first embodiment.
  • the management server 10 receives an SLA input related to the virtual machine 130 or the like from the user (step S1301). At this time, the SLA requirement management unit 100 generates an SLA input management table 110 as shown in FIG. 5 based on the input SLA.
  • the management server 10 generates an SLA management table 111 based on the input SLA (step S1302).
  • the SLA requirement management unit 100 generates the SLA management table 111 using the SLA input management table 110.
  • the SLA requirement management unit 100 generates the SLA management table 111 according to a predetermined policy.
  • the SLA requirement management unit 100 may refer to information such as resource information and topology information in addition to the policy.
  • the management server 10 constructs a base system on the computer system based on the SLA management table 111, resource information, topology information, and the like (step S1303). Since a publicly known method may be used as a construction method of the base system, description thereof is omitted.
  • the management server 10 updates various information based on the constructed infrastructure system (step S1304). Thereafter, the management server 10 ends the process.
  • the management server 10 generates a virtual machine arrangement management table 112, a path management table 114, and infrastructure system management information, and updates the LU ID 804 and the like of the storage management table 113.
  • FIG. 14 is a flowchart illustrating an overview of the state monitoring process executed by the management server 10 according to the first embodiment.
  • the management server 10 periodically executes a state monitoring process described below.
  • the management server 10 may execute the state monitoring process based on an instruction from the operator.
  • the management server 10 initializes the state change management table 116 (step S1401). Specifically, the following processing is executed.
  • the SLA compatibility determination unit 104 acquires the state management table 115 of the base system to be monitored.
  • the SLA suitability determination unit 104 generates the same number of entries as the entries included in the state management table 115 in the state change management table 116. Further, the SLA compatibility determination unit 104 sets the same identifier as the hypervisor ID 1001 to the hypervisor ID 1101 and sets the same identifier as the LU ID 1002 to the LU ID 1102. Further, the SLA suitability determination unit 104 sets “none” in the state change 1103 of all entries.
  • the management server 10 executes information acquisition processing for acquiring information related to I / O performance, path status, storage device status, and the like (step S1402).
  • the state change management table 116 is updated based on the acquisition process. Details of the information acquisition process will be described with reference to FIG.
  • the management server 10 executes a state change determination process (step S1403), and determines whether an event that triggers a change in the configuration of the infrastructure system has occurred (step S1404).
  • the SLA suitability determination unit 104 determines whether or not there is at least one entry for which “present” is set in the state change management table 116. If there is at least one entry for which “present” is set in the state change management table 116, the SLA suitability determination unit 104 determines that an event has occurred. Details of the state change determination process will be described with reference to FIG.
  • the management server 10 ends the process.
  • the management server 10 executes a virtual machine specifying process in order to specify the virtual machine 130 affected by the event (step S1405). Details of the virtual machine specifying process will be described with reference to FIG.
  • the management server 10 executes generation processing of the SLA conformity state management table 117 in order to generate the SLA conformity state management table 117 of the identified virtual machine 130 (step S1406). Details of the generation processing of the SLA conformity state management table 117 will be described with reference to FIG. If there are a plurality of virtual machines 130 identified in step S1405, the generation process of the SLA conformity state management table 117 is executed for each virtual machine 130.
  • the management server 10 executes SLA suitability determination processing for the identified SLA of the virtual machine 130 (step S1407). Details of the SLA suitability determination processing will be described with reference to FIG.
  • the management server 10 executes a selection process for selecting a movement target and a movement destination of the movement target based on the result of the SLA suitability determination process (step S1408). Details of the selection process will be described with reference to FIGS. 20A and 20B.
  • the management server 10 executes a movement process based on the results of the SLA suitability determination process and the selection process (step S1409). Details of the movement process will be described with reference to FIG.
  • the management server 10 determines whether or not the processing has been completed for all the virtual machines 130 identified in step S1405 (step S1410).
  • the migration unit 106 refers to the virtual machine arrangement management table 112 and determines whether there is an entry in which “undecided” is stored in the migration destination 705. If there is no entry in which “undecided” is stored in the migration destination 705, the migration unit 106 determines that the processing has been completed for all the virtual machines 130 identified in step S1405.
  • step S1405 When it is determined that the processing has not been completed for all the virtual machines 130 identified in step S1405, the management server 10 returns to step S1407 and executes the same processing.
  • the management server 10 ends the processing.
  • step S1401 to step S1410 When there are a plurality of state change management tables 116, that is, when there are a plurality of infrastructure systems on the computer system, the processing from step S1401 to step S1410 is repeatedly executed for one state change management table 116.
  • FIG. 15 is a flowchart illustrating an example of information acquisition processing executed by the management server 10 according to the first embodiment.
  • the information acquisition unit 101 of the management server 10 acquires various types of information from the physical server 20, the switch 30, and the storage device 40 (step S1501). Specifically, the following information is acquired.
  • the information acquisition unit 101 transmits a response time acquisition request to the hypervisor 120.
  • the hypervisor 120 transmits I / O information including the response time measured by the I / O performance measurement unit 121, the identifier of the hypervisor 120, the identifier of the virtual machine 130, the identifier of the LU 150, and the like to the information acquisition unit 101.
  • the information acquisition unit 101 transmits a path information acquisition request to the hypervisor 120.
  • the hypervisor 120 transmits information including the path information managed by the path management unit 122, the identifier of the virtual machine 130, and the identifier of the LU 150 to the information acquisition unit 101.
  • the path information includes information indicating a connection state between the physical server 20 and the storage device 40, a path configuration, and the like.
  • the information acquisition unit 101 transmits a firmware version acquisition request to the controller management unit 140.
  • the controller management unit 140 transmits storage information including the identifier of the storage device 40, the identifier of the controller 400, and the firmware version to the information acquisition unit 101. The above is the description of step S1501.
  • the information acquisition unit 101 of the management server 10 generates the state management table 115 based on the acquired information (step S1502), and then ends the process. Specifically, the following processing is executed.
  • the information acquisition unit 101 refers to the path management table 114 before update, and creates the same number of entries as the number of paths in the state management table 115.
  • the information acquisition unit 101 sets values stored in the hypervisor ID 901 and the LU ID 904 in the hypervisor ID 1001 and the LU ID 1002 of the generated entry.
  • the information acquisition unit 101 refers to the requirements of the SLA management table 111 and generates columns of “connection”, “redundancy”, “firmware version”, and “response time” for each hypervisor 120 entry of the monitoring item 1003 To do.
  • the information acquisition unit 101 temporarily stores the path management table 114 before update as a log.
  • the information acquisition unit 101 updates the path management table 114 based on the acquired path information.
  • the information acquisition unit 101 compares the path management table 114 before update with the path management table 114 after update, and confirms the physical connection state between the physical server 20 and the storage apparatus 40.
  • the information acquisition unit 101 When the physical server 20 and the storage device 40 are not normally connected, for example, when a path is deleted, the information acquisition unit 101 performs all the operations corresponding to the hypervisor 120 operating on the physical server 20. “False” is set in the “connection” of the entry. Further, the information acquisition unit 101 sets “false” to “redundancy” of all the entries.
  • the information acquisition unit 101 sets “true” to “connection” of all entries corresponding to the hypervisor 120 operating on the physical server 20. Set. Furthermore, the information acquisition unit 101 determines whether a redundant path is set between the physical server 20 and the storage device 40 based on the updated path management table 114.
  • the information acquisition unit 101 When a redundant path is set between the physical server 20 and the storage device 40, the information acquisition unit 101 performs “redundancy” of all entries corresponding to the hypervisor 120 operating on the physical server 20. “True” is set in. On the other hand, when a redundant path is not set between the physical server 20 and the storage device 40, the information acquisition unit 101 displays “redundancy” of all entries corresponding to the hypervisor 120 operating on the physical server 20. “False” is set in “Sex”.
  • the information acquisition unit 101 refers to the storage management table 113 based on the identifier of the storage device 40 included in the storage information, and identifies the LU 150 to be updated. That is, the information acquisition unit 101 searches for an entry in which the storage apparatus ID 801 matches the identifier of the storage apparatus 40 included in the storage information. The information acquisition unit 101 refers to the LU ID 804 of the searched entry to identify the entry for which the “firmware version” value is set.
  • the information acquisition unit 101 determines whether or not the firmware versions of the plurality of controllers 400 included in one storage device 40 match based on the identifier and firmware version of the controller 400 included in the storage information.
  • the information acquisition unit 101 sets “false” to “firmware version” of the searched entry.
  • the information acquisition unit 101 sets “true” to “firmware version” of the searched entry.
  • the information acquisition unit 101 searches for an entry whose hypervisor ID 1001 and LU ID 1002 match the identifier of the hypervisor 120 and the identification of the LU 150 included in the I / O information.
  • the information acquisition unit 101 sets the response time included in the I / O information in the “response time” of the searched entry.
  • the state management table 115 as shown in FIG. 10 is generated.
  • the status management table 115 is provided with information such as the generated time. Thereby, the management server 10 can manage the state management table 115 as a history.
  • FIG. 16 is a flowchart illustrating an example of the information change determination process executed by the management server 10 according to the first embodiment.
  • the state monitoring unit 102 acquires the latest state management table 115 and the state management table 115 that is the previous generation from the latest state management table 115 (step S1601).
  • the state management table 115 of the previous generation is also referred to as the past state management table 115.
  • the state monitoring unit 102 selects an entry to be compared (step S1602).
  • the comparison is performed on a path basis.
  • the state monitoring unit 102 determines whether or not the I / O performance has changed (step S1603). For example, the following processing is executed.
  • the state monitoring unit 102 acquires a value from the “response time” of the selected entry in the latest state management table 115. In addition, the state monitoring unit 102 acquires values from the past state management table 115 in the same manner.
  • the state monitoring unit 102 determines whether or not the value acquired from the latest state management table 115 has changed more than twice the value acquired from the past state management table 115.
  • the above is an example of the process of step S1604. In addition, it is not limited to the determination method mentioned above.
  • the state monitoring unit 102 searches for an entry that matches the hypervisor ID 1001 and LU ID 1002 of the entry in which the hypervisor ID 1101 and the LU ID 1102 are selected, and “Present” is set in the state change 1103 (step S1604). Thereafter, the state monitoring unit 102 proceeds to step S1605.
  • step S1605 the state monitoring unit 102 determines whether or not the path redundancy state has changed. For example, the following processing is executed.
  • the state monitoring unit 102 acquires a value from each of “connection” and “redundancy” of the selected entry of the latest state management table 115.
  • the state monitoring unit 102 also acquires values from the past state management table 115 in the same manner.
  • the state monitoring unit 102 determines whether or not the value of “connection” has changed from “false” to “true”, or from “true” to “false”. Further, the state monitoring unit 102 determines whether or not the value of “redundancy” has changed from “false” to “true”, or from “true” to “false”.
  • the state monitoring unit 102 determines that the path redundancy state has changed. For example, when the value acquired from “connection” has not changed, but the value acquired from “redundancy” has changed from “true” to “false”, the state monitoring unit 102 determines the redundancy of the path. It is determined that the sex state has changed.
  • step S1607 the state monitoring unit 102 searches for an entry that matches the hypervisor ID 1001 and LU ID 1002 of the entry in which the hypervisor ID 1101 and the LU ID 1102 are selected. “Present” is set in the entry status change 1103 (step S1606). Thereafter, the state monitoring unit 102 proceeds to step S1607. If “presence” is already stored, the process of step S1606 may be omitted.
  • the state monitoring unit 102 determines whether or not the firmware version state of the controller 400 has changed (step S1607). For example, the following processing is executed.
  • the state monitoring unit 102 acquires a value from “firmware version” of the selected entry in the latest state management table 115. In addition, the state monitoring unit 102 acquires values from the past state management table 115 in the same manner.
  • the state monitoring unit 102 determines whether or not the value of “firmware version” has changed from “false” to “true”, or from “true” to “false”. If the value of “firmware version” has changed, the state monitoring unit 102 determines that the path redundancy state has changed.
  • the above is an example of the process of step S1607.
  • step S1609 the state monitoring unit 102 searches for an entry that matches the hypervisor ID 1001 and LU ID 1002 of the entry in which the hypervisor ID 1101 and the LU ID 1102 are selected. “Present” is set in the entry status change 1103 (step S1608). Thereafter, the state monitoring unit 102 proceeds to step S1609. If “presence” is already stored, the process of step S1608 may be omitted.
  • the state monitoring unit 102 determines whether or not the processing has been completed for all the LUs 150, that is, all the entries in the state management table 115 (step S1609).
  • the status monitoring unit 102 returns to step S1602 and executes similar processing.
  • the state monitoring unit 102 ends the processing.
  • FIG. 17 is a flowchart illustrating an example of the virtual machine specifying process executed by the management server 10 according to the first embodiment.
  • the target selection unit 103 refers to the state change management table 116 and identifies the affected hypervisor 120 (step S1701).
  • the influence hypervisor 120 indicates the hypervisor 120 that is affected by the state change of each item corresponding to the monitoring item 1003.
  • the target selection unit 103 refers to the state change management table 116 and searches for an entry in which “present” is stored in the state change 1103.
  • the hypervisor 120 corresponding to the hypervisor ID 1101 of the entry in which “present” is stored is identified as the influence hypervisor 120.
  • the target selection unit 103 refers to the virtual machine arrangement management table 112 based on the identifier of the influence hypervisor 120, identifies the influence virtual machine 130 (step S1702), and updates the entry of the influence virtual machine 130 ( Step S1703).
  • the affected virtual machine 130 refers to the virtual machine 130 operating on the affected hypervisor 120.
  • the target selection unit 103 searches for an entry that matches the hypervisor ID 1101 of the entry for which the hypervisor ID 702 has been searched. Further, the target selection unit 103 sets “undecided” as the movement destination 705 of the searched entry.
  • FIG. 18 is a flowchart for explaining an example of the generation process of the SLA conformity state management table 117 executed by the management server 10 according to the first embodiment.
  • the SLA suitability determination unit 104 refers to the virtual machine arrangement management table 112 and selects one affected virtual machine 130 (step S1801).
  • the SLA suitability determination unit 104 selects one entry from entries whose destination 705 is “undecided”. At this time, the SLA conformity determination unit 104 generates an empty SLA conformity state management table 117 corresponding to the selected affected virtual machine 130.
  • the SLA conformity determination unit 104 generates an entry in the SLA conformity state management table 117 with reference to the state management table 115 (step S1802).
  • the SLA conformity determination unit 104 generates the same number of entries as the entries included in the state management table 115 in the SLA conformance state management table 117.
  • the SLA compatibility determination unit 104 sets values corresponding to the hypervisor ID 1001 and the LU ID 1002 in the hypervisor ID 1201 and the LU ID 1202 of the generated entry.
  • the SLA suitability determination unit 104 refers to the SLA management table 111, acquires the SLA requirement of the selected affected virtual machine 130, and sets it as the requirement 1203 of the entry of each hypervisor 120 (step S1803). .
  • the SLA suitability determination unit 104 acquires a column name corresponding to the SLA requirement in the SLA management table 111.
  • the SLA conformity determination unit 104 generates as many columns as the number of column names acquired in the requirement 1203. Furthermore, the SLA compatibility determination unit 104 sets the acquired column name for each generated column.
  • the SLA suitability determination unit 104 determines whether or not the processing has been completed for all affected virtual machines 130 (step S1804).
  • the SLA suitability determination unit 104 If it is determined that the processing has not been completed for all affected virtual machines 130, the SLA suitability determination unit 104 returns to step S1801 and executes the same processing. When it is determined that the processing has been completed for all the affected virtual machines 130, the SLA suitability determination unit 104 ends the processing.
  • the management server 10 manages the affected virtual machine 130 and the SLA conformity state management table 117 in association with each other.
  • FIG. 19 is a flowchart illustrating an example of the SLA suitability determination process executed by the management server 10 according to the first embodiment.
  • the SLA suitability determination unit 104 refers to the virtual machine arrangement management table 112 and selects one affected virtual machine 130 (step S1901).
  • the process of step S1901 is the same as the process of step S1801.
  • the SLA conformity determination unit 104 acquires the SLA conformity state management table 117 of the selected affected virtual machine 130.
  • the SLA conformity determination unit 104 compares the SLA management table 111 and the latest state management table 115 (step S1902), and updates the SLA conformity state management table 117 based on the comparison result (step S1903). Specifically, the following processing is executed.
  • the SLA compatibility determination unit 104 searches for an entry in which the virtual machine ID 601 in the SLA management table 111 matches the identifier (virtual machine ID 701) of the affected virtual machine 130.
  • the SLA suitability determination unit 104 acquires the values of the redundancy 602, firmware version 603, and response time 604 of the searched entry.
  • the SLA suitability determination unit 104 selects a requirement to be compared.
  • the SLA suitability determination unit 104 selects one entry from the state management table 115, and acquires a column value related to the requirement for which the monitoring item 1003 of the selected entry is selected.
  • the SLA suitability determination unit 104 determines whether or not the selected requirement is satisfied based on the acquired value.
  • the SLA compatibility determination unit 104 searches for an entry that matches the hypervisor ID 1001 and LU ID 1002 of the entry for which the hypervisor ID 1201 and the LU ID 1202 are selected.
  • the SLA suitability determination unit 104 sets “OK” in the column corresponding to the selected requirement of the searched entry.
  • the SLA suitability determination unit 104 searches for an entry that matches the hypervisor ID 1001 and LU ID 1002 of the entry in which the hypervisor ID 1201 and the LU ID 1202 are selected.
  • the SLA suitability determination unit 104 sets “NG” in the column corresponding to the selected requirement of the searched entry.
  • the SLA suitability determination unit 104 sets “OK” to “redundancy” of an entry whose hypervisor ID 1201 is “hypervisor 1” and LU ID 1202 is “LU1”. Further, the “redundancy” of the entry in which the hypervisor ID 1001 is “hypervisor 2” and the LU ID 1002 is “LU1” is “false”. Therefore, the SLA suitability determination unit 104 sets “NG” to “redundancy” of an entry whose hypervisor ID 1201 is “hypervisor 1” and LU ID 1202 is “LU1”.
  • the SLA suitability determination unit 104 repeatedly executes the same processing for all SLA requirements. The above is the description of the processing in steps S1902 and S1903.
  • the SLA suitability determination unit 104 determines whether or not processing has been completed for all affected virtual machines 130 (step S1904).
  • the SLA suitability determination unit 104 If it is determined that the processing has not been completed for all affected virtual machines 130, the SLA suitability determination unit 104 returns to step S1901 and executes the same processing. When it is determined that the processing has been completed for all the affected virtual machines 130, the SLA suitability determination unit 104 ends the processing.
  • 20A and 20B are flowcharts illustrating an example of a selection process executed by the management server 10 according to the first embodiment.
  • step S2002 to step S2007 is processing for searching for a movement destination that is a movement target that satisfies all the SLA requirements.
  • processing from step S2010 to step S2015 is processing for searching for a destination to be moved that satisfies some SLA requirements.
  • the migration destination selection unit 105 refers to the virtual machine arrangement management table 112 and selects one affected virtual machine 130 (step S2001).
  • the process in step S2001 is the same as the process in step S1801.
  • the migration destination selection unit 105 acquires the SLA conformity state management table 117 of the selected affected virtual machine 130. Further, the migration destination selection unit 105 acquires an identifier from the hypervisor ID 702 and LU ID 704 of the entry corresponding to the selected affected virtual machine 130 in the virtual machine arrangement management table 112.
  • the migration destination selection unit 105 acquires the values of the redundancy 602, firmware version 603, and response time 604 of the entry corresponding to the affected virtual machine 130 from the SLA management table 111.
  • the destination selection unit 105 identifies the essential SLA requirement based on the acquired value. In other words, the destination selection unit 105 identifies the requirement for which “must” is set.
  • the movement destination selection unit 105 selects a movement target and searches for a movement target movement destination. Specifically, the migration destination selection unit 105 first selects the affected virtual machine 130 as a migration target, and searches for the physical server 20 (hypervisor 120) that is the migration destination of the affected virtual machine 130 based on SLA requirements. To do. If the migration destination of the virtual machine 130 does not exist, the migration destination selection unit 105 selects the virtual drive 160 as a migration target, and searches for the migration destination LU 150 of the virtual drive 160 based on the SLA requirements.
  • the migration destination selection unit 105 selects the affected virtual machine 130 and the virtual drive 160 as a migration target, and selects each of the affected virtual machine 130 and the virtual drive 160 based on the SLA requirements. Search the destination.
  • the movement target is selected in the order of decreasing load such as the amount of data to be moved and the movement time of the data. That is, the migration destination selection unit 105 first selects the affected virtual machine 130 as the movement target, second selects the virtual drive 160 as the movement target, and thirdly selects the affected virtual machine 130 and the virtual drive 160 as the movement target. Choose as. Since the data amount of the virtual machine 130 is smaller than the data amount of the virtual drive 160 and the movement time is short, the virtual machine 130 is first selected as a movement target. Note that the order of selection of the movement target is not limited to that described above.
  • the migration destination selection unit 105 selects the selected affected virtual machine 130 as a migration target, and determines whether there is a physical server 20 that satisfies all the SLA requirements based on the SLA conformity state management table 117. (Step S2002). Specifically, the following processing is executed.
  • the migration destination selection unit 105 searches for an entry in which the hypervisor ID 1201 is different from the identifier acquired from the hypervisor ID 702 and the LU ID 1202 matches the identifier acquired from the LU ID 704. That is, the hypervisor 120 that shares the LU 150 with the affected hypervisor 120 is identified. In the following description, the hypervisor 120 sharing the LU 150 with the affected hypervisor 120 is also referred to as a candidate hypervisor 120.
  • the destination selection unit 105 selects one candidate hypervisor 120.
  • the destination selection unit 105 determines whether all the values of the requirement 1203 of the entry corresponding to the selected candidate hypervisor 120 are “OK”. When all the values of the entry requirement 1203 are “OK”, the migration destination selection unit 105 determines that there is a physical server 20 that satisfies all the SLA requirements. The destination selection unit 105 performs the same determination for all candidate hypervisors 120.
  • the migration destination selection unit 105 proceeds to step S2004.
  • the migration destination selection unit 105 determines whether the affected virtual machine 130 can be migrated to the physical server 20 on which the retrieved candidate hypervisor 120 is operating. (Step S2003).
  • the determination process in step S2003 may use a known determination method. For example, the migration destination selection unit 105 determines whether or not resources necessary for the affected virtual machine 130 can be secured. When there are a plurality of physical servers 20 to which the affected virtual machine 130 can be moved, the migration destination selection unit 105 selects one physical server 20 based on a predetermined policy. For example, a method of selecting the physical server 20 having the largest amount of free resources or the physical server 20 having the lowest processing load can be considered.
  • the movement destination selection unit 105 proceeds to step S2004.
  • the migration destination selection unit 105 moves the entry corresponding to the affected virtual machine 130 in the virtual machine arrangement management table 112.
  • the destination 705 is updated to “determined” (step S2008).
  • the movement destination selection unit 105 proceeds to step S2009.
  • the migration destination selection unit 105 generates a migration instruction including the identifier of the affected virtual machine 130 and the identifier of the hypervisor 120 on the migration destination physical server 20.
  • the migration destination selection unit 105 selects the virtual drive 160 of the affected virtual machine 130 as a migration target, and determines whether there is an LU 150 that satisfies all the SLA requirements based on the SLA conformity state management table 117. (Step S2004). Specifically, the following processing is executed.
  • the migration destination selection unit 105 searches for an entry in which the hypervisor ID 1201 matches the identifier acquired from the hypervisor ID 702 and the LU ID 1202 is different from the identifier acquired from the LU ID 704. That is, the LU 150 accessible by the influence hypervisor 120 is specified. More specifically, the LU 150 to which the path is set is specified. In the following description, the LU 150 accessible by the influence hypervisor 120 is also referred to as a candidate LU 150.
  • the migration destination selection unit 105 selects one candidate LU 150.
  • the migration destination selection unit 105 determines whether all the values of the requirement 1203 of the entry corresponding to the selected candidate LU 150 are “OK”. When the values of the entry requirement 1203 are all “OK”, the migration destination selection unit 105 determines that there is an LU 150 that satisfies all the SLA requirements. Note that the migration destination selection unit 105 performs the same determination for all candidate LUs 150.
  • the migration destination selection unit 105 proceeds to step S2006.
  • the migration destination selection unit 105 determines whether the virtual drive 160 of the affected virtual machine 130 can be migrated to the retrieved LU 150 (step S2005).
  • the determination process in step S2005 may use a known determination method. For example, the migration destination selection unit 105 determines whether or not the necessary resources for the virtual drive 160 can be secured. If there are a plurality of LUs 150 to which the virtual drive 160 can be moved, the migration destination selection unit 105 selects one LU 150 based on a predetermined policy. For example, a method of selecting the LU 150 having the largest free resource amount can be considered.
  • the migration destination selection unit 105 proceeds to step S2006.
  • the migration destination selection unit 105 sets the migration destination 705 of the entry corresponding to the affected virtual machine 130 in the virtual machine arrangement management table 112 as “ It is updated to “determined” (step S2008). Thereafter, the movement destination selection unit 105 proceeds to step S2009. At this time, the migration destination selection unit 105 generates a migration instruction including an identifier of the affected virtual machine 130, an identifier of the virtual drive 160 of the affected virtual machine 130, an identifier of the migration destination LU 150, and the like.
  • the migration destination selection unit 105 selects the affected virtual machine 130 and the virtual drive 160 of the affected virtual machine 130 as a migration target, and the physical server 20 that satisfies all the SLA requirements based on the SLA conformity state management table 117 and It is determined whether or not a combination of LUs 150 exists (step S2006). Specifically, the following processing is executed.
  • the migration destination selection unit 105 extracts an entry in which the hypervisor ID 1201 is different from the identifier acquired from the hypervisor ID 702, and the LU ID 1202 is different from the identifier acquired from the LU ID 704.
  • the destination selection unit 105 selects one entry from the extracted entries.
  • the destination selection unit 105 determines whether all the values of the requirement 1203 of the selected entry are “OK”. When all the values of the entry requirement 1203 are “OK”, the migration destination selection unit 105 determines that there is a combination of the physical server 20 and the LU 150 that satisfies all the SLA requirements. Note that the destination selection unit 105 performs the same determination for all the extracted entries.
  • the migration destination selection unit 105 proceeds to step S2010.
  • the migration destination selection unit 105 moves the affected virtual machine 130 to the retrieved physical server 20 and the retrieved LU 150. It is determined whether or not the virtual drive 160 of the virtual machine 130 can be moved (step S2007). Note that the process of step S2007 may be a combination of the processes of step S2003 and step S2005.
  • the migration destination selection unit 105 proceeds to step S 2010. move on.
  • the move destination selecting unit 105 105 updates the migration destination 705 of the entry corresponding to the affected virtual machine 130 in the virtual machine arrangement management table 112 to “determined” (step S2008). Thereafter, the movement destination selection unit 105 proceeds to step S2009. At this time, the migration destination selection unit 105 obtains the identifier of the affected virtual machine 130, the identifier of the virtual drive 160 of the affected virtual machine 130, the identifier of the hypervisor 120 on the migration destination physical server 20, the identifier of the migration destination LU 150, and the like. Generate a move instruction containing.
  • step S2009 it is determined whether or not processing has been completed for all affected virtual machines 130 (step S2009).
  • the migration destination selection unit 105 If it is determined that processing has not been completed for all affected virtual machines 130, the migration destination selection unit 105 returns to step S2001 and executes similar processing. When it is determined that the processing has been completed for all affected virtual machines 130, the migration destination selection unit 105 ends the processing.
  • step S2006 When the determination result in step S2006 is NO or the determination result in step S2007 is NO, there is no movement target movement destination that satisfies all the SLA requirements. Therefore, the movement destination selection unit 105 searches for a movement target movement destination that satisfies at least essential requirements.
  • step S2006 determines whether there is a physical server 20 that satisfies the SLA requirement.
  • step S2010 determines whether there is a physical server 20 that satisfies the SLA requirement.
  • the destination selection unit 105 identifies the candidate hypervisor 120 by executing the same processing as in step S2002.
  • the destination selection unit 105 selects one target candidate hypervisor 120.
  • the destination selection unit 105 determines whether or not the required requirement value of the requirement 1203 of the entry corresponding to the selected candidate hypervisor 120 is “OK”. If the required requirement value of the entry requirement 1203 is “OK”, the migration destination selection unit 105 determines that there is a physical server 20 that satisfies some SLA requirements.
  • the destination selection unit 105 performs the same determination for all candidate hypervisors 120.
  • the migration destination selection unit 105 proceeds to step S2012.
  • the migration destination selection unit 105 determines whether or not the affected virtual machine 130 can be migrated to the physical server 20 on which the searched candidate hypervisor 120 is operating. Determination is made (step S2011).
  • the process in step S2011 is the same as the process in step S2003.
  • the migration destination selection unit 105 selects one physical server 20 based on a predetermined policy. For example, a method of selecting the physical server 20 having the largest amount of free resources or the physical server 20 having the lowest processing load can be considered. In addition, a method may be considered in which the migration destination selection unit 105 assigns priorities to requirements other than the essential requirements, and selects the physical server 20 that satisfies the requirements given the priorities with higher priorities.
  • the migration destination selection unit 105 proceeds to step S2012.
  • the migration destination selection unit 105 moves the entry corresponding to the affected virtual machine 130 in the virtual machine arrangement management table 112.
  • the destination 705 is updated to “determined” (step S2017).
  • the movement destination selection unit 105 proceeds to step S2009.
  • the migration destination selection unit 105 generates a migration instruction including the identifier of the affected virtual machine 130 and the identifier of the hypervisor 120 on the migration destination physical server 20.
  • the migration destination selection unit 105 selects the virtual drive 160 of the affected virtual machine 130 as a migration target, and determines whether there is an LU 150 that satisfies some SLA requirements based on the SLA conformity state management table 117. Determination is made (step S2012). Specifically, the following processing is executed.
  • the migration destination selection unit 105 identifies the candidate LU 150 by executing the same processing as in step S2004.
  • the migration destination selection unit 105 selects one candidate LU 150.
  • the migration destination selection unit 105 determines whether or not the required requirement value of the requirement 1203 of the entry corresponding to the selected candidate LU 150 is “OK”. If the required requirement value of the entry requirement 1203 is “OK”, the migration destination selection unit 105 determines that there is an LU 150 that satisfies some SLA requirements. Note that the migration destination selection unit 105 performs the same determination for all candidate LUs 150.
  • the migration destination selection unit 105 proceeds to step S2014.
  • the migration destination selection unit 105 determines whether the virtual drive 160 of the affected virtual machine 130 can be migrated to the retrieved LU 150 (step S2013). .
  • step S2013 is the same as the process of step S2005. If there are a plurality of LUs 150 to which the virtual drive 160 can be moved, the migration destination selection unit 105 selects one LU 150 based on a predetermined policy. For example, a method of selecting the LU 150 having the largest free resource amount can be considered. In addition, the migration destination selection unit 105 may assign a priority to SLA requirements other than the essential SLA requirements, and select an LU 150 that satisfies the SLA requirement to which a higher priority is assigned. It is done.
  • the migration destination selection unit 105 proceeds to step S2014.
  • the migration destination selection unit 105 sets the migration destination 705 of the entry corresponding to the affected virtual machine 130 in the virtual machine arrangement management table 112 as “ Update to “determined” (step S2017). Thereafter, the movement destination selection unit 105 proceeds to step S2009. At this time, the migration destination selection unit 105 generates a migration instruction including an identifier of the affected virtual machine 130, an identifier of the virtual drive 160 of the affected virtual machine 130, an identifier of the migration destination LU 150, and the like.
  • the migration destination selection unit 105 selects the affected virtual machine 130 and the virtual drive 160 of the affected virtual machine 130 as migration targets, and the physical server 20 that satisfies some SLA requirements based on the SLA conformity state management table 117. And whether or not there is a combination of LU 150 (step S2014). Specifically, the following processing is executed.
  • the migration destination selection unit 105 extracts an entry in which the hypervisor ID 1201 is different from the identifier acquired from the hypervisor ID 702, and the LU ID 1202 is different from the identifier acquired from the LU ID 704.
  • the destination selection unit 105 selects one entry from the extracted entries.
  • the destination selection unit 105 determines whether or not the required requirement value of the requirement 1203 of the selected entry is “OK”. When the requirement value of the requirement 1203 of the selected entry is “OK”, the migration destination selection unit 105 determines that there is a combination of the physical server 20 and the LU 150 satisfying some SLA requirements. . Note that the destination selection unit 105 performs the same determination for all the extracted entries.
  • the migration destination selection unit 105 moves the migration destination 705 of the entry corresponding to the affected virtual machine 130 in the virtual machine arrangement management table 112. Is updated to “determined” (step S2016). Thereafter, the movement destination selection unit 105 proceeds to step S2009.
  • the migration destination selection unit 105 moves the affected virtual machine 130 to the retrieved physical server 20 and is retrieved. It is determined whether or not the virtual drive 160 of the affected virtual machine 130 can be moved to the LU 150 (step S2015).
  • step S2015 may be a combination of the processes of step S2011 and step S2013.
  • the destination selection unit 105 assigns points to the SLA requirements other than the essential SLA requirements, and based on the total value of the points assigned to the satisfied SLA requirements.
  • a method of selecting the LU 150 can be considered.
  • the migration destination selection unit 105 When it is determined that at least one of the affected virtual machine 130 or the virtual drive 160 of the affected virtual machine 130 cannot be migrated to the retrieved physical server 20, the migration destination selection unit 105 performs virtual machine placement.
  • the migration destination 705 of the entry corresponding to the affected virtual machine 130 in the management table 112 is updated to “determined” (step S2016). Thereafter, the movement destination selection unit 105 proceeds to step S2009.
  • the migration destination selection unit 105 When it is determined that the affected virtual machine 130 is moved to the retrieved physical server 20 and the virtual drive 160 of the affected virtual machine 130 can be moved to the retrieved LU 150, the migration destination selection unit 105 performs virtual machine placement management.
  • the migration destination 705 of the entry corresponding to the affected virtual machine 130 in the table 112 is updated to “determined” (step S2017). Thereafter, the movement destination selection unit 105 proceeds to step S2009.
  • the migration destination selection unit 105 obtains the identifier of the affected virtual machine 130, the identifier of the virtual drive 160 of the affected virtual machine 130, the identifier of the hypervisor 120 on the migration destination physical server 20, the identifier of the migration destination LU 150, and the like. Generate a move instruction containing.
  • the migration destination selection unit 105 may output an error notification including the identifier of the virtual machine 130 and the like.
  • the management server 10 searches for a destination that satisfies at least the required SLA requirements. Further, by simultaneously moving the virtual machine 130 and the virtual drive 160, the physical server 20 that does not share the LU 150 with the physical server 20 of the migration source can be selected as the physical server 20 of the migration destination.
  • FIG. 21 is a flowchart illustrating an example of the movement process executed by the management server 10 according to the first embodiment.
  • the movement unit 106 moves the movement target to the movement destination device based on the movement instruction generated by the movement destination selection unit 105 (step S2101). Thereafter, the moving unit 106 ends the process.
  • firmware version 603 is set as an indispensable requirement.
  • the virtual machine 130 and the virtual drive 160 are migration targets, and there are no physical servers 20 and LUs 150 that satisfy all the SLA requirements.
  • the firmware of the controllers 400 is updated one by one. At this time, an event occurs because the firmware versions do not match.
  • the management server 10 searches for the LU 150 managed by the storage device 40 having at least the same firmware version of the controller 400, and searches for the physical server 20 on which the hypervisor 120 that can access the LU 150 is operating.
  • the management server 10 moves the virtual machine 130 to the searched hypervisor 120 and moves the virtual drive 160 to the searched LU 150.
  • the management server 10 avoids dangers such as stoppage of the infrastructure system by selecting the physical server 20 or LU 150 that satisfies some requirements as the migration destination of the virtual machine 130 or virtual drive 160. can do.
  • the occurrence of a serious failure can be avoided by moving the resource to a destination that satisfies the essential requirements.
  • redundancy as a factor for determining an SLA violation
  • indirect monitoring can be performed. For example, an SLA violation caused by a direct factor can be avoided in advance by a failure that occurs due to loss of redundancy.
  • the physical server 20 that does not share the LU 150 can also be selected as the physical server 20 to be moved. Therefore, computer resources can be used effectively.
  • this invention is not limited to the above-mentioned Example, Various modifications are included. Further, for example, the above-described embodiments are described in detail for easy understanding of the present invention, and are not necessarily limited to those provided with all the described configurations. Further, a part of the configuration of each embodiment can be added to, deleted from, or replaced with another configuration.
  • each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit.
  • the present invention can also be realized by software program codes that implement the functions of the embodiments.
  • a storage medium in which the program code is recorded is provided to the computer, and a CPU included in the computer reads the program code stored in the storage medium.
  • the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code itself and the storage medium storing it constitute the present invention.
  • Examples of storage media for supplying such program codes include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs (Solid State Drives), optical disks, magneto-optical disks, CD-Rs, magnetic tapes, A non-volatile memory card, ROM, or the like is used.
  • program code for realizing the functions described in this embodiment can be implemented by a wide range of programs or script languages such as assembler, C / C ++, Perl, Shell, PHP, Java, and the like.
  • the program code is stored in a storage means such as a hard disk or memory of a computer or a storage medium such as a CD-RW or CD-R.
  • the CPU included in the computer may read and execute the program code stored in the storage unit or the storage medium.
  • control lines and information lines indicate those that are considered necessary for the explanation, and do not necessarily indicate all the control lines and information lines on the product. All the components may be connected to each other.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Hardware Redundancy (AREA)
  • Debugging And Monitoring (AREA)

Abstract

L'invention concerne un ordinateur de gestion pour gérer un système informatique comprenant un ordinateur et un dispositif de stockage, l'ordinateur ayant une unité de gestion de virtualisation pour gérer une machine virtuelle, le dispositif de stockage ayant une unité de gestion de dispositif de commande pour gérer une zone de stockage logique. Sur le système informatique, un système de base constitué de la machine virtuelle, de la zone de stockage logique et d'un chemin est construit, et l'ordinateur de gestion conserve des informations de gestion de qualité de service pour gérer la qualité de service du système de base comprenant une pluralité de types d'exigences, et a une unité d'obtention d'informations pour obtenir des informations concernant les performances et la configuration, une unité de surveillance d'état pour surveiller l'état du système informatique correspondant à des éléments de surveillance pour chaque chemin, une unité de sélection de cible pour sélectionner la machine virtuelle, dont la qualité de service n'est pas satisfaite, une unité de détermination de conformité pour générer, pour chaque chemin, des informations de gestion d'état de conformité pour gérer les états de conformité de la pluralité d'exigences établies pour la machine virtuelle, et une unité de sélection de destination de déplacement pour sélectionner une destination de déplacement d'une ressource qui satisfait au moins une exigence sur la base des informations de gestion d'état de conformité.
PCT/JP2015/067482 2015-06-17 2015-06-17 Ordinateur de gestion, procédé de gestion de déplacement de ressource et système informatique Ceased WO2016203580A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2015/067482 WO2016203580A1 (fr) 2015-06-17 2015-06-17 Ordinateur de gestion, procédé de gestion de déplacement de ressource et système informatique

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2015/067482 WO2016203580A1 (fr) 2015-06-17 2015-06-17 Ordinateur de gestion, procédé de gestion de déplacement de ressource et système informatique

Publications (1)

Publication Number Publication Date
WO2016203580A1 true WO2016203580A1 (fr) 2016-12-22

Family

ID=57545724

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2015/067482 Ceased WO2016203580A1 (fr) 2015-06-17 2015-06-17 Ordinateur de gestion, procédé de gestion de déplacement de ressource et système informatique

Country Status (1)

Country Link
WO (1) WO2016203580A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110895491A (zh) * 2018-09-12 2020-03-20 株式会社日立制作所 辅助资源分配优化的系统和方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013045444A (ja) * 2011-08-19 2013-03-04 Hitachi Ltd データセンタ内のリソースの使用効率を改善するための方法及び装置
JP2014510316A (ja) * 2011-05-31 2014-04-24 株式会社日立製作所 計算機システム及びそのイベント通知方法
JP2014134904A (ja) * 2013-01-09 2014-07-24 Fujitsu Ltd 仮想マシン管理プログラム及びその方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2014510316A (ja) * 2011-05-31 2014-04-24 株式会社日立製作所 計算機システム及びそのイベント通知方法
JP2013045444A (ja) * 2011-08-19 2013-03-04 Hitachi Ltd データセンタ内のリソースの使用効率を改善するための方法及び装置
JP2014134904A (ja) * 2013-01-09 2014-07-24 Fujitsu Ltd 仮想マシン管理プログラム及びその方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110895491A (zh) * 2018-09-12 2020-03-20 株式会社日立制作所 辅助资源分配优化的系统和方法

Similar Documents

Publication Publication Date Title
US12488020B2 (en) Resource management systems and methods
US9608933B2 (en) Method and system for managing cloud computing environment
US7305520B2 (en) Storage system with capability to allocate virtual storage segments among a plurality of controllers
US10437642B2 (en) Management system for computer system
CN110955487A (zh) Hci环境下的vm/容器和卷配置决定方法及存储系统
US11188243B2 (en) Storage management apparatus, information system, and storage management method
US10990433B2 (en) Efficient distributed arrangement of virtual machines on plural host machines
JP2021064078A (ja) 複数のノードを含むストレージシステムの拡張構成案を作成する装置
US20220283722A1 (en) Volume Placement Based on Resource Use and Scoring Functions
US12086125B2 (en) Multiple volume placement based on resource usage and scoring functions
WO2016203580A1 (fr) Ordinateur de gestion, procédé de gestion de déplacement de ressource et système informatique
US12346571B2 (en) Storage system and storage node management method

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15895601

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15895601

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP