CN117472516B

CN117472516B - Virtual resource scheduling method, device, cluster system, electronic equipment and medium

Info

Publication number: CN117472516B
Application number: CN202311816266.9A
Authority: CN
Inventors: 孙昊良; 栗丽霞; 闫冬冬
Original assignee: Suzhou Metabrain Intelligent Technology Co Ltd
Current assignee: Suzhou Metabrain Intelligent Technology Co Ltd
Priority date: 2023-12-27
Filing date: 2023-12-27
Publication date: 2024-03-29
Anticipated expiration: 2043-12-27
Also published as: CN117472516A

Abstract

The application provides a virtual resource scheduling method, a device, a cluster system, electronic equipment and a medium, and relates to the technical field of computers, wherein the method comprises the following steps: determining a virtual entity to be scheduled; performing resource matching judgment on each host in the cluster system based on a common resource request of the virtual machine and the container to the hosts, and determining a first candidate host list corresponding to the virtual entity; determining a resource type corresponding to the virtual entity, and performing resource matching judgment on each host in the first candidate host list based on a dedicated resource request of the resource type on the host, so as to determine a second candidate host list corresponding to the virtual entity; and determining a target host corresponding to the virtual entity based on the virtual entity starting record of each host in the second candidate host list, and starting the virtual entity in the target host. The method and the device provided by the application realize unified scheduling of the virtual machines and the containers in the cluster system.

Description

Virtual resource scheduling method, device, cluster system, electronic equipment and medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a virtual resource scheduling method, device, cluster system, electronic device, and medium.

Background

The server virtualization technology is to fully utilize the hardware performance of the server by utilizing the virtualization technology. The virtualized system contains a plurality of physical resources including host resources, storage resources, network resources and the like. Virtual resources running in a virtualized system mainly include virtual machines and containers.

Virtual machines are typically scheduled using a virtual machine resource framework, while containers are scheduled using a container management platform (e.g., kubernetes, K8s for short). This results in two sets of scheduling systems for the same physical resource, and for two different virtual resources running on the same physical resource, which results in repeated computation for the physical resource, so that the physical resource cannot be uniformly scheduled, and physical resource conflicts are caused, thereby causing that the virtual machine or the container cannot run normally.

Therefore, how to uniformly schedule the virtual machine and the container, and avoiding physical resource conflict is a technical problem to be solved in the industry.

Disclosure of Invention

The application provides a virtual resource scheduling method, a device, a cluster system, electronic equipment and a medium, which are used for solving the technical problem of how to uniformly schedule virtual machines and containers and avoiding physical resource conflict.

The application provides a virtual resource scheduling method, which comprises the following steps:

determining a virtual entity to be scheduled; the resource type of the virtual entity comprises a virtual machine or a container;

performing resource matching judgment on each host in the cluster system based on a common resource request of the virtual machine and the container to the hosts, and determining a first candidate host list corresponding to the virtual entity;

determining a resource type corresponding to the virtual entity, and performing resource matching judgment on each host in the first candidate host list based on a dedicated resource request of the resource type on the host, so as to determine a second candidate host list corresponding to the virtual entity;

and determining a target host corresponding to the virtual entity based on the virtual entity opening record of each host in the second candidate host list, and opening the virtual entity in the target host.

In some embodiments, the determining the virtual entity to be scheduled includes:

receiving a virtual resource scheduling request;

determining a virtual entity corresponding to the virtual resource scheduling request;

adding the virtual entity to a task queue to be scheduled in the cluster system;

and inquiring the task queue to be scheduled based on a preset inquiring period, and determining the virtual entity positioned at the head position of the task queue to be scheduled as the virtual entity to be scheduled.

In some embodiments, before the receiving the virtual resource scheduling request, the method further comprises:

determining a container management platform running in the cluster system;

a container dispatch engine is disabled in the container management platform.

In some embodiments, the determining the virtual entity corresponding to the virtual resource scheduling request includes:

analyzing the virtual resource scheduling request and determining attribute information corresponding to the virtual resource scheduling request; the attribute information comprises at least one of an identifier, a name, a state, a type, a virtual disk list, a virtual network card list, host information and a security identifier of the virtual resource;

and creating a virtual entity corresponding to the virtual resource scheduling request based on the attribute information.

In some embodiments, the determining the first candidate host list corresponding to the virtual entity based on the resource matching judgment of each host in the cluster system by the common resource request of the virtual machine and the container to the hosts includes:

traversing the cluster system and determining a host list corresponding to the cluster system;

performing resource matching judgment on each host in the host list based on a common resource request of the virtual machine and the container to the hosts;

And adding any host to a first candidate host list corresponding to the virtual entity under the condition that the any host meets each resource request in the common resource requests.

In some embodiments, after the resource matching determination is made for each host in the host list based on the common resource request of the virtual machine and the container for the host, the method further comprises:

any host is determined to be a non-candidate host if the any host does not satisfy any of the common resource requests.

In some embodiments, the common resource request includes at least one of a host not having a processor binding turned on, a remaining memory capacity of the host meeting a memory capacity requirement of the virtual entity, a host not having a host binding turned on in the cluster system, a network card of the host meeting a network resource requirement of the virtual entity, and a security identification of the host being consistent with the security identification of the virtual entity.

In some embodiments, the determining the second candidate host list corresponding to the virtual entity based on the resource matching judgment of each host in the first candidate host list based on the dedicated resource request of the resource type to the host includes:

Under the condition that the resource type is a virtual machine, performing resource matching judgment on each host in the first candidate host list based on a dedicated resource request of the virtual machine on the host, and determining a second candidate host list corresponding to the virtual entity;

or if the resource type is a container, performing resource matching judgment on each host in the first candidate host list based on a request of the container for dedicated resources of the host, and determining a second candidate host list corresponding to the virtual entity.

In some embodiments, the virtual machine's dedicated resource request to the host includes:

in the case where a host uses bare device storage as a system disk, the bare device storage does not support host migration, and in the case where a host uses universal serial bus device, the universal serial bus device does not support host migration.

In some embodiments, the container's proprietary resource request to the host includes:

the container management platform running in the host is initialized and in an enabled state, and the utilization rate of the running catalog corresponding to the container is smaller than a preset utilization rate threshold.

In some embodiments, the determining, based on the virtual entity start record of each host in the second candidate host list, a target host corresponding to the virtual entity includes:

Traversing the virtual entity opening records of all hosts in the second candidate host list, and determining the failure times of opening the virtual entity of each host;

and under the condition that the failure times of any host to start the virtual entity is zero, determining the any host as a target host corresponding to the virtual entity.

