WO2020062057A1 - 一种主机升级方法及设备 - Google Patents
一种主机升级方法及设备 Download PDFInfo
- Publication number
- WO2020062057A1 WO2020062057A1 PCT/CN2018/108408 CN2018108408W WO2020062057A1 WO 2020062057 A1 WO2020062057 A1 WO 2020062057A1 CN 2018108408 W CN2018108408 W CN 2018108408W WO 2020062057 A1 WO2020062057 A1 WO 2020062057A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- group
- host
- upgrade
- target
- virtual machines
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 148
- 230000015654 memory Effects 0.000 claims description 45
- 230000008569 process Effects 0.000 claims description 43
- 238000012545 processing Methods 0.000 claims description 37
- 238000012937 correction Methods 0.000 claims description 17
- 238000012986 modification Methods 0.000 claims description 15
- 230000004048 modification Effects 0.000 claims description 15
- 238000010586 diagram Methods 0.000 description 19
- 230000006870 function Effects 0.000 description 18
- 238000004891 communication Methods 0.000 description 9
- 238000004590 computer program Methods 0.000 description 8
- 238000013461 design Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 6
- 238000012423 maintenance Methods 0.000 description 5
- 230000009286 beneficial effect Effects 0.000 description 4
- 230000006399 behavior Effects 0.000 description 2
- 238000013508 migration Methods 0.000 description 2
- 230000005012 migration Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000000717 retained effect Effects 0.000 description 2
- 238000010187 selection method Methods 0.000 description 2
- 230000002155 anti-virotic effect Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001568 sexual effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45575—Starting, stopping, suspending or resuming virtual machine instances
Definitions
- the IaaS layer provides computing, storage, and network resources for use by the SaaS and PaaS layers.
- the server needs to be restarted to complete the upgrade operation of the server; however, restarting the server will interrupt the virtual machines deployed on the server. If the virtual machine is interrupted, it will not be able to continue to provide services , It does not meet the requirements of business continuity.
- an embodiment of the present application provides a method for upgrading a host.
- the method is used to manage upgrades of multiple hosts. Any one of the multiple hosts may be deployed with a virtual machine, and multiple hosts may be deployed. All the virtual machines belonging to a plurality of business groups, the business group processing a business, different business groups handle different services, for each of the business groups corresponds to a maximum number of shutdown corresponding to the business group, the The maximum number of shutdowns of a business group is defined as the maximum number of virtual machines allowed to be shut down in the business group while the business of the business group is running.
- the at least one target host is selectively selected from the multiple hosts for upgrade.
- the selected at least one target host there is no need to migrate a virtual machine thereon, That is, under the condition that the virtual machine service deployed on the at least one target host is not interrupted, the at least one target host is upgraded, which effectively improves the efficiency of host upgrade.
- the upgrade device first obtains load balancing parameters, where the load balancing parameters indicate that when the services of the service group remain running, the number of virtual machines allowed to be shut down in the service group accounts for the total number of virtual machines included in the service group
- the load balancing parameter may be a unified value, or each of the service groups may correspond to one of the load balancing parameters; after that, the upgrade device may The total number of virtual machines to calculate the maximum number of shutdowns of the business group.
- the upgrade device is upgrading the at least one Before the target host, the upgrade group modification instruction may also be received; after that, the at least one target host is added to the upgrade group, and the hosts included in the upgrade group are modified according to the upgrade group modification instruction, such as deleting the upgrade group.
- the upgrade group modification instruction such as deleting the upgrade group.
- the first host and the second host are selectively selected from the multiple hosts to form an upgrade group.
- the need to migrate the virtual machines on it can upgrade at least one target host without interrupting the virtual machine services deployed on the hosts in the upgrade group, which effectively improves the efficiency of host upgrades.
- the upgrade device when the upgrade device upgrades the host, it is relatively convenient to determine the maximum number of shutdowns of the anti-affinity group according to the load balancing parameters.
- the upgrade device is upgrading the upgrade group
- the hosts in the upgrade group may also receive the upgrade group modification instruction; after that, the upgrade device corrects the hosts included in the upgrade group according to the upgrade group modification instructions, such as deleting one or more hosts of the upgrade group.
- an embodiment of the present application further provides an upgrade device, where the upgrade device is configured to execute the first aspect and a method of any design of the first aspect.
- the upgrade device has the function of implementing the behavior in the method example of the first aspect described above.
- the functions may be implemented by hardware, and may also be implemented by hardware executing corresponding software.
- the hardware or software includes one or more modules corresponding to the functions described above.
- the structure of the upgrade device includes a selection unit, a processing unit, and an upgrade unit, and these units can perform the corresponding functions in the method example of the first aspect described above. For details, see the detailed description in the method example. Here Do not go into details.
- an embodiment of the present application further provides an upgrade device, where the upgrade device is configured to execute the second aspect and a method of any design of the second aspect.
- the upgrade device has the function of implementing the behavior in the method example of the second aspect described above.
- the functions can be implemented by hardware, and can also be implemented by hardware executing corresponding software.
- the hardware or software includes one or more modules corresponding to the functions described above.
- the structure of the upgrade device includes a selection unit, a processing unit, and an upgrade unit, and these units can perform the corresponding functions in the method example of the second aspect described above. For details, refer to the detailed description in the method example. Here Do not go into details.
- an embodiment of the present application further provides an upgrade device, where the upgrade device is configured to execute the second aspect and a method of any design of the second aspect.
- the structure of the upgrade device includes a processor and a memory, and the processor executes program instructions in the memory to implement the method in the second aspect.
- the memory is coupled to the processor and stores program instructions and data necessary for the upgrade device.
- the structure of the upgrading device further includes a communication interface for communicating with other devices.
- the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores instructions, and when the computer-readable storage medium runs on the computer, the computer causes the computer to execute the methods described in the above aspects.
- the present application also provides a computer program product containing instructions, which when executed on a computer, causes the computer to execute the methods described in the above aspects.
- the present application further provides a computer chip, the chip is connected to a memory, and the chip is configured to read and execute a software program stored in the memory and execute the methods described in the foregoing aspects.
- FIG. 1 is a schematic diagram of an existing host upgrade method
- FIG. 2 is a schematic structural diagram of a network system according to an embodiment of the present application.
- FIG. 3 is a schematic diagram of a method for upgrading a host according to an embodiment of the present application.
- FIG. 4 is a schematic diagram of a virtual machine deployment provided by an embodiment of the present application.
- FIG. 6 is a schematic diagram of a method for upgrading a host according to an embodiment of the present application.
- FIG. 7 is a structural diagram of an upgrade device according to an embodiment of the present application.
- FIG. 8 is a structural diagram of an upgrade device according to an embodiment of the present application.
- FIG. 9 is a structural diagram of an upgrade device according to an embodiment of the present application.
- FIG. 10 is a structural diagram of an upgrade device according to an embodiment of the present application.
- the embodiments of the present application provide a host upgrade method and device, which can solve the problem of low efficiency of the server upgrade solution in the prior art.
- the methods and devices described in this application are based on the same inventive concept. Since the principles of the methods and devices for solving problems are similar, the implementation of the devices and methods can be referred to each other, and duplicated details will not be repeated.
- VMs virtual machines
- the hosts are numbered, respectively, host 1 and host 2 , ... host N-1, host N, one or more virtual machines are deployed on each host, for convenience of explanation, two virtual machines are deployed on each host as an example; before the upgrade, it will be configured in advance An empty host is used as a redundant host. At this time, two virtual machines on service 1 are migrated to the redundant host. After the virtual machine is migrated to the redundant host, it can continue to work normally.
- Host 1 after the upgrade operation can be used as a new redundant host, and two virtual machines on Host 2 can be migrated to Host 1 after the upgrade operation.
- the two virtual machines of host 1 can continue to work normally, and the host 2 that has been vacated can perform the upgrade operation because no virtual machine is deployed at this time.
- N to the host migrate virtual machines to host N-1, N then moved to an empty host performing an upgrade, the upgrade to complete the operation.
- a device in which a virtual machine is deployed in the host may be a physical server, such as a rack server and a blade server. This application does not limit the specific type of host. Any device that can be deployed with a virtual machine and needs to be upgraded can be used as the host.
- a virtual machine refers to a virtual device with hardware functions simulated by software, such as a virtual computer.
- the virtual machine is deployed on the host and can perform service processing.
- attributes for the virtual machines such as anti-affinity attributes, and the business groups to which they belong.
- the VMs of a business group can be distributed on one host or on different hosts.
- the embodiments of the present application are not limited, and the services mentioned in the embodiments of the present application may be services in a telecommunication scenario, such as voice call services, video services, multimedia services, etc., or services in other application scenarios.
- anti-affinity, anti-affinity group, anti-affinity is a property of the virtual machine, in order to distinguish the anti-affinity of each virtual machine, you can set the anti-affinity property value of the virtual machine, when When the anti-affinity attribute values of the two virtual machines are the same, it indicates that the anti-affinity of the virtual machine is the same; otherwise, it indicates that the anti-affinity of the virtual machine is different; the anti-affinity of the virtual machine can be used to characterize the function of the virtual machine Whether it is deployed on the same host as other virtual machines, that is, virtual machines with different anti-affinity can be deployed on one host, and multiple virtual machines with the same anti-affinity cannot be configured on the same host.
- Anti-affinity group is a kind of business group.
- weak anti-affinity for the virtual machine.
- a virtual machine with weak anti-affinity can interact with any anti-affinity virtual machine. Deployed on a host.
- a virtual machine may not be set with anti-affinity or weak anti-affinity, and a virtual machine without anti-affinity or multiple virtual machines without weak anti-affinity may be allowed to be deployed on one host. on.
- grouping you can divide the same business and divide it into an anti-affinity group; you can also divide the virtual machine that processes the same business and does not have anti-affinity or weak anti-affinity Machines are grouped into an anti-affinity group.
- Load balancing is a cluster technology for hosts or network devices. Load balancing refers to sharing specific services (network services, network traffic, etc.) to multiple hosts or network devices to improve business processing capabilities and ensure high availability of services. In specific application scenarios, you can choose the number of deployment resources (such as the number of certain types of virtual machines) required according to the business scale, and then comprehensively upgrade the actual requirements under different conditions (such as during the failure period). Resource specifications (for example, the minimum number of virtual machines that are actually required for each service to account for the proportion of the entire virtual machines that are in the same service). Load balancing parameters are used to determine the specifications of the actual required resources.
- the embodiment of the present application provides a method for upgrading the host.
- the method for upgrading the host provided by the embodiment of the present application is used to perform the upgrade of the host.
- the type of the upgrade device that performs the method of upgrading the host is not limited, for example, the upgrade device is a chip, or may be a processor, a host, or the like.
- FIG. 2 it is a schematic structural diagram of a network system applicable to the present application, which may include a host cluster composed of multiple hosts and a host management device.
- the host cluster may include multiple hosts, which may be grouped into multiple host groups, and virtual machines may be deployed on each host in each of the host groups.
- the number of virtual machines can be one or more.
- each host in the host group For all virtual machines deployed on each host in the host group, it can be divided into multiple business groups according to services, each business group includes one or more virtual machines, and the virtual machines in each business group are used to execute the same business.
- Multiple anti-affinity groups can also be divided according to the anti-affinity of each virtual machine, and one of the anti-affinity groups is used to perform the same service.
- the host management device is configured to manage each of the host groups. Specifically, the host management device may manage virtual machines deployed on each host in each of the host groups. The host management device may be The virtual machine distribution service deployed on the multiple hosts may also control the multiple hosts to shut down, restart, and so on.
- the host management device includes at least one management host, and the at least one management host cooperates to manage the host cluster.
- the host management device may include an upgrade device that controls the upgrade of the host group, that is, controls the upgrade of each host in the host group.
- FIG. 3 is a schematic diagram of a host upgrade method according to an embodiment of the present application.
- the method shown in FIG. 3 is applied to multiple hosts.
- One or more virtual machines are deployed on each host, and multiple virtual machines deployed on multiple hosts belong to one or more business groups. Multiple virtual machines belonging to a business group can be deployed on different hosts, and the number of virtual machines of the business group deployed on each host is not limited.
- the method includes:
- Step 301 First, the upgrade device selects at least one host among a plurality of hosts as a target host.
- the upgrade device Before selecting the at least one target host, the upgrade device needs to obtain information of the multiple hosts, and the information of the multiple hosts may include part or all of the following information:
- Device information of the multiple hosts such as the identity of each host, etc.
- information of the virtual machines deployed on each host such as the number of virtual machines deployed on each host, the identity of the virtual machine, and the virtual machine's ownership Information of the business group, etc.
- information of each of the business groups such as the identification of the virtual machine in each of the business groups, the service or the code of the service performed by each of the business groups, etc., in some cases
- the information of the service group may further include an identifier of each of the service groups).
- the information of the multiple hosts may be stored in advance in an upgrade device of the host management device, or may be stored in other management devices of the host management device, such as a virtual machine management device or a process management device in the host management device.
- the upgrading device needs to obtain the information of the multiple hosts first.
- the selected at least one target host needs to meet certain conditions, as follows:
- Condition one all virtual machines deployed on the at least one target host belong to one or more target business groups in the multiple business groups.
- a business group to which all virtual machines deployed on the at least one target host belong is referred to as a target business group. It is equivalent to divide the virtual machines on the target host into different service groups according to different services. Any virtual machine deployed on the at least one target host should belong to one target business group of the multiple business groups, and all virtual machines deployed on the at least one target host can belong to the multiple business groups.
- the same target business group may also belong to different target business groups in the multiple business groups, and the number of services determines the number of business groups.
- the embodiment of the present application does not limit the number of target business groups, and may be multiple or one, and the one or more target business groups should be a part or all of the business groups in the multiple business groups.
- Condition 2 Of all the virtual machines deployed on the at least one target host, the total number of virtual machines belonging to each of the target business groups is not greater than the maximum number of shutdowns corresponding to the corresponding target business group.
- the total number of virtual machines belonging to each target business group deployed on the at least one target host is less than or equal to the maximum corresponding to the corresponding target business group. Number of shutdowns.
- the maximum number of shutdowns corresponding to the service group is the maximum number of virtual machines allowed to be shut down in the service group when the service of the service group is running.
- the maximum number of shutdowns corresponding to the target business group is the maximum number of virtual machines that are allowed to shut down in the target business group while keeping the business of the target business group running.
- Shutting down the virtual machines on the at least one target host will not affect the one or more target business groups.
- Business Even if it has a certain impact on the business, the impact is acceptable and has not caused a serious impact on the processing of the business. That is, for the selected at least one target host, the virtual machine on the at least one target host does not need to be migrated, and the at least one target host can be maintained without interrupting the virtual machine services deployed on the at least one target host.
- the upgrade has effectively improved the efficiency of the host upgrade.
- the maximum number of shutdowns can be set manually based on the administrator's experience. It can also be set automatically by the metadata server or host. Parameters such as the response time and storage delay when the business group runs the business can be used as a basis for judging whether the remaining virtual machines in the business group can maintain the business operation of the target business group.
- Strategy 1 Obtain the number of shutdowns by running test samples, for example, run a certain type of business in the business group, and gradually increase the number of shutdowns. If the number of shutdowns is reduced to the Nth virtual machine in the target business group, the business group It is difficult for the response time of the service to meet the preset threshold, then the maximum number of shutdowns of the target business group is N-1;
- the maximum number of shutdowns of the target business group the total number of virtual machines in the target business group -1.
- the number of selected target hosts is not limited.
- the upgrade device may select multiple target hosts, and for any of the target hosts, each of the multiple target hosts is deployed on each of the target hosts.
- the total number of virtual machines of the target business group should be less than or equal to the maximum number of shutdowns corresponding to the corresponding target business group, that is, for any of the target business groups, the number of virtual machines deployed on each target host belongs to The sum of the number of virtual machines in the business group is less than or equal to the maximum number of shutdowns corresponding to the target business group.
- the number of virtual machines included in the target service group is eight, and currently there are five hosts, namely host 1, host 2, host 3, host 4, and host 5; wherein host 1 and host 2 virtual machines of the target business group are deployed on 3, 1 virtual machine of the target business group is deployed on host 4, and 3 virtual machines of the target business group are deployed on host 5, The host 2 is deployed with 0 virtual machines of the target service group.
- the upgrading device may select the host 5 as a target host. In this case, the number of virtual machines on which the target business group is deployed on the host 5 is three.
- the upgrade device may also select the host 1 and the host 2 as the target host, in which case, the host 1 and the host 2 are deployed with the The total number of virtual machines in the target business group is 4, which is less than the maximum number of shutdowns corresponding to the target business group.
- the upgrade device may also select the host 1 and host 5 as the target host. In this case, the host The total number of virtual machines with the target business group deployed on 1 and host 5 is 5, which is equal to the maximum number of shutdowns corresponding to the target business group.
- the upgrade device has multiple solutions for selecting the target host.
- the specific Options When the number of the target hosts is one, any selection method that can satisfy the virtual machines of each target business group deployed on the target host is not larger than the corresponding maximum number of shutdowns of the target business group is applicable In the embodiment of the present application; when the number of target hosts is multiple, the total number of virtual machines that can satisfy the target business group deployed on the multiple target hosts is not greater than the corresponding target business group The selection method of the corresponding maximum shutdown number is applicable to the embodiments of the present application.
- each virtual machine belongs to one Target business group. Different virtual machines can belong to the same target business group, or they can belong to different target business groups.
- the following describes a situation in which a virtual machine deployed on the at least one target host belongs to multiple target business groups.
- the upgrade device selects the at least one target host among the multiple hosts.
- the at least one target host When multiple virtual machines are deployed on the at least one target host, the following situations exist: a virtual machine deployed on one host among the at least one target host and a virtual machine deployed on another host among the at least one target host.
- the machines belong to different target business groups.
- the total number of virtual machines is not greater than the corresponding maximum number of shutdowns of the target business groups.
- the maximum number of shutdowns corresponding to different target service groups may be the same or different, and the embodiment of the present application is not limited.
- the target business group A includes eight virtual machines and the target business group B includes ten virtual machines.
- the upgrade device may select the host 5 as the target host.
- the number of virtual machines on which the target business group A is deployed on the host 5 is 3, which is less than the maximum number of shutdowns of the target business group A, and the target business group is deployed on the host 5
- the number of virtual machines of B is 2, which is less than the maximum number of shutdowns of the target business group B.
- the upgrade device may also select the host 1 and the host 2 as the target host. In this case, the host 1
- the total number of virtual machines on which the target business group A is deployed on host 2 is 4, which is less than the maximum number of shutdowns of the target business group A.
- Virtual hosts on the host 1 and host 2 are deployed on the target business group B.
- the total number of machines is 4, which is equal to the maximum shutdown number of the target service group B.
- the upgrade device may also select the host 1 and the host 5 as the target host. In this case, the hosts 1 and 5
- the total number of virtual machines with the target business group A deployed is 5, which is equal to the maximum number of shutdowns of the target business group A.
- the total number of virtual machines with the target business group B deployed on the host 1 and host 5 is 4, equal to the maximum threshold of the target business group B Number.
- a virtual machine in a business group processes a business of the business group
- the number of virtual machines that need to participate in processing the business of the business group is different.
- the business group is required More virtual machines are involved; when the amount of data to be processed in the business of the business group is small, it is only necessary that fewer virtual machines of the business group are involved.
- the amount of data to be processed in the business group's business will be significantly different at different times of the day.
- the amount of data to be processed in the business group's business during the day is usually larger than that of the business group at night.
- the amount of data to be processed for the service of the business group in the evening is usually greater than the amount of data for the service of the business group in the midnight.
- the maximum number of shutdowns corresponding to this business group can be based on business statistics within a certain period of time, estimated through data statistics, and pre-configured in the host management device.
- each Maximum number of shutdowns for each business group For example, the maximum number of shutdowns corresponding to different service groups may be configured in different time periods.
- the upgrade device may determine the maximum number of shutdowns corresponding to the service group in the current time period.
- the maximum number of shutdowns corresponding to the business group can be determined in other ways besides being pre-configured.
- One of the following is introduced:
- the upgrading device first obtains a load balancing parameter, where the load balancing parameter indicates that when the services of the service group remain running, the number of virtual machines allowed to be shut down in the service group as a percentage of the total number of virtual machines included in the service group .
- the load balancing parameter is stored in an upgrade device or other management device in the host management device; when the load balance parameter is stored in another management device, the upgrade device may obtain the load balance parameter from the other management device.
- the manner in which the upgrade device obtains the load balancing parameters is not limited in the embodiment of the present application.
- the upgrading device After acquiring the load balancing parameters, the upgrading device calculates the maximum number of shutdowns corresponding to the target service group according to the load balancing parameters and the total number of virtual machines included in the service group.
- Step 302 After determining the at least one target host, the upgrade device stops services running on all virtual machines deployed in the at least one target host in the one or more target business groups, and maintains the one or Services running in a plurality of target service groups that are not deployed on a virtual machine of the at least one target host. It should be noted that maintenance is not stopping. Therefore, no maintenance instruction is required to maintain the virtual machine running services. As long as no stopping instruction is issued, it is maintenance.
- the task scheduling component may be delivered to each host in the host group.
- the service data of the service group is data required to run a service of the service group, and may be, for example, task instructions, user data, and the like.
- the upgrade device notifies the task scheduling component, so that the task scheduling component stops services running on all virtual machines deployed in the at least one target host in the one or more target business groups, and maintains Services in the one or more target service groups that are not deployed on a virtual machine running on the at least one target host.
- the upgrade device selects the at least one target host, since the number of virtual machines of each target business group deployed on the at least one target host is not greater than the maximum number of shutdowns corresponding to the corresponding target business group That is, each virtual machine of the target business group deployed on the target host can stop processing the services of the corresponding target business group without affecting the service, and the A virtual machine of each target service group processes a service of the corresponding target service group.
- the upgrade device may send a notification message to the task scheduling component, where the notification message instructs the task scheduling component to stop sending corresponding correspondence to the virtual machines belonging to each business group deployed by the at least one target host.
- Business data of the target business group may be sent to the task scheduling component.
- the upgrade device stops the services running on all the virtual machines deployed on the at least one target host in the one or more target business groups through the task scheduling component, and maintains the one or more Services running in a plurality of target service groups that are not deployed on a virtual machine of the at least one target host.
- This method is only an example. In fact, there are other methods to ensure that the upgrade device stops services running on all virtual machines deployed in the at least one target host in the one or more target service groups and maintains the services. Services in the one or more target service groups that are not deployed on a virtual machine running on the at least one target host.
- the upgrade device may send a stop instruction to all virtual machines in the one or more target business groups that are deployed on the at least one target host, and that are not deployed in the one or more target business groups All virtual machines of at least one target host send running instructions, which is not limited in this application. Any service that can run all virtual machines deployed in the at least one target host in the one or more target business groups and maintain the The manners of the services running on the virtual machines of the one or more target service groups that are not deployed on the at least one target host are all applicable to the embodiments of the present application.
- the upgrade device upgrades the one or more Services of all virtual machines deployed in the at least one target host in each of the target business groups are migrated to virtual machines in the one or more target business groups that are not deployed in the at least one target host.
- the upgrade device may deliver a service running on a virtual machine belonging to each target business group deployed on the at least one target host to a virtual machine on a host other than the at least one target host;
- the virtual machines belonging to the corresponding target business group are deployed on hosts other than the at least one target host among the multiple hosts.
- the upgrade device may migrate the business data of the virtual machines of each business group in the at least one target host to other virtual machines in the target business group; it may also notify other management devices to transfer the at least one
- the business data of the virtual machines of each business group in a target host is migrated to other virtual machines in the target business group; this can ensure that the services processed by the virtual machines of each of the target business groups on the target host will not be processed.
- the interruption can be continued by other virtual machines in each of the target business groups; other virtual machines in the target business group are deployed on hosts other than the at least one target host among the plurality of hosts Of the virtual machines belonging to the target business group.
- the upgrade device will receive the upgrade group correction instruction for The hosts included in the upgrade group are adjusted. For example, due to service requirements, one host in the upgrade group also carries other services and cannot interrupt other services.
- the upgrade group modification instruction instructs the The upgrade device deletes the host from the upgrade group; for example, there are two hosts in the upgrade group that cannot be upgraded simultaneously.
- the upgrade group correction instruction instructs the upgrade device to delete the two hosts. One of the hosts is deleted from the upgrade group.
- Step 303 The upgrade device upgrades the at least one target host.
- the working state of the target host is changed to a maintenance state, and then the virtual machine deployed on the target host is shut down, and the upgrade device directly or indirectly issues an instruction to trigger the target host to restart and upgrade.
- the target host loads an upgrade file and replaces the locally saved related files.
- the target host is upgraded, all virtual machines deployed on the target host are started, and the maintenance state of the target host is cancelled. So far, the upgrade operation of the target host is completed.
- the at least one target host is selectively selected from the multiple hosts for upgrade.
- the selected at least one target host there is no need to migrate a virtual machine thereon, That is, under the condition that the virtual machine service deployed on the at least one target host is not interrupted, the at least one target host is upgraded, which effectively improves the efficiency of host upgrade.
- One or more virtual machines are deployed on each host, multiple virtual machines on multiple hosts belong to multiple anti-affinity groups, and the virtual machines in each anti-affinity group process a business with different anti-affinity
- the virtual machines in the affinity group process different services.
- Multiple virtual machines in the anti-affinity group are deployed on different hosts.
- the maximum number of shutdowns corresponding to the anti-affinity group is to maintain the anti-affinity.
- the method includes:
- Step 601 The upgrade device selects a first host among a plurality of hosts. Among the virtual machines owned by the first host, the total number of virtual machines in each of the anti-affinity groups is not greater than the corresponding anti-affinity group. The maximum number of shutdowns for the affinity group. After the first host is selected, it can be considered that the first host is added to the upgrade group, and the hosts in the upgrade group will be upgraded in subsequent steps.
- Device information of the multiple hosts (such as the identification of each host, etc.), information of the virtual machines deployed on each host (such as the number of virtual machines deployed on each host, the identity of the virtual machine, the Information of the anti-affinity group, etc.), information of each of the anti-affinity groups (such as the identity of the virtual machine in each of the anti-affinity groups, the identity of each of the anti-affinity groups, The service or the code of the service performed by each of the anti-affinity groups, and in some cases, the information of the business group may further include an identifier of each of the business groups).
- Condition one all virtual machines deployed on the first host belong to one or more target anti-affinity groups in the plurality of anti-affinity groups.
- Condition 2 The total number of virtual machines belonging to each of the target anti-affinity groups among all the virtual machines deployed on the first host is not greater than the maximum number of shutdowns corresponding to the target anti-affinity group.
- the total number of virtual machines belonging to each target anti-affinity group deployed on the first host should be less than or equal to the corresponding target anti-affinity group.
- the maximum number of shutdowns for the affinity group In order for the services of the target anti-affinity group to run normally, the total number of virtual machines belonging to each target anti-affinity group deployed on the first host should be less than or equal to the corresponding target anti-affinity group. The maximum number of shutdowns for the affinity group.
- the maximum number of shutdowns corresponding to the anti-affinity group is the maximum number of virtual machines allowed to be shut down in the anti-affinity group when the business of the anti-affinity group is maintained.
- the target anti-affinity The maximum number of shutdowns corresponding to the sex group is the maximum number of virtual machines allowed to be shut down in the target anti-affinity group while the business of the target anti-affinity group is running. Ensuring that the total number of virtual machines of each of the target anti-affinity groups deployed on the first host is less than or equal to the maximum number of shutdowns corresponding to the corresponding target anti-affinity group; When a host is upgraded, virtual machines located outside the first host can still support the running of services to a certain extent.
- the first host can be upgraded without interrupting the virtual machine services deployed on the first host without the need to migrate the virtual machines thereon, Effectively improve the efficiency of host upgrade.
- Step 602 After the upgrade device selects the first host, a second host is selected from the multiple hosts, and the second host and the first host are added to the upgrade group, where the All virtual machines deployed on the second host do not belong to any of the target anti-affinity groups.
- the embodiment of the present application does not limit the number of the second hosts, and the upgrading device may determine one of the second hosts, or may determine a plurality of the second hosts; the virtual machines deployed thereon do not belong to any one. Any host of the target anti-affinity group may serve as the second host.
- the upgrading device may traverse the hosts other than the first host among the multiple hosts, and sequentially determine whether the virtual machines deployed on each host belong to any of the target anti-affinity groups, if not, It is determined as the second host.
- This embodiment of the present application does not limit the number of the second hosts. Any host that satisfies the virtual machines deployed on it does not belong to any of the target anti-affinity groups can be used as the second host.
- Step 603 The upgrade device stops services running on all virtual machines of the host in the one or more target anti-affinity groups deployed in the upgrade group, and maintains the one or more target anti-affinity.
- the task scheduling component may be delivered to each host in the host group.
- the service of the anti-affinity group is run according to the received service data.
- the service data of the anti-affinity group is data required to run a service of the anti-affinity group, and may be, for example, task instructions, user data, and the like.
- the upgrade device notifies the task scheduling component so that the task scheduling component stops all virtual machines of the hosts in the one or more target anti-affinity groups deployed in the upgrade group from running. And maintaining a service running on a virtual machine of the host in the one or more target anti-affinity groups not deployed in the upgrade group.
- the upgrade device selects the first host and the second host, since the virtual machines of each of the target anti-affinity groups deployed on the first host are not larger than the corresponding target
- the maximum number of shutdowns corresponding to the anti-affinity group that is, each virtual machine of the target anti-affinity group deployed on the first host can stop processing the corresponding one without affecting services.
- the services of the target anti-affinity group are processed by the virtual machines of the corresponding target anti-affinity group that are deployed on other hosts.
- the upgrade device may send a notification message to the task scheduling component, and the notification message instructs the task scheduling component to stop deploying to the hosts in the upgrade group and belonging to each of the target anti-affinity.
- the virtual machine of the sex group delivers the corresponding business data of the target anti-affinity group.
- the upgrade device implements, through the task scheduling component, stopping services running on all virtual machines of the hosts deployed in the upgrade group in the one or more target anti-affinity groups, and maintaining the services A service running on a virtual machine of the host in the one or more target anti-affinity groups not deployed in the upgrade group is performed.
- This method is only an example. In fact, there are other methods to ensure that the upgrade device stops all virtual machines running on the hosts in the one or more target anti-affinity groups deployed in the upgrade group. And maintain a service running on a virtual machine of a host in the one or more target anti-affinity groups that is not deployed in the upgrade group.
- the upgrade device may send a stop instruction to all virtual machines of the host deployed in the upgrade group in the one or more target anti-affinity groups, and send the anti-affinity to the one or more target anti-affinity groups.
- All virtual machines of the hosts in the group that are not deployed in the upgrade group send run instructions, which is not limited in this application.
- anyone that can be deployed in the upgrade group in the one or more target anti-affinity groups can be stopped.
- the services running on all the virtual machines of the host and the manner of maintaining the services running on the virtual machines of the host in the one or more target anti-affinity groups that are not deployed in the upgrade group are applicable to the embodiments of the present application.
- the upgrade device migrates services running on all virtual machines of the hosts in the one or more target anti-affinity groups deployed in the upgrade group to the one or more target business groups that are not deployed in the Upgrade the virtual machines of the hosts in the group.
- the upgrade device may migrate business data of each of the virtual machines of the target anti-affinity group deployed on the hosts in the upgrade group to other virtual machines in the target anti-affinity group. ; May also notify other management devices to migrate the virtual machines belonging to each of the target anti-affinity groups deployed on the hosts in the upgrade group to other corresponding ones of the target anti-affinity groups with business data; Virtual machines; this can ensure that the services processed by the virtual machines of the target anti-affinity group on the first host will not be interrupted and can be processed by other virtual machines in the target anti-affinity group;
- the other virtual machines in the target anti-affinity group are virtual machines that belong to the target anti-affinity group and are deployed on hosts other than the host in the upgrade group among the multiple hosts.
- the upgrade device may further receive the upgrade group correction instruction; after receiving the upgrade group correction instruction, the upgrade device corrects the upgrade group according to the upgrade group.
- the instructions modify the hosts included in the upgrade group.
- the upgrade device receives the upgrade group correction instruction for the upgrade group.
- the hosts included in the upgrade group are adjusted. For example, due to service requirements, one host in the upgrade group also carries other services and cannot interrupt other services. In this case, the upgrade group correction instruction instructs the upgrade device to remove the host from the upgrade group. For another example, there are two hosts in the upgrade group that cannot be upgraded at the same time. In this case, the upgrade group correction instruction instructs the upgrade device to upgrade one of the two hosts from the upgrade. Remove from group.
- the upgrade device may send information of the upgrade group to other management devices, and the information of the upgrade group is used to characterize hosts in the upgrade group, and other management devices may use the information of the upgrade group according to the information of the upgrade group.
- the other management device After determining the upgrade group modification instruction, the other management device sends the upgrade group modification instruction to the upgrade device, and the upgrade device according to the upgrade group modification instruction includes the hosts included in the upgrade group.
- step 303 For the method for upgrading the host, refer to the related description of step 303, and details are not described herein again.
- the first host and the second host are selectively selected from the multiple hosts to form an upgrade group.
- the need to migrate the virtual machines thereon allows the hosts in the upgrade group to be upgraded without interrupting the virtual machine services deployed on the hosts in the upgrade group, which effectively improves the efficiency of host upgrades.
- upgrading hosts in each upgrade group further includes services running on all virtual machines in the one or more target anti-affinity groups deployed on the hosts in the upgrade group, maintaining all Describe the services running on the virtual machines in one or more target service groups that are not deployed on the hosts in the upgrade group.
- the embodiment of the present application further provides an upgrade device for performing the method performed by the upgrade device described in the method embodiment shown in FIG. 3, and related For characteristics, reference may be made to the foregoing method embodiment, and details are not described herein again.
- the upgrade device 700 includes a selection unit 701, a processing unit 702, and an upgrade unit 703:
- the upgrade device 700 is used to manage multiple host upgrades. Any one of the multiple hosts may be deployed with a virtual machine. All the virtual machines deployed on the multiple hosts belong to multiple business groups, and each business group processes One business, different business groups process different services, each business group corresponds to a maximum number of shutdowns, the maximum number of shutdowns corresponding to a business group is to keep the business group's business running, the maximum number of virtual machines allowed to shut down .
- the selection unit 701 is configured to select at least one target host among multiple hosts, and all virtual machines deployed on the at least one target host belong to one or more target services in the multiple service groups. group.
- the processing unit 702 is configured to stop all services running on all the virtual machines deployed on the at least one target host in the one or more target business groups, and maintain the one or more target business groups that are not deployed in all virtual machines. Describe the services running on the virtual machine of at least one target host.
- the upgrading unit 703 is configured to instruct to upgrade the at least one target host.
- the processing unit 702 may further deploy all of the one or more target business groups on the at least one target host.
- the virtual machine is migrated to a virtual machine in the one or more target business groups that is not deployed on the at least one target host, that is, a service of the virtual machine deployed on the at least one target host is delivered to another host Virtual machines so that virtual machines on other hosts continue to process the business of the virtual machines of the at least one target host.
- the maximum number of shutdowns of the business group may be pre-configured or in other ways, one of which is described below:
- the selecting unit 701 first obtains a load balancing parameter, where the load balancing parameter indicates that when the services of the service group remain running, the number of virtual machines allowed to be shut down in the service group accounts for the total number of virtual machines included in the service group. Ratio; after that, the selection unit 701 calculates the maximum number of shutdowns of the business group according to the load balancing parameters and the total number of virtual machines included in the business group.
- the embodiment of the present application further provides an upgrade device for performing the method performed by the upgrade device described in the method embodiment shown in FIG. 6.
- the upgrade device 800 includes a selection unit 801, a processing unit 802, and an upgrade unit 803:
- the upgrade device 800 is used to manage multiple host upgrades, and virtual machines are deployed on the multiple hosts. All the virtual machines deployed on the multiple hosts belong to multiple anti-affinity groups, and each anti-affinity group processes One service, and different anti-affinity groups process different services. Multiple virtual machines in an anti-affinity group are deployed on different hosts among the multiple hosts. Among them, the maximum number of shutdowns of the anti-affinity group. To keep the business of the anti-affinity group running, the maximum number of virtual machines allowed to be shut down in the anti-affinity group.
- the selecting unit 801 is configured to select a first host and a second host among the multiple hosts.
- All virtual machines deployed on the first host belong to one or more target anti-affinity groups of the plurality of anti-affinity groups, and among all the virtual machines deployed on the first host , The total number of virtual machines belonging to each of the target anti-affinity groups is not greater than the maximum number of shutdowns corresponding to the corresponding target anti-affinity group; all virtual machines deployed on the second host do not belong to any The target anti-affinity group.
- the processing unit 802 is configured to stop services running on all the virtual machines of the hosts in the one or more target anti-affinity groups deployed in the upgrade group, and maintain the one or more target anti-affinity A service running on a virtual machine of a host in the sexual group that is not deployed in the upgrade group.
- the upgrade unit 803 is configured to instruct the hosts in the upgrade group to upgrade.
- the processing unit 802 may further deploy all virtual machines of the hosts in the one or more target anti-affinity groups deployed in the upgrade group. Migrating to the virtual machines of the host in the one or more target business groups that are not deployed in the upgrade group; that is, delivering the services of the virtual machines deployed by the hosts in the upgrade group to virtual machines on other hosts Machine, so that the virtual machines on other hosts continue to process the services of the virtual machines deployed by the hosts in the upgrade group.
- the maximum number of shutdowns of the business group may be pre-configured or in other ways, one of which is described below:
- the selection unit 801 first obtains a load balancing parameter, where the load balancing parameter indicates that when the services of the anti-affinity group are kept running, the number of virtual machines allowed to be shut down in the target anti-affinity group accounts for the anti-affinity group. Ratio of the total number of virtual machines included in the affinity group; thereafter, the selecting unit 801 further calculates the number of the anti-affinity group according to the load balancing parameter and the total number of virtual machines included in the anti-affinity group Maximum number of shutdowns.
- the processing unit 802 may also receive the upgrade group modification instruction before the upgrade unit 803 upgrades the hosts in the upgrade group; after that, modify the hosts included in the upgrade group according to the upgrade group modification instruction, such as Delete one or more hosts of the upgrade group.
- the division of units in the embodiments of the present application is schematic, and is only a logical function division. In actual implementation, there may be another division manner.
- the functional units in the embodiments of the present application may be integrated into one process. In the device, it may also exist alone physically, or two or more units may be integrated into one module.
- the above integrated unit may be implemented in the form of hardware or in the form of software functional modules.
- the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
- the technical solution of the present application is essentially a part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium. It includes several instructions to make a terminal device (which may be a personal computer, a mobile phone, or a network device) or a processor execute all or part of the steps of the method in each embodiment of the present application.
- the aforementioned storage media include: U disks, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks or compact discs and other media that can store program codes .
- an embodiment of the present application further provides an upgrade device, which is used to implement the host upgrade method shown in FIG. 3.
- the The upgrade device may take the form shown in FIG. 8.
- the upgrade device 900 shown in FIG. 9 includes at least one processor 901 and a memory 902, and optionally, may further include a communication interface 903.
- a specific connection medium between the processor 901 and the memory 902 is not limited in the embodiment of the present application.
- the memory 902 and the processor 901 are connected by a bus 904 in the figure.
- the bus 904 is indicated by a thick line in the figure.
- the connection modes of other components are only for illustrative purposes and are not cited. Limited.
- the bus 904 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only a thick line is used in FIG. 9, but it does not mean that there is only one bus or one type of bus.
- the processor 901 may have a data transmitting and receiving function, and can communicate with other management devices.
- an independent data transmitting and receiving module such as a communication interface 903, may be provided for transmitting and receiving data.
- data can be transmitted through the communication interface 903.
- the processor 901 in FIG. 9 may call a program stored in the memory 902 so that the upgrade device can execute the upgrade device in the method embodiment shown in FIG. 3. Method of implementation.
- the function / implementation process of the selection unit, the processing unit, and the upgrade unit in FIG. 7 may be implemented by the processor 901 in FIG. 9 calling a computer execution instruction stored in the memory 902.
- the embodiment of the present application further provides an upgrade device, which is used to implement the host upgrade method shown in FIG. 6.
- the The upgrading equipment may take the form shown in FIG. 10.
- the upgrade device 1000 shown in FIG. 10 includes at least one processor 1001 and a memory 1002, and optionally, may further include a communication interface 1003.
- the memory 1002 may be a volatile memory, such as a random access memory; the memory may also be a non-volatile memory, such as a read-only memory, a flash memory, a hard disk drive (HDD), or a solid-state drive (solid-state drive, SSD), or memory 1002 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to this.
- the memory 1002 may be a combination of the above-mentioned memories.
- the specific connection medium between the processor 1001 and the memory 1002 is not limited in the embodiment of the present application.
- the memory 1002 and the processor 1001 are connected by a bus 1004 in the figure, and the bus 1004 is indicated by a thick line in the figure. Limited.
- the bus 1004 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only a thick line is used in FIG. 10, but it does not mean that there is only one bus or one type of bus.
- the processor 1001 may have a data transmitting and receiving function, and can communicate with other management devices.
- an independent data transmitting and receiving module such as a communication interface 1003, may be provided for transmitting and receiving data.
- the processor 1001 is communicating with other management devices. When the device communicates, data can be transmitted through the communication interface 1003.
- the processor 1001 in FIG. 10 can call a program stored in the memory 1002, so that the upgrade device can execute the upgrade device in the method embodiment shown in FIG. Method of implementation.
- the function / implementation process of the selection unit, the processing unit, and the upgrade unit in FIG. 8 may be implemented by the processor 1001 in FIG. 10 calling a computer execution instruction stored in the memory 1002.
- this application may be provided as a method, a system, or a computer program product. Therefore, this application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, this application may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
- computer-usable storage media including, but not limited to, disk storage, CD-ROM, optical storage, etc.
- These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to work in a particular manner such that the instructions stored in the computer-readable memory produce a manufactured article including an instruction device, the instructions
- the device implements the functions specified in one or more flowcharts and / or one or more blocks of the block diagram.
- These computer program instructions can also be loaded on a computer or other programmable data processing device, so that a series of steps can be performed on the computer or other programmable device to produce a computer-implemented process, which can be executed on the computer or other programmable device.
- the instructions provide steps for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
一种主机升级方法及设备,先在多个主机中选取至少一个目标主机,至少一个目标主机需要满足一定的条件;在确定了至少一个目标主机之后,停止一个或者多个目标业务组中部署在至少一个目标主机的所有虚拟机运行的业务,维持一个或者多个目标业务组中未部署在至少一个目标主机的虚拟机运行的业务;之后再对至少一个目标主机进行升级。采用上述方法,有选择的从多个主机中选择至少一个目标主机进行升级,如此可以采用分多个批次的方式对多个主机进行升级,在保证每个业务组业务不中断的前提下,至少一个目标主机可以并行进行升级。
Description
本申请涉及通信技术领域,尤其涉及一种主机升级方法及设备。
在电信场景中的云服务,对应的业务主要通过3层部署,由上自下依次是软件服务(software as a service,SaaS)层、平台服务(platform as a service,PaaS)层、基础设施服务(infrastructure as a service,IaaS)层。SaaS层中部署与业务相关的软件环境和软件逻辑。PaaS层可以提供软件部署平台,省去了硬件和操作***等细节,使得PaaS层可以实现无缝扩展。IaaS是云服务的最底层,主要提供一些基础资源,如云操作***(用于虚拟机的部署)、服务器、存储、交换机等硬件,其中,云操作***可以将根据上层的指令,将虚拟机部署在各个服务器上,IaaS层提供计算、存储、网络资源给SaaS层和PaaS层使用。当IaaS层中的云操作***需要对服务器升级时,需要重启服务器,完成对服务器的升级操作;但服务器的重启会造成服务器上部署的虚拟机中断,若虚拟机中断,则将不能继续提供业务,也就不满足业务连续性的要求。
目前,为保证业务的连续性,在云操作***需要升级时,部署在服务器上的虚拟机通过热迁移技术,在升级前先将待升级服务器上部署的虚拟机迁移到预先配置的冗余服务器上,服务器中虚拟机迁空后,再对迁空的服务器执行升级操作,升级完成后再将升级后的服务器作为进行下一台服务器的升级所需的冗余服务器。
但现有的升级方式,需要配置冗余主机,且热迁移技术中,服务器的升级过程只能单台串行,导致升级效率较低。
发明内容
本申请提供一种主机升级方法及设备,可以解决现有技术中的服务器升级方案效率较低的问题。
第一方面,本申请实施例提供了一种主机升级的方法,所述方法用于管理多个主机升级,所述多个主机的任一主机可部署有虚拟机,多个所述主机上部署的所有虚拟机属于多个业务组,所述业务组处理一个业务,不同所述业务组处理的业务不同,对于每一个所述业务组都对应一个所述业务组对应的最大关机数,所述业务组的最大关机数被定义为保持所述业务组的业务运行时,所述业务组中允许关机的虚拟机的最大数量。具体的,所述升级设备先在所述多个主机中选取至少一个目标主机,所述至少一个目标主机需要满足一定的条件,也即所述至少一个目标主机上部署的所有虚拟机应属于所述多个业务组中的一个或者多个目标业务组,且所述至少一个目标主机上部署的所有虚拟机中,属于每个所述目标业务组的虚拟机总数均不大于对应的所述目标业务组对应的最大关机数。所述升级设备在确定了所述至少一个目标主机之后,停止所述一个或者多个目标业务组中部署在所述至少一个目标主机的所有虚拟机运行的业务,维持所述一个或者多个目标业务组中未部署在所述至少一个目标主机的虚拟机运行的业务;之后再对所述至少一个目标主机进行升级。
通过上述方法,在对所述多个主机升级时,有选择的从多个主机中选择所述至少一个 目标主机进行升级,针对选中的所述至少一个目标主机,不需要迁移其上虚拟机,即可在保证所述至少一个目标主机上部署的虚拟机业务的不中断的情况下,对至少一个目标主机进行升级,有效提高了主机升级的效率。
结合第一方面,在第一方面的第一种可能的实现方式中,所述升级设备在升级所述至少一个目标主机之前,还可以将所述一个或者多个目标业务组中部署在所述至少一个目标主机的所有虚拟机上运行的业务迁移至所述一个或者多个目标业务组中未部署在所述至少一个目标主机的虚拟机,也就是说,将所述至少一个目标主机上部署的虚拟机的业务交付给其他主机上的虚拟机,以使其他主机上的虚拟机继续处理所述至少一个目标主机的虚拟机的业务。
通过上述方法,可以使得所述至少一个目标主机上部署的虚拟机上运行的业务不会中断,可以在主机升级的过程中,可以保证较高的业务处理效率。
结合第一方面和第一方面的第一种可能的实现方式中,在第一方面的第二种可能的实现方式中,所述业务组的最大关机数的设置方式有许多,所述业务组的最大关机数可以是预先配置好的,也可以其他方式,下面列举其中一种:
所述升级设备先获取负载均衡参数,所述负载均衡参数表示的是所述业务组的业务保持运行时,所述业务组中允许关机的虚拟机的数量占所述业务组包含的虚拟机总数的比例,所述负载均衡参数可以一个统一的值,也可以每个所述业务组对应一个所述负载均衡参数;之后,所述升级设备可以根据所述负载均衡参数和所述业务组包含的虚拟机的总数,计算所述业务组的最大关机数。
通过上述方法,所述升级设备在主机升级时,可以较为方便的根据所述负载均衡参数确定出所述业务组的最大关机数。
结合第一方面和第一方面的第一种至第二种可能的实现方式中的任意一种,在第一方面的第三种可能的实现方式中,所述升级设备在升级所述至少一个目标主机之前,还可以接收所述升级组修正指令;之后,将所述至少一个目标主机加入升级组,根据所述升级组修正指令修正所述升级组包含的主机,如删除所述升级组的一个或多个主机。
通过上述方法,可以灵活的对所述升级组包含的主机进行调整,能够适应于不同的升级场景,扩展应用范围。
第二方面,本申请实施例提供了一种主机升级的方法,所述方法用于管理多个主机升级,所述多个主机的任一主机可部署有虚拟机,多个所述主机上部署的所有虚拟机属于多个反亲和性组,每个所述反亲和性组处理一个业务,不同所述反亲和性组处理的业务不同,所述反亲和性组中的虚拟机部署在不同的所述主机上,其中,所述反亲和性组对应的最大关机数被定义为保持所述反亲和性组的业务运行时,所述反亲和性组中允许关机的虚拟机的最大数量。具体的,所述升级设备在所述多个主机中选取第一主机,所述第一主机需满足一定的条件,具体如下:所述第一主机上部署的所有虚拟机属于所述多个反亲和性组中的一个或者多个目标反亲和性组,所述第一主机上部署的所有虚拟机中,属于每个所述目标反亲和性组的虚拟机均总数不大于对应的所述目标反亲和性组对应的最大关机数之后,所述升级设备还需要在所述多个主机中选取第二主机,将所述第二主机和所述第一主机加入升级组,其中,所述第二主机上部署的所有虚拟机不属于所述第一主机上部署的任一所述反亲和性组;所述升级设备在确定了所述第一主机和所述第二主机之后,停止所述一个或者多个目标反亲和性组中部署在所述升级组中的主机的所有虚拟机运行的业务,维持所 述一个或者多个目标反亲和性组中未部署在所述升级组中的主机的虚拟机运行的业务;之后再对所述升级组中的主机进行升级。
通过上述方法,在对所述多个主机升级时,有选择的从多个主机中选择所述第一主机和所述第二主机组成升级组,针对选中的所述升级组中的主机,不需要迁移其上虚拟机,即可在保证所述升级组中的主机上部署的虚拟机业务的不中断的情况下,对至少一个目标主机进行升级,有效提高了主机升级的效率。
结合第二方面,在第二方面的第一种可能的实现方式中,所述升级设备在升级所述升级组中的主机之前,还可以所述一个或者多个目标反亲和性组中部署在所述升级组中的主机的所有虚拟机上运行的业务迁移至所述一个或者多个目标业务组中未部署在所述升级组中的主机的虚拟机;也就是说,将所述升级组中主机上部署的虚拟机的业务交付给其他主机上的虚拟机,以使其他主机上的虚拟机继续处理所述升级组中主机上部署的虚拟机的业务。
通过上述方法,可以使得所述升级组的主机上部署的虚拟机上运行的业务不会中断,可以在主机升级的过程中,可以保证提高的业务处理效率。
结合第二方面和第二方面的第一种可能的实现方式中,在第二方面的第二种可能的实现方式中,所述业务组的最大关机数的设置方式有许多,所述业务组的最大关机数可以是预先配置好的,也可以其他方式,下面列举其中一种:
所述升级设备先获取负载均衡参数,所述负载均衡参数表示的是所述反亲和性组的业务保持运行时,所述反亲和性组中允许关机的虚拟机的数量占所述反亲和性组包含的虚拟机总数的比例;所述负载均衡参数可以一个统一的值,也可以每个所述反亲和性组对应一个所述负载均衡参数;之后,所述升级设备可以根据所述负载均衡参数和所述反亲和性组包含的虚拟机的总数,计算所述反亲和性组的最大关机数。
通过上述方法,所述升级设备在主机升级时,可以较为方便的根据所述负载均衡参数确定出所述反亲和性组的最大关机数。
结合第二方面和第二方面的第一种至第二种可能的实现方式中的任意一种,在第二方面的第三种可能的实现方式中,所述升级设备在升级所述升级组中的主机之前,还可以接收所述升级组修正指令;之后,所述升级设备根据所述升级组修正指令修正所述升级组包含的主机,如删除所述升级组的一个或多个主机。
通过上述方法,可以灵活的对所述升级组包含的主机进行调整,能够适应于不同的升级场景,扩展应用范围。
第三方面,本申请实施例还提供了一种升级设备,所述升级设备用于执行所述第一方面及所述第一方面的任一设计的方法,有益效果可以参见第一方面的描述此处不再赘述。该升级设备具有实现上述第一方面的方法实例中行为的功能。所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中,所述升级设备的结构中包括选择单元、处理单元和升级单元,这些单元可以执行上述第一方面方法示例中的相应功能,具体参见方法示例中的详细描述,此处不做赘述。
第四方面,本申请实施例还提供了一种升级设备,所述升级设备用于执行所述第二方面及所述第二方面的任一设计的方法,有益效果可以参见第二方面的描述此处不再赘述。该升级设备具有实现上述第二方面的方法实例中行为的功能。所述功能可以通过硬件实 现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中,所述升级设备的结构中包括选择单元、处理单元和升级单元,这些单元可以执行上述第二方面方法示例中的相应功能,具体参见方法示例中的详细描述,此处不做赘述。
第五方面,本申请实施例还提供了一种升级设备,所述升级设备用于执行所述第一方面及所述第一方面的任一设计的方法,有益效果可以参见第一方面的描述此处不再赘述。所述升级设备的结构中包括处理器和存储器,所述处理器执行所述存储器中的程序指令,以实现执行所述存储器中的程序指令,以实现上述第一方面中的方法。所述存储器与所述处理器耦合,其保存所述升级设备必要的程序指令和数据。所述升级设备的结构中还包括通信接口,用于与其他设备进行通信。
第六方面,本申请实施例还提供了一种升级设备,所述升级设备用于执行所述第二方面及所述第二方面的任一设计的方法,有益效果可以参见第二方面的描述此处不再赘述。所述升级设备的结构中包括处理器和存储器,所述处理器执行所述存储器中的程序指令,以实现上述第二方面中的方法。所述存储器与所述处理器耦合,其保存所述升级设备必要的程序指令和数据。所述升级设备的结构中还包括通信接口,用于与其他设备进行通信。
第七方面,本申请还提供一种计算机可读存储介质,所述计算机可读存储介质中存储有指令,当其在计算机上运行时,使得计算机执行上述各方面所述的方法。
第八方面,本申请还提供一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机执行上述各方面所述的方法。
第九方面,本申请还提供一种计算机芯片,所述芯片与存储器相连,所述芯片用于读取并执行所述存储器中存储的软件程序,执行上述各方面所述的方法。
图1为现有的主机升级方法的示意图;
图2为本申请实施例提供的一种网络***的结构示意图;
图3为本申请实施例提供的一种主机升级方法示意图;
图4为本申请实施例提供的一种虚拟机的部署示意图;
图5为本申请实施例提供的一种虚拟机的部署示意图;
图6为本申请实施例提供的一种主机升级方法示意图;
图7为本申请实施例提供的一种升级设备的结构图;
图8为本申请实施例提供的一种升级设备的结构图;
图9为本申请实施例提供的一种升级设备的结构图;
图10为本申请实施例提供的一种升级设备的结构图。
本申请实施例提供一种主机升级方法及设备,可以解决现有技术中服务器升级方案的效率较低的问题。其中,本申请所述方法和设备基于同一发明构思,由于方法及设备解决问题的原理相似,因此设备与方法的实施可以相互参见,重复之处不再赘述。
如图1所示,根据云操作***的部署,在各个主机上会部署一个或多个虚拟机(virtual machine,VM);为了方便区分各个主机,对主机进行编号,分别为主机1,主机2,……主机N-1,主机N,在每个主机上均部署有一个或多个虚拟机,为了方便说明,以每台主机上部署两个虚拟机为例;在升级之前,会提前配置一个空的主机作为冗余主机,此时将服务1上的两个虚拟机迁移到冗余主机上,虚拟机迁移到冗余主机上后,可以继续正常工作,迁空的主机1此时由于没有部署虚拟机,则可以执行升级操作;执行了升级操作后的主机1可以作为一个新的冗余主机,主机2上的两个虚拟机可以迁移到执行了升级操作后的主机1中,迁移到执行了升级操作后的主机1的两个虚拟机也可以继续正常工作,迁空了的主机2此时由于没有部署虚拟机,则可以执行升级操作;如此串行,直到主机N上的虚拟机迁移到主机N-1上,迁空的主机N执行升级操作后,完成整个升级操作。
从上述升级过程可以看出,在该方案中,主机的升级过程需要预配置冗余主机,且整个升级过程,无法多个主机并行升级,这就导致主机升级的效率较低。为此,本申请提供了一种主机升级方法。
首先,对本申请中的部分用语进行解释说明,以便本领域技术人员理解。
1、主机,在本申请实施例中,主机中部署有虚拟机的设备,可以是物理服务器,如机架式服务器和刀片式服务器。本申请并不限定主机的具体类型,凡是可以部署有虚拟机,且需要进行升级的设备均可以作为主机。
2、虚拟机,指的是通过软件模拟的具有硬件功能的虚拟设备,例如虚拟计算机,虚拟机部署在主机上,可以进行业务处理。为了对不同的虚拟机进行区分,可以为虚拟机设置属性,如反亲和性属性、归属的业务组等。
3、业务组,通常在执行业务时,需要多个虚拟机一同处理业务,为了区分处理不同业务的虚拟机,将虚拟机划分为组,处理相同业务的虚拟机划分一个业务组,不同业务组处理不同的业务。而一个业务组的虚拟机可以分布在一个主机上,也可以分布在不同的主机上。本申请实施例并不限定,本申请实施例提及的业务可以是电信场景中的业务,如语音通话业务、视频业务、多媒体业务等等,也可以是其他应用场景中的业务。
4、反亲和性,反亲和性组,反亲和性为虚拟机的一种属性,为了区分各个虚拟机的反亲和性,可以设置虚拟机的反亲和性的属性值,当两个虚拟机的反亲和性的属性值相同时,表明虚拟机的反亲和性相同,否则,表明虚拟机的反亲和性不同;虚拟机的反亲和性可用于表征虚拟机能否与其他虚拟机部署在一台主机,也就是说,反亲和性不同的虚拟机可以部署在一个主机上,而反亲和性相同的多个虚拟机则不允许配置在同一主机上,只能分别配置在不同的主机上,一台主机上不允许存在两个相同的反亲和性的虚拟机。当业务组中的所有虚拟机反亲和性相同时,称该业务组也可以称为反亲和性组。即,处理相同业务,且具有相同的反亲和性的虚拟机可以构成反亲和性组。一个反亲和性组执行相同的业务。反亲和性组是业务组的一种。
此外,还可以对虚拟机设置弱反亲和性,例如可以设置弱反亲和性的属性值为一特定的值,具有弱反亲和性的虚拟机可以与任意反亲和性的虚拟机部署在一台主机上。
需要说明的是,虚拟机可以不设置反亲和性或者不设置弱反亲和性,对于没有反亲和性的虚拟机或没有弱反亲和性的多个虚拟机可以允许部署在一个主机上。在分组时,可以将处理同一个业务的、且划分到一个反亲和性组中;还可以将处理同一个业务的、且没有反亲和性的虚拟机或没有弱反亲和性的虚拟机划分到一个反亲和性组中。
5、负载均衡(load balance,LB)参数,负载均衡是一种主机或网络设备的集群技术。 负载均衡是指将特定的业务(网络服务、网络流量等)分担给多个主机或网络设备,以提高业务处理能力,保证业务的高可用性。在具体的应用场景下,可以根据业务规模,选择所需部署资源的数量(如某一类虚拟机的数量),再综合升级时在不同条件下(如在不通过时段),确定实际所需资源的规格(例如,各业务实际所需处于正常运行的虚拟机数量最小数目占整个处于相同业务的虚拟机的比例)。负载均衡参数用于确定的实际所需资源的规格称为。
6、“多个”是指两个或两个以上,其它量词与之类似。“和/或”描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。
为了能够提高主机的升级效率,本申请实施例提供了一种主机升级的方法,如图2所示,以升级设备执行本申请实施例的提供的主机升级的方法,事实上,本申请实施例并不限定执行主机升级的方法的升级设备的类型,例如升级设备是芯片,也可以是处理器、主机等。
如图2所示,为本申请适用的一种网络***的结构示意图,其中可以包括多个主机构成的主机集群、主机管理设备。
所述主机集群中可以包括多个主机,可以对多个主机进行分组,分为多个主机组,在每个所述主机组中的各个主机上可以部署虚拟机,而每个主机上部署的虚拟机的数量可以是一个,也可以多个。
对于所述主机组中的各个主机上部署的所有虚拟机,可以根据业务划分为多个业务组,每个业务组包括一个或多个虚拟机,每个业务组内的虚拟机用于执行同一业务。也可以根据各个虚拟机的反亲和性划分多个反亲和性组,一个所述反亲和性组用于执行同一业务。
所述主机管理设备用于对各个所述主机组进行管理,具体的,所述主机管理设备可以对各个所述主机组中的各个主机上部署的虚拟机进行管理,所述主机管理设备可以为所述多个主机上部署的虚拟机分配业务,也可以控制所述多个主机关机、重启等。所述主机管理设备包括至少一个管理主机,所述至少一个管理主机协同工作,对所述主机集群进行管理。
从功能角度,所述主机管理设备中可以包括升级设备,所述升级设备控制所述主机组的升级,也就是说,控制所述主机组中各个主机的升级。
图3为本申请实施例提供的一种主机升级方法的示意图,如图3所示的方法应用于多个主机。每个主机上部署有一个或多个虚拟机,多个主机上部署的多个虚拟机归属于一个或多个业务组。属于一个业务组的多个虚拟机,可以部署在不同的主机上,并不限定每个主机上部署的该业务组的虚拟机数目。该方法包括:
步骤301:首先,所述升级设备在多个主机中选取至少一个主机作为目标主机。
所述升级设备在选取所述至少一个目标主机之前,需要先获取所述多个主机的信息,所述多个主机的信息可以包括下列信息的部分或全部:
所述多个主机的设备信息(如所述各个主机的标识等)、每个主机上部署的虚拟机的信息(如每个主机上部署的虚拟机的数量、虚拟机的标识、虚拟机所属的业务组的信息等)、每个所述业务组的信息(如每个所述业务组中虚拟机的标识、每个所述业务组所执行的业务或业务的代号等,在一些情况下,所述业务组的信息还可以包括每个所述业务组的标 识)。
所述多个主机的信息可以预先存储在主机管理设备的中的升级设备中,也可以存储在主机管理设备的其他管理设备上,例如主机管理设备中的虚拟机管理设备或进程管理设备,在多个主机的信息存储在主机管理设备中的其他管理设备的情况下,升级设备需要从先获取所述多个主机的信息。
其中,选取的所述至少一个目标主机需要满足一定的条件,具体如下:
条件一、所述至少一个目标主机上部署的所有虚拟机属于所述多个业务组中的一个或者多个目标业务组。
为了方便后文的描述,把所述至少一个目标主机上部署的所有虚拟机所属的业务组称为目标业务组。相当于按照业务的不同,把目标主机上的虚拟机分成不同的业务组。所述至少一个目标主机上部署的任一虚拟机均应该属于所述多个业务组中的一个目标业务组,所述至少一个目标主机上部署的所有虚拟机可以属于所述多个业务组中的同一个目标业务组,也可以属于所述多个业务组中的不同目标业务组,业务的数量决定了业务组的数量。本申请实施例并不限定目标业务组的个数,可以是多个也可以是一个,而所述一个或多个目标业务组应当是所述多个业务组中的业务组的一部分或者全部。
条件二、所述至少一个目标主机上部署的所有虚拟机中,属于每个所述目标业务组的虚拟机总数均不大于对应的所述目标业务组对应的最大关机数。
为了保证所述目标业务组业务的正常运行,应当保证所述至少一个目标主机上部署的属于每个所述目标业务组的虚拟机的总数均小于或等于对应的所述目标业务组对应的最大关机数。
本发明实施例中,业务组对应的最大关机数为保持业务组的业务运行时,业务组中允许关机的虚拟机的最大数量。对应地,目标业务组对应的最大关机数为保持目标业务组的业务运行时,目标业务组中允许关机的虚拟机的最大数量。保证所述至少一个目标主机上部署的每个所述目标业务组的虚拟机的总数小于或等于对应的所述目标业务组对应的最大关机数,即可保证关闭所述至少一个目标主机以对其升级时,位于所述至少一个目标主机之外的虚拟机仍然可以在一定程度上支持业务的运行,关闭所述至少一个目标主机上的虚拟机不会影响所述一个或多个目标业务组的业务。或者,即使对业务有一定影响,但影响是可以接受的,没有对业务的处理造成严重影响。也就是说,针对选中的所述至少一个目标主机,不需要迁移其上虚拟机,即可在保证所述至少一个目标主机上部署的虚拟机业务的不中断的情况下,对至少一个目标主机进行升级,有效提高了主机升级的效率。
需要特别说明的是,最大关机数可以根据管理员的经验进行手动设置。也可以由元数据服务器或者主机自动设置。可以把业务组运行业务时的响应时间、存储延时等参数,作为判断业务组内余下的虚拟机是否能够保持目标业务组的业务运行的依据。
最大关机数可以有多种设置策略。策略一:通过运行测试样例获得关机数量,例如在业务组中运行某种类型的业务,并且逐渐增加关机数量,如果当关闭到所述目标业务组内第N个虚拟机之后,业务组对业务的响应时间难以满足预设阈值,那么所述目标业务组最大关机数是N-1;策略二:根据业务需要的运算资源,以及每个虚拟机所能提供的运算资源,计算出运行业务所需要的保留的虚拟机的数量,目标业务组对应的最大关机数=业务组的虚拟机总数–运行目标业务组内业务需要保留的虚拟机数量。
在一些情况下,至少保留业务组内的一个虚拟机就可以在一定程度上保证一个业务组 内业务的运行,因此:目标业务组的最大关机数=目标业务组的虚拟机总数-1。
本申请实施例中,并不限定选取的目标主机的数量,所述升级设备可以选取多个目标主机,而针对任一所述目标主机,所述多个目标主机上部署的属于每个所述目标业务组的虚拟机的总数量均应小于或等于对应的所述目标业务组对应的最大关机数,也就是说,针对任一所述目标业务组,每个所述目标主机上部署的属于该业务组的虚拟机的数量之和均小于或等于该目标业务组对应的最大关机数。
如图4所示,所述目标业务组包括的虚拟机的数量为8,当前存在五个主机,分别为主机1、主机2、主机3、主机4、主机5;其中所述主机1和主机3上分别部署有所述目标业务组的2个虚拟机,所述主机4部署有所述目标业务组的1个虚拟机,所述主机5部署有所述目标业务组的3个虚拟机,所述主机2部署有所述目标业务组的0个虚拟机。
假设所述目标业务组对应的最大关机数为5,允许关机的虚拟机数量≤(2+0+2+1+3)-5=3,也就是说只要同时关闭的虚拟机总数不超过3个即可。在需要进行设备(主机)的升级时,所述升级设备可以选取所述主机5为目标主机,在这种情况下,所述主机5上部署有所述目标业务组的虚拟机数量是3,小于所述目标业务组对应的最大关机数;所述升级设备也可以选取所述主机1和主机2为所述目标主机,在这种情况下,所述主机1和主机2上部署有所述目标业务组的虚拟机数量总数是4,小于所述目标业务组对应的最大关机数;所述升级设备也可以选取所述主机1和主机5为目标主机,在这种情况下,所述主机1和主机5上部署有所述目标业务组的虚拟机数量总数是5,等于所述目标业务组对应的最大关机数。
基于所述目标业务组中的多个虚拟机在所述多个主机上的部署情况,所述升级设备有多种选择所述目标主机的方案,在本申请实施例中,并不限定具体的选择方案。当所述目标主机数量为一个时,凡是可以满足所述目标主机上部署的每个所述目标业务组的虚拟机均不大于对应的所述目标业务组对应的最大关机数的选择方式均适用于本申请实施例;当所述目标主机数量为多个时,凡是可以满足所述多个目标主机上部署的所述目标业务组的虚拟机的总数量均不大于对应的所述目标业务组对应的最大关机数的选择方式均适用于本申请实施例。
在上述描述中仅是以一个业务组为例进行说明的,在实际的虚拟机部署时,可能会存在多个业务组,针对任一所述主机上部署的虚拟机,每一个虚拟机属于一个目标业务组,不同的虚拟机可以属于相同的目标业务组,也可以属于不同的目标业务组。
下文对所述至少一个目标主机上部署虚拟机属于多个目标业务组的情况进行阐述。
当所述多个主机上部署的虚拟机属于不同业务组时,所述升级设备在所述多个主机中选取所述至少一个目标主机。所述至少一个目标主机上部署多个虚拟机中,存在下面的情况:所述至少一个目标主机中的一个主机上部署的虚拟机与所述至少一个目标主机中的另一个主机上部署的虚拟机归属不同的目标业务组,针对所述至少一个目标主机上属于任一所述目标业务组的虚拟机,虚拟机的总数量均不大于对应的所述目标业务组对应的最大关机数。不同的所述目标业务组对应的最大关机数可以相同,也可以不同,本申请实施例并不限定。
如图5所示,存在两个业务组分别为业务组A和业务组B,所述目标业务组A包括的虚拟机的数量为8,所述目标业务组B包括的虚拟机的数量为10。当前存在五个主机,分别为主机1、主机2、主机3、主机4、主机5;其中所述主机1和主机3上部署有所述目 标业务组A的2个虚拟机,所述主机4部署有所述目标业务组A的1个虚拟机,所述主机5部署有所述目标业务组A的3个虚拟机,所述主机2上未部署有所述目标业务组A的虚拟机,每个主机上部署有所述目标业务组B的2个虚拟机。
假设所述目标业务组A的最大关机数为5,所述目标业务组B的最大关机数为4,所述升级设备可以选取所述主机5为目标主机。在这种情况下,所述主机5上部署有所述目标业务组A的虚拟机数量是3,小于所述目标业务组A的最大关机数,所述主机5上部署有所述目标业务组B的虚拟机数量是2,小于所述目标业务组B的最大关机数;所述升级设备也可以选取所述主机1和主机2为所述目标主机,在这种情况下,所述主机1和主机2上部署有所述目标业务组A的虚拟机数量总数是4,小于所述目标业务组A的最大关机数,所述主机1和主机2上部署有所述目标业务组B的虚拟机数量总数是4,等于所述目标业务组B的最大关机数;所述升级设备也可以选取所述主机1和主机5为目标主机,在这种情况下,所述主机1和主机5上部署有所述目标业务组A的虚拟机数量总数是5,等于所述目标业务组A的最大关机数,所述主机1和主机5上部署有所述目标业务组B的虚拟机数量总数是4,等于所述目标业务组B的最大关机数。
业务组中的虚拟机在处理该业务组的业务时,需参与处理所述业务组的业务的虚拟机数量不同,当该业务组的业务的待处理的数据量较大,则需要该业务组的较多虚拟机均参与;当该业务组的业务的待处理的数据量较小,则只需要所述业务组的较少虚拟机均参与。
例如,在一天的不同时段里,该业务组的业务的待处理数据量会有明显区别,以语音通话业务为例,白天时段该业务组的业务的待处理数据量通常大于夜晚时段该业务组的业务的待处理数据量,傍晚时段该业务组的业务的待处理数据量通常大于午夜时段该业务组的业务的待处理数据量。
该业务组对应的最大关机数可以是基于一定时间内业务统计量为基础,通过数据统计预估,并且预先配置在主机管理设备中的,当所述升级设备需要为主机升级时,可以获取每个业务组对应的最大关机数。例如,在不同的时间段配置可以不同的业务组对应的最大关机数,所述升级设备在选取所述目标主机时,可以确定当前时间段所述业务组对应的最大关机数。
所述业务组对应的最大关机数除了可以预先配置,还可以采用其他方式确定,下面介绍一种:
所述升级设备先获取负载均衡参数,所述负载均衡参数表示所述业务组的业务保持运行时,所述业务组中允许关机的虚拟机的数量占所述业务组包含的虚拟机总数的百分比。
所述负载均衡参数存储主机管理设备中的升级设备或其他管理设备中;当所述负载均衡参数存储在其他管理设备时,所述升级设备可以从其他管理设备获取所述负载均衡参数。所述升级设备获取所述负载均衡参数的方式本申请实施例并不限定。
所述升级设备在获取负载均衡参数之后,根据所述负载均衡参数和业务组包含的虚拟机的总数,计算该目标业务组对应的最大关机数。
步骤302:所述升级设备在确定了所述至少一个目标主机后,停止所述一个或者多个目标业务组中部署在所述至少一个目标主机的所有虚拟机运行的业务,维持所述一个或者多个目标业务组中未部署在所述至少一个目标主机的虚拟机运行的业务。需要说明的是,维持也就是不停止,因此,维持虚拟机运行业务并不需要发出维持指令,只要不发出停止 的指令就属于维持。
通过上述方式,可以保证所述目标业务组的业务能够正常运行,不会使所述目标业务组需要运行的业务中断。
示例性的,由于在所述主机群组中各个主机上部署的虚拟机运行的业务通常是由任务调度组件分配并且下发的,所述任务调度组件可以向所述主机群组中各个主机下发由各个业务组的业务数据,以使得所述主机群组中各个主机上部署的属于各个业务组的虚拟机在接收到对应的所述业务组的业务数据后,根据接收到的业务数据运行所述业务组的业务。
所述业务组的业务数据为运行所述业务组的业务所需的数据,例如,可以是任务指令、用户数据等。
可选地,所述升级设备通知所述任务调度组件,以使所述任务调度组件停止所述一个或者多个目标业务组中部署在所述至少一个目标主机的所有虚拟机运行的业务,维持所述一个或者多个目标业务组中未部署在所述至少一个目标主机的虚拟机运行的业务。所述升级设备在选取了所述至少一个目标主机后,由于所述至少一个目标主机上部署的每个所述目标业务组的虚拟机均不大于对应的所述目标业务组对应的最大关机数,也就是说,所述目标主机上部署的每个所述目标业务组的虚拟机可以在不影响业务的情况下停止处理对应的所述目标业务组的业务,而由部署在其他主机上的每个所述目标业务组的虚拟机处理对应的所述目标业务组的业务。
示例性的,所述升级设备可以向所述任务调度组件发送通知消息,所述通知消息指示所述任务调度组件停止向所述至少一个目标主机部署的属于每个业务组的虚拟机下发对应的所述目标业务组的业务数据。
在上述描述中,所述升级设备通过所述任务调度组件了停止所述一个或者多个目标业务组中部署在所述至少一个目标主机的所有虚拟机运行的业务,并维持了所述一个或者多个目标业务组中未部署在所述至少一个目标主机的虚拟机运行的业务。这种方式仅是举例说明,事实上,还有其他方式可以保证所述升级设备停止所述一个或者多个目标业务组中部署在所述至少一个目标主机的所有虚拟机运行的业务,并维持所述一个或者多个目标业务组中未部署在所述至少一个目标主机的虚拟机运行的业务。例如,所述升级设备可以向所述一个或者多个目标业务组中部署在所述至少一个目标主机的所有虚拟机发送停止指令,向所述一个或者多个目标业务组中未部署在所述至少一个目标主机的所有虚拟机发送运行指令,本申请并不限定,凡是可以停止所述一个或者多个目标业务组中部署在所述至少一个目标主机的所有虚拟机运行的业务以及维持所述一个或者多个目标业务组中未部署在所述至少一个目标主机的虚拟机运行的业务的方式均适用于本申请实施例。
作为一种可能的实施方式,对所述目标主机进行升级前,若所述目标主机上部署的虚拟机仍在运行对应的业务组的业务,则升级之前所述升级设备将所述一个或者多个目标业务组中部署在所述至少一个目标主机的所有虚拟机运行的业务迁移至所述一个或者多个目标业务组中未部署在所述至少一个目标主机的虚拟机。
所述升级设备可以将所述至少一个目标主机上部署的属于每个目标业务组的虚拟机运行的业务交付给除所述至少一个目标主机外的其他主机上的虚拟机;如可以交付给所述多个主机中除所述至少一个目标主机外的其他主机上部署的属于对应的所述目标业务组的虚拟机。
示例性的,所述升级设备可以将所述至少一个目标主机中每个业务组的虚拟机的业务 数据迁移至所述目标业务组中的其他虚拟机;也可以通知其他管理设备将所述至少一个目标主机中每个业务组的虚拟机的业务数据迁移至所述目标业务组中的其他虚拟机;这样可以保证所述目标主机上每个所述目标业务组的虚拟机处理的业务不会中断,能够由每个所述目标业务组中的其他虚拟机继续进行处理;所述目标业务组中的其他虚拟机为所述多个主机中除所述至少一个目标主机之外的主机上部署的属于所述目标业务组中的虚拟机。
所述升级设备对所述至少一个目标主机执行升级前,还可以将所述至少一个目标主机加入升级组,接收所述升级组修正指令。接收到所述升级组修正指令后,所述升级设备根据所述升级组修正指令修正所述升级组包含的主机。
对于所述升级组中的主机,由于一些预设的规则,导致所述升级组中的一个或多个主机不能升级,此时所述升级设备会接收到所述升级组修正指令,用于对所述升级组包含的主机进行调整,例如,由于业务需求,所述升级组中的一个主机还承载有其他业务,不能中断其他业务,在这种情况下,所述升级组修正指令指示所述升级设备将该主机从所述升级组中删除;又例如,所述升级组中存在不能同时升级的两个主机,在这种情况下,所述升级组修正指令指示所述升级设备将该两个主机中的一个主机从所述升级组中删除。
步骤303:所述升级设备升级所述至少一个目标主机。
将所述目标主机的工作状态更改为维护态,之后关闭所述目标主机上部署的虚拟机,所述升级设备直接或者间接的发出指令,触发所述目标主机进行重启升级。在重启升级过程中,所述目标主机加载升级文件,替换本地保存的相关文件,之后所述目标主机升级完成,启动所述目标主机上部署的所有虚拟机,取消所述目标主机的维护态。至此,所述目标主机的升级操作完成。
通过上述方法,在对所述多个主机升级时,有选择的从多个主机中选择所述至少一个目标主机进行升级,针对选中的所述至少一个目标主机,不需要迁移其上虚拟机,即可在保证所述至少一个目标主机上部署的虚拟机业务的不中断的情况下,对至少一个目标主机进行升级,有效提高了主机升级的效率。
在实际应用中,存在多个主机,其中,每个主机上可以均部署有虚拟机,在对主机进行升级时,可以采用分组升级的方式,也就是说,将需要升级的主机分为多个升级组,每个升级组包括一个或多个主机;在确定了各个所述升级组之后,依次对各升级组中的主机执行升级操作。具体地,采用如图3所述的方法,在主机集群中选取至少一个目标主机加入第一升级组,后在主机集群中不属于第一升级组的主机中选取至少一个目标主机加入第二升级组,直到将主机集群中的主机分入不同的升级组后,依次对第一个升级组、第二个升级组、……第N个升级组中的主机进行升级。如图3中所述方法,对每个升级组的至少一个目标主机升级还包括所述一个或者多个目标业务组中部署在所述至少一个目标主机的所有虚拟机运行的业务,维持所述一个或者多个目标业务组中未部署在所述至少一个目标主机的虚拟机运行的业务。
图6为本申请实施例提供的一种主机升级方法的示意图,如图6所示的方法用于多个主机。本实施例和步骤301-步骤303所揭示的实施例相比,区别包括:业务组具体限定为为反亲和性组。同一个业务组的多个虚拟机既可以位于相同主机,也可以位于不同主机;而同一个反亲和性组的多个虚拟机不位于相同主机。
每个主机上部署有一个或多个虚拟机,多个主机上的多个虚拟机属于多个反亲和性 组,每个反亲和性组中的虚拟机处理一个业务,不同反亲和性组中的虚拟机处理的业务不同,所述反亲和性组中的多个虚拟机部署在不同的主机上,其中,反亲和性组对应的最大关机数为保持所述反亲和性组的业务运行时,所述反亲和性组中允许关机的虚拟机的最大数量,该方法包括:
步骤601:所述升级设备在多个主机中选取第一主机,所述第一主机所拥有的虚拟机中:每个所述反亲和性组的虚拟机总数均不大于对应的所述反亲和性组对应的最大关机数。在选中第一主机后,可以认为第一主机被加入了升级组,升级组中的主机在后续步骤中会被升级。
所述升级设备在选取第一主机之前,需要先获取所述多个主机的信息,所述多个主机的信息可以包括下列信息的部分或全部:
所述多个主机的设备信息(如所述各个主机的标识等)、每个主机上部署的虚拟机的信息(如每个主机部署的虚拟机的数量、虚拟机的标识、虚拟机所属的反亲和性组的信息等)、每个所述反亲和性组的信息(如每个所述反亲和性组中虚拟机的标识、每个所述反亲和性组的标识、每个所述反亲和性组所执行的业务或业务的代号等,在一些情况下,所述业务组的信息还可以包括每个所述业务组的标识)。
所述多个主机的信息可以预先存储在主机管理设备的中的所述升级设备中,也可以存储在所述主机管理设备上,在所述多个主机的信息存储在所述主机管理设备的情况下,所述升级设备需要从所述主机管理设备获取所述多个主机的信息。
选取的所述第一主机需要满足如下条件:
条件一、所述第一主机上部署的所有虚拟机属于所述多个反亲和性组中的一个或者多个目标反亲和性组。
为了方便后文的描述,把所述第一主机上部署的所有虚拟机所属的业务组称为目标反亲和性组。相当于按照业务的不同,把第一主机上的虚拟机分成不同的业务组。所述第一主机上部署的任一虚拟机均应该属于所述多个反亲和性组中的一个目标反亲和性组,所述第一主机上部署的所有虚拟机可以属于所述多个反亲和性组中的同一个目标反亲和性组,也可以属于所述多个反亲和性组中的不同目标反亲和性组,业务的数量决定了业务组的数量。本申请实施例并不限定目标反亲和性组的个数,可以是多个也可以是一个。
条件二、所述第一主机上部署的所有虚拟机中属于每个所述目标反亲和性组的虚拟机总数均不大于对应的所述目标反亲和性组对应的最大关机数。
为了所述目标反亲和性组的业务可以正常运行,应当保证所述第一主机上部署的属于每个所述目标反亲和性组的虚拟机的总数小于或等于对应的所述目标反亲和性组对应的最大关机数。
本申请实施例中,反亲和性组对应的最大关机数为保持反亲和性组的业务运行时,反亲和性组中允许关机的虚拟机的最大数量,对应地,目标反亲和性组对应的最大关机数为保持目标反亲和性组的业务运行时,目标反亲和性组中允许关机的虚拟机的最大数量。保证所述第一主机上部署的每个所述目标反亲和性组的虚拟机的总数小于或等于对应的所述目标反亲和性组对应的最大关机数,即可保证关闭所述第一主机以对其升级时,位于所述第一主机之外的虚拟机仍然可以在一定程度上支持业务的运行,关闭所述第一主机上的虚拟机不会影响所述一个或多个目标反亲和性组的业务。或者,即使对业务有一定影响,但影响是可以接受的,没有对业务的处理造成严重影响。也就是说,针对选中的所述第一 主机,不需要迁移其上虚拟机,即可在保证所述第一主机上部署的虚拟机业务的不中断的情况下,对第一主机进行升级,有效提高了主机升级的效率。
反亲和性组是包含的虚拟机具有相同的反亲和性的业务组。在所述多个反亲和性组中选择所述至少一个目标反亲和性组的方法可参照前述实施例中在多个业务组中选择所述至少一个目标业务组的方法,在此不再赘述。关于最大关机数的介绍,同样可以参考步骤301的介绍。
步骤602:所述升级设备选取了所述第一主机之后,在所述多个主机中选取第二主机,将所述第二主机和所述第一主机加入所述升级组,其中,所述第二主机上部署的所有虚拟机不属于任一所述目标反亲和性组。
本申请实施例并不限定所述第二主机的数量,所述升级设备可以确定一个所述第二主机,也可以确定多个所述第二主机;其上部署的虚拟机不属于任一所述目标反亲和性组的主机均可以作为所述第二主机。
所述升级设备可以对所述多个主机中除所述第一主机外的主机进行遍历,依次确定各个主机上部署的虚拟机是否属于任一所述目标反亲和性组,若不属于,则确定为所述第二主机。
本申请实施例并不限定所述第二主机的数量,凡是满足其上部署的虚拟机不属于任一所述目标反亲和性组的主机均可以作为第二主机。
所述升级设备在确定了所述第一主机和所述第二主机后,可以将所述第一主机和所述第二主机加入到一个升级组,执行步骤603。
步骤603:所述升级设备停止所述一个或者多个目标反亲和性组中部署在所述升级组中的主机的所有虚拟机运行的业务,维持所述一个或者多个目标反亲和性组中未部署在所述升级组中的主机的虚拟机运行的业务。
通过上述方式,可以保证所述目标反亲和性组的业务能够正常运行,不会使所述目标反亲和性组需要运行的业务中断。
示例性的,由于在所述主机群组中各个主机上部署的虚拟机运行的业务通常是由任务调度组件分配并且下发的,所述任务调度组件可以向所述主机群组中各个主机下发由各个反亲和性组的业务数据,以使得所述主机群组中各个主机上部署的属于各个反亲和性组的虚拟机在接收到对应的所述反亲和性组的业务数据后,根据接收到的业务数据运行所述反亲和性组的业务。
所述反亲和性组的业务数据为运行所述反亲和性组的业务所需的数据,例如,可以是任务指令、用户数据等。
可选地,所述升级设备通知所述任务调度组件,以使所述任务调度组件停止所述一个或者多个目标反亲和性组中部署在所述升级组中的主机的所有虚拟机运行的业务,维持所述一个或者多个目标反亲和性组中未部署在所述升级组中的主机的虚拟机运行的业务。
所述升级设备在选取了所述第一主机和所述第二主机后,由于所述第一主机上部署的每个所述目标反亲和性组的虚拟机均不大于对应的所述目标反亲和性组对应的最大关机数,也就是说,所述第一主机上部署的每个所述目标反亲和性组的虚拟机可以在不影响业务的情况下停止处理对应的所述目标反亲和性组的业务,而由在其他主机上部署的对应的所述目标反亲和性组的虚拟机处理所述目标反亲和性组的业务。
示例性的,所述升级设备可以向所述任务调度组件发送通知消息,所述通知消息指示所述任务调度组件停止向所述升级组中的主机上部署的属于每个所述目标反亲和性组的虚拟机下发对应的所述目标反亲和性组的业务数据。
在上述描述中,所述升级设备通过所述任务调度组件实现了停止所述一个或者多个目标反亲和性组中部署在所述升级组中的主机的所有虚拟机运行的业务,并维持了所述一个或者多个目标反亲和性组中未部署在所述升级组中的主机的虚拟机运行的业务。这种方式仅是举例说明,事实上,还有其他方式可以保证所述升级设备停止所述一个或者多个目标反亲和性组中部署在所述升级组中的主机的所有虚拟机运行的业务,并维持所述一个或者多个目标反亲和性组中未部署在所述升级组中的主机的虚拟机运行的业务。例如,所述升级设备可以向所述一个或者多个目标反亲和性组中部署在所述升级组中的主机的所有虚拟机发送停止指令,向所述一个或者多个目标反亲和性组中未部署在所述升级组中的主机的所有虚拟机发送运行指令,本申请并不限定,凡是可以停止所述一个或者多个目标反亲和性组中部署在所述升级组中的主机的所有虚拟机运行的业务以及维持所述一个或者多个目标反亲和性组中未部署在所述升级组中的主机的虚拟机运行的业务的方式均适用于本申请实施例。
作为一种可能的实施方式,对所述主机组中的主机进行升级前,若所述主机组中的主机上部署的虚拟机仍在运行对应的反亲和性组的业务,则升级之前所述升级设备将所述一个或者多个目标反亲和性组中部署在所述升级组中的主机的所有虚拟机运行的业务迁移至所述一个或者多个目标业务组中未部署在所述升级组中的主机的虚拟机。
对于每个所述目标反亲和性组而言,所述升级设备可以将所述升级组中的虚拟机运行的业务交付给除所述升级组的主机外的其他主机上部署的虚拟机;例如:可以交付给所述目标反亲和性组所以涉及的多个主机中,除所述升级组的主机外的主机上所部署的、属于对应的所述目标反亲和性组的虚拟机。
示例性的,所述升级设备可以将所述升级组中主机上部署的每个所述目标反亲和性组的虚拟机的业务数据迁移至所述目标反亲和性组中的其他虚拟机;也可以通知其他管理设备将所述升级组中主机上部署的属于每个所述目标反亲和性组的虚拟机上用业务数据迁移至对应的所述目标反亲和性组中的其他虚拟机;这样可以保证所述第一主机上所述目标反亲和性组的虚拟机处理的业务不会中断,能够由所述目标反亲和性组中的其他虚拟机继续进行处理;所述目标反亲和性组中的其他虚拟机为所述多个主机中除所述升级组的主机之外的主机上部署的属于所述目标反亲和性组中的虚拟机。
所述升级设备对所述升级组中的主机执行升级前,所述升级设备还可以接收所述升级组修正指令;接收到所述升级组修正指令后,所述升级设备根据所述升级组修正指令修正所述升级组包含的主机。
对于所述升级组中的主机,由于一些预设的规则,导致所述第一主机或第二主机不能升级,此时所述升级设备会接收到所述升级组修正指令,用于对所述升级组包含的主机进行调整。例如,由于业务需求,所述升级组中的一个主机还承载有其他业务,不能中断其他业务,在这种情况下,所述升级组修正指令指示所述升级设备将该主机从所述升级组中删除;又例如,所述升级组中存在不能同时升级的两个主机,在这种情况下,所述升级组修正指令指示所述升级设备将该两个主机中的一个主机从所述升级组中删除。
示例性的,所述升级设备可以将所述升级组的信息发送给其他管理设备,所述升级组 的信息用于表征所述升级组中的主机,由其他管理设备根据所述升级组的信息确定所述升级组修正指令,之后所述其他管理设备将所述升级组修正指令发送给所述升级设备,所述升级设备根据所述升级组修正指令所述升级组包含的主机。
步骤604:所述升级设备指令升级所述升级组中的主机。
关于升级主机的方法可以参见步骤303的相关描述,此处不再赘述。
通过上述方法,在对所述多个主机升级时,有选择的从多个主机中选择所述第一主机和所述第二主机组成升级组,针对选中的所述升级组中的主机,不需要迁移其上虚拟机,即可在保证所述升级组中的主机上部署的虚拟机业务的不中断的情况下,对所述升级组中的主机进行升级,有效提高了主机升级的效率。
在实际应用中,存在多个主机,其中,每个主机上可以均部署有虚拟机,在对主机进行升级时,可以采用分组升级的方式,也就是说,将需要升级的主机分为多个升级组,每个升级组包括一个或多个主机;在确定了各个所述升级组之后,依次对各升级组中的主机执行升级操作。具体地,采用如图6所示的方法,在主机集群中选取第一主机和第二主机加入第一升级组,后在主机集群中不属于第一升级组的主机中选取第一主机和第二主机加入第二升级组,直到将主机集群中的主机分入不同的升级组后,依次对第一个升级组、第二个升级组、……第N个升级组中的主机进行升级。如图6中所示方法,对每个升级组中的主机升级还包括所述一个或者多个目标反亲和性组中部署在该升级组中主机上的所有虚拟机运行的业务,维持所述一个或者多个目标业务组中未部署在该升级组中主机上的虚拟机运行的业务。
基于与如图3所示的方法实施例同一发明构思,本申请实施例还提供了一种升级设备,用于执行上述如图3所示的方法实施例中所述升级设备执行的方法,相关特征可参见上述方法实施例,此处不再赘述,如图7所示,所述升级设备700包括选择单元701、处理单元702和升级单元703:
所述升级设备700用于管理多个主机升级,所述多个主机的任一主机可部署有虚拟机,多个所述主机上部署的所有虚拟机属于多个业务组,每个业务组处理一个业务,不同业务组处理的业务不同,每一个业务组对应一个最大关机数,业务组对应的最大关机数为保持该业务组的业务运行时,该业务组中允许关机的虚拟机的最大数量。
其中,所述选择单元701,用于在多个所述主机中选取至少一个目标主机,所述至少一个目标主机上部署的所有虚拟机属于所述多个业务组中的一个或者多个目标业务组.
所述处理单元702,用于停止所述一个或者多个目标业务组中部署在所述至少一个目标主机的所有虚拟机运行的业务,维持所述一个或者多个目标业务组中未部署在所述至少一个目标主机的虚拟机运行的业务。
所述升级单元703,用于指示升级所述至少一个目标主机升级。
作为一种可能的实施方式,所述处理单元702在所述升级设备升级所述至少一个目标主机之前,还可以将所述一个或者多个目标业务组中部署在所述至少一个目标主机的所有虚拟机迁移至所述一个或者多个目标业务组中未部署在所述至少一个目标主机的虚拟机,也就是说,将所述至少一个目标主机上部署的虚拟机的业务交付给其他主机上的虚拟机,以使其他主机上的虚拟机继续处理所述至少一个目标主机的虚拟机的业务。
所述业务组的最大关机数的设置方式有许多,所述业务组的最大关机数可以是预先配置好的,也可以其他方式,下面对其中一种进行说明:
所述选择单元701先获取负载均衡参数,所述负载均衡参数表示所述业务组的业务保持运行时,所述业务组中允许关机的虚拟机的数量占所述业务组包含的虚拟机总数的比例;之后,所述选择单元701根据所述负载均衡参数和所述业务组包含的虚拟机的总数,计算所述业务组的最大关机数。
所述处理单元702在所述升级单元703升级所述至少一个目标主机之前,还可以将所述至少一个目标主机加入升级组;若接收到所述升级组修正指令,所述处理单元702根据所述升级组修正指令修正所述升级组包含的主机,如删除所述升级组的一个或多个主机。
基于与如图6所示的方法实施例同一发明构思,本申请实施例还提供了一种升级设备,用于执行上述如图6方法实施例中所述升级设备执行的方法,相关特征可参见上述方法实施例,此处不再赘述,如图8所示,所述升级设备800包括选择单元801、处理单元802和升级单元803:
所述升级设备800用于管理多个主机升级,所述多个主机上部署有虚拟机,多个主机上部署的所有虚拟机属于多个反亲和性组,每个反亲和性组处理一个业务,不同反亲和性组处理的业务不同,一个反亲和性组中的多个虚拟机部署在所述多个主机中的不同主机上,其中,反亲和性组的最大关机数为保持所述反亲和性组的业务运行时,该反亲和性组中允许关机的虚拟机的最大数量。
其中,所述选择单元801,用于选取在所述多个主机中选取第一主机和第二主机。
在所述第一主机上部署的所有虚拟机属于所述多个反亲和性组中的一个或者多个目标反亲和性组,其中,在所述第一主机上部署的所有虚拟机中,属于每个所述目标反亲和性组的虚拟机总数均不大于对应的所述目标反亲和性组对应的最大关机数;所述第二主机上部署的所有虚拟机不属于任一所述目标反亲和性组。
所述处理单元802,用于停止所述一个或者多个目标反亲和性组中部署在所述升级组中的主机的所有虚拟机运行的业务,维持所述一个或者多个目标反亲和性组中未部署在所述升级组中的主机的虚拟机运行的业务。
所述升级单元803,用于指示所述升级组中的主机升级。
所述处理单元802在所述升级单元803升级所述升级组中的主机之前,还可以将所述一个或者多个目标反亲和性组中部署在所述升级组中的主机的所有虚拟机迁移至所述一个或者多个目标业务组中未部署在所述升级组中的主机的虚拟机;也就是说,将所述升级组中主机部署的虚拟机的业务交付给其他主机上的虚拟机,以使其他主机上的虚拟机继续处理所述升级组中主机部署的虚拟机的业务。
所述业务组的最大关机数的设置方式有许多,所述业务组的最大关机数可以是预先配置好的,也可以其他方式,下面对其中一种进行说明:
所述选择单元801先获取负载均衡参数,所述负载均衡参数表示所述反亲和性组的业务保持运行时,所述目标反亲和性组中允许关机的虚拟机的数量占所述反亲和性组包含的虚拟机总数的比例;之后,所述选择单元801还根据所述负载均衡参数和所述反亲和性组包含的虚拟机的总数,计算所述反亲和性组的最大关机数。
所述处理单元802在所述升级单元803升级所述升级组中的主机之前,还可以接收所述升级组修正指令;之后,根据所述升级组修正指令修正所述升级组包含的主机,如删除所述升级组的一个或多个主机。
本申请实施例中对单元的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可 以有另外的划分方式,另外,在本申请各个实施例中的各功能单元可以集成在一个处理器中,也可以是单独物理存在,也可以两个或两个以上单元集成在一个模块中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。
该集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台终端设备(可以是个人计算机,手机,或者网络设备等)或处理器(processor)执行本申请各个实施例该方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(read-only memory,ROM)、随机存取存储器(random access memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
基于如图3所示的方法实施例,本申请实施例还提供了一种升级设备,所述升级设备用于实现如图3所示的主机升级方法,在一个简单的实施例中,所述升级设备可采用图8所示的形式。
如图9所示的升级设备900,包括至少一个处理器901、存储器902,可选的,还可以包括通信接口903。
存储器902可以是易失性存储器,例如随机存取存储器;存储器也可以是非易失性存储器,例如只读存储器,快闪存储器,硬盘(hard disk drive,HDD)或固态硬盘(solid-state drive,SSD)、或者存储器902是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质,但不限于此。存储器902可以是上述存储器的组合。
本申请实施例中不限定上述处理器901以及存储器902之间的具体连接介质。本申请实施例在图中以存储器902和处理器901之间通过总线904连接,总线904在图中以粗线表示,其它部件之间的连接方式,仅是进行示意性说明,并不引以为限。该总线904可以分为地址总线、数据总线、控制总线等。为便于表示,图9中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
处理器901可以具有数据收发功能,能够与其他管理设备进行通信,在如图9装置中,也可以设置独立的数据收发模块,例如通信接口903,用于收发数据;处理器901在与其他管理设备进行通信时,可以通过通信接口903进行数据传输。
当所述升级设备采用图9所示的形式时,图9中的处理器901可以通过调用存储器902中存储的程序,使得所述升级设备可以执行如图3所示方法实施例中的升级设备执行的方法。
具体的,图7中的选择单元、处理单元和升级单元的功能/实现过程均可以通过图9中的处理器901调用存储器902中存储的计算机执行指令来实现。
基于如图6所示的方法实施例,本申请实施例还提供了一种升级设备,所述升级设备用于实现如图6所示的主机升级方法,在一个简单的实施例中,所述升级设备可采用图10所示的形式。
如图10所示的升级设备1000,包括至少一个处理器1001、存储器1002,可选的,还可以包括通信接口1003。
存储器1002可以是易失性存储器,例如随机存取存储器;存储器也可以是非易失性 存储器,例如只读存储器,快闪存储器,硬盘(hard disk drive,HDD)或固态硬盘(solid-state drive,SSD)、或者存储器1002是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质,但不限于此。存储器1002可以是上述存储器的组合。
本申请实施例中不限定上述处理器1001以及存储器1002之间的具体连接介质。本申请实施例在图中以存储器1002和处理器1001之间通过总线1004连接,总线1004在图中以粗线表示,其它部件之间的连接方式,仅是进行示意性说明,并不引以为限。该总线1004可以分为地址总线、数据总线、控制总线等。为便于表示,图10中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
处理器1001可以具有数据收发功能,能够与其他管理设备进行通信,在如图10装置中,也可以设置独立的数据收发模块,例如通信接口1003,用于收发数据;处理器1001在与其他管理设备进行通信时,可以通过通信接口1003进行数据传输。
当所述升级设备采用图10所示的形式时,图10中的处理器1001可以通过调用存储器1002中存储的程序,使得所述升级设备可以执行如图6所示方法实施例中的升级设备执行的方法。
具体的,图8中的选择单元、处理单元和升级单元的功能/实现过程均可以通过图10中的处理器1001调用存储器1002中存储的计算机执行指令来实现。
本领域内的技术人员应明白,本申请的实施例可提供为方法、***、或计算机程序产品。因此,本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然,本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的精神和范围。这样,倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包含这些改动和变型在内。
Claims (18)
- 一种主机升级的方法,其特征在于,所述方法用于管理多个主机升级,所述主机上部署有虚拟机,多个所述主机上的多个虚拟机属于多个业务组,每个所述业务组处理一个业务,不同所述业务组处理的业务不同,相同业务组处理的业务相同,其中,所述业务组对应的最大关机数为保持所述业务组的业务运行时,所述业务组中允许关机的虚拟机的最大数量;所述方法包括:在多个所述主机中选取至少一个目标主机,所述至少一个目标主机上部署的所有虚拟机属于所述多个业务组中的一个或者多个目标业务组,其中,所述至少一个目标主机上部署的所有虚拟机中,属于每个所述目标业务组的虚拟机总数均不大于对应的所述目标业务组对应的最大关机数;停止所述一个或者多个目标业务组中部署在所述至少一个目标主机的所有虚拟机运行的业务,维持所述一个或者多个目标业务组中未部署在所述至少一个目标主机的虚拟机运行的业务;升级所述至少一个目标主机。
- 根据权利要求1中所述的方法,其特征在于,所述升级所述至少一个目标主机之前,所述方法还包括:所述一个或者多个目标业务组中部署在所述至少一个目标主机的所有虚拟机上运行的业务迁移至所述一个或者多个目标业务组中未部署在所述至少一个目标主机的虚拟机。
- 根据权利要求1-2中所述的任一方法,其特征在于,在选取至少一个目标主机之前,所述方法还包括:获取负载均衡参数,所述负载均衡参数表示所述业务组的业务保持运行时,所述业务组中允许关机的虚拟机的数量占所述业务组包含的虚拟机总数的比例;根据所述负载均衡参数和所述业务组包含的虚拟机的总数,计算所述业务组的最大关机数。
- 根据权利要求1-3中所述的任一方法,其特征在于,所述升级所述至少一个目标主机之前,所述方法还包括:将所述至少一个目标主机加入升级组;接收针对所述升级组的修正指令;根据所述修正指令修正所述升级组包含的主机。
- 一种主机升级的方法,其特征在于,所述方法用于管理多个主机升级,所述主机上部署有虚拟机,多个所述主机上的多个虚拟机属于为多个反亲和性组,每个所述反亲和性组处理一个业务,不同所述反亲和性组处理的业务不同,所述反亲和性组中的不同虚拟机部署在不同的所述主机上,其中,所述反亲和性组对应的最大关机数为保持所述反亲和性组的业务运行时,所述反亲和性组中允许关机的虚拟机的最大数量;所述方法包括:在所述多个主机中选取第一主机,在所述第一主机上部署的所有虚拟机属于所述多个反亲和性组中的一个或者多个目标反亲和性组,其中,在所述第一主机上部署的所有虚拟机中,属于每个所述目标反亲和性组的虚拟机总数均不大于对应的所述目标反亲和性组对应的最大关机数;在所述多个主机中选取第二主机,将所述第二主机和所述第一主机加入升级组,其中, 所述第二主机上部署的所有虚拟机不属于任一所述目标反亲和性组;停止所述一个或者多个目标反亲和性组中部署在所述升级组中的主机的所有虚拟机运行的业务,维持所述一个或者多个目标反亲和性组中未部署在所述升级组中的主机的虚拟机运行的业务;升级所述升级组中的主机。
- 根据权利要求5中所述的方法,其特征在于,所述升级所述升级组中的主机之前,所述方法还包括:所述一个或者多个目标反亲和性组中部署在所述升级组中的主机的所有虚拟机上运行的业务迁移至所述一个或者多个目标业务组中未部署在所述升级组中的主机的虚拟机。
- 根据权利要求5-6中任一所述的方法,其特征在于,所述在所述多个主机中选取第一主机之前,还包括:获取负载均衡参数,所述负载均衡参数表示所述反亲和新组的业务保持运行时,所述反亲和性组中允许关机的虚拟机的数量占所述反亲和性组包含的虚拟机总数的比例;根据所述负载均衡参数和所述反亲和性业务组包含的虚拟机的总数,计算所述反亲和性组的最大关机数。
- 根据权利要求5-7中所述的任一方法,其特征在于,所述升级所述升级组中的主机之前,所述方法还包括:接收针对所述升级组的修正指令;根据所述修正指令修正所述升级组包含的主机。
- 一种升级设备,其特征在于,所述升级设备用于管理多个主机升级,所述主机上部署有虚拟机,多个所述主机上的多个虚拟机属于多个业务组,每个所述业务组处理一个业务,不同所述业务组处理的业务不同,相同业务组处理的业务相同,其中,所述业务组对应的最大关机数为保持所述业务组的业务运行时,所述业务组中允许关机的虚拟机的最大数量;所述设备包括选择单元、处理单元和升级单元;所述选择单元,用于在多个所述主机中选取至少一个目标主机,所述至少一个目标主机上部署的所有虚拟机属于所述多个业务组中的一个或者多个目标业务组,其中,所述至少一个目标主机上部署的所有虚拟机中属于每个所述目标业务组的虚拟机总数不大于对应的所述目标业务组对应的最大关机数;所述处理单元,用于停止所述一个或者多个目标业务组中部署在所述至少一个目标主机的所有虚拟机运行的业务,维持所述一个或者多个目标业务组中未部署在所述至少一个目标主机的虚拟机运行的业务;所述升级单元,用于指示所述至少一个目标主机升级。
- 根据权利要求9中所述的设备,其特征在于,所述处理单元在所述升级单元升级所述至少一个目标主机之前,还用于:将所述一个或者多个目标业务组中部署在所述至少一个目标主机的所有虚拟机上运行的业务迁移至所述一个或者多个目标业务组中未部署在所述至少一个目标主机的虚拟机。
- 根据权利要求9或10中所述设备,其特征在于,所述选择单元在选取至少一个目标主机之前,还用于:获取负载均衡参数,所述负载均衡参数表示所述业务组的业务保持运行时,所述业务 组中允许关机的虚拟机的数量占所述业务组包含的虚拟机总数的比例;根据所述负载均衡参数和所述业务组包含的虚拟机的总数,计算所述业务组的最大关机数。
- 根据权利要求9-11中所述的任一设备,其特征在于,所述处理单元在所述升级单元升级所述升级组中的主机之前,还用于:将所述至少一个目标主机加入升级组;接收针对所述升级组的修正指令;根据所述修正指令修正所述升级组包含的主机。
- 一种升级设备,其特征在于,所述升级设备用于管理多个主机升级,所述主机上部署有虚拟机,多个所述主机上的多个虚拟机属于多个反亲和性组,每个所述反亲和性组处理一个业务,不同所述反亲和性组处理的业务不同,所述反亲和性组中的不同虚拟机部署在不同的所述主机上,其中,所述反亲和性组对应的最大关机数为保持所述反亲和性组的业务运行时,所述反亲和性组中允许关机的虚拟机的最大数量,所述设备包括选择单元、处理单元和升级单元:所述选择单元,用于在所述多个主机中选取第一主机;以及在所述多个主机中选取第二主机,将所述第二主机和所述第一主机加入升级组,其中,在所述第一主机上部署的所有虚拟机属于所述多个反亲和性组中的一个或者多个目标反亲和性组,所述第一主机上部署的所有虚拟机中属于每个所述目标反亲和性组的虚拟机总数不大于对应的所述目标反亲和性组对应的最大关机数,所述第二主机上部署的所有虚拟机不属于任一所述目标反亲和性组;所述处理单元,用于停止所述一个或者多个目标反亲和性组中部署在所述升级组中的主机的所有虚拟机运行的业务,维持所述一个或者多个目标反亲和性组中未部署在所述升级组中的主机的虚拟机运行的业务;所述升级单元,用于指示所述升级组中的主机升级。
- 根据权利要求13中所述的设备,其特征在于,所述处理单元在所述升级单元升级所述升级组中的主机之前,还用于:将所述一个或者多个目标反亲和性组中部署在所述升级组中的主机的所有虚拟机上运行的业务迁移至所述一个或者多个目标业务组中未部署在所述升级组中的主机的虚拟机。
- 根据权利要求13或14中所述的设备,其特征在于,所述选择单元在所述多个主机中选取第一主机之前,还用于:获取负载均衡参数,所述负载均衡参数表示所述反亲和新组的业务保持运行时,所述反亲和性组中允许关机的虚拟机的数量占所述反亲和性组包含的虚拟机总数的比例;根据所述负载均衡参数和所述反亲和性业务组包含的虚拟机的总数,计算所述反亲和性组的最大关机数。
- 根据权利要求13-15中所述的任一设备,其特征在于,所述处理单元在所述升级单元升级所述升级组中的主机之前,还用于:接收所述升级组修正指令;根据所述升级组修正指令修正所述升级组包含的主机。
- 一种升级设备,其特征在于,所述升级设备包括处理器和存储器,所述处理器执 行所述存储器中的程序指令,以实现权利要求1-4中任一所述的方法。
- 一种升级设备,其特征在于,所述升级设备包括处理器和存储器,所述处理器执行所述存储器中的程序指令,以实现权利要求5-8中任一所述的方法。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2018/108408 WO2020062057A1 (zh) | 2018-09-28 | 2018-09-28 | 一种主机升级方法及设备 |
CN201880066630.5A CN111213343B (zh) | 2018-09-28 | 2018-09-28 | 一种主机升级方法及设备 |
US17/213,719 US11886905B2 (en) | 2018-09-28 | 2021-03-26 | Host upgrade method and device |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2018/108408 WO2020062057A1 (zh) | 2018-09-28 | 2018-09-28 | 一种主机升级方法及设备 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/213,719 Continuation US11886905B2 (en) | 2018-09-28 | 2021-03-26 | Host upgrade method and device |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020062057A1 true WO2020062057A1 (zh) | 2020-04-02 |
Family
ID=69949552
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/108408 WO2020062057A1 (zh) | 2018-09-28 | 2018-09-28 | 一种主机升级方法及设备 |
Country Status (3)
Country | Link |
---|---|
US (1) | US11886905B2 (zh) |
CN (1) | CN111213343B (zh) |
WO (1) | WO2020062057A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2022156099A1 (zh) * | 2021-01-21 | 2022-07-28 | 中兴通讯股份有限公司 | 主机升级方法、装置、电子设备和存储介质 |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111796854B (zh) * | 2020-07-03 | 2023-03-31 | 中国建设银行股份有限公司 | 一种模块热升级的方法、装置、电子设备和可读存储介质 |
US11662994B1 (en) * | 2020-10-20 | 2023-05-30 | Metactix Llc | System and method for updating an application for a population of computers |
CN113050974B (zh) * | 2021-04-30 | 2024-02-20 | 中国工商银行股份有限公司 | 云计算基础设施在线升级方法及装置 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104484220A (zh) * | 2014-11-28 | 2015-04-01 | 杭州华为数字技术有限公司 | 虚拟化集群的动态资源调度的方法及装置 |
CN105471994A (zh) * | 2015-12-01 | 2016-04-06 | 华为技术有限公司 | 一种控制方法及装置 |
CN106301876A (zh) * | 2015-06-26 | 2017-01-04 | 中兴通讯股份有限公司 | 物理机升级方法、业务迁移方法及装置 |
CN108319492A (zh) * | 2017-01-18 | 2018-07-24 | 华为技术有限公司 | 复位物理机的方法、装置与*** |
US20180241617A1 (en) * | 2017-02-22 | 2018-08-23 | Microsoft Technology Licensing, Llc | System upgrade management in distributed computing systems |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9727440B2 (en) * | 2007-06-22 | 2017-08-08 | Red Hat, Inc. | Automatic simulation of virtual machine performance |
US10999147B2 (en) * | 2016-07-18 | 2021-05-04 | Telefonaktiebolaget Lm Ericsson (Publ) | Allocating VNFC instances with anti affinity rule to hosts |
CN106354531B (zh) * | 2016-08-25 | 2020-03-27 | 杭州华为数字技术有限公司 | 物理节点升级方法及装置 |
CN106648462B (zh) | 2016-11-21 | 2019-10-25 | 华为技术有限公司 | 数据存储方法及装置 |
CN110720091B (zh) * | 2017-06-09 | 2023-12-08 | 瑞典爱立信有限公司 | 用于与托管的应用/虚拟网络功能(vnf)协调基础设施升级的方法 |
US10860367B2 (en) * | 2018-03-14 | 2020-12-08 | Microsoft Technology Licensing, Llc | Opportunistic virtual machine migration |
-
2018
- 2018-09-28 CN CN201880066630.5A patent/CN111213343B/zh active Active
- 2018-09-28 WO PCT/CN2018/108408 patent/WO2020062057A1/zh active Application Filing
-
2021
- 2021-03-26 US US17/213,719 patent/US11886905B2/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104484220A (zh) * | 2014-11-28 | 2015-04-01 | 杭州华为数字技术有限公司 | 虚拟化集群的动态资源调度的方法及装置 |
CN106301876A (zh) * | 2015-06-26 | 2017-01-04 | 中兴通讯股份有限公司 | 物理机升级方法、业务迁移方法及装置 |
CN105471994A (zh) * | 2015-12-01 | 2016-04-06 | 华为技术有限公司 | 一种控制方法及装置 |
CN108319492A (zh) * | 2017-01-18 | 2018-07-24 | 华为技术有限公司 | 复位物理机的方法、装置与*** |
US20180241617A1 (en) * | 2017-02-22 | 2018-08-23 | Microsoft Technology Licensing, Llc | System upgrade management in distributed computing systems |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2022156099A1 (zh) * | 2021-01-21 | 2022-07-28 | 中兴通讯股份有限公司 | 主机升级方法、装置、电子设备和存储介质 |
Also Published As
Publication number | Publication date |
---|---|
US20210216353A1 (en) | 2021-07-15 |
CN111213343A (zh) | 2020-05-29 |
US11886905B2 (en) | 2024-01-30 |
CN111213343B (zh) | 2021-08-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020062057A1 (zh) | 一种主机升级方法及设备 | |
CN108664496B (zh) | 数据迁移方法及装置 | |
US9367340B2 (en) | Resource management method and apparatus for virtual machine system, and virtual machine system | |
US9563463B2 (en) | Computer system and control method therefor | |
US10572454B2 (en) | Storage method and apparatus for distributed file system | |
WO2020076512A1 (en) | Migrating control of a multi-path logical device from a current mpio driver to a target mpio driver | |
US10684878B1 (en) | Virtual machine management | |
US10158579B2 (en) | Resource silos at network-accessible services | |
CN108804465B (zh) | 一种分布式缓存数据库数据迁移的方法及*** | |
CN104461744A (zh) | 一种资源分配方法及装置 | |
CN105718280A (zh) | 一种加速虚拟机io的方法和管理平台 | |
CN102369688A (zh) | 资源动态调整方法和调度设备 | |
CN103634379A (zh) | 一种分布式存储空间的管理方法和分布式存储*** | |
CN112988065B (zh) | 数据迁移方法、装置、设备及存储介质 | |
US11249790B1 (en) | Scheduling usage of oversubscribed computing resources | |
JP2021026659A (ja) | ストレージシステム及びリソース割当て制御方法 | |
US9760454B2 (en) | High availability method and system for improving the utility of physical servers in cloud computing resource pool | |
US20230325082A1 (en) | Method for setting up and expanding storage capacity of cloud without disruption of cloud services and electronic device employing method | |
US11625263B2 (en) | Systems and methods for improved management of virtual machine clusters | |
CN112631994A (zh) | 数据迁移方法及*** | |
CN115033370B (zh) | 存储设备中闪存任务调度方法、装置、存储介质及设备 | |
CN106484310B (zh) | 一种存储阵列操作方法和装置 | |
Nguyen et al. | An improvement of resource allocation for migration process in cloud environment | |
CN111694635A (zh) | 一种服务质量控制方法及装置 | |
CN108153484B (zh) | 一种虚拟化环境下的共享式存储***及其管理方法 |
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: 18935873 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 18935873 Country of ref document: EP Kind code of ref document: A1 |