WO2014148142A1 - Système informatique pour le nuage - Google Patents

Système informatique pour le nuage Download PDF

Info

Publication number
WO2014148142A1
WO2014148142A1 PCT/JP2014/052995 JP2014052995W WO2014148142A1 WO 2014148142 A1 WO2014148142 A1 WO 2014148142A1 JP 2014052995 W JP2014052995 W JP 2014052995W WO 2014148142 A1 WO2014148142 A1 WO 2014148142A1
Authority
WO
WIPO (PCT)
Prior art keywords
host
cloud
management server
hardware
request
Prior art date
Application number
PCT/JP2014/052995
Other languages
English (en)
Japanese (ja)
Inventor
レタンマン カオ
信 萱島
礒川　弘実
Original Assignee
株式会社日立製作所
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社日立製作所 filed Critical 株式会社日立製作所
Publication of WO2014148142A1 publication Critical patent/WO2014148142A1/fr

Links

Images

Classifications

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

Definitions

  • the present invention relates to a computer connection management method and system.
  • VMs virtual machines
  • the virtualization software absorbs the hardware characteristics, the VM does not depend on the hardware characteristics of the computer, and movement between the VM hardware is easy.
  • a computer that operates multiple VMs using virtualization software is called a host.
  • a computer system consisting of multiple hosts and equipped with a function for centrally managing multiple hosts and VMs running on them is called a cloud.
  • the cloud makes it possible to create and manage the number of VMs that exceed the number of VMs that can run on a single host.
  • Each cloud usually has a host that belongs to the cloud and a cloud management server that is a computer that centrally manages VMs running on the host that belongs to the cloud.
  • the cloud management server performs network communication with each host, executes creation, operation, termination, migration between hosts, etc., and centrally and remotely controls VMs on each host.
  • Data center operators may build their own cloud and provide VMs to their customers, but the operation management work for the built cloud may be left to the customer.
  • the data center operator prepares only the host, and the customer incorporates the host into the cloud and uses it as necessary.
  • the customer can manage the cloud to gain the advantage of freely customizing the virtual machine configuration.
  • the cloud is an effective mechanism when sudden expansion is necessary, such as an increase in the number of users. For this reason, in order to respond to the customer's sudden increase in scale, the data center operator may install a spare host in the data center of the customer base.
  • a cloud agent which is software in charge of interaction with the cloud management server, to the host. If necessary, the cloud management server of the customer's cloud is used by adding a spare host on which a cloud agent corresponding to the customer's own cloud is installed.
  • Cloud construction work is the work of starting up the cloud management server first and then adding the installed hosts one by one as the management target of the cloud management server. When building multiple clouds on a large number of hosts, it is necessary to check which cloud is using which host.
  • the cloud can be built on a set of hosts installed at multiple locations. This is important, for example, when multiple VMs that provide similar functions are placed on a host at another site and the functions continue to be provided even if a failure occurs at one site.
  • the host on which the VM with that function runs may need to be located at the same location. In this way, the host on which the VM is placed must be able to be selected according to the user's policy after confirming the host usage status.
  • Patent Document 1 proposes a server that can search which software is operating on which computer on the network. As a result of the search, an IP address of each computer on the network and a list of applications running on the computer are obtained. The usage status of each application can also be found from the search results. Therefore, with the technique of Patent Document 1, the cloud management server can search for a host on which a cloud agent corresponding to the cloud is operating. In addition, it is possible to receive a determination result indicating whether or not the searched host can be used if it is used by another cloud, and can be used if the searched host is not used by another cloud.
  • An object of the present invention is to provide a function for adjusting hosts that can be used between clouds.
  • a cloud management server that manages each cloud and a hardware management server that assigns any of the plurality of hosts to each cloud are provided.
  • Each cloud management server requests the hardware management server to assign a host installed at a desired location, and the hardware management server is installed at the desired location in response to a request from each cloud management server. Assign hosts to each cloud.
  • each cloud in a set of hosts in which a plurality of clouds are mixed, each cloud can use a host at a desired installation location, and cloud quick resource adjustment is possible.
  • FIG. 1 shows the entire system configuration of an embodiment of the present invention.
  • This system includes two management servers for two clouds (Cloud A and Cloud B), multiple hosts for operating VMs, and a hardware management server for assigning hosts to each cloud. Is done.
  • Each server and host are connected via a wide area network (WAN).
  • WAN wide area network
  • Each host is distributed to a plurality of data centers at different locations.
  • This system is a system of a company that operates a certain data center. Multiple hosts that operate VMs operate in data centers installed at locations X and Y that are physically separated.
  • Customer A and Customer B are customers of a company that operates a data center, and operate Cloud A and Cloud B, respectively. It is assumed that VMs running in the cloud provide virtual desktop services and web services to the outside of the system.
  • the system of the present invention includes a cloud management server group represented by a cloud A management server A101, a host group represented by a host 1 (131), a hardware management server 111, and a WAN 1661 for communication between the three parties.
  • the network is configured. Further, as users of this system, there are a customer A 141 who uses the cloud A management server 101, a customer B 142 who uses the cloud B management server 102, and a data center administrator 151 who uses the hardware management server 111.
  • the customer may directly operate the screen of each cloud management server, or may operate from another terminal via a network.
  • the data center administrator may directly operate the screen of the hardware management server 111 or may operate it from another terminal via the network.
  • the host group is a group of computers for operating the VM.
  • the hardware management server 111 is a computer for managing the power state of the host and allocating the host to each cloud.
  • Each cloud management server is a computer for managing each customer's cloud.
  • FIG. 2 illustrates the internal structure of the cloud A management server 101.
  • the server 101 stores a processor (CPU) 222 which is hardware having a calculation function for processing data, a memory 221 which is a storage medium used by the processor when executing a program, and data and data processing software (program).
  • the computer includes a fixed disk 224, which is a non-volatile storage medium, and hardware 223 for network communication.
  • the fixed disk 224 of the server 101 stores software such as an OS (operating system) 201, cloud management software 202, hardware adjustment software 203, and GUI (management screen) 204 for operation by the customer A. These software are loaded into the memory 221 and executed by the processor 222 when the server 101 is activated.
  • the fixed disk 224 of the server 101 stores the cloud A host DB 205.
  • the internal structure of the cloud A host DB 205 will be described later.
  • the OS 201 is software having a function of managing the entire computer, such as loading an application on a memory.
  • the cloud management software 202 is software having a function of transmitting a VM operation command to a host used in the cloud A.
  • the hardware adjustment software 203 is software having a function of communicating with the hardware management server 111 for executing addition / deletion of a host to / from the cloud A and a function of changing the host DB 205 of the cloud A. The operation of the hardware adjustment software 203 will be described later.
  • the GUI 204 is software having a function for the customer A to edit the host DB 205 of the cloud A.
  • FIG. 3 illustrates the internal structure of the cloud A host DB 205.
  • the cloud A host DB 205 is data indicating the host being used by the cloud and the requesting host.
  • the index 301 indicates the identification number of the host requested by the cloud A.
  • the request location 302 describes specific location conditions for each request.
  • the required performance 303 describes specific performance conditions for each request.
  • the performance information illustrated in FIG. 3 is the number of cores that are CPU calculation units and the capacity of Memory that is a storage area used for calculation.
  • the host 304 currently in use describes the host name of the host assigned to each request. If the request is being transmitted, “Request is being transmitted” is described. In addition, when a request is input and the request is not yet transmitted, “request not transmitted” is described. If a host allocation request is transmitted but there is no host that can be allocated, “allocation impossible” is described.
  • the host installation location 305 describes the host installation location assigned to each request.
  • the performance 306 describes the performance of the host hardware assigned to each
  • FIG. 4 illustrates the internal structure of the host 1 (131).
  • the host 1 (131) is a computer that operates a VM in response to a request from the cloud A management server 101 or the cloud B management server 102.
  • the host 1 (131) includes a processor (CPU) 422 which is hardware having a calculation function for processing data, a memory 421 which is a storage medium used by the processor when executing a program, and data and data processing software (program Is a non-volatile storage medium storing a fixed disk 424 and communication hardware 423 for network communication.
  • CPU central processing unit
  • program Is a non-volatile storage medium storing a fixed disk 424 and communication hardware 423 for network communication.
  • the fixed disk 424 of the host 1 (131) stores the OS 401, the virtualization software 402, the cloud B agent 403, the cloud A agent 404, the hardware registration software 405, the VM 406, and the VM 407. These pieces of software are loaded into the memory 421 when the host 1 (131) is activated and executed by the processor 422.
  • the OS 401 is software having a function of managing the entire computer, such as loading an application on a memory.
  • the virtualization software 402 is software having a so-called virtualization function for executing a VM on a memory.
  • the cloud B agent 403 has a function of exchanging VM operation commands with the cloud B management server 102.
  • the cloud A agent 404 has a function of communicating with the cloud A management server 101, receiving a VM operation command from the cloud A management server 101, and transmitting it to the virtualization software 402.
  • the hardware registration software 405 has a function of registering that the host 1 is operating in the hardware management server 111 described later when the host 1 (131) is activated.
  • FIG. 5 illustrates the internal structure of the hardware management server 111.
  • the hardware management server 111 is a computer that receives a host allocation request from the cloud A management server 101 or the cloud B management server 102, searches for a host corresponding to the request, and allocates it to the requested cloud.
  • the hardware management server 111 stores a processor 522 which is hardware having a calculation function for processing data, a memory 521 which is a storage medium used by the processor when executing the program, and data and data processing software (program).
  • the computer includes a fixed disk 524, which is a non-volatile storage medium, and communication hardware 523 for network communication.
  • the OS 501 and the inter-cloud host adjustment software 502 are stored in the fixed disk 524 of the hardware management server 111. These pieces of software are loaded into the memory 521 when the hardware management server 111 is activated, and are executed by the processor 522.
  • the internal structure of the inter-cloud host adjustment software 502 will be described later.
  • the fixed disk 524 of the hardware management server 111 stores four databases: a host replacement condition DB 503, a service DB 504, a cloud host usage status DB 505, and an installation location DB 506.
  • FIG. 6 illustrates the internal structure of the installation location DB 506.
  • the installation location DB 506 is a database that describes the host names, installation locations, and hardware performance of all the hosts on the system.
  • the data center 601 describes in which data center the host is installed.
  • base X When “base X” is written, it means that the host is installed in the data center of base X.
  • the rack 602 is used only when the host is a thin computer, but the identification number of the rack in which the host is installed is described.
  • the rack is a dedicated shelf on which thin computers and the like can be stacked and installed.
  • the chassis 603 is used only when the host is a blade server type computer, and describes the identification number of the chassis in which the host is installed.
  • the chassis is a housing for connecting and storing the blade server.
  • the chassis has a series of blade slots (slots) that can be operated as soon as the blade is inserted.
  • the slot 604 is used only when the host is a blade server type computer, and describes the identification number of the blade slot used by the host.
  • the host name 605 describes the host name of each host.
  • the HW performance 606 describes hardware resource information such as the number of CPU cores and memory capacity of each host.
  • the data center 601, rack 602, chassis 603, and slot 604 are information input when the data center manager 151 installs the host, and the host name 605 and HW performance 606 are information registered when the host is activated. It is.
  • FIG. 7 illustrates the internal structure of the cloud host usage DB 505.
  • the cloud host usage DB 505 is a database that records the allocation status of all hosts on the system.
  • the host name 701 records the host names of all the hosts on the system.
  • the cloud name 702 records the cloud name of the cloud using each host. “Unassigned” is described for hosts not assigned to the cloud.
  • the cloud host usage DB 505 is updated by the hardware / air management server 111 periodically communicating with the cloud management server of each cloud.
  • FIG. 8 illustrates the internal structure of the service DB 504.
  • the service DB 504 is a database that records what kind of cloud agent each host on the system operates and records an address (IP address) on the network for connecting to the agent. First, in the host name 801, the host name of each host is recorded. The service name 802 records what kind of cloud agent is operating for each host. Next, the IP address of each host is recorded in the IP address 803. Information in the service DB 504 is registered by the hardware registration software 405 in each host when the host is activated.
  • FIG. 9 illustrates the internal structure of the host replacement condition DB 503.
  • the host replacement condition DB 503 is a database that describes conditions for replacing a host being used by each cloud with another host.
  • the cloud name 901 describes the cloud name of the cloud operating on the system.
  • the condition 902 describes conditions for replacing each cloud host. For example, it can be replaced with a host on which no VM is operating, or can be replaced with a host on which up to two VMs are operating.
  • the billing 903 describes the amount charged to the customer who requested the replacement by the cloud customer who permitted the replacement for one replacement when the host replacement occurred.
  • the host replacement condition DB 503 is information registered by the data center manager 151 when creating a cloud.
  • FIG. 10 shows an operation procedure of the hardware adjustment software 203 of the cloud management server.
  • the hardware adjustment software 203 is software that requests the hardware management server 111 to allocate a host required by the cloud management server.
  • the hardware adjustment software 203 starts to operate at the same time as the cloud A management server 101 and the cloud B management server 102 are activated.
  • the structure of the request message (request message 1101) transmitted by the hardware adjustment software 203 will be described later.
  • step 1003 the allocation result from the hardware management server 111 is received (step 1003).
  • the structure of the allocation result message (host allocation message 1111) will be described later.
  • step 1004 If a host is allocated as a result of the request (step 1004), the host name of the allocated host is entered in the host in use 304 (step 1006).
  • step 1007 the IP address of the assigned host is transferred to the cloud management software 202 (step 1007).
  • the process returns to step 1001.
  • step 1004 if the host cannot be allocated, “not allocated” is described in the host 304 in use of the entry in the cloud host DB 205, and the process returns to step 1001 (step 1005).
  • FIG. 11A illustrates an internal structure of a message (host allocation request message 1101) transmitted when the hardware adjustment software 203 of the cloud management server requests the hardware management server 111 to allocate a host.
  • the service name 1102 is a cloud agent that is to be operated on the host.
  • the location condition 1103 is information relating to the requested installation location of the host.
  • FIG. 11B illustrates the internal structure of the host allocation message 111 that notifies the host allocation result.
  • assignability 1112 “YES” is described if a host can be assigned with respect to the presented condition, and “NO” if it cannot be assigned.
  • the host name 1113 describes the host name.
  • the IP address 1114 describes the IP address when there is an assigned host.
  • the installation location 1115 describes the installation location when there is an assigned host.
  • the performance 1116 describes the performance of the hardware when there is an assigned host.
  • FIG. 12 shows an operation procedure of the inter-cloud host adjustment software 502 of the hardware management server 111.
  • the inter-cloud host adjustment software 502 of the hardware management server 111 returns a host assignment message 1111 that notifies the assignment result in response to the host assignment request of the hardware adjustment software 203 of the cloud management server.
  • the inter-cloud host adjustment software 502 starts operating at the same time as the hardware management server 111 is activated. First, it waits for a host allocation request (host allocation request message 1101) to arrive from the hardware adjustment software 203 (step 1201).
  • the installation location DB 506 and the service DB 504 check whether there is a host to which the conditions 1102 and 1103 described in the request message 1101 correspond at the same time (step 1202).
  • step 1203 If there is no host to which the conditions 1102 and 1103 simultaneously correspond, a host assignment message 1111 in which “NO” is described in the assignment possibility 1112 is returned, and the process returns to step 1201 (step 1203).
  • step 1204 it is confirmed in the cloud host usage DB 505 whether there is a cloud that uses these hosts (step 1204). If there is an unassigned host in the corresponding host, the host information is described in the host assignment message 1111, “YES” is set in the assignment possibility 1112 of the message, and the response is returned to the hardware adjustment software 203, step 1201 Return to (step 11205).
  • step 1204 if there is no unassigned host in the group of hosts to which the conditions 1102 and 1103 simultaneously correspond, the host can be replaced in the host replacement condition DB 503 for the cloud in use of each corresponding host. Whether or not (step 1206). If there is no cloud in which the host can be replaced, a host assignment message 1111 in which “NO” is described in the assignment permission / inhibition 1112 is returned, and the process returns to step 1201 (step 1207). On the other hand, if there is a cloud in which the host can be replaced, the host is requested to replace the host (step 1208). A detailed procedure for host replacement will be described later. The information of the host that has been replaced is described in the host assignment message 1111, “YES” is set in the message assignment possibility 1112, the hardware adjustment software 203 is returned, and the process returns to step 1201 (step 1209).
  • Steps 1301, 1302, 1303, and 1304 in FIG. 13 exemplify the operation start procedure of the system of this embodiment.
  • the system administrator activates the cloud A management server 101, the cloud B management server 102, the hardware management server 111, and the host group 1300 (step 1301).
  • the host group 1300 includes a host 1 (131), a host 2 (132), a host 3 (133), and a host 4 (134).
  • the data center manager 151 inputs information on the data center 601, rack 602, chassis 603, and slot 604 of the installation location DB 506.
  • the host replacement condition DB 503 is also input (step 1302).
  • Each cloud management server activates the cloud management software 202 and the hardware management software 203 (step 1303).
  • the cloud agent and hardware registration software 405 on each host is activated, and the host information is registered in the host name 605 and the HW performance 606 of the installation location DB 506. Also, the host name, host cloud agent and IP address information are registered in the service DB 504 (step 1304). When step 1304 is completed, the start of operation of the system of this embodiment is completed.
  • each cloud requests the hardware management server 111 to allocate a host, and the hardware management server 111 allocates a host in response to the request (step 1305). Details of step 1305 will be described later.
  • the VM is operated using the resources of the host to which each cloud is assigned.
  • Each cloud may execute step 1305 as necessary to make a host addition request (step 1315).
  • Steps 1306, 1307, and 1308 in FIG. 13 exemplify the operation end procedure of the system of this embodiment.
  • each cloud management server ends the cloud management software 202 and the hardware management software 203 (step 1306).
  • the cloud agent and hardware registration software 405 on each host is terminated (step 1307).
  • the data center manager 151 terminates the cloud A management server 101, the cloud B management server 102, the hardware management server 111, and the host group 1300 (step 1308).
  • FIG. 14 exemplifies the host allocation procedure in step 1305 (FIG. 13).
  • cloud A uses host 1 (131)
  • cloud B uses host 3 (133) and host 4 (134). It is assumed that host 2 is not assigned. Since the cloud B management server 102 requests assignment of one host and a host that satisfies the request condition is not used for another cloud, the hardware management server 111 returns the IP address of the host to the cloud B management server 102 The procedure in the case where the processing of the request is completed is illustrated.
  • the cloud management server 102 requests the hardware management server 111 for a host installed in the data center of the base X that can support the cloud B (step 1401).
  • the request message is illustrated in FIG.
  • the value of the service name 1102 in FIG. 11A is “cloud B”
  • the value of the location condition 1103 is “base X”.
  • the hardware management server 111 executes Step 1202 (FIG. 12) (Step 1402).
  • Step 1202 since the installation location DB 506 and the service DB 504 have the host 2 and the host 3 corresponding to the conditions requested by the cloud B management server 102, the result of step 1202 is “YES”, and the hardware management server 111 performs step 1204.
  • step 1204 when referring to the cloud host usage DB 505, since there is an unallocated host 2 (132), the hardware management server 111 executes step 1205. In step 1205, the hardware management server 111 returns the information of the host 2 (132) on the host assignment message 1111 and returns it to the cloud B management server 102 (step 1403).
  • the cloud B management server 101 receives the information of the host 2 (132) and enters it in the cloud host DB 205 (step 1404).
  • the cloud B management server 102 operates the VM using the resources of the host 2 (132) (step 1405).
  • the host 2 (132) operates the VM in response to a request from the cloud B management server 102 (step 1406).
  • the cloud B management server 102 transmits a VM deletion command to the host 2 (step 1407), deletes the information of the host 2 (132) from the cloud host DB 205 (step 1408), and the host 2 (132) is notified to the hardware management server 111 (step 1409).
  • the host 2 (132) ends the operation of the VM requested to be created from the cloud B management server 102 (step 1410).
  • the hardware management server reflects that the host 2 (132) is in an unallocated state in the cloud host usage DB 505 (step 1411).
  • FIG. 15 exemplifies the inter-cloud host adjustment procedure in the system of this embodiment.
  • FIG. 15 is also a procedure for allocating a host to each cloud in step 1305 (FIG. 13), but corresponds to the case where the host requested by the cloud is already used by another cloud.
  • cloud A uses host 1 (131)
  • cloud B uses host 3 (133) and host 4 (134) (step 1501).
  • the cloud A management server 101 requests the hardware management server 111 for a host on which the cloud agent of cloud A is operating and installed in the data center of the site Y (step 1502).
  • the hardware management server 111 finds a host 4 (134) that satisfies the request (step 1503).
  • Step 1504 it can be confirmed that the host 4 (134) is being used by another cloud (cloud B), and in step 1206, it can be confirmed that the cloud B accepts host replacement. Therefore, the inter-cloud adjustment software 503 executes Step 1208.
  • the processing procedure of step 1208 is illustrated by steps 1505 to 1511 in FIG.
  • the hardware management server 111 transmits a host 2 (132) replacement request to the cloud B management server 102.
  • the condition 902 of the host replacement condition DB 503 is also transmitted simultaneously (step 1505).
  • the cloud B management server 102 checks the number of VMs running on the host 4 (134) and determines whether the condition 902 is met. In this case, assuming that two or less VMs are operating on the host 3, the cloud B management server 102 approves the replacement request (step 1506).
  • the hardware management server 111 searches for an unallocated host that supports Cloud B as an alternative to the host 4 and allocates it to Cloud B.
  • the result is that the host 2 (132) is assigned (step 1507).
  • the cloud B moves the VM from the host 4 (134) to the assigned host 2 (132) and uses the host 2 (132) (step 1508).
  • the cloud B management server 102 that has started using the step 2 deletes the VM on the host (step 1509).
  • the hardware management server 111 transmits the information of the host 4 (134) to the cloud A management server, and allocates the host 4 (134) to the cloud A (step 1510).
  • cloud A starts using the host 4 (134) (step 1511).
  • the host location is described in the host allocation request, but the hardware performance of the host can be used instead of the location.
  • the installation location and hardware performance can be requested simultaneously.
  • the hardware management server 111 refers to the HW performance 606 of the installation location DB 506 and searches for an assignable host.
  • the cloud when a shortage of cloud resources occurs, the cloud automatically adds a host, and realizes a mechanism for returning the host when the host is no longer needed.
  • this invention is not limited to the above-mentioned Example, Various modifications are included.
  • the above-mentioned implementation reward has been described in detail for easy understanding of the present invention, and is not necessarily limited to the one having all the configurations described.
  • each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit.
  • each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the CPU.
  • Information such as programs and databases for realizing each function can be stored in a storage device such as a memory or HDD, or a storage medium such as an IC-card, SD card, or DVD.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Mathematical Physics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer And Data Communications (AREA)

Abstract

L'objet de la présente invention est de produire une fonction permettant de régler un hôte qui peut être utilisé parmi les nuages. L'invention concerne un système informatique dans lequel une pluralité d'hôtes sont disposés à une pluralité de concentrateurs et une pluralité de nuages sont construits, des serveurs de gestion de nuages permettant de gérer les nuages et un serveur de gestion de matériel permettant d'allouer n'importe quel hôte parmi la pluralité d'hôtes aux nuages sont présents, les serveurs de gestion de nuages présentent une requête au serveur de gestion de matériel pour allouer un hôte disposé sur un concentrateur désiré, et en fonction des requêtes provenant des serveurs de gestion de nuages, le serveur de gestion de matériel alloue l'hôte disposé sur le concentrateur désiré aux nuages.
PCT/JP2014/052995 2013-03-19 2014-02-10 Système informatique pour le nuage WO2014148142A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2013055882A JP2016122223A (ja) 2013-03-19 2013-03-19 クラウド向け計算機システム
JP2013-055882 2013-03-19

Publications (1)

Publication Number Publication Date
WO2014148142A1 true WO2014148142A1 (fr) 2014-09-25

Family

ID=51579836

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2014/052995 WO2014148142A1 (fr) 2013-03-19 2014-02-10 Système informatique pour le nuage

Country Status (2)

Country Link
JP (1) JP2016122223A (fr)
WO (1) WO2014148142A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106331150B (zh) * 2016-09-18 2018-05-18 北京百度网讯科技有限公司 用于调度云服务器的方法和装置

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012173869A (ja) * 2011-02-18 2012-09-10 Nippon Telegr & Teleph Corp <Ntt> 割当決定装置、割当決定方法、割当システム及び割当決定プログラム

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012173869A (ja) * 2011-02-18 2012-09-10 Nippon Telegr & Teleph Corp <Ntt> 割当決定装置、割当決定方法、割当システム及び割当決定プログラム

Also Published As

Publication number Publication date
JP2016122223A (ja) 2016-07-07

Similar Documents

Publication Publication Date Title
US10956288B2 (en) Server clustering in a computing-on-demand system
US10082972B2 (en) Method and system for pooling, partitioning, and sharing network storage resources
WO2017072933A1 (fr) Système et procédé de gestion pour système informatique
US9003411B2 (en) Automated provisioning and configuration of virtual and physical servers
JP5272709B2 (ja) アドレス割当方法、コンピュータ、物理マシン、プログラム、及びシステム
US8370481B2 (en) Inventory management in a computing-on-demand system
CN110955487A (zh) Hci环境下的vm/容器和卷配置决定方法及存储系统
US8434078B2 (en) Quick deployment method
US8463882B2 (en) Server cloning in a computing-on-demand system
WO2015049789A1 (fr) Système de gestion de ressources et procédé de gestion de ressources
US11159367B2 (en) Apparatuses and methods for zero touch computing node initialization
JP2008186137A (ja) ストレージシステムの複数の論理リソースを制御する制御装置
WO2014184893A1 (fr) Système informatique et procédé de gestion de ressources
US20100325406A1 (en) Computer system and management device
CN101656718A (zh) 网络服务器系统与其虚拟机器的建立与开启的方法
CN113939803B (zh) 用于专用主机的管理计算资源放置即服务
JP2010257274A (ja) 仮想化環境におけるストレージ管理システム及びストレージ管理方法
JP6055924B2 (ja) ストレージシステム及びストレージシステムの制御方法
JP5439435B2 (ja) 計算機システムおよびその計算機システムにおけるディスク共有方法
JP5492731B2 (ja) 仮想計算機のボリューム割当て方法およびその方法を用いた計算機システム
WO2014148142A1 (fr) Système informatique pour le nuage
JP6244496B2 (ja) サーバストレージシステムの管理システム及び管理方法
JP5492253B2 (ja) 制御装置、制御方法および制御プログラム
KR20190028330A (ko) 풀 그룹화를 이용한 가상 데스크탑 시스템 및 서비스 방법

Legal Events

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

Ref document number: 14770384

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14770384

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP