Physical machine scheduling method and device, electronic equipment and readable storage medium

Abstract

The embodiment of the invention provides a physical machine scheduling method and device, a storage medium and electronic equipment, and relates to the technical field of cloud computing. The method comprises the following steps: receiving a scheduling request sent by a target object, wherein the scheduling request comprises a target object identifier of the target object; obtaining a reference label identifier, wherein the reference label identifier comprises at least one label identifier which is inquired from an object label relation table and corresponds to the target object identifier; querying at least one reference physical machine identifier corresponding to the reference tag identifier from a physical machine tag relationship table, and determining a target physical machine according to a physical machine corresponding to each reference physical machine identifier; and scheduling the target physical machine to execute the target task, such as creating a cloud server. According to the corresponding relation among the target object, the label and the physical machine, the target physical machine can be determined for the target object in time, and the efficiency of the physical machine scheduling process is improved.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and more specifically, to a physical machine scheduling method, apparatus, electronic device, and computer-readable storage medium. Background Technology

[0002] In the field of cloud computing, the creation and migration of cloud services rely on the scheduling of physical machines. With the rapid development of cloud computing technology, people's needs for cloud servers are becoming more diversified and dynamic, which puts forward higher requirements for the scheduling of physical machines.

[0003] Existing technologies divide all physical machines into different isolation zones when scheduling physical machine resources. Different users correspond to different isolation zones, and physical machines are retrieved for users from the isolation zones. Since users have diverse requirements for physical machines when scheduling them, and the number of physical machines included in the isolation zones is large, scheduling physical machines through the isolation zones is inefficient. Summary of the Invention

[0004] This application provides a physical machine scheduling method, apparatus, electronic device, computer-readable storage medium, and computer program product, which can solve the above-mentioned problems of the prior art. The technical solution is as follows:

[0005] According to a first aspect of the embodiments of this application, a physical machine scheduling method is provided, the method comprising:

[0006] Receive a scheduling request sent by the target object, the scheduling request being used to request the scheduling of a physical machine to execute the target task, the scheduling request including the target object identifier of the target object;

[0007] Obtain a reference tag identifier, which includes at least one tag identifier corresponding to the target object identifier, queried from an object tag relationship table. Each tag is used to represent a feature of the physical machine. The object tag relationship table includes the correspondence between object identifiers and tag identifiers.

[0008] The physical machine tag relationship table is used to query at least one reference physical machine identifier corresponding to the reference tag identifier. The target physical machine is determined based on the physical machine corresponding to each reference physical machine identifier. The physical machine tag relationship table includes the correspondence between physical machine identifiers and tag identifiers.

[0009] The target physical machine is scheduled to execute the target task.

[0010] According to a second aspect of the embodiments of this application, a physical machine scheduling apparatus is provided, the apparatus comprising:

[0011] A receiving module is used to receive a scheduling request sent by a target object. The scheduling request is used to request a physical machine to execute a target task. The scheduling request includes the target object identifier of the target object.

[0012] The module is used to obtain a reference tag identifier, which includes at least one tag identifier corresponding to the target object identifier, queried from an object tag relationship table. Each tag is used to represent a feature of the physical machine. The object tag relationship table includes the correspondence between object identifiers and tag identifiers.

[0013] The query module is used to query at least one reference physical machine identifier corresponding to the reference tag identifier from the physical machine tag relationship table, and determine the target physical machine based on the physical machine corresponding to each reference physical machine identifier. The physical machine tag relationship table includes the correspondence between physical machine identifiers and tag identifiers.

[0014] The scheduling module is used to schedule the target physical machine to execute the target task.

[0015] According to a third aspect of the embodiments of this application, an electronic device is provided, the electronic device including a memory, a processor and a computer program stored in the memory, wherein the processor executes the program to implement the steps of the method provided in the first aspect.

[0016] According to a fourth aspect of the embodiments of this application, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps of the method provided in the first aspect.

[0017] According to a fifth aspect of the present application, a computer program product is provided, the computer program product including computer instructions stored in a computer-readable storage medium, wherein when a processor of a computer device reads the computer instructions from the computer-readable storage medium, the processor executes the computer instructions, causing the computer device to perform steps implementing the method provided in the first aspect.

[0018] The beneficial effects of the technical solutions provided in this application are:

[0019] By receiving a scheduling request from the target object, the target object identifier is obtained, enabling the retrieval of the corresponding reference tag identifier. The tag identifier corresponding to the target object identifier in the object tag relationship table is used as the reference tag identifier, with the tag representing the physical machine's characteristics, thus obtaining the physical machine characteristics corresponding to the target object. The reference physical machine identifier corresponding to the reference tag identifier is queried in the physical machine tag relationship table, allowing the retrieval of the corresponding reference physical machine identifier based on the physical machine characteristics of the target object. The target physical machine is determined using each reference physical machine identifier, ensuring that the target physical machine corresponds to the physical machine characteristics of the target object. By setting up the object tag relationship table and the physical machine tag relationship table, a correspondence between the target object, tags, and physical machines is established. This allows for the timely determination of the target physical machine for the target object upon receiving a scheduling request, based on the correspondence between the target object, tags, and physical machine, and the scheduling of the target physical machine to execute the target task in the scheduling request, thereby improving the efficiency of the physical machine scheduling process. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below.

[0021] Figure 1 This is a schematic diagram of a system architecture for implementing physical machine scheduling provided in an embodiment of this application;

[0022] Figure 2 A flowchart illustrating a physical machine scheduling method provided in an embodiment of this application;

[0023] Figure 3 A schematic diagram of a physical machine scheduling process provided in an embodiment of this application;

[0024] Figure 4 A schematic diagram illustrating another physical machine scheduling process provided in this application embodiment;

[0025] Figure 5 A schematic diagram illustrating a process for obtaining a reference label identifier, provided as an embodiment of this application;

[0026] Figure 6 A schematic diagram illustrating another physical machine scheduling process provided in this application embodiment;

[0027] Figure 7 A schematic diagram illustrating another process for obtaining a reference label identifier provided in an embodiment of this application;

[0028] Figure 8 A schematic diagram of the storage structure of an object tag relationship table provided in an embodiment of this application;

[0029] Figure 9a A flowchart illustrating another physical machine scheduling method provided in this application embodiment;

[0030] Figure 9b A schematic diagram illustrating the construction process of an object label relationship table provided in an embodiment of this application;

[0031] Figure 9c A schematic diagram illustrating the construction process of a physical machine tag relationship table provided in an embodiment of this application;

[0032] Figure 10 A schematic diagram illustrating another physical machine scheduling process provided in this application embodiment;

[0033] Figure 11 This is a schematic diagram of the structure of a physical machine scheduling device provided in an embodiment of this application;

[0034] Figure 12 This is a schematic diagram of the structure of an electronic device for physical machine scheduling provided in an embodiment of this application. Detailed Implementation

[0035] The embodiments of this application are described below with reference to the accompanying drawings. It should be understood that the embodiments described below with reference to the accompanying drawings are exemplary descriptions for explaining the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions of the embodiments of this application.

[0036] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the terms “comprising” and “including” as used in embodiments of this application mean that the corresponding feature can be implemented as the presented feature, information, data, step, operation, element, and / or component, but do not exclude implementation as other features, information, data, step, operation, element, component, and / or combinations thereof supported by the art. It should be understood that when we say that an element is “connected” or “coupled” to another element, the one element can be directly connected or coupled to the other element, or it can mean that the one element and the other element establish a connection relationship through an intermediate element. Furthermore, “connected” or “coupled” as used herein can include wireless connection or wireless coupling. The term “and / or” as used herein indicates at least one of the items defined by the term; for example, “A and / or B” can be implemented as “A,” or as “B,” or as “A and B.”

[0037] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0038] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0039] First, let's introduce and explain several terms used in this application:

[0040] Cloud technology refers to a hosting technology that unifies a series of resources such as hardware, software, and networks within a wide area network or local area network to achieve data computing, storage, processing, and sharing.

[0041] Cloud technology is a collective term for network technologies, information technologies, integration technologies, management platform technologies, and application technologies applied to the cloud computing business model. It can form resource pools, providing flexible and convenient on-demand access. Cloud computing technology will become a crucial support. Backend services of technical network systems require substantial computing and storage resources, such as video websites, image websites, and many portal websites. With the rapid development and application of the internet industry, every item may have its own identification mark in the future, requiring transmission to backend systems for logical processing. Data at different levels will be processed separately, and various industry data will all require robust system support, which can only be achieved through cloud computing.

[0042] Cloud computing refers to the delivery and usage model of IT infrastructure, meaning obtaining necessary resources in an on-demand and easily scalable manner through a network. In a broader sense, cloud computing also refers to the delivery and usage model of services, meaning obtaining necessary services in an on-demand and easily scalable manner through a network. These services can be IT and software related, internet-related, or other services. Cloud computing is a product of the development and integration of traditional computer and network technologies such as grid computing, distributed computing, parallel computing, utility computing, network storage technologies, virtualization, and load balancing.

[0043] With the development of the internet, real-time data streams, and the diversification of connected devices, as well as the demands for search services, social networks, mobile commerce, and open collaboration, cloud computing has rapidly developed. Unlike previous parallel distributed computing, cloud computing will fundamentally revolutionize the entire internet model and enterprise management model.

[0044] In cloud computing, a physical machine is an actual, existing server with its own hardware resources such as processors, memory, and storage, and it can run operating systems and applications. Physical machines are typically used as the infrastructure of cloud computing platforms to provide cloud services such as virtual machines and containers. In a cloud computing environment, physical machines can be virtualized, that is, a single physical server can be divided into multiple virtual servers, thereby improving resource utilization and flexibility.

[0045] The physical machine scheduling method, apparatus, electronic device, computer-readable storage medium, and computer program product provided in this application are intended to solve the above-mentioned technical problems of the prior art.

[0046] The technical solutions of this application and their effects are described below through several exemplary embodiments. It should be noted that the following embodiments can be referenced, borrowed from, or combined with each other. Identical terms, similar features, and similar implementation steps in different embodiments will not be repeated.

[0047] Figure 1This is a schematic diagram of the system architecture for implementing physical machine scheduling provided in this application embodiment. Terminal 101 provides a cloud server console interface to the target object, obtains a scheduling request sent by the target object through the cloud server console interface, and requests the scheduling of a physical machine to perform a target task. For example, the target task could be creating a cloud service, and the target object is the object requesting the creation of the cloud service. The scheduling request includes the target object's identifier, such as the user's identity information. After receiving the scheduling request from the target object, terminal 101 sends the target in the scheduling request to server 102. Server 102 stores a pre-generated object tag relationship table and a physical machine tag relationship table. After receiving the target object identifier, server 102 queries the object tag relationship table to find the reference tag identifier corresponding to the target object identifier. In this application embodiment, the tag represents a characteristic of the physical machine. After obtaining the reference tag identifier, server 102 queries the physical machine tag relationship table to find the reference physical machine identifier corresponding to the reference tag identifier. Finally, based on each physical machine identifier, the target physical machine is determined, and the target physical machine is scheduled to perform the target task for the target object.

[0048] Those skilled in the art will understand that the number of terminals described above can be more or less. For example, there may be only one terminal, or there may be dozens or hundreds, or even more terminals. This application does not limit the number or type of terminals. Terminals may be smartphones, tablets, laptops, desktop computers, smart speakers, smartwatches, etc., but are not limited to these. Terminals and servers can be directly or indirectly connected via wired or wireless communication, and this application does not impose any restrictions on this connection.

[0049] In some embodiments, server 102 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms. Server 102 is used to provide background services for applications that support image acquisition. In some embodiments, server 102 undertakes the main computing work, and terminal 101 undertakes the secondary computing work; or, server 102 undertakes the secondary computing work, and terminal 101 undertakes the main computing work; or, server 102 and terminal 101 collaborate on computing using a distributed computing architecture.

[0050] For example, the physical machine scheduling methods in the embodiments of this application can all be performed by a server. The following description uses a server as the execution entity to illustrate the schemes in the embodiments of this application.

[0051] This application provides a physical machine scheduling method, such as... Figure 2 As shown, the method includes steps S201-S204.

[0052] S201. Receive a scheduling request sent by the target object. The scheduling request is used to request the scheduling physical machine to execute the target task. The scheduling request includes the target object identifier of the target object.

[0053] In this embodiment of the application, the target object can be a user who purchases cloud services. The target object can initiate a scheduling request through the cloud service console so that the server can schedule a suitable physical machine to perform the target task. The target task can be creating a cloud server or migrating a cloud server. After receiving the scheduling request, the server obtains the target object identifier of the target object. The target object identifier can be the customer's name or customer's identity information, or it can be a number set by the business personnel for the target object.

[0054] In this embodiment of the application, by receiving the scheduling request of the target object, the target object identifier of the target object is obtained, which is beneficial for subsequent querying of the tag identifier corresponding to the target object identifier according to the object tag relationship table.

[0055] S202. Obtain a reference label identifier, which includes at least one label identifier corresponding to the target object identifier, queried from the object label relationship table. Each label is used to represent a feature of the physical machine. The object label relationship table includes the correspondence between object identifiers and label identifiers.

[0056] In this embodiment, a tag is used to represent a feature of a physical machine. For example, if jumbo frame capability is a feature of a physical machine, then jumbo frame capability can be used as a tag. The tag identifier of each tag can be the name of the tag. For example, when jumbo frame capability is used as a tag, the name of the tag is jumbo frame capability, and the tag identifier is also jumbo frame capability.

[0057] In this embodiment of the application, the object tag relationship table includes the correspondence between object identifiers and tag identifiers. Therefore, one way to obtain the reference tag identifier is to query the tag identifier corresponding to the target object identifier from the object tag relationship table according to the target object identifier obtained in step S201. It should be understood that the tag identifier corresponding to the target object identifier may include one or more, and all the tag identifiers corresponding to the target object identifier are used as reference tag identifiers.

[0058] like Figure 3 As shown, Figure 3An exemplary schematic diagram of a physical machine scheduling process provided in an embodiment of this application is shown. As can be seen from the diagram, when target object 1 initiates a scheduling request, the server obtains the object identifier 1 of target object 1, and obtains the tag identifiers corresponding to object 1 from the object tag relationship table, namely tag identifier a and tag identifier c. Then, the reference tag identifiers corresponding to object identifier 1 are reference tag identifier a and reference tag identifier c.

[0059] In this embodiment, a pre-generated object tag relationship table is used to obtain the correspondence between object identifiers and tag identifiers. This allows the corresponding reference tag identifier to be found in the object tag relationship table based on the target object identifier. This provides the characteristics of the physical machine corresponding to the target object when scheduling the physical machine to execute the target task. This is beneficial for determining the target physical machine based on the characteristics of the physical machine corresponding to the reference tag identifier, so as to execute the target task for the target object.

[0060] S203. Query at least one reference physical machine identifier corresponding to the reference tag identifier from the physical machine tag relationship table, and determine the target physical machine based on the physical machine corresponding to each reference physical machine identifier. The physical machine tag relationship table includes the correspondence between physical machine identifiers and tag identifiers.

[0061] In this embodiment, the physical machine tag relationship table includes the correspondence between physical machine identifiers and tag identifiers. The physical machine identifier can be a number set by business personnel for the physical machine, ensuring a one-to-one correspondence between physical machines and physical machine identifiers. Based on the reference tag identifier obtained in step S202, the physical machine identifier corresponding to the reference tag identifier is queried in the physical machine tag relationship table as a reference physical machine identifier. Each reference tag identifier can correspond to multiple physical machine identifiers. The target physical machine is selected based on each reference physical machine identifier.

[0062] like Figure 3 As shown in the figure, the reference label identifiers for object identifier 1 include reference label identifier a and reference label identifier c. According to the physical machine label relationship table, reference label identifier a corresponds to physical machine identifier A and physical machine identifier B. Therefore, the reference physical machine identifiers for reference label identifier a are reference physical machine identifier A and reference physical machine identifier B. At the same time, reference label identifier c corresponds to physical machine identifier A and physical machine identifier C. Therefore, the reference physical machine identifiers for reference label identifier c are reference physical machine identifier A and reference physical machine identifier C.

