JP2015103095A - Virtual resource management device, virtual resource operation method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce time when cloud service cannot be used.SOLUTION: The virtual resource management device comprises a retrieval part and a duplication part. The retrieval part receives request for expanding an image file for storing a virtual resource designated by a user to a volume which can be operated in a storage, and then retrieves a volume which has been expanded already from the same image file and which has not been updated yet. The duplication part duplicates the retrieved volume, and then provides the user with the volume.

Description

  The present invention relates to a virtual resource management device, a virtual resource operation method, and a virtual resource operation program.

  As a foundation of an IaaS (Infrastructure as a Service) type cloud service, an open stack of Open Source is known. The open stack is mainly intended to provide an API (Application Programming Interface) having a primitive function as an IaaS platform. For example, an API for developing an image file (also simply referred to as “image”) on a volume and creating a volume, an API for acquiring an image file from the volume, and the like are defined.

OpenStack web site, [searched on November 13, 2013], Internet (URL: http://www.openstack.org/) CloudStack web site, [November 13, 2013 search], Internet (URL: http://cloudstack.apache.org/) D. Nurmi, R. Wolski, C. Grzegorczyk, G. Obertelli, S. Soman, L. Youseff, D. Zagorodnov, "The Eucalyptus Open-source Cloud-computing System," In Proceedings of Cloud Computing and Its Applications, Oct . 2008.

  However, the above-described conventional technology has a problem in that the time during which the cloud service cannot be used may become long.

  For example, image files and volumes are often managed by different physical devices. For this reason, when a large-size image file is expanded on a volume, traffic through the network is generated, which may take a long time.

  In VMware, vSphere, and the like, a volume area in which an OS (Operating System) or the like is installed is prepared in the storage, and the volume area in which the OS or the like is installed can be duplicated by copying this volume area. On the other hand, the volume area prepared in advance becomes large, and the area that can be used by the user decreases.

  Similarly, when thinking about acquiring an image file from a volume connected to a virtual machine and using it for recovery in the event of a failure, in order to create an image file safely, the image is acquired after the virtual machine is turned off. It is recommended to do. The image file acquisition may take a long time due to traffic generated through the network. For this reason, the virtual machine is stopped for a long time in order to safely back up the image file.

  The disclosed technology has been made in view of the above, and aims to shorten the time during which the cloud service cannot be used.

  The virtual resource management device disclosed in the present application includes a search unit and a duplication unit. The search unit receives a request to expand an image file storing a virtual resource designated by the user to a volume that can be operated in the storage, and is a volume that has already been expanded from the same image file and has not been updated. Search for volumes. The duplicating unit duplicates the retrieved volume and provides it to the user.

  The virtual resource management apparatus disclosed in the present application includes a volume duplication unit, an image acquisition request unit, and a deletion request unit. The volume duplication unit accepts a request to acquire an image file from the volume, and duplicates the specified volume. The image acquisition request unit requests acquisition of an image from the duplicated volume. The deletion request unit requests deletion of the duplicated volume after the acquisition of the image is completed.

  The virtual resource operation method disclosed in the present application includes a search step and a duplication step. The search process accepts a request to expand an image file storing a virtual resource designated by the user to a volume operable in the storage, and is a volume that has already been expanded from the same image file and has not been updated. Search for volumes. In the duplication step, the retrieved volume is duplicated and provided to the user.

  Further, the virtual resource operation method disclosed in the present application includes a volume duplication process, an image acquisition request process, and a deletion request process. The volume duplication process accepts a request to acquire an image file from the volume and duplicates the designated volume. The image acquisition request process requests acquisition of an image from the copied volume. The deletion request step requests deletion of the duplicated volume after the acquisition of the image is completed.

  Further, the virtual resource operation program disclosed in the present application causes a computer to execute a search procedure and a replication procedure. The search procedure accepts a request to expand an image file that stores a virtual resource specified by the user to a volume that can be operated in the storage, and is a volume that has already been expanded from the same image file and has not been updated. Search for volumes. In the duplication procedure, the retrieved volume is duplicated and provided to the user.

  The virtual resource operation program disclosed in the present application causes a computer to execute a volume duplication procedure, an image acquisition request procedure, and a deletion request procedure. The volume duplication procedure accepts a request to acquire an image file from a volume and duplicates the specified volume. The image acquisition request procedure requests acquisition of an image from the duplicated volume. The deletion request procedure requests deletion of the duplicated volume after the acquisition of the image is completed.

  According to one aspect of the disclosed virtual resource management apparatus, it is possible to reduce the time during which the cloud service cannot be used.

FIG. 1 is a diagram illustrating an example of a configuration of a virtual resource providing system according to the first embodiment. FIG. 2 is a diagram for explaining the processing operation in the virtual resource providing system. FIG. 3 is a diagram for explaining the processing operation in the virtual resource providing system. FIG. 4 is a diagram for explaining the processing operation in the virtual resource providing system. FIG. 5 is a diagram for explaining the processing operation in the virtual resource providing system. FIG. 6 is a diagram for explaining the resource management function DB and the resource management function unit realized by the virtual resource management apparatus. FIG. 7 is a diagram illustrating an example of a data structure of physical device information. FIG. 8 is a diagram illustrating an example of a data structure of virtual resource information. FIG. 9 is a flowchart illustrating a processing procedure performed by the resource management function unit. FIG. 10 is a flowchart illustrating a processing procedure performed by the resource management function unit. FIG. 11 is a diagram illustrating a computer that executes a virtual resource operation program.

  Hereinafter, embodiments of the disclosed virtual resource management apparatus, virtual resource operation method, and virtual resource operation program will be described in detail with reference to the drawings. The invention disclosed by this embodiment is not limited.

(First embodiment)
FIG. 1 is a diagram illustrating an example of a configuration of a virtual resource providing system according to the first embodiment. As illustrated in FIG. 1, the virtual resource providing system includes a user terminal 101, a provider operator terminal 102, a storage 103 a, a storage 103 b, an IaaS controller 104, and a virtual resource management device 105. In the case where the storage 103a and the storage 103b are not distinguished, they are described as the storage 103. Further, the number of storages 103 included in the virtual resource providing system is not limited to the number shown in FIG. 1 and can be arbitrarily changed. Although not shown in FIG. 1, the virtual resource providing system includes a physical server or the like that can generate a virtual resource. In addition, physical servers and storage may be collectively referred to as “physical equipment”.

  The user terminal 101 is a terminal used by the user, and requests the virtual resource management apparatus 105 to operate a virtual resource according to a user instruction. The operator operator terminal 102 is a terminal used by the operator of the virtual resource providing system, and requests the virtual resource management device 105 to operate the virtual resource in accordance with an operator instruction, for example. The storage 103 is, for example, a storage device, and receives a virtual resource operation instruction from the IaaS controller 104 and operates the virtual resource. For example, the storage 103 creates a volume by expanding the image file. For example, the storage 103 generates an image file from the volume. The “image file” referred to here is a file in which the contents of the disc are combined into one. In other words, the “image file” is a file in which information stored in the disc is collected into one. For example, the VM indicates information including a VM OS, a program used by the VM, data, and the like. Also, the VM cannot directly access information stored in the image file. Further, the “volume” is a storage area that the VM can access such as reading and writing, and the image file information is expanded on the volume, and becomes available from the VM. The storage 103 may be divided into a storage device and a storage server that receives requests from an open stack or the like.

  The IaaS controller 104 is connected to the storage 103 and the virtual resource management device 105. The IaaS controller 104 is a device having a CPU (Central Processing Unit), a memory, a data holding area, and a network communication function. The IaaS controller 104 receives a virtual resource operation request from the virtual resource management apparatus 105, and instructs the storage 103 to operate the virtual resource based on the received operation request. For example, the IaaS controller 104 is an open stack or the like.

  The virtual resource management apparatus 105 is connected to the user terminal 101, the operator operator terminal 102, the storage 103, and the IaaS controller 104. The virtual resource management apparatus 105 is an apparatus having a CPU, a memory, a data holding area, and a network communication function. For example, as shown in FIG. 1, the virtual resource management apparatus 105 includes a resource management function DB (Data Base) 106. And a resource management function unit 107.

  For example, when a virtual resource operation is requested from the user terminal 101 or the operator operator terminal 102, such a virtual resource management apparatus 105 uses a virtual resource operation request and information in the resource management function DB 106, Mediates the operation of virtual resources. For example, the virtual resource management apparatus 105 mediates an operation for expanding an image file (also simply referred to as “image”) to generate a volume and an operation for acquiring an image file from the volume.

  Next, processing operations in such a virtual resource providing system will be described with reference to FIGS. 2 to 5 are diagrams for explaining processing operations in the virtual resource providing system. Here, the image development processing operation will be described with reference to FIGS. 2 and 3.

  As shown in FIG. 2, the user terminal 101 or the operator operator terminal 102 transmits a volume creation request to the resource management function unit 107 (step S1). The resource management function unit 107 refers to the resource management function DB 106 (step S2) and acquires physical device information and virtual resource information (step S3). As a result, the resource management function unit 107 selects a storage for generating a volume with reference to the specified volume generation request.

  Next, the resource management function unit 107 searches for a volume cache in the selected storage (step S4). The “volume cache” is a volume developed from a designated image file and indicates a volume that has not been updated.

  FIG. 2 shows a case where the resource management function unit 107 determines that the volume cache exists in the storage 103a. In this case, the resource management function unit 107 requests the storage 103a to duplicate the volume (step S5).

  Then, the storage 103a duplicates the volume (step S6) and notifies the resource management function unit 107 that the volume duplication has been completed (step S7). Subsequently, the resource management function unit 107 notifies the user terminal 101 or the operator operator terminal 102 that the volume duplication has been completed (step S8).

  Next, FIG. 3 shows a processing operation when the resource management function unit 107 determines that the volume cache does not exist in any storage 103 in step S4. Note that the processing operations from step S1 to step S4 shown in FIG. 3 are the same as the processing operations from step S1 to step S4 shown in FIG.

  As shown in FIG. 3, when there is no volume cache, the resource management function unit 107 requests the IaaS controller 104 to create a volume from an image (step S15). Here, a case where the designated image file exists in the storage 103b and a volume is expanded from the image file to the storage 103a will be described. The IaaS controller 104 requests the storage 103a to create a volume (step S16), and requests the storage 103b to transfer the image file to the storage 103a (step S17).

  The storage 103b transfers the image file to the storage 103a (step S18), and the storage 103a generates a volume from the image file (step S19). Then, the storage 103a notifies the IaaS controller 104 that the volume generation is completed (step S20), and then the IaaS controller 104 notifies the resource management function unit 107 that the volume generation is completed (step S20). S21). Then, the resource management function unit 107 notifies the user terminal 101 or the operator operator terminal 102 that the volume generation has been completed (step S22). Thereby, the user can use the generated volume as a volume for the user.

  In addition, the resource management function unit 107 requests the IaaS controller 104 to create a volume cache from the same image after the generation of the user volume is completed. Here, since the volume cache may be registered while the volume is being generated from the image file, the resource management function unit 107 determines again whether or not the volume cache exists. For example, the resource management function unit 107 refers to the resource management function DB 106 (step S23), and acquires physical device information and virtual resource information (step S24). Then, the resource management function unit 107 determines again whether or not a volume cache exists (step S25). If the resource management function unit 107 determines that there is no volume cache, the resource management function unit 107 requests the IaaS controller 104 to generate a volume cache (step S26).

  The IaaS controller 104 requests the storage 103a to create a volume cache (step S27), and requests the storage 103b to transfer the image file to the storage 103a (step S28).

  The storage 103b transfers the image file to the storage 103a (step S29), and the storage 103a generates a volume cache from the image file (step S30). Then, the storage 103a notifies the IaaS controller 104 that the generation of the volume cache has been completed (step S31), and then the IaaS controller 104 notifies the resource management function unit 107 that the generation of the volume cache has been completed. (Step S32). Then, the resource management function unit 107 notifies the user terminal 101 or the operator operator terminal 102 that the generation of the volume cache has been completed (step S33). As a result, the resource management function unit 107 can generate a volume for a user with a short waiting time when requested to expand an image file for which a volume cache has been generated.

  Subsequently, an image acquisition processing operation will be described with reference to FIGS. 4 and 5. As illustrated in FIG. 4, the user terminal 101 or the operator operator terminal 102 transmits an image acquisition request to the resource management function unit 107 (step S41). The resource management function unit 107 refers to the resource management function DB 106 (step S42), and acquires physical device information and virtual resource information (step S43). Thereby, the resource management function unit 107 searches the storage 103 in which the designated volume exists.

  Next, the resource management function unit 107 determines whether to generate a snapshot (step S44). For example, the resource management function unit 107 determines whether to generate a snapshot from the processing time. Here, when generating a snapshot, the power-off time is shortened, but the overall processing time is lengthened. On the other hand, when the snapshot is not generated, the power-off time is not shortened as compared with the case where the snapshot is generated, but the entire processing time is shortened. In other words, the resource management function unit 107 determines that a snapshot is generated when the power-off time is set to be short, and the snapshot is generated when the overall processing time is set to be short. It is determined that no shot is generated. Note that the resource management function unit 107 may receive an instruction from the user as to whether to generate a snapshot. Note that “snapshot” is a mechanism for realizing recording of “a certain point in time” of a volume. For example, by using a mechanism such as copy-on-first-write, high-speed acquisition can be performed by a storage product. . In other words, a snapshot is a difference file. For example, both an initial volume and a snapshot are used at the time of restoration.

  FIG. 4 shows a case where the resource management function unit 107 determines not to generate a snapshot. In this case, the resource management function unit 107 requests the storage 103a to duplicate the volume (step S45). Then, the storage 103a duplicates the volume and generates an intermediate volume (step S46). The “intermediate volume” is a volume generated by duplicating a volume used in the VM, and finally indicates a volume to be deleted.

  The storage 103a notifies the resource management function unit 107 that the volume has been copied (step S47). Subsequently, the resource management function unit 107 notifies the user terminal 101 or the operator operator terminal 102 that the VM can be safely turned on (step S48).

  Further, the resource management function unit 107 requests the IaaS controller 104 to acquire an image (step S49). Here, a case where the designated volume exists in the storage 103a and an image file acquired from this volume is generated in the storage 103b will be described. The IaaS controller 104 requests the storage 103a to transfer the volume to the storage 103b (step S50), and requests the storage 103b to generate an image file (step S51).

  Then, the storage 103a transfers the volume to the storage 103b (step S52), and the storage 103b generates an image file (step S53). The storage 103b notifies the IaaS controller 104 that image acquisition has been completed (step S54). Further, the IaaS controller 104 notifies the resource management function unit 107 that the image acquisition has been completed (step S55). Then, the resource management function unit 107 notifies the user terminal 101 or the operator operator terminal 102 that the image acquisition has been completed (step S56).

  Further, the resource management function unit 107 requests the IaaS controller 104 to delete the intermediate volume (step S57). The IaaS controller 104 requests the storage 103a to delete the intermediate volume (step S58). The storage 103a deletes the intermediate volume (step S59), and notifies the IaaS controller 104 that the intermediate volume has been deleted (step S60). Then, the IaaS controller 104 notifies the resource management function unit 107 that the intermediate volume has been deleted (step S61).

  Next, FIG. 5 illustrates a case where the resource management function unit 107 determines to generate a snapshot in step S44. The processing operations from step S41 to step S44 shown in FIG. 5 are the same as the processing operations from step S41 to step S44 shown in FIG.

  As shown in FIG. 5, the resource management function unit 107 requests the IaaS controller 104 to generate a snapshot (step S71). Here, a case where the designated volume exists in the storage 103a and an image file acquired from this volume is generated in the storage 103b will be described. The IaaS controller 104 requests the storage 103a to generate a snapshot (step S72).

  The storage 103a generates a snapshot (step S73), and notifies the IaaS controller 104 that the snapshot has been generated (step S74). Then, the IaaS controller 104 notifies the resource management function unit 107 that the snapshot has been generated (step S75). Subsequently, the resource management function unit 107 notifies the user terminal 101 or the operator operator terminal 102 that the VM can be safely turned on (step S76).

  The resource management function unit 107 requests the IaaS controller 104 to generate an intermediate volume (step S77). The IaaS controller 104 requests the storage 103a to generate an intermediate volume (step S78), and the storage 103a generates an intermediate volume from the snapshot (step S79). Then, the storage 103a notifies the IaaS controller 104 that the intermediate volume has been generated (step S80). Further, the IaaS controller 104 notifies the resource management function unit 107 that the intermediate volume has been generated (step S81).

  Subsequently, the resource management function unit 107 requests the IaaS controller 104 to acquire an image, and requests the IaaS controller 104 to delete the intermediate volume after the image acquisition is completed. The processing operation from step S82 to step S94 is the same as the processing operation from step S49 to step S61 shown in FIG.

  After the deletion of the intermediate volume is completed, the resource management function unit 107 requests the IaaS controller 104 to delete the snapshot (step S95). Then, the IaaS controller 104 requests the storage 103a to delete the snapshot (step S96). Thereby, the storage 103a deletes the snapshot (step S97), and notifies the IaaS controller 104 that the snapshot has been deleted (step S98). The IaaS controller 104 notifies the resource management function unit 107 that the snapshot has been deleted (step S99).

  Next, the resource management function DB 106 and the resource management function unit 107 realized by the virtual resource management apparatus 105 will be described with reference to FIG. FIG. 6 is a diagram for explaining the resource management function DB 106 and the resource management function unit 107 realized by the virtual resource management apparatus 105.

  As shown in FIG. 6, the resource management function DB 106 stores physical device information 106a and virtual resource information 106b. The physical device information 106 a is information in which virtual resources existing in the storage 103 are associated as information about the storage 103.

  FIG. 7 is a diagram illustrating an example of the data structure of the physical device information 106a. As illustrated in FIG. 7, the physical device information 106a is information in which “physical device” and “virtual resource” are associated with each other. Here, “physical device” stored in the physical device information 106 a indicates an identifier for uniquely identifying the storage 103. For example, data values such as “0001” and “0002” are stored in “physical equipment”. The “virtual resource” stored in the physical device information 106 a indicates the type of virtual resource that exists in the storage 103. For example, data values such as “image A, image B” and “volume A” are stored in “virtual resource”.

  As an example, the physical device information 106a illustrated in FIG. 7 indicates that the virtual resources “image A” and “image B” exist in the storage 103 having the identifier “0001”. In the following, it is assumed that volume A is generated by expanding image A, and volume B is generated by expanding image B.

  Returning to FIG. The virtual resource information 106b is information indicating the presence or absence of a volume cache for the image file, the storage 103 in which the image file exists, and the like. FIG. 8 is a diagram illustrating an example of a data structure of the virtual resource information 106b. As shown in FIG. 8, the virtual resource information 106b is information in which “virtual resource”, “volume cache presence / absence”, and “volume cache storage” are associated with each other.

  Here, the “virtual resource” stored in the virtual resource information 106b indicates the type of the virtual resource. For example, data values such as “image A” and “image B” are stored in “virtual resource”.

  The “volume cache presence / absence” stored in the virtual resource information 106b indicates whether a volume cache has been generated for the image file. For example, “Presence / absence of volume cache” stores data values such as “present” indicating that a volume cache has been generated for an image file, and “not present” indicating that a volume cache has not been generated for an image file. Is done.

  “Volume cache storage” indicates the storage 103 in which the volume cache exists. For example, “volume cache storage” stores an identifier for uniquely identifying the storage 103 such as “0002,000X”.

  For example, the virtual resource information 106b shown in FIG. 8 is generated in the storage 103 identified by “0002” and the storage 103 identified by “000X” for the virtual resource “image A”. Indicates. That is, the volume cache can be generated from the image file to the plurality of storages 103. Note that a volume can be copied only from a volume cache existing in the same storage 103. The virtual resource information 106b indicates that a volume cache is not generated for the virtual resource “image B”.

  Returning to FIG. The resource management function unit 107 includes a reception unit 107a, an image file development unit 107b, and an image file generation unit 107c. The accepting unit 107 a accepts a virtual resource operation request from the user terminal 101 or the operator operator terminal 102. The reception unit 107a transfers the received virtual resource operation request to the image file development unit 107b and the image file generation unit 107c.

  The image file development unit 107b includes a search unit 108, a duplication unit 109, and a request unit 110, and controls processing for developing an image file and generating a volume.

  The search unit 108 receives a request to expand the image file storing the virtual resource designated by the user to a volume that can be operated in the storage, and is a volume that has already been expanded from the same image file and has not been updated. Search for a volume (volume cache). For example, the search unit 108 refers to the resource management function DB 106 and acquires the physical device information 106a and the virtual resource information 106b. Then, the search unit 108 refers to the specified volume generation request and selects a storage for generating the volume. Subsequently, the search unit 108 searches for a volume cache in the selected storage.

  The duplication unit 109 duplicates the volume cache searched by the search unit 108 and provides it to the user.

  When the volume cache does not exist as a result of the search by the search unit 108, the request unit 110 requests the expansion from the designated image file to the volume, and provides the volume to the user. In addition, the request unit 110 further requests the generation of a new volume cache from the designated image file after the expansion to the volume.

  Further, when the request unit 110 requests the generation of a new volume cache from the specified image file after expansion to the volume, the number of other volume caches existing in the storage exceeds a predetermined number. In this case, one of the other volume caches is deleted and the generation of the new volume cache is requested. For example, the request unit 110 requests to delete the old one of the other volume caches. The request unit 110 may request to delete another volume cache with low access frequency.

  The image file generation unit 107c includes a volume duplication unit 111, an image acquisition request unit 112, a deletion request unit 113, and a snapshot acquisition request unit 114, and controls processing for acquiring an image file from a volume.

  The volume duplication unit 111 accepts a request to acquire an image file from the volume, duplicates the specified volume, and requests the storage 103 to generate an intermediate volume.

  The image acquisition request unit 112 requests acquisition of an image from the copied intermediate volume. The image acquisition request unit 112 requests the creation of an intermediate volume from the acquired snapshot and also requests the acquisition of an image from the created intermediate volume.

  The deletion request unit 113 requests deletion of the copied intermediate volume after completion of image acquisition. The deletion request unit 113 requests the deletion of the created intermediate volume and the deletion of the acquired snapshot after completing the acquisition of the image.

  The snapshot acquisition request unit 114 requests acquisition of a snapshot from the designated volume.

  FIG. 9 is a flowchart illustrating a processing procedure performed by the resource management function unit 107. FIG. 9 illustrates a processing procedure of the image file development unit 107b when a volume generation is requested from an image as a virtual resource operation request.

  As illustrated in FIG. 9, the search unit 108 searches the storage 103 that generates a volume (step S <b> 101). Then, the search unit 108 determines whether a volume cache exists in the storage 103 (step S102). If the search unit 108 determines that a volume cache exists in the storage 103 (step S102, Yes), the replication unit 109 requests the storage 103 to replicate the volume from the volume cache (step S103). That is, the duplication unit 109 requests the storage 103 in which the volume cache exists to duplicate the volume cache.

  On the other hand, when the search unit 108 determines that there is no volume cache in the storage 103 (step S102, No), the request unit 110 requests the IaaS controller 104 to generate a volume from the image file (step S104). That is, the request unit 110 requests the IaaS controller 104 to generate a volume from the image file.

  Further, the request unit 110 determines whether or not a volume cache exists in the storage 103 (step S105). Since the request unit 110 may register a volume cache while generating a volume from an image file, the request unit 110 determines again in step S105 whether a volume cache exists.

  If the request unit 110 determines that there is a volume cache in the storage 103 (step S105, Yes), the process ends. On the other hand, when the request unit 110 determines that there is no volume cache in the storage 103 (No in step S105), the request unit 110 determines whether the number of volume caches in the storage exceeds the upper limit (step S106).

  If it is determined that the number of volume caches in the storage does not exceed the upper limit (No at Step S106), the process proceeds to Step S108. On the other hand, when the request unit 110 determines that the number of volume caches in the storage exceeds the upper limit (step S106, Yes), the request unit 110 requests the IaaS controller 104 to delete the old volume cache (step S107). The request unit 110 requests the IaaS controller 104 to generate a volume cache from the image file (step S108).

  FIG. 10 is a flowchart illustrating a processing procedure performed by the resource management function unit 107. FIG. 10 illustrates a processing procedure of the image file generation unit 107c when an image generation is requested from a volume as a virtual resource operation request.

  As illustrated in FIG. 10, when the volume replication unit 111 is requested to generate an image from a volume, the volume replication unit 111 determines whether to create a snapshot (step S <b> 201). For example, in response to an image file acquisition request from the user, the volume duplicating unit 111 determines whether to create a snapshot using a parameter or the like. For example, since the snapshot is acquired at high speed, the parameter is set so that the snapshot is selected when the power-off time of the VM is shortened. Although the power-off time is longer than that of the snapshot, the parameter is set so that creation of an intermediate volume is selected when the entire processing time is shortened.

  Here, if the volume replication unit 111 determines not to create a snapshot (No in step S201), the volume replication unit 111 replicates the volume from the designated volume and requests the storage 103 to generate an intermediate volume (step S202).

  Then, the volume replication unit 111 notifies the user that the VM can be safely turned on (step S203). Subsequently, the image acquisition request unit 112 requests the IaaS controller 104 to acquire an image from the intermediate volume (step S204). Then, when the image generation is completed, the deletion request unit 113 requests the IaaS controller 104 to delete the intermediate volume (step S205) and ends the process.

  On the other hand, when the volume replication unit 111 determines to create a snapshot (Yes in step S201), the snapshot acquisition request unit 114 requests the IaaS controller 104 to generate a snapshot from the specified volume (step S206). ).

  Then, the volume replication unit 111 notifies the user that the VM can be safely turned on (step S207). Subsequently, the image acquisition request unit 112 requests the IaaS controller 104 to generate an intermediate volume from the snapshot (step S208). Then, the image acquisition request unit 112 requests the IaaS controller 104 to acquire an image from the intermediate volume (step S209). Then, when the image generation is completed, the deletion request unit 113 requests the IaaS controller 104 to delete the intermediate volume (step S210). Also, the deletion request unit 113 requests the IaaS controller 104 to delete the snapshot (step S211), and ends the process.

  As described above, when creating a volume from a specific image file, the virtual resource management apparatus 105 according to the first embodiment creates a copy from a cache volume to the same storage. That is, in the virtual resource management apparatus 105 according to the first embodiment, it is possible to omit transfer via the network between the storage 103 that manages the image file and the storage that manages the volume. Thereby, a volume can be created with a short waiting time.

  Further, when there is no cache volume, the virtual resource management apparatus 105 according to the first embodiment creates a cache volume after creating a volume for the user. As a result, the cache hit rate can be increased. Here, the more frequently used image files are, the higher the cache hit rate, and the more effective.

  Further, the virtual resource management apparatus 105 according to the first embodiment deletes a cache that has an upper limit on the number and size of caches and is less frequently used. As a result, it is possible to prevent the volume area that is not for the user from becoming large, such as VMware and vSphere.

  Further, the virtual resource management apparatus 105 according to the first embodiment creates a replication volume and acquires an image from the replication volume when creating an image file from the volume. As a result, the time during which the VM is powered off can be reduced to the time during which a replica volume is created.

  Further, when creating an image file from a volume, the virtual resource management apparatus 105 according to the first embodiment creates a snapshot, creates a volume from the snapshot, and acquires an image. As a result, an image can be acquired while reducing the time during which the VM is powered off.

(Second Embodiment)
Although the embodiments of the present invention have been described so far, the present invention may be implemented in other embodiments besides the above-described embodiments. Therefore, other embodiments will be described below.

(System configuration)
Also, among the processes described in this embodiment, all or part of the processes described as being performed automatically can be performed manually, or the processes described as being performed manually can be performed. All or a part can be automatically performed by a known method. In addition, the processing procedures, control procedures, specific names, and information including various data and parameters shown in the above-mentioned documents and drawings (for example, FIGS. 1 to 10) are optional unless otherwise specified. Can be changed.

  Further, each component of each illustrated apparatus is functionally conceptual, and does not necessarily need to be physically configured as illustrated. That is, the specific form of distribution / integration of each device is not limited to the one shown in the figure, and all or a part of the distribution / integration may be functionally or physically distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. For example, in the virtual resource management apparatus 105, the resource management function unit 107 may be configured to include a reception unit 107a and an image file development unit 107b, or includes a reception unit 107a and an image file generation unit 107c. It may be configured as follows.

(program)
It is also possible to generate a virtual resource operation program in which the processing executed by the virtual resource management apparatus 105 according to the first embodiment is described in a language that can be executed by a computer. In this case, when the computer executes the virtual resource operation program, the same effect as in the above embodiment can be obtained. Further, the virtual resource operation program is recorded on a computer-readable recording medium, and the virtual resource operation program recorded on the recording medium is read by the computer and executed, thereby realizing the same processing as in the above embodiment. May be. Hereinafter, an example of a computer that executes a virtual resource operation program that realizes the same function as that of the virtual resource management apparatus 105 illustrated in FIG. 1 and the like will be described.

  FIG. 11 is a diagram illustrating a computer 1000 that executes a virtual resource operation program. As illustrated in FIG. 11, the computer 1000 includes, for example, a memory 1010, a CPU 1020, a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These units are connected by a bus 1080.

  The memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM 1012. The ROM 1011 stores a boot program such as BIOS (Basic Input Output System). The hard disk drive interface 1030 is connected to the hard disk drive 1031. The disk drive interface 1040 is connected to the disk drive 1041. For example, a removable storage medium such as a magnetic disk or an optical disk is inserted into the disk drive 1041. For example, a mouse 1051 and a keyboard 1052 are connected to the serial port interface 1050. For example, a display 1061 is connected to the video adapter 1060.

  Here, as shown in FIG. 11, the hard disk drive 1031 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. The virtual resource operation program described in the above embodiment is stored in the hard disk drive 1031 or the memory 1010, for example.

  Further, the virtual resource operation program is stored in, for example, the hard disk drive 1031 as a program module in which a command executed by the computer 1000 is described. Specifically, a program module 1093 in which a search procedure for executing information processing similar to that of the search unit 108 described in the above embodiment and a replication procedure for executing information processing similar to that of the replication unit 109 is described Stored in the drive 1031. Alternatively, the volume duplication order for performing the same information processing as the volume duplication unit 111 described in the above embodiment, the image acquisition request procedure for executing the same information processing as the image acquisition request unit 112, and the deletion request unit 113 are the same. The program module 1093 describing the deletion request procedure for executing the information processing is stored in the hard disk drive 1031.

  Data used for information processing by the virtual resource operation program is stored as program data 1094 in, for example, the hard disk drive 1031. Then, the CPU 1020 reads the program module 1093 and the program data 1094 stored in the hard disk drive 1031 to the RAM 1012 as necessary, and executes the above-described procedures.

  Note that the program module 1093 and the program data 1094 related to the virtual resource operation program are not limited to being stored in the hard disk drive 1031, but are stored in a removable storage medium, for example, by the CPU 1020 via the disk drive 1041 or the like. It may be read out. Alternatively, the program module 1093 and the program data 1094 related to the virtual resource operation program are stored in another computer connected via a network such as a LAN (Local Area Network) or a WAN (Wide Area Network), and the network interface 1070 is stored. Via the CPU 1020.

