WO2016157274A1 - ストレージ管理計算機 - Google Patents
ストレージ管理計算機 Download PDFInfo
- Publication number
- WO2016157274A1 WO2016157274A1 PCT/JP2015/059536 JP2015059536W WO2016157274A1 WO 2016157274 A1 WO2016157274 A1 WO 2016157274A1 JP 2015059536 W JP2015059536 W JP 2015059536W WO 2016157274 A1 WO2016157274 A1 WO 2016157274A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- host computer
- storage
- information
- logical volume
- storage area
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
- G06F9/5016—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals the resource being the memory
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0604—Improving or facilitating administration, e.g. storage management
- G06F3/0605—Improving or facilitating administration, e.g. storage management by facilitating the interaction with a user or administrator
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/061—Improving I/O performance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0629—Configuration or reconfiguration of storage systems
- G06F3/0631—Configuration or reconfiguration of storage systems by allocating resources to storage systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0662—Virtualisation aspects
- G06F3/0665—Virtualisation aspects at area level, e.g. provisioning of virtual or logical volumes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/0671—In-line storage system
- G06F3/0683—Plurality of storage devices
- G06F3/0685—Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45579—I/O management, e.g. providing access to device drivers or storage
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45583—Memory management, e.g. access or allocation
Definitions
- the present invention relates to a computer system including a storage device, and more particularly to a storage area management technique in an environment where storage media are distributed and arranged.
- Patent Document 1 presents to a user information to be used for searching a storage area based on a user's operation history when allocating a storage area in order to support management of the storage area of a storage apparatus to be allocated to a host computer.
- a technique for allocating a volume searched based on presented information to a host computer is disclosed.
- server flash Flash Memory Drive
- the storage resource provided in the host computer and the storage resource provided in the storage computer are managed separately by each host management computer and storage management computer.
- the host management computer and the storage management computer do not share the management information of each other, it has been difficult to perform allocation utilizing the usage status of each storage area and the characteristics of the storage medium.
- server flash generally exhibits high I / O performance when the I / O access pattern is Random in the same manner as when operating in the storage apparatus, while operating in the storage apparatus. Compared with, the latency performance is excellent because there is no data communication overhead.
- Patent Document 1 when allocating storage areas, there is room for improvement in the storage resource management method because performance characteristics depending on the use of the storage medium and resources managed by the host management computer are not taken into consideration. .
- the present invention has an object to generate a configuration plan that realizes storage area allocation according to the access characteristics of a host computer based on the use status of storage resources of the host computer and the storage device.
- a management computer communicates with a host computer and a storage device, and includes a memory and a CPU.
- Configuration information including information on a plurality of storage media with different performances provided in the host computer and the storage device, and indicating the storage area provided by the storage medium and the host computer in association with each other is stored in the memory.
- the CPU receives a storage area allocation request to the host computer including information on the characteristics of access by the host computer and the capacity of the storage area to be allocated, the CPU refers to the configuration information, and stores the storage medium included in the storage apparatus and the host computer. Based on the access characteristics included in the request, select a storage medium that can provide a storage area of the requested capacity, and generate and output a configuration plan that allocates the storage area to the host computer from the selected storage medium .
- FIG. 1 shows an outline of the first embodiment.
- FIG. 2 illustrates the overall configuration of the computer system according to the first embodiment.
- FIG. 3 is a conceptual diagram of the host computer according to the first embodiment.
- FIG. 4 shows a host management computer according to the first embodiment.
- FIG. 5 illustrates a storage apparatus according to the first embodiment.
- FIG. 6 illustrates a storage management computer according to the first embodiment.
- FIG. 7 illustrates a server information table according to the first embodiment.
- FIG. 8 shows a storage volume table related to the first embodiment.
- FIG. 9 illustrates a storage pool table according to the first embodiment.
- FIG. 10 is a flowchart of the allocation resource determination process in the resource allocation plan generation program according to the first embodiment.
- FIG. 11 illustrates a volume tiering policy setting table according to the second embodiment.
- FIG. 12 shows a Tiering Policy table according to the second embodiment.
- FIG. 13 is an overall flowchart of the resource allocation plan generation program according to the third embodiment.
- various types of information may be described using the expression “aaa table”, but the various types of information may be expressed using a data structure other than a table. In order to show that it does not depend on the data structure, the “aaa table” can be called “aaa information”.
- a processor for example, CPU (Central Processing) included in the control device included in the computer. Unit) indicates that it is being executed.
- CPU Central Processing
- the processing is simply described with the storage device as the subject, it indicates that the controller included in the storage device is executing.
- control device and the controller may be the processor itself, or may include a hardware circuit that performs a part or all of the processing performed by the control device or the controller.
- the program may be installed in each computer or storage device from a program source.
- the program source may be, for example, a program distribution server or a storage medium.
- FIG. 1 is a diagram showing an outline of the first embodiment.
- the Memory 24 of the storage management computer 1 includes information on the storage medium installed in the host computer, information on the VM (Virtual Machine) 6, logical configuration information and performance information from the VM to the storage area of the storage device. Is stored.
- the storage apparatus 4 holds a physical device 52 (storage medium group) and stores information of the host computer 5 and the VM 6.
- the VM 6 operates on the host computer 5, and the VM 6 data is stored in the physical device 52.
- the resource allocation plan generation program 2 of the storage management computer 1 first receives the input of the capacity of the storage area to be allocated to the host computer 5 or the VM 6, the requested access pattern, and Read ratio information (access characteristics). Next, based on the performance characteristics based on the received information, the type of storage medium, and its arrangement, an area corresponding to the access characteristics is selected from the storage areas of the storage device or the host computer, and a resource allocation plan (configuration plan) is selected. Generate and output. And the process which sets the produced
- the server flash is a storage resource in the host computer and is managed separately from the server flash in other host computers.
- the storage apparatus is often shared between a plurality of host computers. For this reason, the administrator of the host computer (host management computer) and the administrator of the storage apparatus are generally different.
- the Flash Memory Drive (hereinafter referred to as “storage flash”) provided in the storage computer is used for workloads with a lot of I / O and workloads with a lot of read requests in order to improve the performance of the entire system. It is preferable to preferentially allocate the high-performance storage resources.
- a storage flash allocation request can be made to the storage administrator without considering the balance of the entire system.
- read requests are concentrated on server flash because server flash is allocated, and workloads with very few read requests to storage and workloads with low I / O requests to storage because there are few write requests.
- situations such as allocating storage resources such as storage flash may occur.
- a situation may occur in which a storage flash is not allocated to a server that is not equipped with a server flash, resulting in an imbalance in allocated resources among tenants.
- the above-mentioned problems are solved, and storage area allocation is performed not only by resource management of the storage apparatus but also by utilizing the storage area usage status and storage medium characteristics of the host computer and the storage apparatus.
- FIG. 2 shows the overall configuration of the computer system according to the first embodiment.
- the computer system of this embodiment has a host computer 5 and a storage device 4.
- the host computer 5 and the storage device 4 are connected via a data network 15.
- the computer system further includes a host management computer 35 and a storage management computer 1.
- the host computer 5, the host management computer 35, the storage management computer 1, and the storage device 4 are connected via the management network 16.
- the data network 15 is, for example, a SAN (Storage Area Network), but may be an IP (Internet Protocol) network or a data communication network other than these.
- the management network 16 is, for example, an IP network, but may be a SAN or a data communication network other than these. Further, the data network 15 and the management network 16 may be the same network. Further, the host computer 5, the host management computer 35, and the storage management computer 1 may be the same computer.
- the host computer 5 includes a storage medium group 7, a control device such as a CPU (Central Processing Unit) 8, a storage device such as a Memory 9, a M-I / F (Management-Interface) 10, and a CI / F (Communication-Interface). 11 and I / O-I / F (I / O-Interface) 12.
- the host computer 5 may have an input / output device (keyboard, display device, etc.).
- the CPU 8 executes a program stored in the Memory 9.
- a CPU executes a program stored in a Memory connected to the CPU.
- the MI / F 10 is an interface with the management network 16 and transmits / receives data and control commands to / from the storage apparatus 4, the host management computer 35, and the storage management computer 1.
- the C-I / F 11 is an interface with the data network 15 and transmits / receives data and control commands to / from the storage apparatus 4.
- the I / O-I / F is an interface with the storage medium group 7 and transmits / receives data and control commands to / from the storage medium group 7.
- the host management computer 35a is described as the entity that manages the server flash of the host computer 5a
- the host management computer 35b is described as the entity that manages the server flash of the host computer 5b. It is not limited to.
- the processing of the host management computer 35 may be executed by the host computer 5, and the host management computer 35 may be read as the host computer 5 in the following description.
- the data network 15 may include a switch such as an FC (Fibre Channel) switch, and the switch is connected to each of the CI / F 11 of the host computer 5 and the DI / F 51 of the storage apparatus 4. Data and control commands may be sent and received between them.
- FC Fibre Channel
- FIG. 3 shows the logical configuration of the host computer 5.
- the host computer 5 includes a hypervisor (hereinafter referred to as “HV”) 13 that can logically generate the VM 6 and execute the VM 6.
- the HV 13 can control a plurality of VMs 6 at a time.
- Each of the plurality of VMs 6 can execute an application as if it were a stand-alone physical computer.
- FIG. 4 shows the host management computer 35.
- the host management computer 35 includes a CPU 37, a display device 38 (display unit) such as an LCD (Liquid Crystal Display), a Memory 39, and an I / F 36.
- the host management computer 35 may have an input device (such as a keyboard).
- the I / F 36 is an interface with the management network 16 and transmits / receives data and control commands to / from the storage apparatus 4, the host computer 5, and the storage management computer 1.
- a host configuration management program 40 and a host setting program 41 are stored in the memory 39.
- the host configuration management program 40 is a program for managing the configuration information of each host computer 5 such as the storage medium group 7 including the server flash.
- the host configuration management program 40 communicates with a host information acquisition program 25 of the storage management computer 1 described later, and transmits / receives various types of information.
- the host setting program 41 is a program for executing various settings of the storage medium group 7 including the server flash of the host computer 5.
- the various settings include settings for using the server flash as a cache and settings for allocating an arbitrary capacity of the server flash to the VM.
- FIG. 5 shows the configuration of the storage apparatus 4.
- the storage apparatus 4 includes a disk controller 55 and a physical device 52.
- the disk controller 52 includes a CPU 47, a memory 48, an MI / F 45, a storage port HI / F (Host-Interface) 46, and a DI / F (Disk-Interface) 51.
- the MI / F 45 is an interface with the management network 16 and transmits / receives data and control commands to / from the host computer 5, the host management computer 35, and the storage management computer 1.
- the HI / F 46 is an interface with the data network 15 and transmits / receives data and control commands to / from the host computer 5.
- the DI / F 51 transmits / receives data and control commands to / from the physical device 52.
- the physical device 52 includes a plurality of types of physical storage media 53 such as an HDD (Hard Disk Drive) and a Flash Memory Drive (storage flash, StF).
- the HDD refers to a physical storage medium other than the flash medium.
- the storage apparatus 4 creates a logical volume 54 from the storage areas of a plurality of physical storage media 53 in the physical device 52. A plurality of logical volumes 54 may be created in the storage device 4.
- the logical volume 54 may be a Thin Provisioning volume which is a format capable of dynamically expanding the capacity.
- Thin provisioning is a technology that allocates a partial area of a physical storage area (hereinafter referred to as a page) to a logical volume, dynamically expands the storage area, and effectively uses the storage area.
- the logical volume 54 provides a page for assignment to the Thin Provisioning volume.
- the capacity of the Thin Provisioning volume can be dynamically expanded by allocating pages from the logical volume 54 included in the pool to the Thin Provisioning volume.
- the storage configuration management program 49 is a program that manages the configuration information of the storage apparatus 4.
- the storage configuration management program 49 communicates with a storage information acquisition program 27 of the storage management computer 1 described later, and transmits / receives various information.
- the storage setting program 50 is a program for executing various settings of the storage device 4.
- the various settings include a setting for securing a cache area for temporarily storing data to be read / written for the logical volume 54, a setting for securing a processor for performing read / write processing for the logical volume 54, etc. Settings for improving the access performance to the computer 5 are included.
- FIG. 6 shows the configuration of the storage management computer 1.
- the storage management computer 1 includes a CPU 21, a display device 22 (display unit) such as an LCD, a Memory 24, and an I / F 23. Further, an input device (keyboard or the like) may be included.
- the I / F 23 is an interface with the management network 16 and transmits / receives data and control commands to / from the storage apparatus 4, the host computer 5, and the host management computer 35.
- programs including a host information acquisition program 25, a storage information acquisition program 27, and a resource allocation plan generation program 2 are stored. Further, the Memory 24 stores an information table including a server information table 31, a storage volume table 32, and a storage pool table 33.
- storage management computer 1 For convenience, it is referred to as “storage management computer 1”, but as described in the present embodiment, the management target of this computer is not limited to the storage device.
- FIG. 7 shows the server information table 31.
- This table is a table for managing information of the host computer 5.
- the server information table 31 includes a tenant ID 60 indicating the tenant to which the host computer belongs, an Sv ID 61 indicating the host computer, a VM ID 62 indicating the VM operating on the host computer, a VM Capacity 120 indicating the total capacity of the VM, SvF ID63 indicating the server flash included in the host computer, SvF Total Capacity 64 indicating the total capacity of the server flash, SvF Allocated Capacity 65 indicating the allocated capacity of the server flash, and the total capacity of the hard disk built in the host computer HDD Total Capacity 66, HDD Used Capacity 67 indicating the used capacity of the hard disk, Rea of the host computer and VM workload With a a Read Rate68 showing the I / O ratio, and Required Performance69 showing the performance required host computer and the VM workload, the.
- a tenant refers to a logical group of host computers, and
- this table defines the correspondence between resources.
- “null” can be stored in the VM ID 62 as information indicating that the target host computer does not operate the VM.
- “null” may be stored in the SvF ID 63 as information indicating that the server flash is not installed in the target host computer.
- the Required Performance 69 can store “High” as information indicating that the required performance of the target host computer and VM workload is high, for example.
- the Performance 69 can store “null” as information indicating that the required performance is not set.
- FIG. 8 shows the storage volume table 32.
- This table is a table for managing information on the logical volume 54 of the storage apparatus 4.
- the storage volume table 32 includes a VOL ID 70 indicating a logical volume, a Storage ID 71 indicating a storage device that provides the logical volume, a VOL type 72 indicating the type of the logical volume, a Capacity 73 indicating the total capacity of the logical volume, and a logical volume.
- Used Capacity 74 indicating the used capacity of the volume
- Target Port ID 75 indicating the target port of the storage device to which the logical volume is allocated
- Initiator ID 76 indicating the device having the initiator port to which the logical volume is allocated
- the logical volume VM ID 77 indicating the VM to which is assigned
- Source Resource ID 79 indicating the resource from which the logical volume is configured
- Drive Type 80 indicating the type of the physical storage medium of the logical volume
- Read rate 81 indicating the read I / O ratio to the logical volume.
- a Random rate 82 indicating a Random I / O ratio to the logical volume.
- the VOL type 72 when the VOL type 72 is “VVOL”, it indicates a Thin Provisioning volume configured by providing a pool volume from the storage pool.
- the source resource ID 79 is an ID of a pool managed by the storage pool table 33 described later.
- the source resource ID 79 stores the ID of the physical storage medium of the storage device managed separately.
- the logical volume in which the information of the physical storage medium is stored in the Source Resource ID 79 may be a volume that is directly provided to the host computer as a storage area. Further, it may be managed as a pool volume in a storage pool table 33 described later and provided to a Thin Provisioning volume.
- Initiator ID 76 stores, for example, the identifier of the host computer indicated by Sv ID 61 of server information table 31.
- Drive Type 80 for example, “SSD” or the like can be stored as information indicating the type of physical storage medium constituting the logical volume. If the logical volume is not assigned to the Target Port and the Initiator Port, “Null” is stored in the Target Port ID 75, the Initiator ID 76, the VM ID 77, and the Initiator Port ID 78.
- the Read rate 81 and the Random rate 82 are not necessarily stored.
- FIG. 9 shows the storage pool table 33.
- This table is a table for managing information on pools constituting a Thin Provisioning volume that is a form of a logical volume of the storage apparatus 4. From the storage pool table 33, the correspondence between the logical volumes and the logical volumes constituting the pool can be known.
- the storage pool table 33 has the following information.
- the storage ID 90 is information for identifying the storage apparatus 4 having a pool.
- the pool ID 91 is information for identifying a pool.
- the Drive Type 96 is information indicating the type of physical storage medium that constitutes the pool.
- the Page ID 92 is information for identifying pages belonging to the pool.
- the VOL ID 93 is information for identifying a VOL having a page.
- the VOL LBA 94 is information indicating the position of the page in the VOL (for example, the top LBA of the page and the LBA at the end of the page).
- the Pool VOL ID 95 is information for identifying the logical volume 54 having the storage area to which the page is allocated. “N / A (Not / Assigned)” indicates that the page is not allocated to any storage area.
- the server information table 31, the storage volume table 32, and the storage pool table 33 may be combined or a part thereof may be referred to as “configuration information” of the computer system.
- the host information acquisition program 25 acquires the configuration / performance information of the host computer 5 from the host configuration management program 40 of the host management computer 35 and stores it in the server information table 31 and the like. Specifically, the host information acquisition program 25 stores the configuration / performance information of each host computer 5 and the configuration information of the VM 6 in the server information table 31. The host information acquisition program 25 may execute these processes periodically or in response to a user operation.
- the storage information acquisition program 27 acquires the configuration information of the storage apparatus 4 from the storage configuration management program 49 of the storage apparatus 4 and updates the storage volume table 32 and the storage pool table 33 based on the acquired configuration information. I do. Regarding the storage volume table 32, the storage information acquisition program 27 stores the acquired configuration information of the storage apparatus 4 on the VM 6 information stored in the server information table 31 and having the same host computer identifier (Initiator ID 76, Sv ID 61). Are stored in association with each other. Note that the storage information acquisition program 27 may execute these processes periodically or in response to a user operation.
- the resource allocation plan generation program 2 receives the request information regarding resource allocation notified by the input from the user, and is stored in the received information, the server information table 31, the storage volume table 32, and the storage pool table 33. Based on the information, a resource allocation plan considering the type and arrangement of the physical storage medium is generated.
- the resource allocation plan generation program 2 identifies the host computer and VM identifier to which the resource is allocated, the capacity of the storage area (or logical volume) to be allocated, and the access pattern issued (accessed) by the VM (or host computer) to the allocated storage area.
- the user's input including designation of information and I / O read ratio information is accepted (S1). If the capacity allocation target is not a VM, only the identifier of the host computer is specified.
- VM etc. when referring to a VM or a host computer to which resources are allocated, it may be collectively referred to as “VM etc.”.
- the I / O access pattern refers to the ratio of sequential access to random access, “Sequential” in which sequential access is dominant, “Random” in which random access is dominant, and the ratio of sequential and random access is comparable. “Balanced” or the like is designated. The user may determine and specify based on the characteristics of the application operated on the VM or the like. This information is hereinafter referred to as “request access pattern”.
- the Read ratio is “Read” when the processing performed by the application operating on the VM or the like is mainly data reading, “Write” when the writing is main, and the ratio is about the same. Designated as “Balanced”. This information is hereinafter referred to as “request I / O type”.
- the input content received from the user is, for example, “allocation request of 1000 GB storage area to the VM ID 002 on the host computer with Sv ID001.
- the request access pattern from the VM is“ Random ”, and the request I / O type is information such as “Read”.
- the user input may be received via an input device such as a keyboard or a mouse or the display device 22, may be received from another program, or a receiving method other than these may be used.
- the resource allocation plan generation program 2 refers to the tables 31-33 and acquires information on the host computer 5 and the storage device 4 (S2). Then, the allocated resource is determined based on the information acquired in S1 and S2 (S3), and the process is terminated.
- the resource options to be allocated for example, a logical volume providing the HDD 500 GB is allocated from the storage area of the storage device “St1”, and the server flash 500 GB is allocated as a cache.
- a logical volume that provides the storage flash 500 GB of the storage device “St1” is allocated, or only the HDD 100 GB of the host computer is allocated.
- the allocation is determined in consideration of these conditions and the resource utilization status. For example, if the requested access pattern is “Sequential”, the HDD is given priority over the flash media as the storage medium to be assigned, and the HDD of the host computer having excellent latency performance is assigned with priority over the HDD of the storage apparatus. If the requested I / O type is “Read”, it is better to assign a server flash, but if the requested access pattern is “Balanced”, the priority is lowered from “Random” and the server flash is assigned. Allocate if there is enough free space.
- the storage device resource may be an HDD.
- the access pattern and the I / O type may be combined or may be referred to as “access characteristics”.
- the storage area of the storage device is provided to the host computer as a Thin Provisioning volume, but a configuration plan for allocating other logical volumes and storage areas can be generated.
- the volume allocation request input by the user may include designation of the volume type.
- FIG. 10 shows the details of the allocation resource determination process (S3).
- the resource allocation generation program 2 determines a resource to be allocated to the specified VM or the like according to the request access pattern and the request I / O type, the usage status of the system resource, and the resource allocated to the specified VM or the like.
- the threshold A in S5 is information for managing the free space that should be secured, and is calculated by the following calculation formula, for example.
- Threshold A (total SvF capacity of the specified host computer) * 50% + user-specified capacity
- the server flash can be allocated if 50% or more of the total capacity remains. .
- the value of 50% is set in advance, but can be changed according to the usage policy of the user.
- the request access pattern is Balanced and the server flash allocation is not a particularly suitable pattern, but the request I / O type is Read, and the server flash allocation is suitable from the viewpoint of the I / O type. Therefore, the policy is to use the server flash when there is enough free space.
- S7 it is determined whether or not a server flash has already been allocated to a VM or the like designated for capacity allocation (S7).
- Yes in S7 since priority is given to allocating the server flash to other VMs and the like, it is determined that only the storage area of the storage apparatus is allocated to the VM.
- the allocated storage device resource may be an HDD, not a high-performance storage flash.
- the storage pool table 33 it is determined whether or not there is a storage device having a pool of HDDs that have a free space greater than the specified capacity (S16).
- Drive Type 96 determines the capacity of a medium that is a disk medium such as SATA or SAS instead of SSD.
- the resource allocation plan generation program 2 refers to the storage pool table 33 and searches for a pool composed of a Drive Type storage medium indicating the HDD. For each searched pool, the total capacity of pages with Pool VOL ID “N / A” is calculated as the free capacity of the pool.
- a resource allocation plan for allocating the HDD is generated.
- the storage setting program 50 of the storage apparatus 4 is provided with a pool volume from the pool of the HDD to form a Thin Provisioning volume, and issues an instruction to allocate to the request target VM or the like (S20), and the process is terminated.
- a resource allocation plan (configuration plan) may be output to the display device 22. Further, it may accept an execution request for the output configuration plan and issue an allocation instruction to the storage apparatus 4. The same applies when the process of S20 is reached through the other steps of the flow.
- allocation of the designated capacity is determined from the server flash provided in the designated host computer (S8), and the process proceeds to S16.
- the storage pool table 33 it is determined whether there is a free space of the capacity designated for allocation in the HDD of the storage apparatus 4 (S16). If there is free space by the same determination as described above, a resource allocation plan for allocating a storage area from the pool of the HDD is generated. A logical volume assignment using the storage area is issued to the storage setting program 50 of the storage apparatus 4, and an instruction to set a server flash as a cache of the assigned logical volume is issued to the host setting program 41 of the host management computer 35. The process is issued (S20).
- the server information table 31 is referred to and it is determined whether or not there is a host computer having a server flash having a space larger than the specified capacity in the same tenant as the specified host computer. (S9).
- the determination in S9 may be not less than the specified capacity and may be not less than the threshold A as in S5. If the result of S9 is Yes, the VM that has received the capacity allocation request is operated not by the designated host computer but by the host computer searched in S9, and a message indicating that the use of the server flash is recommended is output, and the processing ends. (S12).
- the target of capacity allocation is not a VM but a host computer
- a message indicating that it is recommended that an application scheduled to use data stored in the allocated storage area be operated on the host computer searched in S9 is output. good.
- the information may be output to the user via the display device 22, the information may be notified to another program, or other formats may be used.
- S10 If the result of S10 is Yes, if a server flash is allocated to the VM (or host computer), the allocation is canceled and the VM for which capacity allocation is requested is searched in S10 instead of the designated host computer. The fact that it is recommended that the server be allocated by operating on the host computer on which the VM is operated is output (S13). If the target of capacity allocation is not a VM but a host computer, a message indicating that it is recommended to run an application scheduled to use data stored in the allocated storage area on the host computer searched in S10 is output. good.
- the threshold value B in S11 is information for performing control to preferentially allocate a storage flash when the server flash of the specified host computer is low with respect to the server flash availability of another host computer. For example, when the requested access pattern is Random, the following calculation formula is used.
- Threshold B (total SvF free capacity of host computers other than the specified host computer in the tenant) / (number of host computers other than the specified host computer)
- the threshold B is set lower than when the request access pattern is Random.
- the threshold value when the requested access pattern is Balanced may be defined as 50% of the threshold value in the case of Random, or may be other values and can be changed according to the user's usage policy. It is.
- priority is given to the allocation of the storage flash to the I / O whose access pattern is Random by setting the threshold value B lower than that when the request access pattern is Random. Is possible.
- S14 it is determined whether or not there is a free space larger than the requested capacity in the flash media storage area of the storage device 4 (S14).
- the determination in S14 is made by referring to the storage pool table 33 and calculating the free capacity of the Flash media pool such as SSD, as in S16. If the result of S14 is Yes, a resource allocation plan for allocating the storage area is generated. A logical volume allocation instruction using the storage area is issued to the storage setting program 50 of the storage apparatus 4 and the process is terminated (S20).
- S15 the result of S11 or the result of S14 is No, it is determined whether or not the HDD in the designated host computer has a space larger than the designated capacity
- the HDD is given priority over the Flash medium as the storage medium to be allocated. Further, since the HDD of the host computer having excellent latency performance is assigned with priority over the HDD of the storage apparatus, the process proceeds to S15.
- S4 If the result of S4 is that the request access pattern is Random or Balanced and the request I / O type is Write or Balanced, the process proceeds to S10.
- the above is the allocation resource determination process (S3) of the resource allocation plan generation program 2.
- the policy for each branch of the flow is not limited to the above. For example, when a determination is made to cancel the allocation of the server flash from another VM or the like, a configuration plan for canceling the allocation from the VM to which the allocation of the server flash is not prioritized with reference to the server information table 31 and the storage volume table 32 is proposed. It is good also as outputting.
- server flash allocation is performed from a VM whose Read ratio is “Balanced” or “Write”. It may be determined to cancel and recommend the allocation to the requested VM. For example, if the range in which the Read ratio is 40 to 70% is defined as “Balanced”, in the case of FIG. 8, the Read ratio of the VM001 in Sv002 is “Balanced”, and there is a capacity allocation request for the VM with higher priority. In this case, it is determined that the server flash can be deallocated, and a configuration plan is output.
- the free capacity of the storage area of the storage device the total page capacity for which no pool volume is set in the corresponding pool was calculated, but when assigning the Thin Provisioninging volume to be allocated to the host computer Therefore, it is not always necessary to secure a storage medium. For example, a threshold value that is greater than or equal to the actual capacity is set for each pool, and if it is within the threshold value, even if the physical storage medium capacity of the pool is actually exceeded, it is stored in the host computer from the pool. A configuration plan for allocating an area may be generated.
- the storage management computer 1 After the execution of the resource allocation plan is completed, the storage management computer 1 updates the information in the tables 31-33 upon receiving a setting completion notification from the host computer 2 and the storage apparatus 4 or by acquiring periodic information.
- a configuration plan suitable for performance characteristics based on the type and location of the physical storage medium is generated, and the generated configuration It is possible to instruct the execution of the plan. Thereby, it becomes possible to improve the I / O performance of the whole computer system.
- the resource allocation plan generation program 2 of the storage management computer 1 generates an allocation plan for the storage medium group 7 including the logical volume 54 of the storage apparatus 4 and the server flash of the host computer 5. .
- the storage management computer 1 performs processing for generating a resource allocation plan for the dynamic thin provisioning volume 54a.
- the dynamic thin provisioning volume is a form of the logical volume 54 of the storage apparatus 4 and is a logical volume whose capacity can be expanded dynamically, similar to the thin provisioning volume.
- it can be dynamically changed to another page with different response performance and reliability depending on the access status to the Dynamic Thin Provisioning volume 54a. It is.
- the volume Tiering Policy setting table 100 and the Tiering Policy table 101 are additionally stored in the Memory 24 of the storage management computer 1.
- part of the processing of the resource allocation plan generation program 2 of the storage management computer 1 is changed. In the following, these differences will be described.
- FIG. 11 shows a volume tiering policy setting table 100 stored in the memory 24 of the storage management computer 1 in the second embodiment.
- the volume tiering policy setting table 100 is a table for managing information on the tiering policy set in the dynamic thin provisioning volume 54a. From the volume tiering policy setting table 100, the correspondence relationship between the dynamic thin provisioning volume 54a and the tiering policy set in the volume is known.
- “Tiering Policy” is information that defines rules for the dynamic thin provisioning volume 54a to assign and change pages.
- the volume tiering policy setting table 100 includes the following information.
- the VOL ID 105 is information for identifying the Dynamic Thin Provisioning volume 54a.
- the storage ID 106 is information for identifying the storage apparatus 4 having the volume 54a.
- the Tiering Policy ID 107 is information for identifying the Tiering Policy set in the volume 54a.
- FIG. 12 shows the Tiering Policy table 101 stored in the Memory 24 of the storage management computer 1 in the second embodiment.
- the Tiering Policy table 101 is a table for managing information on the Tiering Policy.
- the Tiering Policy table 101 defines rules for page assignment and assignment change defined by the Tiering Policy.
- the Tiering Policy table 101 includes the following information.
- the Tiering Policy ID 110 is information for identifying the Tiering Policy.
- Tier1 rate 111 indicates the ratio of the storage area of Tier1 that can be used by the dynamic thin provisioning volume 54a in which the Tiering Policy is set to the total capacity of the volume. For example, when the total capacity of the volume 54a indicated in the capacity 73 of the storage volume table 32 is 100 GB and the Tier1 rate 111 is 30%, the capacity of the storage area of the Tier1 that can be used by the Dynamic Thin Provisioning volume 54a is 30 GB. It becomes.
- Tier1 is information for specifying the type (performance range) of the physical storage medium constituting the volume 54a, and it may be defined that the Drive Type 80 of the storage volume table 32 is an SSD, or any other type It may be associated with the physical storage medium.
- the Tier 2 rate 112 and the Tier 3 rate 113 indicate the ratio of the storage areas of the Tier 2 and Tier 3 that can be used by the Dynamic Thin Provisioning volume 54a in which the Tiering Policy is set with respect to the total capacity of the volume.
- the Tiering Policy ID 107 is stored in the Tiering Policy ID 107 of the volume Tiering Policy setting table 100, and the Tiering Policy set in the volume 54a can be determined.
- the priority of use is defined in advance for each Tier, Tiers with the highest priority are assigned in order from the data with the largest number of I / Os, and pages corresponding to the available Tiers are used. Is assigned, the page with the next highest priority is assigned.
- the Tiering Policy may be a format that specifically defines a Tier assigned to the I / O number and the range of the I / O number, or other formats.
- the pool is composed of one type of storage medium.
- the storage pool table 33 of the second embodiment can store “Mix” indicating that it is configured from a plurality of types of physical storage media as a drive type 96 of the pool.
- the Drive Type 80 of the storage volume table 32 can store “Mix” in the column of the Dynamic Thin Provisioning volume.
- the information obtained by adding the volume Tiering Policy setting table 100 and the Tiering Policy table 101 to the tables 31-33 or a part thereof may be referred to as “configuration information”.
- the process of the allocation resource determination process S3a by the resource allocation plan generation program 2a of the second embodiment will be described.
- the allocated resource determination process S3a is different from the allocated resource determination process S3 of the first embodiment only in the process corresponding to S20, and other processes are not changed.
- a resource allocation plan for allocating the Dynamic Thin Provisioninging volume 54a in which Tiering Policy (TP001 in the example of FIG. 12) with a high Flash media ratio is set is generated after S14.
- the generated resource allocation plan (configuration plan) is output to the display device 22, or an instruction to allocate the dynamic thin provisioning volume 54a is issued to the storage setting program 50 of the storage device 4, and the process is terminated (S21). .
- a resource allocation plan for allocating the Dynamic Thin Provisioning volume 54a in which the Tiering Policy (TP003 in the example of FIG. 12) with no Flash media allocation is set is generated after S16.
- the generated resource allocation plan is output to the display device 22.
- the allocation of the dynamic thin provisioning volume 54a is issued to the storage setting program 50 of the storage apparatus 4, and a server flash setting command is issued to the host setting program 41 of the host management computer 35, and the process is terminated ( S22).
- Tiering Policy including Flash media is set when the storage flash is more than the specified capacity, but Tier 1 rate is high if the value stored in Required Performance 69 of server information table 31 is High.
- a conditional branch such as assigning a Tiering Policy with a low Tier1 rate if the value stored in the Required Performance 69 is Low may be added, or other conditions may be added.
- the performance based on the type and location of the physical storage medium even in a configuration in which a plurality of host computers using server flash share a storage device and a configuration using a Dynamic Thin Provisioning volume.
- a configuration plan suitable for the characteristics can be generated. Thereby, it becomes possible to improve the I / O performance of the whole computer system.
- the resource allocation plan generation program 2 of the storage management computer 1 generates an allocation plan for the storage medium group 7 including the logical volume 54 of the storage apparatus 4 and the server flash of the host computer 5 in response to the input. It was illustrated that it was generated.
- the storage management computer 1 performs a process of generating a plan for changing the allocation of resources that have already been allocated.
- the processing of the resource allocation plan generation program 2 of the storage management computer 1 is partially changed. In the following, these differences will be described.
- FIG. 13 mainly shows processing by the resource allocation plan generation program 2b of the third embodiment.
- the resource allocation plan generation program 2b is different from the resource allocation plan generation program 2 of the first embodiment only in the contents of S1 and S2 and S20 of the allocation resource determination process S3, and other processes are not changed.
- the processes of S26 and S3 are repeated for the allocated logical volume 54.
- the allocated logical volume 54 indicates a logical volume 54 stored in the storage volume table 32 in association with a VM or the like.
- the resource allocation plan generation program 2b refers to the storage volume table 32 and uses the logical volume Random rate as the information of the allocated logical volume 54, such as the logical volume capacity 73 and the VM to which the logical volume is allocated.
- Read rate is acquired (S26).
- the acquired VM or the like to which the logical volume is allocated is used as the requested VM or the like, the capacity of the logical volume is set as the requested allocated capacity, and the Random rate and Read rate information is requested as the access pattern and the request I / O.
- the allocation resource determination process S3 is performed as the O type.
- a configuration change plan is generated and a message to recommend that the configuration change plan is recommended is output.
- a logical volume that includes server flash and Flash media is assigned to a VM with a high Required Performance. It is possible to assign with priority.
- S20 only the generation / output of the allocation plan is performed and no setting instruction is given to the host computer 5 and the storage apparatus 4, but a configuration change is performed to continue I / O to the host computer 5 and the VM 6.
- a configuration change proposal may be implemented.
- the performance characteristics based on the type and location of the physical storage medium are suitable.
- the configuration can be reconstructed. Thereby, it becomes possible to improve the I / O performance of the whole computer system.
- the resource allocation plan generation program 2 of the storage management computer 1 generates an allocation plan for the storage medium group 7 including the logical volume 54 of the storage apparatus 4 and the server flash of the host computer 5 in response to the input. It was illustrated that it was generated.
- the storage management computer 1 performs a process of generating a plan for changing the allocated resource in response to the movement of the data in the first logical volume 54 to the second logical volume 54. .
- the resource allocation plan generation program 2c of the fourth embodiment is different from the resource allocation plan generation program 2 of the first embodiment only in the contents of S1 and S2 and S20 of the allocation resource determination process S3, and other processes are not changed.
- the resource allocation plan generation program 2c receives information on the logical volume 54 that is the data migration source and migration destination (S30). Next, the resource allocation plan generation program 2c refers to the storage volume table 32, and as the received information on the logical volume 54 of the data migration source, the logical volume capacity 73, the host computer 4 to which the logical volume is allocated, and The VM 6 obtains the Random rate and Read rate of the logical volume (S31). Subsequently, the VM or the like to which the acquired logical volume is allocated is set as the requested VM or the like, the capacity of the logical volume is set as the requested allocation capacity, and the information of the Random rate and Read rate is requested as the access pattern and the request.
- an allocation resource determination process S3 is performed.
- a configuration change plan is generated as a storage area allocation plan for the logical volume that is the migration destination, and a message indicating that it is recommended to implement the allocation plan is output.
- the resource allocation plan generation program 2 of the storage management computer 1 generates an allocation plan for the storage medium group 7 including the logical volume 54 of the storage apparatus 4 and the server flash of the host computer 5 in response to the input. It was illustrated that it was generated.
- the storage management computer 1 performs a process of generating a plan for changing the allocation of the allocated resource when the data of the VM 6 moves from the first logical volume 54 to the second logical volume 54. Do.
- the processing of the resource allocation plan generation program 2 of the storage management computer 1 is partially changed. In the following, these differences will be described.
- the server information table 31 and the storage volume table 32 of the fifth embodiment store information on throughput in addition to the table information of the first embodiment.
- Throughput refers to the processing capacity per unit time of a storage area or an I / O issuer.
- the server information table 31 has a Throughput Performance column, and stores throughput information for each VM. For example, information such as “Throughput Performance” is “50 GB / s” is stored for VM001 of Sv001.
- the storage volume table 32 has a Throughput Performance column, and stores throughput information for each logical volume. For example, for VOL1, information such as “Throughput Performance” being “100 GB / s” is stored.
- FIG. 14 shows the processing of the resource allocation plan generation program 2d of the fifth embodiment.
- the resource allocation plan generation program 2d is different from the resource allocation plan generation program 2 of the first embodiment only in the contents of S1 and S2 and S20 of the allocation resource determination process S3, and other processes are not changed.
- the resource allocation plan generation program 2d first, information on the VM 6 to be moved and information on the logical volume 54 to which the VM 6 is to be moved are received from the host management computer 35 (S35). Next, the resource allocation plan generation program 2d acquires information on the migration source logical volume 54 in which the data of the VM 6 to be moved is stored, based on the VM information acquired in S35 and the information in the storage volume table 32. (S36).
- the resource allocation plan generation program 2d repeats S38 and S3 for the migration source logical volume 54 and the migration destination logical volume 54.
- the resource allocation plan generation program 2d refers to the storage volume table 32, and acquires the capacity of each logical volume, information on the host computer 4 and VM 6 to which each logical volume is allocated, etc. as information on the logical volume 54 before and after the migration. Then, the Random rate and Read rate of the logical volume are calculated (S38).
- each ratio is calculated in consideration of movement of VM data.
- the Random rate and Read rate related to the remaining storage data when the VM data is migrated are calculated.
- information on the migration source logical volume before the VM migration stored in the storage volume table 32 is requested to the migration destination logical volume after migration. Acquired as performance etc.
- the storage volume table 32 is specifically referred to. If it is determined that data other than the VM data is stored on the logical volume, the logical volume is reconfigured. First, the throughput performance of the logical volume is acquired from the storage volume table 32. Further, the server information table 31 is referred to, and the total capacity of the VM data (VM Capacity 120) and the throughput performance related to the VM are acquired. For example, assume that the throughput performance of the logical volume is 100 GB / s and the Read ratio is 50%, the throughput performance for the VM is 50 GB / s, and the Read ratio is 80%.
- the Random rate is calculated based on the throughput performance and I / O ratio of the entire logical volume and the VM.
- the allocation resource determination process S3 is performed using the Random rate and Read rate information acquired in S38 as the request access pattern and the request I / O type. Then, in S20 of the allocation resource determination process S3, a configuration change plan for the storage area to be allocated to the migration source and migration destination logical volumes is generated, and a message indicating that it is recommended to implement the configuration change plan is output. In S20, only the configuration change proposal is generated and output, and no setting instruction is given to the host computer 5 and the storage apparatus 4, but the configuration change is performed to continue I / O to the host computer 4 and the VM 6. In addition, a configuration change proposal for resource allocation may be implemented.
- the fifth embodiment even when a plurality of host computers using a server flash share a storage apparatus, data of the VM 6 is moved from the first logical volume 54 to the second logical volume 54. It is possible to change the allocation of storage resources suitable for the performance characteristics based on the type and location of the physical storage medium. This makes it possible to improve the I / O performance of the entire computer system.
- the flash media and the like are exemplified as objects to be managed, but the management object is not limited to this.
- the technology of each embodiment can be applied to a high-performance storage resource such as NVDIMM (Non-Volatile Dual In-line Memory Module).
- the allocation target is the host computer and the VM, but it is also possible to generate a resource allocation plan for an object or application other than the VM that is stored in the storage area of the storage device and operates on the host computer. Is possible.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
上記の計算式の例では、サーバフラッシュが総容量の50%以上余るならば、割り当てて良いと判断する。50%という値は予め設定されるが、ユーザの利用方針に合わせて変更することが可能である。当該ケースは、要求アクセスパタンはBalancedであり、サーバフラッシュの割り当てが特別適しているパタンではないが、要求I/O種別がReadであり、I/O種別の観点ではサーバフラッシュの割り当てが適しているため、サーバフラッシュの空き容量に余裕がある場合には利用するというポリシーである。
上記計算式の例では、テナント内の指定されたホスト計算機以外のホスト計算機のサーバフラッシュの空き容量の平均値に比べて、指定されたホスト計算機のサーバフラッシュの空きが少なければ、ストレージフラッシュの割り当てを判定する処理へ進む。S11により、サーバフラッシュの余裕が少ないホスト計算機に、優先してストレージフラッシュを割り当てることが可能となる。
第5実施形態では、ストレージ管理計算機1のリソース割当案生成プログラム2の処理が一部変更される。以降ではこれらの差分について示す。
Claims (15)
- ホスト計算機とストレージ装置と通信し、
前記ホスト計算機及び前記ストレージ装置が備える、性能の異なる複数の記憶媒体の情報を含み、前記記憶媒体より提供される記憶領域と前記ホスト計算機とを関連付けて示す、構成情報を格納するメモリと、
前記メモリに接続され、
前記ホスト計算機によるアクセスの特性及び割当てる記憶領域の容量の情報を含む、前記ホスト計算機への記憶領域の割当て要求を受け付け、
前記構成情報を参照して、前記ストレージ装置及び前記ホスト計算機が備える記憶媒体の中から、前記要求に含まれるアクセス特性に基づいて、前記容量の記憶領域を提供可能な前記記憶媒体を選択し、
前記選択した記憶媒体より前記容量の記憶領域を前記ホスト計算機に割り当てる構成案を生成し、
前記構成案を出力する、CPUと、
を備えることを特徴とする管理計算機。 - 前記CPUが、
前記構成案に基づいて前記ホスト計算機へ前記記憶領域の割り当てがされるよう制御する、
請求項1に記載の管理計算機。 - 前記構成情報は、
前記記憶領域に格納され前記ホスト計算機により実行される仮想マシンを、前記記憶領域と関連付けて示す情報を含み、
前記CPUは、前記仮想マシンに対する記憶領域の割当て要求を受け付けて、前記構成案を生成する
請求項2に記載の管理計算機。 - 前記要求に含まれるアクセス特性の情報には、前記仮想マシンより発行されるRandom I/OとSequential I/Oの比率の情報と、Read I/OとWrite I/Oの比率の情報を含む、
請求項3に記載の管理計算機。 - 前記ホスト計算機及び前記ストレージ装置が備える記憶媒体にFlash Memory Driveを含む、
請求項4に記載の管理計算機。 - 前記CPUは、
前記Random I/OとSequential I/Oの比率の情報と、Read I/O とWrite I/Oの比率の情報に基づき、前記ホスト計算機が備えるFlash Memory Driveを前記仮想マシンが利用可能なキャッシュとして割当てるか否かを判断し、前記構成案を生成する
請求項5に記載の管理計算機。 - 前記CPUは、
さらに、前記ホスト計算機が備えるFlash Memory Driveの空き容量に関する第一の閾値を算出し、前記第一の閾値に基づいて、前記仮想マシンに前記ホスト計算機が備えるFlash Memory Driveを割当てるか否かを判断し、
前記要求に含まれるRandom I/OとSequential I/Oの比率と、Read I/O とWrite I/Oの比率に基づいて、前記第一の閾値を変更する
請求項6に記載の管理計算機。 - 前記CPUは、
前記要求に含まれるRead I/Oの比率が大きい場合、前記第一の閾値を、前記Read I/Oの比率が小さい場合と比較して小さな値として算出することで、前記Read I/Oの比率が大きな仮想マシンに前記ホスト計算機のFlash Memory Driveを優先して割当てる構成案を生成する
請求項7に記載の管理計算機。 - 複数の前記ホスト計算機が、複数の前記仮想マシンが記憶媒体を共有可能なテナントを構成しており、
前記CPUは、
前記要求の対象である仮想マシンが動作するホスト計算機が属する前記テナントを構成するホスト計算機の中に、前記アクセス特性に対応する記憶媒体を備えるホスト計算機が存在するか否かを検索し、
存在すると判断した場合に、前記検索したホスト計算機が備える記憶媒体より前記仮想マシンに記憶領域を割り当てる構成案を生成する
請求項3に記載の管理計算機。 - 複数の前記ホスト計算機が、複数の前記仮想マシンが記憶媒体を共有可能なテナントを構成しており、
前記CPUが、
前記要求の対象である仮想マシンが動作するホスト計算機と同じテナントに属する、他のホスト計算機が備える記憶媒体の空き容量に基づいて、前記仮想マシンが動作するホスト計算機が備えるFlash Memory Driveの容量に関する第二の閾値を算出し、
前記第二の閾値に基づき、前記ストレージ装置が備えるFlash Memory Driveを前記仮想マシンに割り当てるか否かを判断し、前記構成案を生成する
請求項8に記載の管理計算機。 - 前記構成情報は、さらに前記仮想マシンに対する要求性能の情報を含み、
前記CPUは、
前記構成情報を参照して、前記要求性能が高い前記仮想マシンに対して、Flash Memory Driveより優先して記憶領域を割り当てる構成案を生成する
請求項3に記載の管理計算機。 - 前記メモリは、さらに、
前記ストレージ装置が提供する記憶領域に対して、前記ストレージ装置が備える性能の異なる複数の記憶媒体より提供される容量の割合を示す階層ポリシー情報、を格納し、
前記CPUは、
前記階層ポリシー情報を参照し、前記要求に含まれるアクセス特性に対応する階層ポリシーに基づいて提供された記憶領域を、前記ホスト計算機に割り当てる構成案を生成する、
請求項1に記載の管理計算機。 - 前記構成情報は、前記ホスト計算機に関連付けられた前記記憶領域に対するアクセス特性の情報をさらに含み、
前記CPUは、
前記要求を受け付ける代わりに、前記構成情報を参照して、前記記憶領域の容量及び前記記憶領域に対するアクセス特性の情報に基づき、前記記憶領域に関連付けられたホスト計算機に対して、前記ストレージ装置または前記ホスト計算機の記憶媒体より異なる記憶領域を割当てる構成変更案を生成する、
請求項1に記載の管理計算機。 - 前記構成情報は、前記記憶媒体より記憶領域を提供される論理ボリュームと前記ホスト計算機とを関連付けて示す情報を含み、前記論理ボリュームに対するアクセス特性の情報をさらに格納し、
前記CPUは、
前記要求を受け付ける代わりに、前記論理ボリュームに格納されたデータが他の論理ボリュームへ移動されることを契機として、
前記構成情報を参照し、移動元の論理ボリュームの容量及び前記移動元の論理ボリュームに対するアクセス特性の情報に基づき、前記論理ボリュームに関連付けられたホスト計算機に対して、前記ストレージ装置または前記ホスト計算機の記憶媒体より記憶領域を割当てる構成変更案を生成する
請求項1に記載の管理計算機。 - 前記構成情報は、前記記憶媒体より記憶領域を提供される論理ボリュームと前記仮想マシンとを関連付けて示す情報、前記論理ボリュームに対するアクセス特性の情報、及び、前記論理ボリューム及び前記論理ボリュームに関連付けられた仮想マシンのスループットの情報を含み、
前記CPUは、
前記要求を受け付ける代わりに、第一の論理ボリュームに格納された前記仮想マシンのデータが、第二の論理ボリュームへ移動されることを契機として、
前記構成情報を参照して、前記第一の論理ボリュームの前記データ移動後のアクセス特性を、前記構成情報に含まれる前記第一の論理ボリュームに対するアクセス特性と、前記第一の論理ボリューム及び前記仮想マシンのスループットとを用いて算出し、
前記構成情報に含まれる前記第一の論理ボリュームに対するアクセス特性を、前記第二の論理ボリュームの前記データ移動後のアクセス特性として算出し、
前記第一の論理ボリュームと前記第二の論理ボリュームに対して、前記ストレージ装置または前記ホスト計算機の記憶媒体より記憶領域を割当てる構成変更案を生成する、
請求項3に記載の管理計算機。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/320,025 US10248460B2 (en) | 2015-03-27 | 2015-03-27 | Storage management computer |
PCT/JP2015/059536 WO2016157274A1 (ja) | 2015-03-27 | 2015-03-27 | ストレージ管理計算機 |
JP2017508810A JP6383861B2 (ja) | 2015-03-27 | 2015-03-27 | ストレージ管理計算機 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2015/059536 WO2016157274A1 (ja) | 2015-03-27 | 2015-03-27 | ストレージ管理計算機 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016157274A1 true WO2016157274A1 (ja) | 2016-10-06 |
Family
ID=57004148
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2015/059536 WO2016157274A1 (ja) | 2015-03-27 | 2015-03-27 | ストレージ管理計算機 |
Country Status (3)
Country | Link |
---|---|
US (1) | US10248460B2 (ja) |
JP (1) | JP6383861B2 (ja) |
WO (1) | WO2016157274A1 (ja) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2021530803A (ja) * | 2018-07-19 | 2021-11-11 | ナム テク カンパニー リミテッドNamu Tech Co., Ltd. | クラウドプラットフォームでアプリケーションコンテナのボリューム(ストレージ)プロビゾニング方法 |
US11416152B2 (en) | 2017-09-12 | 2022-08-16 | Kioxia Corporaton | Information processing device, information processing method, computer-readable storage medium, and information processing system |
US11734045B2 (en) | 2020-03-19 | 2023-08-22 | Fujitsu Limited | Construction management device, information processing system, and non-transitory computer-readable storage medium |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108207114B (zh) * | 2015-08-18 | 2021-12-21 | 瑞典爱立信有限公司 | 用于重新配置虚拟机的技术 |
WO2017072933A1 (ja) * | 2015-10-30 | 2017-05-04 | 株式会社日立製作所 | 計算機システムの管理システム及び管理方法 |
US11977456B2 (en) * | 2016-11-23 | 2024-05-07 | 2236008 Ontario Inc. | File system framework |
US10296262B2 (en) * | 2017-02-02 | 2019-05-21 | International Business Machines Corporation | Aligning tenant resource demand in a multi-tier storage environment |
US11301487B1 (en) * | 2017-07-21 | 2022-04-12 | EMC IP Holding Company LLC | Automated server discovery |
JP7180485B2 (ja) * | 2019-03-22 | 2022-11-30 | 株式会社デンソー | 中継装置およびキュー容量制御方法 |
JP7154261B2 (ja) * | 2020-09-25 | 2022-10-17 | 株式会社日立製作所 | 複合型ストレージシステム |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2015015592A1 (ja) * | 2013-07-31 | 2015-02-05 | 株式会社日立製作所 | 計算機システム及び計算機システム制御方法 |
JP5707540B1 (ja) * | 2014-01-31 | 2015-04-30 | 株式会社東芝 | 階層化ストレージシステム、ストレージコントローラ、及び階層間のデータ移動を代替する方法 |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4139675B2 (ja) * | 2002-11-14 | 2008-08-27 | 株式会社日立製作所 | 仮想ボリュームの記憶領域割当方法、その装置及びプログラム |
JP4343578B2 (ja) * | 2003-05-08 | 2009-10-14 | 株式会社日立製作所 | ストレージ運用管理システム |
US7788460B2 (en) * | 2004-04-13 | 2010-08-31 | Intel Corporation | Defragmenting objects in a storage medium |
JP4987107B2 (ja) * | 2010-07-30 | 2012-07-25 | キヤノン株式会社 | 画像形成装置 |
JP5589081B2 (ja) * | 2010-09-08 | 2014-09-10 | 株式会社日立製作所 | コンピュータシステムの管理方法及び管理装置 |
-
2015
- 2015-03-27 JP JP2017508810A patent/JP6383861B2/ja active Active
- 2015-03-27 US US15/320,025 patent/US10248460B2/en active Active
- 2015-03-27 WO PCT/JP2015/059536 patent/WO2016157274A1/ja active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2015015592A1 (ja) * | 2013-07-31 | 2015-02-05 | 株式会社日立製作所 | 計算機システム及び計算機システム制御方法 |
JP5707540B1 (ja) * | 2014-01-31 | 2015-04-30 | 株式会社東芝 | 階層化ストレージシステム、ストレージコントローラ、及び階層間のデータ移動を代替する方法 |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11416152B2 (en) | 2017-09-12 | 2022-08-16 | Kioxia Corporaton | Information processing device, information processing method, computer-readable storage medium, and information processing system |
JP2021530803A (ja) * | 2018-07-19 | 2021-11-11 | ナム テク カンパニー リミテッドNamu Tech Co., Ltd. | クラウドプラットフォームでアプリケーションコンテナのボリューム(ストレージ)プロビゾニング方法 |
US11734045B2 (en) | 2020-03-19 | 2023-08-22 | Fujitsu Limited | Construction management device, information processing system, and non-transitory computer-readable storage medium |
Also Published As
Publication number | Publication date |
---|---|
JPWO2016157274A1 (ja) | 2017-08-17 |
JP6383861B2 (ja) | 2018-08-29 |
US10248460B2 (en) | 2019-04-02 |
US20170132044A1 (en) | 2017-05-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6383861B2 (ja) | ストレージ管理計算機 | |
US11080081B2 (en) | Virtual machine and volume allocation in hyperconverged infrastructure environment and storage system | |
US10503413B1 (en) | Methods and apparatus for SAN having local server storage including SSD block-based storage | |
JP5512833B2 (ja) | ストレージの仮想化機能と容量の仮想化機能との両方を有する複数のストレージ装置を含んだストレージシステム | |
US10108460B2 (en) | Method and system for integrated deployment planning for virtual appliances | |
JP5981563B2 (ja) | 情報記憶システム及び情報記憶システムの制御方法 | |
EP3729251A1 (en) | Virtualized ocssds spanning physical ocssd channels | |
US9256382B2 (en) | Interface for management of data movement in a thin provisioned storage system | |
US20170031699A1 (en) | Multiprocessing Within a Storage Array System Executing Controller Firmware Designed for a Uniprocessor Environment | |
JP2014175009A (ja) | 仮想マシンをサポートするフラッシュ・ベースのキャッシング・ソリューションでの動的キャッシュ共有のためのシステム、方法、およびコンピュータ可読媒体 | |
WO2014155555A1 (ja) | 管理システム及び管理プログラム | |
KR102521051B1 (ko) | 하이브리드 데이터 룩-업 방법 | |
US8447947B2 (en) | Method and interface for allocating storage capacities to plural pools | |
JP2015531090A (ja) | ストレージデバイスの高速アクセス及びデータ保護を実現する計算機、計算機システム、及びi/o要求処理方法 | |
US9239681B2 (en) | Storage subsystem and method for controlling the storage subsystem | |
JP2022034455A (ja) | 計算機システムおよび管理方法 | |
JP7107981B2 (ja) | 計算機システム | |
WO2018235149A1 (ja) | ストレージ装置及び記憶領域管理方法 | |
US9690610B2 (en) | Computer system and management computer controlling method | |
US20150363128A1 (en) | Computer system and management system and management method of storage system | |
JP2013122691A (ja) | 割り当て装置およびストレージ装置 | |
US20240095079A1 (en) | Dynamic Core Allocation Among Containers on a Host | |
WO2017163322A1 (ja) | 管理計算機、および計算機システムの管理方法 | |
JP6657990B2 (ja) | ストレージ装置、仮想ボリューム制御システム、仮想ボリューム制御方法および仮想ボリューム制御プログラム | |
JP6351387B2 (ja) | 情報処理装置、プログラムおよび記録媒体 |
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: 15887430 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15320025 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 2017508810 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 15887430 Country of ref document: EP Kind code of ref document: A1 |