Virtual machine creation and management system

Abstract

The present disclosure relates to a virtual machine creation and management system, the system comprising a virtual machine management platform and a virtualization platform, the virtualization platform being used to create a virtual machine based on a user's creation request, the creation request including resource attribute information of the virtual machine to be created; the virtual machine management platform being used to receive information from the virtualization platform, the information including resource attribute information and creation time of the virtual machine created by the virtualization platform, and the virtual machine management platform being further used to manage the virtual machine based on the received information, the management including claiming and approving the virtual machine. The present disclosure not only significantly shortens the delivery time of virtual machines and ensures the success rate of virtual machine delivery, but also reduces the burden on the virtualization platform while reducing the complexity of the virtual machine management platform, thereby reducing the construction cost of the overall system.

Description

Technical Field

[0001] The present disclosure relates to the technical field of cloud computing, and in particular to a virtual machine creation and management system. Background Art

[0002] A virtual machine management system (also known as a virtual machine management platform) is a system built outside of the virtualization platform that records and manages the business attributes of virtual machines. While similar in functionality to general cloud management platforms, its implementation is simpler and suitable for small and medium-sized users with low management requirements. While business attributes generally don't affect virtual machine operations, they are crucial for enterprises managing virtualized resources, preventing overuse and waste, and facilitating resource recovery and reuse.

[0003] Currently, virtual machine management systems leverage the functionality of common cloud management platforms to manage virtual machine applications, approvals, quotas, and billing. However, these platforms typically first record business attributes and verify their accuracy and completeness before leveraging the platform's automated operations to create virtualized servers within the virtualization platform. This approach has the following drawbacks:

[0004] a. Users must first complete the business attributes and obtain approval before they can obtain the virtual machine they want to use, which prolongs the delivery time of the virtual machine;

[0005] b. The VM management system needs to call the virtualization platform's interface to create or modify VMs. These resource modification operations not only involve complex business logic but also rely heavily on the VM management system's accurate understanding of available resources on the virtualization platform. Otherwise, operations are likely to fail, directly reducing the success rate of delivery. To avoid this, the VM management system needs to frequently synchronize resource status data with the virtualization platform, which increases the burden on the virtualization platform.

[0006] c. To achieve single-system operation, the cloud management platform must integrate many non-critical functions, such as resource grouping, system logging, performance monitoring, fault alerts, virtual machine image management, and resource scheduling. These functions are already available on some virtualization platforms. However, when the scale of virtualization is small, providing a complete set of functions greatly increases the complexity of the virtual machine management system, increasing the overall system construction cost and lowering the value. Summary of the Invention

[0007] In view of this, the present disclosure proposes a virtual machine creation and management system, which can not only create new virtual machines in a timely manner and significantly shorten the delivery time of virtual machines, but also manage the claiming and approval of virtual machines.

[0008] According to one aspect of the present disclosure, there is provided a virtual machine creation and management system, comprising a virtual machine management platform and a virtualization platform;

[0009] The virtualization platform is used to create a virtual machine according to a creation request of a user, wherein the creation request includes resource attribute information of the virtual machine to be created;

[0010] The virtual machine management platform is used to receive information from the virtualization platform, the information including resource attribute information and creation time of the virtual machine created by the virtualization platform. The virtual machine management platform is also used to manage the virtual machine based on the received information, and the management includes claiming and approving the virtual machine.

[0011] In one possible implementation, the virtualization platform is further configured to perform at least one of the following judgments before creating the virtual machine:

[0012] Determine whether to allow the creation of the virtual machine based on the usage time of the virtual machine to be created;

[0013] Determine whether to allow the creation of a virtual machine based on the current utilization of virtualization resources;

[0014] Determine whether to allow the creation of a virtual machine based on the number of users of the current virtualization platform.

[0015] In one possible implementation, the virtual machine management platform is further configured to generate a virtual machine list based on the received information, so that the user can select a virtual machine to be claimed from the virtual machine list and upload corresponding business attribute information, thereby enabling the virtual machine management platform to claim the virtual machine.

[0016] In a possible implementation, the virtual machine management platform is further configured to send an approval request for the virtual machine to an auditor, and approve the virtual machine based on the approval result of the virtual machine.

[0017] In one possible implementation, the virtual machine management platform is further configured to automatically perform at least one of the following actions to manage the virtual machine:

[0018] When receiving claim information for a virtual machine that is allowed to be claimed, changing the state of the virtual machine to claimed;

[0019] When the task of sending the approval request of the virtual machine is completed, the status of the virtual machine is changed to pending approval;

[0020] According to the approval result of the virtual machine, the status of the virtual machine is changed to approved or rejected;

[0021] When receiving deletion information of a virtual machine, changing the state of the virtual machine to pending deletion;

[0022] Execute corresponding actions on the virtual machine based on its status.

[0023] In a possible implementation, performing corresponding actions on the virtual machine according to the state of the virtual machine includes:

[0024] When the state of the virtual machine is empty and no claim information is associated with the virtual machine within a first time, the operation of the virtual machine is stopped, wherein the first time is related to the creation time of the virtual machine, and the claim information includes business attribute information.

[0025] In one possible implementation, performing corresponding actions on the virtual machine based on the state of the virtual machine includes: when the virtual machine is in a state awaiting approval and no approval result is associated with the virtual machine within a second time, stopping the operation of the virtual machine, wherein the second time is related to the claim time of the virtual machine.

[0026] In a possible implementation, performing corresponding actions on the virtual machine according to the state of the virtual machine includes: when the virtual machine is in an approved state, maintaining the operation of the virtual machine.

[0027] In a possible implementation, performing a corresponding action on the virtual machine according to the state of the virtual machine includes: when the virtual machine is in a rejected state, stopping the operation of the virtual machine.

[0028] In one possible implementation, performing corresponding actions on the virtual machine based on the state of the virtual machine includes: when the state of the virtual machine is empty and the current time has not reached a third time, maintaining the operation of the virtual machine, wherein the third time is related to the creation time of the virtual machine.

