Method and device for changing specification of cloud server in shrinkage manner and related components

Abstract

The invention discloses a method and device for changing the specification of a cloud server in a shrinkage mode and a related assembly. The method comprises the steps that a specification changing request of a user is received through a management interface assembly; judging whether the specification change request meets a shrinkage matching condition or not through the control service component, and if yes, selecting a current host where the cloud server is located as a target host; if not, executing a predetermined host selection method and selecting a target host; after the target host is selected, controlling the target host to complete a specification changing process through the periodic management component, and creating a cloud server with a new specification on the node through the information of the cloud server; and the cloud server information is updated according to the received confirmation instruction or the cloud server of the new specification is rolled back to the cloud server of the original specification according to the received rollback instruction. According to the invention, when a larger specification is changed into a smaller specification, the existing resources are used for changing, additional resources do not need to be redistributed, and the resource utilization rate and the changing success rate are improved.

Description

Technical Field

[0001] The present invention relates to the field of cloud computing technology, and in particular to a method, device and related components for reducing the size of a cloud server. Background Art

[0002] With the rapid development of cloud computing technology, OpenStack, as an open source cloud computing management platform, has been widely used in many enterprises and data centers. Through its rich components and flexible architecture, OpenStack provides users with a full range of cloud service management functions including computing, storage and network. Among them, the specification change of cloud servers is a key function, which allows users to dynamically adjust the resource configuration of cloud servers according to actual needs, such as CPU, memory, disk size, etc., to adapt to different application scenarios and workloads.

[0003] In a traditional OpenStack environment, when a user needs to change the specifications of a cloud server, the system usually requires reallocation of resources according to the new specifications. This means that if the resources required for the target specifications (such as the number of CPU cores, memory capacity, etc.) cannot be met in the current environment, or if there are resource constraints (such as the resources of the physical host are already heavily occupied by other virtual machines), the specification change operation may fail. This resource limitation not only affects the user's flexibility and usage experience, but may also cause business interruption or performance degradation, especially in a multi-tenant environment with fierce resource competition.

[0004] Specifically, when OpenStack receives a request to change the specifications of a cloud server, the system will first check the resource status of the current cluster to determine whether there are enough resources to meet the new specifications. This check process includes evaluating the remaining computing power, memory capacity, storage space, and network connection resources of the physical host. If the resources are insufficient, even if it is only temporary, the system will reject the specification change request and return a corresponding error message to the user. Summary of the invention

[0005] The purpose of the present invention is to provide a method, device and related components for reducing the size of cloud server specifications, aiming to solve the problems of high failure rate of specification change in existing specification change methods under resource constraints.

[0006] In a first aspect, an embodiment of the present invention provides a method for reducing the size of a cloud server specification, including:

[0007] receiving specification change requests from users through the management interface component;

[0008] Determine whether the specification change request satisfies the downsizing and reconfiguration condition by controlling the service component. If so, select the current host where the cloud server is located as the destination host; if not, execute a predetermined host selection method and select the destination host.

[0009] After the destination host is selected, the cycle management component controls the destination host to complete the specification change process, and creates a cloud server of new specifications on the node based on the cloud server information, and updates the cloud server information according to the received confirmation instruction or rolls back the cloud server of new specifications to the cloud server of original specifications according to the received rollback instruction.

[0010] In a second aspect, an embodiment of the present invention further provides a device for reducing the size of a cloud server, including:

[0011] A management interface component for receiving specification change requests from users;

[0012] The control service component is used to determine whether the specification change request meets the downsizing and reconfiguration conditions, and if so, select the current host where the cloud server is located as the destination host; if not, execute a predetermined host selection method and select the destination host;

[0013] The cycle management component is used to control the destination host to complete the specification change process after the destination host is selected, and to create a cloud server of new specifications on the node through the information of the cloud server, and to update the cloud server information according to the received confirmation instruction or to roll back the cloud server of new specifications to the cloud server of original specifications according to the received rollback instruction.

[0014] In a third aspect, an embodiment of the present invention further provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method for reducing the size of a cloud server specification as described in the first aspect when executing the computer program.

[0015] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements the method for reducing the size of the cloud server specifications as described in the first aspect.

[0016] The present invention discloses a method, device and related components for changing the specifications of a cloud server in a reduced amount. The method includes: receiving a user's specification change request through a management interface component; judging whether the specification change request meets the reduced amount change condition through a control service component, if it meets the condition, selecting the current host where the cloud server is located as the destination host; if it does not meet the condition, executing a predetermined host selection method and selecting the destination host; after the destination host is selected, controlling the destination host through a cycle management component to complete the specification change process, and creating a cloud server of a new specification on the node through the information of the cloud server, and updating the cloud server information according to the received confirmation instruction or rolling back the cloud server of the new specification to the cloud server of the original specification according to the received rollback instruction. When changing from a larger specification to a smaller specification, the present invention directly uses existing resources for change without reallocating additional resources, thereby improving resource utilization and the success rate of the change. The embodiment of the present invention also provides a device, computer equipment and readable storage medium for changing the specifications of a cloud server in a reduced amount, which has the above-mentioned beneficial effects and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying any creative work.

[0018] Figure 1 A schematic diagram of an application environment of the method for reducing the size of a cloud server according to the present invention;

[0019] Figure 2 A flowchart of a method for changing cloud server specifications for scaling down;

[0020] Figure 3 A first sub-flow chart of a method for changing the specifications of a cloud server in a reduced volume;

[0021] Figure 4 A second sub-flow chart of the method for reducing the size of a cloud server;

[0022] Figure 5 A third sub-flow chart of the method for changing the specifications of a cloud server for scaling down;

[0023] Figure 6 A schematic block diagram of an apparatus for changing the specifications of a cloud server for scaling down;

[0024] Figure 7 A schematic block diagram of a computer device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0025] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0026] It should be understood that when used in this specification and the appended claims, the terms "include" and "comprises" indicate the presence of described features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or combinations thereof.

[0027] It should also be understood that the terms used in this specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. As used in the specification of the present invention and the appended claims, the singular forms "a", "an" and "the" are intended to include plural forms unless the context clearly indicates otherwise.

