WO2023221444A1 - 一种资源管理方法以及相关装置 - Google Patents

一种资源管理方法以及相关装置 Download PDF

Info

Publication number
WO2023221444A1
WO2023221444A1 PCT/CN2022/133401 CN2022133401W WO2023221444A1 WO 2023221444 A1 WO2023221444 A1 WO 2023221444A1 CN 2022133401 W CN2022133401 W CN 2022133401W WO 2023221444 A1 WO2023221444 A1 WO 2023221444A1
Authority
WO
WIPO (PCT)
Prior art keywords
cloud
information
resource
plan
available
Prior art date
Application number
PCT/CN2022/133401
Other languages
English (en)
French (fr)
Inventor
陈普
Original Assignee
华为云计算技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为云计算技术有限公司 filed Critical 华为云计算技术有限公司
Publication of WO2023221444A1 publication Critical patent/WO2023221444A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0283—Price estimation or determination
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Definitions

  • Embodiments of the present application relate to the field of computers, and in particular, to a resource management method and related devices.
  • cloud service providers connect a large number of computing resources through the network to form a huge resource pool to provide cloud services to user equipment.
  • the user equipment manages and schedules the computing resources in the resource pool through the resource management server. .
  • the user equipment sends a cloud resource application to the resource management server.
  • the cloud resource application includes the specifications of the computing resources, such as the number of processor cores and memory size.
  • the provider of the cloud service provides the user device with corresponding price information for cloud resource application based on the usage of cloud resources in the current resource pool, and the user device chooses to subscribe to the cloud service based on the price information provided by the cloud service provider.
  • cloud service providers only provide price information for user devices based on the available resource status information in the resource pool at the time of resource application.
  • the available resource status information in the resource pool will vary depending on the user equipment used at different times. Changes, therefore, providers of current transaction methods cloud services provide inaccurate pricing information, further leading to wastage of computing resources in resource pools.
  • Embodiments of the present application provide a resource management method and related devices for improving the utilization of cloud resources.
  • the first aspect of the embodiment of the present application provides a resource management method.
  • the method can be executed by a management server, or by a component of the management server, such as a processor, a chip or a chip system of the management server. It can also be executed by a management server that can implement A logical module or software implementation that manages all or part of the server's functionality.
  • the resource management method provided by the first aspect of the embodiment of the present application includes: the management server obtains the available resource status information of the cloud server cluster, and the available resource status information includes one or more of the following: Available cloud resource capacity in different periods and available cloud resource specifications in different periods in the future. Available cloud resource capacity includes the number of virtual machines, physical hosts or containers available in future periods.
  • Available cloud resource specifications include the number of processor cores, memory size or Graphics card model.
  • the management server generates cloud service price information based on the available resource status information.
  • the cloud service price information includes price information of one or more specifications of cloud resources in different periods in the future.
  • the management server sends cloud service price information to the user device.
  • the management server can obtain the available cloud resource status information of the cloud server cluster in the future period, and generate the corresponding cloud service price based on the available cloud resource status information, because the cloud service price is based on the available cloud resources in different periods in the future.
  • the price is calculated based on the type and available cloud resource capacity. Therefore, the cloud service price can accurately reflect the adequacy or shortage of available cloud resources, which is more conducive to the sales of cloud resources and thereby improves the utilization efficiency of cloud resources in cloud servers.
  • the management server before the management server obtains the available resource status information of the cloud server cluster, receives plan information sent by the user equipment.
  • the plan information is used to provide the management server with the user equipment's demand plan for cloud resources.
  • the plan information include one or more of the following information: the demand period of cloud resources or the demand specifications of cloud resources.
  • the management server When the management server generates cloud service price information based on available resource status information, the management server generates cloud service price information based on plan information and available resource status information.
  • the cloud service price information is the corresponding cloud service price information described in the plan information.
  • the management server receives the plan information submitted by the user equipment, and generates the cloud service price corresponding to the plan information based on the plan information submitted by the user equipment and the available resource status, because the user equipment has submitted in advance the demand capacity for cloud resources in the future period. and demand specifications. Therefore, the management server can provide more accurate cloud service prices based on planning information, further improving the utilization efficiency of cloud resources.
  • the available cloud resource specifications in the available resource status information are consistent with the demand specifications in the plan information, and the management server determines the cloud resources of the corresponding specifications based on the demand specifications in the plan information submitted by the user equipment.
  • the embodiment of the present application provides that the available cloud resource specifications provided by the management server are consistent with the demand specifications in the plan information, so that the available cloud resource specifications meet the demand specifications of the plan information, improving the realizability of the method.
  • the management server when the management server generates cloud service price information based on plan information and available resource status information, when the available resource status information meets the plan information, and the available cloud resource capacity in the available resource status information is greater than or equal to the target When the threshold is exceeded, the management server generates cloud service discount information.
  • the management server can provide discounted prices for cloud services to user devices that submit planning information in advance, thereby improving the utilization of cloud resources.
  • the management server after the management server sends the cloud service price information to the user equipment, the management server receives the order information sent by the user equipment, and the order information is used to confirm the cloud service price information corresponding to the plan information.
  • the management server after the management server sends the cloud service price information to the user equipment, it receives the order request corresponding to the plan information sent by the user equipment, thereby improving the implementability of the solution.
  • the management server before the management server sends the cloud service price information to the user equipment, the management server receives the query request sent by the user equipment.
  • the management server sends available resource status information and cloud service price information to the user device according to the query request.
  • the management server sends the available cloud resource specifications and available cloud resource capacity and corresponding prices in the future period to the user, and the user device selects what needs to be ordered. Time period, cloud resource specifications, and cloud resource capacity.
  • the management server can send the available resource status information and the corresponding cloud service price information in the future period to the user equipment based on the query request sent by the user equipment, and the user equipment selects the cloud resource demand period and cloud resources to be ordered. specifications and cloud resource capacity, thereby improving the utilization of cloud resources.
  • the management server after the management server sends available resource status information and cloud service price information to the user equipment according to the query request, the management server receives the order information sent by the user equipment, and the order information includes at least one specification of the cloud selected by the user equipment. The resource and the price of the cloud resource for at least one specification.
  • the management server after the management server sends available resource status information and cloud service price information to the user equipment, it receives the cloud resource demand period, cloud resource specifications, and cloud resource capacity selected by the user equipment, thereby improving the realizability of the solution.
  • the management server obtains the scheduling information of the cloud server cluster.
  • the scheduling information includes one or more of the following information: Submitted cloud resource plan , cloud resource plan based on historical cloud resource change prediction, idle cloud resource plan that needs to be reserved, total cloud resource plan, maximum cloud resource plan for a single device and continuation plan of cloud resources in use.
  • the management server generates available resource status information of the cloud server cluster based on the scheduling information. Specifically, the management server subtracts the submitted cloud resource plan, the cloud resource plan based on historical cloud resource change predictions, the idle cloud resource plan that needs to be reserved, and the continuation plan of the cloud resources in use from the total cloud resource plan to obtain Available cloud resource capacity at different times.
  • the management server can regularly obtain the scheduling information of the cloud server cluster, and calculate the available resource status information based on the scheduling information, thereby improving the accuracy of the available resource status information.
  • the second aspect of the embodiment of the present application provides a resource management device.
  • the resource management device includes a transceiver unit and a processing unit.
  • the transceiver unit is used to obtain the available resource status information of the cloud server cluster.
  • the available resource status information includes one or more of the following: available cloud resource capacity of the cloud server cluster in different periods in the future and available cloud resource specifications in different periods in the future.
  • the processing unit is configured to generate cloud service price information based on available resource status information, where the cloud service price information includes price information of multiple specifications of cloud resources.
  • the transceiver unit is also used to send cloud service price information to the user device.
  • the transceiver unit is also used to receive planning information sent by the user equipment.
  • the planning information is used to provide the management server with the user equipment's demand plan for cloud resources.
  • the planning information includes one or more of the following information: Cloud The demand period of resources or the demand specifications of cloud resources.
  • the processing unit is specifically used to generate cloud service price information based on plan information and available resource status information.
  • the available cloud resource specifications in the available resource status information are consistent with the demand specifications in the planning information.
  • the processing unit is specifically configured to generate cloud service discount information when the available resource status information meets the plan information, and the available cloud resource capacity in the available resource status information is greater than or equal to the target threshold.
  • the transceiver unit is also configured to receive order information sent by the user equipment, and the order information is used to confirm the cloud service price information corresponding to the plan information.
  • the transceiver unit is also configured to receive a query request sent by the user equipment.
  • the processing unit is also used to send available resource status information and cloud service price information to the user device according to the query request.
  • the transceiver unit is further configured to receive order information sent by the user equipment, where the order information includes at least one specification of cloud resources selected by the user equipment and a price of at least one specification of the cloud resource.
  • the transceiver unit is also used to obtain scheduling information of the cloud server cluster.
  • the scheduling information includes one or more of the following information: submitted cloud resource plans, cloud resource plans based on historical cloud resource change predictions, The idle cloud resource plan that needs to be reserved, the total cloud resource plan, the maximum cloud resource plan for a single device, and the continuation plan for cloud resources in use.
  • the processing unit is also used to generate available resource status information of the cloud server cluster based on the scheduling information.
  • the third aspect of the embodiment of the present application provides a management server, which includes a processor.
  • the processor is coupled to a memory.
  • the processor is configured to store instructions.
  • the management server executes the above first aspect or the first aspect. The method described in any possible implementation manner.
  • the fourth aspect of the embodiments of the present application provides a computer-readable storage medium on which instructions are stored.
  • the computer executes the method described in the above-mentioned first aspect or any possible implementation manner of the first aspect. method.
  • the fifth aspect of the embodiments of the present application provides a computer program product.
  • the computer program product includes instructions. When the instructions are executed, the computer implements the method described in the above-mentioned first aspect or any possible implementation manner of the first aspect. .
  • Figure 1 is a schematic system architecture diagram of a cloud resource scheduling system provided by an embodiment of the present application
  • Figure 2 is a schematic flow chart of a resource management method provided by an embodiment of the present application.
  • Figure 3 is a schematic diagram of a cloud resource scheduling plan provided by an embodiment of the present application.
  • Figure 4a is a schematic flow chart of another resource management method provided by an embodiment of the present application.
  • Figure 4b is a schematic diagram of a management server UI interface provided by an embodiment of the present application.
  • Figure 5 is a schematic flow chart of another resource management method provided by an embodiment of the present application.
  • Figure 6 is a schematic structural diagram of a resource management device provided by an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a management server provided by an embodiment of the present application.
  • Embodiments of the present application provide a resource management method and related devices for improving the resource utilization efficiency of cloud servers.
  • FIG. 1 is a schematic system architecture diagram of a cloud resource scheduling system provided by an embodiment of the present application.
  • the cloud resource scheduling system 100 includes a management server 101 , a cloud server 102 and a user equipment 103 .
  • the user equipment 103 is connected to the cloud server 102 through the management server 101 .
  • the functions of each part in the cloud resource scheduling system 100 are introduced in detail below.
  • the management server 101 is used to manage and schedule cloud resources provided by the cloud server 102, including collecting the resource status of all physical hosts in the cloud server 102, issuing new cloud resource applications to the user equipment 103 for scheduling, and providing user equipment 103 with Pricing information for cloud services.
  • the management server 101 includes a planning resource transaction module 1011 and a resource scheduling module 1012.
  • the computing resource transaction module 1011 is used to calculate whether the available resource status information of the cloud server 102 meets the cloud resource application requirements of the user device 103, and according to the available resource status information Generate pricing information for cloud services.
  • the resource scheduling module 1012 is used to obtain the available resource status information of the cloud server 102 and schedule the cloud resources provided by the cloud server 102.
  • the management server 101 can also externally provide an operable UI interface and an application programming interface API that can be called.
  • the management server 101 can also provide transaction services for externally providing cloud resources in the cloud server 102 .
  • the management server 101 is such as OpenStack, VMware, etc.
  • the cloud server 102 is used to provide cloud resources for the user equipment 103.
  • the cloud server 103 includes multiple physical hosts, where multiple virtual machines are deployed on each physical host.
  • Cloud resources provided by the cloud server 102 include physical hosts, virtual machines and containers.
  • the cloud server 102 provides available cloud resources to the user device 103 according to the scheduling plan of the management server 101. It can be understood that multiple cloud servers 102 also form a cloud service cluster, and the server cluster provides cloud services to the user equipment 103.
  • the user device 103 is used to request cloud resources from the management server 101. Specifically, the user device 103 can send a request for cloud resources to the management server 101 based on the UI interface or web UI interface provided by the management server 101, or can send a resource request to the management server 101 through the application software of the user device 103.
  • the specifics are not limited. .
  • Figure 2 is a schematic flowchart of a resource management method provided by an embodiment of the present application.
  • the resource management method provided by the embodiment of this application includes but is not limited to the steps:
  • the management server obtains the available resource status information of the cloud server cluster.
  • the available resource status information includes one or more of the following information: available cloud resource capacity and available cloud resource specifications of the cloud server cluster in different periods in the future.
  • the management server obtains the available resource status information of the cloud server cluster.
  • the available resource status information includes one or more of the following information: the available cloud resource capacity and available cloud resource specifications of the cloud server in different periods in the future.
  • the types of cloud resources in this embodiment of the present application include virtual machines, physical hosts, and containers, where each type of cloud resource includes different specifications.
  • the specifications of a virtual machine include the number of processor cores, memory size, and graphics card model.
  • Available cloud resource capacity includes the number of virtual machines, physical hosts and containers that the cloud server cluster can provide to user devices.
  • the management server's planned transaction module queries the resource scheduling module for scheduling information, and the management server's planned transaction module generates the available resource status of the cloud server cluster based on the scheduling information.
  • the scheduling information of the cloud server cluster includes one or more of the following information: submitted cloud resource plan, cloud resource plan based on historical cloud resource change prediction, idle cloud resource plan that needs to be reserved, total cloud resource plan, single The maximum cloud resource plan for the device and the continuation plan for the cloud resources in use.
  • the resource plan application that has been submitted includes the demand capacity and demand specifications of user equipment for cloud resources in the future period.
  • the above-mentioned user equipment includes user equipment that has currently submitted plan information but has not completed the order, and other user equipment that has submitted completed plan information and completed the order. user equipment.
  • a cloud resource plan based on historical cloud resource change predictions refers to a plan that manages cloud resource usage changes in future periods based on historical cloud resource usage predictions by the management server.
  • the idle cloud resource plan that needs to be reserved refers to the cloud resources that the management service plans to reserve in order to cope with sudden cloud resource usage needs.
  • the idle resources that need to be reserved include new users that may appear between the current time and the planned application start time. Resource application for equipment, or new resource application for user equipment after the planned application start time.
  • the overall cloud resource application plan refers to the maximum planned cloud resource capacity that the cloud server cluster can provide, including the maximum resource capacity that each resource type can provide under different resource types.
  • the maximum cloud resource plan for a single device refers to the cloud resource plan set by the management server for the maximum cloud resource capacity that can be allocated to a single user device.
  • the continuation plan of cloud resources in use refers to the cloud resource plan reserved by the management server for the continuation of cloud resources in use by user devices.
  • Figure 3 is a schematic diagram of the cloud resource capacity of a cloud server cluster changing over time according to an embodiment of the present application.
  • the total cloud resource capacity of the cloud server cluster at each moment in the time period 0 to t6 is S7.
  • the idle cloud resource capacity that the cloud server cluster needs to reserve at each moment in the time period from 0 to t6 is S6-S5, and the continued cloud resource capacity of the cloud resources in use at each moment in the time period from 0 to t6 is S0.
  • the cloud resource capacity of the cloud resource plan 1 submitted by the user device at each time is S5-S3, and in the time period from t0 to t2, the cloud resource plan is predicted based on historical cloud resource changes at each time.
  • the cloud resource capacity in 1 is S1-S0
  • the cloud resource capacity in cloud resource plan 2 based on the historical cloud resource change prediction at each moment in the time period from t3 to t5 is S1-S0.
  • the cloud resource capacity in the maximum cloud resource plan of a single device at each moment is S3-S2.
  • Cloud resource capacity refers to the maximum cloud resource capacity that the management server can allocate to a single user device.
  • the resource plan 1 submitted by the user device, or the resource plan 2 submitted by the user device, and the resource plan 3 submitted by the user device are all The maximum resource capacity of the single device cannot be exceeded.
  • the management server can further calculate the available cloud resource capacity of the cloud server cluster in different periods according to the cloud resource plans of different periods.
  • the total cloud resource application plan in Figure 3 subtracts the idle cloud resource plan that needs to be reserved, the submitted cloud resource plan 1, the submitted cloud resource plan 2, the submitted cloud resource plan 3, and the historical forecast.
  • the available cloud resource plan can be obtained by the cloud resource plan 1, the cloud resource plan 2 based on historical forecasts, and the continuation of the cloud resources in use.
  • the available cloud resource plan can indicate the available cloud resource capacity in different time periods in the future. From the example shown in Figure 3, it can be seen that the available cloud resource capacity reaches the maximum value during the period 0 to t0 and between the period t5 and t6.
  • the idle cloud resource plan that needs to be reserved, the submitted cloud resource plan, the cloud resource plan based on the prediction of historical cloud resource changes, and the continuation plan of the cloud resources in use are included in the cloud resource plan.
  • Resource capacity has not changed during the period.
  • the cloud resource capacity in these plans may also change within the period. For example, the cloud resource capacity in these plans increases or decreases over time within the period.
  • the example shown in Figure 3 is only a cloud resource plan for a future period under a certain cloud resource type.
  • each cloud resource type has its corresponding cloud resource plan.
  • the management server can calculate available cloud resource plans under different cloud resource types based on the cloud resource plan in the future period.
  • the management server can periodically obtain the available resource status information of the cloud server cluster, or can trigger the management server to obtain the available resource status information of the cloud server cluster based on the cloud resource request of the user device.
  • the specific details are not limited.
  • the management server generates cloud service price information based on available resource status information.
  • the management server After obtaining the available resource status information, the management server generates cloud service price information based on the available resource status information. Specifically, the management server can generate price information for cloud services in different time periods based on the available cloud resource capacity in different time periods in the available resource status information. When the available cloud resource capacity is sufficient within a certain period, the management server can generate discount information for cloud services during that period.
  • the management server can generate cloud service price information corresponding to the plan information based on the plan information submitted by the user device and the available resource status information, or it can also use the available resource status information to generate cloud service price information.
  • the resource status information and the corresponding cloud service price information are sent to the user device for the user device to make a selection.
  • the details are not limited. The following two methods will be introduced respectively in the embodiments shown in Figure 4a and Figure 5 .
  • the management server can also generate different cloud service discount information for different user devices. For example, in the scenario where the user device submits planning information, the management server can generate different discount information based on the total cloud resource demand of the user device. For another example, the management server can generate different discount information for different user levels.
  • the management server sends cloud service price information to the user device.
  • the management server sends cloud service price information to the user device. After receiving the cloud service price information sent by the management server, the user device sends ordering information to the management server, and the ordering information is used to confirm the cloud service price information.
  • the management server reserves cloud resources corresponding to the ordering information for the user device based on the ordering information.
  • the management server can obtain the available cloud resource status information of the cloud server cluster in the future period, and generate the corresponding cloud service price based on the available cloud resource status information, because the cloud service price is based on the available cloud resources in different periods in the future.
  • the price is calculated based on the type and available cloud resource capacity. Therefore, the cloud service price can accurately reflect the adequacy or shortage of available cloud resources.
  • the management server sells the cloud resources related to the server according to the cloud service price, thereby improving the cloud service. Utilization of cloud resources in servers.
  • Figure 4a is a schematic flow chart of another resource management method provided by an embodiment of the present application.
  • the resource management method shown in Figure 4a includes the following steps:
  • the user device submits planning information to the management server.
  • the user equipment submits planning information to the management server.
  • the planning information is used to provide the management server with the user equipment's demand plan for cloud resources.
  • the planning information includes one or more of the following information: cloud resource demand period, cloud resource demand capacity and cloud resource demand plan. Resource requirements specifications.
  • the cloud resource type code can represent the type of cloud resource.
  • the cloud resource type code g5 represents a virtual machine with a 16-core processor, 32g memory, and RTX5000 graphics card.
  • the user equipment can submit plan information in a variety of ways.
  • the management server can submit plan information through the UI interface of the management server, or can also submit plan information by calling the planned transaction module in the management server through the application program interface API. There is no specific limit.
  • the planning information of the user equipment to the planned transaction module of the management server on March 30, 2022 includes: the user equipment applies for 100 virtual machines, the type of the virtual machine is g5, and the demand start time is 2022 It starts at 0:00 on April 1 and ends at 24:00 on April 15, 2022.
  • FIG 4b is a schematic diagram of a UI interface of a management server provided by an embodiment of the present application.
  • the user equipment can submit planning information of the user equipment through the UI interface of the management server.
  • the planning information submitted by the user equipment includes demand specifications of cloud resources and demand capacity of cloud resources in different planning time periods. For example, from 6:00 to 12:00 on April 1, 2022, to April 30, 2022, the required cloud resource specifications for user equipment are G4 virtual machines, and the required cloud resource capacity is 100 units.
  • the planning transaction module of the management server obtains the scheduling information of the cloud server cluster from the resource scheduling module.
  • the planning transaction module of the management server obtains the scheduling information of the cloud server cluster from the resource scheduling module.
  • the scheduling information includes one or more of the following information: submitted cloud resource plan, cloud resource plan based on historical cloud resource change prediction, required reservation idle cloud resource plan, total cloud resource plan, maximum cloud resource plan for a single device and continuation plan for cloud resources in use.
  • the planning and transaction module of the management server can regularly query the scheduling information of the cloud server cluster from the resource scheduling module, and can also trigger the query of scheduling information based on the planning information submitted by the user equipment, or the resource scheduling module can also regularly query the planning and transaction module. Reporting of scheduling information is not limited to specific details.
  • the planned transaction module of the management server generates available resource status information based on the scheduling information of the cloud server cluster.
  • the planned transaction module of the management server generates available resource status information based on the scheduling information of the cloud server cluster.
  • the available resource status information generated by the planned transaction module of the management server based on the scheduling information includes one or more of the following: available cloud resource capacity or available cloud resource specifications in different available periods in the future.
  • the available resource status information generated by the management server's planned transaction module based on the scheduling information is from 0:00 to 6:00 on April 1, 2022 to April 15, 2022, and the virtual machine type
  • the available cloud resource capacity for g4 is 5,000 virtual machines. From April 1, 2022 to April 15, 2022, from 6:00 to 18:00, the available cloud resource capacity for the virtual machine type g4 is 3,000 virtual machines.
  • the planning transaction module of the management server generates cloud service price information based on the planning information and available resource status information.
  • the plan transaction module of the management server generates cloud service price information based on the plan information and available resource status information.
  • the cloud service price information includes the cloud service price corresponding to the plan information. Further, when the available resource status information meets the plan information, and the available cloud resource capacity in the available resource status information is greater than or equal to the first threshold, the management server generates cloud service discount information. In addition, the available cloud resource specifications in the available resource status information need to be consistent with the cloud resource demand specifications in the planning information.
  • the management server can better calculate the available resource status information, and the management server can design more cloud service price discounts for the user equipment that submitted the plan information.
  • the planned transaction module of the management server sends cloud service price information to the user device.
  • the plan transaction module of the management server sends cloud service price information to the user device, and the cloud service price information includes cloud service discount information corresponding to the plan information.
  • the management server can return cloud service price information through the UI interface, and can send cloud service price information through the application program interface API, with no specific limitations.
  • the user device sends order information to the management server.
  • the user device After confirming the cloud service price information sent by the planned transaction module of the management server, the user device sends ordering information to the planned transaction module, and the ordering information is used to confirm the cloud service price information.
  • the cloud resource plan corresponding to the ordering information sent by the planned transaction module of the management server to the resource scheduling module instructs the resource scheduling module to perform cloud resource allocation tasks on the cloud server cluster.
  • the resource scheduling module of the management server saves the cloud resource plan and reserves required cloud resources.
  • the resource scheduling module of the management server saves the cloud resource plan and reserves the cloud resources required by the cloud resource plan.
  • the resource scheduling module of the management server sends a notification message to the user device.
  • the resource scheduling module of the management server sends a notification message to the user device.
  • the notification message is used to notify the user device that the cloud resources have been prepared.
  • the management server may send the notification message to the user device through message service, SMS service, email service, or a request call based on Hypertext Transfer Protocol HTTP.
  • the content of the notification message may include the applied virtual machine ID, container ID or bare metal physical ID, and is not specifically limited.
  • the resource scheduling module of the management server notifies the cloud server cluster to allocate corresponding cloud resources.
  • the resource scheduling module of the management server When the start time of the cloud resource plan is reached, the resource scheduling module of the management server notifies the cloud server cluster to allocate corresponding cloud resources. For example, the management server notifies the cloud server cluster to start virtual machines or containers.
  • the management server receives the plan information submitted by the user equipment, and generates the cloud service price corresponding to the plan information based on the plan information submitted by the user equipment and the available resource status, because the user equipment has submitted in advance the demand capacity for cloud resources in the future period. and demand specifications. Therefore, the management server can provide more accurate cloud service prices based on planning information, improving the efficiency of cloud resources.
  • FIG. 5 is a schematic flowchart of another resource management method provided by an embodiment of the present application.
  • the resource management method shown in Figure 5 includes the following steps:
  • the planned transaction module of the management server obtains the scheduling information of the cloud server cluster from the resource scheduling module.
  • the planned transaction module of the management server generates available resource status information based on the scheduling information of the cloud server cluster.
  • the planned transaction module of the management server generates cloud service price information based on available resource status information.
  • the planned transaction module of the management server generates cloud service price information based on available resource status information. Specifically, the planned transaction module of the management server can generate cloud service price information for different periods of time based on available cloud resource specifications and corresponding available cloud resource capacity for different periods in the future.
  • the management server generates available cloud resource capacity and corresponding cloud service prices for different periods. For example, the number of available g5 virtual machines from 00:00 to 6:00 is 2,000, and the cloud service price is The price is 10 yuan per unit. The number of available g5 virtual machines from 06:00 to 18:00 is 1,000 units. The cloud service price is 20 yuan per unit.
  • the user device queries available resource status information and corresponding cloud service price information.
  • the user device queries the available resource status information and the corresponding cloud service price.
  • the user device can obtain the available resource status information for sale and the corresponding cloud service price through the UI interface or API.
  • the management server can send all the cloud service price information in different periods to the user equipment, and the user equipment selects the demand period of the cloud resources, the demand capacity of the cloud resources and the demand specifications of the cloud resources. It is understandable that the cloud service price information queried by user devices at different times will fluctuate.
  • the user device sends order information to the management server.
  • the user equipment determines the ordering information based on the queried available resource status information and the corresponding cloud service price.
  • the ordering information is used to confirm the available resource status information and the corresponding cloud service price information that the user equipment chooses to purchase.
  • the ordering information includes the demand period, cloud resource demand capacity and cloud resource demand specifications confirmed by the user equipment.
  • the planning transaction module of the management server submits the cloud resources corresponding to the ordering information to the resource scheduling module.
  • the resource scheduling module of the management server saves the cloud resource plan and reserves the required cloud resources.
  • the resource scheduling module of the management server sends a notification message to the user device.
  • the resource scheduling module of the management server notifies the cloud server cluster to allocate corresponding cloud resources.
  • the management server can send the available resource status information and the corresponding cloud service price information in the future period to the user equipment based on the query request sent by the user equipment, and the user equipment selects the cloud resource demand period and cloud resources to be ordered. specifications and cloud resource capacity, thereby improving the utilization of cloud resources.
  • FIG. 6 is a schematic structural diagram of a resource management device provided by an embodiment of the present application. This device is used to implement various steps performed by the management server in the above embodiments.
  • the resource management device 600 includes a transceiver unit 601 and a processing unit 602.
  • the transceiver unit 601 is used to obtain the available resource status information of the cloud server cluster.
  • the available resource status information includes one or more of the following: available cloud resource capacity of the cloud server cluster in different periods in the future and available cloud resource specifications in different periods in the future.
  • the processing unit 602 is configured to generate cloud service price information according to the available resource status information, where the cloud service price information includes price information of multiple specifications of cloud resources.
  • the transceiver unit 601 is also used to send cloud service price information to user equipment.
  • the transceiver unit 601 is also configured to receive planning information sent by the user equipment.
  • the planning information is used to provide the management server with the user equipment's demand plan for cloud resources.
  • the planning information includes one or more of the following information: The demand period of cloud resources or the demand specifications of cloud resources.
  • the processing unit 602 is specifically configured to generate cloud service price information based on plan information and available resource status information.
  • the available cloud resource specifications in the available resource status information are consistent with the demand specifications in the planning information.
  • the processing unit 602 is specifically configured to generate cloud service discount information when the available resource status information meets the plan information, and the available cloud resource capacity in the available resource status information is greater than or equal to the target threshold.
  • the transceiver unit 601 is also configured to receive order information sent by the user equipment, and the order information is used to confirm the cloud service price information corresponding to the plan information.
  • the transceiving unit 601 is also configured to receive a query request sent by the user equipment.
  • the processing unit 602 is also configured to send available resource status information and cloud service price information to the user equipment according to the query request.
  • the transceiver unit 601 is also configured to receive order information sent by the user equipment, where the order information includes at least one specification of cloud resources selected by the user equipment and the price of the at least one specification of the cloud resource.
  • the transceiver unit 601 is also used to obtain the scheduling information of the cloud server cluster.
  • the scheduling information includes one or more of the following information: submitted cloud resource plans, cloud resource plans based on historical cloud resource change predictions. , the idle cloud resource plan that needs to be reserved, the total cloud resource plan, the maximum cloud resource plan for a single device, and the continuation plan for cloud resources in use.
  • the processing unit 602 is also configured to generate available resource status information of the cloud server cluster according to the scheduling information.
  • each unit in the device can be a separate processing element, or it can be integrated and implemented in a certain chip of the device.
  • it can also be stored in the memory in the form of a program, and a certain processing element of the device can call and execute the unit. Function.
  • all or part of these units can be integrated together or implemented independently.
  • the processing element described here can also be a processor, which can be an integrated circuit with signal processing capabilities.
  • each step of the above method or each unit above can be implemented by an integrated logic circuit of hardware in the processor element or implemented in the form of software calling through the processing element.
  • FIG 7 is a schematic structural diagram of a management server provided by an embodiment of the present application.
  • the management server 700 includes: a processor 710, a memory 720, and an interface 730.
  • the processor 710, the memory 720, and the interface 730 are coupled through a bus (not labeled in the figure).
  • the memory 720 stores instructions. When the execution instructions in the memory 720 are executed, the management server 700 executes the method executed by the management server in the above method embodiment.
  • the management server 700 may be one or more integrated circuits configured to implement the above methods, such as one or more application specific integrated circuits (ASICs), or one or more microprocessors (digital signal processors). , DSP), or one or more field programmable gate arrays (FPGA), or a combination of at least two of these integrated circuit forms.
  • ASICs application specific integrated circuits
  • DSP digital signal processors
  • FPGA field programmable gate arrays
  • the unit in the device can be implemented in the form of a processing element scheduler
  • the processing element can be a general processor, such as a central processing unit (Central Processing Unit, CPU) or other processors that can call programs.
  • CPU central processing unit
  • these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • SOC system-on-a-chip
  • the processor 710 can be a central processing unit (CPU), or other general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or a field-programmable processor.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA Field programmable gate array
  • a general-purpose processor can be a microprocessor or any conventional processor.
  • Memory 720 may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase electrically programmable read-only memory (EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (RAM), which is used as an external cache.
  • RAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • Double data rate synchronous dynamic random access memory double data date SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous link dynamic random access memory direct rambus RAM, DR RAM
  • the bus may also include a power bus, a control bus, a status signal bus, etc.
  • the bus can be a peripheral component interconnect express (PCIe) bus, an extended industry standard architecture (EISA) bus, a unified bus (unified bus, Ubus or UB), or a computer quick link (compute express link (CXL), cache coherent interconnect for accelerators (CCIX), etc.
  • PCIe peripheral component interconnect express
  • EISA extended industry standard architecture
  • CXL computer quick link
  • CXL cache coherent interconnect for accelerators
  • the bus can be divided into address bus, data bus, control bus, etc.
  • the resource management device 600 shown in Figure 6 and the management server 700 shown in Figure 7 can be the management server 101 in the system architecture shown in Figure 1 above.
  • a computer-readable storage medium is also provided.
  • Computer-executable instructions are stored in the computer-readable storage medium.
  • the processor of the device executes the computer-executed instructions
  • the device executes the above method embodiment. The method executed by the management server.
  • a computer program product includes computer-executable instructions, and the computer-executable instructions are stored in a computer-readable storage medium.
  • the processor of the device executes the computer execution instruction
  • the device executes the method executed by the management server in the above method embodiment.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the above integrated units can be implemented in the form of hardware or software functional units.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), magnetic disk or optical disk and other media that can store program code. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Development Economics (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Strategic Management (AREA)
  • Finance (AREA)
  • Signal Processing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Game Theory and Decision Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本申请实施例公开了一种云资源管理方法以及相关装置，用于提升云服务器的资源利用率。本申请实施例方法包括：获取云服务器集群的可用资源状态信息，可用资源状态信息包括以下一项或多项：云服务器集群在未来不同时段的可用云资源容量和未来不同时段的可用云资源规格。根据可用资源状态信息生成云服务价格信息，云服务价格信息包括多个规格的云资源的价格信息。向用户设备发送云服务价格信息。

Description

一种资源管理方法以及相关装置
本申请要求于2022年5月17日提交中国专利局、申请号为“202210536539.3”、申请名称为“一种资源管理方法以及相关装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及计算机领域，尤其涉及一种资源管理方法以及相关装置。
背景技术
随着云计算技术的发展，云服务的提供商将大量的计算资源通过网络连接起来构成一个巨大的资源池为用户设备提供云服务，用户设备通过资源管理服务器管理和调度资源池中的计算资源。
目前用户设备与云服务的提供商在云资源的交易过程中，用户设备向资源管理服务器发出云资源申请，云资源申请中包括计算资源的规格，例如处理器核心数和内存大小等。云服务的提供商基于当前资源池中的云资源的使用情况为用户设备提供云资源申请相应的价格信息，用户设备根据云服务提供商提供的价格信息选择订购云服务。
目前云服务的提供商仅根据用户设备在资源申请时刻的资源池中的可用资源状态信息为用户设备提供价格信息，而由于资源池中的可用资源状态信息会随着不同时刻使用的用户设备发生变化，因此，目前交易方式云服务的提供商提供的价格信息不准确，进一步导致资源池中的计算资源浪费。
发明内容
本申请实施例提供了一种资源管理方法以及相关装置，用于提升云资源的利用率。
本申请实施例第一方面提供了一种资源管理方法，该方法可以由管理服务器执行，也可以由管理服务器的部件，例如管理服务器的处理器、芯片或芯片系统等执行，还可以由能实现全部或部分管理服务器功能的逻辑模块或软件实现。以管理服务器执行为例，本申请实施例第一方面提供的资源管理方法包括：管理服务器获取云服务器集群的可用资源状态信息，可用资源状态信息包括以下一项或多项：云服务器集群在未来不同时段的可用云资源容量和未来不同时段的可用云资源规格，其中可用云资源容量包括未来时段可用的虚拟机、物理主机或容器的数量，可用云资源规格包括处理器核数、内存大小或显卡型号。管理服务器根据可用资源状态信息生成云服务价格信息，云服务价格信息包括未来不同时段的一个或者多个规格的云资源的价格信息。管理服务器向用户设备发送云服务价格信息。
本申请实施例中管理服务器能够获取云服务器集群在未来时段的可用云资源状态信息，并根据可用云资源状态信息生成相应的云服务价格，由于该云服务价格是根据未来不同时段的可用云资源类型和可用云资源容量计算得到的价格，因此，该云服务价格能准确反映出可用云资源的充足或紧缺情况，更利于云资源的销售，从而提升云服务器中云资源 的利用效率。
一种可能的实施方式中，管理服务器获取云服务器集群的可用资源状态信息之前，管理服务器接收用户设备发送的计划信息，计划信息用于向管理服务器提供用户设备对云资源的需求计划，计划信息包括以下一项或多项信息：云资源的需求时段或云资源的需求规格。管理服务器根据可用资源状态信息生成云服务价格信息的过程中，管理服务器根据计划信息和可用资源状态信息生成云服务价格信息，该云服务价格信息为计划信息所述对应的云服务价格信息。
本申请实施例中管理服务器接收用户设备提交的计划信息，并基于用户设备提交的计划信息和可用资源状态生成计划信息对应的云服务价格，由于用户设备预先提交了未来时段对云资源的需求容量和需求规格，因此，管理服务器能够基于计划信息提供更准确的云服务价格，进一步提升了云资源的利用效率。
一种可能的实施方式中，可用资源状态信息中的可用云资源规格与计划信息中的需求规格一致，管理服务器根据用户设备提交的计划信息中的需求规格确定相应的规格的云资源。
本申请实施例提供管理服务器提供的可用云资源规格与计划信息中的需求规格一致，从而可用云资源规格满足计划信息的需求规格，提升了方式的可实现性。
一种可能的实施方式中，管理服务器根据计划信息和可用资源状态信息生成云服务价格信息的过程中，当可用资源状态信息满足计划信息，且可用资源状态信息中可用云资源容量大于或等于目标阈值时，管理服务器生成云服务折扣信息。
本申请实施例中管理服务器对对于预先提交计划信息的用户设备可以提供云服务的折扣价格，从而提升了云资源的利用率。
一种可能的实施方式中，管理服务器向用户设备发送云服务价格信息之后，管理服务器接收用户设备发送的订购信息，订购信息用于确认计划信息对应的云服务价格信息。
本申请实施例中管理服务器向用户设备发送云服务价格信息之后，接收用户设备发送计划信息对应的订购请求，从而提升了方案可实现性。
一种可能的实施方式中，管理服务器向用户设备发送云服务价格信息前，管理服务器接收用户设备发送的查询请求。管理服务器根据查询请求向用户设备发送可用资源状态信息和云服务价格信息，管理服务器将未来时段的可用云资源规格以及可用云资源容量以及对应的价格都发送给用户，由用户设备选择需要订购的时段、云资源规格以及云资源容量。
本申请实施例中管理服务器可以基于用户设备发送的查询请求将未来时段的可用资源状态信息和相应的云服务价格信息发送至用户设备，由用户设备自己选择要订购的云资源需求时段、云资源规格以及云资源容量，从而提升了云资源的利用率。
一种可能的实施方式中，管理服务器根据查询请求向用户设备发送可用资源状态信息和云服务价格信息之后，管理服务器接收用户设备发送的订购信息，订购信息包括用户设备选择的至少一个规格的云资源和至少一个规格的云资源的价格。
本申请实施例中管理服务器向用户设备发送可用资源状态信息和云服务价格信息之后，接收用户设备选择的云资源需求时段、云资源规格以及云资源容量，从而提升了方案 可实现性。
一种可能的实施方式中，管理服务器获取云服务器集群的可用资源状态信息的过程中，管理服务器获取云服务器集群的调度信息，调度信息包括以下一项或多项信息：已提交的云资源计划、基于历史云资源变化预测的云资源计划、需预留的空闲云资源计划、总的云资源计划、单设备的最大云资源计划和使用中云资源的延续计划。管理服务器器根据调度信息生成云服务器集群的可用资源状态信息。具体的，管理服务器将总的云资源计划减去已提交的云资源计划、基于历史云资源变化预测的云资源计划、需预留的空闲云资源计划、使用中云资源的延续计划即可以得到不同时段的可用云资源容量。
本申请实施例中管理服务器可以定期获取云服务器集群的调度信息，并基于调度信息计算得到可用资源状态信息，从而提升了可用资源状态信息的准确性。
本申请实施例第二方面提供了一种资源管理装置，该资源管理装置包括收发单元和处理单元。其中，收发单元用于获取云服务器集群的可用资源状态信息，可用资源状态信息包括以下一项或多项：云服务器集群在未来不同时段的可用云资源容量和未来不同时段的可用云资源规格。处理单元用于根据可用资源状态信息生成云服务价格信息，云服务价格信息包括多个规格的云资源的价格信息。收发单元还用于向用户设备发送云服务价格信息。
一种可能的实施方式中，收发单元还用于接收用户设备发送的计划信息，计划信息用于向管理服务器提供用户设备对云资源的需求计划，计划信息包括以下一项或多项信息：云资源的需求时段或云资源的需求规格。处理单元具体用于根据计划信息和可用资源状态信息生成云服务价格信息。
一种可能的实施方式中，可用资源状态信息中的可用云资源规格与计划信息中的需求规格一致。
一种可能的实施方式中，处理单元具体用于当可用资源状态信息满足计划信息，且可用资源状态信息中可用云资源容量大于或等于目标阈值时，生成云服务折扣信息。
一种可能的实施方式中，收发单元还用于接收用户设备发送的订购信息，订购信息用于确认计划信息对应的云服务价格信息。
一种可能的实施方式中，收发单元还用于接收用户设备发送的查询请求。处理单元还用于根据查询请求向用户设备发送可用资源状态信息和云服务价格信息。
一种可能的实施方式中，收发单元还用于接收用户设备发送的订购信息，订购信息包括用户设备选择的至少一个规格的云资源和至少一个规格的云资源的价格。
一种可能的实施方式中，收发单元还用于获取云服务器集群的调度信息，调度信息包括以下一项或多项信息：已提交的云资源计划、基于历史云资源变化预测的云资源计划、需预留的空闲云资源计划、总的云资源计划、单设备的最大云资源计划和使用中云资源的延续计划。处理单元还用于根据调度信息生成云服务器集群的可用资源状态信息。
本申请实施例第三方面提供了一种管理服务器，包括处理器，处理器与存储器耦合，处理器用于存储指令，当指令被处理器执行时，以使得管理服务器执行上述第一方面或第一方面任意一种可能的实施方式所述的方法。
本申请实施例第四方面提供了一种计算机可读存储介质，其上存储有指令，指令被执行时，以使得计算机执行上述第一方面或第一方面任意一种可能的实施方式所述的方法。
本申请实施例第五方面提供了一种计算机程序产品，计算机程序产品中包括指令，指令被执行时，以使得计算机实现上述第一方面或第一方面任意一种可能的实施方式所述的方法。
可以理解，上述提供的任一种资源管理装置、管理服务器、计算机可读介质或计算机程序产品等所能达到的有益效果可参考对应的方法中的有益效果，此处不再赘述。
附图说明
图1为本申请实施例提供的一种云资源调度系统的系统架构示意图；
图2为本申请实施例提供的一种资源管理方法的流程示意图；
图3为本申请实施例提供的一种云资源调度计划示意图；
图4a为本申请实施例提供的另一种资源管理方法的流程示意图；
图4b为本申请实施例提供的一种管理服务器UI界面示意图；
图5为本申请实施例提供的另一种资源管理方法的流程示意图；
图6为本申请实施例提供的一种资源管理装置的结构示意图；
图7为本申请实施例提供的一种管理服务器的结构示意图。
具体实施方式
本申请实施例提供了一种资源管理方法以及相关装置，用于提升云服务器的资源利用效率。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
下面结合附图介绍本申请实施例提供的资源管理方法以及相关装置。
请参阅图1，图1为本申请实施例提供的一种云资源调度系统的系统架构示意图。如图1所示，该云资源调度系统100包括管理服务器101、云服务器102和用户设备103，其中，用户设备103通过管理服务器101与云服务器102相连接。下面具体介绍云资源调度系统100中各部分的功能。
管理服务器101用于对云服务器102提供的云资源进行管理和调度，包括收集云服务器102中所有物理主机的资源状态，对用户设备103发出新的云资源申请进行调度，以及为用户设备103提供云服务的价格信息。
管理服务器101中包括计划资源交易模块1011和资源调度模块1012，其中计算资源交易模块1011用于测算云服务器102的可用资源状态信息是否满足用户设备103的云资源申请需求，以及根据可用资源状态信息生成云服务的价格信息。资源调度模块1012用于获取云服务器102的可用资源状态信息，以及对云服务器102提供的云资源进行调度。
在一些可能的实现方式中，管理服务器101还能够对外提供可进行操作的UI界面，以及可以被调用的应用程序编程接口API。管理服务器101还能够提供对外提供云服务器102中的云资源的交易服务。管理服务器101例如OpenStack和VMware等。
云服务器102用于为用户设备103提供用云资源。云服务器103中包括多个物理主机，其中每个物理主机上部署多个虚拟机。云服务器102提供的云资源包括物理主机、虚拟机和容器。云服务器102根据管理服务器101的调度计划为用户设备103提供可用的云资源。可以理解的是，多个云服务器102也组成云服务集群，由服务器集群为用户设备103提供云服务。
用户设备103用于向管理服务器101请求云资源。具体的，用户设备103可以基于管理服务器101提供的UI界面或者web UI界面向管理服务器101发送云资源的请求，也可以通过用户设备103的应用软件向管理服务器101发送资源请求，具体不做限定。
下面以图1所示的系统架构为例，介绍本申请实施例提供的资源管理方法。
请参阅图2，图2为本申请实施例提供的一种资源管理方法的流程示意图。如图2所示，本申请实施例提供的资源管理方法包括但不限于步骤：
201.管理服务器获取云服务器集群的可用资源状态信息，可用资源状态信息包括以下一项或多项信息：云服务器集群在未来不同时段的可用云资源容量和可用云资源规格。
管理服务器获取云服务器集群的可用资源状态信息，可用资源状态信息包括以下一项或多项信息：云服务器在未来不同时段的可用云资源容量和可用云资源规格。本申请实施例中的云资源的类型包括虚拟机、物理主机和容器，其中每种类型的云资源下包括不同的规格，例如，虚拟机的规格包括处理器核数、内存大小和显卡型号。可用云资源容量包括云服务器集群可以提供给用户设备使用的虚拟机、物理主机和容器数量。
具体的，管理服务器在获取云服务器集群的可用资源状态信息的过程中，管理服务器的计划交易模块向资源调度模块查询调度信息，管理服务器的计划交易模块基于调度信息生成云服务器集群的可用资源状态信息。其中云服务器集群的调度信息包括以下一项或多项信息：已提交的云资源计划、基于历史云资源变化预测的云资源计划、需预留的空闲云资源计划、总的云资源计划、单设备的最大云资源计划和使用中云资源的延续计划。
其中，已经提交资源计划申请包括未来时段内用户设备对云资源的需求容量和需求规格，上述用户设备包括当前已提交计划信息但还未完成订购的用户设备和其他已经提交完成计划信息并完成订购的用户设备。
基于历史云资源变化预测的云资源计划是指管理服务器根据历史云资源使用情况预测 得到的未来时段云资源使用变化情况的计划。
需预留的空闲云资源计划是指管理服务为了应对突发的云资源使用需求而计划预留的云资源，需预留的空闲资源包括当前时间到计划申请开始时间中的可能出现的新用户设备的资源申请，或者计划申请开始时间之后已有用户设备的新增资源申请。
总的云资源申请计划是指云服务器集群能够提供的可供计划的最大云资源容量，包括不同资源类型下每种资源类型能够提供的最大资源容量。
单设备的最大云资源计划是指管理服务器为单个用户设备所能分配的最大云资源容量设置的云资源计划。使用中云资源的延续计划是指管理服务器为用户设备延续正在使用的云资源预留的云资源计划。
请参阅图3，图3为本申请实施例提供的一种云服务器集群的云资源容量随着时间变化的示意图。在图3所示的示例中，从0至t6时间段云资源容量的计划分配情况可以看出，在0至t6的时间段中每个时刻云服务器集群的总的云资源容量为S7，在0至t6的时间段中每个时刻云服务器集群需预留的空闲云资源容量为S6-S5，在0至t6的时间段中每个时刻使用中云资源的延续的云资源容量为S0。在t1至t4的时间段中每个时刻用户设备已提交的云资源计划1的云资源容量为S5-S3,在t0至t2的时间段中每个时刻基于历史云资源变化预测的云资源计划1中的云资源容量为S1-S0，在t3至t5的时间段中每个时刻基于历史云资源变化预测的云资源计划2中的云资源容量为S1-S0。
从图3所示的示例中可以看出，在0至t6的时间段中每个时刻单设备的最大云资源计划中的云资源容量为S3-S2，该单设备的最大云资源计划中的云资源容量是指管理服务器为单个用户设备所能分配的最大云资源容量，图中用户设备已提交的资源计划1、或者用户设备已提交的资源计划2以及用户设备已提交的资源计划3都不能超出该单设备的最大资源容量。
在图3所示的示例中，管理服务器进一步可以根据不同时段的云资源计划计算得到不同时段云服务器集群的可用云资源容量。例如，图3中总的云资源申请计划中减去需预留的空闲云资源计划、已提交的云资源计划1、已提交的云资源计划2、已提交的云资源计划3、基于历史预测的云资源计划1、基于历史预测的云资源计划2和使用中云资源的延续即可以得到可用云资源计划。该可用云资源计划可以指示未来不同时段下可用云资源容量，从图3所示的示例中可以看出，在0至t0时段以及在t5至t6时段，可用云资源容量达到最大值。
需要说明的是，在图3所示的示例中，需预留的空闲云资源计划、已提交的云资源计划、基于历史云资源变化预测的云资源计划以及使用中云资源的延续计划中云资源容量在时段内都未发生变化。在申请中的其他示例中，这些计划中的云资源容量在时段内也可以变化，例如，这些计划的云资源容量在时段内随时间变化增加或者减少。
此外，图3所示的示例仅为某一种云资源类型下的未来时段的云资源计划。对于不同的云资源类型，每一种云资源类型都有其对应的云资源计划，管理服务器可以基于未来时段的云资源计划计算不同云资源类型下的可用云资源计划。
本申请实施例中管理服务器可以定期获取云服务器集群的可用资源状态信息，也可以 基于用户设备的云资源请求触发管理服务器获取云服务器集群的可用资源状态信息，具体不做限定。
202.管理服务器根据可用资源状态信息生成云服务价格信息。
管理服务器获取可用资源状态信息之后，根据可用资源状态信息生成云服务价格信息。具体的，管理服务器可以根据可用资源那状态信息中不同时段下的可用云资源容量来生成不同时段的云服务的价格信息。当某个时段内可用云资源容量充足时，管理服务器可以生成该时段内云服务的折扣信息。
本申请实施例中管理服务器根据可用资源状态信息生成云服务价格信息的过程中，管理服务器可以根据用户设备提交的计划信息和可用资源状态信息生成计划信息对应的云服务价格信息，也可以将可用资源状态信息和相应的云服务价格信息发送至用户设备供用户设备进行选择，具体不做限定。后续图4a和图5所示的实施例会分别针对上述两种方式进行介绍。
可以理解的是，管理服务器对不同的用户设备也可以生成不同的云服务折扣信息。例如，在用户设备提交计划信息的场景下，管理服务器可以根据用户设备的云资源需求总量生成不同的折扣信息。再例如，管理服务器可以针对不同的用户等级生成不同的折扣信息。
203.管理服务器向用户设备发送云服务价格信息。
管理服务器向用户设备发送云服务价格信息。用户设备接收管理服务器发送的云服务价格信息之后，向管理服务器发送订购信息，该订购信息用于确认云服务价格信息。管理服务器根据订购信息为用户设备预留订购信息对应的云资源。
本申请实施例中管理服务器能够获取云服务器集群在未来时段的可用云资源状态信息，并根据可用云资源状态信息生成相应的云服务价格，由于该云服务价格是根据未来不同时段的可用云资源类型和可用云资源容量计算得到的价格，因此，该云服务价格能准确反映出可用云资源的充足或紧缺的情况，管理服务器按照该云服务价格对与服务器的云资源进行销售，从而提升云服务器中云资源的利用率。
下面分别结合图4a和图5分别对用户设备提交计划信息和管理服务器提供可用资源状态信息两种方式进行介绍。
请参阅图4a，图4a为本申请实施例提供的另一种资源管理方法的流程示意图。图4a所示的资源管理方法包括以下步骤：
401.用户设备向管理服务器提交计划信息。
用户设备向管理服务器提交计划信息，该计划信息用于向管理服务器提供用户设备对云资源的需求计划，计划信息包括以下一项或多项信息：云资源的需求时段、云资源需求容量和云资源的需求规格。云资源的类型代号可以代表云资源的类型，例如，云资源的类型代号g5代表16核处理器、32g内存、RTX5000显卡的虚拟机。
本申请实施例中用户设备可以通过多种方式提交计划信息，例如，管理服务器可以通过管理服务器的UI界面提交计划信息，也可以通过应用程序接口API调用管理服务器中的计划交易模块提交计划信息，具体不做限定。
在步骤401的一个示例中，用户设备在2022年3月30日向管理服务器的计划交易模块的计划信息中包括：用户设备申请100台虚拟机，虚拟机的类型为g5、需求开始时间为2022年4月1日0：00，结束时间为2022年4月15日24：00。
请参阅图4b，图4b为本申请实施例提供的一种管理服务器的UI界面示意图。在图4b所示的示例中，用户设备可以通过管理服务器的UI界面提交用户设备的计划信息，用户设备提交的计划信息包括不同计划时间段的云资源的需求规格和云资源的需求容量。例如，用户设备在2022年4月1日至2022年4月30日的6:00—12:00，云资源的需求规格为G4型虚拟机,云资源的需求容量为100台。
402.管理服务器的计划交易模块从资源调度模块获取云服务器集群的调度信息。
管理服务器的计划交易模块从资源调度模块获取云服务器集群的调度信息，调度信息包括以下一项或多项信息：已提交的云资源计划、基于历史云资源变化预测的云资源计划、需预留的空闲云资源计划、总的云资源计划、单设备的最大云资源计划和使用中云资源的延续计划。
本申请实施例中，管理服务器的计划交易模块可以定期从资源调度模块查询云服务器集群的调度信息，也可以基于用户设备提交计划信息触发查询调度信息，或者资源调度模块也可以定期向计划交易模块上报调度信息，具体不做限定。
403.管理服务器的计划交易模块根据云服务器集群的调度信息生成可用资源状态信息。
管理服务器的计划交易模块根据云服务器集群的调度信息生成可用资源状态信息。具体的，管理服务器的计划交易模块根据调度信息生成的可用资源状态信息包括以下一项或多项：未来不同可用时段内的可用云资源容量或可用云资源规格。
例如，在步骤403的一个示例中，管理服务器的计划交易模块根据调度信息生成的可用资源状态信息为2022年4月1日至2022年4月15日0：00至6：00，虚拟机类型为g4的可用云资源容量为5000台虚拟机，2022年4月1日至2022年4月15日6：00至18：00，虚拟机类型为g4的可用云资源容量为3000台虚拟机。
404.管理服务器的计划交易模块根据计划信息和可用资源状态信息生成云服务价格信息。
管理服务器的计划交易模块根据计划信息和可用资源状态信息生成云服务价格信息，该云服务价格信息包括计划信息所对应的云服务价格。进一步，当可用资源状态信息满足计划信息，且可用资源状态信息中可用云资源容量大于或等于第一阈值，则管理服务器生成云服务折扣信息。另外可用资源状态信息中可用云资源规格需要与计划信息中云资源的需求规格一致。
本申请实施例中由于用户设备向管理服务器提交了计划信息，因此管理服务器能够更好的计算可用资源状态信息，管理服务器可以向提交计划信息的用户设备设计更多的云服务价格折扣。
405.管理服务器的计划交易模块向用户设备发送云服务价格信息。
管理服务器的计划交易模块向用户设备发送云服务价格信息，该云服务价格信息中包 括计划信息对应的云服务折扣信息。具体的，管理服务器可以通过UI界面返回云服务价格信息，可以通过应用程序接口API发送云服务价格信息，具体不做限定。
406.用户设备向管理服务器发送订购信息。
用户设备确认管理服务器的计划交易模块发送的云服务价格信息之后，向计划交易模块发送订购信息，该订购信息用于确认云服务价格信息。
407.管理服务器的计划交易模块向资源调度模块发送的订购信息对应的云资源计划。
管理服务器的计划交易模块向资源调度模块发送的订购信息对应的云资源计划，该云资源计划指示资源调度模块对云服务器集群执行云资源的分配任务。
408.管理服务器的资源调度模块保存云资源计划，预留所需的云资源。
管理服务器的资源调度模块保存云资源计划，预留云资源计划所需的云资源。
409.管理服务器的资源调度模块向用户设备发送通知消息。
管理服务器的资源调度模块向用户设备发送通知消息，该通知消息用于向用户设备通知云资源已经准备完成。
本申请实施例中管理服务器向用户设备发送通知消息的方式可以是消息服务、短信服务、邮件服务或基于超文本传输协议HTTP的请求调用等方式。通知消息的内容可以包括申请的虚拟机ID、容器ID或者裸金属物理ID，具体不做限定。
410.当到达计划时间时，管理服务器的资源调度模块通知云服务器集群分配对应的云资源。
当到达云资源计划的开始时间时，管理服务器的资源调度模块通知云服务器集群分配对应的云资源。例如，管理服务器通知云服务器集群启动虚拟机或容器。
本申请实施例中管理服务器接收用户设备提交的计划信息，并基于用户设备提交的计划信息和可用资源状态生成计划信息对应的云服务价格，由于用户设备预先提交了未来时段对云资源的需求容量和需求规格，因此，管理服务器能够基于计划信息提供更准确的云服务价格，提升了云资源的利效率。
请参阅图5，图5为本申请实施例提供的另一种资源管理方法的流程示意图。图5所示的资源管理方法包括以下步骤：
501.管理服务器的计划交易模块从资源调度模块获取云服务器集群的调度信息。
502.管理服务器的计划交易模块根据云服务器集群的调度信息生成可用资源状态信息。
本申请实施实施例步骤501至步骤502中管理服务器所执行的操作与上述图4a所示的实施例中的步骤402至步骤403中管理服务器所执行的操作类似，具体不再赘述。
503.管理服务器的计划交易模块根据可用资源状态信息生成云服务价格信息。
管理服务器的计划交易模块根据可用资源状态信息生成云服务价格信息。具体的，管理服务器的计划交易模块可以根据未来不同时段的可用云资源规格和对应的可用云资源容量生成不同时段的云服务价格信息。
例如，在步骤503的一个示例中，管理服务器生成不同时段可用云资源容量以及对应 的云服务价格，例如，00:00至6:00的g5型可用虚拟机数量为2000台，云服务价格为10元每台，06:00至18:00的g5型可用虚拟机数量为1000台，云服务价格为20元每台。
504.用户设备查询可用资源状态信息和对应的云服务价格信息。
用户设备查询可用资源状态信息和对应的云服务价格，用户设备可以通过UI界面或者API获取待销售的可用资源状态信息和对应的云服务价格。
本申请实施例中管理服务器可以将不同时段的云服务价格信息全部发送至用户设备，由用户设备选择云资源的需求时段、云资源需求容量和云资源的需求规格。可以理解的是，用户设备在不同时刻查询到的云服务价格信息会产生浮动。
505.用户设备向管理服务器发送订购信息。
用户设备基于查询到的可用资源状态信息和对应的云服务价格确定订购信息，订购信息用于确认用户设备选择购买的可用资源状态信息以及对应的云服务价格信息。订购信息中包括用户设备确认订购的云资源的需求时段、云资源需求容量和云资源的需求规格。
506.管理服务器的计划交易模块向资源调度模块提交订购信息对应的云资源。
507.管理服务器的资源调度模块保存云资源计划，预留所需的云资源。
508.管理服务器的资源调度模块向用户设备发送通知消息。
509.当到达计划时间时，管理服务器的资源调度模块通知云服务器集群分配对应的云资源。
本申请实施实施例步骤506至步骤509中管理服务器所执行的操作与上述图4a所示的实施例中的步骤407至步骤410中管理服务器所执行的操作类似，具体不再赘述。
本申请实施例中管理服务器可以基于用户设备发送的查询请求将未来时段的可用资源状态信息和相应的云服务价格信息发送至用户设备，由用户设备自己选择要订购的云资源需求时段、云资源规格以及云资源容量，从而提升了云资源的利用率。
以上介绍本申请实施例中提供的资源管理方法，下面结合附图介绍本申请实施例提供的相关装置。
请参阅图6，图6为本申请实施例提供的一种资源管理装置的结构示意图。该装置用于实现上述各实施例中管理服务器所执行的各个步骤，如图6所示，该资源管理装置600包括收发单元601和处理单元602。
其中，收发单元601用于获取云服务器集群的可用资源状态信息，可用资源状态信息包括以下一项或多项：云服务器集群在未来不同时段的可用云资源容量和未来不同时段的可用云资源规格。处理单元602用于根据可用资源状态信息生成云服务价格信息，云服务价格信息包括多个规格的云资源的价格信息。收发单元601还用于向用户设备发送云服务价格信息。
一种可能的实施方式中，收发单元601还用于接收用户设备发送的计划信息，计划信息用于向管理服务器提供用户设备对云资源的需求计划，计划信息包括以下一项或多项信息：云资源的需求时段或云资源的需求规格。处理单元602具体用于根据计划信息和可用资源状态信息生成云服务价格信息。
一种可能的实施方式中，可用资源状态信息中的可用云资源规格与计划信息中的需求规格一致。
一种可能的实施方式中，处理单元602具体用于当可用资源状态信息满足计划信息，且可用资源状态信息中可用云资源容量大于或等于目标阈值时，生成云服务折扣信息。
一种可能的实施方式中，收发单元601还用于接收用户设备发送的订购信息，订购信息用于确认计划信息对应的云服务价格信息。
一种可能的实施方式中，收发单元601还用于接收用户设备发送的查询请求。处理单元602还用于根据查询请求向用户设备发送可用资源状态信息和云服务价格信息。
一种可能的实施方式中，收发单元601还用于接收用户设备发送的订购信息，订购信息包括用户设备选择的至少一个规格的云资源和至少一个规格的云资源的价格。
一种可能的实施方式中，收发单元601还用于获取云服务器集群的调度信息，调度信息包括以下一项或多项信息：已提交的云资源计划、基于历史云资源变化预测的云资源计划、需预留的空闲云资源计划、总的云资源计划、单设备的最大云资源计划和使用中云资源的延续计划。处理单元602还用于根据调度信息生成云服务器集群的可用资源状态信息。
应理解以上装置中单元的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且装置中的单元可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分单元以软件通过处理元件调用的形式实现，部分单元以硬件的形式实现。例如，各个单元可以为单独设立的处理元件，也可以集成在装置的某一个芯片中实现，此外，也可以以程序的形式存储于存储器中，由装置的某一个处理元件调用并执行该单元的功能。此外这些单元全部或部分可以集成在一起，也可以独立实现。这里所述的处理元件又可以成为处理器，可以是一种具有信号的处理能力的集成电路。在实现过程中，上述方法的各步骤或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路实现或者以软件通过处理元件调用的形式实现。
值得说明的是，对于上述方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本申请本申请并不受所描述的动作顺序的限制，其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作并不一定是本申请本申请所必须的。
本领域的技术人员根据以上描述的内容，能够想到的其他合理的步骤组合，也属于本申请本申请的保护范围内。其次，本领域技术人员也应该熟悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作并不一定是本申请本申请所必须的。
请参阅图7，图7为本申请实施例提供的一种管理服务器的结构示意图。如图7所示，该管理服务器700包括：处理器710、存储器720和接口730，处理器710、存储器720与接口730通过总线(图中未标注)耦合。存储器720存储有指令，当存储器720中的执行指令被执行时，管理服务器700执行上述方法实施例中管理服务器所执行的方法。
管理服务器700可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(application specific integrated circuit，ASIC)，或，一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(field  programmable gate array，FPGA)，或这些集成电路形式中至少两种的组合。再如，当装置中的单元可以通过处理元件调度程序的形式实现时，该处理元件可以是通用处理器，例如中央处理器(central processing unit，CPU)或其它可以调用程序的处理器。再如，这些单元可以集成在一起，以片上系统(system-on-a-chip，SOC)的形式实现。
处理器710可以是中央处理单元(central processing unit，CPU)，还可以是其它通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
存储器720可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data date SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
总线除包括数据总线之外，还可以包括电源总线、控制总线和状态信号总线等。总线可以是快捷外围部件互连标准(peripheral component interconnect express，PCIe)总线，或扩展工业标准结构(extended industry standard architecture，EISA)总线、统一总线(unified bus，Ubus或UB)、计算机快速链接(compute express link，CXL)、缓存一致互联协议(cache coherent interconnect for accelerators，CCIX)等。总线可以分为地址总线、数据总线、控制总线等。
可以理解的是，本申请实施例中图6所示的资源管理装置600和图7所示的管理服务器700可以是上述图1所示的系统架构中的管理服务器101。
在本申请的另一个实施例中，还提供一种计算机可读存储介质，计算机可读存储介质中存储有计算机执行指令，当设备的处理器执行该计算机执行指令时，设备执行上述方法实施例中管理服务器所执行的方法。
在本申请的另一个实施例中，还提供一种计算机程序产品，该计算机程序产品包括计算机执行指令，该计算机执行指令存储在计算机可读存储介质中。当设备的处理器执行该计算机执行指令时，设备执行上述方法实施例中管理服务器所执行的方法。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的 划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，read-only memory)、随机存取存储器(RAM，random access memory)、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (19)

  1. 一种资源管理方法，其特征在于，包括：
    获取云服务器集群的可用资源状态信息，所述可用资源状态信息包括以下一项或多项：所述云服务器集群在未来不同时段的可用云资源容量和未来不同时段的可用云资源规格；
    根据所述可用资源状态信息生成云服务价格信息，所述云服务价格信息包括多个规格的云资源的价格信息；
    向用户设备发送所述云服务价格信息。
  2. 根据权利要求1所述的方法，其特征在于，所述获取云服务器集群的可用资源状态信息之前，所述方法还包括：
    接收用户设备发送的计划信息，所述计划信息用于向管理服务器提供所述用户设备对云资源的需求计划，所述计划信息包括以下一项或多项信息：云资源的需求时段或云资源的需求规格；
    所述根据所述可用资源状态信息生成云服务价格信息包括：
    根据所述计划信息和所述可用资源状态信息生成云服务价格信息。
  3. 根据权利要求2所述的方法，其特征在于，所述可用资源状态信息中的可用云资源规格与所述计划信息中的需求规格一致。
  4. 根据权利要求2或3所述的方法，其特征在于，所述根据所述计划信息和所述可用资源状态信息生成云服务价格信息包括：
    当所述可用资源状态信息满足所述计划信息，且所述可用资源状态信息中可用云资源容量大于或等于目标阈值时，生成云服务折扣信息。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述向用户设备发送所述云服务价格信息之后，所述方法还包括：
    接收所述用户设备发送的订购信息，所述订购信息用于确认所述计划信息对应的云服务价格信息。
  6. 根据权利要求1所述的方法，其特征在于，所述向用户设备发送所述云服务价格信息前，所述方法还包括：
    接收所述用户设备发送的查询请求；
    根据所述查询请求向所述用户设备发送所述可用资源状态信息和所述云服务价格信息。
  7. 根据权利要求6所述的方法，其特征在于，所述根据所述查询请求向所述用户设备发送所述可用资源状态信息和所述云服务价格信息之后，所述方法还包括：
    接收所述用户设备发送的订购信息，所述订购信息包括所述用户设备选择的至少一个规格的云资源和所述至少一个规格的云资源的价格。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述获取云服务器集群的可用资源状态信息包括：
    获取所述云服务器集群的调度信息，所述调度信息包括以下一项或多项信息：已提交的云资源计划、基于历史云资源变化预测的云资源计划、需预留的空闲云资源计划、总的 云资源计划、单设备的最大云资源计划和使用中云资源的延续计划；
    根据所述调度信息生成所述云服务器的可用资源状态信息。
  9. 一种资源管理装置，其特征在于，包括：
    收发单元，用于获取云服务器集群的可用资源状态信息，所述可用资源状态信息包括以下一项或多项：所述云服务器集群在未来不同时段的可用云资源容量和未来不同时段的可用云资源规格；
    处理单元，用于根据所述可用资源状态信息生成云服务价格信息，所述云服务价格信息包括多个规格的云资源的价格信息；
    所述收发单元还用于向用户设备发送所述云服务价格信息。
  10. 根据权利要求9所述的装置，其特征在于，所述收发单元还用于接收用户设备发送的计划信息，所述计划信息用于向管理服务器提供所述用户设备对云资源的需求计划，所述计划信息包括以下一项或多项信息：云资源的需求时段或云资源的需求规格；
    所述处理单元具体用于根据所述计划信息和所述可用资源状态信息生成云服务价格信息。
  11. 根据权利要求10所述的装置，其特征在于，所述可用资源状态信息中的可用云资源规格与所述计划信息中的需求规格一致。
  12. 根据权利要求10或11所述的装置，其特征在于，所述处理单元具体用于：
    当所述可用资源状态信息满足所述计划信息，且所述可用资源状态信息中可用云资源容量大于或等于目标阈值时，生成云服务折扣信息。
  13. 根据权利要求9至12中任一项所述的装置，其特征在于，所述收发单元还用于：
    接收所述用户设备发送的订购信息，所述订购信息用于确认所述计划信息对应的云服务价格信息。
  14. 根据权利要求9所述的装置，其特征在于，所述收发单元还用于接收所述用户设备发送的查询请求；
    所述处理单元还用于根据所述查询请求向所述用户设备发送所述可用资源状态信息和所述云服务价格信息。
  15. 根据权利要求14所述的装置，其特征在于，所述收发单元还用于：
    接收所述用户设备发送的订购信息，所述订购信息包括所述用户设备选择的至少一个规格的云资源和所述至少一个规格的云资源的价格。
  16. 根据权利要求9至15中任一项所述的装置，其特征在于，所述收发单元还用于：
    获取所述云服务器集群的调度信息，所述调度信息包括以下一项或多项信息：已提交的云资源计划、基于历史云资源变化预测的云资源计划、需预留的空闲云资源计划、总的云资源计划、单设备的最大云资源计划和使用中云资源的延续计划；
    所述处理单元还用于根据所述调度信息生成所述云服务器集群的可用资源状态信息。
  17. 一种管理服务器，其特征在于，包括处理器，所述处理器与存储器耦合，所述处理器用于存储指令，当所述指令被所述处理器执行时，以使得所述管理服务器执行权利要求1至8中任一项所述的方法。
  18. 一种计算机可读存储介质，其上存储有指令，其特征在于，所述指令被执行时，以使得计算机执行权利要求1至8中任一项所述的方法。
  19. 一种计算机程序产品，所述计算机程序产品中包括指令，其特征在于，所述指令被执行时，以使得计算机实现权利要求1至8中任一项所述的方法。
PCT/CN2022/133401 2022-05-17 2022-11-22 一种资源管理方法以及相关装置 WO2023221444A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210536539.3 2022-05-17
CN202210536539.3A CN117130761A (zh) 2022-05-17 2022-05-17 一种资源管理方法以及相关装置

Publications (1)

Publication Number Publication Date
WO2023221444A1 true WO2023221444A1 (zh) 2023-11-23

Family

ID=88834486

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/133401 WO2023221444A1 (zh) 2022-05-17 2022-11-22 一种资源管理方法以及相关装置

Country Status (2)

Country Link
CN (1) CN117130761A (zh)
WO (1) WO2023221444A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117971512A (zh) * 2024-04-02 2024-05-03 杭州骋风而来数字科技有限公司 一种算力智能调度系统和方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111866062A (zh) * 2020-06-02 2020-10-30 北京邮电大学 一种云服务交易的可信协商方法及装置
CN111885147A (zh) * 2020-07-20 2020-11-03 兰州理工大学 边缘计算中的一种资源动态定价方法
US10938674B1 (en) * 2016-07-01 2021-03-02 EMC IP Holding Company LLC Managing utilization of cloud computing resources
US20210232479A1 (en) * 2020-01-24 2021-07-29 Netapp, Inc. Predictive reserved instance for hyperscaler management
CN113626199A (zh) * 2021-08-19 2021-11-09 京东科技信息技术有限公司 闲置云计算资源的管理方法、装置、电子设备和存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10938674B1 (en) * 2016-07-01 2021-03-02 EMC IP Holding Company LLC Managing utilization of cloud computing resources
US20210232479A1 (en) * 2020-01-24 2021-07-29 Netapp, Inc. Predictive reserved instance for hyperscaler management
CN111866062A (zh) * 2020-06-02 2020-10-30 北京邮电大学 一种云服务交易的可信协商方法及装置
CN111885147A (zh) * 2020-07-20 2020-11-03 兰州理工大学 边缘计算中的一种资源动态定价方法
CN113626199A (zh) * 2021-08-19 2021-11-09 京东科技信息技术有限公司 闲置云计算资源的管理方法、装置、电子设备和存储介质

Also Published As

Publication number Publication date
CN117130761A (zh) 2023-11-28

Similar Documents

Publication Publication Date Title
US9635103B2 (en) Dynamic virtual resource request rate control for utilizing physical resources
Jin et al. Towards optimized fine-grained pricing of IaaS cloud platform
US10296971B2 (en) Providing real-time trading of virtual infrastructure resources
US9626210B2 (en) Resource credit pools for replenishing instance resource credit balances of virtual compute instances
CN111176796B (zh) 用于虚拟计算机资源调度的滚动资源信贷
US9529633B2 (en) Variable timeslices for processing latency-dependent workloads
US9294236B1 (en) Automated cloud resource trading system
US9760928B1 (en) Cloud resource marketplace for third-party capacity
US20110145094A1 (en) Cloud servicing brokering
US10037501B2 (en) Energy management costs for a data center
US9985848B1 (en) Notification based pricing of excess cloud capacity
US9240025B1 (en) Dynamic pricing of network-accessible resources for stateful applications
WO2019205791A1 (zh) 为多个用户标识调整流量套餐的方法及装置
US20110208606A1 (en) Information Technology Services E-Commerce Arena for Cloud Computing Environments
US9246986B1 (en) Instance selection ordering policies for network-accessible resources
WO2023221444A1 (zh) 一种资源管理方法以及相关装置
US11783237B2 (en) Dynamic modification of interruptibility settings for network-accessible resources
CN108833296A (zh) 批处理速率的控制方法和装置
CN114461374A (zh) 一种实例分配方法、系统及装置
WO2022083764A1 (zh) 一种实例分配方法、系统及装置
US10601905B2 (en) Priority switching based on resource usage patterns
US10922666B1 (en) Resource management for logical and physical availability zones of a provider network
Sutagundar et al. Development of fog based dynamic resource allocation and pricing model in IoT
WO2023142920A1 (zh) 一种云服务计费方法以及装置
CN109995539A (zh) 一种ocs的流量授权方法、ocs、服务器及可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22942464

Country of ref document: EP

Kind code of ref document: A1