[0029] In one possible implementation, performing corresponding actions on the virtual machine based on the state of the virtual machine includes: when the virtual machine is in a state awaiting approval and the current time has not reached a fourth time, maintaining the operation of the virtual machine, wherein the fourth time is related to the claim time of the virtual machine.

[0030] In a possible implementation, performing a corresponding action on the virtual machine according to the state of the virtual machine includes: when the virtual machine is in a state to be deleted, deleting the virtual machine.

[0031] In one possible implementation, the virtual machine management platform is specifically used to receive information from the virtualization platform at preset time intervals, wherein the status of the virtual machine corresponding to the received information is empty, and the resource attribute information includes information about resources occupied or used by the virtual machine.

[0032] The present invention creates virtual machines through a virtualization platform, and the virtual machine management platform receives information from the virtualization platform and manages the virtual machines based on the information. When users submit a virtual machine creation request to the virtualization platform, they do not need to fill in business attribute information. They can first create and use the virtual machine, and then go through the claim and approval process. This not only significantly shortens the delivery time of the virtual machine and ensures the success rate of virtual machine delivery, but also reduces the burden on the virtualization platform while reducing the complexity of the virtual machine management platform, thereby reducing the construction cost of the overall system.

[0033] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, rather than limiting the present disclosure. Other features and aspects of the present disclosure will become clear from the following detailed description of exemplary embodiments with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate exemplary embodiments, features, and aspects of the disclosure and, together with the description, serve to explain the principles of the disclosure.

[0035] Figure 1 A schematic diagram illustrating the operation process of a virtual machine creation and management system according to an embodiment of the present disclosure is shown.

[0036] Figure 2 A schematic diagram of a virtual machine management platform according to an embodiment of the present disclosure is shown.

[0037] Figure 3 A block diagram of an apparatus for executing a virtual machine management method according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0038] Various exemplary embodiments, features, and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. The same reference numerals in the accompanying drawings represent elements with the same or similar functions. Although various aspects of the embodiments are shown in the accompanying drawings, the drawings are not necessarily drawn to scale unless otherwise indicated.

[0039] The word “exemplary” is used exclusively herein to mean “serving as an example, example, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.

[0040] In addition, numerous specific details are provided in the following detailed description to better illustrate the present disclosure. Those skilled in the art will appreciate that the present disclosure can be practiced without certain specific details. In some instances, methods, means, components, and circuits well known to those skilled in the art are not described in detail in order to highlight the main points of the present disclosure.

[0041] In order to facilitate those skilled in the art to understand the technical solution provided by the embodiments of the present disclosure, the technical environment in which the technical solution is implemented is described below.

[0042] When managing virtual machines, two types of VM attributes are generally of interest: resource attributes and business attributes. Resource attributes describe the specific resources a VM occupies or uses, such as computing resources, network resources, and storage resources. This information is typically recorded in the virtualization platform. Business attributes describe the business management information associated with the VM, such as the VM's creator or user, the approver of the creation, the permitted usage period, the applicable fee, and whether the created VM exceeds the user's preset quota. While these business attributes generally do not affect VM operation, they are crucial for enterprises to manage virtualized resources, prevent overuse and waste, and facilitate resource recycling and reuse. Currently, when creating a VM, both resource and business attribute information must be entered. Only after approval can the VM be created and used by the user. This complex management logic directly prolongs VM delivery time, impacting the user experience. Therefore, simplifying VM management logic and shortening VM delivery time are crucial.

[0043] The present disclosure proposes a virtual machine creation and management system, including a virtual machine management platform and a virtualization platform. Users can create virtual machines through the virtualization platform. When creating a new virtual machine, the user does not need to fill in the business attribute information of the virtual machine when submitting a virtual machine creation request to the virtualization platform, and does not need to obtain approval from the virtual machine. The new virtual machine can be created directly on the virtualization platform based on the resource attribute information of the virtual machine, which significantly shortens the delivery time of the virtual machine and ensures the success rate of virtual machine delivery. The virtual machine management platform can receive information from the virtualization platform and manage the virtual machine based on this information. While reducing the burden on the virtualization platform, it also reduces the complexity of the virtual machine management platform, thereby reducing the construction cost of the overall system.

[0044] The embodiment of the present disclosure proposes a virtual machine creation and management system, including a virtual machine management platform and a virtualization platform;

[0045] The virtualization platform is used to create a virtual machine according to the user's creation request, and the creation request includes resource attribute information of the virtual machine to be created;

[0046] The virtual machine management platform is used to receive information from the virtualization platform, including resource attribute information and creation time of the virtual machines created by the virtualization platform. The virtual machine management platform is also used to manage the virtual machines based on the received information, including the claiming and approval of the virtual machines.

[0047] Now Figure 1 The virtual machine creation and management system operation process is shown as an example to illustrate the virtual machine creation process:

[0048] The user, or creator, sends a virtual machine creation request to the virtualization platform. This request may include information about the creator and resource attributes of the virtual machine to be created, such as the resource attributes of the virtual machine. This resource attribute information indicates the resources occupied or used by the virtual machine, and may include, but is not limited to, the number of physical CPU cores, memory size, storage space, and the number of virtual network cards.

[0049] After receiving a virtual machine creation request from a creator, the virtualization platform creates the requested virtual machine based on the information in the creation request, particularly the resource attribute information. Upon successful creation, the virtualization platform sends a notification message to the creator, confirming the successful creation of the virtual machine. This notification message may also include creation information, which may include but is not limited to the virtual machine's name, number, creation time, resource attribute information, and creator information.

[0050] After the creator receives the prompt message sent by the virtualization platform, he can use the newly created virtual machine normally.

[0051] By creating a virtual machine through the above process, users only need to fill in the resource attribute information to obtain the required virtual machine. They can use the virtual machine first without filling in the business attribute information at the same time. The virtual machine can be included in the business management after approval. This greatly shortens the delivery time of the virtual machine and makes it convenient for users to carry out activities as soon as possible.