[0028] It should be further understood that the term "and / or" used in the present description and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0029] See also Figure 1-5 The present invention provides a method for reducing the size of a cloud server and changing its specifications, which can be applied in Figure 1In the application environment, the client and the server communicate through the network. The method is executed by Openstack installed on the server. Openstack is an open source cloud computing management platform project and a combination of a series of software open source projects. OpenStack aims to provide software for the construction and management of public and private clouds, helping service providers and enterprises to implement cloud infrastructure services (Infrastructure as a Service) similar to Amazon ec2 and S3, and provide scalable and elastic cloud computing services for private and public clouds. OpenStack includes Nova components. Nova components are virtual server deployment and business computing modules developed by NASA. They are computing components of OpenStack and are responsible for managing virtual machines. They mainly include management interface components nova-api, control service components nova-conductor, task scheduling and allocation components nova-scheduler, cycle management components nova-compute, and call interface components nova-placement. The Openstack on the server side can receive the specification change request sent by the client through the management interface component nova-api; then the control service component nova-conductor determines whether the specification change request meets the conditions for scaling down and re-allocation. If the conditions for scaling down and re-allocation are met, the current host where the cloud server is located is selected as the destination host; if the conditions for scaling down and re-allocation are not met, the predetermined host selection method is executed and the destination host is selected; after the destination host is selected, the cycle management component nova-compute controls the destination host to complete the specification change process, and creates a cloud server of a new specification on the node through the information of the cloud server, and updates the cloud server information according to the received confirmation instruction or rolls back the cloud server of the new specification to the cloud server of the original specification according to the received rollback instruction. Among them, the client can be but is not limited to various personal computers, laptops, smart phones, tablets and portable wearable devices. The server can be implemented with an independent server or a server cluster consisting of multiple servers.

[0030] The management interface component nova-api is responsible for providing management functions for virtual machine instances, network resources, and storage volumes in the nova component. Through nova-api, users can manage and control cloud computing resources in a standardized way to achieve efficient resource utilization and flexible configuration.

[0031] The control service component nova-conductor is responsible for handling communication and task management between services in the nova component. By introducing nova-conductor, the security and scalability of the system are enhanced, while the efficiency of resource management is optimized.

[0032] The control service component nova-scheduler is responsible for scheduling and allocating tasks for virtual machine instances in the nova component. It ensures that virtual machine instances can run in the best position through a series of algorithms and strategies to achieve optimal resource utilization and system stability.

[0033] The lifecycle management component nova-compute is responsible for handling the lifecycle management of virtual machine instances in the nova component. It receives requests through the message queue and performs operations such as creation, termination, and migration of virtual machines.

[0034] The call interface component nova-placement is the component responsible for resource management and scheduling in the nova component. It provides a unified resource management interface, allowing other OpenStack services to query and report resource usage, thereby enabling effective resource scheduling and management.

[0035] See also Figure 2 As shown, Figure 2 A flowchart of a method for reducing the size of a cloud server provided by an embodiment of the present invention includes the following steps:

[0036] S101: receiving a specification change request from a user through a management interface component;

[0037] Specifically, receiving the user's specification change request through the management interface component (i.e., nova-api) includes: receiving the user's specification change request; then authenticating the specification change request and verifying the parameters (such as whether the specification exists, etc.); if the authority is sufficient and the parameter input is normal, sending the specification change request to the control service component (i.e., nova-conductor) through the creation request method; if the authority is insufficient or the parameter input is abnormal, ending the specification change.

[0038] Among them, the specification is the configuration of a cloud server instance, including the number of vCPU cores, memory size, network performance, etc. Due to various reasons such as increased business volume and cost reduction, users will need to continuously adjust the specifications of their cloud servers to achieve the best cost-effectiveness and service effect. Changing the specifications means that additional resources will be allocated to the new specifications to meet the requirements of the cloud server specification change. This involves the consumption of resources such as the CPU and memory of the host machine. In this process, the resources required for the old and new specifications are occupied. If a larger specification changes to a smaller specification, the CPU and memory resources required are equivalent to a change from large to small. Therefore, when allocating resources, the resources occupied by the original specifications of the cloud server can be allocated to the new specifications.

[0039] This embodiment effectively prevents unauthorized access and illegal operations through authentication and parameter verification, thereby improving the security of the system. Parameter verification ensures the legitimacy of input data and prevents invalid or erroneous data from entering the system, thereby ensuring the integrity and consistency of the data.

[0040] In one embodiment, receiving a user's specification change request through the management interface component nova-api includes: receiving the user's specification change request; then authenticating and verifying parameters of the specification change request; then judging whether the specification change request is valid (i.e., vaild); if the specification change request is valid, creating a request through a create request method (i.e., createbuild) and judging whether the creation is successful; if the creation is successful, sending the specification change request to the control service component through the create request method; if the creation is unsuccessful, feeding back a fault code resp 202 to the user; if the specification change request is invalid, feeding back a fault code resp 40x to the user.

[0041] Clear error information feedback (such as fault code resp 202, resp 40x) can help users find and correct problems in a timely manner, improving user experience. At the same time, standardized change request processing procedures help reduce system failures and errors and improve system reliability and stability.

[0042] S102: determining, by the control service component, whether the specification change request satisfies a reduction and reconfiguration condition; if so, selecting the current host where the cloud server is located as the destination host; if not, executing a predetermined host selection method and selecting the destination host;

[0043] Specifically, the control service component determines whether the specification change request meets the decrement change condition, including:

[0044] Determine whether the new vcpu in the specification change request is less than or equal to the original vcpu, and whether the new memory in the specification change request is less than or equal to the original memory;

[0045] If the vcpu of the new specification in the specification change request is less than or equal to the vcpu of the original specification, and the memory of the new specification in the specification change request is less than or equal to the memory of the original specification, then determine whether the type of the new specification in the specification change request is consistent with the type of the original specification, and whether the attribute of the new specification in the specification change request is consistent with the attribute of the original specification;

[0046] If the vcpu of the new specification in the specification change request is larger than the vcpu of the original specification or the memory of the new specification in the specification change request is larger than the memory of the original specification, it is determined that the reduction and reconfiguration conditions are not met.

[0047] The determining whether the type of the new specification in the specification change request is consistent with the type of the original specification, and whether the attribute of the new specification in the specification change request is consistent with the attribute of the original specification includes:

[0048] If the type of the new specification in the specification change request is consistent with the type of the original specification, and the attributes of the new specification in the specification change request are consistent with the attributes of the original specification, then it is determined that the reduction and replacement conditions are met;

