WO2016170625A1 - 計算機システムの管理システム - Google Patents
計算機システムの管理システム Download PDFInfo
- Publication number
- WO2016170625A1 WO2016170625A1 PCT/JP2015/062279 JP2015062279W WO2016170625A1 WO 2016170625 A1 WO2016170625 A1 WO 2016170625A1 JP 2015062279 W JP2015062279 W JP 2015062279W WO 2016170625 A1 WO2016170625 A1 WO 2016170625A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- resource
- tenant
- resources
- administrator
- management
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
-
- 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]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Definitions
- the present invention generally relates to resource allocation control of a computer system.
- Patent Document 1 JP 2014-23142 (Patent Document 1). This publication provides: “A cloud computing subsystem for provisioning computing resources having various service levels on a specific network isolation area. Furthermore, from each tenant in the cloud computing subsystem, and "Providing a protocol that controls the flow of frames to each tenant" (see summary).
- XaaS (X as Service) is known.
- XaaS is a service that makes it possible to use any resource (for example, hardware, line, software execution environment, application software, development environment, etc.) necessary for construction or operation of an information system through a network such as the Internet.
- the character (or word) adopted as “X” of XaaS differs depending on the type (service model) of XaaS.
- PaaS Platinum as Service
- PaaS PaaS (Platform as Service)
- IaaS Infrastructure as Service
- HaaS Hardware as Service
- Patent Document 1 does not disclose an operation after provisioning a resource of a type conforming to XaaS. Management after provisioning of multiple types of resources according to multiple types of XaaS is not straightforward.
- the types of resources (tenant environment allocation resources) to be provisioned as tenant environments for each tenant differ depending on the XaaS type. . Therefore, it is necessary to perform resource management for a plurality of types of resources of the same computer system in consideration of different tenant environment allocation resource types depending on the XaaS type.
- XaaS resource management server is, for example, a management server that exists for each type of XaaS and manages at least tenant environment allocation resources according to a specific XaaS.
- the “common resource management server” is a management server that manages at least lower-level resources among the resources of the computer system.
- “Lower level resource” is a lower level resource than the tenant environment allocation resource.
- the common resource management server When one common resource management server is shared by a plurality of XaaS resource management servers, the common resource management server considers that the type of tenant environment allocation resource managed by each XaaS resource management server is different. It is necessary to control requests for resources from the resource management server.
- the management system has an interface device connected to a computer system including a plurality of resources including resources of a plurality of resource types, and a processor connected to the interface device.
- the processor allocates resources of different resource types depending on the XaaS (X as a Service) type among multiple resources including resources of multiple resource types to the tenant environment, and provides multiple tenant environments including multiple XaaS To do.
- the processor manages, as lower resources, resources lower than the resources allocated to each tenant environment among a plurality of resources including resources of a plurality of resource types.
- the processor executes a change process on at least one or more subordinate resources among resources managed as subordinate resources.
- the management system is a management system for managing a computer system including a plurality of resources including resources of a plurality of resource types, and includes a plurality of XaaS resource management servers corresponding to a plurality of types of XaaS and a common resource management server. .
- Each of the plurality of XaaS resource management servers provides a tenant environment according to the XaaS corresponding to the XaaS resource management server.
- the common resource management server allocates resources of different resource types depending on the XaaS type among a plurality of resources including resources of a plurality of resource types to the tenant environment corresponding to the XaaS.
- the common resource management server manages, as lower resources, resources lower than the resources allocated to each tenant environment among a plurality of resources including resources of a plurality of resource types.
- the common resource management server receives a resource change request from any of the XaaS resource management servers, the common resource management server sets at least one or more lower resources among the resources managed as lower resources for the tenant environment provided by the XaaS resource management server.
- the change process is executed for it.
- FIG. 1 shows an overview of an information system according to an embodiment.
- An example of a management system is shown.
- An outline of the computer system is shown.
- the structural example of an integrated management server is shown.
- the example of the interface which a system management program provides to each of a XaaS resource management server is shown.
- a comparative example of resource management methods is shown.
- An example of the resource management method which concerns on embodiment is shown.
- the structural example of a computer system is shown.
- the structural example of a blade server is shown.
- 2 shows a configuration example of a storage apparatus.
- the structural example of a XaaS resource management server is shown.
- the structural example of a common resource management server is shown. 2 shows an example of the configuration of a plurality of resources in a computer system.
- the structural example of a tenant management table is shown.
- the structural example of a tenant environment management table is shown.
- the structural example of a service model management table is shown.
- the structural example of a resource separate management table is shown.
- the structural example of an administrator management table is shown.
- the structural example of a tenant environment management table is shown.
- the structural example of a resource management table is shown.
- the structural example of an operation authority management table is shown.
- the structural example of a dependency management table is shown.
- the structural example of a monitoring table is shown.
- the structural example of a resource group management table is shown.
- An overview of the flow of processing performed in response to a request from the tenant administrator is shown.
- An example of a search result screen is shown.
- a specific example of execution environment construction of VMaaS will be described.
- a specific example of construction of an execution environment for PaaS will be shown.
- An example of the flow of processing performed in response to a request from a system administrator is shown.
- An example of the flow of a service model change process is shown.
- An example of occupation resource maintenance is shown.
- An example of the information displayed with respect to a tenant administrator is shown.
- An example of information displayed to the system administrator is shown.
- xxx table information may be described using the expression “xxx table”, but the information may be expressed in any data structure. That is, “xxx table” can be referred to as “xxx information” to indicate that the information does not depend on the data structure.
- xxx information information may be described using the expression “xxx table”, but the information may be expressed in any data structure. That is, “xxx table” can be referred to as “xxx information” to indicate that the information does not depend on the data structure.
- the configuration of each table is an example, and one table may be divided into two or more tables, or all or part of the two or more tables may be a single table. Good.
- ID or name is used as element identification information, but other types of identification information may be used instead or in addition.
- a reference number or a common number in the reference number is used, and when a description is made by distinguishing the same type of element, the reference number of the element is used.
- an ID assigned to the element may be used instead of the reference code.
- an I / O (Input / Output) request is a write request or a read request, and may be referred to as an access request.
- the “storage unit” may be one or more storage devices including a memory.
- the storage unit may be at least a main storage device of a main storage device (typically a volatile memory) and an auxiliary storage device (typically a nonvolatile storage device).
- PDEV indicates a physical storage device, and may typically be a nonvolatile storage device (for example, an auxiliary storage device).
- the PDEV may be, for example, an HDD (Hard Disk Drive) or an SSD (Solid State Drive).
- RAID is an abbreviation for Redundant Array of Independent (or Inexpensive) Disks.
- the RAID group is composed of a plurality of PDEVs, and stores data according to the RAID level associated with the RAID group.
- the RAID group may be referred to as a parity group.
- the parity group may be, for example, a RAID group that stores parity.
- the process may be described with “program” as the subject, but the program is executed by a processor (for example, a CPU (Central Processing Unit)) so that a predetermined process can be appropriately performed. Since the processing is performed using a storage unit (for example, a memory) and / or an interface device (for example, a communication port), the subject of processing may be a processor.
- the processing described with the program as the subject may be processing performed by a processor or an apparatus or system having the processor.
- the processor may include a hardware circuit that performs a part or all of the processing.
- the program may be installed in a computer-like device from a program source.
- the program source may be, for example, a storage medium that can be read by a program distribution server or a computer.
- the program distribution server may include a processor (for example, a CPU) and a storage unit, and the storage unit may further store a distribution program and a program to be distributed. Then, the processor of the program distribution server executes the distribution program, so that the processor of the program distribution server may distribute the distribution target program to other computers.
- a processor for example, a CPU
- the storage unit may further store a distribution program and a program to be distributed. Then, the processor of the program distribution server executes the distribution program, so that the processor of the program distribution server may distribute the distribution target program to other computers.
- two or more programs may be realized as one program, or one program may be realized as two or more programs.
- the management system may be composed of one or more computers.
- the management computer displays information (specifically, for example, the management computer displays information on its own display device, or the management computer (eg, management server) displays the information for display).
- a remote display computer (for example, when transmitting to a management client), the management computer is a management system.
- the plurality of computers may include a display computer when the display computer performs display) is the management system. .
- the management computer may include an interface device connected to an I / O system including a display system, a storage unit (eg, memory), and a processor connected to the interface device and the storage unit.
- the display system may be a display device included in the management computer or a display computer connected to the management computer.
- the I / O system may be an I / O device (for example, a keyboard and a pointing device or a touch panel) included in the management computer, a display computer connected to the management computer, or another computer. “Displaying display information” by the management computer means displaying the display information on the display system, which may be displaying the display information on a display device included in the management computer.
- the management computer may transmit display information to the display computer (in the latter case, the display information is displayed by the display computer).
- the management computer inputting / outputting information may be inputting / outputting information to / from an I / O device of the management computer, or a remote computer connected to the management computer (for example, a display)
- Information may be input / output to / from the computer.
- the information output may be a display of information.
- VOL is an abbreviation for logical volume and may be a logical storage device.
- the VOL may be a substantial VOL (RVOL) or a virtual VOL (VVOL).
- the VOL may be an online VOL provided to a host system connected to a storage system that provides the VOL, and an offline VOL that is not provided to the host system (not recognized by the host system).
- the “RVOL” may be a VOL based on a physical storage unit (for example, one or more RAID groups) included in the storage system having the RVOL.
- VVOL may be at least one of an external connection VOL (EVOL), a capacity expansion VOL (TPVOL), and a snapshot VOL.
- the EVOL is based on a storage space (for example, VOL) of an external storage system, and may be a VOL according to a storage virtualization technology.
- the TPVOL is composed of a plurality of virtual areas (virtual storage areas), and may be a VOL according to capacity virtualization technology (typically Thin Provisioning).
- the snapshot VOL may be a snapshot VOL that is provided as a snapshot of the original VOL.
- the TPVOL may typically be an online VOL.
- the snapshot VOL may be an RVOL.
- a “pool” is a logical storage area (for example, a set of a plurality of pool VOLs), and may be prepared for each use.
- the TP pool may be a storage area composed of a plurality of real areas (substantial storage areas). A real area may be allocated from the TP pool to the virtual area of TPVOL.
- the snapshot pool may be a storage area in which data saved from the original VOL is stored.
- One pool may be used as both a TP pool and a snapshot pool.
- the “pool VOL” may be a VOL that is a component of the pool.
- the pool VOL may be an RVOL or an EVOL.
- the pool VOL may typically be an offline VOL.
- the VOL may be called LU (Logical Unit).
- FIG. 1 shows an overview of an information system according to the embodiment.
- the information system includes a computer system 120, a tenant system 110, and a management system 170.
- the computer system 120 has a plurality of resources including a plurality of types of resources.
- the resource type is referred to as “resource type”. Multiple resources have dependencies between different resource types.
- the resource may be a physical resource or a virtual resource.
- the plurality of resources for example, there are one or more storage apparatuses and one or more blade servers connected to the one or more storage apparatuses.
- the computer system 120 may be a so-called integrated platform including both blade servers and storage devices.
- the “blade server” is an example of a server computer and may be referred to as a “server computer”. Specific examples of the plurality of resources will be described later.
- the tenant system 110 is a system composed of one or more computers, and exists for each tenant.
- a “tenant” is an example of a user, and is a user who borrows (or purchases) a tenant environment allocation resource among a plurality of resources that the computer system 120 has.
- a “tenant” is a user of a cloud service that provides a computer system resource.
- a “tenant environment allocation resource” is a resource (an example of a provisioned resource) allocated to a tenant environment, and may be referred to as a “provisioning resource”.
- the “tenant environment” is a virtual environment provided to the tenant (tenant system 110).
- the tenant By allocating resources to the environment, the tenant (tenant system 110) can use the resource (tenant environment allocation resource) and higher-level resources created based on the resource.
- the tenant system 110 is connected to the computer system 120 and the management system 170 via a communication network (for example, an IP (Internet Protocol) network) 150.
- the tenant system 110 can log in to the resource, for example, as the use of the tenant environment allocation resource.
- the tenant system 110 may be, for example, a personal computer that starts a browser (for example, a Web browser).
- FIG. 2 shows a configuration example of the management system 170.
- the management system 170 includes an integrated management server 160, a XaaS resource management server group 141, and a common resource management server 130.
- the XaaS resource management server group 141 is a plurality of XaaS resource management servers 140 that differ depending on the type of XaaS. This is the resource management server 140-3.
- the XaaS resource management server 140 is a computer that exists for each type of XaaS, for example, and manages at least the tenant environment allocation resource among the tenant environment allocation resource according to a specific XaaS and its upper resources. There are types of resources necessary for the plurality of XaaS resource management servers 140 to provide tenant environment allocation resources, such as server resources or storage resources.
- the common resource management server 130 manages the types of resources that are commonly required by the plurality of XaaS resource management servers 140. Further, the common resource management server 130 may also serve as a kind of XaaS resource management server 140.
- the integrated management server 160 is one or more computers used by the tenant administrator or the system administrator.
- the “tenant administrator” is an administrator of the tenant system 110.
- the tenant administrator and the user of the tenant system 110 may be employees who belong to the same tenant.
- the tenant administrator may be an employee of a company different from the tenant.
- the “system administrator” is an administrator of the computer system 120.
- the integrated management server 160 is connected to the tenant system 110 and the computer system 120 via the communication network 150.
- the integrated management server 160 is connected to each XaaS resource management server 140 and the common resource management server 130 via the communication network 150.
- Each XaaS resource management server 140 is connected to the common resource management server 130 via the communication network 150.
- the integrated management server 160 associates and manages each XaaS type and the XaaS resource management server 140 corresponding to the XaaS.
- the integrated management server 160 transmits a tenant administrator request (for example, resource allocation request) to any XaaS resource management server 140 based on the requested XaaS type. For example, when a tenant administrator (tenant system 110) requests a PaaS tenant environment, the integrated management server 160 transmits a tenant administrator request to the PaaS resource management server 140-1.
- the XaaS resource management server 140 executes processing based on the received request from the tenant administrator, thereby allocating resources (tenant environment allocation resources) to the tenant environment and providing the tenant environment to the tenant system 110.
- the XaaS resource management server 140 requests the common resource management server 130 to allocate resources.
- the XaaS resource management server 140 receives a response to the request (for example, a response indicating that resources have been allocated to the tenant environment) from the common resource management server 130.
- the XaaS resource management server 140 transmits a response to the request from the tenant administrator to the integrated management server 160.
- the integrated management server 160 transmits information necessary for using the resource (for example, information necessary for login) to the tenant system 110 (tenant administrator).
- the tenant system 110 can use the tenant environment allocation resource (or its higher resources) of the computer system 120 based on the information.
- the integrated management server 160 transmits a request from the system administrator to the common resource management server 130 or the XaaS resource management server 140.
- the integrated management server 160 responds to the system administrator (the system administrator's management computer) based on the response from the common resource management server 130 or the XaaS resource management server 140.
- the process executed by the common resource management server 130 and the XaaS resource management server 140 may be executed by the integrated management server 160.
- FIG. 3 shows an outline of the computer system 120.
- the computer system 120 provides a plurality of types of XaaS.
- the type of XaaS differs depending on the term used as “X”, in other words, the type of resource used as the tenant environment allocation resource.
- X the type of resource used as the tenant environment allocation resource.
- PaaS Platinum as a Service
- VMaaS VM as a Service
- STGaas Storage as a Service
- FIG. 3 the tenant environment allocation resource is highlighted (displayed in gray), but as can be seen from FIG. 3, the type of tenant environment allocation resource (the hierarchy to which the tenant environment allocation resource belongs) differs depending on the XaaS type.
- the tenant environment allocation resource is provided based on a resource (lower resource) lower than the tenant environment allocation resource.
- a VM Virtual Machine
- APP application program
- the server memory is an example of a server resource
- the LU is an example of a storage resource.
- LPARaaS LPAR (as a Service).
- the plurality of resources included in the computer system 120 have a dependency relationship.
- the terms “upper / lower” and “dependent / dependent” (or “parent / child”) will be used to represent the logical location (eg, hierarchy) of the resource.
- the meaning of “second resource above the first resource” means that the second resource is topologically related to the first resource and is one higher than the hierarchy (type) to which the first resource belongs. This means that the second resource belongs to the above hierarchy (type).
- the meaning of “the second resource that is the dependency source (or parent) of the first resource” means that the second resource is a resource that is one level higher than the first resource. That is, in the description of the present embodiment, “dependence source” (or “parent”) is a concept included in “higher”.
- the meaning of “second resource lower than the first resource” means that the second resource is topologically related to the first resource and is one more than the hierarchy (type) to which the first resource belongs. This means that the second resource belongs to the lower hierarchy (type).
- the meaning of “second resource that is a dependency (or child) of the first resource” means that the second resource is a resource that is one level lower than the first resource. That is, in the description of the present embodiment, “dependence destination” (or “child”) is a concept included in “lower”.
- the hierarchy it is conceivable that the physical resource is located in the lower hierarchy as the OSI (Open Systems Interconnection) reference model is located, and the closer to the APP, the higher the hierarchy.
- the server resource and the storage resource can be treated as the same hierarchy in terms of physical resources. However, in consideration of the fact that the server resource is necessary for executing APP, This resource may be in a higher hierarchy than the storage resource.
- Tenant environment allocation resource A resource allocated to the tenant environment.
- Higher resource A higher resource than the tenant environment allocation resource.
- Lower resource A resource lower than the tenant environment allocation resource.
- Unallocated resource An unallocated resource is a resource managed by the system administrator, and is not a dependency of a higher resource, a tenant environment allocated resource, or a lower resource. Unallocated resources can be lower resources or tenant environment allocated resources by the system administrator.
- the resources of the computer system 120 are managed based on the corresponding category among the categories “upper resource”, “tenant environment allocation resource”, “lower resource”, and “unallocated resource”.
- this category is referred to as “resource category” or “resource class”.
- Resource management by the system administrator examples include the following.
- Resource creation A resource higher than the resource is created based on the resource managed by the system administrator.
- Resource deletion Resource is deleted. Release the dependency between the deletion target resource and the dependency destination resource of the deletion target resource. As an extension, if a resource does not have a dependency with another resource, it may be treated as an unallocated resource.
- Attribute change Resource attribute is changed.
- the VM (Virtual Machine) attribute includes, for example, memory capacity, number of CPUs, number of virtual NIC (Network Interface Controller / Card), virtual PDEV (capacity or number), VM identifier, login information (for example, IP address when logging in).
- Dependency change Change resource dependency. For example, VM migration.
- Resource monitoring Monitors resources. For example, resource metric values (for example, measured values), resource states, and resource attributes are monitored.
- the system administrator may not perform the above resource management for all the resources of the computer system 120 shown in FIG. For example, it is not preferable that the tenant administrator (or tenant) see changes in tenant environment allocation resources or higher resources before and after resource management.
- the change here is, for example, dependency change or attribute change.
- some tenant administrators may not want the system administrator to see information about higher-level resources.
- FIG. 6 is an example of a resource management method for solving the above-described problem. Specifically, a comparative example of the resource management method when only the tenant environment of the same XaaS type is provided in the computer system is shown. In FIG. 6, tenant environment allocation resources are highlighted (displayed in gray).
- VM # 2 recognizes LU # 3 and accesses LU # 3.
- the management system changes the blade server executing VM # 2 from blade server # 2 to blade server # 3, which is a lower resource of VM # 3 managed by another tenant administrator # 4 Is possible.
- none of the tenant administrators # 3 and # 4 appears to have changed the amount or performance of each tenant environment allocation resource or its upper resources.
- the dependency relationship between the tenant environment allocation resource and its lower-level resources can be changed.
- the number of XaaS that can be provided by the computer system is limited to one.
- the type of tenant environment allocation resource is different among XaaS types, so a computer system and a management system are required for each XaaS type.
- a plurality of types of tenant environment allocation resources corresponding to a plurality of types of XaaS exist in the computer system 120, and the computer system 120 provides a plurality of XaaS type tenant environments.
- the management system 170 enables appropriate resource management for the resources of the computer system 120.
- FIG. 7 shows an example of a resource management method according to the embodiment.
- tenant environment allocation resources are highlighted (displayed in gray).
- the tenant environment allocation resource type is also different. For this reason, if resource management (for example, resource dependency change) is performed without considering the difference in tenant environment allocation resource type, a defect that can be recognized by the tenant administrator (for example, the amount or performance of the tenant environment allocation resource) May fall, or the amount or performance of higher-order resources may fall).
- resource management for example, resource dependency change
- the change destination resource is a tenant environment allocation resource for another XaaS type tenant environment
- a problem that can be recognized by the tenant administrator may occur. This is a problem that occurs when a plurality of types of XaaS corresponding to a plurality of tenant administrators share one computer system 120.
- the management system 170 (for example, the common resource management server 130) allocates resources to the tenant environment for each of a plurality of tenant administrators (tenants), the tenant environment allocation resource and its lower level Manage at least one of the resources (eg both).
- the management system 170 detects an event for the tenant, the management system 170 executes resource management based on the resource category of the resource operated in the processing according to the event.
- Detecting an event for a tenant means that any resource corresponding to the tenant is overloaded (for example, the metric value for that resource exceeds the threshold), or any resource corresponding to the tenant A request from the system administrator may be accepted for such a resource.
- the request may be a request for allocating resources satisfying requirements desired by the tenant administrator or a request for changing the type of XaaS.
- the management system 170 changes the tenant environment allocation resource and the performance or amount of the dependency destination resource with respect to the dependency relationship between the one or more tenant environment allocation resources and the one or more dependency destination resources. Do not make changes that change. This is because such a dependency change is visible to the tenant administrator (or tenant). For example, when a change occurs in the performance or amount of the tenant environment allocation resource due to a change in the performance or amount of the dependency destination resource, the change can be recognized by the tenant administrator (or tenant). As an example, the number of dependent resources decreases, and as a result, the amount of dependent resources (for example, memory capacity) decreases.
- the number of dependent resources decreases, and as a result, the amount of dependent resources (for example, memory capacity) decreases.
- the management system 170 (for example, the common resource management server 130) has the same performance or amount of the dependency destination resource before and after the change of the dependency relationship between the one or more tenant environment allocation resources and the one or more dependency destination resources ( The change may not be changed. This is because there is no change in the performance or amount of the tenant environment allocation resource recognized by the tenant administrator (or tenant) if the dependency destination resource performance or amount does not change. For example, a change in which the number of dependent resources changes but the amount of dependent resources (for example, memory capacity) does not change is permitted.
- changes in the performance or amount of tenant environment allocation resources are as follows.
- the XaaS type is VMaaS
- changes in the performance or amount of tenant environment allocation resources are attributed to VM (Virtual Machine) resource attributes (for example, memory capacity, number of CPUs, virtual NIC (Network Interface Controller / Card), virtual PDEV (Capacity or number), VM identifier, login information (for example, IP address when logging in)).
- VM Virtual Machine
- the change in the performance or amount of the tenant environment allocation resource may be a change in memory capacity.
- the change in the performance or amount of the tenant environment allocation resource may be the same as in the case where the XaaS type is VMaaS or a change in memory.
- the performance or amount of the tenant environment allocation resource changes according to the storage device resource attributes (for example, LUN (Logical Unit Number), port number, VOL identifier, VOL capacity, pool configuration (for example, tier). A change in at least one of the ratios.
- the management system 170 (for example, the common resource management server 130) performs resource interchange between lower resources of different XaaS types. Specifically, for example, it is assumed that LU # 1 is provided to tenant administrator # 1 as a tenant environment allocation resource of STGaS, and pool # 1 is a lower-level resource. Further, it is assumed that VM # 1 is provided to tenant administrator # 2 as a tenant environment allocation resource of VMaaS and pool # 2 is a lower-level resource.
- the management system 170 can grasp the status of the resource by repeatedly (for example, periodically) receiving information including the metric value (for example, measured value) of the resource from the computer system 120.
- the management information includes information representing dependency relationships (for example, topology relationships) of a plurality of resources and information representing tenant environment allocation resources and lower resources for each of a plurality of tenant administrators (tenants). To do.
- the management system 170 detects an overload of the pool # 2, the management system 170 moves the data # 2 (D # 2) in the pool # 2 to another pool in order to eliminate the overload of the pool # 2. It is assumed that (the pool associated with LU # 2 (VOL according to thin provisioning) is changed to another pool). It is assumed that the management system 170 detects that the pools # 1 and # 3 are the migration destination candidates for the data # 2 and the load on the pool # 1 is the lowest based on the management information. Here, based on the management information, the management system 170 detects that both the pool # 1 and the pool # 2 correspond to the resource category of the lower resource. Since the change of the pool, which is a lower-level resource, is not visible to the tenant administrator, the management system 170 moves data # 2 (D # 2) from pool # 2 to pool # 1 and LU # 2 to pool # 2. Instead of pool # 1.
- the management system 170 (for example, the common resource management server 130) can execute resource management that does not cause a problem that the tenant administrator can recognize. Even if the XaaS type is different between tenant environments and the tenant environment allocation resource type is different, the management system 170 of this embodiment manages the resources of the computer system in association with the resource categories. Resource interchange is possible between resources of the same type that are subordinate resources.
- resources of a plurality of resource types included in the computer system 120 have a dependency relationship between different resource types, for example, a hierarchical topology configuration (the route may not exist).
- the resource may be a virtual resource or a physical resource.
- APP application program
- OS operating system
- VM virtual memory and virtual CPU
- LPAR Logical partitioning
- blade server blade server element
- storage device for example, LU (VOL), pool, PDEV, PG (parity group)
- the concept of “upper / lower” may differ depending on what is being managed (for example, monitored), but may be defined in the management system 170 according to a predetermined standard. For example, when resources are in a “connection relationship”, one resource may be lower, and the other resource that is dependent on one resource (based on one resource) may be higher. In the case of “inclusion relationship” between resources, one resource may be lower and the other resource including one resource may be higher.
- FIG. 8 shows a configuration example of the computer system 120.
- the computer system 120 includes a plurality (or one) of storage devices 220 and a plurality (or one) of blade servers 210 connected to the plurality of storage devices 220 via a SAN (Storage Area Network) 230.
- the blade server 210 is an example of a server device.
- another type of communication medium such as a PCIe bus may be employed.
- FIG. 9 shows a configuration example of the blade server 210.
- the blade server 210 includes an FE-I / F (front-end interface device) 310 connected to the tenant system 110 and the management system 170 (at least one of the integrated management server 160, the XaaS resource management server 140, and the common resource management server 130).
- a BE-I / F (back-end interface device) 340 connected to the storage apparatus 220, a memory 330, and a CPU 320 connected thereto. Based on the blade server 210, LPAR, VM, and APP can be executed or provided.
- FIG. 10 shows a configuration example of the storage apparatus 220.
- the storage apparatus 220 includes a duplexed storage controller 400 and a plurality of PDEVs 460 connected to each storage controller 400.
- a plurality of PGs are configured by the plurality of PDEV 460.
- the storage controller 400 is connected to the FE-I / F 450 connected to the blade server 210 and the management system 170 (at least one of the integrated management server 160, the XaaS resource management server 140, and the common resource management server 130) and the PDEV 460. It has a BE-I / F 430, a memory 410, and a CPU 420 connected to them.
- the storage controller 400 provides the LU to the blade server 210, manages the relationship between the LU and the pool, manages the configuration of the PG, and manages the relationship between the PG and the pool.
- FIG. 11 shows a configuration example of the XaaS resource management server 140.
- the XaaS resource management server 140 includes an input device (for example, a keyboard and a pointing device) 610, a display device 620, an I / F (interface device) connected to the integrated management server 160 and the common resource management server 130 (and the computer system 120). ) 650, a storage unit (for example, a memory) 630 for storing a computer program and information, and a CPU 640 connected thereto.
- the input device 610 and the display device 620 may be integrated like a touch panel. Instead of the input device 610 and the display device 620, the XaaS resource management server 140 may be connected to a display computer (for example, a personal computer operated by a tenant administrator) having the input device and the display device.
- the computer program stored in the storage unit 630 is, for example, a tenant management program 660, which is executed by the CPU 640.
- the information stored in the storage unit 630 is, for example, first management information 670.
- the first management information 670 includes a tenant management table 1400, a tenant environment management table 1500, a service model management table 1600, a resource individual management table 1700, and a monitoring table 1750.
- the tenant management program 660 monitors each of a plurality of resources (for example, a higher-level resource and a tenant environment allocation resource) recognized by the XaaS resource management server 140, and the time and monitoring result (for example, metric value, resource state (for example, Operation, failure, etc.) are registered in the monitoring table 1750.
- the processing performed by the tenant management program 660 for example, at least one of the following may be employed.
- the tenant management program 660 requests the common resource management server 130 to allocate resources to the tenant environment (provision of resources allocated to the tenant environment).
- the tenant management program 660 manages resources provisioned in response to the request as tenant environment allocation resources.
- the tenant management program 660 displays resource information corresponding to the tenant administrator.
- the resource information may be displayed based on the first management information 670 that the XaaS resource management server 140 has, or may be displayed based on information from the common resource management server 130.
- the tenant management program 660 may not include a lower resource in at least resource information displayed in response to a resource allocation request (for example, a change request).
- the tenant management program 660 performs a process of changing the dependency relationship between one or more upper resources and one or more tenant environment allocation resources. However, in the process, for example, when there are a plurality of clients (clients of the XaaS resource management server 140) that use different upper resources, the tenant management program 660 determines the dependency destination (migration destination) of the upper resources of the first client. The tenant environment allocation resource or higher resource of the second client is not changed. Further, for example, the tenant management program 660 prevents a plurality of resources of the same type (same hierarchy) from being associated with higher ranks of occupied resources.
- FIG. 12 shows a configuration example of the common resource management server 130.
- the common resource management server 130 includes an input device (for example, a keyboard and a pointing device) 710, a display device 720, an I / F (interface device) 750 connected to the XaaS resource management server 140 and the computer system 120, a computer program, and A storage unit 730 (for example, a memory) that stores information and a CPU (processor) 740 connected thereto are included.
- the input device 710 and the display device 720 may be integrated like a touch panel.
- the common resource management server 130 may be connected to a display computer having an input device and a display device (for example, a personal computer operated by a system administrator).
- the computer program stored in the storage unit 730 is, for example, a system management program 760, which is executed by the CPU 740.
- the information stored in the storage unit 730 is, for example, second management information 770.
- the second management information 770 includes an administrator management table 1800, a tenant environment management table 1900, a resource management table 2000, an operation authority management table 2100, a dependency relationship management table 2200, a monitoring table 2300, and a resource group management table 2400.
- the system management program 760 monitors each of a plurality of resources recognized by the common resource management server 130 (for example, at least a lower resource among upper resources, tenant environment allocation resources, lower resources, and unallocated resources).
- the result eg, metric value, resource state (eg, operation, failure, etc.) is registered in the monitoring table 2300.
- the system management program 760 includes a resource found in response to a request (for example, a resource allocation request) from the integrated management server 160 or the XaaS resource management server 140 in a resource group corresponding to the requesting tenant administrator. .
- the system management program 760 When the system management program 760 receives a request (for example, a resource change request), the resource operated in the processing according to the request (for example, tenant environment allocation resource) is a resource corresponding to the requesting tenant administrator If it is a resource in the group, the process according to the request is performed. On the other hand, if the resource (for example, tenant environment allocation resource) operated in the process according to the request is a resource outside the resource group corresponding to the requesting tenant administrator or the requesting XaaS resource management server 140, the system management program 760 rejects the process according to the request. Such control is performed based on the resource group management table 2400, for example.
- the system management program 760 may receive a request from a computer other than the integrated management server 160 and the XaaS resource management server 140.
- the request is, for example, a snapshot creation request for a backup system (because it is desired to take a snapshot in cooperation with the application quiescence time).
- a resource group management table 2400 (and an operation authority table) such as an access control list may be prepared in advance. For example, when resources are allocated to the tenant administrator, the ID of the allocated resource may be associated with the ID of the tenant administrator (may be registered in the resource group management table 2400).
- the system management program 760 sets the dependency destination resources (typically all dependency destination resources) of one or more tenant environment allocation resources corresponding to the first tenant administrator (first tenant) to the first Do not operate in response to a request from the second tenant administrator (or second tenant) who is a different tenant administrator (or tenant) than the tenant administrator (or first tenant) .
- the system management program 760 sets the first tenant administrator (first tenant administrator) as a target resource candidate to be operated in response to a request from the second tenant administrator (second tenant).
- Dependent resources typically all dependent resources of one or more tenant environment allocation resources corresponding to (one tenant) are not included.
- the information corresponding to the first tenant administrator (first tenant) (at least information related to the dependency destination resource) from being provided to the second tenant administrator (second tenant).
- PaaS and VMaaS as examples.
- an APP (PaaS resource) is provided as a tenant environment allocation resource to the first tenant administrator (first tenant) and the dependency destination resource is a VM (or server), APP (PaaS resource) and Without changing the relationship with the VM (dependence destination resource), the VM that is the dependency destination resource of the APP (PaaS resource) is used as the tenant environment allocation resource (VMaaS resource) or the like as the second tenant administrator (second If it is provided to the tenant), APP (PaaS resource) is a tenant environment allocation resource on the one hand, but becomes a higher resource on the other hand.
- the system management program 760 determines the dependency destination resource of one or more tenant environment allocation resources corresponding to the first tenant administrator (first tenant) as the second tenant administrator (or the second tenant administrator). Since no operation is performed in response to a request from a tenant), such a problem can be avoided.
- the system management program 760 displays resource information (for example, a summary list) provided to the tenant administrator for each tenant administrator (for each tenant).
- the displayed resource information may include information on lower resources, for example, the number of provided resources and the amount of provided resources (for example, storage capacity, number of servers, number of CPUs, memory capacity). .
- the tenant administrator can know how resources are managed (assigned) from the viewpoint of the system administrator.
- the system management program 760 displays the ID of the tenant administrator (or the ID of the resource group including the fault resource) corresponding to the fault resource (the resource corresponding to the state “Fault”)
- the XaaS resource management server 140 is notified of the existence (for example, when a certain PG (parity group) is degenerated), the XaaS resource management server 140 corresponding to the degenerated PG is notified).
- the system management program 760 allocates resources (tenant environment allocation resources) to the tenant environment.
- the system management program 760 performs a process of changing the dependency relationship between one or more tenant environment allocation resources and one or more subordinate resources. In this processing, for example, the system management program 760 does not change the dependency destination (migration destination) of the tenant environment allocation resource of the first tenant administrator to the tenant environment allocation resource or the upper resource of the second tenant administrator. . For example, even if the system management program 760 changes one or more resources on which the tenant environment allocation resource depends, the amount or performance of the one or more resources does not change. Further, for example, the system management program 760 prevents a plurality of resources of the same type (same hierarchy) from being associated with higher ranks of occupied resources.
- the system management program 760 prevents a plurality of resources of the same type (same hierarchy) from being associated with higher ranks of occupied resources.
- the system management program 760 determines the ratio or capacity of the unallocated resources of the computer system 120 when the resources of the computer system 120 are insufficient, when the resource usage rate of the computer system 120 exceeds a predetermined threshold, and In at least one of cases where the value falls below a predetermined threshold value, the fact is notified to the system administrator (computer of the system administrator).
- system management program 760 When receiving a request from the tenant administrator or the system administrator, the system management program 760 refers to the operation authority management table 2100 and executes processing according to the request and the operation authority.
- FIG. 4 shows a configuration example of the integrated management server 160.
- the integrated management server 160 includes an input device (for example, a keyboard and a pointing device) 810, a display device 820, an I / F (interface device) connected to the XaaS resource management server 140 and the common resource management server 130 (and the computer system 120). ) 850, a storage unit 830 (for example, a memory) for storing computer programs and information, and a CPU 840 connected thereto.
- the input device 810 and the display device 820 may be integrated like a touch panel. Instead of the input device 810 and the display device 820, the integrated management server 160 may be connected to a display computer having an input device and a display device (for example, a personal computer operated by a system administrator).
- the computer program stored in the storage unit 830 is, for example, the tenant management program 660 or the system management program 760, which is executed by the CPU 740.
- Information stored in the storage unit 730 is, for example, first management information 670 and second management information 770.
- FIG. 13 shows an example of the configuration of a plurality of resources in the computer system 120.
- the resource configuration of the computer system 120 (for example, the resources from the top to the bottom) according to the resource conditions (for example, performance, capacity, etc.) specified in the resource allocation request from the tenant administrator or the resource allocation control by the system administrator As the dependency), various configurations can be adopted.
- the VM may not exist, may be executed on VM control software (VMM: Virtual Machine Monitor), or may be executed on a hypervisor (HV).
- VMM may be executed on the HV, or may be executed on the LPAR (conceptual logical machine larger than the VM).
- LPAR may be performed on the HV.
- One or more APPs may be executed on the OS.
- the resource on which at least one of the VMM, HV, LPAR, VMM, and OS depends may be a physical resource such as a CPU or a memory.
- the virtual blade server 210 may be constructed within one blade server 210 or across two or more blade servers 210.
- the virtual blade server 210 may include two or more resources from physical resources (for example, CPU and memory) to APP.
- the storage apparatus 220 provides LU (online VOL) to the blade server 210 (for example, VM, LPAR).
- the storage apparatus 220 receives an I / O request designating an LU from the blade server 210, and the storage controller 400 (CPU 420) in the storage apparatus 220 follows the I / O request to perform I / O (for example, an LU area).
- the I / O target data may be temporarily written in the memory.
- a virtual storage device 220 may be constructed within one storage device 220 or across two or more storage devices 220.
- the virtual storage device 220 may include two or more resources from the physical resources (for example, the storage controller 400 and the PDEV 460) to the LU.
- a part of the computer system 120 may be managed by the XaaS resource management server 140, and the rest may be managed by the common resource management server 130.
- the management system 170 may include at least the common resource management server 130 among the XaaS resource management server 140 and the common resource management server 130.
- the management information stored in the management system 170 may be information including the first management information 670 stored in the XaaS resource management server 140 and the second management information 770 stored in the common resource management server 130.
- FIG. 14 shows a configuration example of the tenant management table 1400.
- the tenant management table 1400 holds information related to tenants managed by the tenant administrator.
- the tenant management table 1400 has a record for each tenant. Information stored in each record includes a tenant ID 1401, a tenant name 1402, tenant details 1403, a tenant environment ID 1404, and a charge amount 1405.
- the tenant ID 1401 is a tenant ID.
- the tenant name 1402 represents the name of the tenant.
- the tenant details 1403 is information including details about the tenant.
- the tenant environment ID 1404 is an ID of the tenant environment.
- the charged amount 1405 represents the amount charged according to the use of the tenant environment.
- FIG. 15 shows a configuration example of the tenant environment management table 1500.
- the tenant environment management table 1500 holds information related to the tenant environment managed by the tenant administrator.
- the tenant environment management table 1500 has a record for each tenant environment.
- Information stored in each record includes a tenant environment ID 1501, a service model name 1502, an allocated resource ID 1503, a dependency destination resource ID 1504, and an upper resource ID 1505.
- the tenant environment ID 1501 is an ID of the tenant environment.
- the service model name 1502 represents the name of the XaaS type corresponding to the tenant environment (tenant).
- the allocated resource ID 1503 is an ID of a resource (tenant environment allocated resource) allocated to the tenant environment.
- the dependency destination resource ID 1504 is an ID of a resource on which the tenant environment allocation resource depends.
- the upper resource ID 1505 is an ID of an upper resource that exists above the tenant environment allocation resource.
- the upper resource ID 1505 may represent a dependency relationship between the upper resources in addition to the ID of each upper resource. Each time the upper resource on the tenant environment allocation resource increases or decreases, the upper resource ID 1505 may be updated.
- FIG. 16 shows a configuration example of the service model management table 1600.
- the service model management table 1600 holds information related to the service model (XaaS type).
- the service model management table 1600 has a record for each service model.
- Information stored in each record includes a service model name 1601 and an assigned resource type 1602.
- the service model name 1601 represents the name of the XaaS type.
- the allocation resource type 1602 represents the type of tenant environment allocation resource according to the associated XaaS type.
- FIG. 17 shows a configuration example of the resource individual management table 1700.
- the resource individual management table 1700 holds information on resources to be managed by the tenant administrator.
- the resource individual management table 1700 has a record for each resource to be managed.
- Information stored in each record includes a resource ID 1701, a resource category 1702, a state 1703, and details 1704.
- the resource ID 1701 is a resource ID.
- the resource category 1702 represents a resource category.
- the categories include, for example, “tenant environment allocation resource”, “upper resource”, “lower resource”, and “unallocated resource”.
- a state 1703 represents the state of the resource. Examples of the status 1703 include “operation”, “stop”, “failure”, and the like.
- the value of the state 1703 may be determined based on the monitoring result of the corresponding resource, for example.
- Details 1704 include detailed information about the resource.
- the details 1704 include details on tenant environment allocation resources corresponding to PaaS, information on PaaS execution environment, execution environment requirements at the time of generation, installed middleware type, list of information on VM to be used, and data storage destination. It may contain information to represent. Further, for example, the details 1704 include information on the VM CPU, information on the VM memory, information on the VM virtual disk, information on the storage destination storage area of the VM virtual disk (for example, on the internal file system). Information indicating the location of the server), the ID of the boot image, and the ID of the server execution environment of the server used by the VM.
- the server used by the VM may mean the blade server 210 or LPAR.
- Information on the server execution environment includes information on the CPU of the server corresponding to the environment (for example, the number of CPUs and the number of CPU cores), information on the memory of the server (for example, memory capacity), and information on the network interface of the server (for example, NIC Type, MAC address), information on the I / O interface of the server (for example, HBA (Host Bus Adapter)) (for example, HBA type, WWN (World Wide Name)), the server via the I / O interface
- Information on the LU to be recognized for example, a unique ID (for example, a combination of the storage device 220 serial number and LUN), LU capacity), and information on a storage port (FE-I / F 310 port of the storage controller) May include.
- the unique ID is information used to determine whether or not the same LU is accessed when, for example, the same LU is accessed from multiple storage ports via multipath.
- the tables shown in FIGS. 14 to 17 are the tables included in the first management information 670. It should be noted that the first management information 670 may not include information related to higher-level resources and dependent resources even if information related to tenant environment allocation resources is included. Information related to the upper resources is that each client computer (not shown) of the XaaS resource management server 140 constructs one or more upper resources having an arbitrary dependency on the tenant environment allocation resource, and relates to the one or more upper resources constructed. Information may be retained.
- the XaaS resource management server 140 may reserve a resource to be reserved in advance (in this case, the status 1703 “spare” may be registered in the table 1700), or the execution environment information of the deleted resource (Information necessary for executing the resource (for example, an instance such as login information)) may be managed as a backup.
- FIG. 18 shows a configuration example of the administrator management table 1800.
- the administrator management table 1800 holds information related to the tenant administrator and the system administrator.
- the administrator management table 1800 has a record for each administrator.
- Information stored in each record includes an administrator ID 1801, an administrator type 1802, and a tenant environment ID 1803.
- the administrator ID 1801 is an administrator ID.
- the administrator type 1802 represents the type of administrator (for example, whether it is a tenant administrator or a system administrator).
- the tenant environment ID 1803 is an ID of a tenant environment corresponding to the administrator.
- the tenant environment ID 1803 corresponding to the system administrator may be a value (for example, “-”) which means that the system administrator can manage all the provided tenant environments.
- FIG. 19 shows a configuration example of the tenant environment management table 1900.
- the configuration of the tenant environment management table 1900 in the second management information 770 may be the same as the configuration of the tenant environment management table 1500 in the first management information 670. That is, the tenant environment management table 1900 has a record for each tenant environment, and information stored in each record includes a tenant environment ID 1903, a service model name 1902, an assigned resource ID 1903, a dependency destination resource ID 1904, and an upper resource ID 1905. Each time the upper resource on the tenant environment allocation resource increases or decreases, the ID of the increased or decreased upper resource is notified from the XaaS resource management server 140, and the system management program 760 is notified to the upper resource ID 1905. IDs may be added or deleted. Note that the tenant environment management table 1900 in the second management information 770 may not include the column of the upper resource ID 1905.
- FIG. 20 shows a configuration example of the resource management table 2000.
- the resource management table 2000 holds information about resources.
- the resource management table 2000 has a record for each resource.
- Information stored in each record includes a resource type, resource ID 2002, resource category 2003, dependency resource ID 2004, state 2005, and details 2006.
- the resource type represents the type of resource.
- the resource ID 2002 is a resource ID.
- the resource category 2003 represents a resource category (whether it corresponds to a higher resource, a tenant environment allocation resource, a lower resource, or an unallocated resource).
- the dependency destination resource ID 2004 is an ID of a resource dependency destination resource (child resource).
- the status 2005 represents the status of the resource.
- Details 2006 include information regarding the details of the resource.
- the details 2006 may be similar to the details 1703 described with reference to FIG.
- occupied means an occupied resource.
- the occupied resource means that the resource and the higher-level resource correspond to only one tenant administrator (tenant) (in other words, do not correspond to a plurality of tenant administrators).
- shared means a shared resource.
- the shared resource means that the resource or its upper resource corresponds to a plurality of tenant administrators.
- “Occupied” / “Shared” is a state associated with at least one of the dependency-destination resource and lower-level resources. Any lower resource of the shared resource may be treated as a shared resource.
- the system management program 760 may perform allocation control so that lower resources of the occupied resources are not shared resources as much as possible (maintained as occupied resources as much as possible).
- FIG. 21 shows a configuration example of the operation authority management table 2100.
- the operation authority management table 2100 holds information regarding the operation authority of various administrators. In the operation authority management table 2100, for each of the tenant administrator and the system administrator (administrator type 1802), for each resource category 2003 (resource category 2003), whether or not reference to information about the resource is permitted (operation authority) ) And whether or not the change of the information on the resource is permitted (change of operation authority).
- an “unallocated resource” is a resource that is not allocated to any tenant administrator (tenant) (a resource that does not correspond to any of the higher resource, tenant environment allocated resource, and lower resource).
- the system management program 760 When the system management program 760 receives a request from the first tenant administrator, (a) the resource operated in the processing according to the received request is assigned to the first tenant (tenant corresponding to the first tenant administrator). If it is an allocated resource, the process according to the request is executed. (B) If the resource operated in the process according to the received request is a resource allocated to a tenant other than the first tenant, the request is executed. Reject the process that follows. When receiving a request from the system administrator of the computer system, the system management program 760 executes a process based on the content of the process according to the received request and the authority assigned to the system administrator.
- FIG. 22 shows a configuration example of the dependency management table 2200.
- Dependency management table 2200 holds information on resource type dependency.
- the dependency management table 2200 has a record for each resource type.
- Information stored in each record includes a resource type name 2001 and a dependency destination resource type name 2002.
- the resource type name 2001 represents the name of the resource type.
- the dependence destination resource type name 2002 represents the name of the resource type of the resource that can be the dependence destination of the resource belonging to the resource type. There may be a plurality of dependent resource types for one resource type.
- the dependency relationship represented by the dependency relationship management table 2200 represents a resource type dependency relationship that can be constructed in the computer system 120.
- the actual dependency relationships of a plurality of resources are constructed within the range allowed by the dependency relationship management table 2200.
- the actual dependency relationship is represented by the resource management table 2000.
- FIG. 23 shows a configuration example of the monitoring table 2300.
- the monitoring table 2300 holds information related to monitoring results (monitoring results for resources of the computer system 120) by the system management program 760.
- the monitoring table 2300 may include, for example, time (information indicating the time at which the monitoring result is acquired) 2301 and monitoring result (information indicating the monitoring result (for example, metric value, resource state)) 2302.
- the monitoring result by the tenant management program 660 (the monitoring result received by the system management program 760 from the tenant management program 660) may be merged with the monitoring table 2300.
- the system management program 760 may monitor lower resources, and the tenant management program 660 may monitor tenant environment allocation resources and higher resources.
- FIG. 24 shows a configuration example of the resource group management table 2400.
- the resource group management table 2400 holds information on resource groups.
- a resource group is a set of resources assigned to one tenant administrator (tenant). That is, the resource group includes not only the tenant environment allocation resource but also at least one of a higher resource and a lower resource.
- the resource group management table 2400 has a record for each resource group. Information stored in each record includes a resource group ID 2401, an administrator ID 2402, a group configuration 2403, and operation authority details 2404.
- the resource group ID 2401 is a resource group ID.
- the administrator ID 2402 is an administrator ID.
- the group configuration 2403 is a list of IDs of resources included in the resource group.
- the operation authority details 2404 includes information related to the operation authority regarding the resource group.
- an administrator ID corresponding to an administrator who has issued a request for resource operation (for example, referring to or changing (for example, assigning) information related to a resource) is assigned to the resource group including the resource. If it matches the corresponding administrator ID 2402, the operation is restricted by the system management program 760 according to the operation authority defined in the operation authority management table 2100. On the other hand, if the administrator ID corresponding to the administrator who issued the request for the resource operation does not match the administrator ID 2402 corresponding to the resource group including the resource, the operation is rejected by the system management program 760.
- the above is the table included in the second management information 770.
- the information on the higher level resource and the tenant environment allocation resource is transmitted to the XaaS resource management server 140 corresponding to the XaaS of the tenant system corresponding to those resources, and the tenant management is performed based on the information.
- Control may be performed by the program 660.
- a part of the control performed by the system management program 760 may be offloaded to the tenant management program 660.
- at least one operation of the upper resource and the tenant environment allocation resource may be restricted by the tenant management program 660.
- each of the integrated management server, the XaaS resource management server 140, and the common resource management server of the management system 170 updates the first management information 670 and the second management information 770 (when there is an information update process). (Or at regular or irregular timings), and may notify each other of information necessary for updating the first management information 670 and the second management information 770. Further, each of the integrated management server, the XaaS resource management server 140, and the common resource management server of the management system 170 acquires or calculates information necessary for the following processing based on the first management information 670 and the second management information 770. To do.
- FIG. 25 shows an outline of the flow of processing performed in response to a request from the tenant administrator.
- the tenant management program 660 of the integrated management server 160 receives a request from the tenant administrator (for example, a resource allocation request) via the input device 810.
- the integrated management server 160 transmits the tenant administrator's request to the XaaS resource management server 140 corresponding to the XaaS type based on the requested XaaS type. For example, when a tenant administrator requests a PaaS tenant environment or a request from the tenant system 110 provided with a PaaS tenant environment, the integrated management server 160 uses the PaaS resource management server 140- 1, a tenant administrator's request (for example, resource allocation request) is transmitted.
- the integrated management server 160 associates and manages each XaaS type and the XaaS resource management server 140 corresponding to the XaaS.
- the XaaS resource management server 140 executes processing based on the received request from the tenant administrator. For example, the XaaS resource management server 140 requests the common resource management server 130 to allocate resources.
- the request includes, for example, an environment construction request (request for construction of a new tenant environment), a resource change request (request for change of resources allocated to an existing tenant environment), a service model change request (request for change of XaaS type) ) And resource reference requests (requests for displaying information about resources).
- resource changes for example, adding a resource to be allocated to an existing tenant environment, removing any tenant environment allocation resource from the existing tenant environment, and changing a tenant environment allocation resource as a dependency destination of a higher-level resource Any of changing (migrating higher-level resources) may be used.
- the common resource management server 130 receives the request.
- the system management program 760 refers to at least one of the operation authority management table 2100 and the resource group management table 2400 as to whether or not the transmission source tenant administrator has an operation authority for processing (operation) according to the request. Judgment by. For example, when referring to the table, the system management program 760 uses the administrator ID (or the administrator ID input when the tenant administrator logs in) as the administrator ID corresponding to the request source administrator (the tenant administrator who transmitted the request). , An administrator ID associated with the request received from the XaaS resource management server 140). In S2502, for example, any one of the following processes (x1) to (x2) or two or more processes may be performed.
- the system management program 760 specifies that the requesting administrator is a tenant administrator, the type of the operation target resource according to the received request, the type of request (resource reference or change), and the operation Based on the authority management table 2100, the presence / absence of operation authority is determined.
- the administrator ID corresponding to the resource group including the ID of the resource matches the specified administrator ID. Is determined based on the resource group management table 2400. Based on the result of the determination, the tenant management program 660 determines whether or not there is an operation authority. In this embodiment, one common resource management server 130 is shared by a plurality of tenant administrators, but a resource group is managed for each tenant. When there is an operation request, it is possible to determine whether the request source administrator is a tenant administrator corresponding to the operation target resource. The presence or absence of execution of processing according to the request is controlled according to the result of the determination.
- the operation is stored in the operation authority management table 2100. It is controlled by the system management program 760 in accordance with the prescribed operation authority. On the other hand, if the manager ID of the manager who issued the operation request does not match the manager ID corresponding to the resource group including the resource, the system management program 760 rejects the operation.
- the system management program 760 of the management system 170 determines that the resource operated in the process according to the request is If the resource is allocated to the first user, the process according to the request is executed. If the resource is allocated to a user other than the first user, the process according to the request is rejected.
- the system management program 760 executes processing according to the request received in S2502. For example, the following are (A) to (D).
- a management system 170 having a CPU (processor) that executes the system management program 760 has resources of different resource types depending on the type of XaaS (X as a Service) among a plurality of resources including a plurality of resource types that the computer system 120 has. Are assigned to a tenant environment, and a plurality of tenant environments including a plurality of XaaS are provided.
- the management system 170 having a CPU (processor) that executes the system management program 760 includes, among the plurality of resources including a plurality of resource types of the computer system 120, resources lower than the resources allocated to each tenant environment. Manage as. For example, the management system 170 records the resource category 2003 as a lower resource in the resource management table 2000 for each resource lower than the resource assigned to each tenant environment. Note that the management system 170 may record and manage any of the tenant environment allocation resource, upper resource, lower resource, and unallocated resource category 2003 in the resource management table 2000 for each of the plurality of resources of the computer system. good.
- the system management program 760 registers a new tenant environment ID and a service model name associated therewith in the tenant environment management table 1900.
- the registered service model name may be a service model name (specified service model name) associated with the environment construction request. Further, the system management program 760 adds a new tenant environment ID to the record corresponding to the request source administrator (update of the administrator management table 1800).
- the system management program 760 acquires the allocated resource type corresponding to the service model name (specified service model name) based on the service model management table 1600.
- the system management program 760 searches the resource management table 2000 for a resource of the assigned resource type corresponding to the specified service model name (resource type).
- resources for example, a resource whose status is “active”
- a condition for example, a condition specified by the requesting administrator
- FIG. 26 shows an example of the search result screen. This screen is an example of a screen for constructing an environment corresponding to LPARaaS.
- a search result for example, a list of tenant environment allocation resource candidates found and details of each resource candidate
- the details of the resource candidates may be the performance and quantity regarding the resource to which each resource candidate depends.
- the system management program 760 may also search for lower resource candidates, but does not include the lower resource candidates in the search result as the display target. This is because it is not necessary for the tenant administrator to know.
- the system management program 760 receives selection of a resource candidate (tenant environment allocation resource candidate) desired by the request source administrator from the search results.
- the system management program 760 registers the ID of the selected resource candidate (the tenant environment allocation resource candidate ID and the dependency resource ID) in the tenant environment management table 1900. As a result, resources are allocated to the tenant environment. Further, the system management program 760 adds the selected resource candidate (ID) to the resource group (group configuration 2403) corresponding to the requesting administrator (update of the resource group management table 2400). Also, the system management program 760 updates the resource management table 2000 for the selected resource candidate and its lower resources.
- the system management program 760 gives priority to the resource of the allocated resource type corresponding to the specified service model name (resource type) from the unallocated resource (resource whose status is “unallocated”). You can look for it.
- the system management program 760 of the management system 170 selects a resource managed as an unallocated resource that is not allocated to any of the plurality of users as a resource (for example, tenant environment allocation resource) allocated to the requesting user. And assign.
- the system management program 760 of the management system 170 allocates one or more subordinate resources of provisioning resources corresponding to other users and unallocated resources that are not allocated to any of the plurality of users to the requesting user. If possible, the unassigned resource may be selected and assigned with priority.
- the system management program 760 assigns a resource of the assigned resource type corresponding to the specified service model name (resource type) to a lower resource corresponding to another tenant administrator (tenant administrator different from the requesting administrator). Alternatively, it may be generated based on an unallocated resource. The system management program 760 may prioritize the reserved resource corresponding to the request source administrator over the unallocated resource.
- Each dependent resource of a tenant environment allocation resource candidate is an unallocated resource (a dynamically generated resource may be an example of an “unallocated resource”) or a lower-level resource corresponding to another tenant administrator It is our shared resource.
- system management program 760 may search for a shared resource as a dependency resource of a tenant environment allocation resource candidate over a dedicated resource among lower resources corresponding to another tenant administrator. Further, the system management program 760 may not use the occupied resource among the lower resources corresponding to another tenant administrator as a candidate resource of the tenant environment allocation resource candidate.
- the system management program 760 also searches the resource management table 2000 for resources lower than the selected resource (tenant environment allocation resource), and uses the found resource as a lower resource to register the tenant environment allocation registered in (A3). Associate with resources.
- the system management program 760 may search for unallocated resources in preference to lower resources corresponding to another tenant administrator.
- the system management program 760 may prioritize the reserved resource corresponding to the request source administrator over the unallocated resource.
- the system management program 760 may search for a shared resource as a lower resource in preference to a dedicated resource among lower resources corresponding to another tenant administrator. Further, the system management program 760 may not use the occupied resources among the lower resources corresponding to the different tenant administrator as candidates. An unallocated resource or a shared resource among lower resources corresponding to another tenant administrator is selected as a lower resource.
- the management system 170 having a CPU (processor) that executes the system management program 760 refers to the resource management table 2000, and at least one of the resources managed as lower resources
- the process according to the resource change request (change process) is executed for the lower level resource.
- the management system 170 that executes the system management program 760 includes, as the change process, the performance or amount of the dependency resource of one or more tenant environment assignment resources before the change process and the one or more tenant environment assignments after the change process.
- a process of changing the dependency relationship between the one or more tenant environment allocation resources and their lower resources is performed so that the performance or amount of the resource dependency resource is the same.
- the management system 170 that executes the system management program 760 refers to the tenant environment management table 1900 and the resource management table 2000, identifies the dependence destination resource from the dependence destination resource IDs 1904 and 2004, and further details each resource from the details 2006. Performance or quantity may be acquired.
- the system management program 760 manages the tenant environment management table 1900, the resource management table 2000, and the resource group management. At least one of the tables 2400 is updated.
- the system management program 760 identifies the service model (XaaS type) corresponding to the tenant environment ID 1803 identified from the service model change request.
- the system management program 760 searches for a tenant environment allocation resource candidate and a dependency destination resource candidate according to the changed service model specified from the service model change request based on the resource management table 2000 (or newly generates a resource) To get).
- the tenant environment allocation resource candidate obtained here may be an unallocated resource (a newly generated resource) or a shared resource among lower resources corresponding to another tenant administrator. Further, the candidates obtained here may be candidates automatically narrowed down by the system management program 760, or may be candidates selected by the request source administrator from the list of found candidates.
- the system management program 760 determines whether the service model can be changed based on the results of (C1) and (C2). If the result of this determination is negative, the service model change is rejected.
- (C4) If the determination result of (C3) is affirmative, the system management program 760 assigns the tenant environment specified in (C1) to the tenant environment allocation resource before the service model change and the IDs of its dependent resources. Instead, the tenant environment allocation resource selected in (C2) and the respective IDs of the dependency destination resources are related (update of the tenant environment management table 1900).
- the system management program 760 determines that the tenant before the change if the service model change is a change in which the tenant environment allocation resource type is a higher type, such as a change from IaaS to PaaS.
- the upper resource on the environment allocation resource may be a tenant environment allocation resource according to the changed service model.
- the system management program 760 selects a resource so that the data in the LU corresponding to the tenant is not updated or a restart for recognition of the path from the tenant system 110 to the LU or the like is not necessary when the service model is changed. .
- the tenant system 110 can use the path before the service model change even after the service model is changed by migrating the data in the LU to the LU after the change.
- the system management program 760 identifies the resource (tenant environment allocation resource and its dependent resource) corresponding to the request source administrator from the administrator management table 1800 and the tenant environment management table 1900.
- the system management program 760 displays the resource list specified in (D1) to the requesting administrator. This resource list does not include information regarding lower-level resources corresponding to the requesting administrator.
- FIG. 27 shows a specific example of VMAAS execution environment construction. The description common to the description of FIG. 25 is omitted or simplified.
- the integrated management server 160 receives an input of a request associated with a VM condition (VM instance requirement) from the tenant administrator, and transmits the request to the XaaS resource management server 140.
- a VM condition VM instance requirement
- the tenant management program 660 of the XaaS resource management server 140 transmits a request associated with the input VM condition to the common resource management server 130 in response to the request.
- the VM condition associated with the request may include a condition regarding an LU provided to the VM as a condition regarding the VM.
- the system management program 760 of the common resource management server 130 receives the request and selects an LPAR (and LU) that matches the condition associated with the received request by referring to the second management information 770. To do.
- the “selection” mentioned here may include dynamic creation of an LPAR that meets the conditions.
- the system management program 760 updates the second management information 770 including the resource management table 2000 and the like.
- step S2704 the system management program 760 transmits an identifier for managing the selected (generated) LPAR to the request source XaaS resource management server 140.
- the tenant management program 660 installs HV (hypervisor) in the LPAR (server) of the identifier from the system management program 760. After that, the tenant management program 660 acquires the LPAR (and LU) configuration information from the HV.
- HV hypervisor
- the tenant management program 660 transmits a request that associates the conditions related to the storage area associated with the LPAR and the LPAR ID (server ID) to the common resource management server 130.
- the system management program 760 receives the request, and selects an LU that meets the conditions associated with the received request by referring to the second management information 770.
- the “selection” mentioned here may include dynamic creation of an LU that meets the conditions.
- the system management program 760 updates the second management information 770 in order to set the LU to be accessible from the designated server (LPAR).
- the system management program 760 transmits information related to the completion of LU allocation to the XaaS resource management server 140.
- the information includes information related to the configuration of the blade server 210 (for example, more detailed information than information managed by the XaaS resource management server 140 (for example, information indicating the fan, power supply, and physical arrangement on the blade server 210), and information related to the LPAR configuration. It may include at least one of (for example, information representing the relationship between the blade server 210 and the LPAR), information about the storage configuration, and information about the connection between the LPAR and the LU (for example, network connection information).
- the tenant management program 660 causes the tenant system 110 to recognize the LU (storage area) newly allocated to the HV based on the information from the system management program 760, and then updates the configuration information via the HV.
- Information necessary in this case includes information on the configuration of the blade server 210, information on the LU (for example, LUN, capacity, connection destination LPAR), and information on the configuration of the VM (for example, , Memory, CPU amount, virtual network, virtual disk), information on the correspondence between the virtual disk and the storage area (LU), OS information (for example, OS image) that executes the VM, IP address, and login to the VM May include at least one of information for (eg, a password).
- the tenant management program 660 instructs creation of a VM of the instance type specified in the HV, applies the OS image specified in the option to the VM, and acquires VM login information (for example, IP address and password). .
- the tenant management program 660 stores the result in the first management information 670 and transmits it to the integrated management server 160.
- the integrated management server 160 notifies the VM login information (for example, IP address and password) to the tenant administrator.
- the tenant administrator logs in to the VM using the notified VM login information and uses the VM.
- S2702 to S2705 may be performed when the tenant management program 660 determines that LPAR (server) is insufficient.
- S2706 to S2709 may be performed when the tenant management program 660 determines that the storage area is insufficient.
- the VM condition VM instance requirement
- the resource type may be specified, but the ID of the resource itself may not be specified.
- FIG. 28 shows a specific example of construction of an execution environment for PaaS. Description of points in common with the description of FIG. 25 (and FIG. 27) is omitted or simplified.
- the integrated management server 160 receives an input of a request associated with a PaaS condition (PaaS instance requirement) from the tenant administrator, and transmits the request to the XaaS resource management server 140.
- PaaS instance requirement includes information on the type of middleware required (for example, Hadoop or DBMS (database management system)) and the scale of the environment executed by the middleware (for example, the amount of memory, the amount of storage, the table size of the database). It's okay.
- the tenant management program 660 of the XaaS resource management server 140 calculates the necessary LPAR (server) and storage area based on the input PaaS conditions in response to the request.
- S2803 is performed.
- S2803 is a process including S2702 to S2705.
- S2804 is performed.
- S2804 is a process including S2706 to S2709.
- the tenant management program 660 creates a VM and applies a boot image including middleware based on the PaaS condition on the VM.
- the tenant management program 660 updates the first management information 670.
- the tenant management program 660 transmits the VM login information to the integrated management server 160.
- the integrated management server 160 notifies the VM login information (for example, IP address and password) to the tenant administrator.
- the tenant administrator logs in to the VM using the notified VM login information and uses the VM.
- step S2809 the tenant management program 660 determines whether scale-up or scale-down is necessary, for example, by monitoring the VM OS.
- S2810 scale-up or scale-down
- the tenant management program 660 requests the common resource management server 130 when a new server (LPAR) is required or when storage performance needs to be improved.
- LPAR new server
- the tenant management program 660 changes the middleware settings and reflects the added or deleted resources.
- the scale up or down can be performed by the following method. For example, an instance requirement update request that the tenant administrator wants to scale up or down is input to the XaaS resource management server 140. Alternatively, for example, the tenant management program 660 allocates fewer resources than requirements specified by the tenant administrator, and increases (or decreases) resources when necessary based on the monitoring result.
- information about middleware for example, monitoring information including middleware configuration information, information indicating the correspondence between middleware and server (LPAR), and elements used for determination of scale-up or down (for example, metric value)
- middleware for example, monitoring information including middleware configuration information, information indicating the correspondence between middleware and server (LPAR), and elements used for determination of scale-up or down (for example, metric value)
- LPAR middleware configuration information
- elements used for determination of scale-up or down for example, metric value
- FIG. 29 shows an example of the flow of processing performed in response to a request from the system administrator.
- the system administrator program determines whether or not the system administrator has an operation authority for processing (operation) in accordance with a request from the system administrator by referring to the operation authority management table 2100.
- the system management program 760 permits processing according to the request. That is, the system management program 760 executes the process.
- the system management program 760 determines whether the process satisfies a predetermined exception condition. For example, even in the process of changing the dependency relationship between one or more tenant environment allocation resources and one or more dependent resources, the amount (or performance) of the one or more dependent resources must be changed before and after the change. For example, a positive determination result (determination result indicating that the exception condition is satisfied) is obtained.
- the system management program 760 rejects execution of the request from the system administrator in S2904.
- FIG. 30 shows an example of the flow of service model change processing.
- the system management program 760 identifies the service model (XaaS type) corresponding to the tenant environment ID 1803 identified from the service model change request. Further, the system management program 760 obtains a tenant environment allocation resource candidate according to the changed service model specified from the service model change request by searching (or newly generating a resource) based on the resource management table 2000. . For example, when the amount of obtained resource candidates does not satisfy the condition (including a case where it is found that a resource candidate satisfying the condition cannot be obtained), the determination result is negative.
- the system management program 760 returns a rejection (error) to the request source.
- the system management program 760 obtains the identified tenant environment in place of the IDs of the tenant environment allocation resource before the service model change and its dependency destination resource in S3003.
- the IDs of the tenant environment allocation resource and its dependent resources are associated (update of the tenant environment management table 1900).
- PaaS is an example of the first XaaS type
- VMaaS an example of IaaS
- the second XaaS type is a lower XaaS type than the first XaaS type (XaaS type corresponding to the lower tenant environment allocation resource type).
- the service model change request received by the system management program 760 specifies a PaaS execution environment (tenant environment).
- the system management program 760 obtains the requirements for creating the PaaS execution environment (for example, the resource amount and performance corresponding to the PaaS execution environment are specified by referring to the resource management table 2000). Identify resources to be allocated as tenant environment allocation resources. The resource is specified preferentially from the resources already associated with the tenant corresponding to the service model change (in particular, when the load of the PaaS execution environment is lower than the predetermined load, for example).
- the system management program 760 adds a resource when the resource (for example, amount or performance) specified in (1B) does not satisfy the condition, and sets the predetermined resource (for example, middleware) so that the added resource is recognized by the predetermined resource (for example, middleware). Change resource settings.
- the system management program 760 displays the login information for the resource specified in (1B) to the requesting administrator (for example, a system administrator or a tenant administrator).
- the system management program 760 refers to the second management information 770 to determine whether or not PaaS can be achieved in the current VM execution environment (VM instance configuration). For example, the system management program 760 determines whether the VM execution environment is within the range of the PaaS execution environment after the change (for example, whether middleware not required in the PaaS execution environment is associated with the VM execution environment) Or not). (2B) When the determination result of (2A) is affirmative, the system management program 760 switches the execution environment (tenant environment) from the VM execution environment to the PaaS execution environment. In this switching, data used by the VM (data in the memory) is not erased.
- the system management program 760 saves data (data in the memory) used by the VM (e.g., saves to the LU), and stops the VMaaS. Then, the system management program 760 constructs a corresponding PaaS execution environment and applies the saved data to the PaaS execution environment.
- the system management program 760 may notify the requesting administrator (for example, a tenant administrator or system administrator) of the changed login information.
- the system management program 760 of the management system 170 refers to the resource management table 2000 to The following control may be executed based on the dependency relationship of each tenant environment allocation resource of the resource type according to the plurality of XaaS types corresponding to the user. That is, the system management program 760 of the management system 170 follows the dependency relationship between the tenant environment allocation resource according to the first XaaS type corresponding to the first user and its upper resources, and the first XaaS type corresponding to the first user. Select a resource of a resource type that does not change at least one of the tenant environment allocation resource and the dependency relationship between the tenant environment allocation resource and its lower resources as the tenant environment allocation resource. Also good.
- FIG. 31 shows an example of occupation resource maintenance.
- Pool # 1 is an occupied resource
- any resources (LU # 1, blade server 210 # 1, VM # 5) that are topologically related to the occupied resource and that are above the occupied resource are occupied. It is a resource.
- Pool # 2 is changed from a shared resource (a resource corresponding to tenant administrator # 2 and #) to an occupied resource (a resource corresponding only to tenant administrator # 2).
- the system management program 760 must migrate the data (D # 3) corresponding to the tenant administrator # 3 among the data in the Pool # 2 to another pool (Pool # 1 or # 3).
- the system management program 760 identifies from the second management information 770 whether each of the migration destination candidates Pool # 1 and # 3 is an occupied resource or a shared resource. Thereby, it is specified that Pool # 1 is an occupied resource, and it is specified that Pool # 3 is a shared resource. The system management program 760 migrates D # 3 to Pool # 3 that is a shared resource (D # 3 is not migrated to Pool # 1 that is an occupied resource).
- the system management program 760 changes the dependency relationship between resources so that the resource above Pool # 2 that becomes the occupied resource also becomes the occupied resource. Specifically, for example, the system management program 760 determines whether each of the resources above Pool # 2 is a shared resource, and sets the resource determined to be a shared resource as an occupied resource. More specifically, for example, the system management program 760 changes the dependency destination of the VM # 2 and the dependency source of the LU # 3 from the blade server 210 # 2 to the blade server in order to make the blade server 210 # 2 an occupied resource. Change to 210 # 3 (shared resource). If such a change is made between lower-level resources corresponding to different tenant administrators, the system management program 760 may make the change without querying the tenant administrator.
- the system management program 760 may be affected by the tenant administrator. Changes may be made when a response is received indicating that permission is issued.
- the system management program 760 of the management system 170 occupies one or more lower resources corresponding to any user, the system management program 760 controls the occupied lower resources and the resources above them to not correspond to other users.
- the system management program 760 of the management system 170 secures a resource of the same type as the subordinate resource type of the tenant environment allocation resource based on the predicted value of the resource increase amount for the tenant environment allocation resource corresponding to any user. .
- the system management program 760 of the management system 170 detects an event for any tenant administrator or tenant, the type of resource operated in the process according to the detected event is reserved for the tenant administrator or tenant. In the case of corresponding to the resource type, the reserved resources may be preferentially allocated to the tenant environment allocation resource corresponding to the tenant administrator or the tenant.
- the resource reserved (reserved) for the requesting tenant administrator may be given the highest priority.
- the priority of unallocated resources may be lower than the priority of resources reserved for the requesting tenant administrator.
- the priority of the shared resource among the lower-level resources corresponding to the tenant administrator different from the requesting tenant administrator is the priority of the resource reserved for the requesting tenant administrator and the priority of the unallocated resource. May be lower than at least one of them.
- the priority of resources reserved for a tenant administrator different from the requesting tenant administrator may be lower than the priority of resources reserved for the requesting tenant administrator.
- the system management program 760 is not assigned to any tenant administrator or tenant as a resource to be assigned to the first tenant administrator or the tenant environment of the first tenant. Both the resource and the tenant administrator other than the first tenant administrator or the first tenant or one or more subordinate resources of the tenant environment allocation resource corresponding to the tenant are the first tenant administrator or the first tenant administrator When it is possible to allocate to the tenant environment of one tenant, the unallocated resources are preferentially allocated to the tenant environment of the first tenant administrator or the first tenant.
- FIG. 5 shows an example of an interface provided by the system management program 760 to each of the XaaS resource management servers 140.
- the system management program 760 receives, from each tenant administrator (XaaS resource management server 140), a request from the tenant administrator, and in response to the request, searches for a resource that matches the request, and information related to the found resource It operates as a platform management function that provides an interface for displaying.
- the provided interface is an interface corresponding to the tenant administrator of the provision destination.
- the system management program 760 when the system management program 760 receives a resource reference request or resource allocation request through the interface provided to the tenant administrator # 1, the resource corresponding to the tenant administrator # 1 is assigned to the tenant environment management table 1900 and the resource.
- the resource information specified from at least the tenant environment management table 1900 in the management table 2000 is displayed on the interface.
- the system management program 760 when the request is a resource reference request, the system management program 760 may include information on lower resources in the information to be displayed. Thereby, the tenant administrator can grasp the dependency relationship with the lower resources.
- the request when the request is a resource allocation request, the system management program 760 may not include information on lower resources in the information to be displayed. Thereby, it can be avoided that the lower-level resource can be operated from the tenant administrator.
- the resource allocation request is at least one example of an environment construction request, a resource change request, and a service model change request.
- the system management program 760 when receiving a reference request from the system administrator, the system management program 760 assigns a resource corresponding to the tenant administrator to at least the tenant of the tenant environment management table 1900 and the resource management table 2000 for each tenant administrator.
- the resource information for each tenant administrator (information of the identified resource) may be displayed as specified from the environment management table 1900 and shown in FIG.
- the system management program 760 stores information on resources corresponding to the tenant. Then, the information to be displayed to the request source is determined, and the determined information is displayed to the request source. Specifically, for example, when the received request is a resource reference request from any of a plurality of tenant administrators or a plurality of tenants, the system management program 760 corresponds to the tenant administrator or tenant. Does not display information on resources below the tenant environment allocation resources above.
- the system management program 760 uses the tenant administrator or tenant corresponding to the tenant as tenant administrator or tenant resource information. Displays information about resources lower than the tenant environment allocation resource, and does not display information about resources higher than one or more tenant environment allocation resources.
- resource allocation control is performed in response to a request from a tenant administrator or system administrator, but instead or in addition, the tenant management indicates that the resource is in a predetermined situation from the monitoring result of the resource.
- the program 660 or the system management program 760 it may be performed by the tenant management program 660 or the system management program 760.
- the plurality of resource management servers 140 may include two or more XaaS resource management servers 140 for the same XaaS (the same type of XaaS).
- the common resource management server 130 may perform the following processing.
- “management operation” for a resource is an operation for control or management related to the resource. Specifically, for example, reference to resource information, dependency relationship between resources of different resource types, and the like. There are changes.
- the common resource management server 130 may manage the provided resource in association with the XaaS resource management server 140 that provided the resource.
- the common resource management server 130 may manage a resource group that is a group of resources provided to the XaaS resource management server 140 for each XaaS resource management server 140.
- the common resource management server 130 When the common resource management server 130 provides a resource that is not included in any resource group to the XaaS resource management server 140, the common resource management server 130 corresponds to the XaaS resource management server 140 that provides the resource. May be included in the selected resource group. (*) Thereafter, the common resource management server 130 may perform control (for example, access control) for each resource group. (*) A first example of control for each resource group is as follows, for example. That is, the common resource management server 130 performs a management operation on the resource from the administrator (typically a tenant administrator) of any XaaS resource management server 140 based on the correspondence relationship between the resource and the XaaS resource management server. Can be accepted.
- the administrator typically a tenant administrator
- the common resource management server 130 manages the management operation target resource if the resource is included in a resource group corresponding to the XaaS resource management server of the management operation source tenant administrator. You may accept the operation.
- the common resource management server 130 rejects the management operation if the resource to be managed is a resource not included in the resource group corresponding to the XaaS resource management server of the tenant administrator who is the management operation source. You can do it.
- a second example of control for each resource group is as follows, for example. That is, the common resource management server 130 may accept a management operation from an administrator (typically a system administrator) of the common resource management server regardless of the above-described correspondence relationship.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
Description
(*)テナント環境割当てリソース:テナント環境に割当てられたリソース。
(*)上位リソース:テナント環境割当てリソースより上位のリソース。
(*)下位リソース:テナント環境割当てリソースより下位のリソース。
(*)未割当てリソース:未割当てリソースはシステム管理者が管理するリソースであって、上位リソース、テナント環境割当てリソース、下位リソースの依存先となっていないリソース。未割当てリソースは、システム管理者によって、下位リソースやテナント環境割当てリソースになり得るものである。
(*)リソース作成:システム管理者が管理するリソースに基づいて、そのリソースより上位のリソースを作成する。
(*)リソース消去:リソースを削除。削除対象リソースと、削除対象リソースの依存先リソースとの依存関係を解放する。その延長として、あるリソースが他のリソースと依存関係をもたない場合、未割当てリソースとして扱われても良い。
(*)属性変更:リソースの属性を変更。なお、属性の一例として、VM(Virtual Machine)の属性は、例えば、メモリ容量、CPU数、仮想NIC(Network Interface Controller/Card)数、仮想PDEV(容量又は数)、VM識別子、ログイン情報(例えばログインするときのIPアドレス)である。
(*)依存関係変更:リソースの依存関係を変更する。例えば、VMのマイグレーションである。
(*)リソース監視:リソースを監視する。例えば、リソースのメトリック値(例えば測定値)、リソースの状態、リソースの属性を監視する。
(1A)システム管理プログラム760が受け付けたサービスモデル変更要求では、PaaS実行環境(テナント環境)が指定されている。
(1B)システム管理プログラム760が、PaaS実行環境作成時の要件を取得し(例えば、PaaS実行環境に対応したリソースの量、性能等を、リソース管理テーブル2000等を参照することにより特定し)、テナント環境割当てリソースとして割当てるべきリソースを特定する。そのリソースの特定は、サービスモデル変更に対応するテナントに既に対応付けられているリソースから優先的に行われる(特に、例えば、PaaS実行環境の負荷が所定負荷より低い場合)。
(1C)システム管理プログラム760は、(1B)で特定したリソース(例えば量又は性能)が条件に満たない場合、リソースを追加し、追加したリソースが所定リソース(例えばミドルウェア)に認識されるよう所定リソースの設定を変更する。
(1D)システム管理プログラム760は、(1B)で特定したリソースのログイン用情報を要求元管理者(例えばシステム管理者又はテナント管理者)に対して表示する。
(2A)システム管理プログラム760は、第2管理情報770を参照して、今のVM実行環境(VMインスタンス構成)でPaaS化できるか否かを判断する。例えば、システム管理プログラム760は、VM実行環境が変更後のPaaS実行環境の条件の範囲内か否か(例えば、VM実行環境に、PaaS実行環境で必要とされていないミドルウェアが関連付けられていないか否か)を判断する。
(2B)(2A)の判断結果が肯定の場合、システム管理プログラム760は、実行環境(テナント環境)を、VM実行環境からPaaS実行環境に切り替える。なお、その切り替えでは、VMが使用するデータ(メモリ内のデータ)が消えないようになっている。例えば、システム管理プログラム760は、VMが使用するデータ(メモリ内のデータ)を退避し(例えばLUへ退避し)、VMaaSを停止する。そして、システム管理プログラム760は、対応するPaaS実行環境を構築し、退避したデータをPaaS実行環境に適用する。システム管理プログラム760は、ログイン用情報(例えばIPアドレス)が変わる場合、変更後のログイン用情報を要求元管理者(例えばテナント管理者又はシステム管理者)に通知してよい。
(*)共通リソース管理サーバ130は、提供されるリソースとそのリソースを提供したXaaSリソース管理サーバ140とを対応づけて管理してよい。例えば、共通リソース管理サーバ130は、XaaSリソース管理サーバ140毎に、そのXaaSリソース管理サーバ140に対して提供されたリソースのグループであるリソースグループを管理してよい。共通リソース管理サーバ130は、XaaSリソース管理サーバ140に、いずれのリソースグループにも含まれていないリソースを提供する場合、その提供されるリソースを、そのリソースの提供先のXaaSリソース管理サーバ140に対応したリソースグループに含めてよい。
(*)その後、共通リソース管理サーバ130は、リソースグループ毎の制御(例えばアクセス制御)を行ってよい。
(*)リソースグループ毎の制御の第1の例は、例えば次の通りである。すなわち、共通リソース管理サーバ130は、いずれかのXaaSリソース管理サーバ140の管理者(典型的にはテナント管理者)からの、リソースに対する管理操作を、リソースとXaaSリソース管理サーバとの対応関係に基づいて受け付けてよい。具体的には、例えば、共通リソース管理サーバ130は、管理操作対象のリソースが、管理操作元のテナント管理者のXaaSリソース管理サーバに対応するリソースグループに含まれているリソースであれば、その管理操作を受け付けてよい。一方、例えば、共通リソース管理サーバ130は、管理操作対象のリソースが、管理操作元のテナント管理者のXaaSリソース管理サーバに対応するリソースグループに含まれていないリソースであれば、その管理操作を拒否してよい。
(*)リソースグループ毎の制御の第2の例は、例えば次の通りである。すなわち、共通リソース管理サーバ130は、共通リソース管理サーバの管理者(典型的にはシステム管理者)からの管理操作を、上述の対応関係に関わらず受け付けてよい。
Claims (15)
- 複数のリソースタイプのリソースを含む複数のリソースを備える計算機システムに接続するインターフェースデバイスと、
前記インターフェースデバイスに接続するプロセッサと、
を有し、
前記プロセッサは、
前記複数のリソースタイプのリソースを含む前記複数のリソースのうち、XaaS(X as a Service)のタイプにより異なるリソースタイプのリソースを、テナント環境に割当て、
複数のXaaSを含む複数のテナント環境を提供し、
前記複数のリソースタイプのリソースを含む前記複数のリソースのうち、各テナント環境に割り当てたリソースより下位のリソースを、下位リソースとして管理し、
リソースの変更要求を受け付けると、前記下位リソースとして管理されたリソースのうち、少なくとも1以上の下位リソースに対して変更処理を実行する、
管理システム。 - 前記プロセッサは、前記計算機システムの複数のリソースそれぞれについて、テナント環境に割り当てられたリソースであるテナント環境割当てリソースと、テナント環境割当てリソースより上位のリソースである上位リソースと、前記下位リソースと、未割当てリソースのいずれかのリソースカテゴリで管理する、
請求項1記載の管理システム。 - 前記プロセッサは、前記変更処理として、
前記変更処理前の1以上のテナント環境割当てリソースの依存先リソースの性能又は量と、前記変更処理後の前記1以上のテナント環境割当てリソースの依存先リソースの性能又は量が同じであるように、前記1以上のテナント環境割当てリソースと前記1以上のテナント環境割当てリソースの下位リソースとの依存関係を変更する処理を行う、
請求項1記載の管理システム。 - 前記変更処理は、いずれかのテナント環境のXaaSタイプを第1XaaSタイプから第2XaaSタイプに変更する処理を含み、
前記プロセッサは、前記変更処理として、
前記第2XaaSタイプに従うリソースタイプのリソースであって、前記第1依存関係及び前記第2依存関係のうちの少なくとも一方が変更されることの無いリソースを、プロビジョニングリソースとして選択する、
請求項1記載の管理システム。 - 前記プロセッサは、いずれかのテナント環境に割り当てられている下位リソースを占有する場合、占有する下位リソース及びその上位にあるリソースを、前記いずれかのユーザ以外のユーザに対応させない、
請求項1記載の管理システム。 - 前記プロセッサは、第1のテナント環境の第1のテナント管理者又は第1のテナントに対応した1以上のテナント環境割当てリソースの依存先リソースを、第1のテナント管理者又は第1のテナントとは別のテナント管理者又はテナントである第2のテナント管理者又は第2のテナントからの要求に応答して操作することを行わない、
請求項1記載の管理システム。 - 前記プロセッサは、第1のテナント管理者又は第1のテナントに対応したテナント環境割当てリソースに関するリソース増加量の予測値を基に、そのテナント環境割当てリソースの下位リソースのタイプと同じタイプのリソースを確保し、
操作されるリソースのリソースタイプが、前記、第1のテナント管理者又は第1のテナントについて確保されているリソースのリソースタイプに該当する場合、前記プロセッサは、前記第1のテナント管理者又は第1のテナントに対応したテナント環境割当てリソースとして、前記確保されているリソースを優先的に割り当てる、
請求項1記載の管理システム。 - 前記プロセッサは、第1のテナント管理者又は第1のテナントのテナント環境に対して割当てるリソースとして、いずれのテナント管理者又はテナントにも割当てられていない未割当てリソースと、前記第1のテナント管理者又は第1のテナント以外のいずれかのテナント管理者又はテナントに対応した1以上のテナント環境割当てリソースの下位リソースとのいずれも、前記第1のテナント管理者又は第1のテナントのテナント環境に割当てることが可能な場合、前記未割当てリソースを優先して前記第1のテナント管理者又は第1のテナントのテナント環境に割当てる、
請求項1記載の管理システム。 - 前記第1のテナント管理者から要求を受けた場合、前記プロセッサは、
前記受けた要求に従う処理において操作されるリソースが前記第1のテナントに割当てられているリソースであれば、その要求に従う処理を実行し、
前記受けた要求に従う処理において操作されるリソースが前記第1のテナント以外のテナントに割当てられているリソースであれば、その要求に従う処理を拒否し、
前記計算機システムのシステム管理者から要求を受けた場合、前記プロセッサは、
前記受けた要求に従う処理の内容と、前記システム管理者に割当てられた権限とに基づく処理を実行する、
請求項8記載の管理システム。 - 複数のテナント管理者又は複数のテナントからリソース参照要求を受け付けた場合、又は、前記計算機システムのシステム管理者からリソース参照要求を受け付けた場合、前記プロセッサは、
テナントに対応したリソースの情報であって、要求元に対して表示する情報を決定し、
決定した情報を、前記要求元に対して表示する、
請求項1記載の管理システム。 - 前記受けた要求が、前記複数のテナント管理者又は複数のテナントのうちのいずれかからのリソース参照要求の場合、前記プロセッサは、そのテナント管理者又はテナントに対応した1以上のテナント環境割当てリソースより下位のリソースの情報を表示しない、
請求項10記載の管理システム。 - 前記受けた要求が、前記システム管理者からのリソース参照要求の場合、前記プロセッサは、テナント管理者又はテナントに対応するリソースの情報として、そのテナント管理者又はテナントに対応した1以上のテナント環境割当てリソースより下位のリソースの情報を表示し、1以上のテナント環境割当てリソースよりも上位のリソースの情報を表示しない、
請求項10記載の管理システム。 - 前記プロセッサは、前記複数のテナントにそれぞれ対応した複数のテナント管理者の各々に対し、そのテナント管理者からの要求に応答してその要求に適合したリソースを探し見つかったリソースに関する情報を表示する機能であるプラットフォーム管理機能として動作するようになっている、
請求項8記載の管理システム。 - 複数のリソースタイプのリソースを含む複数のリソースを備える計算機システムを管理する管理システムであって、
複数タイプのXaaSに対応した複数のXaaSリソース管理サーバと
共通リソース管理サーバと
を有し、
前記複数のXaaSリソース管理サーバの各々は、そのXaaSリソース管理サーバに対応するXaaSに従うテナント環境を提供し、
前記共通リソース管理サーバは、
前記複数のリソースタイプのリソースを含む前記複数のリソースのうち、XaaSのタイプにより異なるリソースタイプのリソースを、そのXaaSに対応したテナント環境に割当て、
前記複数のリソースタイプのリソースを含む前記複数のリソースのうち、各テナント環境に割り当てたリソースより下位のリソースを、下位リソースとして管理し、
リソースの変更要求をいずれかのXaaSリソース管理サーバから受け付けると、前記下位リソースとして管理されたリソースのうち、少なくとも1以上の下位リソースに対して変更処理を実行する、
管理システム。 - 前記複数のXaaSリソース管理サーバは、同一のXaaSについて2以上のXaaSリソース管理サーバを含み、
前記共通リソース管理サーバは、
提供されるリソースとそのリソースを提供したXaaSリソース管理サーバとを対応づけて管理し、
いずれかのXaaSリソース管理サーバの管理者からの、リソースに対する管理操作を、リソースとXaaSリソース管理サーバとの対応関係に基づいて受け付け、
前記共通リソース管理サーバの管理者からの管理操作を、前記対応関係に関わらず受け付ける、
請求項14記載の管理システム。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2015/062279 WO2016170625A1 (ja) | 2015-04-22 | 2015-04-22 | 計算機システムの管理システム |
US15/553,603 US10437642B2 (en) | 2015-04-22 | 2015-04-22 | Management system for computer system |
JP2017513888A JP6392978B2 (ja) | 2015-04-22 | 2015-04-22 | 計算機システムの管理システム |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2015/062279 WO2016170625A1 (ja) | 2015-04-22 | 2015-04-22 | 計算機システムの管理システム |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016170625A1 true WO2016170625A1 (ja) | 2016-10-27 |
Family
ID=57142948
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2015/062279 WO2016170625A1 (ja) | 2015-04-22 | 2015-04-22 | 計算機システムの管理システム |
Country Status (3)
Country | Link |
---|---|
US (1) | US10437642B2 (ja) |
JP (1) | JP6392978B2 (ja) |
WO (1) | WO2016170625A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2021157562A (ja) * | 2020-03-27 | 2021-10-07 | 日鉄ソリューションズ株式会社 | 情報処理装置、情報処理方法、及びプログラム |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9378065B2 (en) | 2013-03-15 | 2016-06-28 | Advanced Elemental Technologies, Inc. | Purposeful computing |
US9721086B2 (en) | 2013-03-15 | 2017-08-01 | Advanced Elemental Technologies, Inc. | Methods and systems for secure and reliable identity-based computing |
WO2017068770A1 (ja) * | 2015-10-22 | 2017-04-27 | 日本電気株式会社 | コンピュータ、デバイス割当管理方法及びプログラム記録媒体 |
CN109844722B (zh) * | 2016-08-12 | 2022-09-27 | 利奇得公司 | 分解式结构交换计算平台 |
US20180097744A1 (en) * | 2016-10-05 | 2018-04-05 | Futurewei Technologies, Inc. | Cloud Resource Provisioning for Large-Scale Big Data Platform |
US11153224B2 (en) * | 2017-02-09 | 2021-10-19 | Radcom Ltd. | Method of providing cloud computing infrastructure |
WO2020219801A1 (en) | 2019-04-25 | 2020-10-29 | Liqid Inc. | Multi-protocol communication fabric control |
EP3959604A4 (en) | 2019-04-25 | 2023-01-18 | Liqid Inc. | MACHINE TEMPLATES FOR DEDICATED COMPUTING UNITS |
US11048491B1 (en) * | 2020-05-11 | 2021-06-29 | Microsoft Technology Licensing, Llc | Cloud on-demand staging environments |
US11442776B2 (en) | 2020-12-11 | 2022-09-13 | Liqid Inc. | Execution job compute unit composition in computing clusters |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2013055601A1 (en) * | 2011-10-11 | 2013-04-18 | International Business Machines Coporation | Discovery-based indentification and migration of easily cloudifiable applications |
WO2014155555A1 (ja) * | 2013-03-27 | 2014-10-02 | 株式会社日立製作所 | 管理システム及び管理プログラム |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102255933B (zh) * | 2010-05-20 | 2016-03-30 | 中兴通讯股份有限公司 | 云服务中介、云计算方法及云系统 |
GB2503463A (en) * | 2012-06-27 | 2014-01-01 | Ibm | Overriding abstract resource manager methods to provide resources to implement nodes in a service definition |
US8990374B2 (en) | 2012-07-18 | 2015-03-24 | Hitachi, Ltd. | Method and apparatus of cloud computing subsystem |
US9942114B1 (en) * | 2014-05-13 | 2018-04-10 | Amazon Technologies, Inc. | Automatic tag-based architecture diagrams |
-
2015
- 2015-04-22 US US15/553,603 patent/US10437642B2/en active Active
- 2015-04-22 WO PCT/JP2015/062279 patent/WO2016170625A1/ja active Application Filing
- 2015-04-22 JP JP2017513888A patent/JP6392978B2/ja active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2013055601A1 (en) * | 2011-10-11 | 2013-04-18 | International Business Machines Coporation | Discovery-based indentification and migration of easily cloudifiable applications |
WO2014155555A1 (ja) * | 2013-03-27 | 2014-10-02 | 株式会社日立製作所 | 管理システム及び管理プログラム |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2021157562A (ja) * | 2020-03-27 | 2021-10-07 | 日鉄ソリューションズ株式会社 | 情報処理装置、情報処理方法、及びプログラム |
Also Published As
Publication number | Publication date |
---|---|
US20180046509A1 (en) | 2018-02-15 |
JP6392978B2 (ja) | 2018-09-19 |
JPWO2016170625A1 (ja) | 2017-09-21 |
US10437642B2 (en) | 2019-10-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6392978B2 (ja) | 計算機システムの管理システム | |
US11663029B2 (en) | Virtual machine storage controller selection in hyperconverged infrastructure environment and storage system | |
US11936731B2 (en) | Traffic priority based creation of a storage volume within a cluster of storage nodes | |
US8327370B2 (en) | Dynamic policy manager method, system, and computer program product for optimizing fractional resource allocation | |
US9582221B2 (en) | Virtualization-aware data locality in distributed data processing | |
US8103826B2 (en) | Volume management for network-type storage devices | |
JP6121527B2 (ja) | 計算機システム及びリソース管理方法 | |
JP5199000B2 (ja) | ファイルサーバリソース分割方法、システム、装置及びプログラム | |
US20210405902A1 (en) | Rule-based provisioning for heterogeneous distributed systems | |
JP2005216151A (ja) | 資源運用管理システム及び資源運用管理方法 | |
US20220057947A1 (en) | Application aware provisioning for distributed systems | |
US20150234671A1 (en) | Management system and management program | |
JP2003345631A (ja) | 計算機システム及び記憶領域の割当方法 | |
WO2015114816A1 (ja) | 管理計算機および管理プログラム | |
JP2019133291A (ja) | 情報処理装置,情報処理システムおよび制御プログラム | |
US10019182B2 (en) | Management system and management method of computer system | |
US11726684B1 (en) | Cluster rebalance using user defined rules | |
US10552224B2 (en) | Computer system including server storage system | |
JP6244496B2 (ja) | サーバストレージシステムの管理システム及び管理方法 | |
US11609831B2 (en) | Virtual machine configuration update technique in a disaster recovery environment | |
CN110955487B (zh) | Hci环境下的vm/容器和卷配置决定方法及存储系统 |
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: 15889864 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2017513888 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15553603 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 15889864 Country of ref document: EP Kind code of ref document: A1 |