This application is based upon and claims the benefit of priority of the prior Japanese Patent Application No. 2012-208133, filed on Sep. 21, 2012, the entire contents of which are incorporated herein by reference.
The embodiment discussed herein is related to an information processing system, a recording medium, and an information processing method.
As the use of cloud computing, a service is provided by defining specifications of a logical machine by a service administrator who manages the service, requesting an infrastructure administrator who manages a cloud platform to assign physical resources for the specifications, and executing the logical machine to which the physical resources have been assigned.
When an infrastructure administrator who manages the cloud platform 10 receives information of a specification of a logical machine and a request to assign a physical resource from the service administrator, the infrastructure administrator confirms a usage status of a resource pool 60 managed by the infrastructure administrator. If the physical resource is enabled to be assigned for the requested specification, the physical resource is assigned to the logical machine, and the logical machine is executed on the cloud platform 10. Since a plurality of logical machines are executed on the cloud platform 10, the infrastructure administrator adjusts assignments of physical resources based on execution states of logical machines in order to ensure the requested specification. In addition, the infrastructure administrator causes mirroring of a disk to be executed in order to have redundancy of data to be managed, switches disks, couples a disk, and the like. The resource pool 60 managed by the infrastructure administrator includes a CPU resource pool 61 including CPU resources, a memory resource pool 62 including memory resources, a disk resource pool 63 including disk resources, and a physical server 64 such as a rack server or a blade server. An assignment and adjustment of a physical resource included in the resource pool 60, a coupling and switching of a disk, and the like are executed under the authority of an infrastructure supervisor.
Assignments of disks to logical machines on the cloud platform 10 includes a shared assignment that causes a disk to be shared by multiple logical machines, and a dedicated assignment that causes a specific disk to be assigned to a specific logical machine. For example, in order to couple a logical machine to a disk storing information to be disclosed to multiple logical machines or a disk storing information to be shared and used, the service administrator defines a specification of a disk resource and defines that an assignment of the disk is the shared assignment. If the shared assignment is defined for logical machines, the infrastructure administrator permits a disk to be shared by the logical machines.
In order to couple a logical machine to a disk storing information specific to an operating system (OS) of the logical machine or a disk storing information that is not to be disclosed to another logical machine, the service administrator defines a specification of a disk resource and defines that an assignment of the disk is the dedicated assignment. The infrastructure administrator assigns, in a dedicated manner, the disk to the logical machine for which the dedicated assignment is defined. In this case, even if the logical machine does not access the disk, another logical machine is not coupled to the disk. For example, when the logical machine is stopped by the service administrator, assignments of a CPU resource and a memory resource to the stopped logical machine are released, and the resources become physical resources that are enabled to be assigned to another logical machine. The dedicated assignment of a disk to the stopped logical machine is not released in order to inhibit information specific to the logical machine from being overwritten by accessing the interested disk by another logical machine.
When the service administrator requests the infrastructure administrator to assign a physical resource, a requested specification is only registered on the side of the infrastructure administrator, and the physical resource is not assigned. When the service administrator requests the infrastructure administrator to activate a logical machine, a CPU resource, a memory resource, and the like are assigned. This is due to the fact that finite physical resources are released in a time period in which the logical machine is not executed in order to effectively use the physical resources.
As described above, in order to ensure consistency of data based on an usage status of a disk, a logical machine and the disk are associated with each other so as to ensure a coupling of the logical machine to the disk in an assignment mode and are registered when specifications of the logical machine are registered by the infrastructure administrator. When activation of the logical machine is requested by the service administrator, the logical machine is coupled to the associated disk and the disk becomes accessible in the mode associated to the disk.
As a technique for executing exclusive control so as to cause a resource to be excessively shared by multiple physical servers, the following technique is known. When a bit that corresponds to a resource to be accessed and is stored in a management region corresponding to a certain server executed on a common device is on, and a bit that corresponds to the interested resource and is stored in a management region corresponding to another server is off, the technique causes the access to be executed as success of the exclusive control.
Japanese Laid-open Patent Publication No. 2003-85026 is an example of related art.
According to one exemplary embodiment, the disclosure is directed to an information processing system that sets, coupling information defining a logically coupling corresponding to a first disk, to an uncoupled state indicating that a first logical machine associated with the first disk and the first disk are not coupled, in response to a request to stop the first logical machine, and releases a coupling between the first logical machine and the first disk based on the uncoupled state set in the coupling information.
The object and advantages of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the claims.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not restrictive of the invention, as claimed.
First, inventors' ideas regarding cloud computing are described. For cloud computing, an infrastructure administrator who manages a cloud platform has an authority to switch and couple disks. Thus, a service administrator does not change a disk assigned to a logical machine to another disk without approval of the infrastructure administrator.
For example, when a logical machine that is coupled to a disk is stopped due to an error of the disk or the like, the coupling of the disk to the logical machine is not released without the authority of the infrastructure administrator. Thus, even if an assignment of the logical machine to another disk is registered, the service administrator waits for the infrastructure administrator to release the disk in order to restart a service. In this case, if support for the infrastructure administrator is not sufficient, the service may be stopped during the time when the disk is not completely released.
According to the embodiment described later, a coupling of a logical machine to a disk may be released by a computer that provides a request to stop the logical machine via a coupling information defining a logically coupling between a logical machine and a disk associated with the logical machine and referred when a physically coupling between the logical machine and a disk is controlled.
The service management server 100 is a computer that includes a CPU 110, a memory 120, a storage device 130, an NIC 140, and a bus 150. The bus 150 couples the CPU 110, the memory 120, the storage device 130, and the NIC 140 to each other. The CPU 110 includes at least one processor that executes a process. The memory 120 is, for example, a random access memory (RAM). The storage device 130 is a nonvolatile memory such as a read only memory (ROM) or a flash memory or a magnetic disk device such as a hard disk drive (HDD). The NIC 140 is an interface circuit that transmits and receives data to and from an external device. The service management server 100 communicates with the infrastructure management server 200 through the NIC 140.
A program in which a process of controlling the service management server 100 is described is stored in the memory 120. An operation of the service management server 100 is controlled by causing the CPU 110 to execute the program stored in the memory 120. The service management server 100 defines specifications of a logical machine as illustrated in
The infrastructure management server 200 is a computer that includes a CPU 210, a memory 220, a storage device 230, an NIC 240, and a bus 250. The bus 250 couples the CPU 210, the memory 220, the storage device 230, and the NIC 240 to each other. The CPU 210 includes at least one processor that executes a process. The memory 220 is, for example, a RAM. The storage device 230 is a nonvolatile memory such as a ROM or a flash memory or a magnetic disk device such as an HDD. The NIC 240 is an interface circuit that transmits and receives data to and from an external device. The infrastructure management server 200 communicates with the service management server 100 and the resource pool 300 through the NIC 240.
A program in which a process of controlling the infrastructure management server 200 is described, and a program in which processes illustrated in
The server 310 is a computer that includes a CPU 311, a memory 312, a storage device 313, an NIC 314, and a bus 315. The bus 315 couples the CPU 311, the memory 312, the storage device 313, and the NIC 314 to each other. The CPU 311 includes at least one processor that executes a process. The memory 312 is, for example, a RAM. The NIC 314 is an interface circuit that transmits and receives data to and from an external device. The server 310 communicates with the infrastructure management server 200 and the resource pool 330 through the NIC 314.
A program in which a process of controlling an operation of the server 310 is described, and a program for executing a logical machine in accordance with a resource assigned by the infrastructure management server 200, are stored in the memory 312. An operation of the server 310 is controlled by causing the CPU 312 to execute the programs stored in the memory 312, and a logical machine is executed by the server 310. The server 310 is coupled to a network 350 through the NIC 314 and communicates with a computer coupled to the network 350.
The resource pool 300 includes the server 320. The server 320 has substantially the same configuration as the management target 310, and a description thereof is omitted. Servers to be managed, which are included in the resource pool 300, are not limited to the servers 310 and 320. The resource pool 300 may include only a single server to be managed or include the servers 310 and 320 and one or more other servers to be managed.
The disk resource pool 330 includes disks 331, 332, and 333. The disks 331, 332, and 333 are nonvolatile memories such as ROMs or flash memories or magnetic disk devices such as HDDs. In the embodiment, disks that are included in the disk resource pool 330 are not limited to the disks 331, 332, and 333. The disk resource pool 330 may include only a single disk or include the disks 331, 332, and 333 and one or more other disks.
When receiving information of specifications of a logical machine and a request to assign a physical resource from the service management server 100, the infrastructure management server 200 confirms a usage status of the resource pool 300 managed by the infrastructure management server 200. If the physical resource is enabled to be assigned in accordance with the requested specifications, the physical resource is assigned to the logical machine, and the logical machine is executed on the resource pool 300. Since multiple logical machines are executed on the resource pool 300, the infrastructure administrator adjusts assignments of physical resources based on execution states of logical machines in order to ensure the requested specifications. In addition, the infrastructure administrator causes mirroring of a disk to be executed in order to have redundancy of data to be managed, switches disks, couples a disk, and the like. As described above, the logical machine is executed as a logical server providing a desired service.
The physical resources that are the CPUs and the memories and included in the servers 310 and 320 correspond to the CPU resource pool 61 and the memory resource pool 62, which are described with reference to
The identifier of the logical machine is an identifier that is added by the service administrator and identifies the logical machine. The logical machine that is executed as a logical machine is uniquely identified by the logical machine identifier. The type of the logical machine is information that indicates whether the logical machine is a physical machine or a virtual machine. For example, if the type of the logical machine indicates “physical”, a rack server, a blade server, or the like, which satisfies specifications requested by the server management server 100, is assigned, and the logical machine is executed as a physical machine. If the type of the logical machine indicates “virtual”, a resource that satisfies the specifications requested by the server management servers 100 is assigned, and the logical machine is executed as a virtual machine.
The state of the logical machine indicates whether or not the interested logical machine is executed on the server 310 in response to an activation request from the service management server 100. For example, if the type of the logical machine indicates a “currently executed” state, the logical machine is currently executed on the server 310 in response to the activation request from the service management server 100. If the type of the logical machine indicates a “defined” state, the service management server 100 provides a request to assign a resource to the logical machine, the logical machine is registered in the logical machine management information 400, and the service management server 100 does not provide a request to activate the logical machine, or provides a request to stop the logical machine and the logical machine is not executed on the server 310.
The information of the CPU resource and the information of the memory resource indicate specifications, requested by the service management server 100, of the logical machine. The information of the network resource indicates an association of an NIC number with a virtual local area network (VLAN).
In addition, the logical machine management information 400 indicates a relationship between a logical unit number (LUN) and the identifier of a disk and indicates an assignment mode of the disk. As the assignment mode, a dedicated assignment mode, a shared assignment mode, or an exclusively shared assignment mode is set. If the dedicated assignment mode is set, a specific disk resource is assigned to only a specific logical machine, as described with reference to
In addition,
In addition,
The disk identifier is an identifier that is added by the infrastructure management server 200 and identifies a disk. The disk is uniquely identified by the disk identifier. The disk type identifies the type of the disk using a flag indicating “existing” or “dynamic”. If the flag indicates “existing”, the flag means that an LUN that is created in advance by redundant arrays of inexpensive disks (RAID) or a disk resource management product is used by a logical machine. If the flag indicates “dynamic”, the flag means that an LUN is dynamically assigned to a logical machine from a RAID group of a RAID device by the infrastructure management server 200 upon registration of the logical machine.
The disk size indicates the capacity of the disk. The assignment mode indicates the “dedicated” assignment mode, the “shared” assignment mode, the “exclusively shared” assignment mode, or “not assigned”. The disk resource management information 500 also indicates an assignee logical machine. For example, the disk Disk0001 is assigned to the logical machine LS0001 as an assignee logical machine in the dedicated assignment mode, while a disk Disk0012 is assigned to the logical machine LS0001 and logical machines LS0222 and LS0256 in the shared assignment mode. A disk Disk0003 is not assigned to a logical machine, and an assignment mode of the disk Disk0003 indicates “not assigned”.
In
When the service management server 100 transmits definition information of specifications of a logical machine and a request to assign a resource to the logical machine, the infrastructure management server 200 executes a process 700 of starting to check an assignment of a disk to the logical machine. The definition information that is transmitted by the service management server 100 includes information of the identifier of the logical machine, the type of the logical machine, a CPU resource, a memory resource, an assignment of a network resource, an assignment of a disk resource, the capacity of the disk resource, the identifier of the disk, an assignment mode of the disk, and the like, which are requested as the specifications of the logical machine. The definition information is, for example, described using Extensible Markup Language (XML) and is transmitted to the infrastructure management server 200.
When the process illustrated in
For the set N (LUN), the process 702 of checking whether or not the definition information specifies the identifier of the disk to be assigned to the logical machine is executed by the logical machine managing section 600.
In the process 702, a disk requested to be assigned to the LUN N by the service management server 100 and whether or not an assignment of the disk is defined are checked based on the definition information. If the logical machine managing section 600 determines that the disk identifier is not specified by the definition information in the process 702, the process illustrated in
The process 703 of checking whether or not the disk identifier specified by the definition information exists in the disk resource management information 500 is executed by the logical machine managing section 600. Since disk resources are managed by the infrastructure management server 200, the disk requested by the service management server 100 may be already removed from the resource pool 300 by the infrastructure management server 200. Thus, in the process 703, whether or not the disk requested by the service management server 100 exists in the resource pool 300 is checked by causing the logical machine managing unit 600 to reference the disk resource management information 500 and determine whether or not the disk identifier specified by the definition information transmitted by the service management server 100 exists in the disk resource management information 500. If the logical machine managing section 600 determines that the disk identifier specified by the definition information does not exist in the process 703, the process illustrated in
The process 704 of determining whether or not an assignment mode associated with the disk identifier specified by the definition information indicates “not assigned” in the disk resource management information 500 is executed by the logical machine managing section 600. If the logical machine managing section 600 determines that the assignment mode does not indicate “not assigned” in the process 704, the process illustrated in
The process 705 of changing the assignment mode associated with the disk identifier to the assignment mode specified by the definition information in the disk resource management information 500 is executed by the disk resource managing section 610. The process 705 is executed if the logical machine managing section 600 determines that the disk specified by the definition information is not assigned to any logical machine in the process 704. Thus, even if the assignment mode specified by the definition information is any of the assignment modes, the assignment mode specified by the definition information may be set in the disk resource management information 500 in the process 705. When the process 705 is terminated, the process illustrated in
The process 706 of associating the logical machine identifier specified by the definition information with an assignee logical machine associated with the disk identifier specified by the definition information in the disk resource management information 500 is executed by the disk resource managing section 610. The assignee logical machine is associated with the disk by the process 706. When the process 706 is terminated, the process illustrated in
The process 707 of incrementing the LUN N to be checked by 1 is executed by the logical machine managing section 600 in order to check an assignment of a disk for each of LUNs for the disk resource requested by the definition information. The LUN N to be checked is changed by the process 707. When the process 707 is terminated, the process illustrated in
The process 708 of determining whether or not the set N (LUN) is equal to or smaller than the maximum value of LUNs specified by the definition information is executed by the logical machine managing section 600. If the logical machine managing section 600 determines that the set N is equal to or smaller than the maximum value in the process 708, another LUN that is not to be checked may remain, and thus the process illustrated in
If the logical machine managing section 600 determines that the assignment mode does not indicate “not assigned” in the process 704, the process 709 of determining whether or not the assignment mode specified by the definition information is the “dedicated” assignment mode is executed by the logical machine managing section 600. If the logical machine managing section 600 determines that the assignment mode is the “dedicated” assignment mode in the process 709, the logical machine managing section 600 determines that the specified disk is already assigned in the process 704, the disk is not assigned in the “dedicated” assignment mode as indicated by the definition information, and thus the process illustrated in
The process 710 of determining whether or not the assignment mode specified by the definition information is the “exclusively shared” assignment mode is executed by the logical machine managing section 600. If the logical machine managing section 600 determines that the assignment mode is not the “exclusively shared” assignment mode, the process illustrated in
The process 711 of determining whether or not the assignment mode associated with the disk identifier specified by the definition information is set as the “exclusively shared” assignment mode in the disk resource management information 500 is executed by the logical machine managing section 600. After the logical machine managing section 600 determines that the disk specified by the definition information is already assigned in the process 704, whether or not the disk is assigned to another logical machine in the “exclusively shared” assignment mode is checked in the process 711. If the logical machine managing section 600 determines that the assignment mode is set as the “exclusively shared” assignment mode in the process 711, the logical machine managing section 600 determines that the disk is enabled to be assigned to the other logical machine (to which the disk is already assigned) and the logical machine specified by the definition information in the “exclusively shared” assignment mode, and the process illustrated in
The process 712 of determining whether or not the assignment mode of the disk specified by the definition information is set as the “shared” assignment mode in the disk resource management information 500 is executed by the logical machine managing section 600. If the logical machine managing section 600 determines that the assignment mode is set as the “shared” assignment mode, the disk is enabled to be assigned as indicated by the definition information, and the process illustrated in
The rollback process 713 of releasing the assignment of the disk is executed by the disk resource managing section 610. Even if the disk is successfully assigned to an LUN of the logical machine after the process 700, the disk may not be assigned to another LUN as a result of the processes 713, 709, 710, and 712. In this case, unless associations of assigned disks with logical machines are released, it is determined that the disks are already assigned regardless of the fact that the assignments are unsuccessful, and the disks are not enabled to be used by another logical machine. Thus, the associations of the assigned disks with the logical machines are removed from the disk resource management information 500 by the rollback process 713, and whereby the disk is enabled to be assigned to another logical machine.
After the rollback process 713 is executed, a process 714 of notifying of an error is executed by the disk resource managing section 610. In the process 714, the infrastructure management server 200 notifies the service management server 100 that the disk is not assigned to the logical machine and registration of the logical machine in the logical machine management information 400 fails.
When the series of processes are executed, the process of checking the assignment of the disk to the logical machine is terminated, and the process 715 of notifying the service management server 100 that the registration of the logical machine is completed is executed by the infrastructure management server 200.
When receiving, from the service management server 100, a request to delete a logical machine registered in the logical machine management information 400, the infrastructure management server 200 executes a process 800 of starting the process of releasing an assignment of a disk to the interested logical machine. The process illustrated in
The process 801 of checking whether or not the identifier of the disk assigned to the logical machine to be deleted is associated with the set N (LUN) in the logical machine management information 400 is executed by the logical machine managing section 600. If the disk identifier is not associated, the process illustrated in
The process 802 of deleting the identifier of the logical machine requested to be deleted by the service management server 100 from an “assignee logical machine” associated to the interested disk identifier is executed by the disk resource managing section 610. The association of the logical machine to be deleted with the assigned disk is released by the process 802.
A process 803 of determining whether or not the assignee logical machine associated with the interested disk identifier is deleted in the disk resource management information 500 is executed by the disk resource managing section 610. If the disk resource managing section 610 determines that the assignee logical machine associated with the interested disk identifier exists, the process illustrated in
The process 804 of changing an assignment mode associated with the interested disk identifier to “not assigned” in the disk resource management information 500 is executed by the disk resource managing section 610.
The process 805 of changing the set LUN is executed by the logical machine managing section 600 in order to check a disk assigned to another LUN of the logical machine requested to be deleted by the service management server 100. In the process 805, the LUN N is reduced by 1, for example.
A process 806 of determining whether or not disks for all LUNs of the logical machine requested to be deleted by the service management server 100 have been checked is executed by the logical machine managing section 600. For example, if the LUN N is reduced by 1 in the process 805, the logical machine managing section 600 determines whether or not the LUN N is a negative number in the process 806. If the logical machine managing section 600 determines that any of the disks for all the LUNs of the logical machine to be deleted is yet to be checked, the process illustrated in
When the series of processes are executed, the process 807 of terminating the process of releasing an assignment of a disk to the logical machine is executed by the infrastructure management server 200.
A process 851 of setting a state of a logical machine requested to be stopped to the “defined” state in the logical machine management information 400 is executed by the logical machine managing section 600. Although information of the logical machine requested to be stopped is left in the logical machine management information 400 by the process 851, the logical machine is not executed on the cloud platform.
A process 852 of setting coupling information of a disk associated with the logical machine requested to be stopped to the “uncoupled” state in the disk resource management information 500 is executed by the disk resource managing section 610. In the process 852, the coupling information of the disk coupled to the logical machine is updated to the “uncoupled” state, and the coupling of the logical machine to the disk is released. If the coupling information indicates the “uncoupled” state and the logical machine to which the disk of which the coupling information is updated to the “uncoupled” state is assigned is requested to be activated, the coupling of the logical machine requested to be activated to the disk is permitted. In the embodiment, when a specific process is executed so as to update the coupling information as the “uncoupled” state from the “uncoupled” state, the coupling information may be set to the “uncoupled” state.
A process 901 of checking the state of the assignment of the disk to the logical machine requested to be activated is executed by the logical machine managing section 600. In the process 901, the logical machine managing section 600 references the logical machine management information 400 and checks whether or not a disk identifier, a logical machine identifier, and an assignment mode are associated with each other for the logical machine requested to be activated. The process 901 is executed in order to check whether or not information on the logical machine to be activated has an inconsistency due to a power failure, a system failure, or the like. If the logical machine managing section 600 determines that the logical machine management information 400 has an inconsistency, the process illustrated in
The process 902 of checking whether or not the identifier of a disk associated with the logical machine to be activated exists in the disk resource management information 500 is executed by the disk resource managing section 610. In the process 902, the disk resource managing section 610 checks whether or not an assignment of the disk has an inconsistency on the assumption that the disk is temporarily assigned to the logical machine by the process illustrated in
The process 903 of checking whether or not the logical machine to be activated is associated with an assignee logical machine associated with the disk identifier checked in the process 902 is executed by the disk resource managing section 610. The process 903 is executed in order to check whether or not the information on the logical machine to be activated has an inconsistency due to a power failure, a system failure, or the like. If the disk resource managing section 610 determines that the logical machine to be activated is not associated, the process illustrated in
The process 904 of checking whether or not an assignment mode associated with the disk identifier checked in the process 902 matches an assignment mode requested, as a specification, for the logical machine to be activated is executed by the disk resource managing section 610. The process 904 is executed in order to check whether or not the information on the logical machine to be activated has an inconsistency due to a power failure, a system failure, or the like. If the disk resource managing section 610 determines that the assignment modes match, the process illustrated in
The process 905 of notifying of an error is executed by the infrastructure management server 200. In the process 905, the infrastructure management server 200 notifies the service management server 100 that activation of the logical machine requested to be activated has failed since the checking of the process 901, 902, 903, or 904 is not normally terminated. In the process 905, the infrastructure management server 200 may notify the service management server 100 of a checking process that is not normally terminated.
The process 906 of determining whether or not the assignment mode of the logical machine to be activated is the “dedicated” assignment mode based on the logical machine management information 400 is executed by the logical machine managing section 600. If the logical machine managing section 600 determines that the assignment mode of the logical machine to be activated is not the “dedicated” assignment mode, the process illustrated in
The process 907 of determining whether or not coupling information of a disk assigned to the logical machine to be activated indicates the “uncoupled” state in the disk resource management information 500 is executed by the disk resource managing section 610. The process 907 is executed after the logical machine managing section 600 determines that the assignment mode of the logical machine to be activated is the “dedicated” assignment mode. If the disk resource managing section 610 determines that the coupling information of the disk does not indicate the “uncoupled” state in the process 907, another logical machine may be coupled to the disk and the logical machine to be activated is not enabled to be coupled to the disk in the “dedicated” assignment mode regardless of the fact that the assignment mode of the logical machine to be activated is the “dedicated” assignment mode. Thus, if the disk resource managing section 610 determines that the assignment mode of the logical machine to be activated is not the “dedicated” assignment mode, the process illustrated in
The process 908 of determining whether or not the assignment mode of the logical machine to be activated is the “exclusively shared” assignment mode in the logical machine management information 400 is executed by the logical machine managing section 600. The process 908 is executed after the logical machine managing section 600 determines that the assignment mode of the logical machine to be activated is not the “dedicated” assignment mode in the process 906. If the logical machine managing section 600 determines that the assignment mode of the logical machine to be activated is not the “exclusively shared” assignment mode in the process 908, the checking processes 901 to 904 have been normally terminated, and the assignment mode of the logical machine to be activated is the “shared” assignment mode. If the logical machine managing section 600 determines that the assignment mode of the logical machine to be activated is not the “exclusively shared” assignment mode in the process 908, the process illustrated in
The process 909 of determining whether or not the coupling information of the disk associated with the logical machine to be activated indicates the “uncoupled” state in the disk resource management information 500 is executed by the disk resource managing section 610. If the disk resource managing section 610 determines that the coupling information of the disk indicates the “uncoupled” state, the logical machine to be activated is enabled to be coupled to the disk in the “exclusively shared” assignment mode, and the process illustrated in
In the embodiment, if a request to activate a logical machine to which a disk of which an assignment mode is set to the “exclusively shared” assignment mode is assigned in the disk resource management information 500 is provided, and another logical machine is coupled to the disk, the coupling information of the disk is set to the “coupled” state and whereby the logical machine requested to be activated is not coupled to the disk and activated.
As described with reference to
The process 910 of coupling the logical machine to be activated to the disk in the assignment mode specified by the disk resource management information 500 is executed by the disk resource managing section 610. In the process 910, the logical machine to be activated is coupled to the disk and activated.
The process 911 of determining whether or not the coupling process 910 is successfully executed is executed by the disk resource managing section 610. If the disk resource managing section 610 determines that the coupling process 910 is not successfully executed, the process illustrated in
The process 912 of determining whether or not the coupling information of the disk associated with the logical machine to be activated indicates the “uncoupled” state in the disk resource management information 500 is executed by the disk resource managing section 610. If the disk resource managing section 610 determines that the coupling information does not indicate the “uncoupled” state, the process illustrated in
The process 914 of changing the “number of connections” of the disk associated with the logical machine to be activated in the disk resource management information 500 is executed by the disk resource managing section 610. In the process 914, the disk resource managing section 610 monitors information of the number of connections to the disk and may make various processing determinations for the disk.
A process 915 of terminating the process of coupling the logical machine to the associated disk is executed by the infrastructure management server 200.
In the embodiment, an assignment of a disk in the “exclusively shared” assignment mode is approved by the infrastructure management server 200 and registered in the disk resource management information 500 as described above. Then, any of logical machines is activated based on coupling information of disks in the disk resource management information 500 in response to switching between activation and stop of a logical machine by the service management server 100. For example, when a request to couple a logical machine to a disk is provided in response to a request to activate the logical machine, and coupling information of the disk indicates the “coupled” state in the disk resource management information 500, an exclusive coupling to the disk is ensured by causing the logical machine (requested to be activated) not to be activated. In addition, if a logical machine coupled to the disk in the exclusively shared mode already exists, the coupling information of the disk is set to the “uncoupled” state in the disk resource management information 500 by causing the service management server 100 to temporarily stop the coupled logical machine. Then, when the service management server 100 provides, to the infrastructure management server 200, a request to activate another logical machine that has been registered in the disk resource management information 500 and for which the exclusively shared assignment mode has been set, the other logical machine is coupled to the disk in the exclusively shared mode and activated.
As described above, in the embodiment, since an assignment of a disk to a logical machine is switched based on switching between activation and stop of the logical machine by the service management server 100, the disk may be switched without approval of the infrastructure management server 200.
In cloud computing, a resource of a logical machine to be executed is basically managed by the infrastructure management server 200. Specifically, if specifications of the logical machine are satisfied, an assignment of a resource from the resource pool 300 is managed by an operation of the infrastructure management server 200. If the operational management is executed, and a logical machine coupled exclusively to a disk is stopped due to an error or the like, the coupling of the logical machine to the disk included in the resource pool 300 is released under the authority of the infrastructure management server 200. Thus, the service management server 100 waits for the infrastructure management server 200 to release the disk in order to restart the service. According to the embodiment, however, the service management server 100 that activates and stops the logical machine may release the disk and switch the disk even if support is not quickly provided regardless of the fact that the release process is to be executed by the infrastructure management server 200 managing the cloud platform, and whereby the service management server 100 may quickly restart the service.
The mirroring of the data stored in the disk Disk0201 into the disk Disk0202 is executed by the infrastructure management server 200 that manages the cloud platform. If the disk Disk0201 fails, disk chassis failover is executed to couple the logical machine SERVICE_A—1 to the disk Disk0202 storing the mirrored data. In order to recover access to the disk Disk0201 from the logical machine SERVICE_A—1, the disk Disk0201 is switched under the authority of the infrastructure management server 200 that manages the disks Disk0201 and Disk0202. Thus, the disk chassis failover is not executed only under the authority of the service management server 100.
The disk Disk0200 is assigned to the logical machine SERVICE_A—1 in the exclusively shared assignment mode, and the disk Disk0201 is assigned to the logical machine SERVICE_A—1 in the dedicated assignment mode. The disk Disk0200 is assigned to the logical machine SERVICE_A—2 in the exclusively shared assignment mode, and the disk Disk0202 is assigned to the logical machine SERVICE_A—2 in the dedicated assignment mode. In the state illustrated in
Since the logical machine SERVICE_A—1 is coupled to the disk Disk0201 in the dedicated assignment mode, the coupling information of the disk Disk0201 indicates the “coupled” state in the disk resource management information 1100. The disk Disk0202 is assigned to the logical machine SERVICE_A—2 in the dedicated assignment mode. The disk Disk0202 is a backup disk for the case where an error occurs to the disk Disk0201. The logical machine SERVICE_A—2 is a backup logical machine. Thus, the logical machine SERVICE_A—2 is not activated and coupled to the disk Disk0202 until the service management server 100 provides an activation request. Specifically, the disk Disk0202 is only assigned to the logical machine SERVICE_A—2 and not coupled to the logical machine SERVICE_A—2, and thus the logical machine SERVICE_A—2 does not read and write data from and in the disk Disk0202.
The case where the service management server 100 transmits a request to activate the logical machine SERVICE_A—2 to the infrastructure management server 200 is described below. When the service management server 100 transmits the request to activate the logical machine SERVICE_A—2 to the infrastructure management server 200, the infrastructure management server 200 executes the process illustrated in
The logical machine SERVICE_A—2 is a backup logical machine for the logical machine SERVICE_A—1 and enabled to be coupled to the mirrored backup disk Disk0202. In order to execute the logical machine SERVICE_A—2 as a backup logical machine, system information, stored in the disk Disk0200, of the logical machine SERVICE_A—1 is used. As described with reference to
In the embodiment, the infrastructure management server 200 approves that the disk Disk0200 is assigned to the logical machine SERVICE_A—2 in the exclusively shared assignment mode and the disk Disk0202 is assigned to the logical machine SERVICE_A—2 in the dedicated assignment mode, and the assignments are managed with the disk resource management information 1100. Thus, the logical machine SERVICE_A—2 is enabled to be coupled to the disks Disk0200 and Disk0202 by the process 910 illustrated in
As illustrated in
The disk Disk0300 is assigned to the logical machine SERVICE_A—3 in the exclusively shared assignment mode, while the disk Disk0301 is assigned to the logical machine SERVICE_A—3 in the dedicated assignment mode. In the state illustrated in
Since the logical machine SERVICE_A—3 is coupled to the disk Disk0301 in the dedicated assignment mode, the coupling information of the disk Disk0301 indicates the “coupled” state in the disk resource management information 2100. The logical machine SERVICE_A—4 is not coupled to the disk Disk0301. Thus, the contents of data to be used during an operation are protected even when the test is executed.
The disk Disk0302 for the test is assigned to the logical machine SERVICE_A—4 in the dedicated assignment mode. Since the logical machine SERVICE_A—4 is a logical machine for the test, the logical machine SERVICE_A—4 is not activated until the service management server 100 provides a request to activate the logical machine SERVICE_A—4, and the logical machine SERVICE_A—4 is not coupled to the disk Disk0302. Since the disk Disk0302 is assigned to the logical machine SERVICE_A—4 and not coupled to the logical machine SERVICE_A—4, the logical machine SERVICE_A—4 does not read and write data from and in the disk Disk0302.
The case where the service management server 100 transmits a request to activate the logical machine SERVICE_A—4 to the infrastructure management server 200 is described below. When the service management server 100 transmits the request to activate the logical machine SERVICE_A—4, the infrastructure management server 200 executes the process illustrated in
The logical machine SERVICE_A—4 is a logical machine for the test of the logical machine SERVICE_A—3 and enabled to be coupled to the disk Disk0302 for the test. In order to execute the logical machine SERVICE_A—4 as a logical machine for the test, system information, stored in the disk Disk0300, of the logical machine SERVICE_A—3 is used. As described with reference to
In the embodiment, the infrastructure management server 200 approves that the disk Disk0300 is assigned to the logical machine SERVICE_A—4 in the exclusively shared assignment mode and the disk Disk0302 is assigned to the logical machine SERVICE_A—4 in the dedicated assignment mode, and the assignments are managed using the disk resource management information 2100. Thus, the logical machine SERVICE_A—4 may be coupled to the disks Disk0300 and Disk0302 by the process 910 illustrated in
When the test that is executed by the logical machine SERVICE_A—4 is terminated, the service management server 100 transmits a request to stop the logical machine SERVICE_A—4 to the infrastructure management server 200. When the infrastructure management server 200 receives the request to stop the logical machine SERVICE_A—4, the state of the logical machine SERVICE_A—4 is updated to the “defined” state in the logical machine management information 2000, and the coupling information of the disks Disk0300 and Disk0302 is updated to the “uncoupled” state in the disk resource management information 2100. By these processes, the connections of the logical machine SERVICE_A—4 to the disks Disk0300 and Disk0302 are released. After that, when the service management server 100 transmits a request to activate the logical machine SERVICE_A—3 to the infrastructure management server 200, the logical machine SERVICE_A—3 may be coupled to the disk Disk0300 in the exclusively shared assignment mode. This is due to the fact that the coupling information of the disk Disk0300 is the “uncoupled” state. In addition, the logical machine SERVICE_A—3 may be coupled to the disk Disk0301 in the dedicated assignment mode. Thus, the logical machine SERVICE_A—3 may be coupled to the disk Disk0300 storing the system file corrected by the test executed by the logical machine SERVICE_A—4 and may operate the service.
In the aforementioned example, the disk Disk0300 is exclusively shared by the logical machines SERVICE_A—3 and SERVICE_A—4, and the system file is not overwritten by one of the logical machines SERVICE_A—3 and SERVICE_A—4 during the time when the other logical machine SERVICE_A—3 or SERVICE_A—4 is coupled to the disk Disk0300. In addition, since it is sufficient if the logical machines SERVICE_A—3 and SERVICE_A—4 are switched, a procedure error may be inhibited during the correction of the system file. Since the disk Disk0301 is assigned to the logical machine SERVICE_A—3 in the dedicated assignment mode and the disk Disk0302 is assigned to the logical machine SERVICE_A—4 in the dedicated assignment mode, the assignments inhibit the data stored in the disk Disk0301 and used for the operation of the service from being broken during the test and inhibit information from leaking. According to the embodiment, the service management server 100 that provides the requests to activate and stop the logical machines switches the logical machines and thereby switches connections of the disks during the test operation without the authority of the infrastructure management server 200.
In order to couple the logical machine SERVICE_A—5 to the disk Disk0402 in the dedicated assignment mode, the service management server 100 temporarily deletes a definition to be used to couple the logical machine SERVICE_A—5 to the disk Disk0401 in the dedicated assignment mode. Then, the service management server 100 transmits, to the infrastructure management server 200, definition information to be used to couple the logical machine SERVICE_A—5 to the disk Disk0402 in the dedicated assignment mode. The infrastructure management server 200 receives the definition information and executes the process illustrated in
The example describes that the disk coupled in the dedicated assignment mode is changed. After the definition information of the logical machine is deleted from the infrastructure management server 200, the other definition information is transmitted to the infrastructure management server 200. Specifically, the service management server 100 executes the series of processes and waits for approval of the infrastructure administrator for the series of processes.
Next, it is assumed that if a failure occurs to the disk Disk0401, a logical machine SERVICE_A—6 is coupled to the disk Disk0402 storing the data obtained by mirroring the data stored in the disks Disk0400 and Disk0401 and continues to provide the service.
If both logical machine SERVICE_A—5 and logical machine SERVICE_A—6 are coupled to the disk Disk0400 storing the system file, the system file is updated by the logical machines SERVICE_A—5 and SERVICE_A—6 and may not be normal. Thus, if the exclusively shared assignment mode is not used, the logical machine SERVICE_A—5 is coupled to the disk Disk0400 in the dedicated assignment mode and the service is operated. In addition, if the exclusively shared assignment mode is not used, an assignee logical machine of the disk Disk0400 is the logical machine SERVICE_A—5 in the disk resource management information 500 managed by the infrastructure management server 200, and the logical machine SERVICE_A—6 is not registered. Specifically, in order to set the logical machine SERVICE_A—6 as an assignee logical machine of the disk Disk0400, the definition of the logical machine SERVICE_A—5 is temporarily deleted from the disk resource management information 500. Then, the service management server 100 transmits, to the infrastructure management server 200, definition information indicating a request to assign the logical machine SERVICE_A—6 to the disk Disk0400 in the dedicated assignment mode.
In the examples described with reference to
According to the embodiment, the service management server 100 that manages activation and stop of a logical machine may change a coupling of a disk to the logical machine without the authority of the infrastructure management server 200. For example, coupling information of a disk is changed to the “uncoupled” state in the information managed by the infrastructure management server 200 based on a request to stop a logical machine coupled to the disk. When the coupling information is changed to the “uncoupled” state in the information, the process of releasing the coupling of the logical machine to the disk is executed. In addition, when the coupling information of the disk indicates the “uncoupled” state in the information, activation of a logical machine that shares the disk in the exclusively shared assignment mode is permitted, an exclusive coupling of the logical machine to the disk is ensured, and data is inhibited from being broken due to simultaneous connections of logical machines to the disk.
All examples and conditional language recited herein are intended for pedagogical purposes to aid the reader in understanding the invention and the concepts contributed by the inventor to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions, nor does the organization of such examples in the specification relate to a showing of the superiority and inferiority of the invention. Although the embodiment of the present invention has been described in detail, it should be understood that the various changes, substitutions, and alterations could be made hereto without departing from the spirit and scope of the invention.
Number | Date | Country | Kind |
---|---|---|---|
2012-208133 | Sep 2012 | JP | national |