[0049] If the type of the new specification in the specification change request is inconsistent with the type of the original specification, or the attribute of the new specification in the specification change request is inconsistent with the attribute of the original specification, it is determined that the reduction and replacement conditions are not met.

[0050] Through strict conditional judgment, the system can ensure that the specification change request meets the conditions for reducing quantity and changing configuration, thereby effectively preventing waste of resources and improving system stability and effective use of resources.

[0051] It should be noted that this embodiment does not limit the order of judging whether the vcpu of the new specification in the specification change request is less than or equal to the vcpu of the original specification, whether the memory of the new specification in the specification change request is less than or equal to the memory of the original specification, whether the type of the new specification in the specification change request is consistent with the type of the original specification, and whether the attributes of the new specification in the specification change request are consistent with the attributes of the original specification. The corresponding judgment order can be selected according to the actual situation, or the judgment can be made at the same time. For example, it can be judged in turn whether the type of the new specification in the specification change request is consistent with the type of the original specification, whether the attributes of the new specification in the specification change request are consistent with the attributes of the original specification, whether the vcpu of the new specification in the specification change request is less than or equal to the vcpu of the original specification, and whether the memory of the new specification in the specification change request is less than or equal to the memory of the original specification. It can also be other judgment orders, and this embodiment will not elaborate on this.

[0052] Specifically, the specification type is used to distinguish the architecture, so judging whether the type of the new specification in the specification change request is consistent with the type of the original specification includes: judging whether the hardware platform of the new specification in the specification change request (such as x86 and ARM) is consistent with the hardware platform of the original specification; and judging whether the architecture of the new specification in the specification change request (such as a stand-alone instance and a cluster instance) is consistent with the architecture of the original specification. If the hardware platform of the new specification in the specification change request is consistent with the hardware platform of the original specification, and the architecture of the new specification in the specification change request is consistent with the architecture of the original specification, then it is judged that the type of the new specification in the specification change request is consistent with the type of the original specification. If the hardware platform of the new specification in the specification change request is inconsistent with the hardware platform of the original specification, or the architecture of the new specification in the specification change request is inconsistent with the architecture of the original specification, then it is judged that the type of the new specification in the specification change request is inconsistent with the type of the original specification.

[0053] By ensuring that the new specifications are consistent with the original specifications in terms of hardware platform and architecture, technical compatibility issues caused by specification changes can be avoided, thereby improving system stability and reliability.

[0054] In this embodiment, the attributes include a configuration method for non-uniform memory access (NUMA). If NUMA is not configured in the specification or is configured to 0, NUMA is not enabled. If it is configured to 1, it is a single NUMA node configuration for the host, that is, the vCPU and memory required by the cloud server are obtained from the single NUMA node of the host. If it is configured to 2, the vCPU and memory are obtained evenly from each NUMA node of the host.

[0055] Determining whether the attributes of the new specification in the specification change request are consistent with the attributes of the original specification includes:

[0056] Extract the NUMA configuration value from the new specification in the specification change request (denoted as A). Extract the NUMA configuration value from the original specification (denoted as B).

[0057] If A is 0 or not configured, and B is also 0 or not configured, it is determined that the attributes of the new specification in the specification change request are consistent with the attributes of the original specification.

[0058] If A is 1 and B is also 1, it is determined that the attributes of the new specification in the specification change request are consistent with the attributes of the original specification.

[0059] If A is 2 and original_numa_config is also 2, it is determined that the attributes of the new specification in the specification change request are consistent with the attributes of the original specification.

[0060] Except for the above three cases, in the rest, A and B do not match (for example, A is 1 and B is 2), and it is determined that the attributes of the new specification in the specification change request are inconsistent with the attributes of the original specification.

[0061] By ensuring consistent NUMA configuration, you can ensure that the performance of the virtual machine instance after the specification change is consistent with that before the change, avoiding performance fluctuations caused by different NUMA configurations. At the same time, different NUMA configurations will affect the allocation of vCPUs and memory. Consistent NUMA configuration can avoid resource allocation imbalance or resource contention problems.

[0062] In this embodiment, the reconfiguration of the size is to reconfigure the specifications through the resources currently owned by the cloud server, and it does not need to reallocate resources to it, thereby achieving the purpose of saving resources. Therefore, if the reconfiguration conditions are met, the host where the cloud server is currently located must be specified as the destination host and the record type must be set as decrement-resize, and then the next process can be continued. At the same time, because the reconfiguration of the size is to use the existing resources of the cloud server, it does not need to allocate resources to the new specifications through placement. If the reconfiguration of the new specifications is not a reconfiguration of the size, it is necessary to allocate resources to the new specifications through placement.

[0063] Specifically, executing a predetermined host selection method and selecting a destination host includes:

[0064] The control service component sends the instruction to the task scheduling component (nova-scheduler) to execute the original adjustment (resize) process. Then, the task scheduling component obtains the list of hosts that meet the resource conditions from the resource allocation (placement) according to the new specifications of vcpu and memory, and then obtains the optimal destination host list through the filter and weight calculation. The filter will filter out the hosts that meet the requirements of these filter conditions according to a series of filters such as vcpu filter (filtering hosts that meet the vcpu requirements of cloud servers), memory filter (filtering hosts that meet the memory requirements of cloud servers), and computing node filter (filtering hosts where computing nodes are running). Then the weight will be arranged according to the vcpu margin, memory margin, and the number of hosts that failed to create cloud servers. The higher the priority, the more it is placed in front to obtain a sorted list. Then the task scheduling component nova-scheduler will return the sorted list to the control service component nova-conductor, and finally the control service component nova-conductor selects the first host from the sorted list as the destination host, that is, selects the optimal host as the destination host.

[0065] This embodiment uses the task scheduling component (nova-scheduler) to obtain a list of hosts that meet the conditions from the resource allocation (placement) service according to the new vcpu and memory requirements, ensuring accurate matching and efficient use of resources. At the same time, the filter mechanism (such as vcpu filter, memory filter, etc.) further selects hosts that meet specific requirements, avoiding waste and over-allocation of resources.

[0066] After the destination host is selected, the control service component nova-conductor will use the prep_resize method to package the request and send it to the cycle management component nova-compute of the destination host for the next process.

[0067] Specifically, the control service component nova-conductor will use the prep_resize method to package the request and send it to the cycle management component nova-compute of the destination host, including:

[0068] The control service component nova-conductor queries the source host information from the database, including the current status and configuration of the virtual machine instance. At the same time, it obtains detailed information about the virtual machine instance, including UUID, current specifications, status, etc. Then the control service component nova-conductor constructs the request data, including the following key information: UUID of the virtual machine instance: identifies the virtual machine instance to be changed. New specifications (flavor): describes the new resource requirements such as vCPU, memory, disk, etc. Source host information: information about the host currently running the virtual machine instance. Destination host information: information about the optimal destination host selected. Migration type: decrement-resize, indicating that this is a migration to reduce specifications. Then the control service component nova-conductor creates a migration record in the database, recording relevant information about the migration, such as migration type, source host, destination host, etc. The control service component nova-conductor sends the request data to the cycle management component nova-compute of the destination host through a message queue (such as RabbitMQ).

[0069] The prep_resize method allows the destination host to reserve the required resources in advance to ensure resource availability during the specification change process. The prep_resize method also ensures that the state of the virtual machine instance is effectively managed during the specification change process to avoid state confusion.

[0070] S103: After the destination host is selected, the cycle management component is used to control the destination host to complete the specification change process, and a cloud server of a new specification is created on the node according to the cloud server information, and the cloud server information is updated according to the received confirmation instruction or the cloud server of the new specification is rolled back to the cloud server of the original specification according to the received rollback instruction.

[0071] Specifically, if the type of the new specification is decrement-resize (i.e., re-allocation by reducing the capacity), there is no need to verify the rationality of resources such as cpu and memory, nor is there any need to allocate additional resources to the new specifications of the cloud server. The resource allocation of the new specification is obtained from the resources originally allocated to the original specifications of the cloud server. For example, if the specifications of the original cloud server are allocated with the resources of a certain host numa 1, the required cpu and memory and other resources are taken from the resources allocated by numa 1 to the cloud server of the new specification. Because the result of the specification change is in a pending confirmation state, the resources occupied by the original specification on the host cannot be released, and the re-allocation operation is performed on the same host. The resources used by the new specification at this time are taken from the vcpu and memory occupied by the original specification on the host. Therefore, before the cloud server updates the cloud server information according to the received confirmation instruction (confirm) or rolls back the cloud server of the new specification to the cloud server of the original specification according to the received rollback instruction (revert), the resource occupation on the destination host is still based on the original specification.

[0072] In this embodiment, after the step of creating a cloud server of a new specification on the node using the information of the cloud server, the following steps are included:

[0073] The user's command request is received through the management interface component, and the command request is authenticated and parameter checked. If the authority is sufficient and the parameter input is normal, the command request is sent to the cycle management component through the creation request method. If the authority is insufficient or the parameter input is abnormal, the user's command request is terminated; wherein the command request is a confirmation command or a rollback command.

[0074] This embodiment effectively prevents unauthorized access and illegal operations through authentication and parameter verification, thereby improving the security of the system. Parameter verification ensures the legitimacy of input data and prevents invalid or erroneous data from entering the system, thereby ensuring the integrity and consistency of the data.

[0075] In one embodiment, see Figure 4 and Figure 5 After the step of creating a cloud server of a new specification on the node through the information of the cloud server, the process includes: receiving the user's instruction request through the management interface component; then authenticating and verifying the specification change request; then judging whether the specification change request is valid (i.e., vaild); if the specification change request is valid, creating a request through a create request method (i.e., create build) and judging whether the creation is successful; if the creation is successful, sending the instruction request to the cycle management component through the create request method; if the creation is unsuccessful, feeding back a fault code resp 202 to the user; if the specification change request is invalid, feeding back a fault code resp 40x to the user.

[0076] Clear error information feedback (such as fault code resp 202, resp 40x) can help users find and correct problems in a timely manner, improving user experience. At the same time, standardized change request processing procedures help reduce system failures and errors and improve system reliability and stability.

[0077] Furthermore, updating the cloud server information according to the received confirmation instruction includes: updating the information of the cloud server with a new specification into the database record of the cloud server through the cycle management component; determining whether the change to the new specification is a reduction in capacity; if the change to the new specification is a reduction in capacity, releasing the excess resources of the original specification and creating a resource inventory record according to the new specification; if the change to the new specification is not a reduction in capacity, releasing all resources occupied by the original specification.

[0078] Specifically, if the instruction is a confirm instruction, the cycle management component nova-compute will submit the result of changing the cloud server to the new specification. Then the cloud server information will be updated, and the new specification information will be updated to the database records related to the cloud server, such as the specification information in the metadata information of the cloud server. According to the type of change, it is determined whether it is a reduction and re-allocation. If the type is decrement-resize, it is a reduction and re-allocation. The excess resources of the original specification will be released. The excess resources are the resources occupied by the original specification minus the resources required for the new specification, and a resource inventory (allocation) record will be created according to the new specification, and the process ends. If it is not a reduction and re-allocation, the cloud server will release all the resources occupied by the original specification, and the process ends.

[0079] Since the original configuration update process involves reallocating resources for the current specification, the process generates an allocation record after the resources are allocated to the target node. In contrast, the reduced configuration update process uses the resources occupied by the original specification for update, so no new allocation record is created. In this process, the record of resource occupancy only exists in the resource list of the original specification. When the process is submitted, the resource list of the original specification will be deleted. To ensure the normal operation of the system and avoid interference with other cloud server operations involving resource occupancy, a resource list occupancy record of the current specification should be created at this time. The resource list, as a list of resources occupied by the cloud server on the node, covers key resources such as virtual CPU (vcpu), memory, and disk.

[0080] In one embodiment, when the user issues a confirm command, the management interface component nova-api will send a request to the cycle management component nova-compute after authentication and parameter verification. The cycle management component nova-compute will release the resources that are not needed for the new specification and create a resource inventory record for the cloud server of the new specification by calling the interface component nova-placement to ensure that the resource inventory is normal.

[0081] In this embodiment, rolling back the cloud server of new specifications to the cloud server of original specifications according to the received rollback instruction includes: recovering the information of the cloud server of new specifications through the cycle management component; judging whether the change of the new specifications is a reduction in capacity; if the change of the new specifications is a reduction in capacity, rolling back the information of the cloud server of new specifications to the cloud server of original specifications; if the change of the new specifications is not a reduction in capacity, recovering the resources allocated to the new specifications and rolling back the information of the cloud server of new specifications to the cloud server of original specifications.

