Resource management and control method and device, and storage medium

Abstract

Provided in the embodiments of the present disclosure are a resource management and control method and device, and a storage medium. The method comprises: respectively monitoring the resource state of a specified type of resources on a target physical host, and the resource state of a target type of resources that the specified type of resources is required to match; if the monitored resource states do not meet specification guarantee requirements set for the specified type of resources, selecting a target instance from among instances on the target physical host that occupy the target type of resources; and migrating the target instance out of the target physical host. In this way, by means of resource management and control, resource replenishment can be performed on a target type of resources on a target physical host in a timely manner, such that a situation wherein a specified type of resources are necessarily left unused due to the remaining quantity of the specified type of resources being sufficient and the remaining quantity of the target type of resources that the specified type of resources is required to match being insufficient is avoided, thereby effectively increasing the utilization rate of the specified type of resources, and ensuring that various instances that need to occupy the specified type of resources can be created in a more timely manner.

Description

Resource management method, device and storage medium

[0001] This disclosure claims priority to the Chinese patent application filed with the China Patent Office on September 28, 2023, with application number 2023112892174 and application name “A Resource Management Method, Device and Storage Medium,” the entire contents of which are incorporated by reference into this disclosure. Technical Field

[0002] The present disclosure relates to the field of cloud computing technology, and in particular to a resource management method, device, and storage medium. Background Art

[0003] Hybrid deployment allows multiple instances of different types to coexist on the same physical host. Different instances may require different resource types and specifications.

[0004] Currently, in hybrid deployment solutions, idle resources often occur, resulting in a waste of physical resources, especially scarce resources such as GPUs (Graphics Processing Units). Idle resources will lead to high cost losses.

[0005] Summary of the Invention

[0006] Various aspects of the present disclosure provide a resource management method, device, and storage medium to improve resource utilization on a physical host.

[0007] The present disclosure provides a resource management method, including:

[0008] Monitor the resource status of the specified type of resources and the target type of resources they need to match on the target physical host respectively;

[0009] If the monitored resource status does not meet the specification guarantee requirement set for the specified type of resource, selecting a target instance from the instances occupying the target type of resource on the target physical host;

[0010] The target instance is migrated from the target physical host so that the resource states of the designated type resources and the target type resources in the target physical host meet the specification guarantee requirement.

[0011] The embodiment of the present disclosure also provides a management and control device, including a memory, a processor, and a communication component;

[0012] The memory is used to store one or more computer instructions;

[0013] The processor is coupled to the memory and the communication component, and is configured to execute the one or more computer instructions to implement the aforementioned resource management method.

[0014] The embodiment of the present disclosure further provides a physical host, including a memory, a processor, and a communication component, wherein the physical host provides resources of a specified type and resources of a target type and carries one or more instances;

[0015] The memory is used to store one or more computer instructions;

[0016] The processor is coupled to the memory and the communication component and is configured to execute the one or more computer instructions for:

[0017] Monitoring the resource status of the designated type of resource and the target type of resource required for collocation;

[0018] If the monitored resource status does not meet the specification guarantee requirements set for the specified type of resource, a target instance is selected from instances occupying the target type of resource;

[0019] The target instance is migrated out so that the resource states of the designated type resource and the target type resource meet the specification guarantee requirement.

[0020] The embodiment of the present disclosure further provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed by one or more processors, the one or more processors are caused to execute the aforementioned resource management method.

[0021] An embodiment of the present disclosure provides a computer program product, including a computer program, which implements the method described in any one of the above aspects when executed by a processor.

[0022] In the disclosed embodiment, the resource status of the specified type of resource and the target type of resource required to be matched on the target physical host can be monitored separately; if the monitored resource status does not meet the specification guarantee requirements set for the specified type of resource, the target instance is selected from the instances occupying the target type of resource on the target physical host; the target instance is migrated from the target physical host so that the resource status of the specified type of resource and the target type of resource in the target physical host meet the specification guarantee requirements. In this way, the target type of resource on the target physical host can be replenished in a timely manner through resource management and control, avoiding the situation where the remaining amount of the specified type of resource is sufficient, but the remaining amount of the target type of resource required to be matched is insufficient, resulting in the specified type of resource having to be idle, thereby effectively improving the utilization rate of the specified type of resource and ensuring that various instances that need to occupy the specified type of resource can be created more promptly. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The drawings described herein are used to provide a further understanding of the present disclosure and constitute a part of the present disclosure. The exemplary embodiments of the present disclosure and their descriptions are used to explain the present disclosure and do not constitute an improper limitation of the present disclosure. In the drawings:

[0024] FIG1 is a logical diagram of a resource management method provided by an exemplary embodiment of the present disclosure;

[0025] FIG2 is a flow chart of a resource management method provided by an exemplary embodiment of the present disclosure;

[0026] FIG3 is a flow chart of a resource management method provided by another exemplary embodiment of the present disclosure;

[0027] FIG4 is a flow chart of a resource management method provided by another exemplary embodiment of the present disclosure;

[0028] Figures 5a and 5b are schematic diagrams of an exemplary application scenario provided by the present disclosure;

[0029] FIG6 is a schematic structural diagram of a management and control device provided by an exemplary embodiment of the present disclosure;

[0030] FIG7 is a schematic structural diagram of a physical host provided by yet another exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0031] To make the objectives, technical solutions, and advantages of the present disclosure more clear, the technical solutions of the present disclosure will be clearly and completely described below in conjunction with the specific embodiments of the present disclosure and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present disclosure.

[0032] Before describing in detail the technical solutions provided by the various embodiments of the present disclosure, several technical concepts involved in the present disclosure are briefly described as follows.

[0033] A physical host, also known as a physical server, is a physical machine hardware facility that includes independent resources such as CPU, memory, and disk. Combined with the deployment of the software environment, the physical host provides various basic resources for instances and serves as the instance runtime environment.

[0034] A cloud instance is the foundation of cloud computing, used to provide computing services. It represents a simulated server and can include basic computing components such as the CPU, memory, operating system, network, and disk. Cloud instances can include virtual machines and containers.

[0035] Instance products: Instances are categorized based on their performance, price, configuration, and other characteristics to meet different customer usage scenarios.

[0036] Instance specifications: The specifications of the various physical resources required by the instance, such as the number of CPU cores or memory capacity required.

[0037] Hybrid deployment: Within the same hardware and software environment, a single physical host can support the coexistence of multiple instance products. Hybrid deployment primarily involves two aspects of hybridization: the physical resources provided by the physical host must be diverse; and the instance types supported on the physical host can be diverse, while the types of physical resources required by different instances may vary. For example, a physical host can provide both CPU and GPU resources and support the deployment of both GPU and CPU instances, although GPU and CPU instances require different types of resources.

[0038] During the research process, the inventors discovered that creating or releasing instances on a physical host will cause the resource status on the physical host to change. However, in many cases, the resource status on the physical host can no longer meet the specification requirements of the relevant instances. On the one hand, this will cause some of the remaining resources to become fragmented resources, which will be idle for a long period of time, resulting in resource waste; on the other hand, instances of relevant specifications may not be delivered on time due to the inability to find qualified physical hosts, resulting in untimely instance delivery. To this end, this embodiment proposes a resource management and control solution for managing fragmented resources on the physical host to improve resource utilization in the physical host.

[0039] Figure 1 is a logical diagram of a resource management method provided by an exemplary embodiment of the present disclosure. Referring to Figure 1 , the resource management method provided by this embodiment can be executed by a management and control device, which can be implemented as software, hardware, or a combination of software and hardware. The management device can be integrated into a management and control device.

[0040] The control device in this embodiment can be an existing control node used in cloud computing technology to control physical hosts. By modifying the existing control node, it can be enabled to execute the resource control method provided in this embodiment. In other words, a new control module can be added to the existing control node to execute the resource control method provided in this embodiment. Of course, the control device in this embodiment can also be an independent device unrelated to the existing control node. In this case, the control device in this embodiment can communicate with each deployed physical host to control the resources in each physical host.

[0041] In this embodiment, the types and amounts of physical resources included in different physical hosts may vary, and are not limited here.

[0042] During research, the inventors discovered that instance specifications typically specify a variety of resource types. Consequently, various types of resources within a physical host often need to be sold in combination to match the instance specifications. To address this, this embodiment proposes setting specification guarantee requirements for specific resource types and, through resource management, ensuring that specific resource types on the physical host meet these guarantee requirements, thereby avoiding the aforementioned fragmentation of specific resource types.

[0043] The specification guarantee requirements in this embodiment are used to ensure that the specified type of resources and target type of resources on the physical host can meet the specified specification requirements. The resource management method provided in this embodiment proposes to use resource management to ensure that the specified type of resources and target type of resources on the physical host can meet the specification guarantee requirements, thereby addressing the fragmentation problem of the specified type of resources on the physical host.

[0044] FIG2 is a flow chart of a resource management method provided by an exemplary embodiment of the present disclosure. Referring to FIG2 , the method may include:

[0045] Step 200: monitor the resource status of the specified type of resources and the target type of resources required to be matched on the target physical host respectively;

[0046] Step 201: If the monitored resource status does not meet the specification guarantee requirements set for the specified type of resource, a target instance is selected from the instances occupying the target type of resource on the target physical host;

[0047] Step 202: Migrate the target instance from the target physical host so that the resource states of the designated type resources and target type resources in the target physical host meet the specification assurance requirements.

[0048] In this embodiment, the timing of resource control by the control device on the target physical host is not limited. For example, the control device may periodically control the resources of the target physical host. Alternatively, the control device may be triggered manually or at a specified time to trigger resource control on the target physical host. During each round of resource control, the control device may implement steps 200 to 202 to manage resource fragmentation on the target physical host.

[0049] Among them, the designated type of resources in this embodiment can be any type of physical resource that needs to be fragmented. The designated type of resources in this embodiment can include but are not limited to GPU resources and local storage resources, etc., of course, it can also be other types of resources, such as CPU resources, memory resources or communication resources. In actual applications, resources such as GPU resources and local storage resources are relatively scarce and the cost is relatively high. Therefore, according to the resource management method provided in this embodiment, fragmentation management of these scarce resources can obtain more obvious effects and benefits. Of course, according to the resource management method provided in this embodiment, fragmentation management of other types of resources can also obtain effects and benefits. In this embodiment, there is no limitation on the designated type of resources.

[0050] As mentioned above, the resource management method provided in this embodiment can be executed by a management and control device. In step 200, the management and control device can monitor the resource status of the specified type of resources and the target type of resources required for matching on the target physical host. The target physical host can be any physical host that may experience resource fragmentation of the specified type.

[0051] In this embodiment, the resource status can be used to represent the resource usage. In this embodiment, the representation dimension used in the resource status is not limited. For example, the occupied amount can be used as the representation dimension, or the remaining amount can be used as the representation dimension.

[0052] Among them, for a specified type of resource, there may be one or more resources that need to be matched. For example, for GPU resources, the resources that need to be matched may include CPU resources or memory resources, etc. For a specified type of resource, the type of resource that needs to be matched is usually affected by the resource occupation requirements of the relevant instance. It is worth noting that in actual applications, the target type that needs to be paid attention to in step 200 may be pre-specified for the specified type of resource, and the target type may be all resource types or part of the resource types that need to be matched with the specified type of resource. For example, the resources that need to be matched with GPU resources include CPU resources, memory resources, communication resources and network disk resources. In this embodiment, only CPU resources can be used as the target type resource that needs to be paid attention to in step 200. This is because in actual applications, many types of resources on the physical host are usually very sufficient or can be time-shared and reused. Even if they need to be matched with specified type resources, it will not cause fragmentation problems of specified type resources. Therefore, there is no need to pay attention to it.

[0053] In addition, in step 200, various implementations may be used to monitor the resource status of the specified type of resources and the target type of resources required to be matched on the target physical host.

[0054] In an optional implementation method: the target machine model corresponding to the target physical host can be determined; the resource configuration information associated with the target machine model can be queried to determine the total amount of resources corresponding to the specified type of resources and the target type of resources on the target physical host; the usage of the specified type of resources and / or the target type of resources by each instance scheduled to the target physical host can be monitored to characterize the resource status.

[0055] In this implementation, the occupied amount is used as the representation dimension of the resource status. Resource configuration information can be recorded separately for different models. The resource configuration information may include resource types and the total amount of resources corresponding to each type of resource. It should be understood that physical hosts of the same model are consistent in resource configuration. Therefore, after determining the target model corresponding to the target physical host, the control device can query the resource configuration information associated with the target model to determine the total amount of resources corresponding to the specified type of resources and the target type of resources on the target physical host.

[0056] In addition, in this implementation, the control device can perform instance scheduling, that is, the control device can receive an instance creation request and schedule the instance creation request to a suitable physical host to control the hit physical host to respond to the instance creation request and create the required instance. Usually, the instance creation request will specify the required instance specifications, so that the control device can monitor the instance's occupancy of related resources from the received instance creation request. Accordingly, for the target physical host, the control device can monitor the occupancy of the specified type of resources and / or target type of resources by each instance scheduled to the target physical host, thereby calculating the corresponding occupied amount of the specified type of resources and target type of resources on the target physical host.

[0057] In this implementation, the management and control device can accurately monitor the resource status of the specified type of resources and the target type of resources required to match them on the target physical host without the target physical host being aware of them, providing a processing basis for subsequent resource management and control steps.

[0058] It should be understood that the above implementation is illustrative only. Other implementations can be used in this embodiment to monitor the resource status of a specified type of resource and its corresponding target type of resource on the target physical host, and the present invention is not limited thereto. For example, the target physical host can proactively report the remaining amount of the specified type of resource and the target type of resource to the control device. In this way, the remaining amount can be used as a dimension to represent the resource status.

[0059] Continuing with reference to FIG2 , in step 201 , it is determined whether the resource status monitored in step 200 meets the specification guarantee requirements set for the specified type of resource. If not, a target instance is selected from instances occupying target type resources on the target physical host.

[0060] Here, it is proposed to use the resource status monitored in step 200 as a reference basis to evaluate whether a fragmentation problem currently exists in the designated type of resources on the target physical host.

[0061] Considering that the essence of the fragmentation problem is the problem of unreasonable resource surplus, this embodiment proposes that in step 201, the surplus of the specified type of resources and the surplus of the target type of resources can be determined based on the respective resource states of the specified type of resources and the target type of resources; if the surplus of the specified type of resources and the surplus of the target type of resources do not meet the specification guarantee requirements, it is determined that the monitored resource state does not meet the specification guarantee requirements. Among them, the specification guarantee requirements may include the specification relationship specified for the specified type of resources and the target type of resources. The specification relationship in this embodiment can be represented by the ratio between the resource amount of the specified type of resources and the resource amount of the target type of resources, or can be represented by the numerical values ​​corresponding to the resource amount of the specified type of resources and the resource amount of the target type of resources.

[0062] In step 201, specification assurance requirements corresponding to the specified type of resources can be set separately on the physical hosts containing the specified type of resources. Moreover, the specification assurance requirements set for the specified type of resources on different physical hosts may not be exactly the same. The specification assurance requirements set for the specified type of resources are affected by the instance types supported by the target physical host. To this end, in an exemplary setting scheme provided in this embodiment, appropriate specification assurance requirements can be set for the specified type of resources by referring to the resource specification information required for each type of instance supported by the target physical host.

[0063] Specifically, in this exemplary setting scheme: the resource specification information required for each type of instance that needs to occupy a specified type of resource and is supported for deployment on the target physical host can be obtained; from the obtained resource specification information, the specification relationship between the required specified type of resource and the target type of resource is parsed respectively; from the parsed specification relationship, the target specification relationship is selected to set the specification guarantee requirements corresponding to the specified type of resource.

[0064] In this exemplary setting scheme, resource specification information is maintained for each type of instance. The resource specification information can record the resource type required by the instance and the amount of resources required under each type of resource. In addition, the supported instance types for deployment can be maintained for each physical host. In this way, the management and control device can first determine which types of instances supported for deployment on the target physical host need to occupy the specified type of resources. After that, the resource specification information required by each of these types of instances can be queried, and based on the amount of resources required under the specified type of resources and the target type of resources recorded in the resource specification information, the specification relationship between the specified type of resources and the target type of resources required by each of these types of instances can be parsed.

[0065] Based on this, in this exemplary setup, the control device can select an appropriate target specification relationship from the previously analyzed specification relationships to set the specification assurance requirements for the specified resource type. Preferably, the specification relationship can be characterized by the resource quantity ratio between the specified resource type and the target resource type. Based on this, the minimum of these ratios can be selected as the target ratio. Accordingly, the specification assurance requirement can be designed to ensure that the remaining quantity ratio is less than or equal to this target ratio.

[0066] For example, the target physical server supports deploying Class A, Class B, and Class C instances, all of which require GPU resources. By querying the resource specifications required by each of these three instance types, we can determine that the required specification ratio for Class A instances is GPU:CPU = 1:8; for Class B instances, GPU:CPU = 1:4; and for Class C instances, GPU:CPU = 1:16. Based on this, the required GPU:CPU ratio of 1:16 for Class C instances can be used as the target specification ratio, and the guaranteed specification requirement can be designed to ensure that the remaining resources on the target physical host are sufficient to support the build of all instances requiring the specified resource types. In particular, instances requiring the largest resource requirements for the target resource type can be built on the target physical host in a timely manner, eliminating the problem of delayed builds due to insufficient resources.

[0067] During the research process, the inventors found that the specification guarantee requirements set according to the above preferred method can achieve very good fragmentation management effects when managing and controlling the specified type of resources on the target physical host, and almost no fragmentation problems will occur. However, it should be understood that in this exemplary design scheme, other values ​​can also be selected as target ratios from the resource quantity ratios analyzed above, for example, the middle value, the minimum value, etc., and this is not limited here. However, when different values ​​are selected, there are slight differences in the fragmentation management effects that can be obtained, but they can all improve the fragmentation problem of the specified type of resources on the target physical host.

[0068] It is also worth noting that other design solutions can be used in this embodiment to set specification assurance requirements for specified resource types on the target physical host, and are not limited to the exemplary setting solution described above. For example, a ratio threshold value can be set for the specified resource type in the specification assurance requirement based on experience, and the specification assurance requirement can be designed to ensure that the remaining quantity ratio monitored in step 200 is less than or equal to the ratio threshold value. Further design solution examples are not provided here.

[0069] If it is determined that the resource status monitored in step 200 does not meet the specification guarantee requirements based on the set specification guarantee requirements, the target instance can be selected from the instances occupying the target type resources on the target physical host according to the preset migration strategy for migration.

[0070] In step 201 , considering that migrating instances that do not occupy target type resources will not bring any resource replenishment effect to target type resources in the target physical host, it is proposed to select a target instance from instances that occupy target type resources.

[0071] The migration strategy that can be adopted in step 201 will be described in detail later, and this embodiment does not limit this.

[0072] Continuing with Figure 2 , in step 202, the target instance may be migrated from the target physical host so that the remaining amount of target type resources on the target physical host meets the specification guarantee requirements. In this embodiment, after the target instance is migrated, a portion of the target type resources on the target physical host may be released to replenish the target type resources on the target physical host. This allows more target type resources to be available on the target physical host for use with the designated type resources, thereby reducing the amount of fragmented designated type resources on the target physical host.

[0073] In this embodiment, the migration destination of the target instance is not limited. To avoid the fragmentation of specified resource types on other physical hosts caused by the migration of the target instance, in a preferred solution: if the target instance does not occupy the specified resource type, a physical host that does not support the deployment of instances that require the specified resource type can be selected from other physical hosts as the target instance's destination host; the target instance is then migrated to the selected destination host.

[0074] As mentioned earlier, different physical hosts support different instance types. Therefore, the control device queries each physical host's list of supported instance types and, from among the physical hosts other than the target host, identifies a host that doesn't support the deployment of instances that occupy the specified resource type. This host is then selected as the target host for the target instance. This prevents the migration of the target instance from causing resource fragmentation on the target host. Furthermore, since the target instance doesn't need to occupy the specified resource type, its lack of support on the target host won't affect the migration.

[0075] This optimal solution ensures that the target instance can be migrated to the destination host without any problems, while avoiding the fragmentation of specific types of resources on the destination host. Therefore, it can effectively guarantee the resource utilization of the target physical host and the destination host.

[0076] Of course, in this embodiment, other technical solutions can also be used to select a destination host for the target instance. It is not limited to the above-mentioned preferred solution. For example, if the target instance also needs to occupy a specified type of resource, then a migration prediction can be performed on other physical hosts based on the amount of resources that the target instance needs to occupy under the specified type of resource and the target type of resource, respectively, to predict whether the ratio of the remaining amount between the specified type of resource and the target type of resource on the corresponding physical host after the target instance is migrated to the physical host still meets the specification guarantee requirements set for the specified type of resource; based on this, a physical host whose prediction result is that the ratio of the remaining amount between the specified type of resource and the target type of resource after the target instance is migrated to the physical host still meets the corresponding specification guarantee requirements can be selected from other physical hosts as the destination host. This selection method can also avoid the problem of fragmentation of the specified type of resource introduced on the destination host due to the migration of the target instance. No further examples of the selection scheme are given here.

[0077] In summary, in this embodiment, the resource status of the specified type of resources and the target type of resources required to match them on the target physical host can be monitored separately; if the monitored resource status does not meet the specification guarantee requirements set for the specified type of resources, the target instance is selected from the instances occupying the target type of resources on the target physical host; the target instance is migrated from the target physical host so that the resource status of the specified type of resources and the target type of resources in the target physical host meet the specification guarantee requirements. In this way, the target type of resources on the target physical host can be replenished in a timely manner through resource management and control, avoiding the situation where the remaining amount of the specified type of resources is sufficient, but the remaining amount of the target type of resources required to match them is insufficient, resulting in the specified type of resources having to be idle, thereby effectively improving the utilization rate of the specified type of resources and ensuring that various instances that need to occupy the specified type of resources can be created more promptly.

[0078] In the above or following embodiments, a variety of migration strategies can be used to select a target instance. FIG3 is a flow chart of a resource management method provided by another exemplary embodiment of the present disclosure. Referring to FIG3, the resource management method may include:

[0079] Step 300: Monitor the resource status of the specified type of resources and the target type of resources required to be matched on the target physical host;

[0080] Step 301: If the monitored resource status does not meet the specification guarantee requirement set for the specified type of resource, a target instance is selected from instances on the target physical host that occupy the target type of resource and do not occupy the specified type of resource;

[0081] Step 302: Migrate the target instance from the target physical host so that the resource states of the designated type resources and target type resources in the target physical host meet the specification assurance requirements.

[0082] Regarding step 300 and step 302, reference may be made to the relevant descriptions in the aforementioned embodiment, which will not be repeated here. Based on step 301, this embodiment proposes an optional implementation method for selecting a target instance.

[0083] Referring to step 301, this embodiment proposes selecting a target instance from instances on the target physical host that occupy resources of the target type but do not occupy resources of the specified type. As mentioned throughout, the control device in this embodiment can complex instance scheduling. Therefore, the control device can obtain information such as the types and specifications of the instances running on each physical host. Thus, in step 301, the control device can seamlessly identify which instances running on the target physical host occupy resources of the target type but do not occupy resources of the specified type.

[0084] Here, setting the filtering range to "instances that occupy target type resources and do not occupy specified type resources" can release a portion of target type resources after the filtered target instances are migrated out, thereby increasing the remaining amount of target type resources in the target physical host. However, the migration of the target instances will not cause the remaining amount of specified type resources on the target physical host to change. Furthermore, this can more efficiently ensure that the ratio of the remaining amount between specified type resources and target type resources on the target physical host meets the specification guarantee requirements.

[0085] Under this screening range, this embodiment further proposes an exemplary solution for screening target instances therefrom, which may be:

[0086] Determine the remaining amount of the target type resource according to the resource status of the target type resource;

[0087] Based on the specification guarantee requirements and the remaining amount of target type resources, calculate the amount of target type resources required to meet the specification guarantee requirements;

[0088] With the goal of achieving the freed-up amount for the total occupied resources of the target type, a target instance is selected from instances on the target physical host that occupy resources of the target type and do not occupy resources of the specified type.

[0089] In this exemplary solution, since instances within the screening range won't cause a change in the remaining amount of a specified resource type, the focus is solely on whether the remaining amount of the target resource type, as a result of the selected target instance, meets the required specification guarantee. To this end, this exemplary solution introduces the parameter "freed-up amount" for the target resource type as a basis for selecting target instances. Based on this, instances within the aforementioned screening range whose total usage of the target resource type reaches this freed-up amount can be selected as target servers.

[0090] In actual applications, the number of target servers screened out may be one or more. When the number of target servers is one, the target server's occupation of the target type resources on the target physical server has reached the aforementioned required freed-up amount. In this way, after the target server is migrated out, the amount of target type resources freed up is added to the remaining amount of target type resources already on the target physical host. The remaining amount ratio between the specified type resources and the target type resources can meet the required specification guarantee requirements. When the number of target physical servers is multiple, the total amount of target type resources occupied by multiple target servers on the target physical server can reach the aforementioned required freed-up amount. In this way, after the target servers are migrated out, the amount of target type resources freed up is added to the remaining amount of target type resources already on the target physical host. The remaining amount ratio between the specified type resources and the target type resources can meet the required specification guarantee requirements.

[0091] It is worth noting that in this embodiment, in addition to using the freed-up amount parameter as a screening criterion as in the aforementioned exemplary solution, other screening criteria may also be used, such as the total amount of target type resources occupied by the remaining instances on the target physical host after excluding the target instance. Further examples are not provided here.

[0092] During the research process, the inventors found that there are usually multiple selectable instances within the aforementioned screening range. Therefore, how to reasonably select the target instance becomes a problem that needs to be considered. Two exemplary screening methods are provided below.

[0093] The first one:

[0094] Instances occupying target type resources and not occupying specified type resources on the target physical host can be sorted according to the amount of target type resources they occupy.

[0095] Instances are selected in descending order of occupancy until the remaining amount of target type resources in the target physical host meets the required specification guarantee requirements.

[0096] Use the selected instance as the target instance.

[0097] In this screening method, instances within the screening range that have the lowest resource usage of the target type are preferentially selected. After a sufficient number of instances have been screened, screening is stopped, and the screening results are obtained. "Sufficient" here means that the freed-up capacity resulting from the selected instances, or other parameters used as screening criteria in this embodiment, have met the relevant requirements. For example, the freed-up capacity resulting from the selected instances is equal to or greater than the required freed-up capacity.

[0098] In this way, the target instances selected using this screening method will mostly be instances with relatively small specifications, which can effectively ensure the migration success rate and more efficiently manage fragmented resources.

[0099] The second type:

[0100] Instances occupying target type resources and not occupying specified type resources on the target physical host can be sorted according to the current load.

[0101] Instances are selected in descending order of load, ensuring that the remaining resources of the target type in the target physical host meet the required specifications.

[0102] Use the selected instance as the target instance.

[0103] This filtering method prioritizes instances with lower loads within the filtering range. Once a sufficient number of instances have been selected, the filtering process stops, resulting in a final result. This method ensures that the target instances selected are mostly those with lower loads, resulting in a smaller amount of data required for migration and higher migration efficiency. This allows for more efficient management of fragmented resources.

[0104] It should be understood that the above two screening methods are merely exemplary. In this embodiment, other screening methods may also be used, such as random screening or giving priority to instances with a later creation time, etc. No further examples are given here.

[0105] In summary, in this embodiment, an optional implementation method for selecting a target instance is provided based on step 301. In this optional implementation method, the screening range is limited to instances that occupy target type resources but do not occupy specified type resources, and the target instance can be screened out within the screening range to ensure that the remaining amount of target type resources in the target physical host can meet the required specification guarantee requirements after the target instance is migrated out. Under the limitation of the screening range, the selected target instance can supplement the target type resources on the target physical host after migrating from the target physical host, but it will not cause the remaining amount of specified type resources on the target physical host to change. Therefore, this can effectively improve the efficiency of fragmentation management of specified type resources.

[0106] It is worth noting that in addition to the optional implementation method for selecting the target instance provided in step 301, other implementation methods can also be used to select the target instance. For example, the screening range can be set to instances that occupy resources of the target type. Further implementation examples are not provided here.

[0107] In the above or following embodiments, the management and control device does not need to perform resource management on all physical hosts. Instead, it can screen out physical hosts that may have fragmentation problems from the deployed physical hosts and perform fragmentation processing on them according to the resource management method provided in the above embodiments. Figure 4 is a flow chart of a resource management method provided by another exemplary embodiment of the present disclosure. Referring to Figure 4, the method may include:

[0108] Step 400: When a newly deployed physical host appears, determine the target machine model corresponding to the newly deployed physical host;

[0109] Step 401: query the resource configuration information associated with the target model to determine whether a specified type of resource exists on the newly deployed physical host;

[0110] Step 402: query the instance type list supported by the newly deployed physical host to determine whether the newly deployed physical host supports mixed deployment of multiple types of instances;

[0111] Step 403: If the newly deployed physical host has resources of the specified type and supports mixed deployment of multiple types of instances, the newly deployed physical host is determined as the target physical host;

[0112] Step 404: If the remaining amount ratio between the specified type of resource on the monitored target physical host and the target type of resource required for matching does not meet the specification guarantee requirement set for the specified type of resource, a target instance is selected from the instances occupying the target type of resource on the target physical host;

[0113] Step 405: Migrate the target instance from the target physical host so that the remaining amount of target type resources in the target physical host meets the specification guarantee requirement.

[0114] Among them, step 404 and step 405 can refer to the relevant description in the above embodiment and will not be repeated here.

[0115] In this embodiment, the control device is aware of the deployment and offline of the physical host. Therefore, when a newly deployed physical host appears, the control device can determine whether the physical host may have a fragmentation problem corresponding to the specified type of resources according to steps 400-403 of this embodiment.

[0116] Referring to Figure 4 , in step 400, the target machine model corresponding to the newly deployed physical host can be determined. As mentioned above, different machine models are associated with their own resource configuration information. Based on this, in step 401, the resource configuration information associated with the target machine model can be queried to determine whether the newly deployed physical host has a resource of the specified type.

[0117] With reference to FIG4 , in this embodiment, in step 402, it is further proposed that a list of instance types supported by the newly deployed physical host can be queried to determine whether the newly deployed physical host supports mixed deployment of multiple types of instances. For a physical host that does not support mixed deployment of multiple types of instances, since the instance type carried thereon is single, the ratio of the remaining amount between each type of resource is usually relatively stable, and therefore, fragmented resources usually do not occur. On a physical host that supports mixed deployment, since different types of instances require different types of resources and resource specifications, the creation or release of instances on such physical hosts will cause the ratio of the remaining amount between each type of resource to change dynamically, and therefore, fragmented resources often occur.