[0063] In this embodiment, a pre-generated physical machine label relationship table is used to obtain the correspondence between physical machine identifiers and label identifiers. This allows the corresponding reference physical machine identifier to be found in the physical machine label relationship table based on the reference label identifier, and then the corresponding physical machine is located based on the reference physical machine identifier, thereby determining the target physical machine and improving the efficiency of scheduling physical machines for the target object. Furthermore, the determined target physical machine differs depending on the user's scheduling strategy, achieving coarse-grained isolation during physical machine scheduling.

[0064] S204. Schedule the target physical machine to execute the target task.

[0065] In this embodiment, the target physical machine is determined based on an object label relationship table and a physical machine label relationship table. Once the target physical machine is determined, the target task requested by the target object can be executed based on that target physical machine. For example, if the target task is to create a cloud server, then a cloud server will be created for the target object based on the target physical machine.

[0066] In this embodiment, by receiving a scheduling request sent by a target object, the target object identifier is obtained, and a corresponding reference tag identifier is obtained based on the target object identifier. By using the tag identifier corresponding to the target object identifier in the object tag relationship table as the reference tag identifier, and the tag is used to represent the characteristics of the physical machine, the physical machine characteristics corresponding to the target object are obtained. By querying the physical machine tag relationship table for the reference physical machine identifier corresponding to the reference tag identifier, the corresponding reference physical machine identifier is obtained based on the physical machine characteristics corresponding to the target object. The target physical machine is determined based on the physical machine corresponding to each reference physical machine identifier, so that the target physical machine can correspond to the characteristics of the physical machine corresponding to the target object. By setting the object tag relationship table and the physical machine tag relationship table, a correspondence between the target object, the tag, and the physical machine is established. Thus, after receiving the scheduling request of the target object, the target physical machine can be determined for the target object in a timely manner based on the correspondence between the target object, the tag, and the physical machine, and the target physical machine can be scheduled to execute the target task in the scheduling request, thereby improving the efficiency of the physical machine scheduling process.

[0067] Based on the above embodiments, as an optional embodiment, the process of constructing the object label relationship table includes:

[0068] Obtain the first scheduling policy for each object. The first scheduling policy is used to represent the requirements of the corresponding object on the physical machine when using the physical machine.

[0069] For each first scheduling strategy, each feature corresponding to the first scheduling strategy is treated as a label, and a label identifier for that label is generated. A correspondence between the label identifier and the first object identifier of the corresponding object is established in the object label relationship table.

[0070] In this embodiment, the object tag relationship table is generated based on the first scheduling strategy of each object. Before the target object initiates a scheduling request, business personnel can summarize the first scheduling strategies of all objects and generate a corresponding entry in the object tag relationship table based on the first scheduling strategy of each object. The first scheduling strategy of each object represents the object's requirements for the physical machine's characteristics when using it. Those skilled in the art should understand that the object's requirements for the physical machine's characteristics when using it are the same as the requirements for the cloud server created based on the physical machine. For example, if a user's first scheduling strategy requires the created cloud server to have jumbo frame capability, it means that the user requires the physical machine to have jumbo frame capability when using it. Similarly, if a user's first scheduling strategy requires the created cloud server to be multi-queue, it means that the user requires the physical machine to be a multi-queue physical machine when using it.

[0071] In this embodiment, a corresponding feature is extracted from the first scheduling strategy and used as a label. Therefore, the label is used to represent a feature of the physical machine. The label identifier can be a label name, which can be determined based on the feature represented by the label. For example, if the label represents the giant frame capability of the physical machine, then the label name is Giant Frame Capability.

[0072] In this embodiment, an object may have multiple first scheduling policies, and the tags are generated according to the first scheduling policies. Therefore, each object may correspond to multiple tags, and each object identifier may correspond to multiple tag identifiers. After determining the correspondence between objects and tags, a correspondence between the first object identifier and the tag identifier of each object is established. The correspondence between the first object identifiers and tag identifiers of all objects constitutes an object tag relationship table.

[0073] In this embodiment, by obtaining the first scheduling strategy of each object, the characteristic requirements of each object on the physical machine when using the physical machine are obtained; by using the corresponding characteristic in the first scheduling strategy as a label, the label is used to represent a characteristic of the physical machine; by establishing the correspondence between the first object identifier and the label, the specific requirements of each object on the physical machine when using the physical machine can be clarified. Therefore, in this embodiment, the correspondence between the target object identifier and the label identifier in the object label relationship table is generated according to the first scheduling strategy of the target object, so that the target physical machine finally determined in this embodiment can meet the first scheduling strategy of the target object, and realizes targeted scheduling of physical machines to execute target tasks for the target object.

[0074] Based on the above embodiments, as an optional embodiment, the first scheduling strategy is used to represent the features that the corresponding object requires the physical machine to have when using the physical machine, or the features that it requires the physical machine not to have.

[0075] The process of constructing the object label relationship table also includes:

[0076] Generate first indication information corresponding to each tag, and establish the correspondence between the first object identifier, the tag identifier and the first indication information; the first indication information corresponding to each tag is used to indicate whether the scheduling policy corresponding to the tag requires the physical machine to have the corresponding feature or requires the physical machine not to have the corresponding feature.

[0077] In this embodiment, the first scheduling strategy represents the requirements for the physical machine's characteristics. These requirements can be either requiring the physical machine to possess the corresponding characteristics or requiring it not to possess the corresponding characteristics. It should be understood that different users may have different requirements for the physical machine's characteristics. For example, one user might require the physical machine to have jumbo frame capability to ensure good transmission performance of the created cloud server, while another user might have lower requirements for the transmission performance of the created cloud server and, to reduce costs, require the physical machine not to have jumbo frame capability.

[0078] In this embodiment of the application, the object tag relationship table is generated according to the first scheduling strategy of each object. In order to clearly display the specific scheduling strategy of the object in the object tag relationship table, a correspondence between the object identifier, the tag identifier and the first indication information is established. The first indication information is used to indicate whether the scheduling strategy corresponding to the tag requires the physical machine to have the corresponding feature or requires the physical machine not to have the corresponding feature.

[0079] In this embodiment, the first indication information can be represented by "require" and "reject". If the first indication information is "require", it means that the corresponding object requires the physical machine to have the features represented by the corresponding label. If the first indication information is "reject", it means that the corresponding object requires the physical machine not to have the features represented by the corresponding label. As an optional embodiment, the first indication information can also be represented by "1" and "0". If the first indication information is "1", it means that the corresponding object requires the physical machine to have the features represented by the corresponding label. If the first indication information is "0", it means that the corresponding object requires the physical machine not to have the features represented by the corresponding label.

[0080] In this embodiment of the application, an object label relationship table is constructed, which not only establishes the correspondence between object identifiers and label identifiers, but also establishes the correspondence between object identifiers, label identifiers and first indication information. This allows the specific requirements of the corresponding object when using a physical machine to be clearly defined based on the first indication information in the object label relationship table, thereby improving the efficiency of scheduling a suitable physical machine for the object.

[0081] Based on the above embodiments, as an optional embodiment, the target physical machine is determined according to the physical machine corresponding to each reference physical machine identifier, including:

[0082] For each reference tag identifier, if the first indication information corresponding to the reference tag identifier in the object tag relationship table is used to indicate that the scheduling strategy corresponding to the tag requires the physical machine to have the corresponding characteristics, then the physical machine is identified as the physical machine of the reference physical machine identifier corresponding to the reference tag identifier, and is used as the candidate physical machine corresponding to the reference tag identifier.

[0083] For each reference tag identifier, if the first indication information corresponding to the reference tag identifier in the object tag relationship table is used to indicate that the scheduling strategy corresponding to the tag requires the physical machine to not have the corresponding feature, then the physical machine whose physical machine identifier is not the reference physical machine identifier corresponding to the reference tag identifier is taken as the candidate physical machine corresponding to the reference tag identifier.

[0084] Take the intersection of all candidate physics machines corresponding to the reference labels, and use that as the target physics machine.

[0085] In this embodiment, the reference tag identifier is the tag identifier corresponding to the target object identifier in the object tag relationship table. One target object identifier may correspond to multiple reference tag identifiers. For each reference tag identifier, the first indication information corresponding to that reference tag identifier is queried from the object tag relationship table. It should be understood that the first indication information corresponds to both the reference tag identifier and the target object identifier. If the first indication information is "require" or "1", indicating that the first scheduling policy corresponding to the tag requires the physical machine to have the corresponding feature, the physical machine identifier corresponding to that reference tag identifier is queried from the physical machine tag relationship table, and the physical machine corresponding to the reference physical machine identifier corresponding to that reference tag identifier is selected as a candidate physical machine.

[0086] In this embodiment of the application, for each reference tag identifier, the first indication information of the reference tag identifier in the object tag relationship table is "reject" or "0", which means that the first scheduling policy bit corresponding to the tag requires the physical machine to not have the corresponding feature. The physical machine identifier that does not correspond to the reference tag identifier is queried from the physical machine tag relationship table, and the physical machine corresponding to the physical machine identifier that does not correspond to the reference tag identifier is taken as the candidate physical machine corresponding to the reference tag identifier.

[0087] like Figure 4 As shown, Figure 4 An exemplary schematic diagram of another physical machine scheduling process provided in this application embodiment is shown. After receiving the scheduling request of target object 2, the target object identifier of the target object, i.e., object identifier 2, is obtained. The tag identifiers corresponding to object identifier 2 include tag identifier b and tag identifier c. The first indication information corresponding to both object identifier 2 and tag identifier b is 0, and the first indication information corresponding to both object identifier 2 and tag identifier c is 1. Therefore, the query result is obtained, i.e., object identifier 2 includes reference tag identifier b, the corresponding first indication information is 0, and includes reference tag identifier c, the corresponding first indication information is 1.

[0088] If the physical machine identifier corresponding to the reference label identifier b of the query object identifier 2 in the physical machine label relationship table includes physical machine identifier A and physical machine identifier B, then physical machine identifier A and physical machine identifier B are used as the reference physical machine identifier of the reference label identifier b. Since the first indication information corresponding to the object identifier 2 and the reference label identifier b is 0, physical machine identifiers other than the reference physical machine identifiers are used as candidate physical machine identifiers. That is, the candidate physical machine identifier corresponding to the reference label identifier a of the target object 2 is physical machine identifier C.

[0089] The physical machine identifiers corresponding to the reference label identifier c of the query object identifier 2 in the physical machine label relationship table include physical machine identifier B and physical machine identifier C. Then, physical machine identifier B and physical machine identifier C are used as reference physical machine identifiers of the reference label identifiers. Since the first indication information corresponding to the object identifier 2 and the reference label identifier c is 1, the reference physical machine identifiers are used as candidate physical machine identifiers. That is, the candidate physical machine identifiers corresponding to the reference label identifier c of the target object 2 are physical machine identifier B and physical machine identifier C.

[0090] In this embodiment, for each reference tag identifier corresponding to the target object identifier, a corresponding candidate physical machine is found, and the intersection of all candidate physical machines corresponding to all reference tag identifiers is taken as the target physical machine. It can be understood that each candidate physical machine corresponds to one or more scheduling policies of the target object. By taking the intersection of all candidate physical machines as the target physical machine, the target physical machine can satisfy each scheduling policy of the target object.

[0091] like Figure 4 As shown, the candidate physical machine identifier of the reference label identifier b of the target object 2 is physical machine identifier C, and the candidate physical machine identifiers of the reference label identifier c are physical machine identifier B and physical machine identifier C. Then, the intersection of the physical machine identifiers of the reference label identifier b and the reference label identifier c is taken to obtain the target physical machine identifier C. Then, physical machine C is taken as the target physical machine.

[0092] In this embodiment, by determining the first indication information corresponding to each reference tag identifier, the characteristics that the target object requires the physical machine to possess and the characteristics that it does not possess are determined. Through the physical machine tag relationship table, the physical machine identifiers of physical machines possessing the characteristics required by the target object are determined, as are the physical machine identifiers of physical machines that do not possess the characteristics required by the target object. By taking the intersection of the candidate physical machines, the target physical machine is determined to possess the characteristics required by the target object and not possess the characteristics that it does not possess. That is, the target physical machine conforms to the first scheduling strategy of the target object. Scheduling the target physical machine to execute the target task is simple and has low usage costs.

[0093] Based on the above embodiments, as an optional embodiment, the process of constructing the object label relationship table further includes:

[0094] Obtain a second scheduling policy applicable to all objects. The second scheduling policy is used to represent the requirements of any object on the physical machine's characteristics when using the physical machine.

[0095] The feature corresponding to the second scheduling strategy is used as a label, and a label identifier for the label is generated. A correspondence between the label identifier and the preset object identifier is established in the object label identifier table.

[0096] Obtaining reference label identification also includes:

[0097] At least one tag identifier corresponding to the preset object identifier is retrieved from the object tag relationship table and used as a reference tag identifier.

[0098] In this embodiment, the second scheduling strategy can be generated by business personnel to represent a common scheduling strategy, that is, the requirements of any object on the characteristics of the physical machine when using the physical machine. For example, the second scheduling strategy can be to require the physical machine for creating cloud services to be a multi-queue physical machine, then all objects must use a multi-queue physical machine when creating a cloud server.

[0099] Similar to the first scheduling strategy, the features corresponding to the second scheduling strategy are used as a label. For example, if the second scheduling request requires multiple queues for physical machines, the label represents multiple queues, and the label name can be "Multiple Queues," while the label identifier can be the label name. Simultaneously, a preset object identifier is set corresponding to this label identifier, so that it can be determined from the preset object identifier that the label identifier corresponds to each object. For example, the preset object identifier can be "default," or it can be a special symbol, such as "*." Therefore, the labels in this embodiment can be created individually for a single user or for all users.

[0100] In this embodiment, the reference label for the target object can also be obtained through a preset object identifier. By querying the object label relationship table, the label corresponding to the preset object identifier is used as the reference label for the target object.

[0101] like Figure 5 As shown, Figure 5 This is a schematic diagram of a process for obtaining a reference tag identifier according to an embodiment of this application. After receiving a scheduling request for target object 2, the reference tag identifier of target object 2 is queried from the object tag relationship table to obtain the target object identifier, i.e., object identifier 2. The tag identifiers corresponding to object identifier 2 include tag identifier b and tag identifier c. The tag identifier corresponding to the preset object identifier is tag identifier a. Therefore, the reference tag identifier of the target object includes tag identifier a, tag identifier b, and tag identifier c.

[0102] In this embodiment of the application, by obtaining the second scheduling strategy, a preset correspondence between object identifiers and tag identifiers is generated and stored in the object tag relationship table, so that when determining the target physical machine, not only the customer's requirements for the physical machine can be met, but also the business personnel's requirements for the physical machine can be met.

[0103] Based on the above embodiments, as an optional embodiment, the second scheduling strategy is used to represent the characteristics that any object requires the physical machine to have when using the physical machine, or the characteristics that it requires not to have.

[0104] The process of constructing the object label relationship table also includes:

[0105] Establish the correspondence between preset object identifiers, label identifiers, and primary indication information;

[0106] The target physics machine is determined based on the physics machine corresponding to each reference physics machine identifier, including:

[0107] For each reference label identifier, if the reference label identifier does not correspond to the target object identifier in the object label relationship table, then the first indication information in the object label relationship table that corresponds to both the reference label identifier and the preset object identifier is used as the target indication information; if the reference label identifier corresponds to the target object identifier in the object label relationship table, then the first indication information in the object label relationship table that corresponds to both the reference label identifier and the target object identifier is used as the target indication information.

[0108] For each reference tag identifier, if the target indication information of the reference tag identifier is used to indicate that the scheduling policy corresponding to the tag requires the physical machine to have the corresponding feature, then the physical machine is identified as the physical machine of the reference physical machine identifier corresponding to the reference tag identifier, and is used as the candidate physical machine corresponding to the reference tag identifier; if the target indication information of the reference tag identifier is used to indicate that the scheduling policy corresponding to the tag requires the physical machine to not have the corresponding feature, then the physical machine identifier is not the physical machine of the reference physical machine identifier corresponding to the reference tag identifier, and is used as the candidate physical machine corresponding to the reference tag identifier.