[0082] Specifically, if the instruction is a revert rollback instruction, the cycle management component nova-compute will roll back the cloud server of the new specification to the cloud server of the original specification. For example, first recycle the cloud server of the new specification, including the recycling of its related information, such as network, disk, etc. Then determine whether the change of the new specification is a reduction in allocation. If the type of the changed specification is decrement, it is a reduction in allocation. Since the cloud server of the new specification uses the resources of the original specification, there is no need to roll back the resources allocated to the new specification. If it is not a reduction in allocation, the resources allocated to the new specification by the destination host need to be recycled. Finally, the cloud server of the new specification is rolled back to the cloud server of the original specification through the network, disk and other information of the cloud server, and the process ends.

[0083] The revert rollback process is to roll back the cloud server in the pending confirmation state to the cloud server of the original specifications. When the user changes his specifications by mistake, the cloud server in the pending confirmation state can be rolled back to the previous cloud server, thus avoiding potential problems and costs caused by specification changes.

[0084] Through the above method, this embodiment can directly use existing resources to make changes when changing from a larger specification to a smaller specification, without reallocating additional resources, thereby saving computing resource consumption and improving computing node resource utilization and change success rate.

[0085] See also Figure 6 This embodiment provides a device 500 for reducing the size of a cloud server, including:

[0086] Management interface component 501, used to receive specification change request from user;

[0087] The control service component 502 is used to determine whether the specification change request meets the reduction and reconfiguration conditions. If the reduction and reconfiguration conditions are met, the current host where the cloud server is located is selected as the destination host; if the reduction and reconfiguration conditions are not met, a predetermined host selection method is executed to select the destination host;

[0088] The cycle management component 503 is used to control the destination host to complete the specification change process after the destination host is selected, and to create a cloud server of new specifications on the node through the information of the cloud server, and to update the cloud server information according to the received confirmation instruction or to roll back the cloud server of new specifications to the cloud server of original specifications according to the received rollback instruction.

[0089] Furthermore, the management interface component 501 includes:

[0090] A receiving unit, used for receiving a specification change request from a user;

[0091] An authentication unit, used for authenticating and verifying parameters of the specification change request;

[0092] A creation unit, configured to, if the authority is sufficient and the parameter input is normal, send the specification change request to the control service component by creating a request method;

[0093] The end unit is used to end the specification change if the authority is insufficient or the parameter input is abnormal.

[0094] Among them, the specification is the configuration of a cloud server instance, including the number of vCPU cores, memory size, network performance, etc. Due to various reasons such as increased business volume and cost reduction, users will need to continuously adjust the specifications of their cloud servers to achieve the best cost-effectiveness and service effect. Changing the specifications means that additional resources will be allocated to the new specifications to meet the requirements of the cloud server specification change. This involves the consumption of resources such as the CPU and memory of the host machine. In this process, the resources required for the old and new specifications are occupied. If a larger specification changes to a smaller specification, the CPU and memory resources required are equivalent to a change from large to small. Therefore, when allocating resources, the resources occupied by the original specifications of the cloud server can be allocated to the new specifications.

[0095] In addition, the management interface component nova-api is the component in the nova component responsible for providing management functions for virtual machine instances, network resources, and storage volumes. Through nova-api, users can manage and control cloud computing resources in a standardized way to achieve efficient resource utilization and flexible configuration.

[0096] The control service component nova-conductor is responsible for handling communication and task management between services in the nova component. By introducing nova-conductor, the security and scalability of the system are enhanced, while the efficiency of resource management is optimized.

[0097] This embodiment effectively prevents unauthorized access and illegal operations through authentication and parameter verification, thereby improving the security of the system. Parameter verification ensures the legitimacy of input data and prevents invalid or erroneous data from entering the system, thereby ensuring the integrity and consistency of the data.

[0098] Furthermore, the control service component 502 includes:

[0099] A first judgment unit is used to judge whether the vcpu of the new specification in the specification change request is less than or equal to the vcpu of the original specification, and whether the memory of the new specification in the specification change request is less than or equal to the memory of the original specification;

[0100] a second judgment unit, configured to judge whether the type of the new specification in the specification change request is consistent with the type of the original specification, and whether the attribute of the new specification in the specification change request is consistent with the attribute of the original specification, if the vcpu of the new specification in the specification change request is less than or equal to the vcpu of the original specification, and the memory of the new specification in the specification change request is less than or equal to the memory of the original specification;

[0101] The first determination unit is used to determine that the downsizing condition is not met if the vcpu of the new specification in the specification change request is larger than the vcpu of the original specification or the memory of the new specification in the specification change request is larger than the memory of the original specification.

[0102] Furthermore, the control service component 502 also includes:

[0103] A second determination unit, configured to determine that the reduction and re-allocation condition is met if the type of the new specification in the specification change request is consistent with the type of the original specification, and the attribute of the new specification in the specification change request is consistent with the attribute of the original specification;

[0104] The third determination unit is configured to determine that the reduction and re-matching condition is not met if the type of the new specification in the specification change request is inconsistent with the type of the original specification, or the attribute of the new specification in the specification change request is inconsistent with the attribute of the original specification.

[0105] Through strict conditional judgment, the system can ensure that the specification change request meets the conditions for reducing quantity and changing configuration, thereby effectively preventing waste of resources and improving system stability and effective use of resources.

[0106] Specifically, the specification type is used to distinguish the architecture, so judging whether the type of the new specification in the specification change request is consistent with the type of the original specification includes: judging whether the hardware platform of the new specification in the specification change request (such as x86 and ARM) is consistent with the hardware platform of the original specification; and judging whether the architecture of the new specification in the specification change request (such as a stand-alone instance and a cluster instance) is consistent with the architecture of the original specification. If the hardware platform of the new specification in the specification change request is consistent with the hardware platform of the original specification, and the architecture of the new specification in the specification change request is consistent with the architecture of the original specification, the second judgment unit judges that the type of the new specification in the specification change request is consistent with the type of the original specification. If the hardware platform of the new specification in the specification change request is inconsistent with the hardware platform of the original specification, or the architecture of the new specification in the specification change request is inconsistent with the architecture of the original specification, the third judgment unit judges that the type of the new specification in the specification change request is inconsistent with the type of the original specification.

[0107] Furthermore, the management interface component 501 also includes:

[0108] The instruction sending unit is used to receive the user's instruction request after the step of creating a cloud server of a new specification on the node through the information of the cloud server, authenticate and verify the parameters of the instruction request, and if the authority is sufficient and the parameter input is normal, send the instruction request to the cycle management component through the creation request method; if the authority is insufficient or the parameter input is abnormal, terminate the user's instruction request; wherein, the instruction request is a confirmation instruction or a rollback instruction.

[0109] This embodiment effectively prevents unauthorized access and illegal operations through authentication and parameter verification, thereby improving the security of the system. Parameter verification ensures the legitimacy of input data and prevents invalid or erroneous data from entering the system, thereby ensuring the integrity and consistency of the data.

[0110] Furthermore, the cycle management component 503 includes:

[0111] An updating unit, used to update the information of the cloud server of the new specification into the database record of the cloud server;

[0112] The first reduction determination unit is used to determine whether the change of the new specification is a reduction change;

[0113] A record creation unit is used to release the redundant resources of the original specification if the change of the new specification is a reduction in quantity and to create a resource list record according to the new specification;

[0114] The release unit is used to release all resources occupied by the original specification if the change to the new specification is not a reduction in quantity.

[0115] Specifically, if the instruction is a confirm instruction, the cycle management component nova-compute will submit the result of changing the cloud server to the new specification. Then the update unit will update the information of the cloud server, and update the information of the new specification to the database records related to the cloud server, such as the specification information in the metadata information of the cloud server. The first reduction judgment unit determines whether it is a reduction and reconfiguration based on the type of change. If the type is decrement-resize, it is a reduction and reconfiguration. The record creation unit releases the excess resources of the original specification. The excess resources are the resources occupied by the original specification minus the resources required for the new specification, and creates a resource list (allocation) record according to the new specification, and the process ends. If it is not a reduction and reconfiguration, the release unit releases all resources occupied by the original specification, and the process ends.

[0116] Since the original configuration update process involves reallocating resources for the current specification, the process generates an allocation record after the resources are allocated to the target node. In contrast, the reduced configuration update process uses the resources occupied by the original specification for update, so no new allocation record is created. In this process, the record of resource occupancy only exists in the resource list of the original specification. When the process is submitted, the resource list of the original specification will be deleted. To ensure the normal operation of the system and avoid interference with other cloud server operations involving resource occupancy, a resource list occupancy record of the current specification should be created at this time. The resource list, as a list of resources occupied by the cloud server on the node, covers key resources such as virtual CPU (vcpu), memory, and disk.

[0117] Furthermore, the cycle management component 503 also includes:

[0118] A recycling unit, used to recycle information of cloud servers of new specifications;

[0119] The second reduction determination unit is used to determine whether the change of the new specification is a reduction in quantity;

[0120] A rollback unit, used to roll back the information of the cloud server of the new specification to the cloud server of the original specification if the change of the new specification is a reduction in quantity;

[0121] The resource recovery unit is used to recover the resources allocated to the new specification and roll back the information of the cloud server of the new specification to the cloud server of the original specification if the change of the new specification is not a reduction in capacity.

[0122] Specifically, if the instruction is a revert rollback instruction, the cycle management component nova-compute will roll back the cloud server of the new specification to the cloud server of the original specification. For example, the recycling unit first recycles the cloud server of the new specification, including the recycling of its related information, such as network, disk, etc. Then the second reduction judgment unit determines whether the change of the new specification is a reduction and re-allocation. If the type of the change specification is decrement, it is a reduction and re-allocation. Because the cloud server of the new specification uses the resources of the original specification, there is no need to roll back the resources allocated to the new specification. If it is not a reduction and re-allocation, the resource recovery unit needs to recycle the resources allocated to the new specification by the destination host. Finally, the cloud server of the new specification is rolled back to the cloud server of the original specification through the network, disk and other information of the cloud server, and the process ends.

[0123] The revert rollback process is to roll back the cloud server in the pending confirmation state to the cloud server of the original specifications. When the user changes his specifications by mistake, the cloud server in the pending confirmation state can be rolled back to the previous cloud server, thus avoiding potential problems and costs caused by specification changes.

[0124] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-mentioned devices and components can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here.

[0125] The above-mentioned device for reducing the size of the cloud server specification can be implemented in the form of a computer program, which can be used in the following ways: Figure 7 Runs on the computer device shown.

[0126] See also Figure 7 , Figure 7 6 is a schematic block diagram of a computer device provided by an embodiment of the present invention. The computer device 600 includes a processor 602 , a memory and a network interface 605 connected via a system bus 601 , wherein the memory may include a non-volatile storage medium 603 and an internal memory 604 .

[0127] The non-volatile storage medium 603 can store an operating system 6031 and a computer program 6032. When the computer program 6032 is executed, the processor 602 can execute the intelligent prediction method of disability assessment terms based on data processing.

[0128] The processor 602 is used to provide computing and control capabilities and support the operation of the entire computer device 600.

[0129] The internal memory 604 provides an environment for the operation of the computer program 6032 in the non-volatile storage medium 603. When the computer program 6032 is executed by the processor 602, the processor 602 can execute an intelligent prediction method for disability assessment terms based on data processing.

[0130] The network interface 605 is used for network communication, such as providing data information transmission, etc. Those skilled in the art will understand that Figure 7 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present invention, and does not constitute a limitation on the computer device 600 to which the solution of the present invention is applied. The specific computer device 600 may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0131] Among them, the processor 602 is used to run the computer program 6032 stored in the memory to achieve the following functions: receiving the user's specification change request through the management interface component; judging whether the specification change request meets the downsizing and reconfiguration conditions through the control service component, if the downsizing and reconfiguration conditions are met, selecting the current host where the cloud server is located as the destination host; if the downsizing and reconfiguration conditions are not met, executing the predetermined host selection method and selecting the destination host; after the destination host is selected, controlling the destination host through the cycle management component to complete the specification change process, and creating a cloud server of new specifications on the node through the information of the cloud server, and updating the cloud server information according to the received confirmation instruction or rolling back the cloud server of new specifications to the cloud server of original specifications according to the received rollback instruction.

[0132] In one embodiment, when the processor 602 executes the step of receiving the user's specification change request through the management interface component, it performs the following operations: receiving the user's specification change request; authenticating and verifying the parameters of the specification change request; if the authority is sufficient and the parameter input is normal, sending the specification change request to the control service component by creating a request method; if the authority is insufficient or the parameter input is abnormal, ending the specification change.