[0052] Whenever the virtualization platform completes a virtual machine creation task, a new entry of information about the newly created virtual machine is added to the virtualization platform. This information is related to the virtual machine management method (described below) executed by the virtual machine management platform (also known as the virtual machine management system). Based on this information, the virtual machine management platform can manage the claiming and approval of virtual machines. The virtual machine management platform can generate a virtual machine list based on the received information, allowing users to select the virtual machine to be claimed from the list and upload the corresponding business attribute information, thereby enabling the virtual machine management platform to claim the virtual machine. The virtual machine management platform can also send a virtual machine approval request to the reviewer and approve the virtual machine based on the approval result. In one possible implementation, the virtual machine management platform can periodically obtain this information from the virtualization platform, that is, receive information from the virtualization platform at preset time intervals. For example, the virtual machine management platform can automatically synchronize relevant information about newly created virtual machines on the virtualization platform every two hours to facilitate the virtual machine management platform's automatic supervision of the claiming, approval, and deletion of these newly created virtual machines. The synchronized (received) information may include resource attribute information, creation time, creator information, etc. of the virtual machine created on the virtualization platform. Among them, the resource attribute information may include information about the resources occupied or used by the virtual machine, etc. After this information is synchronized to the virtual machine management platform, the status of the corresponding virtual machine is initially empty. The status of the virtual machine is also used as the marking information of the virtual machine by the virtual machine management platform. The status of the virtual machine may also include claimed, pending approval, approved, rejected, pending deletion, deleted, etc. (see below for details).

[0053] like Figure 2 The diagram of the virtual machine management platform shown in the figure shows that the virtual machine management platform can handle issues such as virtual machine claiming, approval, and deletion in real time by executing virtual machine management methods, thereby automatically changing the status of virtual machines. It can also perform corresponding actions on virtual machines based on the status of virtual machines, and can also handle virtual machine issues in other special circumstances. Among them, the virtual machine management method executed by the virtual machine management platform is related to the time limit policy. Before explaining the virtual machine management method, the time limit policy is explained first:

[0054] In one possible implementation, the virtual machine management platform can pre-set a time limit policy. According to the preset implementation policy, the virtual machine can be automatically configured with relevant time limits. The time limits may include the claim validity period, approval validity period, review cycle, etc.

[0055] Among them, the claim validity period refers to the valid time range for the user to apply for virtual machine claim after creating the virtual machine. Regarding the claim validity period, there can be: under the effect of the preset time limit policy, the virtual machine management platform can automatically set the corresponding claim validity period for the virtual machine synchronized from the virtualization platform, and the claim validity period can be set based on the creation time of the virtual machine. For example, the creation time of a virtual machine synchronized to the virtual machine management platform is 14:00 on July 23, and a claim validity period of up to 24 hours can be automatically set for the virtual machine. That is, if a user claims the virtual machine before 14:00 on July 24, then the virtual machine can continue to be used normally. Otherwise, after the claim validity period, the user may no longer claim the virtual machine and will not be able to continue to use the virtual machine normally. In other words, after creation, the user can use it for up to 24 hours.

[0056] Among them, the approval validity period refers to the time range in which the user obtains valid approval after completing the claim of the virtual machine. Regarding the approval validity period, there may be: under the effect of the preset time limit policy, the virtual machine management platform can automatically set a corresponding approval validity period for the virtual machine that has been claimed by the user, and the approval validity period can be set based on the claim time of the virtual machine. For example, in response to a virtual machine being claimed at 14:00 on January 23, the virtual machine management platform can automatically set an approval validity period of up to 48 hours for the virtual machine, that is, if the virtual machine obtains valid approval before 14:00 on January 25, then the virtual machine can continue to be used normally, otherwise, after the approval validity period, the virtual machine may no longer be approved, and the virtual machine cannot continue to be used normally. Among them, valid approval means that the relevant reviewers of the virtual machine agree to approve the virtual machine and its activities, and the review content may include the resource attribute information, business attribute information, etc. of the virtual machine.

[0057] Regarding the review cycle, the VM management platform can automatically set a review cycle for each VM based on a preset time limit policy. Based on this review cycle, the VM management platform automatically verifies VM ownership and approval. The review cycle can be set uniformly to three hours. This means that for each VM, the VM management platform automatically verifies ownership and approval every three hours to ensure compliance. If a VM is not owned within the claim validity period or is not approved within the approval validity period, normal operation of the VM will be suspended.

[0058] The time limit can be set uniformly or based on the level of the created virtual machine. A higher level indicates a more important virtual machine, so a relatively looser review period can be set for high-level virtual machines. For example, a 48-hour claim period can be set for high-level virtual machines, while a 24-hour claim period can be set for general-level virtual machines.

[0059] According to the above-mentioned time limit strategy and the following virtual machine management method, the technical solution proposed in the embodiment of the present disclosure simplifies the business logic, and adopts the method of first creating and using the virtual machine and then claiming and approving it for delivery, thereby shortening the delivery time of the virtual machine. Although there are time management loopholes, the losses caused by each virtual machine can be limited to a short period of time (for example, within 1 day). For usage scenarios such as relatively sufficient virtualization resources, a limited number of users, and the use time of the virtual machine far exceeding 1 day, the application of the embodiment of the present disclosure will result in certain losses, but these losses are usually acceptable. More importantly, it can bring about the simplification of the overall business logic and the shortening of delivery time. Furthermore, the embodiment of the present disclosure also proposes a supplementary solution for usage scenarios where the loss cannot be accepted, such as insufficient virtualization resources, a large number of users, and a very short use time of the virtual machine. Accordingly, in the embodiment of the present disclosure, before the virtualization platform creates a virtual machine, the virtualization platform can also be used to perform at least one of the following logical judgments to determine whether to allow the creation of a new virtual machine:

[0060] The virtual machine creation is determined based on the usage duration of the virtual machine to be created. For example, when the virtualization platform receives a request for new resources, i.e., to create a virtual machine, it obtains the usage duration of the virtual machine to be created, as sent by the user (i.e., the resource applicant). If the usage duration of the virtual machine to be created is equal to or greater than a preset threshold (e.g., 5 days), the virtual machine is created. If the usage duration of the virtual machine to be created is less than the preset threshold, the user is notified to apply for a special approval process. Only after obtaining approval for the virtual machine creation through the special approval process can the virtualization platform proceed with creating the virtual machine based on the user's creation request. Otherwise, if the special approval process is rejected, the virtual machine is not created. The special approval process can be performed by the resource administrator or the virtualization platform automatically comparing the resource applicant's utilization rate of the resources already requested to determine whether to allow the new resource application, i.e., the creation of the virtual machine. In addition to the special approval process, the virtualization platform can also provide new billing models to reduce the economic losses caused by special scenarios. The new billing model can be based on usage duration or can increase the billing standards of the existing model.

[0061] The system determines whether to allow the creation of a virtual machine based on the current utilization of virtualized resources. For example, when the virtualization platform receives a request for new resources, i.e., to create a virtual machine, it checks the available capacity of the current virtualized resources. If the overall available resource capacity is less than a preset capacity threshold (e.g., 30%), the virtual machine will not be created and the user will be prompted that the available resource capacity is insufficient. Otherwise, the virtual machine will be created.

[0062] Whether to allow the creation of a virtual machine is determined based on the number of users of the current virtualization platform. For example, when the virtualization platform receives a request for new resources, that is, a request to create a virtual machine, it checks the number of users of the current virtualization platform; if the number of users does not exceed the preset number (for example, 200 people), the virtual machine is created; if the number of users exceeds the preset number threshold, the user is notified to apply for a special approval process, and only after obtaining approval to create a virtual machine through the special approval process can the virtualization platform continue to create a new virtual machine according to user needs. Otherwise, if the special approval process is rejected, the virtual machine will not be created. Among them, the special approval process can choose to let the resource administrator decide whether to allow the continued creation of virtual machines on the current virtualization platform. If the resource administrator allows, the virtualization platform continues to create virtual machines; if the resource administrator does not allow, the virtualization platform prompts the user that the number of users of the current virtualization platform is large, so a new virtual machine will not be created.

[0063] Based on the virtual machine creation and management system and time limit strategy described above, the virtual machine management method implemented by the virtual machine management platform is now explained:

[0064] The virtual machine management platform is also used to automatically perform at least one of the following actions to manage the virtual machine:

[0065] When receiving claim information for a virtual machine that is allowed to be claimed, changing the state of the virtual machine to claimed;

[0066] When the task of sending the approval request of the virtual machine is completed, the status of the virtual machine is changed to pending approval;

[0067] According to the approval result of the virtual machine, the status of the virtual machine is changed to approved or rejected;

[0068] When receiving deletion information of a virtual machine, changing the state of the virtual machine to pending deletion;

[0069] Execute corresponding actions on the virtual machine based on its status.

[0070] Based on a series of designed execution logic, namely the virtual machine management method, the virtual machine management platform can monitor each link of virtual machine creation, claiming, approval, maintenance, deletion, etc. It can not only change the status of the virtual machine according to the virtual machine information, but also perform corresponding actions in a timely manner according to the status of the virtual machine to automatically verify the compliance of the virtual machine usage, thereby realizing effective supervision of the virtual machine, which is efficient, convenient and highly automated.

[0071] Now still Figure 1 The virtual machine management method performed by the virtual machine management platform is described using the schematic diagram of the virtual machine creation and management system operation process as an example:

[0072] In one possible implementation, the virtual machine management platform is specifically used to receive information from the virtualization platform at preset time intervals, wherein the status of the virtual machine corresponding to the received information is empty, and the resource attribute information includes information about the resources occupied or used by the virtual machine. For example, the virtual machine management platform can automatically synchronize the relevant information of the newly created virtual machines on the virtualization platform every 2 hours. Now assume that the information U synchronized by the virtual machine management platform this time may include three newly created virtual machines and related information, that is, they may have: their respective names are V1, V2, and V3, the creation time is t1, t2, and t3, and the resource attribute information is I1, I2, and I3. In addition, the tag information of these synchronized virtual machines in the virtual machine management platform is empty, that is, the current status of V1, V2, and V3 is empty.

[0073] According to the time limit strategy described above, the virtual machine management platform can determine the validity period of claiming these virtual machines V1, V2, and V3, namely R1, R2, and R3. The validity period of claiming R1, R2, and R3 is set based on the creation time of each virtual machine V1, V2, and V3. In this embodiment, R1 = t1 + 24h, R2 = t2 + 24h, and R3 = t3 + 24h. Taking R1 as an example (R2 and R3 are the same as R1 and will not be repeated here), if the current time exceeds R1, the user may not be able to claim V1 and continue to use V1. The user can claim V1 before R1. Among them, the management of virtual machine claiming can be implemented according to the following virtual machine management method:

[0074] When claim information is received for a virtual machine that is allowed to be claimed, the state of the virtual machine is changed to claimed. The virtual machine that is allowed to be claimed may be a virtual machine that has been created and has not exceeded the claim validity period. The claim information may include but is not limited to the claimer information and the service attribute information of the virtual machine.

[0075] like Figure 1As shown, the user, or claimant, sends a claim request for a virtual machine to the virtual machine management platform. After receiving the claim request, the virtual machine management platform can provide the claimant with a control for entering a unique identification code, allowing the claimant to identify the virtual machine to be claimed. The unique identification code can also be directly included in the claim request. Each unique identification code corresponds to one and only one virtual machine. The unique identification code can be the virtual machine's IP address, name, or serial number, and can be flexibly configured based on user needs. In addition to selecting a virtual machine using a unique identification code, the virtual machine management platform can also provide the claimant with a list of virtual machines, allowing the claimant to select the virtual machine to be claimed from the list. The virtual machine list can be generated based on information received from the virtualization platform at preset intervals by the virtual machine management platform. The information in the list can be displayed based on the user's needs, including but not limited to the virtual machine's name and resource attribute information. Furthermore, the virtual machine management platform can display only the virtual machines that are allowed to be claimed, and may not display virtual machines with statuses of claimed, pending approval, approved, rejected, pending deletion, or deleted. In addition, public servers on the virtualization platform can be claimed by public users on the virtual machine management platform to avoid the public server being deleted due to personal reasons.

[0076] Once the claimant has confirmed the VM they wish to claim, the VM management platform performs two steps: first, it sends the VM's resource attribute information to the claimant for verification; second, it sends the VM's business attribute information to the claimant for completion. These two steps can be performed simultaneously or sequentially, and can be flexibly configured based on user usage habits. Business attribute information may include, but is not limited to, the user's real name, organization or department, the VM's purpose, the VM's usage period and associated fees, and the approver of the creation activity.

[0077] When the claimant completes the verification of resource attribute information and the filling of business attribute information, the virtual machine management platform can automatically change the status of the virtual machine from empty to claimed. Among them, if the claimant completes the verification of resource attribute information and finds an error, the virtual machine management platform can send a request to the virtualization platform to recreate the virtual machine or change the virtual machine configuration. In addition, if the claimant completes the filling of business attribute information, the claimant can judge whether the filling work is completed based on their own experience. It can also be set up with a corresponding policy to determine whether the business attribute information filled in by the claimant is complete, that is, to determine whether the claimant has completed the filling work, just like the pre-set time limit policy.

[0078] Let's take R1 as an example: the claimant sends a claim request for the virtual machine to the virtual machine management platform at t1+1h. After receiving the claim request, the virtual machine management platform can provide the claimant with a control for entering a unique identification code and / or a virtual machine list. The claimant can choose any of the methods to determine the virtual machine V1 to be claimed. Among them, the virtual machine list can be generated based on the above U. The virtual machine management platform sends the resource attribute information I1 of V1 that the claimant has determined to claim to the claimant for verification, and provides the claimant with a control for filling in the business attribute information of V1. When the claimant completes the verification and filling, the virtual machine management platform can automatically change the status of V1 to claimed.

[0079] Based on the time limit policy described above, the virtual machine management platform can also determine the audit period for these virtual machines V1, V2, and V3. In this embodiment, the audit period is 3 hours. The audit period of 3 hours is set based on the creation time of each virtual machine V1, V2, and V3. The virtual machine management platform can automatically verify whether virtual machines V1, V2, and V3 are used in compliance with the audit period. The automatic verification content may include the following aspects of virtual machine claim:

[0080] According to the state of the virtual machine, the corresponding action is performed on the virtual machine, which may include: when the state of the virtual machine is empty and the current time has not reached the third time, maintaining the operation of the virtual machine, wherein the third time is related to the creation time of the virtual machine. Now take the above-mentioned V2 as an example: the virtual machine management platform performs the first automatic verification of V2 at t2+3h, and finds that no claim information related to V2 is received from t2 to t2+3h, and the current time t2+3h has not reached the third time, i.e. t2+24h, i.e. R1, which means that V2 is still within the claim validity period, and the virtual machine management platform can continue to maintain the operation of V2. In a possible implementation, the virtual machine management method may also include: when the claim validity period of the virtual machine is about to expire, sending a reminder message to the creator to remind the creator to claim it or conveying the claim to the claimer in time. This can avoid the situation where the virtual machine cannot be claimed due to the user forgetting to claim it and cannot be used normally.

[0081] According to the status of the virtual machine, corresponding actions are performed on the virtual machine, which may include: when the status of the virtual machine is empty, and no claim information is associated with the virtual machine within the first time, stopping the operation of the virtual machine, wherein the first time is related to the creation time of the virtual machine, and the claim information includes business attribute information. Among them, stopping the operation of the virtual machine includes deleting the virtual machine, disabling the network of the virtual machine, and shutting down the virtual machine. Now take the above-mentioned V3 as an example: the virtual machine management platform performs the last automatic verification of V3 at t3+24h, and finds that no claim information related to V3 is associated with V3 within the first time, that is, from t3 to t3+24h. This means that V3 is in a situation where the claim validity period has expired and no user has come to claim it. The virtual machine management platform can stop the operation of V3. Among them, you can choose the method of stopping the operation of the virtual machine according to the level of V3. For example, if V3 is a high-level virtual machine, you can choose to disable the virtual machine's network or shut down the virtual machine, thereby temporarily stopping the virtual machine's activities and avoiding serious consequences caused by directly deleting the virtual machine. If V3 is a low-level virtual machine, you can choose to delete the virtual machine, so that the corresponding resources can be directly released on the virtualization platform, which is beneficial to the resource planning of the virtualization platform.

[0082] In addition to the management methods mentioned above regarding virtual machine ownership, the virtual machine management platform can also automatically verify virtual machine approval issues based on the review cycle. Before explaining the automatic verification content of approval, we will first explain the validity period of virtual machine approval using the above V1, V2, and V3:

[0083] According to the time limit strategy described above, the virtual machine management platform can determine the approval validity period of each of these virtual machines V1, V2, and V3, namely S1, S2, and S3. The approval validity period is set based on the claim time of each virtual machine V1, V2, and V3. Now assume that V1, V2, and V3 complete the claim within their respective claim validity periods R1, R2, and R3, and their respective claim times are t1', t2', and t3'. In this embodiment, S1 = t1'+48h, R2 = t2'+48h, and R3 = t3'+48h. Taking S1 as an example (S2 and S3 are the same as S1, and will not be repeated here), if the current time exceeds S1, the user may not be able to initiate the approval of V1 and cannot continue to use V1. The approval problem of V1 can be completed before S1. Among them, the approval problem of the virtual machine can be implemented according to the following virtual machine management method:

[0084] When the task of sending the approval request for the virtual machine is completed, the status of the virtual machine is changed to pending approval.

[0085] like Figure 1As shown, a user, i.e., the approval initiator (typically the claimant), can initiate an approval request on the virtual machine management platform. This approval request may include, but is not limited to, information related to the virtual machine to be approved, such as creation information and claim information. Based on the approval request, the virtual machine management platform sends a pending approval message to the corresponding approver. This pending approval message may include, but is not limited to, the approval request and the approval validity period of the corresponding virtual machine. Sending the approval validity period to the approver helps the approver plan their time wisely and avoid overdue approvals. When the pending approval message is successfully sent, i.e., when the approval request for the virtual machine is completed, the virtual machine management platform automatically changes the status of the virtual machine from claimed to pending approval. For example, let's take the previously claimed virtual machine V1 as an example: the approval initiator initiates an approval request for V1 on the virtual machine management platform at t1'+1h. Based on V1's approval request, the virtual machine management platform sends a pending approval message for V1 to the corresponding approver. When the pending approval message for V1 is successfully sent, the virtual machine management platform automatically changes the status of V1 from claimed to pending approval.

[0086] The approver who receives the pending approval message can approve it on the virtual machine management platform or the external review system. Take the virtual machine management platform as an example: the approver reviews the virtual machine based on the pending approval message and uploads the approval result to the virtual machine management platform. The uploaded result can be approved or passed, rejected or not passed. The virtual machine management platform can automatically change the status of the virtual machine based on the result uploaded by the approver. If the approval result uploaded by the approver is approved or passed or other results indicating qualified approval, then the virtual machine management platform can automatically change the status of the virtual machine to approved. The change process for rejected is the same as that for approved, and will not be repeated here. Among them, the action of the virtual machine management platform automatically changing the status of the virtual machine can be based on the review cycle, or by setting a timely response policy to achieve that the virtual machine management platform changes the status of the virtual machine as soon as the approver uploads the approval result, so that the status of the virtual machine in the virtual machine management platform is the latest status.

[0087] Automatic verification can also include virtual machine approval:

[0088] Based on the state of the virtual machine, performing corresponding actions on the virtual machine may include: when the virtual machine is in a pending approval state and the current time has not yet reached a fourth time, maintaining the operation of the virtual machine, wherein the fourth time is related to the claim time of the virtual machine. Taking the claimed V2 as an example: the virtual machine management platform performs the first automatic review of the claimed V2 at t2'+3h (the first time here refers to the first automatic review of V2 for approval after being claimed). It finds that no approval results related to V2 have been received between t2' and t2'+3h, and the current time t2'+3h has not yet reached the fourth time, i.e., t2'+48h, i.e., S1, indicating that V2 is still within the approval validity period, and the virtual machine management platform may continue to maintain the operation of V2. In one possible implementation, the virtual machine management method may further include: sending a reminder message to the approver when the virtual machine's approval validity period is about to expire. This can prevent the virtual machine from being unable to be used normally due to the approver's own forgetfulness in reviewing the virtual machine, resulting in the virtual machine being overdue and unapproved.

[0089] According to the status of the virtual machine, corresponding actions are performed on the virtual machine, which may include: when the virtual machine is in a state awaiting approval, and no approval result is associated with the virtual machine within a second time, stopping the operation of the virtual machine, wherein the second time is related to the claim time of the virtual machine. Among them, stopping the operation of the virtual machine includes deleting the virtual machine, disabling the network of the virtual machine, and shutting down the virtual machine. Now take the above-mentioned claimed V3 as an example: the virtual machine management platform performs the last automatic verification of V3 at t3'+48h (the last time here refers to the last automatic verification of V3 for approval after being claimed), and finds that no approval result related to V3 is associated with V3 within the second time, that is, from t3' to t3'+48h. This means that V3 is in a situation where the approval validity period has exceeded and no valid approval has been obtained. The virtual machine management platform can stop the operation of V3. Among them, you can choose the method of stopping the operation of the virtual machine according to the level of V3. For example, if V3 is a high-level virtual machine, you can choose to disable the virtual machine's network or shut down the virtual machine, thereby temporarily stopping the virtual machine's activities and avoiding serious consequences caused by directly deleting the virtual machine. If V3 is a low-level virtual machine, you can choose to delete the virtual machine, so that the corresponding resources can be directly released on the virtualization platform, which is beneficial to the resource planning of the virtualization platform.

[0090] Based on the status of the virtual machine, corresponding actions are performed on the virtual machine, which may include: maintaining the operation of the virtual machine when the virtual machine is in an approved state. Maintaining the operation of the virtual machine may include: deducting configuration quotas and / or recording bills and / or deducting fees. Taking the aforementioned claimed V1 as an example: V1's current status is Approved. The virtual machine management platform treats V1 as a virtual machine that has been effectively approved and treats V1 as a truly normal virtual machine in use, performing business activities such as quota deduction, billing, and fee deductions for V1.

[0091] According to the status of the virtual machine, corresponding actions are performed on the virtual machine, which may include: when the virtual machine is in a rejected state, stopping the operation of the virtual machine. Among them, stopping the operation of the virtual machine includes any one of deleting the virtual machine, disabling the network of the virtual machine, and shutting down the virtual machine. Now take the above-mentioned claimed V1 as an example: the current status of V1 is rejected, and the virtual machine management platform regards V1 as a virtual machine that has not obtained valid approval and chooses to stop the operation of V1. Among them, the method of stopping the operation of the virtual machine can be selected according to the level of V1. For example, if V1 is a high-level virtual machine, you can choose to disable the network of the virtual machine or shut down the virtual machine, thereby temporarily stopping the activity of the virtual machine and avoiding the serious consequences of choosing to directly delete the virtual machine. If V1 is a low-level virtual machine, you can choose to delete the virtual machine, so that the corresponding resources can be directly released on the virtualization platform, which is beneficial to the resource planning of the virtualization platform.

[0092] In addition to the management methods mentioned above regarding virtual machine approval, the virtual machine management platform can also automatically verify virtual machine deletion issues based on the review cycle. The automatic verification content can include the following aspects of virtual machine deletion:

[0093] Executing corresponding actions on the virtual machine according to the state of the virtual machine may include: deleting the virtual machine when the virtual machine is in a state to be deleted.

[0094] The user sends a virtual machine deletion request to the virtual machine management platform. After receiving the deletion request, the virtual machine management platform can provide the user with a control for entering a unique identification code (see above), so that the claimant can determine the virtual machine to be deleted by entering the unique identification code. It can also provide the user with a virtual machine list, so that the user can select the virtual machine to be deleted in the virtual machine list, and the virtual machine management platform will change the status of the virtual machine to be deleted to pending deletion. The virtual machine list here can display virtual machines with statuses of empty, claimed, pending approval, approved, and rejected. The user can select any virtual machine on the virtual machine management platform to submit a deletion request based on the actual work situation. The virtual machine management platform can respond to the deletion request based on the preset deletion policy and can set the deletion policy based on the level of the virtual machine. If the virtual machine is of a high level, then the deletion issue can be arranged for an approver to approve it. In addition, the virtual machine management method provided in this embodiment also includes: prohibiting users from directly deleting virtual machines on the virtualization platform to avoid security issues caused by wrong or accidental deletion.

[0095] Based on the virtual machine's pending deletion status, the virtual machine management platform sends a deletion instruction to the virtualization platform. The virtualization platform executes the deletion instruction, releasing the virtual machine's resources and unique identifier. The virtual machine management platform receives a successful deletion notification from the virtualization platform and changes the virtual machine's status to deleted.

[0096] It should be noted that the creator, claimant, approval initiator, and user mentioned above may or may not be the same person, and a virtual machine can be claimed and used by multiple people.

[0097] The virtual machine management method implemented by the virtual machine management platform proposed in the embodiment of the present disclosure is based on the idea of ​​first creating and using the virtual machine and then claiming and approving the virtual machine. This significantly shortens the delivery time of the virtual machine, simplifies the management business logic of the virtual machine, and can more effectively supervise the virtual machine.

[0098] The virtual machine management platform proposed in the embodiments of the present disclosure focuses primarily on the business attributes of virtual machines, while the management of virtual machine resource attributes or other characteristics is still provided by the virtualization platform, and the two have little functional overlap. As a supplement to the virtualization platform, the virtual machine management platform provides necessary and scalable business management functions, such as virtual machine ownership, usage approval, quotas, and billing, reducing the scale and complexity of the virtualization platform and thus reducing the difficulty of developing the virtualization platform. Furthermore, the virtual machine management platform proposed in the embodiments of the present disclosure does not need to call the virtualization platform's interface to create virtual machines, a process that can easily fail due to the virtualization platform's insufficient understanding of available resource data. The virtual machine management platform simply calls the virtualization platform's interface to delete the virtual machine or place the virtual machine in a state with limited usage. The success rate of this operation is generally much higher than the success rate of creating the virtual machine, thus reducing the difficulty of developing the virtual machine management platform. In addition, the virtual machine management platform proposed in the embodiments of the present disclosure periodically executes the virtual machine management method based on the current state and information of the virtual machine. During subsequent operation, the business management function can be easily expanded according to newly added management factors and business rules, making it structurally scalable.

[0099] In some embodiments, the functions or modules included in the system provided by the embodiments of the present disclosure can be used to execute the method described in the above method embodiment. Its specific implementation can refer to the description of the above method embodiment. For the sake of brevity, it will not be repeated here.

[0100] An embodiment of the present disclosure further proposes an electronic device, comprising: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to implement the above-mentioned virtual machine management method when executing the instructions stored in the memory.

[0101] The present disclosure also provides a computer-readable storage medium having computer program instructions stored thereon, wherein the computer program instructions, when executed by a processor, implement the above-mentioned virtual machine management method. The computer-readable storage medium may be a volatile or non-volatile computer-readable storage medium.

[0102] An embodiment of the present disclosure also provides a computer program product, including computer-readable code, or a non-volatile computer-readable storage medium carrying computer-readable code. When the computer-readable code runs in a processor of an electronic device, the processor in the electronic device executes the above method.

[0103] Figure 3 1 is a block diagram of an apparatus 1900 for executing the above-mentioned virtual machine management method according to an exemplary embodiment. For example, the apparatus 1900 can be provided as a server or a terminal device. Figure 3The apparatus 1900 includes a processing component 1922, which further includes one or more processors, and memory resources represented by a memory 1932 for storing instructions, such as applications, that can be executed by the processing component 1922. The application stored in the memory 1932 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 1922 is configured to execute the instructions to perform the virtual machine management method described above.

[0104] The device 1900 may also include a power supply component 1926 configured to perform power management of the device 1900, a wired or wireless network interface 1950 configured to connect the device 1900 to a network, and an input / output (I / O) interface 1958. The device 1900 may operate based on an operating system stored in the memory 1932, such as Windows Server™, MacOS X™, Unix™, Linux™, FreeBSD™, or the like.

[0105] In an exemplary embodiment, a non-volatile computer-readable storage medium is also provided, such as a memory 1932 including computer program instructions, which can be executed by the processing component 1922 of the device 1900 to implement the virtual machine management method described above.

[0106] The present disclosure may be a system, method and / or computer program product. The computer program product may include a computer-readable storage medium carrying computer-readable program instructions for causing a processor to implement various aspects of the present disclosure.

[0107] A computer-readable storage medium can be a tangible device that can hold and store instructions for use by an instruction execution device. A computer-readable storage medium can be, for example, but not limited to, an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device, such as a punch card or a raised structure in a groove on which instructions are stored, and any suitable combination thereof. As used herein, a computer-readable storage medium is not to be construed as a transient signal per se, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., a light pulse through a fiber optic cable), or an electrical signal transmitted through an electrical wire.

[0108] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions to be stored in the computer-readable storage medium in each computing / processing device.

[0109] The computer program instructions for performing the operations of the present disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, and conventional procedural programming languages ​​such as "C" language or similar programming languages. Computer-readable program instructions may be executed entirely on a user's computer, partially on a user's computer, as an independent software package, partially on a user's computer, partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., utilizing an Internet service provider to connect via the Internet). In some embodiments, an electronic circuit, such as a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), may be personalized by utilizing the state information of the computer-readable program instructions. The electronic circuit may execute the computer-readable program instructions, thereby realizing various aspects of the present disclosure.