[0109] Take the intersection of all candidate physics machines corresponding to the reference labels, and use that as the target physics machine.

[0110] In this embodiment, the second scheduling strategy is used to represent the characteristics that any object requires the physical machine to possess, or the characteristics that the physical machine is not required to possess, when using the physical machine. To clearly display the specific second scheduling strategy in the object tag feature table, a correspondence between a preset object identifier, a tag identifier, and first indication information is established.

[0111] In this embodiment, the object label relationship table is generated based on a first scheduling strategy and a second scheduling strategy. Since the first scheduling strategy and the second scheduling strategy may have different requirements for the characteristics represented by the labels, for example, the first scheduling strategy requires the physical machine to have the characteristics represented by label 'a', while the second scheduling strategy requires the physical machine not to have the characteristics represented by label 'a', a contradiction arises when determining the target physical machine for the target object. Therefore, the following solution is formulated:

[0112] For each reference label identifier, query the object label relationship table to see if the reference label identifier corresponds to the target object identifier. If the reference label identifier does not correspond to the target object identifier, it means that the reference label identifier has a correspondence with the preset object identifier in the object label relationship table. In this case, the first indication information that corresponds to both the preset object identifier and the reference label identifier is used as the target indication information corresponding to the reference label identifier. If the reference label identifier corresponds to the target object identifier, the first indication information that corresponds to both the target object identifier and the reference label identifier is used as the target indication information corresponding to the reference label identifier.

[0113] like Figure 6 As shown, Figure 6An exemplary schematic diagram of another physical machine scheduling process provided in this application embodiment is shown. After receiving the scheduling request of target object 3, the reference tag identifier of target object 3 is obtained. Based on the target object identifier 3 and the preset object identifier, the reference tag identifier of target object 3 is obtained as tag identifier a, and tag identifier a corresponds to target object identifier 3. Then, the first indication information corresponding to both target object identifier 3 and tag identifier a is used as the target indication information, that is, the reference tag identifier of target object 3 is tag identifier a, and the target indication information of reference tag identifier a is 0.

[0114] As can be seen from the above embodiments, when the requirements of the first scheduling strategy and the second scheduling strategy for the same feature of the physical machine conflict, the target physical machine is determined according to the correspondence between the object identifier, the tag identifier and the first indication information generated by the first scheduling strategy.

[0115] In this embodiment, for each reference tag identifier of the target object, if the target indication information of the reference tag identifier is "require" or "1", indicating that the scheduling policy corresponding to the tag requires the physical machine to have the corresponding feature, then the physical machine identifier corresponding to the reference tag identifier is queried from the physical machine tag relationship table, and the physical machine corresponding to the reference physical machine identifier corresponding to the reference tag identifier is taken as a candidate physical machine. If the target indication information of the reference tag identifier is "reject" or "0", indicating that the scheduling policy corresponding to the tag does not require the physical machine to have the corresponding feature, then the physical machine identifier that does not correspond to the reference tag identifier is queried from the physical machine tag relationship table, and the physical machine corresponding to the physical machine identifier that does not correspond to the reference tag identifier is taken as a candidate physical machine corresponding to the reference tag identifier.

[0116] The target physical machine is obtained by taking the intersection of all candidate physical machines identified by the reference labels of the target object.

[0117] like Figure 6 As shown, after obtaining the reference tag identifier 'a' of target object 3, the physical machine tag relationship table is queried. The physical machine identifier corresponding to the reference tag identifier 'a' is physical machine identifier A. Therefore, the reference physical machine identifier of the reference tag identifier is physical machine identifier A. Since the target indication information of the reference tag identifier 'a' is 0, the candidate physical machine identifiers are physical machine identifiers other than the reference physical machine identifier, namely physical machine identifiers B and C. Because the reference tag identifier of target object 3 is only tag identifier 'a', the intersection of the candidate physical machines corresponding to the reference tag identifier of target object 3 is used to obtain physical machine B and physical machine C. Therefore, physical machine B can be used as the target physical machine, or physical machine C can be used as the target physical machine.

[0118] Based on the above embodiments, as an optional embodiment, any scheduling strategy is also used to indicate the application scenario, and the requirements for the physical machine characteristics are the requirements for the physical machine characteristics under the application scenario;

[0119] The process of constructing the object tag relationship table also includes: establishing the corresponding relationship between object identifiers, tag identifiers and application scenarios;

[0120] The scheduling request also includes the target application scenario and obtaining reference tag identifiers, including:

[0121] Retrieve at least one tag identifier from the object tag relationship table that corresponds to both the corresponding object identifier and the target application scenario, and use it as a reference tag identifier.

[0122] In this embodiment, considering that the requirements for physical machine characteristics may differ for an object in different application scenarios, for any of the first and second scheduling strategies, the scheduling strategy also includes the application scenario corresponding to the requirements for physical machine characteristics. The application scenario could be creating a cloud server or migrating a cloud server. For example, the scheduling strategy could require the physical machine creating the cloud server to have jumbo frame capabilities. To more clearly display the object's scheduling strategy in the object identifier relationship table, the construction of the object tag relationship table also includes establishing a correspondence between the corresponding object identifier, tag identifier, and application scenario. It should be understood that if the scheduling strategy is the first scheduling strategy, the corresponding object identifier is the object identifier of the object corresponding to the first scheduling strategy; if the scheduling strategy is the second scheduling strategy, the corresponding object identifier is the preset object identifier.

[0123] In this embodiment, the obtained scheduling strategy also includes a target application scenario. This involves querying the object tag relationship table for a tag identifier that corresponds to both the target object identifier and the target application scenario, and then querying the object tag relationship table for another tag identifier that corresponds to both the target object identifier and the target application scenario, using these as reference tag identifiers. Therefore, the application scenario corresponding to the reference tag identifier is consistent with the target application scenario corresponding to the scheduling request of the target object.

[0124] like Figure 7 As shown, Figure 7 This is a schematic diagram of another process for obtaining a reference tag identifier provided in an embodiment of this application. After receiving a scheduling request from target object 1, the application scenario 1 of target object 1 is obtained. The tag identifier corresponding to both object identifier 1 and application scenario 1 is used as the reference tag identifier. Typically, the tag identifier corresponding to both the preset tag identifier and application scenario 1 is used as the reference tag identifier. At this time, the reference tag identifier of target object 1 includes tag identifier a and tag identifier b.

[0125] In this embodiment of the application, a correspondence between the corresponding object identifier, tag identifier and application scenario is established in the object tag relationship table by the application scenario indicated by the scheduling strategy. This allows a tag identifier that corresponds to both the object identifier and the application scenario to be obtained based on the target application scenario in the scheduling request of the target object. Using this tag identifier as a reference tag identifier can better reflect the specific requirements of the target object for the physical machine characteristics, and make the physical machine obtained based on the reference tag identifier better meet the requirements of the target object.

[0126] Based on the above embodiments, as an optional embodiment, the feature is an attribute or capability;

[0127] The process of constructing the object label relationship table also includes:

[0128] Generate second indication information corresponding to each label, and establish a correspondence between object identifier, label identifier and second indication information in the object label relationship table; the second indication information corresponding to each label is used to describe the corresponding characteristics, attributes or capabilities, required by the scheduling strategy corresponding to the label for the physical machine.

[0129] The process of constructing the physical machine tag relationship table is as follows:

[0130] For any physical machine and any tag, based on the second indication information corresponding to the tag identifier of any tag in the object tag relationship table, obtain the features of any physical machine that correspond to the second indication information;

[0131] If any physical machine possesses the attribute or capability corresponding to the second indication information of the tag identifier in the object tag relationship table, then a correspondence between the physical machine identifier and the tag identifier is established in the physical machine tag relationship table.

[0132] In the embodiments of this application, the characteristics of the physical machine can be attributes or capabilities of the physical machine. For example, multi-queue is an attribute of the physical machine, and giant frame capability is a capability of the physical machine. The requirements for the characteristics of the physical machine can be divided into requirements for a certain attribute of the physical machine or requirements for a certain capability of the physical machine.