[0133] In one embodiment, when the processor 602 executes the control service component to determine whether the specification change request meets the condition of downsizing, the processor 602 performs the following operations: determine whether the vcpu of the new specification in the specification change request is less than or equal to the vcpu of the original specification, and whether the memory of the new specification in the specification change request is less than or equal to the memory of the original specification; if the vcpu of the new specification in the specification change request is less than or equal to the vcpu of the original specification, and the memory of the new specification in the specification change request is less than or equal to the memory of the original specification, then determine whether the type of the new specification in the specification change request is consistent with the type of the original specification, and whether the attributes of the new specification in the specification change request are consistent with the attributes of the original specification; if the vcpu of the new specification in the specification change request is greater than the vcpu of the original specification or the memory of the new specification in the specification change request is greater than the memory of the original specification, then determine that the downsizing condition is not met.

[0134] In one embodiment, when the processor 602 executes the step of determining whether the type of the new specification in the specification change request is consistent with the type of the original specification, and whether the attributes of the new specification in the specification change request are consistent with the attributes of the original specification, it performs the following operations: if the type of the new specification in the specification change request is consistent with the type of the original specification, and the attributes of the new specification in the specification change request are consistent with the attributes of the original specification, it is determined that the reduction and re-matching condition is met; if the type of the new specification in the specification change request is inconsistent with the type of the original specification, or the attributes of the new specification in the specification change request are inconsistent with the attributes of the original specification, it is determined that the reduction and re-matching condition is not met.

[0135] In one embodiment, when the processor 602 executes the step of creating a cloud server of a new specification on the node through the information of the cloud server, it performs the following operations: receiving the user's instruction request through the management interface component, authenticating and verifying the parameters of the instruction request, and if the authority is sufficient and the parameter input is normal, sending the instruction request to the cycle management component through the creation request method; if the authority is insufficient or the parameter input is abnormal, terminating the user's instruction request; wherein, the instruction request is a confirmation instruction or a rollback instruction.

[0136] In one embodiment, when the processor 602 executes the step of updating the cloud server information according to the received confirmation instruction, it performs the following operations: updating the information of the cloud server of the new specification to the database record of the cloud server through the cycle management component; determining whether the change of the new specification is a reduction in capacity; if the change of the new specification is a reduction in capacity, releasing the excess resources of the original specification and creating a resource inventory record according to the new specification; if the change of the new specification is not a reduction in capacity, releasing all resources occupied by the original specification.

[0137] In one embodiment, when the processor 602 executes the step of rolling back the cloud server of new specifications to the cloud server of original specifications according to the received rollback instruction, the processor 602 performs the following operations: recovering the information of the cloud server of new specifications through the cycle management component; determining whether the change of the new specifications is a reduction in size; if the change of the new specifications is a reduction in size, rolling back the information of the cloud server of new specifications to the cloud server of original specifications; if the change of the new specifications is not a reduction in size, recovering the resources allocated to the new specifications and rolling back the information of the cloud server of new specifications to the cloud server of original specifications.

[0138] Those skilled in the art will understand that Figure 7The embodiments of the computer device shown in the figure do not constitute a limitation on the specific composition of the computer device. In other embodiments, the computer device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. For example, in some embodiments, the computer device may only include a memory and a processor. In such embodiments, the structure and function of the memory and the processor are the same as those of the embodiment of the present invention. Figure 7 The embodiments shown are consistent and will not be described again here.

[0139] It should be understood that in the embodiment of the present invention, the processor 602 may be a central processing unit (CPU), and the processor 602 may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0140] In another embodiment of the present invention, a computer-readable storage medium is provided. The computer-readable storage medium may be a non-volatile computer-readable storage medium. The computer-readable storage medium stores a computer program, wherein the computer program implements the following steps when executed by a processor: receiving a user's specification change request through a management interface component; determining whether the specification change request satisfies a reduction and reconfiguration condition through a control service component, and if the reduction and reconfiguration condition is met, selecting the current host where the cloud server is located as the destination host; if the reduction and reconfiguration condition is not met, executing a predetermined host selection method and selecting a destination host; after the destination host is selected, controlling the destination host through a cycle management component to complete the specification change process, and creating a cloud server of a new specification on the node through the information of the cloud server, and updating the cloud server information according to the received confirmation instruction or rolling back the cloud server of the new specification to the cloud server of the original specification according to the received rollback instruction.

[0141] In one embodiment, the receiving of a user's specification change request through a management interface component includes: receiving a user's specification change request; authenticating and verifying parameters of the specification change request; if the authority is sufficient and the parameter input is normal, sending the specification change request to the control service component through a create request method; if the authority is insufficient or the parameter input is abnormal, ending the specification change.

[0142] In one embodiment, the determining whether the specification change request satisfies the downsizing condition by controlling the service component includes: determining whether the vcpu of the new specification in the specification change request is less than or equal to the vcpu of the original specification, and whether the memory of the new specification in the specification change request is less than or equal to the memory of the original specification; if the vcpu of the new specification in the specification change request is less than or equal to the vcpu of the original specification, and the memory of the new specification in the specification change request is less than or equal to the memory of the original specification, determining whether the type of the new specification in the specification change request is consistent with the type of the original specification, and whether the attributes of the new specification in the specification change request are consistent with the attributes of the original specification; if the vcpu of the new specification in the specification change request is greater than the vcpu of the original specification or the memory of the new specification in the specification change request is greater than the memory of the original specification, determining that the downsizing condition is not met.

[0143] In one embodiment, the judging whether the type of the new specification in the specification change request is consistent with the type of the original specification, and whether the attribute of the new specification in the specification change request is consistent with the attribute of the original specification includes: if the type of the new specification in the specification change request is consistent with the type of the original specification, and the attribute of the new specification in the specification change request is consistent with the attribute of the original specification, then it is judged that the reduction and re-matching condition is met; if the type of the new specification in the specification change request is inconsistent with the type of the original specification, or the attribute of the new specification in the specification change request is inconsistent with the attribute of the original specification, then it is judged that the reduction and re-matching condition is not met.