(Other)
The specific program described in this embodiment can be distributed via a network such as the Internet. The specific program can also be executed by being recorded on a computer-readable recording medium such as a hard disk, a flexible disk (FD), a CD-ROM, an MO, or a DVD, and being read from the recording medium by the computer.

105 Virtual Resource Management Device 106 Resource Management Function DB
106a Physical device information 106b Virtual resource information 107 Resource management function unit 107a Reception unit 107b Image file development unit 107c Image file generation unit 108 Search unit 109 Replication unit 110 Request unit 111 Volume replication unit 112 Image acquisition request unit 113 Deletion request unit 114 Snap Shot acquisition request unit 1000 Computer 1010 Memory 1011 ROM
1012 RAM
1020 CPU
1030 Hard disk drive interface 1031 Hard disk drive 1040 Disk drive interface 1041 Disk drive 1050 Serial port interface 1051 Mouse 1052 Keyboard 1060 Video adapter 1061 Display 1070 Network interface 1080 Bus 1091 OS
1092 Application program 1093 Program module 1094 Program data

Claims (8)

Accepts a request to expand an image file that stores a virtual resource specified by the user to a volume that can be operated in the storage, and searches for a volume that has already been expanded from the same image file and has not been updated. A search section;
A virtual resource management device comprising: a duplicating unit that duplicates the searched volume and provides the volume to the user.   If the volume does not exist as a result of the search by the search unit, the specified image file is requested to be expanded to a volume, the volume is provided to the user, and after the expansion to the volume, the specified The virtual resource management apparatus according to claim 1, further comprising a request unit that further requests generation of a new volume from the image file that has been processed. A volume duplication unit that accepts a request to obtain an image file from a volume and duplicates the specified volume;
An image acquisition request unit that requests acquisition of an image from the duplicated volume;
A virtual resource management apparatus comprising: a deletion request unit that requests deletion of the duplicated volume after completion of acquisition of the image. It further has a snapshot acquisition request unit that requests acquisition of a snapshot from a specified volume,
The image acquisition request unit requests creation of a volume from the acquired snapshot, and requests acquisition of an image from the created volume.
The virtual resource management apparatus according to claim 3, wherein the deletion request unit requests deletion of the created volume after the completion of acquisition of the image, and requests deletion of the acquired snapshot. . Accepts a request to expand an image file that stores a virtual resource specified by the user to a volume that can be operated in the storage, and searches for a volume that has already been expanded from the same image file and has not been updated. Search process;
A virtual resource operation method comprising: a duplication step of duplicating the retrieved volume and providing the volume to the user. A volume duplication process that accepts a request to obtain an image file from a volume and duplicates the specified volume;
An image acquisition requesting process for requesting acquisition of an image from the duplicated volume;
And a deletion requesting step for requesting deletion of the duplicated volume after completion of acquisition of the image. Accepts a request to expand an image file that stores a virtual resource specified by the user to a volume that can be operated in the storage, and searches for a volume that has already been expanded from the same image file and has not been updated. Search procedure and
A virtual resource operation program for causing a computer to execute a duplication procedure for duplicating the retrieved volume and providing it to the user. A volume replication procedure that accepts a request to retrieve an image file from a volume and replicates the specified volume;
An image acquisition request procedure for requesting acquisition of an image from the duplicated volume;
A virtual resource operation program for causing a computer to execute a deletion request procedure for requesting deletion of the duplicated volume after completion of acquisition of the image.

Images