[0118] Accordingly, in step 403, if the newly deployed physical host has resources of the specified type and supports mixed deployment of multiple types of instances, the newly deployed physical host is determined as the target physical host.

[0119] Thereafter, the control device may perform real-time resource control on each of the identified target physical hosts according to the resource control solution provided in steps 404 and 405, so as to manage the fragmentation of the specified type of resources on these target physical hosts. It should be understood that the target physical hosts identified by the control device may be one or more, and the target physical hosts that the control device focuses on will also change dynamically as the physical hosts are deployed and taken offline. Newly deployed physical hosts may be added as target physical hosts, while target physical hosts that have been taken offline will no longer be focused on.

[0120] In summary, this embodiment allows for the selection of physical hosts from among the deployed physical hosts that have resources of a specified type and support the mixed deployment of multiple types of instances. These hosts are then selected as target physical hosts, and resource management and control are performed on each of these selected physical hosts to manage the fragmentation of the specified type of resources on them. This can comprehensively and accurately address the fragmentation of various resources on the deployed physical hosts and improve resource utilization within them.

[0121] Figures 5a and 5b are schematic diagrams of an exemplary application scenario provided by the present disclosure. Referring to Figures 5a and 5b, a memory management solution is described in detail by taking fragmentation management of GPU resources in physical host A as an example.

[0122] Referring to Figure 5a, in this exemplary application scenario, physical host A provides 4 GPUs and 64 CPU cores, and supports hybrid deployment. After scheduling by the control device, physical host A first creates a GPU instance (essentially an instance) based on customer requirement 1, and this GPU instance occupies 2 GPUs and 8 CPU cores. Subsequently, a CPU instance (essentially an instance) is created based on customer requirement 2, and this CPU instance occupies 40 CPU cores. At this point, physical host A still has 2 GPUs and 16 CPU cores remaining. However, some time later, the aforementioned customer requirement 1 releases 2 GPUs and 8 CPU cores.

[0123] Afterwards, when the control device monitors the resources of physical host A, it can be detected that the remaining ratio between the GPU and the CPU on physical host A is: 4:24. The control device also obtains the specification guarantee requirement set for the GPU of physical host A: the remaining ratio between the GPU and the CPU is less than or equal to 1:8. Therefore, the control device detects that a GPU fragmentation problem has occurred on physical host A at this time.

[0124] Referring to Figure 5b, the control device can filter out some CPU instances from physical host A and migrate these CPU instances to other physical hosts to free up more CPU cores on physical host A, so that the GPU:CPU on physical host A can meet the 1:8 requirement.

[0125] The above memory management process can maintain a stable ratio of GPU to CPU on physical host A at approximately 1:8, without significant fluctuations. This ensures that physical host A can readily host instances with a GPU:CPU ratio of ≥ 1:8, especially ensuring the timely deployment of instances with the maximum GPU:CPU ratio of 1:8, thereby improving the resource utilization of physical host A.

[0126] FIG6 is a schematic diagram of the structure of a control device provided by an exemplary embodiment of the present disclosure. As shown in FIG6 , the control device includes: a memory 60 and a processor 61 .

[0127] The processor 61 is coupled to the memory 60 and is configured to execute the computer program in the memory 60 to:

[0128] Monitor the resource status of the specified type of resources and the target type of resources they need to match on the target physical host respectively;

[0129] If the monitored resource status does not meet the specification guarantee requirements set for the specified type of resource, the target instance is selected from the instances occupying the target type of resource on the target physical host;

[0130] Migrate the target instance from the target physical host so that the resource status of the specified type of resources and the target type of resources in the target physical host meet the specification guarantee requirements.

[0131] In an optional embodiment, the processor 61 may be configured to:

[0132] Determine the remaining amount of the specified type of resource and the remaining amount of the target type of resource according to the respective resource states of the specified type of resource and the target type of resource;

[0133] If the remaining amount of the specified type of resource and the remaining amount of the target type of resource do not meet the specification guarantee requirement, it is determined that the monitored resource status does not meet the specification guarantee requirement;

[0134] The specification assurance requirements include the specification relationship between the specified type of resources and the target type of resources.

[0135] In an optional embodiment, when selecting a target instance from instances occupying target type resources on a target physical host, the processor 61 may be configured to:

[0136] Select the target instance from the instances on the target physical host that occupy resources of the target type but do not occupy resources of the specified type.

[0137] In an optional embodiment, when the processor 61 selects a target instance from instances on the target physical host that occupy resources of the target type and do not occupy resources of the specified type, it may be configured to:

[0138] Determine the remaining amount of the target type resource according to the resource status of the target type resource;

[0139] Based on the specification guarantee requirements and the remaining amount of target type resources, calculate the amount of target type resources required to meet the specification guarantee requirements;

[0140] With the goal of achieving the freed-up amount for the total occupied resources of the target type, a target instance is selected from instances on the target physical host that occupy resources of the target type and do not occupy resources of the specified type.

[0141] The number of target instances is one or more.

[0142] In an optional embodiment, when selecting a target instance, the processor 61 may be configured to:

[0143] Sort instances on the target physical host that occupy resources of the target type and do not occupy resources of the specified type by their usage of the target type resources.

[0144] Instances are selected in descending order of occupancy until the remaining amount of target type resources in the target physical host meets the guaranteed specification requirements.

[0145] Use the selected instance as the target instance.

[0146] In an optional embodiment, when selecting a target instance, the processor 61 may be configured to:

[0147] Sort instances on the target physical host that occupy resources of the target type and do not occupy resources of the specified type based on the current load.

[0148] Instances are selected in descending order of load until the remaining amount of target type resources in the target physical host meets the specification guarantee requirements.

[0149] Use the selected instance as the target instance.

[0150] In an optional embodiment, when the processor 61 monitors the resource status of a specified type of resource and the target type of resource required to be matched on the target physical host, it may be configured to:

[0151] Determine the target model corresponding to the target physical host;

[0152] Query the resource configuration information associated with the target machine model to determine the total amount of resources corresponding to the specified type of resources and the target type of resources on the target physical host;

[0153] The usage of the specified type of resources and / or target type of resources by each instance scheduled to the target physical host is monitored to represent the resource status.

[0154] In an optional embodiment, the processor 61 may also be configured to:

[0155] In the case of a newly deployed physical host, determine the target machine model corresponding to the newly deployed physical host;

[0156] Query the resource configuration information associated with the target model to determine whether the specified type of resources exists on the newly deployed physical host;

[0157] Query the instance type list supported by the newly deployed physical host to determine whether the newly deployed physical host supports mixed deployment of multiple types of instances;

[0158] If the newly deployed physical host has resources of the specified type and supports mixed deployment of multiple types of instances, the newly deployed physical host is determined as the target physical host.

[0159] In an optional embodiment, when migrating the target instance from the target physical host, the processor 61 may be configured to:

[0160] If the target instance does not occupy the specified type of resources, a physical host that does not support the deployment of instances that require the specified type of resources is selected from other physical hosts as the destination host for the target instance.

[0161] Migrate the target instance to the selected destination host.

[0162] In an optional embodiment, the processor 61 may also be configured to:

[0163] Obtain the resource specification information required by each type of instance that needs to occupy a specified type of resources and is supported for deployment on the target physical host;

[0164] From the acquired resource specification information, parse out the specification relationship between the required specified type resources and the target type resources;

[0165] From the parsed specification relationships, select a target specification relationship to set the specification assurance requirements for the specified type of resources.

[0166] In an optional embodiment, the specified type of resources includes one or more resources of GPU resources or local storage resources.

[0167] Furthermore, as shown in Figure 6 , the control device further includes other components such as a communication component 62 and a power supply component 63. Figure 6 only schematically illustrates some components, which does not mean that the control device only includes the components shown in Figure 6 .

[0168] It is worth noting that the technical details in the above-mentioned embodiments of the control device can be referred to the relevant description in the aforementioned method embodiment. In order to save space, they will not be repeated here, but this should not cause a loss of the scope of protection of this disclosure.

[0169] In addition to the resource control methods implemented by the control device mentioned in the above embodiments, the physical host can also autonomously manage resource fragmentation. Figure 7 is a schematic diagram of the structure of a physical host provided by another exemplary embodiment of the present disclosure. As shown in Figure 6, the physical host may include: memory 70 and processor 71. The physical host provides resources of the specified type and target type and carries one or more instances.

[0170] The processor 71 is coupled to the memory 70 and is configured to execute the computer program in the memory 70 to:

[0171] Monitor the resource status of the specified type of resources and the target type of resources they need to match;

[0172] If the monitored resource status does not meet the specification guarantee requirements set for the specified type of resource, the target instance is selected from the instances occupying the target type of resource;

[0173] Migrate the target instance so that the resource status of the specified type resources and target type resources meet the specification guarantee requirements.

[0174] In this embodiment, the physical host can autonomously manage the fragmentation of designated types of resources.

[0175] In an optional embodiment, the processor 71 may also be configured to:

[0176] Determine the remaining amount of the specified type of resource and the remaining amount of the target type of resource according to the respective resource states of the specified type of resource and the target type of resource;

[0177] If the remaining amount of the specified type of resource and the remaining amount of the target type of resource do not meet the specification guarantee requirement, it is determined that the monitored resource status does not meet the specification guarantee requirement;

[0178] The specification assurance requirements include the specification relationship between the specified type of resources and the target type of resources.

[0179] In an optional embodiment, when selecting a target instance from instances occupying resources of the target type, the processor 71 may be configured to:

[0180] Select the target instance from instances that occupy resources of the target type and do not occupy resources of the specified type.

[0181] In an optional embodiment, when the processor 71 selects a target instance from instances that occupy resources of the target type and do not occupy resources of a specified type, it may be configured to:

[0182] Determine the remaining amount of the target type resource according to the resource status of the target type resource;

[0183] Based on the specification guarantee requirements and the remaining amount of target type resources, calculate the amount of target type resources required to meet the specification guarantee requirements;

[0184] With the goal of achieving the freed-up amount for the total occupied resources of the target type, select the target instance from instances that occupy resources of the target type and do not occupy resources of the specified type.

[0185] The number of target instances is one or more.

[0186] In an optional embodiment, when selecting a target instance, the processor 71 may be configured to:

[0187] Sort instances that occupy target type resources but do not occupy specified type resources by their usage of target type resources.

[0188] Instances are selected in descending order of occupancy until the remaining amount of target type resources meets the guaranteed specifications.

[0189] Use the selected instance as the target instance.

[0190] In an optional embodiment, when selecting a target instance, the processor 71 may be configured to:

[0191] Sort instances that occupy resources of the target type and do not occupy resources of the specified type based on their current load.

[0192] Instances are selected in descending order of load until the remaining resources of the target type meet the guaranteed specifications.

[0193] Use the selected instance as the target instance.

[0194] In an optional embodiment, when the processor 71 monitors the resource status of a specified type of resource and the target type of resource it needs to match, it may be configured to:

[0195] Determine the target model that corresponds to itself;

[0196] Query the resource configuration information associated with the target model to determine the total amount of resources corresponding to the specified type of resources and the target type of resources;

[0197] Monitor the usage of designated type resources and / or target type resources by each instance hosted by the system to represent the resource status.

[0198] In an optional embodiment, when migrating the target instance, the processor 71 may be configured to:

[0199] If the target instance does not occupy the specified type of resources, a physical host that does not support the deployment of instances that require the specified type of resources is selected from other physical hosts as the destination host for the target instance.

[0200] Migrate the target instance to the selected destination host.

[0201] In an optional embodiment, the processor 71 may also be configured to:

[0202] Obtain the resource specification information required by each type of instance that it supports deployment and requires the use of specified types of resources;

[0203] From the acquired resource specification information, parse out the specification relationship between the required specified type resources and the target type resources;

[0204] From the parsed specification relationships, select a target specification relationship to set the specification assurance requirements for the specified type of resources.

[0205] In an optional embodiment, the specified type of resources includes one or more resources of GPU resources or local storage resources.

[0206] Furthermore, as shown in Figure 7, the physical host also includes other components such as a communication component 72 and a power supply component 73. Figure 7 only schematically shows some components, which does not mean that the physical host only includes the components shown in Figure 7.

[0207] Accordingly, an embodiment of the present disclosure further provides a computer-readable storage medium storing a computer program, which, when executed, can implement the steps in the above method embodiment that can be performed by the control device or the physical host.