[0144] In one embodiment, after the step of creating a cloud server of a new specification on the node through the information of the cloud server, it includes: receiving the user's instruction request through the management interface component, authenticating and verifying the parameters of the instruction request, and if the authority is sufficient and the parameter input is normal, sending the instruction request to the cycle management component through the creation request method; if the authority is insufficient or the parameter input is abnormal, terminating the user's instruction request; wherein, the instruction request is a confirmation instruction or a rollback instruction.

[0145] In one embodiment, updating the cloud server information according to the received confirmation instruction includes: updating the information of the cloud server of the new specification into the database record of the cloud server through the cycle management component; determining whether the change of the new specification is a reduction in capacity; if the change of the new specification is a reduction in capacity, releasing the excess resources of the original specification and creating a resource inventory record according to the new specification; if the change of the new specification is not a reduction in capacity, releasing all resources occupied by the original specification.

[0146] In one embodiment, rolling back the cloud server of new specifications to the cloud server of original specifications according to the received rollback instruction includes: recycling the information of the cloud server of new specifications through the cycle management component; judging whether the change of the new specifications is a reduction in capacity; if the change of the new specifications is a reduction in capacity, rolling back the information of the cloud server of new specifications to the cloud server of original specifications; if the change of the new specifications is not a reduction in capacity, recycling the resources allocated to the new specifications and rolling back the information of the cloud server of new specifications to the cloud server of original specifications.

[0147] The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same and similar parts between the various embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description. It should be pointed out that for ordinary technicians in this technical field, without departing from the principle of the present invention, several improvements and modifications can be made to the present invention, and these improvements and modifications also fall within the scope of protection of the claims of the present invention.

[0148] It should also be noted that, in this specification, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprises", or any other variations thereof are intended to cover non-exclusive.

[0149] Inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of more restrictions, the elements defined by the sentence "including a..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

Claims

1. A method for reducing the size of a cloud server specification, characterized in that: include: receiving specification change requests from users through the management interface component; Determine whether the specification change request satisfies the downsizing and reconfiguration condition by controlling the service component. If so, select the current host where the cloud server is located as the destination host; if not, execute a predetermined host selection method and select the destination host. After the destination host is selected, the cycle management component controls the destination host to complete the specification change process, and creates a cloud server of new specifications on the node based on the cloud server information, and updates the cloud server information according to the received confirmation instruction or rolls back the cloud server of new specifications to the cloud server of original specifications according to the received rollback instruction.

2. The method for reducing the size of a cloud server according to claim 1, characterized in that: Receiving a user's specification change request through the management interface component includes: Receive specification change requests from users; Authenticating and verifying parameters of the specification change request; If the authority is sufficient and the parameter input is normal, the specification change request is sent to the control service component through a create request method; If the authority is insufficient or the parameter input is abnormal, the specification change is terminated.

3. The method for reducing the size of a cloud server according to claim 1, characterized in that: The determining whether the specification change request satisfies the condition of reducing the quantity and changing the configuration by controlling the service component includes: Determine whether the vcpu of the new specification in the specification change request is less than or equal to the vcpu of the original specification, and whether the memory of the new specification in the specification change request is less than or equal to the memory of the original specification; If the vcpu of the new specification in the specification change request is less than or equal to the vcpu of the original specification, and the memory of the new specification in the specification change request is less than or equal to the memory of the original specification, then determine whether the type of the new specification in the specification change request is consistent with the type of the original specification, and whether the attribute of the new specification in the specification change request is consistent with the attribute of the original specification; If the vcpu of the new specification in the specification change request is larger than the vcpu of the original specification or the memory of the new specification in the specification change request is larger than the memory of the original specification, it is determined that the reduction and reconfiguration condition is not met.

4. The method for reducing the size of a cloud server according to claim 3, characterized in that: The determining whether the type of the new specification in the specification change request is consistent with the type of the original specification, and whether the attribute of the new specification in the specification change request is consistent with the attribute of the original specification includes: If the type of the new specification in the specification change request is consistent with the type of the original specification, and the attribute of the new specification in the specification change request is consistent with the attribute of the original specification, it is determined that the reduction and re-allocation condition is met; If the type of the new specification in the specification change request is inconsistent with the type of the original specification, or the attribute of the new specification in the specification change request is inconsistent with the attribute of the original specification, it is determined that the reduction and re-matching condition is not met.

5. The method for reducing the size of a cloud server according to claim 1, characterized in that: After the step of creating a cloud server of a new specification on the node using the information of the cloud server, the method further includes: The management interface component receives the user's command request, authenticates and verifies the parameters of the command request. If the authority is sufficient and the parameter input is normal, the command request is sent to the cycle management component by creating a request method. If the authority is insufficient or the parameter input is abnormal, the user's command request is terminated; wherein the command request is a confirmation command or a rollback command.

6. The method for reducing the size of a cloud server according to claim 5, characterized in that: The updating of cloud server information according to the received confirmation instruction includes: Updating the information of the cloud server of the new specification into the database record of the cloud server through the cycle management component; Determine whether the change to the new specification is a reduction in quantity; If the change to the new specification is to reduce the quantity and re-allocate, the excess resources of the original specification will be released, and a resource list record will be created according to the new specification; If the change to the new specification is not a reduction in quantity, all resources occupied by the original specification will be released.

7. The method for reducing the size of a cloud server according to claim 5, characterized in that: The step of rolling back the cloud server of the new specification to the cloud server of the original specification according to the received rollback instruction includes: Recovering information of cloud servers of new specifications through the cycle management component; Determine whether the change to the new specification is a reduction in quantity; If the new specification is a downsizing change, the information of the new specification cloud server will be rolled back to the original specification cloud server; If the change to the new specification is not a reduction in capacity, the resources allocated to the new specification will be recovered and the information of the cloud server of the new specification will be rolled back to the cloud server of the original specification.

8. A device for reducing the size of a cloud server specification, characterized in that: include: A management interface component for receiving specification change requests from users; The control service component is used to determine whether the specification change request meets the downsizing and reconfiguration conditions, and if so, select the current host where the cloud server is located as the destination host; if not, execute a predetermined host selection method and select the destination host; The cycle management component is used to control the destination host to complete the specification change process after the destination host is selected, and to create a cloud server of new specifications on the node through the information of the cloud server, and to update the cloud server information according to the received confirmation instruction or to roll back the cloud server of new specifications to the cloud server of original specifications according to the received rollback instruction.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method for reducing the size of a cloud server as described in any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method for reducing the size of a cloud server as described in any one of claims 1 to 7 is implemented.

Images