In some embodiments, after determining the number of failures of each host to open the virtual entity, the method further includes:

under the condition that the failure times of starting the virtual entity of each host in the second candidate host list are not zero, determining the starting priority of each host based on the failure times of starting the virtual entity of each host; the opening priority and the failure times are in a negative correlation;

and determining the host corresponding to the highest starting priority as the target host corresponding to the virtual entity.

In some embodiments, after determining the opening priority of each host based on the number of failures of each host to open the virtual entity, the method further includes:

under the condition that the opening priority of each host is the same, acquiring the residual memory capacity of each host;

and determining the host corresponding to the highest residual memory capacity as the target host corresponding to the virtual entity.

In some embodiments, after the starting the virtual entity in the target host, the method further comprises:

determining an opening result of the virtual entity in the target host;

and under the condition that the starting result is successful, resetting the failure times of starting the virtual entity in the virtual entity starting record of the target host.

In some embodiments, after the determining the start result of the virtual entity in the target host, the method further includes:

and adding one operation to the failure times of opening the virtual entity in the virtual entity opening record of the target host under the condition that the opening result is failure.

In some embodiments, after the determining the first candidate host list corresponding to the virtual entity, the method further includes:

generating first scheduling failure information corresponding to the virtual entity under the condition that the first candidate host list is empty;

the first scheduling failure information comprises the resource type of the virtual entity and the resource matching judgment result of the common resource request to each host in the cluster system.

In some embodiments, after the determining the second candidate host list corresponding to the virtual entity, the method further includes:

Generating second scheduling failure information corresponding to the virtual entity under the condition that the second candidate host list is empty;

the second scheduling failure information includes a resource type of the virtual entity and a result of the dedicated resource request to determine a resource match of each host in the first candidate host list.

The application provides a virtual resource scheduling device, which comprises:

a determining unit, configured to determine a virtual entity to be scheduled; the resource type of the virtual entity comprises a virtual machine or a container;

the first detection unit is used for carrying out resource matching judgment on each host in the cluster system based on a common resource request of the virtual machine and the container to the hosts, and determining a first candidate host list corresponding to the virtual entity;

the second detection unit is used for determining the resource type corresponding to the virtual entity, carrying out resource matching judgment on each host in the first candidate host list based on the dedicated resource request of the resource type on the host, and determining a second candidate host list corresponding to the virtual entity;

the scheduling unit is used for determining a target host corresponding to the virtual entity based on the virtual entity opening record of each host in the second candidate host list, and opening the virtual entity in the target host.

The application provides a cluster system, which comprises the virtual resource scheduling device and a plurality of hosts;

the host is connected with the virtual resource scheduling device and is used for starting a virtual entity to be scheduled.

The application provides an electronic device, which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor realizes the virtual resource scheduling method when executing the program.

The present application provides a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the virtual resource scheduling method.

The virtual resource scheduling method, the device, the cluster system, the electronic equipment and the medium provided by the application determine the virtual entity to be scheduled; performing resource matching judgment on each host in the cluster system based on a common resource request of the virtual machine and the container to the hosts, and determining a first candidate host list corresponding to the virtual entity; determining a resource type corresponding to the virtual entity, and performing resource matching judgment on each host in the first candidate host list based on a dedicated resource request of the resource type on the host, so as to determine a second candidate host list corresponding to the virtual entity; determining a target host corresponding to the virtual entity based on the virtual entity opening records of all hosts in the second candidate host list, and opening the virtual entity in the target host; the method has the advantages that the common resource request and the dedicated resource request are adopted to carry out resource matching judgment on each host in the cluster system, candidate hosts are obtained by screening from each host in the cluster system, and the target hosts are determined according to the virtual entity opening records of the candidate hosts, so that unified scheduling of virtual machines and containers in the cluster system is realized, repeated calculation of host resources is avoided, host resource conflict during scheduling is avoided, and normal opening and operation of the virtual machines and containers in the cluster system are ensured.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

In order to more clearly illustrate the technical solutions of the present application or the prior art, the following description will briefly introduce the drawings used in the embodiments or the description of the prior art, and it is obvious that, in the following description, the drawings are some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic flow chart of a virtual resource scheduling method provided in the present application;

fig. 2 is a schematic structural diagram of a virtual resource scheduling device provided in the present application;

FIG. 3 is a schematic diagram of a cluster system provided herein;

FIG. 4 is a schematic diagram of a hybrid scheduling apparatus for virtual machines and containers provided herein;

FIG. 5 is a flow chart of a hybrid scheduling method for virtual machines and containers provided herein;

fig. 6 is a schematic structural diagram of an electronic device provided in the present application.

Detailed Description

In order to make the present application solution better understood by those skilled in the art, the following description will be made in detail and with reference to the accompanying drawings in the embodiments of the present application, it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.

It should be noted that the terms "first," "second," and the like herein are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that embodiments of the present application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Fig. 1 is a schematic flow chart of a virtual resource scheduling method provided in the present application, and as shown in fig. 1, the method includes steps 110, 120, 130, and 140.

Step 110, determining a virtual entity to be scheduled; the resource types of the virtual entities include virtual machines or containers.

Specifically, an application object of the virtual resource scheduling method provided by the embodiment of the application is a cluster system. A clustered system refers to a system in which multiple computers or servers are connected together through a network to achieve high performance, high availability, and scalability. They can work together and provide services to achieve higher computing power, storage power and reliability. Each computer or server in the system is referred to as a host or node.

The execution subject of the method provided by the embodiment of the application may be a virtual resource scheduling device. The apparatus may be implemented in software, for example a virtual resource scheduler running in a clustered system; the virtual resource scheduling method may also be a device, such as a mobile terminal, a tablet computer, a desktop computer, or a server.

In the embodiment of the application, the physical machine, the virtual machine and the container need to be distinguished. The physical machine refers to a real computer hardware device, and includes physical components such as a processor, a memory, a storage device, a network interface, and the like. The system is entity equipment which realizes the calculation and storage functions through hardware, and can independently run an operating system and application programs. A virtual machine is a logical computer environment created by virtualization technology that emulates a complete computer system on a physical machine, including processors, memory, storage, and network interfaces, among others. Each virtual machine may run its own operating system and application programs, just like a separate physical machine. The virtual machine technology enables a plurality of independent virtual machines to run on one physical machine at the same time, and each virtual machine can have an independent operating system and an application program which are mutually isolated. A container is also a virtualization technology that allows multiple applications or services to run on the same operating system, each packaged into a separate container. The container provides a lightweight, portable, and extensible way to package and deploy applications and services. In the embodiment of the application, the virtual resource refers to a virtual machine and a container running in a clustered system.

The virtual entity refers to an entity class corresponding to the virtual resource. Entity classes are used to represent a collection of objects with similar properties and behaviors. From a resource type perspective, a virtual entity may include a virtual machine and a container. For example, a virtual machine may be defined as a virtual entity that includes attributes (identity, name, status, etc.) and behaviors (create, open, run, etc.) of the virtual machine.

And 120, performing resource matching judgment on each host in the cluster system based on the common resource request of the virtual machine and the container to the hosts, and determining a first candidate host list corresponding to the virtual entity.

Specifically, in the embodiment of the present application, the host refers to a physical machine in a cluster system, such as a computer or a server. Resource request refers to the act of applying for use of a resource. In the embodiment of the present application, the resource request refers to a request of a running virtual machine or a container to a host resource, where the host resource may include a processor resource, a storage resource, a network resource, a device resource, and the like.

The common resource request refers to a common request for host resources by the virtual machine and the container while running in the host. The common request may be determined as a common resource request based on a request for host resources by the virtual machine when running in the host and a request for host resources by the container when running in the host.

The method can judge the matching of the resources provided by each host in the cluster system according to the common resource request, and determine whether each host can provide the host resources meeting the common resource request. If any host is capable of providing host resources meeting the common resource request, determining the host as a first candidate host and adding the first candidate host to a first candidate host list; if any host cannot provide host resources that satisfy the common resource request, the host is determined to be a non-first candidate host.

After resource matching judgment is carried out on all hosts in the cluster system, a first candidate host list can be obtained. The first candidate host list is a list of all first candidate hosts that satisfy the common resource request.

And 130, determining a resource type corresponding to the virtual entity, and performing resource matching judgment on each host in the first candidate host list based on a dedicated resource request of the resource type on the host, so as to determine a second candidate host list corresponding to the virtual entity.

Specifically, the dedicated resource request refers to a request of a virtual entity of different resource types for a host resource when running in the host, and can be determined according to the requirements of the virtual entity of different resource types for the host resource when running in the host. For example, because the virtual machine needs to simulate a complete hardware environment, more resources (especially memory) are occupied, and the container can share the kernel and other resources of the host. The two types of virtual entities are different in their requests for host resources.

The resource type corresponding to the virtual entity can be determined first, and the dedicated resource request corresponding to the resource type can be obtained. And then, evaluating and judging the resources which can be provided by each host in the first candidate host list according to the exclusive resource request, and determining whether each host can provide host resources which meet the exclusive resource request.

If any host in the first candidate host list can provide host resources meeting the exclusive resource request, determining the host as a second candidate host, and adding the second candidate host to the second candidate host list; if any host cannot provide host resources that satisfy the dedicated resource request, the host is determined to be a non-second candidate host.

After resource matching judgment is carried out on all the first candidate hosts in the first candidate host list, a second candidate host list can be obtained. The second candidate host list is a list of all second candidate hosts that fulfill the dedicated resource request.

And 140, determining a target host corresponding to the virtual entity based on the virtual entity opening record of each host in the second candidate host list, and opening the virtual entity in the target host.

Specifically, the virtual entity opening record refers to a history of opening the virtual entity in the host. For example, the virtual entity activation record may include information such as the number of failures to activate the virtual entity, the number of successes to activate the virtual entity, and the type of resources to activate the virtual entity.

The target host refers to a host that is scheduled to turn on and run the virtual entity to be scheduled. If the second candidate host list is empty, the fact that hosts meeting the resource request and capable of running the virtual entity to be scheduled do not exist in the cluster system is indicated. If only one host is available in the second candidate host list, the host can be directly determined as the target host corresponding to the virtual entity.

In the case that the second candidate host list includes a plurality of available hosts, a virtual entity opening record of each host may be obtained, and a target host corresponding to the virtual entity may be determined according to the records. For example, the number of failures of starting the virtual entity in the virtual entity starting record of each host may be compared, and the host with the minimum number of failures is determined as the target host corresponding to the virtual entity.

After the target host is determined, a virtual entity to be scheduled can be started and operated in the target host, so that the virtual entity is scheduled.

In a clustered system, virtual machines, containers, or both are allowed to run on individual hosts. Compared with the scheduling of the virtual machine through the virtual machine resource framework and the scheduling of the container through the container management platform, the virtual resource scheduling method provided by the embodiment of the application can uniformly manage the virtual machine and the container.

The virtual resource scheduling method provided by the embodiment of the application determines the virtual entity to be scheduled; performing resource matching judgment on each host in the cluster system based on a common resource request of the virtual machine and the container to the hosts, and determining a first candidate host list corresponding to the virtual entity; determining a resource type corresponding to the virtual entity, and performing resource matching judgment on each host in the first candidate host list based on a dedicated resource request of the resource type on the host, so as to determine a second candidate host list corresponding to the virtual entity; determining a target host corresponding to the virtual entity based on the virtual entity opening records of all hosts in the second candidate host list, and opening the virtual entity in the target host; the method has the advantages that the common resource request and the dedicated resource request are adopted to carry out resource matching judgment on each host in the cluster system, candidate hosts are obtained by screening from each host in the cluster system, and the target hosts are determined according to the virtual entity opening records of the candidate hosts, so that unified scheduling of virtual machines and containers in the cluster system is realized, repeated calculation of host resources is avoided, host resource conflict during scheduling is avoided, and normal opening and operation of the virtual machines and containers in the cluster system are ensured.

It should be noted that each embodiment of the present application may be freely combined, permuted, or executed separately, and does not need to rely on or rely on a fixed execution sequence.

In some embodiments, step 110 comprises:

receiving a virtual resource scheduling request;

inquiring the task queue to be scheduled based on a preset inquiring period, and determining the virtual entity positioned at the head position of the task queue to be scheduled as the virtual entity to be scheduled.

Specifically, a user may trigger the starting of a virtual machine or container in a clustered system. For example, a user may select a virtual machine or a container that needs to be opened in a creation interface in the cluster system, and the creation interface generates a virtual resource scheduling request in response to a selection or an input of the user in the creation interface, and sends the virtual resource scheduling request to the virtual resource scheduling device. The virtual resource scheduling request is used for requesting to schedule each host in the cluster system and determining a target host for starting and running the virtual entity.

The virtual resource scheduling device analyzes the received virtual resource scheduling request and determines a virtual entity corresponding to the virtual resource scheduling request according to the information in the virtual resource scheduling request. The virtual resource scheduling request may be used to request the start of a virtual entity or may be used to request the start of a group of virtual entities.

In the operation of a cluster system, a user is usually faced with the scenario of starting virtual entities (virtual machines or containers) in batches, and in this multi-task concurrency scenario, if the virtual machines or containers are not uniformly scheduled to control, host resource conflicts will necessarily occur in the virtual machines or containers.

The virtual resource scheduling means may create a task queue to be scheduled for managing the determined virtual entity. Each entry in the task queue to be scheduled corresponds to a virtual entity. The virtual resource scheduling device can add the virtual entity corresponding to the virtual resource scheduling request to the tail position of the task queue to be scheduled according to the receiving time of the virtual resource scheduling request.

The virtual resource scheduling device can query the task queue to be scheduled according to a preset query period, and each time, the virtual entity positioned at the head of the task queue to be scheduled is determined to be the virtual entity to be scheduled. The preset inquiry period can be set as required, for example, 2 seconds.

For the same host resource, the allocation can be uniformly scheduled, and the situation that the virtual machine and the container are in conflict or repeated allocation is avoided. For example, if the memory is not uniformly scheduled and concurrently controlled, when virtual machines or containers are opened in batches, host memory over-allocation occurs, failure in opening or degradation in host performance occurs to a certain extent, and some serious shortage of host resources and a large amount of host resources remain.

According to the virtual resource scheduling method, the virtual entity corresponding to the virtual resource scheduling request is managed through the task queue to be scheduled, the virtual entity to be scheduled can be orderly determined under the condition that the virtual entity is opened in batches in the cluster system, unified scheduling of the virtual machines and containers in the cluster system is achieved, repeated calculation of host resources is avoided, and host resource conflicts during scheduling are avoided.

In some embodiments, prior to receiving the virtual resource scheduling request, the method further comprises:

determining a container management platform running in a cluster system;

the container dispatch engine is disabled in the container management platform.

Specifically, a container management platform is operated in the cluster system. The container management platform is used for managing containerized applications on a plurality of hosts in the cluster system. For example, the container management platform may be a container orchestration engine such as K8s (Kubernetes) or K3s (lightweight Kubernetes). The container management platform typically configures a container scheduling engine and automatically schedules all containerized applications in the clustered system. If the container scheduling engine is allowed to automatically schedule the containers, the container scheduling engine and the virtual resource scheduling device generate conflict, and unified scheduling of the virtual machines and the containers in the cluster system cannot be realized.

Thus, the container scheduling engine may be disabled in the container management platform prior to receiving the virtual resource scheduling request, such that only the virtual resource scheduling device in the clustered system schedules the container.

According to the virtual resource scheduling method, the container scheduling engine is disabled in the container management platform, so that the conflict between the container scheduling engine and the virtual resource scheduling device is avoided, unified scheduling of the virtual machines and the containers in the cluster system is realized, repeated calculation of host resources is avoided, and the occurrence of host resource conflict during scheduling is avoided.

In some embodiments, determining a virtual entity corresponding to a virtual resource scheduling request includes:

Specifically, after receiving the virtual resource scheduling request, the virtual resource scheduling request may be parsed to extract attribute information. These attribute information are used to describe the scheduling characteristics of the virtual resources. For example, the virtual resource identifier, name, state, type, virtual disk list, virtual network card list, host information, security level identifier, etc. may be included.

The identification is used to uniquely identify the virtual resource. The name is the name of the virtual resource in the clustered system. The state is the state of the virtual resource in the cluster system, and can comprise creation, deletion, starting, stopping, running and the like. The type is the resource type of the virtual resource, including the virtual machine and the container. A virtual disk list refers to a list of disk image files used to store virtual machines or containers in a virtualized environment. The virtual network card list refers to a list of virtual network card devices used in a virtualized environment to connect a virtual machine or container to a network. The host information may include whether the virtual resource is bound to the host, the memory of the bound host, the processor of the bound host, the identity of the bound host, and the like. The security level identifier refers to a mark for classifying and marking data to define the security level and access authority of the data.

According to the attribute information, the virtual resource corresponding to the virtual resource scheduling request can be subjected to abstract representation, and a virtual entity corresponding to the virtual resource scheduling request is created.

According to the virtual resource scheduling method provided by the embodiment of the application, the virtual resource scheduling request is analyzed, the attribute information corresponding to the virtual resource scheduling request is determined, and the virtual entity is created according to the attribute information, so that the virtual entity can be accurately represented.

In some embodiments, step 120 comprises:

traversing a cluster system, and determining a host list corresponding to the cluster system;

and adding any host to the first candidate host list corresponding to the virtual entity under the condition that any host meets each resource request in the common resource requests.

Specifically, each host in the cluster system may be traversed to determine a host list corresponding to the cluster system. For example, the hosts may be traversed according to the order of the host identities of the hosts, the states of the hosts may be obtained, and the hosts with the available states may be added to the host list.

Common resource requests of the virtual machine and the container to the host are determined, and the common resource requests can comprise common requests of two different types of virtual resources to the host processor, memory, storage and the like.

And carrying out resource matching judgment on each host in the host list according to the common resource request, matching the resources which can be provided by each host with the resource requirements in the common resource request, and judging whether each host can provide the resources which meet the common resource request.

The common resource request may include a plurality of resource requests, such as a processor resource request, a memory resource request, a storage resource request, a network resource request, and the like. And matching various resources which can be provided by any host with each resource request in the common resource requests, if the host meets each resource request in the common resource requests, determining the host as a first candidate host, and adding the host to a first candidate host list corresponding to the virtual entity.

According to the virtual resource scheduling method provided by the embodiment of the application, resource matching judgment is carried out on each host in the host list according to the common resource request of the virtual machine and the container to the hosts, so that screening of each host in the cluster system is realized, unified calculation of host resources in the cluster system is realized, repeated calculation of the host resources is avoided, and host resource conflict during scheduling is avoided.

In some embodiments, after performing the resource matching determination on each host in the host list based on the common resource request of the virtual machine and the container to the host, the method further comprises:

in the event that any of the common resource requests is not satisfied by any of the hosts, any of the hosts is determined to be non-candidate hosts.

Specifically, for multiple resource requests in a common resource request, if any one of the hosts does not satisfy any of the resource requests, then that host may be considered incapable of providing the resources required by the virtual machine or container, and is determined to be a non-candidate host (here, a non-first candidate host).

According to the virtual resource scheduling method provided by the embodiment of the application, under the condition that any host does not meet any resource request in the common resource requests, the host is determined to not meet the common resource requests, unified calculation of host resources in the cluster system is realized, repeated calculation of the host resources is avoided, and host resource conflict during scheduling is avoided.

In some embodiments, the common resource request includes at least one of a host not having a processor binding turned on, a remaining memory capacity of the host meeting a memory capacity requirement of the virtual entity, a host not having a host binding turned on in the clustered system, a network card of the host meeting a network resource requirement of the virtual entity, and a security identification of the host being consistent with a security identification of the virtual entity.

In particular, the common resource request essentially provides constraints or filtering conditions that both the virtual machine and the container possess for the host, which both require execution by the schedule.

Host not opening processor bindings refers to a host that is not opening processor (Central Processing Unit, CPU) bindings as a candidate, thus allowing a virtual machine or container to run.

Memory generally refers to the physical hardware devices in a host that are used to temporarily store data and programs. Whereas storage generally refers to the physical hardware devices in a host that are used to preserve data for long periods of time.

The virtual entity needs a certain memory capacity when running, so the residual memory capacity of the host should meet the memory capacity requirement of the virtual entity, that is, the residual memory capacity of the host should be greater than or equal to the memory capacity requirement of the virtual entity.

The virtual entity generates certain data when running, and the host is required to provide storage capacity. Thus, the storage capacity provided by the host should meet the storage capacity requirements of the virtual entity.

In a virtualized environment, host binding generally refers to binding the MAC (Media Access Control Address) address and IP (Internet Protocol) address of a virtual machine with a host to ensure that the virtual machine has a unique identity in the network and is able to communicate normally.

The host is not started to bind in the cluster system, which means that the host is not bound with other virtual machines, and the virtual machines or containers are allowed to run.

The network card of the host meeting the network resource requirement of the virtual entity means that the network card of the host should provide enough bandwidth and speed to support the virtualization technology so as to meet the requirement of the virtual entity on network traffic.

The consistency of the security level identification of the host and the security level identification of the virtual entity means that the security level of the host is consistent with the security level of the virtual entity under the condition of security requirements, so that sensitive data can be effectively protected and managed, and data leakage and improper access are prevented.

According to the virtual resource scheduling method provided by the embodiment of the application, a plurality of common resource requests are determined from the resource requirements of the virtual machine and the container on the hosts, so that screening of each host in the cluster system is conveniently realized.

In some embodiments, step 130 comprises:

or under the condition that the resource type is a container, performing resource matching judgment on each host in the first candidate host list based on the exclusive resource request of the container on the host, and determining a second candidate host list corresponding to the virtual entity.

In particular, there are different proprietary resource requests for the host considering that virtual resources of different resource types are outside of the common resource request. The dedicated resource request is related to the resource type.

The resource type of the virtual entity may be determined first. If the resource type of the virtual entity is the virtual machine, the exclusive resource request of the virtual machine to the host can be obtained, the resource matching judgment is carried out on each host in the first candidate host list according to the exclusive resource request, the host meeting the exclusive resource request is taken as a second candidate host, and the second candidate host list is added; if any of the dedicated resource requests is not satisfied by any of the hosts, the host is determined to be a non-second candidate host.

If the resource type of the virtual entity is a container, acquiring an exclusive resource request of the container to the host, performing resource matching judgment on each host in the first candidate host list according to the exclusive resource request, taking the host meeting the exclusive resource request as a second candidate host, and adding the second candidate host list; if any of the dedicated resource requests is not satisfied by any of the hosts, the host is determined to be a non-second candidate host.

According to the virtual resource scheduling method, corresponding exclusive resource requests are determined according to the resource types, and resource matching judgment is carried out on each host in the first candidate host list, so that unified calculation of host resources in a cluster system is realized, repeated calculation of the host resources is avoided, and host resource conflict during scheduling is avoided.

In some embodiments, the request for dedicated resources of the virtual machine to the host includes:

in the case where the host uses bare device storage as a system disk, the bare device storage does not support host migration, and in the case where the host uses universal serial bus device, the universal serial bus device does not support host migration.

In particular, bare device storage refers to a storage way that maps a storage device directly to a virtual machine without any abstraction and encapsulation of it. In bare device storage, a virtual machine can directly access data on a physical device, so that higher performance and lower latency can be achieved. In the case where a host uses bare device storage as a system disk, the bare device storage should not support host migration, otherwise the virtual machine will not be able to access the data after host migration.

A universal serial bus (Universal Serial Bus, USB) device is a common computer external device connection interface, and is used for connecting various external hardware devices such as a keyboard, a mouse, a printer, and a storage device. In the case of a usb device being used by a host, the usb device does not support host migration, otherwise the virtual machine will not be able to access the usb device after host migration.

According to the virtual resource scheduling method, the hardware resource requirements in host migration are limited according to the virtual machine, so that the virtual machine can be smoothly started in the screened hosts.

Specifically, the container management platform running in the host has been initialized and is in an enabled state, indicating that the host allows the Xu Kaiqi container and is capable of providing the basic configuration conditions for container operation.

In addition, when the container is running, an operation directory, also called a work directory (working directory), needs to be set in the host. When the container is opened, this running catalog is entered by default, which is the underlying catalog of applications in the container. Once the running catalog is entered, commands and applications in the container are executed under the catalog, which can make operations in the container more convenient and uniform. If the utilization of the running catalog is greater than or equal to the preset utilization threshold, then it is indicated that the host has failed to run more containers. Therefore, the utilization rate of the running catalog corresponding to the container should be smaller than the preset utilization rate threshold. The preset utilization threshold may be set as desired, for example 90%. The utilization rate of the running catalog refers to the utilization rate of the storage space corresponding to the running catalog.

According to the virtual resource scheduling method, the hardware resource requirements in host migration are limited according to the container, so that the container can be smoothly opened in the screened hosts.

In some embodiments, step 140 comprises:

and under the condition that the failure times of any host to start the virtual entity is zero, determining any host as a target host corresponding to the virtual entity.

Specifically, in the case that the second candidate host list includes a plurality of available hosts, the target host corresponding to the virtual entity may be determined according to the virtual entity activation record. The method can be carried out according to the following steps:

step one, traversing the host list

Traversing each host in the second candidate host list one by one.

Step two, obtaining a virtual entity opening record

And aiming at each host, acquiring a corresponding virtual entity opening record, wherein the record comprises a failed opening record.

Step three, counting failure times

And counting the failure times of each host for starting the virtual entity, namely counting the failure times in the starting record of the host.

Step four, checking failure times

The failure times of the host to open the virtual entity are zero, and the resources provided by the host can be considered to be enough to open and operate the virtual machine or the container, or the success rate of opening the virtual machine or the container in the host is higher.

And checking the failure times of each host, and if the failure times of any host are found to be zero, determining the host as a target host corresponding to the virtual entity.