[0208] The memory in Figures 6 and 7 is used to store computer programs and can be configured to store various other data to support operations on the computing platform. Examples of such data include instructions for any application or method operating on the computing platform, contact data, phone book data, messages, pictures, videos, etc. The memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, or optical disk.

[0209] The communication components in Figures 6 and 7 above are configured to facilitate wired or wireless communication between the device where the communication component is located and other devices. The device where the communication component is located can access a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G / LTE, 5G and other mobile communication networks, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0210] The power supply assembly in Figures 6 and 7 provides power to various components of the device in which the power supply assembly is located. The power supply assembly may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device in which the power supply assembly is located.

[0211] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0212] The present disclosure is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present disclosure. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0213] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0214] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0215] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0216] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0217] The above are merely embodiments of the present disclosure and are not intended to limit the present disclosure. Various modifications and variations are possible for those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present disclosure shall be included within the scope of protection of the present disclosure.

Claims

1. A resource management method, wherein: include: Monitor the resource status of the specified type of resources and the target type of resources required to match them on the target physical host respectively; If the monitored resource status does not meet the specification guarantee requirement set for the specified type of resource, selecting a target instance from the instances occupying the target type of resource on the target physical host; The target instance is migrated from the target physical host so that the resource states of the designated type of resources and the target type of resources in the target physical host meet the specification guarantee requirement.

2. The method according to claim 1, wherein: Also includes: Determining the remaining amount of the designated type of resource and the remaining amount of the target type of resource according to the respective resource states of the designated type of resource and the target type of resource; If the remaining amount of the designated type of resource and the remaining amount of the target type of resource do not meet the specification guarantee requirement, determining that the monitored resource state does not meet the specification guarantee requirement; The specification guarantee requirement includes the specification relationship specified for the specified type of resources and the target type of resources.

3. The method according to claim 1, wherein: Selecting a target instance from instances occupying the target type resource on the target physical host includes: The target instance is selected from instances on the target physical host that occupy resources of the target type and do not occupy resources of the specified type.

4. The method according to claim 3, wherein: Selecting the target instance from instances on the target physical host that occupy resources of the target type and do not occupy resources of the specified type includes: Determining the remaining amount of the target type resource according to the resource status of the target type resource; Based on the specification guarantee requirement and the remaining amount of the target type resource, calculating the freed-up amount of the target type resource required to meet the specification guarantee requirement; With the total amount of occupation of the target type of resources reaching the vacated amount as a goal, the target instance is selected from instances on the target physical host that occupy the target type of resources and do not occupy the designated type of resources; The number of the target instances is one or more.

5. The method according to any one of claims 3 or 4, wherein: Selecting the target instance includes: According to the occupation amount of the target type resource, the instances on the target physical host that occupy the target type resource and do not occupy the designated type resource are sorted; Selecting instances in order of occupancy from low to high, until the selected instances make the remaining amount of the target type resources in the target physical host meet the specification guarantee requirement; The selected instance is used as the target instance.

6. The method according to any one of claims 3 or 4, wherein: Selecting the target instance includes: According to the current load, the instances on the target physical host that occupy the target type of resources and do not occupy the specified type of resources are sorted; Selecting instances in order of load from low to high until the selected instances make the remaining amount of the target type resources in the target physical host meet the specification guarantee requirement; The selected instance is used as the target instance.

7. The method according to claim 1, wherein: Monitor the resource status of the specified type of resources and the target type of resources they need to match on the target physical host, including: Determine a target machine model corresponding to the target physical host; Querying the resource configuration information associated with the target machine model to determine the total amount of resources corresponding to the designated type of resources and the target type of resources on the target physical host; The occupation of the designated type of resources and / or the target type of resources by each instance scheduled to the target physical host is monitored to characterize the resource status.

8. The method according to claim 1, wherein: Also includes: In the case of a newly deployed physical host, determine the target machine model corresponding to the newly deployed physical host; Querying resource configuration information associated with the target machine model to determine whether the specified type of resource exists on the newly deployed physical host; Querying a list of instance types supported by the newly deployed physical host to determine whether the newly deployed physical host supports mixed deployment of multiple types of instances; If the designated type of resource exists on the newly deployed physical host and supports mixed deployment of multiple types of instances, the newly deployed physical host is determined as the target physical host.

9. The method according to claim 1, wherein: Migrating the target instance from the target physical host includes: If the target instance does not occupy the specified type of resources, a physical host that does not support the deployment of instances that need to occupy the specified type of resources is selected from other physical hosts as the destination host of the target instance; Migrate the target instance to the selected destination host.

10. The method according to any one of claims 1 or 2, wherein: Also includes: Obtain resource specification information required by each type of instance that needs to occupy the specified type of resources and is supported for deployment on the target physical host; From the acquired resource specification information, respectively parse out the specification relationship between the required specified type resources and the target type resources; A target specification relationship is selected from the parsed specification relationships to set specification assurance requirements corresponding to the specified type of resources.

11. The method according to claim 1, wherein: The specified type of resources includes one or more resources of GPU resources or local storage resources.

12. A control device, wherein: Includes memory, processor, and communication components; The memory is used to store one or more computer instructions; The processor is coupled to the memory and the communication component, and is used to execute the one or more computer instructions to execute the resource management method described in any one of claims 1-11.

13. A physical host, wherein: The physical host comprises a memory, a processor and a communication component, wherein the physical host provides resources of a specified type and resources of a target type and carries one or more instances; The memory is used to store one or more computer instructions; The processor is coupled to the memory and the communication component and is configured to execute the one or more computer instructions for: Respectively monitoring the resource status of the designated type of resource and the target type of resource required to be matched therewith; If the monitored resource status does not meet the specification guarantee requirements set for the specified type of resource, the resource will be occupied. Select a target instance from the instances of the target type resource; The target instance is migrated out so that the resource states of the designated type resources and the target type resources meet the specification guarantee requirement.

14. A computer-readable storage medium storing computer instructions, wherein: When the computer instructions are executed by one or more processors, the one or more processors are caused to execute the resource management method described in any one of claims 1-11.

15. A computer program product, wherein: The invention comprises a computer program, which implements the method according to any one of claims 1 to 11 when being executed by a processor.

Images