[0133] In this embodiment, the second indication information indicates whether the requirement for a physical machine's characteristics is an attribute requirement or a capability requirement. A correspondence between object identifiers, tag identifiers, and the second indication information is established in the object tag relationship table. In other words, the second indication information indicates whether the corresponding tag is an attribute or a capability. The second indication information can be "host" or "host_tag". When the second indication information is "host", it indicates that the tag corresponding to the second indication information is an attribute of the physical machine; when the second indication information is "host_tag", it indicates that the tag corresponding to the second indication information is a capability of the physical machine. As an optional embodiment, the second indication information can be "0" or "1". When the second indication information is "0", it indicates that the tag corresponding to the second indication information is an attribute of the physical machine; when the second indication information is "1", it indicates that the tag corresponding to the second indication information is a capability of the physical machine.

[0134] As an optional embodiment, the object tag relationship table may also include the tag creator, the reason for tag creation, the tag creation time, and remarks. The remarks include the application scenario. The tag and related information are generated according to any scheduling strategy and sent to the review server for review. When the review is approved, the object identifier, tag identifier, first instruction information, second instruction information, remarks, tag creator, tag creation reason, and tag creation time are stored in the object tag relationship table.

[0135] like Figure 8 As shown, Figure 8 This diagram illustrates the storage structure of an object tag relationship table provided in an embodiment of this application. As shown in the diagram, the storage structure of the object tag relationship table includes eight parts: user information, tag name, attitude, category, value, reason, operator, and time. The user information contains specific information about the user who formulates the scheduling strategy, representing the user responsible for the tag's effect. This information may include the first object identifier in this embodiment, and may also include customer identity information. If the scheduling strategy is a second scheduling strategy formulated by business personnel, then the user information is "default".

[0136] The label name is the name of the attribute or capability corresponding to the corresponding scheduling strategy. The attitude is the first indication information in this application embodiment, which is used to indicate when the corresponding object uses the physical machine. The require indicates that the physical machine is required to have the feature corresponding to the label, and the reject indicates that the physical machine is not required to have the feature corresponding to the label.

[0137] The category is the second indication information in this application embodiment. The host indicates that the feature represented by the tag is an attribute that the physical machine itself has. The host_tag indicates that the feature represented by the tag is a capability that the physical machine has as determined by business personnel.

[0138] The value is used to store remarks information, including the application scenarios in this application embodiment. It can also record the requirements of the corresponding object for other configuration information of the physical machine. All information in the remarks information can be stored in the form of a list.

[0139] The reason is the reason for creating the corresponding tag, such as "User 1 wants to create a cloud server with jumbo frame capability";

[0140] The operator is the information of the business personnel who generate the corresponding tags. It is important to understand that the user information is the information of the user who proposes the scheduling strategy, and the operator is the information of the business personnel who generate the tags for the user.

[0141] The time refers to the time when business personnel generate tags according to the scheduling strategy.

[0142] As can be seen from the storage structure of the object tag relationship table, a corresponding piece of information in the object tag relationship table not only includes the user's specific scheduling strategy, but also audit information such as the reason for creating the tag, the operator, and the time. This is beneficial because the corresponding information can be sent to the audit server for review before it is stored in the object tag relationship table. For example, the audit can check whether the operator has the authority to generate the corresponding information. Once the review is passed, the corresponding information is stored in the object tag relationship table, thereby improving the accuracy of the corresponding information in the object tag relationship table.

[0143] In this embodiment, the physical machine tag relationship table is constructed based on the second indication information of each tag. For any physical machine and any tag, to determine whether there is a correspondence between them, the second indication information corresponding to the tag is queried from the object tag relationship table. If the second indication information indicates that the tag is an attribute, then all attributes possessed by the physical machine are obtained. If the tag is included among all attributes possessed by the physical machine, then a correspondence is established between the physical machine identifier of the physical machine and the tag identifier of the tag. If the second indication information indicates that the tag is a capability, then all capabilities possessed by the physical machine are obtained. As an optional embodiment, business personnel can analyze the physical machine to obtain the capabilities possessed by the physical machine. If the capabilities possessed by the physical machine include the tag, then a correspondence is established between the physical machine identifier of the physical machine and the tag identifier of the tag.

[0144] As can be seen, the physical machine tag relationship table in this application embodiment is used to store the attributes or capabilities of each physical machine. When the physical machine identifier corresponds to the tag identifier, the physical machine corresponding to the physical machine identifier has the attributes or capabilities represented by the tag corresponding to the tag identifier.

[0145] In this embodiment, by establishing a correspondence between physical machine identifiers and tag identifiers, the attributes or capabilities of each physical machine are clearly defined. That is, by displaying the tags corresponding to the physical machines, it can be determined which attributes and capabilities each physical machine possesses. Therefore, constructing a physical machine identifier relationship table in this embodiment is equivalent to tagging each physical machine.

[0146] It's important to note that to provide users with suitable physical machines in a timely manner, business personnel can pre-assess the performance of each physical machine. If some physical machines are found to be faulty and unusable, or if business personnel do not want certain physical machines to be used by users during operation, they can create a second scheduling policy. Then, by generating tags based on the second scheduling policy, these faulty physical machines are tagged, establishing a correspondence between the physical machine identifier and the tag identifier. This ensures that physical machines with that tag are not selected when choosing a target physical machine for the user. For example, if the second scheduling policy requires that the physical machine to be used must not be unusable, then "unusable" corresponds to the tag and does not correspond to the first indication information. This establishes a correspondence between the "unusable" tag and unusable physical machines. Simultaneously, based on the first indication information, these unusable physical machines will not be selected for the user when choosing a physical machine.

[0147] In this embodiment, by establishing a correspondence between physical machine identifiers and tag identifiers, the attributes and capabilities of each physical machine are clearly defined. This allows for the rapid identification of candidate physical machines during application based on the reference tag identifier of the target object and the corresponding first indication information, improving the efficiency of target physical machine determination. Furthermore, for different users, different target physical machines are scheduled according to their different scheduling strategies, thereby achieving coarse-grained physical isolation.

[0148] like Figure 9a As shown, Figure 9a A schematic flowchart of another physical machine scheduling method provided in this application embodiment includes S901a-S906a:

[0149] Physical machine scheduling process:

[0150] S901a. Receive a scheduling request sent by the target object. The scheduling request is used to request the scheduling physical machine to execute the target task. The scheduling request includes the target object identifier of the target object.

[0151] S902a. Obtain the target application scenario from the scheduling request;

[0152] S903a. Use the tag identifier in the object tag relationship table that corresponds to both the target object identifier and the target application scenario as the reference tag identifier, or use the tag identifier that corresponds to both the preset object identifier and the target application scenario as the reference tag identifier.

[0153] S904a, For each reference label identifier of the target object, determine the target indication information of the reference label identifier;

[0154] S905a. For each reference tag identifier of the target object, a candidate physical machine is determined based on the physical machine tag relationship table, the reference tag identifier, and the target indication information.

[0155] S906a: Take the intersection of all candidate physical machines corresponding to the reference labels of the target object, and use it as the target physical machine.

[0156] like Figure 9b As shown, Figure 9b A schematic diagram illustrating the construction process of an object label relationship table provided in this application embodiment includes S901b-S907b:

[0157] S901b: Obtain the first scheduling strategy for each object, which represents the requirements of the corresponding object for the characteristics of the physical machine when using the physical machine;

[0158] S902b. For each first scheduling strategy, each feature corresponding to the first scheduling strategy is treated as a label, and a label identifier is generated for the label. A correspondence between the label identifier and the first object identifier of the corresponding object is established in the object label relationship table.

[0159] S903b: Generate the first indication information corresponding to each label, and establish the correspondence between the first object identifier, the label identifier, and the first indication information;

[0160] S904b: Obtain a second scheduling policy applicable to all objects, which represents the requirements of any object on the physical machine's characteristics when using the physical machine;

[0161] S905b: Take the feature corresponding to the second scheduling strategy as a label, generate the label identifier of the label, and establish the correspondence between the label identifier and the preset object identifier in the object label identifier table;

[0162] S906b. Establish the corresponding relationship between object identifiers, tag identifiers, and application scenarios;