[0110] Various aspects of the present disclosure are described herein with reference to flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present disclosure. It should be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.

[0111] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processor of the computer or other programmable data processing device, a device is generated that implements the functions / actions specified in one or more blocks in the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, where these instructions cause the computer, programmable data processing device, and / or other device to operate in a specific manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing various aspects of the functions / actions specified in one or more blocks in the flowchart and / or block diagram.

[0112] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more blocks in the flowchart and / or block diagram.

[0113] The flow charts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the systems, methods and computer program products according to multiple embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and the part of the module, program segment or instruction contains one or more executable instructions for realizing the prescribed logical function. In some alternative implementations, the functions marked in the box can also occur in a sequence different from that marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be implemented by a dedicated hardware-based system that performs the prescribed function or action, or can be implemented by a combination of dedicated hardware and computer instructions.

[0114] While various embodiments of the present disclosure have been described above, the foregoing description is intended to be illustrative, non-exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is selected to best explain the principles of the embodiments, their practical applications, or technological improvements in the marketplace, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. A virtual machine creation and management system, characterized in that: Including virtual machine management platform and virtualization platform; The virtualization platform is used to create a virtual machine according to a creation request of a user, wherein the creation request includes resource attribute information of the virtual machine to be created; The virtualization platform is further configured to send a prompt message indicating successful creation of the virtual machine to the user after successfully creating the virtual machine, so that the user can use the successfully created virtual machine after receiving the prompt message; The virtualization platform is also used to generate information related to the virtual machine after successfully creating the virtual machine. The virtual machine management platform is used to receive information from the virtualization platform, the information including resource attribute information and creation time of the virtual machine created by the virtualization platform. The virtual machine management platform is also used to manage the virtual machine based on the received information, and the management includes claiming and approving the virtual machine. The management of the virtual machine based on the received information includes: configuring the claim validity period of the newly created virtual machine synchronized from the virtualization platform based on the creation time of the virtual machine, so that the user can use the unclaimed virtual machine within the claim validity period. The claim validity period refers to the effective time range for the user to apply for virtual machine claim after creating the virtual machine.

2. The virtual machine creation and management system according to claim 1, characterized in that: Before creating a virtual machine, the virtualization platform is further configured to perform at least one of the following judgments: Determine whether to allow the creation of the virtual machine based on the usage time of the virtual machine to be created; Determine whether to allow the creation of a virtual machine based on the current utilization of virtualization resources; Determine whether to allow the creation of a virtual machine based on the number of users of the current virtualization platform.

3. The virtual machine creation and management system according to claim 1, characterized in that: The virtual machine management platform is further configured to generate a virtual machine list based on the received information, so that the user can select a virtual machine to be claimed from the virtual machine list and upload corresponding service attribute information, thereby enabling the virtual machine management platform to claim the virtual machine.

4. The virtual machine creation and management system according to claim 3, characterized in that: The virtual machine management platform is further configured to send an approval request for the virtual machine to an auditor, and implement approval of the virtual machine based on the approval result of the virtual machine.

5. The virtual machine creation and management system according to claim 1, characterized in that: The virtual machine management platform is further configured to automatically perform at least one of the following actions to manage the virtual machine: When receiving claim information for a virtual machine that is allowed to be claimed, changing the state of the virtual machine to claimed; When the task of sending the approval request of the virtual machine is completed, the status of the virtual machine is changed to pending approval; According to the approval result of the virtual machine, the status of the virtual machine is changed to approved or rejected; When receiving deletion information of a virtual machine, changing the state of the virtual machine to pending deletion; Execute corresponding actions on the virtual machine based on its status.

6. The virtual machine creation and management system according to claim 5, characterized in that: The performing corresponding actions on the virtual machine according to the state of the virtual machine includes: When the state of the virtual machine is empty and no claim information is associated with the virtual machine within a first time, the operation of the virtual machine is stopped, wherein the first time is related to the creation time of the virtual machine, and the claim information includes business attribute information.

7. The virtual machine creation and management system according to claim 5, characterized in that: The performing corresponding actions on the virtual machine according to the state of the virtual machine includes: When the virtual machine is in a state of pending approval and no approval result is associated with the virtual machine within a second time, the operation of the virtual machine is stopped, wherein the second time is related to the claiming time of the virtual machine.

8. The virtual machine creation and management system according to claim 5, characterized in that: The performing corresponding actions on the virtual machine according to the state of the virtual machine includes: When the virtual machine is in an approved state, the operation of the virtual machine is maintained.

9. The virtual machine creation and management system according to claim 5, characterized in that: The performing corresponding actions on the virtual machine according to the state of the virtual machine includes: When the virtual machine is in the rejected state, the operation of the virtual machine is stopped.

10. The virtual machine creation and management system according to claim 5, characterized in that: The performing corresponding actions on the virtual machine according to the state of the virtual machine includes: When the state of the virtual machine is empty and the current time has not reached a third time, the operation of the virtual machine is maintained, wherein the third time is related to the creation time of the virtual machine.

11. The virtual machine creation and management system according to claim 5, characterized in that: The performing corresponding actions on the virtual machine according to the state of the virtual machine includes: When the virtual machine is in a state awaiting approval and the current time has not reached a fourth time, the operation of the virtual machine is maintained, wherein the fourth time is related to the claiming time of the virtual machine.

12. The virtual machine creation and management system according to claim 5, characterized in that: The performing corresponding actions on the virtual machine according to the state of the virtual machine includes: When a virtual machine is in the pending deletion state, delete the virtual machine.

13. The virtual machine creation and management system according to claim 1, characterized in that: The virtual machine management platform is specifically configured to receive information from a virtualization platform at preset time intervals, wherein the state of the virtual machine corresponding to the received information is empty, and the resource attribute information includes information about resources occupied or used by the virtual machine.

Images