If the failure times of the plurality of hosts are zero, one host can be randomly selected from the hosts as a target host; the host with the most provided resources can be used as the target host according to the ordering of the processor resources, the memory resources, the storage resources, the network resources and the like which can be provided by each host.

According to the virtual resource scheduling method provided by the embodiment of the invention, the target host is determined according to the failure times of starting the virtual entity by each host, so that the success rate of virtual resource scheduling is improved.

In some embodiments, after determining the number of failures of each host to open the virtual entity, the method further comprises:

And determining the host corresponding to the highest opening priority as a target host corresponding to the virtual entity.

Specifically, under the condition that the failure times of starting the virtual entity of each host in the second candidate host list are not zero, the starting priority of each host can be determined according to the failure times of starting the virtual entity of each host.

The starting priority is used for measuring the priority degree of each host to start the virtual entity to be scheduled. The higher the opening priority, the greater the likelihood that the corresponding host becomes the target host; the smaller the opening priority, the less likely the corresponding host becomes the target host. The opening priority and the failure times are in a negative correlation, which means that the smaller the failure times are, the higher the success rate of opening the virtual machine or the container in the host is, and the higher the opening priority is.

And the hosts in the second candidate host list can be arranged in a descending order according to the starting priority, and the host corresponding to the highest starting priority is selected and used as the target host corresponding to the virtual entity.

According to the virtual resource scheduling method provided by the embodiment of the invention, the starting priority of each host is determined according to the failure times of starting the virtual entity of each host, unified management and scheduling of the hosts in the cluster system are realized, and the success rate of virtual resource scheduling is improved.

In some embodiments, after determining the opening priority of each host based on the number of failures of each host to open the virtual entity, the method further comprises:

and determining the host corresponding to the highest residual memory capacity as a target host corresponding to the virtual entity.

Specifically, each host in the second candidate host list may face the case where the opening priority is the same, in which case the remaining memory capacity of each host may be calculated. The higher the remaining memory capacity, the more adequate the memory resources provided by the host; the lower the remaining memory capacity, the more limited the memory resources provided by the host. The remaining memory capacity can also be measured by the memory utilization, and the lower the memory utilization, the higher the remaining memory capacity under the condition that the total memory capacity of each host is consistent.

And the hosts with the same starting priority can be arranged in descending order according to the residual memory capacity, and the host corresponding to the highest residual memory capacity is selected and used as the target host corresponding to the virtual entity.

According to the virtual resource scheduling method provided by the embodiment of the invention, the target host is determined according to the residual memory capacity under the condition that the starting priority of each host is the same, unified management and scheduling of hosts in the cluster system are realized, and the success rate of virtual resource scheduling is improved.

In some embodiments, after the virtual entity is turned on in the target host, the method further comprises:

determining an opening result of the virtual entity in the target host;

Specifically, after the virtual entity is started in the target host, a starting result of the virtual entity in the target host may be obtained. The results of the opening may include success or failure.

If the start result is successful, the target host may be considered to be able to provide sufficient resources for starting the virtual machine or container. Therefore, the failure times of starting the virtual entity in the virtual entity starting record of the target host can be cleared, so that the number of hosts available in the cluster system can be increased when virtual resources are scheduled next time, and the success rate of virtual resource scheduling is improved.

In some embodiments, after determining the start result of the virtual entity in the target host, the method further comprises:

Specifically, if the start result is failure, the target host may be considered to be unable to provide sufficient resources for starting the virtual machine or container. Therefore, the failure times of starting the virtual entity in the virtual entity starting record of the target host can be added, so that whether the host is available or not can be quickly determined according to the virtual entity starting record in the next virtual resource scheduling, and the success rate of the virtual resource scheduling is improved.

In some embodiments, step 120 further comprises, after:

Specifically, when judging the resources, if no available candidate host is found, feedback is needed to the user or the cluster system, and the failure reason is prompted in the feedback information.

And under the condition that the first candidate host list is empty, indicating that no available first candidate host exists, generating first scheduling failure information corresponding to the virtual entity to be scheduled. The first scheduling failure information is mainly used for prompting the matching failure of the common resource request.

From the content perspective, the first scheduling failure information includes the resource type of the virtual entity and the resource matching judgment result of the common resource request to each host in the cluster system. Here, the resource matching determination result may be a matching result (satisfied or not satisfied) of the host to each resource request in the common resource requests.

According to the virtual resource scheduling method provided by the embodiment of the invention, under the condition that the first candidate host list is empty, the first scheduling failure information corresponding to the virtual entity is generated, and feedback and error reporting are carried out on the user or the cluster system, so that the user can conveniently and rapidly check the reasons, and the use experience of the user on the cluster system is improved.

In some embodiments, after determining the second candidate host list corresponding to the virtual entity, the method further includes:

the second scheduling failure information includes a resource type of the virtual entity and a result of judging a resource match of the dedicated resource request to each host in the first candidate host list.

Specifically, in the case that the second candidate host list is empty, which indicates that there is no available second candidate host, the second scheduling failure information corresponding to the virtual entity may be generated. The second scheduling failure information is mainly used for prompting the matching failure of the exclusive resource request.

From the content perspective, the second scheduling failure information includes the resource type of the virtual entity and the result of judging the resource matching of the dedicated resource request to each host in the first candidate host list. Here, the resource matching determination result may be a matching result (satisfied or unsatisfied) of the host to each resource request in the dedicated resource requests.

According to the virtual resource scheduling method provided by the embodiment of the invention, the second scheduling failure information corresponding to the virtual entity is generated under the condition that the second candidate host list is empty, and feedback and error reporting are carried out on the user or the cluster system, so that the user can conveniently and rapidly check the reasons, and the use experience of the user on the cluster system is improved.

The apparatus provided in the embodiments of the present application will be described below, and the apparatus described below and the method described above may be referred to correspondingly.

Fig. 2 is a schematic structural diagram of a virtual resource scheduling apparatus provided in the present application, and as shown in fig. 2, a virtual resource scheduling apparatus 200 includes:

a determining unit 210, configured to determine a virtual entity to be scheduled; the resource type of the virtual entity comprises a virtual machine or a container;

a first detecting unit 220, configured to determine a first candidate host list corresponding to a virtual entity, by performing resource matching judgment on each host in the cluster system based on a common resource request of the virtual machine and the container to the hosts;

A second detecting unit 230, configured to determine a resource type corresponding to the virtual entity, and determine a second candidate host list corresponding to the virtual entity by performing resource matching judgment on each host in the first candidate host list based on a dedicated resource request of the resource type on the host;

the scheduling unit 240 is configured to determine a target host corresponding to the virtual entity based on the virtual entity start record of each host in the second candidate host list, and start the virtual entity in the target host.