[0163] S907b: Generate the second indication information corresponding to each label, and establish the correspondence between object identifier, label identifier and second indication information in the object label relationship table.

[0164] like Figure 9c As shown, Figure 9c A schematic diagram of the construction process of a physical machine tag relationship table provided in this application embodiment includes S901c-S902c:

[0165] S901c. For any physical machine and any tag, based on the second indication information corresponding to the tag identifier of any tag in the object tag relationship table, obtain the features of any physical machine that correspond to the second indication information.

[0166] S902c. If any physical machine possesses the attribute or capability corresponding to the second indication information corresponding to the tag identifier of any tag in the object tag relationship table, then establish a correspondence between the physical machine identifier and the tag identifier in the physical machine tag relationship table.

[0167] like Figure 10 As shown, Figure 10 An exemplary schematic diagram of another physical machine scheduling process provided in an embodiment of this application is illustrated. For example... Figure 10 As shown, the physical machine scheduling method provided in this application embodiment can be applied to the scheduling system in the field of cloud computing. The scheduling system receives the user's scheduling request through API, determines a physical machine from a large number of physical machines, and performs the corresponding task for the user, such as creating a cloud server. After determining the physical machine to be scheduled, resources are deducted from the physical machine resource database.

[0168] To improve the efficiency of the scheduling system in selecting physical machines, a correspondence between user scheduling policies, tags, and physical machines is established. Specifically, this includes the table generation process S1a-S4a and the scheduling process S1b-S4b. The table generation process includes S1a, obtaining the user's scheduling policies, such as three scheduling policies: scheduling policy 1, scheduling policy 2, and scheduling policy 3; S2a, generating tags for each scheduling policy, resulting in tag 1, tag 2, and tag 3; S3a, storing each tag in the tag definition configuration table according to the storage structure of the object tag relationship table, where the tag definition configuration table is the object tag relationship table in this embodiment; and S4a, affixing tags to the physical machines, thus constructing the physical machine tag relationship table. It should be noted that S4a can be performed before or after S3a. The scheduling process includes S1b, accepting the user's scheduling request, S2b, querying the user's specific scheduling policy based on the corresponding information in the label definition configuration table according to the object information in the scheduling request, querying the labels required for the physical machine and the labels required not to be possessed by the physical machine according to the user's scheduling policy, and S4b, determining the physical machine based on the label corresponding to the physical machine.

[0169] This application provides a physical machine scheduling device, such as... Figure 11 As shown, the physical machine scheduling device may include: a receiving module 1101, an obtaining module 1102, a querying module 1103, and a scheduling module 1104, wherein,

[0170] The receiving module 1101 is used to receive a scheduling request sent by the target object. The scheduling request is used to request the scheduling physical machine to execute the target task. The scheduling request includes the target object identifier of the target object.

[0171] The module 1102 is used to obtain a reference tag identifier, which includes at least one tag identifier corresponding to the target object identifier, queried from the object tag relationship table. Each tag is used to represent a feature of the physical machine. The object tag relationship table includes the correspondence between object identifiers and tag identifiers.

[0172] The query module 1103 is used to query at least one reference physical machine identifier corresponding to the reference tag identifier from the physical machine tag relationship table, and determine the target physical machine according to the physical machine corresponding to each reference physical machine identifier. The physical machine tag relationship table includes the correspondence between physical machine identifiers and tag identifiers.

[0173] The scheduling module 1104 is used to schedule the target physical machine to execute the target task.

[0174] This application provides an electronic device, including a memory, a processor, and a computer program stored in the memory. The processor executes the computer program to implement the steps of a physical machine scheduling method. Compared with related technologies, this method can achieve the following: by receiving a scheduling request sent by a target object, obtaining a target object identifier, and obtaining a corresponding reference tag identifier based on the target object identifier; by using the tag identifier corresponding to the target object identifier in the object tag relationship table as a reference tag identifier, where the tag represents the characteristics of the physical machine, obtaining the physical machine characteristics corresponding to the target object; by querying the physical machine tag relationship table for a reference physical machine identifier corresponding to the reference tag identifier, obtaining the corresponding reference physical machine identifier based on the physical machine characteristics corresponding to the target object; by using each reference physical machine identifier, determining the target physical machine, so that the target physical machine can correspond to the characteristics of the physical machine corresponding to the target object; by setting the object tag relationship table and the physical machine tag relationship table, a correspondence between the target object, the tag, and the physical machine is established, thereby enabling the timely determination of the target physical machine for the target object after receiving the scheduling request from the target object, based on the correspondence between the target object, the tag, and the physical machine, and scheduling the target physical machine to execute the target task in the scheduling request, thus improving the efficiency of the physical machine scheduling process.

[0175] In one alternative embodiment, an electronic device is provided, such as Figure 12 As shown, Figure 12 The illustrated electronic device 4000 includes a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, for example, via a bus 4002. Optionally, the electronic device 4000 may further include a transceiver 4004, which can be used for data interaction between the electronic device and other electronic devices, such as sending and / or receiving data. It should be noted that in practical applications, the transceiver 4004 is not limited to one type, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of this application.

[0176] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 4001 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0177] Bus 4002 may include a pathway for transmitting information between the aforementioned components. Bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Bus 4002 can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the figure, but this does not indicate that there is only one bus or one type of bus.

[0178] The memory 4003 may be ROM (Read Only Memory) or other types of static storage devices capable of storing static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices capable of storing information and instructions, or EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, other magnetic storage devices, or any other medium capable of carrying or storing computer programs and capable of being read by a computer, without limitation herein.

[0179] The memory 4003 stores computer programs that execute embodiments of this application, and its execution is controlled by the processor 4001. The processor 4001 executes the computer programs stored in the memory 4003 to implement the steps shown in the foregoing method embodiments.

[0180] The electronic device package may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital radio receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), and in-vehicle terminals (such as in-vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. Figure 12 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments disclosed herein.

[0181] This application provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it can implement the steps and corresponding content of the aforementioned method embodiments. Compared with existing technologies, this method achieves the following: By receiving a scheduling request from a target object, the target object identifier is obtained, enabling the retrieval of a corresponding reference tag identifier. By using the tag identifier corresponding to the target object identifier in the object tag relationship table as the reference tag identifier, and using the tag to represent the physical machine's characteristics, the physical machine characteristics corresponding to the target object are obtained. By querying the physical machine tag relationship table for the reference physical machine identifier corresponding to the reference tag identifier, the corresponding reference physical machine identifier is obtained based on the physical machine characteristics corresponding to the target object. The target physical machine is determined using each reference physical machine identifier, ensuring that the target physical machine corresponds to the physical machine characteristics of the target object. By setting up the object tag relationship table and the physical machine tag relationship table, a correspondence between the target object, tags, and physical machines is established. This allows for timely determination of the target physical machine for the target object upon receiving a scheduling request, based on the correspondence between the target object, tags, and physical machines, and scheduling the target physical machine to execute the target task in the scheduling request, thus improving the efficiency of the physical machine scheduling process.

[0182] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium, a computer-readable medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0183] This application also provides a computer program product, including a computer program that, when executed by a processor, can implement the steps and corresponding content of the aforementioned method embodiments. Compared with the prior art, it can achieve the following: by receiving a scheduling request sent by a target object, obtaining a target object identifier, so as to obtain a corresponding reference tag identifier based on the target object identifier; by using the tag identifier corresponding to the target object identifier in the object tag relationship table as a reference tag identifier, and the tag is used to represent the characteristics of the physical machine, so as to obtain the physical machine characteristics corresponding to the target object; by querying the reference physical machine identifier corresponding to the reference tag identifier in the physical machine tag relationship table, so as to obtain the corresponding reference physical machine identifier based on the physical machine characteristics corresponding to the target object; by using each reference physical machine identifier, determining the target physical machine, so that the target physical machine can correspond to the characteristics of the physical machine corresponding to the target object; by setting the object tag relationship table and the physical machine tag relationship table, a correspondence between the target object, the tag, and the physical machine is established, so that after receiving the scheduling request of the target object, the target physical machine can be determined for the target object in a timely manner according to the correspondence between the target object, the tag, and the physical machine, and the target physical machine can be scheduled to execute the target task in the scheduling request, thereby improving the efficiency of the physical machine scheduling process.

[0184] The terms "first," "second," "third," "fourth," "1," "2," etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in a sequence other than that shown in the figures or text.

[0185] It should be understood that although arrows indicate various operation steps in the flowcharts of this application's embodiments, the order in which these steps are implemented is not limited to the order indicated by the arrows. Unless explicitly stated herein, in some implementation scenarios of this application's embodiments, the implementation steps in each flowchart can be executed in other orders as required. Furthermore, some or all steps in each flowchart, based on the actual implementation scenario, may include multiple sub-steps or multiple stages. Some or all of these sub-steps or stages can be executed at the same time, and each sub-step or stage can also be executed at different times. In scenarios where execution times differ, the execution order of these sub-steps or stages can be flexibly configured according to requirements, and this application's embodiments do not limit this.

[0186] The above description is only an optional implementation method for some implementation scenarios of this application. It should be noted that for those skilled in the art, other similar implementation methods based on the technical concept of this application without departing from the technical concept of this application also fall within the protection scope of the embodiments of this application.

Claims

1. A physical machine scheduling method, characterized in that, include: Receive a scheduling request sent by the target object, the scheduling request being used to request the scheduling physical machine to execute the target task, the scheduling request including the target object identifier of the target object; Obtain a reference tag identifier, which includes at least one tag identifier corresponding to the target object identifier, queried from an object tag relationship table. Each tag is used to represent a feature of the physical machine. The object tag relationship table includes the correspondence between object identifiers and tag identifiers. The physical machine tag relationship table is used to query at least one reference physical machine identifier corresponding to the reference tag identifier. The target physical machine is determined based on the physical machine corresponding to each reference physical machine identifier. The physical machine tag relationship table includes the correspondence between physical machine identifiers and tag identifiers. The target physical machine is scheduled to execute the target task.

2. The method according to claim 1, characterized in that, The process of constructing the object label relationship table includes: Obtain the first scheduling policy for each object, where the first scheduling policy represents the requirements of the corresponding object for the characteristics of the physical machine when using the physical machine. For each first scheduling strategy, each feature corresponding to the first scheduling strategy is taken as a label, and a label identifier of the label is generated. A correspondence between the label identifier and the first object identifier of the corresponding object is established in the object label relationship table.

3. The method according to claim 2, characterized in that, The first scheduling strategy is used to represent the characteristics that the corresponding object requires the physical machine to have when using the physical machine, or the characteristics that the physical machine is required not to have; The process of constructing the object label relationship table also includes: Generate first indication information corresponding to each tag, and establish a correspondence between the first object identifier, the tag identifier, and the first indication information; the first indication information corresponding to each tag is used to indicate whether the scheduling strategy corresponding to the tag requires the physical machine to have the corresponding feature, or requires the physical machine not to have the corresponding feature.

4. The method according to claim 3, characterized in that, The step of determining the target physical machine based on the physical machine corresponding to each reference physical machine identifier includes: For each reference tag identifier, if the first indication information corresponding to the reference tag identifier in the object tag relationship table is used to indicate that the scheduling strategy corresponding to the tag requires the physical machine to have the corresponding characteristics, then the physical machine is identified as the physical machine of the reference physical machine identifier corresponding to the reference tag identifier, and is used as the candidate physical machine corresponding to the reference tag identifier; For each reference tag identifier, if the first indication information corresponding to the reference tag identifier in the object tag relationship table is used to indicate that the scheduling strategy corresponding to the tag requires the physical machine to not have the corresponding feature, then the physical machine whose physical machine identifier is not the reference physical machine identifier corresponding to the reference tag identifier is taken as the candidate physical machine corresponding to the reference tag identifier. The intersection of all candidate physics machines corresponding to the reference labels is taken as the target physics machine.

5. The method according to claim 3, characterized in that, The process of constructing the object label relationship table also includes: Obtain a second scheduling policy applicable to all objects, the second scheduling policy being used to represent the requirements of any object on the physical machine's characteristics when using the physical machine; The feature corresponding to the second scheduling strategy is used as a label, and a label identifier of the label is generated. A correspondence between the label identifier and the preset object identifier is established in the object label identifier table. Obtaining the reference label identifier further includes: At least one tag identifier corresponding to the preset object identifier is retrieved from the object tag relationship table and used as a reference tag identifier.

6. The method according to claim 5, characterized in that, The second scheduling strategy is used to represent the characteristics that any object requires the physical machine to have, or the characteristics that it is required not to have, when using the physical machine; The process of constructing the object label relationship table also includes: Establish the correspondence between preset object identifiers, label identifiers, and primary indication information; The step of determining the target physical machine based on the physical machine corresponding to each reference physical machine identifier includes: For each reference tag identifier, if the reference tag identifier does not correspond to the target object identifier in the object tag relationship table, then the first indication information in the object tag relationship table that corresponds to both the reference tag identifier and the preset object identifier is used as the target indication information; if the reference tag identifier corresponds to the target object identifier in the object tag relationship table, then the first indication information in the object tag relationship table that corresponds to both the reference tag identifier and the target object identifier is used as the target indication information. For each reference tag identifier, if the target indication information of the reference tag identifier is used to indicate that the scheduling policy corresponding to the tag requires the physical machine to have the corresponding feature, then the physical machine is identified as the physical machine of the reference physical machine identifier corresponding to the reference tag identifier, and is used as the candidate physical machine corresponding to the reference tag identifier; if the target indication information of the reference tag identifier is used to indicate that the scheduling policy corresponding to the tag requires the physical machine not to have the corresponding feature, then the physical machine is identified as a physical machine that is not the reference physical machine identifier corresponding to the reference tag identifier, and is used as the candidate physical machine corresponding to the reference tag identifier. The intersection of all candidate physics machines corresponding to the reference labels is taken as the target physics machine.

7. The method according to any one of claims 6, characterized in that, Any scheduling strategy is also used to indicate the application scenario, and the requirements for the physical machine characteristics are the requirements for the physical machine characteristics under the application scenario; The process of constructing the object tag relationship table also includes: establishing the corresponding relationship between object identifiers, tag identifiers and application scenarios; The scheduling request also includes the target application scenario, and obtaining the reference tag identifier includes: Query at least one tag identifier that corresponds to both the corresponding object identifier and the target application scenario from the object tag relationship table, and use it as a reference tag identifier.

8. The method according to any one of claims 1-7, characterized in that, The feature is an attribute or capability; The process of constructing the object label relationship table also includes: Generate second indication information corresponding to each tag, and establish a correspondence between object identifier, tag identifier and second indication information in the object tag relationship table; the second indication information corresponding to each tag is used to describe the corresponding characteristic or capability that the physical machine is required to possess by the scheduling strategy corresponding to the tag. The process of constructing the physical machine tag relationship table is as follows: For any physical machine and any tag, based on the second indication information corresponding to the tag identifier of any tag in the object tag relationship table, the features of any physical machine corresponding to the second indication information are obtained; If any physical machine possesses the attribute or capability corresponding to the second indication information of the tag identifier of any tag in the object tag relationship table, then a correspondence between the physical machine identifier and the tag identifier is established in the physical machine tag relationship table.

9. A physical machine scheduling device, characterized in that, include: A receiving module is used to receive a scheduling request sent by a target object. The scheduling request is used to request a physical machine to execute a target task. The scheduling request includes the target object identifier of the target object. The module is used to obtain a reference tag identifier, which includes at least one tag identifier corresponding to the target object identifier, queried from an object tag relationship table. Each tag is used to represent a feature of the physical machine. The object tag relationship table includes the correspondence between object identifiers and tag identifiers. The query module is used to query at least one reference physical machine identifier corresponding to the reference tag identifier from the physical machine tag relationship table, and determine the target physical machine based on the physical machine corresponding to each reference physical machine identifier. The physical machine tag relationship table includes the correspondence between physical machine identifiers and tag identifiers. The scheduling module is used to schedule the target physical machine to execute the target task.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory, characterized in that, The processor executes the computer program to implement the steps of the method according to any one of claims 1-8.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1-8.

12. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1-8.

Images