The virtual resource scheduling device provided by the embodiment of the application determines a virtual entity to be scheduled; performing resource matching judgment on each host in the cluster system based on a common resource request of the virtual machine and the container to the hosts, and determining a first candidate host list corresponding to the virtual entity; determining a resource type corresponding to the virtual entity, and performing resource matching judgment on each host in the first candidate host list based on a dedicated resource request of the resource type on the host, so as to determine a second candidate host list corresponding to the virtual entity; determining a target host corresponding to the virtual entity based on the virtual entity opening records of all hosts in the second candidate host list, and opening the virtual entity in the target host; the method has the advantages that the common resource request and the dedicated resource request are adopted to carry out resource matching judgment on each host in the cluster system, candidate hosts are obtained by screening from each host in the cluster system, and the target hosts are determined according to the virtual entity opening records of the candidate hosts, so that unified scheduling of virtual machines and containers in the cluster system is realized, repeated calculation of host resources is avoided, host resource conflict during scheduling is avoided, and normal opening and operation of the virtual machines and containers in the cluster system are ensured.

In some embodiments, the determining unit is to:

receiving a virtual resource scheduling request;

In some embodiments, the determining unit is to:

determining a container management platform running in a cluster system;

the container dispatch engine is disabled in the container management platform.

In some embodiments, the determining unit is to:

In some embodiments, the first detection unit is configured to:

In some embodiments, the second detection unit is configured to:

in the case of a host using bare device storage as a system disk, the bare device storage does not support host migration, and in the case of a universal serial bus device used by the host, the universal serial bus device does not support host migration.

In some embodiments, the scheduling unit is to:

determining an opening result of the virtual entity in the target host;

In some embodiments, the scheduling unit is to:

In some embodiments, the apparatus further comprises:

the abnormal management unit is used for generating first scheduling failure information corresponding to the virtual entity under the condition that the first candidate host list is empty;

the first scheduling failure information comprises the resource type of the virtual entity and the judgment result of the common resource request on each host in the cluster system.

In some embodiments, the exception management unit is to:

the second scheduling failure information includes a resource type of the virtual entity and a determination result of the dedicated resource request on each host in the first candidate host list.

Fig. 3 is a schematic structural diagram of a cluster system provided in the present application, and as shown in fig. 3, a cluster system 300 includes a virtual resource scheduling apparatus 200 in the foregoing embodiment, and a plurality of hosts 310;

the host 310 is connected to the virtual resource scheduling apparatus 200 and is configured to turn on a virtual entity to be scheduled.

Specifically, the embodiment of the application does not limit the number of hosts in the cluster system. The cluster system may provide clients to users. A user may submit a virtual resource scheduling request to the clustered system at a client for requesting a host in the clustered system to turn on a virtual entity.

The virtual resource scheduling device executes the virtual resource scheduling method in the above embodiment, selects a target host from a plurality of hosts, and forwards a virtual resource scheduling request to the target host. The target host is used for starting the virtual entity to be scheduled.

According to the cluster system provided by the embodiment of the application, the virtual resource scheduling device is configured, and as the common resource request and the dedicated resource request are adopted to carry out resource matching judgment on each host in the cluster system, candidate hosts are obtained by screening from each host in the cluster system, and the target hosts are determined according to the virtual entity opening records of the candidate hosts, unified scheduling of virtual machines and containers in the cluster system is realized, repeated calculation of host resources is avoided, host resource conflict during scheduling is avoided, and normal opening and operation of the virtual machines and containers in the cluster system are ensured.

Fig. 4 is a schematic structural diagram of a hybrid scheduling apparatus for virtual machines and containers provided in the present application, and as shown in fig. 4, the hybrid scheduling apparatus 400 includes a virtual entity queue management module 410, a scheduling engine processing module 420, a common scheduling detection module 430, a virtual machine scheduling detection module 440, a container scheduling detection module 450, a cache information processing module 460, an exception information processing module 470, and a task management module 480.

Fig. 5 is a flow chart of a hybrid scheduling method of a virtual machine and a container provided in the present application, and as shown in fig. 5, the hybrid scheduling device in the foregoing embodiment disables a scheduling module of a container management platform service itself in a cluster system and uses a unified scheduling engine processing module before executing the hybrid scheduling method.

Step 510, the user opens the virtual machine or container, and the system issues the work task and adds the work task to the task queue to be scheduled. The virtual entity queue management module periodically judges whether a virtual entity to be scheduled exists in the scheduling queue, and if so, takes out the virtual entity at the head of the queue, one at a time.

Step 520, the scheduling engine processing module firstly calls the public scheduling detection module to obtain all host lists in the system, traverses the host lists, sequentially calls methods in the public scheduling detection module aiming at hosts in the lists, judges whether all conditions of the hosts meet the condition of starting the virtual entity, adds the hosts into the candidate host list if all conditions of the hosts meet the condition of starting the virtual entity, and eliminates the hosts if one method returns an error. For starvation type resources such as memory and storage of a host, concurrent control is needed, and serial upgrade of scheduling can be achieved through a queue to be scheduled, so that memory overflow or insufficient disk space can be avoided.

In step 530, the scheduling engine processing module obtains a candidate host list, and continues to execute with the virtual entity and the candidate host list as parameters. Firstly judging the type of the virtual entity, if the virtual entity is a virtual machine, calling a virtual machine scheduling detection module, and if the virtual entity is a container, calling a container scheduling detection module.

The virtual machine scheduling detection module traverses the candidate host list and further filters the candidate host list through special constraint conditions of the virtual machine to obtain a new candidate host list; the container scheduling detection module traverses the candidate host list and further filters the candidate host list through the special constraint conditions of the container to obtain a new candidate host list.

Step 540, a candidate host list is obtained, in which a most suitable host is required to be obtained from the list and returned to the scheduling engine processing module, the data in the cache information processing module is firstly obtained, the cache data information is analyzed, and whether the virtual entity has a record of opening failure and the number of opening failure on each candidate host is judged. If so, the selected priority of the host is reduced, the higher the number of times is, the lower the priority is, the first sorting is performed according to the priority, finally the hosts with the same priority are sorted according to the residual memory capacity, the host with the highest priority and the highest residual memory capacity is selected, and the host is returned to the task management module.

Step 550, if the boot task is successful, the cache information corresponding to the virtual entity is cleaned, including the record information of the previous failure of the virtual entity in the host; if the virtual entity is started to fail, the failure information is recorded into a cache, whether the failure record from the virtual entity to the host exists or not is firstly judged, if the failure record does not exist, the failure record is newly added, and if the failure record exists, the number of failures is increased by 1.

In the above step, if no available host is found during the scheduling detection, the information of the scheduling failure needs to be fed back to the abnormal information processing module. And the abnormal information processing module displays the abnormal information of the scheduling failure. The virtual machine and the container can share internationalization information, and replace virtual entity names with placeholders, and when interface display is needed, the virtual entity type display uses internationalized names as parameters for transmission.

According to the hybrid scheduling method, virtual machines and container scheduling are integrated and unified, two sets of scheduling frames are prevented from occurring in a cluster system, so that scheduling conflict or superdivision of partial resources is avoided, maintenance cost brought by the two sets of scheduling frames is reduced, a scheduler is easier to understand, learning and maintenance cost is reduced, user experience and usability of products are improved, and core competitiveness of the products is improved.

Fig. 6 is a schematic structural diagram of an electronic device provided in the present application, and as shown in fig. 6, the electronic device may include: processor (Processor) 610, communication interface (Communications Interface) 620, memory (Memory) 630, and communication bus (Communications Bus) 640, wherein Processor 610, communication interface 620, memory 630 complete communication with each other through communication bus 640. The processor 610 may invoke logic commands in the memory 630 to perform the methods described in the above embodiments, such as:

Determining a virtual entity to be scheduled; the resource type of the virtual entity comprises a virtual machine or a container; performing resource matching judgment on each host in the cluster system based on a common resource request of the virtual machine and the container to the hosts, and determining a first candidate host list corresponding to the virtual entity; determining a resource type corresponding to the virtual entity, and performing resource matching judgment on each host in the first candidate host list based on a dedicated resource request of the resource type on the host, so as to determine a second candidate host list corresponding to the virtual entity; and determining a target host corresponding to the virtual entity based on the virtual entity starting record of each host in the second candidate host list, and starting the virtual entity in the target host.

In addition, the logic commands in the memory described above may be implemented in the form of software functional units and may be stored in a computer readable storage medium when sold or used as a stand alone product. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several commands for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The processor in the electronic device provided by the embodiment of the present application may call the logic instruction in the memory to implement the above method, and the specific implementation manner of the processor is consistent with the implementation manner of the foregoing method, and may achieve the same beneficial effects, which are not described herein again.

The present application also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, is implemented to perform the methods provided by the above embodiments.

The specific embodiment is consistent with the foregoing method embodiment, and the same beneficial effects can be achieved, and will not be described herein.

Embodiments of the present application provide a computer program product comprising a computer program which, when executed by a processor, implements a method as described above.

The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.

From the above description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus necessary general hardware platforms, or of course may be implemented by means of hardware. Based on this understanding, the foregoing technical solution may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the respective embodiments or some parts of the embodiments.

Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and are not limiting thereof; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the corresponding technical solutions.

Claims

1. A virtual resource scheduling method, comprising:

determining a target host corresponding to the virtual entity based on a virtual entity opening record of each host in the second candidate host list, and opening the virtual entity in the target host;

the common resource request refers to a common request of a virtual machine and a container to host resources when the virtual machine and the container run in the host; the exclusive resource request refers to a request of a virtual entity with different resource types for a host resource when running in the host;

the dedicated resource request of the virtual machine to the host comprises:

In the case where a host uses bare device storage as a system disk, the bare device storage does not support host migration, and in the case where a host uses universal serial bus device, the universal serial bus device does not support host migration;

the proprietary resource request of the container to the host includes:

the container management platform running in the host is initialized and in an enabling state, and the utilization rate of the running catalogue corresponding to the container is smaller than a preset utilization rate threshold;

the determining, based on the virtual entity opening record of each host in the second candidate host list, a target host corresponding to the virtual entity includes:

2. The method for scheduling virtual resources according to claim 1, wherein the determining a virtual entity to be scheduled includes:

receiving a virtual resource scheduling request;

3. The virtual resource scheduling method of claim 2, wherein prior to receiving the virtual resource scheduling request, the method further comprises:

determining a container management platform running in the cluster system;

a container dispatch engine is disabled in the container management platform.

4. The method for scheduling virtual resources according to claim 2, wherein the determining the virtual entity corresponding to the virtual resource scheduling request includes:

5. The method for scheduling virtual resources according to claim 1, wherein the determining the first candidate host list corresponding to the virtual entity based on the resource matching determination of each host in the cluster system by the common resource request of the virtual machine and the container to the host includes:

6. The method of claim 5, wherein after performing the resource matching determination on each host in the host list based on the common resource request of the virtual machine and the container to the host, the method further comprises:

7. The method of claim 6, wherein the common resource request includes at least one of host unopened processor binding, host remaining memory capacity meeting virtual entity memory capacity requirements, host storage capacity meeting virtual entity storage capacity requirements, host unopened host binding in the clustered system, host network card meeting virtual entity network resource requirements, and host security identification consistent with virtual entity security identification.

8. The method for scheduling virtual resources according to claim 1, wherein the determining the second candidate host list corresponding to the virtual entity by performing resource matching judgment on each host in the first candidate host list based on the dedicated resource request of the resource type for the host includes:

9. The method for scheduling virtual resources according to claim 1, wherein after determining the number of failures of each host to open a virtual entity, the method further comprises:

10. The virtual resource scheduling method of claim 9, wherein after determining the turn-on priority of each host based on the number of failures of each host to turn on the virtual entity, the method further comprises:

11. The virtual resource scheduling method of claim 1, wherein after the virtual entity is turned on in the target host, the method further comprises:

determining an opening result of the virtual entity in the target host;

12. The method of claim 11, wherein after determining a result of the opening of the virtual entity in the target host, the method further comprises:

13. The method for scheduling virtual resources according to claim 1, wherein after determining the first candidate host list corresponding to the virtual entity, the method further comprises:

14. The method for scheduling virtual resources according to claim 1, wherein after determining the second candidate host list corresponding to the virtual entity, the method further comprises:

15. A virtual resource scheduling apparatus, comprising:

the scheduling unit is used for determining a target host corresponding to the virtual entity based on the virtual entity opening record of each host in the second candidate host list, and opening the virtual entity in the target host;

The dedicated resource request of the virtual machine to the host comprises:

the proprietary resource request of the container to the host includes:

the scheduling unit is used for:

16. A cluster system comprising the virtual resource scheduling apparatus of claim 15, and a plurality of hosts;

17. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the virtual resource scheduling method of any one of claims 1 to 14 when the program is executed by the processor.

18. A non-transitory computer readable storage medium having stored thereon a computer program, wherein the computer program when executed by a processor implements the virtual resource scheduling method of any one of claims 1 to 14.