Method, device, and system for creating an instance

Abstract

The present application provides a method for creating an instance, comprising: a cloud platform receiving a first resource allocation request from a first user, wherein the first resource allocation request includes the number of resources to be allocated to the first user; the cloud platform allocating a first resource to the first user based on the number of resources to be allocated to the first user; the cloud platform receiving a first instance creation request from the first user, wherein the first instance creation request includes the number of instances to be created by the first user; and the cloud platform creating an instance on the first resource based on the number of instances to be created by the first user. The above solution can improve resource utilization.

Description

Technical Field

[0001] The present application relates to cloud computing, and more particularly to a method, device, and system for creating an instance. Background Art

[0002] Cloud computing is a service related to information technology, software, and the internet. It combines numerous computing, storage, and network resources, automating their management through software. This allows for rapid resource provision with minimal human involvement. In other words, computing power becomes a commodity, circulated online like water, electricity, and gas—easy to access and relatively inexpensive.

[0003] However, how to improve the utilization of cloud platforms is a very important technical challenge. Summary of the Invention

[0004] In order to solve the above problems, the present application provides a method, device and system for creating an instance, which can improve resource utilization.

[0005] In a first aspect, a method for creating an instance is provided, comprising:

[0006] The cloud platform receives a first resource allocation request from a first user, wherein the first resource allocation request includes the quantity of resources that the first user needs to allocate;

[0007] The cloud platform allocates the first resource to the first user according to the quantity of resources required to be allocated to the first user;

[0008] The cloud platform receives a first instance creation request from the first user, wherein the first instance creation request includes the number of instances that the first user needs to create;

[0009] The cloud platform creates instances on the first resource according to the number of instances that the first user needs to create.

[0010] In this embodiment, the cloud platform allocates the resources required by the user to the user, and the user can create an instance on the first resource according to his or her needs. Since the first resource belongs to the user, the user can monitor the usage status of the first resource and schedule and manage the first resource according to the usage status of the first resource, thereby improving the utilization rate of the first resource.

[0011] In some possible designs, the cloud platform receives a first instance adding request from the first user, wherein the first instance adding request includes the number of instances that the first user needs to add;

[0012] The cloud platform adds instances to the first resource according to the number of new instances required by the first user.

[0013] In some possible designs, the cloud platform receives a first instance deletion request from the first user, wherein the first instance deletion request includes the number of instances that the first user needs to delete;

[0014] The cloud platform deletes instances on the first resource according to the number of instances that the first user needs to delete.

[0015] In some possible designs, the number of instances that the first user needs to create is greater than or equal to 2.

[0016] In some possible designs, the cloud platform receives a first query instruction from the user, queries the usage status of the first resource according to the first query instruction, and sends the usage status of the first resource to the user.

[0017] In a second aspect, a method for creating an instance is provided, comprising:

[0018] The cloud platform receives a second resource allocation request from a third party, wherein the second resource allocation request includes the quantity of resources that the third party needs to allocate;

[0019] The cloud platform allocates the second resource to the third party according to the quantity of resources required to be allocated by the third party;

[0020] The cloud platform receives a second instance creation request from a second user, wherein the second instance creation request includes the number of instances that the second user needs to create;

[0021] The cloud platform creates instances on the second resource according to the number of instances that the second user needs to create.

[0022] In the above embodiment, the third party can purchase the second resource from the provider of the cloud platform and create an instance on the second resource according to the needs of the user. The third party acts as an intermediary to manage and charge users, which encourages the third party to create more services that improve the utilization of the cloud platform, thereby prospering the cloud platform market.

[0023] In some possible designs, the cloud platform receives a second new instance request from the second user, wherein the second new instance request includes the number of new instances that the second user needs to add; the cloud platform adds instances to the second resource based on the number of new instances that the second user needs to add.

[0024] In some possible designs, the cloud platform receives a second instance deletion request from the second user, wherein the second instance deletion request includes the number of instances that the second user needs to delete; the cloud platform deletes instances on the second resource according to the number of instances that the second user needs to delete.

[0025] In some possible designs, the number of instances that the second user needs to create is greater than or equal to 2.

[0026] In some possible designs, the cloud platform receives a second query instruction from the third party, queries the usage status of the second resource according to the second query instruction, and sends the usage status of the second resource to the third party.

[0027] In a third aspect, a cloud platform is provided, comprising: a receiving module, an allocating module, and a creating module.

[0028] The receiving module is configured to receive a first resource allocation request from a first user, wherein the first resource allocation request includes the amount of resources that the first user needs to allocate;

[0029] The allocation module is configured to allocate the first resource to the first user according to the quantity of resources required to be allocated to the first user;

[0030] The receiving module is configured to receive a first instance creation request from the first user, wherein the first instance creation request includes the number of instances that the first user needs to create;

[0031] The creation module is configured to create instances on the first resource according to the number of instances that the first user needs to create.

[0032] In some possible designs, the cloud platform also includes a new adding module, and the receiving module is used to receive a first new instance request from the first user, wherein the first new instance request includes the number of new instances that the first user needs to add; the new adding module is used to add instances to the first resource according to the number of new instances that the first user needs to add.

[0033] In some possible designs, the cloud platform also includes a deletion module, and the receiving module is used to receive a first instance deletion request from the first user, wherein the first instance deletion request includes the number of instances that the first user needs to delete; the deletion module is used to delete instances on the first resource according to the number of instances that the first user needs to delete.

[0034] In some possible designs, the number of instances that the first user needs to create is greater than or equal to 2.

[0035] In some possible designs, the cloud platform also includes a query module, the receiving module is used to receive the user's first query instruction, the query module is used to query the usage status of the first resource according to the first query instruction, and send the usage status of the first resource to the user.

[0036] In a fourth aspect, a cloud platform is provided, comprising: a receiving module, an allocating module and a creating module.

[0037] The receiving module is used for the cloud platform to receive a second resource allocation request from a third party, wherein the second resource allocation request includes the amount of resources that the third party needs to allocate;

[0038] The allocation module is configured to allocate the second resource to the third party according to the quantity of resources required to be allocated to the third party;

[0039] The receiving module is configured to receive a second instance creation request from a second user, wherein the second instance creation request includes the number of instances that the second user needs to create;

[0040] The creation module is used to create instances on the second resource according to the number of instances that the second user needs to create.

[0041] In some possible designs, the cloud platform also includes a new module,

[0042] The receiving module is configured to receive a second instance adding request from the second user, wherein the second instance adding request includes the number of instances that the second user needs to add;

[0043] The adding module is used to add instances to the second resource according to the number of instances required by the second user.

[0044] In some possible designs, the cloud platform further includes a deletion module.

[0045] The receiving module is configured to receive a second instance deletion request from the second user, wherein the second instance deletion request includes the number of instances that the second user needs to delete;

[0046] The deletion module is configured to delete instances on the second resource according to the number of instances that the second user needs to delete.

[0047] In some possible designs, the number of instances that the second user needs to create is greater than or equal to 2.

[0048] In some possible designs, the cloud platform further includes a query module.

[0049] The receiving module is used to receive a second query instruction from the third party,

[0050] The query module is used to query the usage status of the second resource according to the second query instruction, and send the usage status of the second resource to the third party.

[0051] In a fifth aspect, a management node is provided, characterized in that it includes a processor and a memory, and the processor executes the code in the memory to perform the method as described in any one of the first aspects.

[0052] In a sixth aspect, a computer-readable storage medium is provided, characterized in that it includes instructions, which, when executed on a computer, enable the computer to execute the method as described in any one of the first aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background technology, the drawings required for use in the embodiments of the present application or the background technology will be described below.

[0054] Figure 1 This is a schematic diagram of the structure of a cloud system involved in this application;

[0055] Figure 2 This is a schematic diagram of the structure of a cloud platform provided by this application;

[0056] Figure 3 This is a schematic diagram of the structure of another cloud platform provided by this application;

[0057] Figure 4A-4B This is a schematic diagram of the structure of some specific cloud platforms involved in this application;

[0058] Figure 5 is a schematic diagram of a user desktop of a terminal device involved in this application;

[0059] Figure 6 This is a schematic diagram of a resource purchase webpage provided by this application;

[0060] Figure 7 This is a schematic diagram of creating an example web page improved by this application;

[0061] Figures 8A-8D It is a schematic diagram of some newly added and deleted instances;

[0062] Figures 9A-9C It is a flowchart of some example creation methods provided by this application;

[0063] Figure 10 This is a schematic diagram of a user creating a resource monitoring system and a second scheduling manager on a first resource provided by the present application;

[0064] Figure 11 This is a flowchart of another example creation method provided by this application;

[0065] Figure 12 This is a schematic diagram of the structure of a cloud platform provided by this application;

[0066] Figure 13 This is a structural diagram of another management node provided by this application. DETAILED DESCRIPTION

[0067] See also Figure 1 , Figure 1 1 is a schematic diagram of a cloud system involved in this application. The cloud system of this application may include: a terminal device 11, a network device 12 and a cloud platform 13.

[0068] The terminal device 11 can run a client application, which is an intermediary between the user and the server. The user inputs instructions to the client, and the client translates the instructions into data and sends it to the cloud platform 13. After the cloud platform 13 processes the data, it returns the result. Then, the client presents the result to the user in a graphical form, such as a game client application, a VR client application, etc. The terminal device can be a high-configuration, high-performance device (for example, multi-core, high main frequency, large memory, etc.) or a low-configuration, low-performance device (for example, single-core, low main frequency, small memory, etc.). Moreover, after the cloud platform 13 performs a large number of computing and storage tasks, the terminal device can be a terminal with high input and output capabilities, high communication capabilities, low computing capabilities, and low storage capabilities, such as a cloud terminal, a thin terminal, etc.

[0069] The network device 12 is used to transmit data between the terminal device 11 and the cloud platform 13 via a communication network of any communication mechanism / communication standard. The communication network can be a wide area network, a local area network, a point-to-point connection, or any combination thereof.

[0070] The owner of the cloud platform 13 deploys its own cloud computing infrastructure, namely, computing resources (e.g., servers), storage resources (e.g., memory), and network resources (e.g., network cards). The public cloud owner (e.g., operator) then virtualizes the computing, storage, and network resources of the cloud computing infrastructure and provides corresponding services to cloud users (e.g., users). Users can leverage the services provided by the cloud platform to run their own applications, such as deep learning applications, artificial intelligence applications, and big data applications.

[0071] like Figure 2As shown in Figure 1, the cloud platform can provide the following three services to users of terminal devices: cloud computing Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS).

[0072] IaaS provides users with access to cloud computing infrastructure, including processing, storage, networking, and other basic computing resources. Users can deploy and run arbitrary software, including operating systems and applications. Users do not manage or control any cloud computing infrastructure, but they can control the choice of operating system, storage space, deployed applications, and may also gain control over limited network components (such as firewalls and load balancers).

[0073] PaaS provides users with the ability to deploy applications developed or acquired using vendor-provided development languages ​​and tools (e.g., Java, Python, .NET) onto cloud computing infrastructure. Users do not need to manage or control the underlying cloud computing infrastructure, including networks, servers, operating systems, and storage. However, they do have control over deployed applications and possibly the configuration of the hosting environment in which they run.

[0074] SaaS provides users with applications running on the operator's cloud computing infrastructure. Users can access these applications on various devices through client interfaces, such as browsers. Users do not need to manage or control any cloud computing infrastructure, including networks, servers, operating systems, storage, and so on.

[0075] It should be understood that the above three services are only used as specific examples. In actual applications, the services may also be other services with a higher or lower degree of integration, which are not specifically limited here.

[0076] See also Figure 3 , Figure 3 2 is a schematic diagram of the structure of another cloud platform involved in this application. The cloud platform includes: a management node 210 and a resource pool 220. The management node 210 can communicate with the resource pool 220.

[0077] Management node 210 includes a cloud management platform 211, an operating system 212, and hardware 213. Cloud management platform 211 can be AWS (Amazon Web Service), OpenStack, or CloudStack for providing IAAS services, Hadoop or Apache Mesos for providing PaaS services, or Kubernetes or Swarm for providing SAAS services, etc., without specific limitation. Hardware 213 can include a physical network card 214.

[0078] exist Figure 3 In the illustrated example, the management node 210 is centralized. In other embodiments, the management node 210 may also be distributed. For example, in a centralized configuration, the functions of the management node 210 are centralized on a single super server. In a distributed configuration, the functions of the management node 210 are distributed across multiple standard servers. This is not specifically limited here.

[0079] The resource pool 220 may include a computing resource pool, a storage resource pool, and a network resource pool, wherein the computing resource pool, the storage resource pool, and the network resource pool are all unified resource pools formed by decoupling physical hardware resources from upper layer applications through a virtualization management program.

[0080] The computing resource pool can include multiple processor units. Each processing unit can include a central processing unit (CPU), cache memory, a northbridge chip, a southbridge chip, a direct memory access (DMA) controller, and so on. The CPU is the center of computing and control. The CPU can adopt a complex instruction set computer (CISC) architecture (e.g., the x86 architecture), a reduced instruction set computer (RISC) architecture (e.g., the MIPS (microprocessor without interlocked piped stages) architecture), and so on. The CPU also includes multiple registers, which are high-speed storage components with limited storage capacity. They can be used to temporarily store instructions, data, and addresses, such as the instruction register (IR), program counter (PC), and accumulator (ACC). The cache memory is used to store instructions or data that the CPU has just used or is reusing. If the CPU needs to use the same instruction or data again, it can directly call it from the cache memory, reducing CPU latency and thus improving system efficiency. The northbridge chip is the chip closest to the CPU and is responsible for data transfer between the CPU and the cache memory. Because the northbridge chip processes a large amount of data and generates a significant amount of heat, it can be covered with a heat sink or equipped with a fan to enhance heat dissipation. The southbridge chip processes low-speed signals, communicates with the CPU through the northbridge, and exchanges data with external devices through various interfaces. The DMA controller copies data from one address space to another. Before data transfer, the CPU transfers bus control to the DMA controller. After the data transfer is complete, the DMA controller immediately returns bus control to the CPU. The DMA controller maintains bus control during data transfer. Optionally, the processing unit also includes a digital signal processor (DSP), a graphics processing unit (GPU), a neural network processing unit (NPU), and so on. Processing units can adopt either a homogeneous or heterogeneous architecture. Common heterogeneous architectures include CPU+DSP, CPU+NPU, CPU+GPU, and CPU+DSP+GPU.

[0081] The storage resource pool can include multiple memories and multiple hard disks. The multiple hard disks can adopt a homogeneous structure or a heterogeneous structure. The hard disks can include mechanical hard disks (HDD), solid state drives (SDD), hybrid hard drives (HDD), etc.

[0082] The network resource pool may include multiple network cards, multiple routers, multiple switches, multiple firewalls, and multiple load balancers, etc. Multiple network cards may adopt a homogeneous structure or a heterogeneous structure. Network cards may include: standard Ethernet cards, PCMCIA network cards, wireless network cards, fiber optic network cards, Ethernet cards, token ring network cards, 100M network cards, Gigabit network cards, and smart network cards, etc. Multiple routers may include backbone routers, enterprise routers, and access routers, and may include "border routers" and "intermediate node routers," etc. Switches may include WAN switches and LAN switches, and may include Ethernet switches, Fast Ethernet switches, Gigabit Ethernet switches, FDDI switches, ATM switches, and Token Ring switches, and may include enterprise switches, department switches, and workgroup switches, etc. Firewalls may include: filtering firewalls and application proxy type firewalls. Load balancing may include local load balancing and global load balancing.

[0083] It should be understood that the above cloud system is merely a specific example and should not constitute a specific limitation.

[0084] Figure 4A-4B These are some embodiments that further refine the management node 210. Figure 4A The cloud management platform in the management node 210 shown is OpenStack, which is used to create virtual machine instances. Figure 4B The cloud management platform in the management node 210 shown is Kubernetes, which is used to create container instances.

[0085] See also Figure 4A , Figure 4A This is a schematic diagram of a specific cloud platform involved in this application. Figure 4A Cloud platform in Figure 2 The cloud management platform 211 in the cloud platform is specifically implemented. Taking OpenStack as an example, the cloud management platform 211 can include computing services 215, storage services 216, and network services 217. In addition, it can also include identity service modules and dashboard service modules (not shown).

[0086] The computing service 215 can be a computing organization controller in the cloud management platform 211, which is used to manage all activities of the instance in its life cycle. For example, the computing service 215 can be a Nova component. The Nova component can include a Nova scheduling manager (Nova scheduler) 218 ​​for allocating instances to specific computing nodes; the Nova interface (Nova API) is used as the entrance to the Nova component to accept user requests; the management component (Nova conductor) is responsible for interacting with the Nova database, and the computing component (Nova compute) is used to create and manage instances and provide message delivery; the message queue (MESSAGE queue) is used for message delivery between various Nova components (not shown in the figure).

[0087] The storage service 216 may be a component in the cloud management platform 211 for providing storage. For example, the storage service 216 may be one or more of the Cinder component, the Swift component, and the Glance component. Among them, the main purpose of the Cinder component is to provide block storage services, the main purpose of the Swift component is to provide object storage services, and the main purpose of the Glance component is to provide image storage services. Taking the storage service 216 as the Cinder component as an example, the Cinder component may include: the Cinder interface (Cinder API) is used as the entrance to the Cinder component to accept user requests; the Cinder scheduling manager is responsible for collecting the capacity and capability information reported by the backend, and completing the scheduling of the volume to the specified capacity component (cinder-volume) according to the set algorithm; the capacity component (cinder-volume) uses different configuration files and connects to different backend devices. Each storage manufacturer inserts driver code to interact with the device to complete the device capacity and capability information collection and volume operations. The support component (Cinder backup) is used to implement the backup of volume data to other storage media (currently Swift / Ceph / TSM provides drivers).

[0088] Network service 217 may be a component in cloud management platform 211 that provides network topology management for network nodes. For example, network service 217 may be a Neutron component. Neutron components may include network components such as networks, subnets, ports, switches, and routers.

[0089] In addition, the cloud management platform 211 may also include an identity service module and a dashboard service module. The identity service module, as an authentication system, can verify which users have access to which services and offers multiple authentication methods, including user account and password, tokens, and login mechanisms similar to AWS. The dashboard service module provides a graphical user interface. For example, if the cloud management platform 211 is OpenStack, the identity service module could be Keystone, and the dashboard service module could be Horizon.

[0090] See also Figure 4B , Figure 4B This is a schematic diagram of a specific cloud platform involved in this application. Figure 4B Cloud platform in Figure 3 The cloud management platform 211 in the cloud platform is specifically implemented. Taking Kubernetes (k8s for short) as an example, the cloud management platform 211 may include an API server 315, a controller manager 316, a scheduler 317, and a cluster state storage 318.

[0091] The AIP server 315 is the only entry point for resources and provides mechanisms such as authentication, authorization, access control, API registration and discovery.

[0092] The control management server 316 is responsible for creating containers and maintaining the state of the cluster, such as fault detection, automatic expansion, and rolling updates. The control management server 316 may include a replication controller (Replication Controller), a node controller (Node Controller), a namespace controller (Namespace Controller), a service account controller (ServiceAccount Controller), a token controller (Token Controller), a service controller (ServiceController), and an endpoint controller (Endpoint Controller).

[0093] The scheduling manager 317 is used to schedule containers to corresponding nodes according to a predetermined scheduling strategy. The scheduling strategy is mainly divided into two parts: preselection strategy (Predicates) and priority strategy (Priorites). The preselection strategy is a mandatory rule that traverses all nodes and selects a list of nodes that meet the requirements according to the specific preselection strategy. If no node meets the preselection strategy, the container will be suspended until a node can meet it. The priority strategy, based on the first step of screening, scores and ranks the selected nodes according to the priority strategy to obtain the best one.

[0094] The cluster state storage 318 is responsible for storing the configuration information of the cluster and the status information of various resources. When the data changes, the cluster state storage will quickly notify other related components.

[0095] It should be understood that the above Figure 4A as well as Figure 4B The cloud management platform 211 shown is only a specific embodiment. In actual applications, the cloud management platform 211 can also have other structures, which are not specifically limited here. In some application scenarios, the management node 210 can also be installed with OpenStack and Kubernetes at the same time to provide users with containers and virtual machine instances at the same time.

[0096] An instance can be understood as a cloud server (Cloud Virtual Machine, CVM), which contains the most basic resources such as computing resources (including processors), storage resources (including memory and disks), and network resources. For example, an instance can include virtual machines or containers, etc. Instances are created by the cloud system based on the instance specifications selected by the user. Cloud systems usually provide several instance specifications, and instances created with different instance specifications have at least one of the computing resources, storage resources, and network resources that are different. Taking Table 1 as an example, the cloud system can provide the following instance specifications:

[0097] Table 1 Several instance specifications provided by the cloud system

[0098]

[0099]

[0100] Users can create instances by selecting from a variety of instance specifications. For example, if you need to create an instance that meets the needs of massive storage resources, you can choose a big data instance specification. If you need to create an instance with high throughput and low access latency, you can choose a high input / output instance specification. However, for ease of management and limited resources, cloud platforms generally only offer a limited number of instance specifications; it is impossible to provide an unlimited number of instance specifications.

[0101] When a user selects a specific instance specification to create an instance, the cloud platform's scheduling manager allocates the required resources to the compute, storage, and network resources in the resource pool according to the parameters of that specific instance specification. This means that the compute, storage, and network resources in the resource pool are allocated to the instance based on the instance's requirements. After the instance is successfully created, the instance has exclusive access to the compute, storage, and network resources allocated to it. Users can install their own applications on the instance, but if the application's utilization is low, the resource utilization allocated to the instance will be low.

[0102] In order to solve the above problems, the present application provides an instance creation method, device and system, which can effectively improve resource utilization.

[0103] The following is a detailed introduction to the user desktop on the terminal device. The user desktop is displayed after the terminal device is started.

[0104] like Figure 5 As shown, the user desktop 410 may include an icon display area 411 , a taskbar 412 , a calendar indicator 413 , and a start menu 414 .

[0105] Icon display area 411 can be used to display icons or shortcuts for commonly used applications. For example, it can display: computer icon 411A, recycle bin icon 411B, browser icon 411C, email icon 411D, WeChat icon 411E, and QQ icon 411F. Among them, browser icon 411C can be used to open a browser application. For example, in response to a user operation on browser icon 411C, such as a double-click of the left button, the terminal device can open the browser application and enter the address of the user webpage provided by the cloud platform in the browser address bar to log in to the user webpage provided by the cloud platform.

[0106] The taskbar 412 can be used to display icons of applications currently in use. For example, if the user has opened the WeChat application, the QQ application, and the browser program, the WeChat icon, the QQ icon, and the browser icon will be displayed on the taskbar 412. When the user clicks an icon in the taskbar 412, the terminal device determines whether the application corresponding to the icon is in an open state or a hidden state. If it is in an open state, the corresponding application is changed to a hidden state. Conversely, if it is in a hidden state, the corresponding application is changed to an open state.

[0107] The calendar indicator 413 may be used to indicate the current time, such as date, day of the week, hour and minute information, etc.

[0108] The start menu 414 is a fundamental part of the graphical user interface (GUI) in the Windows operating system (Windows) and can be considered the central control area of ​​the operating system. The start menu 414 generally includes options such as shut down the computer, run, help, search, settings, files, and an application list. Users can find the application list by clicking on the start menu 414. The application list can include shortcuts to multiple applications, such as a computer shortcut, a recycle bin shortcut, a browser shortcut, an email shortcut, a WeChat shortcut, a QQ shortcut, and the like. Among them, the browser shortcut can be used to launch a browser application. For example, in response to a user operation on a browser shortcut, such as double-clicking the left button, the terminal device can launch the browser application and enter the address of the user web page provided by the cloud platform in the browser's address bar to log in to the user web page provided by the cloud platform. By default, the start menu 414 is located at the lower left corner of the screen. Of course, the user can also set the start menu 414 to other locations on the screen as needed.

[0109] It is understandable that Figure 5 The user desktop on the terminal device is merely illustrated as an example and should not constitute a limitation on the embodiments of the present application.

[0110] The following details the resource purchase webpage and instance creation webpage on the terminal device. The resource purchase webpage is triggered by the user triggering the browser icon on the user's desktop and entering the address of the resource purchase webpage in the browser's address bar. The instance creation webpage is triggered by the user triggering the browser icon on the user's desktop and entering the address of the instance creation webpage in the browser's address bar. Here, users can purchase the computing resources, storage resources, and network resources they need through the resource purchase webpage. Then, they can create one or more instances based on the purchased computing resources, storage resources, and network resources through the instance creation webpage.

[0111] like Figure 6 As shown, the resource purchase webpage 510 may include: a title bar 511 , a resource name prompt box 512 , a computing resource input box 513A, a storage resource input box 513B, a network resource input box 513C, a purchase button 514 and a cancel button 515 .

[0112] The title bar 511 is used to display the theme of the web page, for example, the resource purchase page. The theme of the web page can be displayed in the center, on the left, etc., which is not specifically limited here.

[0113] The resource name prompt box 512 can be a display text box or an input text box. When the resource name is automatically generated by the cloud platform, the resource name prompt box 512 can be displayed in a display text box, and the resource name automatically generated by the cloud platform is displayed in the display text box; when the resource name is input by the user, the resource name prompt box 512 can be displayed in an input text box, and the resource name input by the user is displayed in the input text box. For example, the user can enter the resource name "S1" in the input text box.

[0114] The computing resource input box 513A, storage resource input box 513B, and network resource input box 513C can be used to enter the quantity of computing resources, storage resources, and network resources that the user wishes to purchase, respectively. For example, if the user wishes to purchase 20u of computing resources, 60G of storage resources, and 10M / mps of network resources, the user can enter 20u in the computing resource input box 513A, 60G in the storage resource input box 513B, and 10M / mps in the network resource input box 513C. It will be understood that computing resources can be divided into multiple computing basic units, storage resources can be divided into multiple storage basic units, and network resources can be divided into multiple network basic units. Therefore, when purchasing, the user needs to enter an integer multiple of the basic unit. In addition, although not shown in the figure, the user can also specify the type of computing resources, storage resources, and network resources. For example, the user can specify that the computing resources use a CPU chip + GPU chip, the storage resources use an SDD, the network resources use an SDN, and so on.

[0115] The buy button 514 is used for the user to confirm the purchase of the resource, whereas the cancel button 515 is used for the user to cancel the purchase of the resource. When the user clicks the buy button 514, the terminal device sends an allocation request to the cloud platform to allocate the resource purchased by the user to the user.

[0116] like Figure 7 As shown, the create instance webpage 610 may include: a title bar 611 , a resource name input box 612 , an instance quantity input box 613 , an instance unit 614 , a create button 615 , a cancel button 616 , a add button 617 and a delete button 618 .

[0117] The title bar 611 is used to display the theme of the web page, for example, the creation example page. Wherein, the theme of the web page can be displayed in the center, on the left, etc., which is not specifically limited here.

[0118] The resource name prompt box 612 may be an input text box, and the user may input the name of the resource for which an instance needs to be created into the resource name prompt box 612 .

[0119] The instance quantity input box 613 may be an input text box, and the user creates a corresponding number of instances on the resource according to the value input in the instance quantity input box 613 .

[0120] The number of instance units 614 is equal to the value entered in the instance quantity input box 613. Each instance unit 614 includes a computing resource input box 614A, a storage resource input box 614B and a network resource input box 614C, which can be used to input the number of computing resources, storage resources and network resources of the corresponding instance respectively.

[0121] For example, if the user wants to create two instances on the purchased resource named "S1", where instance 1 requires 5u of computing resources, 20G of storage resources, and 5M / mps of network resources, and instance 2 requires 10u of computing resources, 5G of storage resources, and 2M / mps of network resources, then the user can enter the resource name "S1" in the resource name prompt box 612, enter "2" in the instance quantity input box 613, enter 5u in the computing resource input box 614A of the instance unit 614 corresponding to instance 1, enter 20G in the storage resource input box 614B, and enter 5M / mps in the network resource input box 614C; enter 10u in the computing resource input box 614A of the instance unit 614 corresponding to instance 2, enter 5G in the storage resource input box 614B, and enter 2M / mps in the network resource input box 614C.

[0122] It can be understood that, although not shown in the figure, the user can also specify the types of computing resources, storage resources, and network resources used by each instance. For example, the user can specify that the computing resources of instance 1 use CPU chips + GPU chips, the storage resources use SDD, and the network resources use SDN; the computing resources of instance 2 use CPU chips, the storage resources use SDD, and the network resources use SDN, and so on.

[0123] The Create button 615 allows the user to confirm instance creation, while the Cancel button 616 allows the user to cancel instance creation. When the user clicks the Create button 615, the terminal device sends a Create Instance request to the cloud platform to create an instance based on the user's purchased resources. Conversely, when the user clicks the Cancel button 616, the terminal device does not send a Create Instance request to the cloud platform to create an instance based on the user's purchased resources. The Add button 617 is used to add instances for the user's purchased resources, and the Delete button 618 is used to delete instances for the user's purchased resources.

[0124] It is understandable that Figure 6 as well as Figure 7 The resource purchase webpage 510 and the instance creation webpage 610 on the terminal device are merely shown as examples and should not constitute a limitation on the embodiments of the present application.

[0125] The following will introduce in detail the new instance page and the delete instance page on the terminal device. Figure 8A As shown, the user can start the instance by clicking the Add button 617 on the Create Instance page. Figure 8B Add an instance page 710 as shown, thereby adding an instance to the resource purchased by the user, or, as shown in FIG. Figure 8C As shown, the user can start the process by clicking the delete button 618 on the create instance page. Figure 8D The delete instance web page 810 is shown, thereby reducing the instance for the resources purchased by the user.

[0126] like Figure 8B As shown, the new instance webpage 710 includes: a title bar 711 , a new instance quantity input box 712 , a new instance unit 713 , a create button 714 and a cancel button 715 .

[0127] The title bar 711 is used to display the theme of the web page, for example, a newly added instance page. The theme of the web page can be displayed in the center, on the left, etc., which is not specifically limited here.

[0128] The newly added instance quantity input box 712 may be an input text box, and the user adds a corresponding number of instances to the resource according to the value input in the newly added instance quantity input box 712 .

[0129] The number of newly added instance units 713 is equal to the value entered in the newly added instance number input box 712. Each newly added instance unit 713 includes a computing resource input box 713A, a storage resource input box 713B and a network resource input box 713C, which can be used to input the number of computing resources, storage resources and network resources of the corresponding instance respectively.

[0130] For example, if the user wants to add two new instances to the purchased resource "S1", among which instance 3 requires 3u of computing resources, 10G of storage resources, and 1M / mps of network resources, and instance 4 requires 2u of computing resources, 15G of storage resources, and 2M / mps of network resources, then the user can enter the value 2 in the new instance quantity input box 712, enter 3u in the computing resource input box 713A of the instance unit 713 corresponding to instance 3, enter 10G in the storage resource input box 713B, and enter 1M / mps in the network resource input box 713C; enter 2u in the computing resource input box 713A of the instance unit 713 corresponding to instance 4, enter 15G in the storage resource input box 713B, and enter 2M / mps in the network resource input box 713C.

[0131] It can be understood that, although not shown in the figure, the user can also specify the types of computing resources, storage resources, and network resources used by each instance. For example, the user can specify that the computing resources of instance 3 use CPU chips, the storage resources use SDD, and the network resources use SDN; the computing resources of instance 4 use CPU+GPU chips, the storage resources use SDD, and the network resources use SDN, and so on.

[0132] The Create button 714 is used for the user to confirm the creation of a new instance, whereas the Cancel button 715 is used for the user to cancel the creation of a new instance.

[0133] like Figure 8D As shown, the delete instance webpage 810 includes a title bar 811 , an instance selection box 812 , a delete button 813 , and a cancel button 814 .

[0134] The title bar 811 is used to display the theme of the web page, for example, the delete instance page. The theme of the web page can be displayed in the center, on the left, etc., which is not specifically limited here.

[0135] Instance selection box 812 can be used to display multiple created instances, from which the user can select the instance to be deleted. For example, instance selection box 812 may display that instance 1, instance 2, instance 3, and instance 4 have been created on resource "S1". When instance 1 and instance 2 are selected by the user, the cloud platform can delete instance 1 and instance 2, and release the computing resources, storage resources, and network resources occupied by instance 1 and instance 2.

[0136] The delete button 813 is used for the user to confirm deleting the instance, whereas the cancel button 814 is used for the user to cancel deleting the instance.

[0137] It is understandable that Figure 8B as well as Figure 8D The newly added instance webpage 710 and the deleted instance webpage 810 on the terminal device are merely exemplified and should not constitute a limitation on the embodiments of the present application.

[0138] See also Figure 9A , Figure 9A This is a flow chart of an example creation method provided by this application. The example creation method of this embodiment includes:

[0139] S101: A terminal device receives a first resource allocation request input by a user, wherein the first resource allocation request is used to request a cloud platform to allocate resources required by the user to the user.

[0140] In a specific embodiment, the first resource allocation request may include the resource name, the quantity of computing resources, storage resources, and network resources that the user wishes to purchase, etc. Furthermore, the resource allocation request may also include the type of computing resources, storage resources, and network resources specified by the user, etc., which are not specifically limited herein.

[0141] In a specific embodiment, the user can log in to the resource purchase webpage provided by the cloud platform through a terminal device and enter the resource name, the number of computing resources, storage resources and network resources that the user wants to purchase on the resource purchase webpage. For details, please refer to Figure 6 And related content will not be described in detail here.

[0142] S102: The terminal device sends a first resource allocation request to the cloud platform via the network device. Correspondingly, the cloud platform receives the first resource allocation request sent by the terminal device via the network device.

[0143] S103: The cloud platform allocates the first resource required by the user to the user according to the first resource allocation request sent by the terminal device.

[0144] In a specific embodiment, the cloud platform may allocate to the user the amount of computing resources, storage resources, and network resources that the user wishes to purchase.

[0145] In a specific embodiment, after the cloud platform allocates the first resource required by the user to the user, the cloud platform opens the user to the permission to view the usage status of the first resource. The user can query the usage status of the first resource, such as the usage status of computing resources, the usage status of storage resources, the usage status of network resources, etc.

[0146] In a specific embodiment, a user can optimize the usage of resources allocated to the user. After the cloud platform allocates the resources required by the user, the user can create a traditional data center of his own on these resources and optimize these resources using traditional optimization methods of his own data center.

[0147] S104: The terminal device receives a first instance creation request input by a user, wherein the first instance creation request is used to request the cloud platform to create an instance on the resource.

[0148] In a specific embodiment, the first instance creation request may include the number of instances, the computing resources required by the instance, the storage resources required by the instance, the network resources required by the instance, etc. Optionally, the instance creation request may also include the type of computing resources used by the instance, the type of storage resources used by the instance, the type of network resources used by the instance, etc., which are not specifically limited here.

[0149] In a specific embodiment, a user can view the usage status of a first resource and determine how to create an instance based on the usage status of the first resource. Specifically, the user can send a first query instruction to the cloud platform. The cloud platform queries the usage status of the first resource based on the first query instruction and sends the usage status of the first resource to the user. The user can then determine how to create an instance based on the usage status of the first resource.

[0150] In a specific embodiment, Figure 10 As shown, the cloud platform can set a first scheduling manager on the resource pool, that is, Figure 4A The schedule manager 218 shown, or Figure 4B The scheduling manager 317 shown creates a second scheduling manager and a resource monitoring system on the first resource allocated to the user. The first scheduling manager belongs to the cloud platform provider, meaning the cloud platform provider can schedule and manage resources in the resource pool through the first scheduling manager. The second scheduling manager and resource monitoring system belong to the user, meaning the user can monitor the usage of the first resource through the resource monitoring system and schedule and manage resources in the first resource through the second scheduling manager, thereby achieving load balancing of instances in the first resource and early prediction of failures.

[0151] In a specific embodiment, the user can log in to the instance creation webpage provided by the cloud platform through a terminal device and enter the instance quantity, computing resources required by the instance, storage resources required by the instance, and network resources required by the instance on the instance creation webpage. For details, please refer to Figure 7 And related content will not be described in detail here.

[0152] S105: The terminal device sends a first instance creation request to the cloud platform via the network device. Correspondingly, the cloud platform receives the first instance creation request sent by the terminal device via the network device.

[0153] S106: The cloud platform creates multiple instances on the first resource according to the first instance creation request sent by the terminal device.

[0154] In this embodiment, the cloud platform allocates the resources required by the user to the user, and the user can create an instance on the first resource according to his or her needs. Since the first resource belongs to the user, the user can set up a second scheduling manager and a resource monitoring system on the first resource by himself or herself. The resource monitoring system can monitor the usage status of the first resource, and the second scheduling manager can be used to schedule and manage the first resource according to the usage status of the first resource, thereby improving the utilization rate of the first resource.

[0155] After the cloud platform creates multiple instances on the first resource, it can also add instances on the first resource to improve the utilization of the first resource, or reduce instances on the first resource to reduce the load of the first resource, thereby improving the performance of the instances on the first resource.

[0156] like Figure 9B As shown, the cloud platform can add one or more instances to the first resource. Figure 9A Based on steps S101 to S106 of the example creation method shown, the following steps may be added:

[0157] S107: The terminal device receives a new instance request input by the user, wherein the new instance request is used to request the cloud platform to add an instance on the resource.

[0158] In a specific embodiment, the request to add an instance may include the resource name, the number of instances to be added, the number of computing resources, storage resources, and network resources for each instance to be added, etc. Furthermore, the resource allocation request may also include the type of computing resources, storage resources, and network resources specified by the user for the instance to be added, etc., which are not specifically limited here.

[0159] In a specific embodiment, the user can log in to the new instance page provided by the cloud platform through a terminal device and enter the number of new instances, the number of computing resources, the number of storage resources, and the number of network resources for each new instance on the new instance page. For details, please refer to Figure 6 And related content will not be described in detail here.

[0160] S109: The terminal device sends a request for adding a new instance to the cloud platform via the network device. Correspondingly, the cloud platform receives the request for adding a new instance sent by the terminal device via the network device.

[0161] S111: The cloud platform adds one or more instances to the resource according to the new instance request sent by the terminal device.

[0162] like Figure 9C As shown, the cloud platform can reduce one or more instances on the first resource. Figure 9ABased on steps S101 to S106 of the example creation method shown, the following steps may be added:

[0163] S108: The terminal device receives a deletion instance request input by the user, wherein the deletion instance request is used to request the cloud platform to delete the instance on the resource.

[0164] In a specific embodiment, the instance deletion request may carry a resource name, a deletion instance identifier, and the like.

[0165] In a specific embodiment, the user can log in to the delete instance page provided by the cloud platform through the terminal device, and select the instance to be deleted on the delete instance page, etc. For details, please refer to Figure 7 And related content will not be described in detail here.

[0166] S110: The terminal device sends a request to delete the instance to the cloud platform via the network device. Correspondingly, the cloud platform receives the request to delete the instance sent by the terminal device via the network device.

[0167] S112: The cloud platform deletes one or more instances on the first resource according to the instance deletion request sent by the terminal device.

[0168] See also Figure 11 , Figure 11 This is a flow chart of the second instance creation method provided by this application. The instance creation method of this embodiment includes:

[0169] S201: A first terminal device receives a second resource allocation request input by a third party, wherein the second resource allocation request is used to request a cloud platform to allocate resources required by the third party to the third party.

[0170] In a specific embodiment, the third party may be an intermediary that specializes in purchasing resources from cloud service providers and distributing the purchased resources to consumers.

[0171] In a specific embodiment, the second resource allocation request may include the resource name, the quantity of computing resources, storage resources, and network resources that the user wishes to purchase, etc. Furthermore, the second resource allocation request may also include the type of computing resources, storage resources, and network resources specified by the user, etc., which are not specifically limited herein.

[0172] In a specific embodiment, the third party can log in to the resource purchase webpage provided by the cloud platform through the first terminal device and enter the resource name, the number of computing resources, storage resources and network resources that the user wants to purchase on the resource purchase webpage. For details, please refer to Figure 6 And related content will not be described in detail here.

[0173] S202: The first terminal device sends a second resource allocation request to the cloud platform via the network device. Correspondingly, the cloud platform receives the second resource allocation request sent by the first terminal device via the network device.

[0174] S203: The cloud platform allocates the second resource required by the third party to the third party according to the second resource allocation request sent by the first terminal device.

[0175] In a specific embodiment, the cloud platform may allocate the amount of computing resources, storage resources, and network resources that the third party wishes to purchase to the third party.

[0176] In a specific embodiment, after the cloud platform allocates resources required by a third party to the third party, the cloud platform grants the third party access to view the usage status of these resources. The third party can query the usage of these resources, such as computing resource usage, storage resource usage, and network resource usage. Conversely, for resources not allocated to the third party, the cloud platform does not grant access to view the usage status of these resources, and the third party cannot query the usage of these resources.

[0177] In a specific embodiment, a third party can optimize the use of resources allocated to the third party. After the cloud platform allocates the resources required by the third party to the third party, the third party can create a traditional data center of its own on these resources and optimize these resources using traditional optimization methods of its own data center.

[0178] S204: The second terminal device receives a second instance creation request input by the user, wherein the second instance creation request is used to request the cloud platform to create an instance on the second resource.

[0179] In a specific embodiment, the second instance creation request may carry the number of instances, the computing resources required by the instance, the storage resources required by the instance, the network resources required by the instance, etc. Optionally, the instance creation request may also carry the type of computing resources used by the instance, the type of storage resources used by the instance, the type of network resources used by the instance, etc., which are not specifically limited here.

[0180] In a specific embodiment, the user can log in to the instance creation webpage provided by the cloud platform through the second terminal device, and enter the instance quantity, computing resources required by the instance, storage resources required by the instance, and network resources required by the instance on the instance creation webpage. For details, please refer to Figure 7 And related content will not be described in detail here.

[0181] S205: The second terminal device sends a second instance creation request to the cloud platform via the network device. Correspondingly, the cloud platform receives the second instance creation request sent by the second terminal device via the network device.

[0182] S206: The cloud platform creates multiple instances on the second resource according to the second instance creation request sent by the second terminal device.

[0183] In a specific embodiment, a third party can view the usage status of the second resource and determine how to create an instance based on the usage status of the second resource. Specifically, the third party can send a second query instruction to the cloud platform. The cloud platform queries the usage status of the second resource based on the second query instruction and sends the usage status of the second resource to the third party. The third party can then determine how to allow the user to create an instance based on the usage status of the second resource.

[0184] It is understood that users can also add and delete instances on the second resource. The specific process is the same as Figure 9A Adding and deleting instances on the corresponding first resource are similar. Figure 9A Steps S107-S112 in the above description will not be described in detail here.

[0185] In the above embodiment, the third party can purchase the second resource from the provider of the cloud platform and create an instance on the second resource according to the needs of the user. The third party acts as an intermediary to manage and charge users, which encourages the third party to create more services that improve the utilization of the cloud platform, thereby prospering the cloud platform market.

[0186] See also Figure 12 , Figure 12 The management node of this embodiment includes: a receiving module 910 , an allocating module 920 , and a creating module 930 .

[0187] In a specific embodiment, each module of the cloud platform can perform the following functions:

[0188] The receiving module 910 is configured to receive a first resource allocation request from a first user, wherein the first resource allocation request includes the amount of resources that the first user needs to allocate.

[0189] The allocation module 920 is configured to allocate the first resource to the first user according to the quantity of resources required to be allocated to the first user;

[0190] The receiving module 910 is configured to receive a first instance creation request from the first user, wherein the first instance creation request includes the number of instances that the first user needs to create;

[0191] The creation module 930 is configured to create instances on the first resource according to the number of instances that the first user needs to create.

[0192] In the above solution, the cloud platform can execute Figure 9A-9B For details, see the method described in Figure 9A-9B The records in the article will not be described in detail here.

[0193] In a specific embodiment, each module of the cloud platform can perform the following functions:

[0194] The receiving module 910 is used for the cloud platform to receive a second resource allocation request from a third party, wherein the second resource allocation request includes the amount of resources that the third party needs to allocate;

[0195] The allocation module 920 is configured to allocate the second resource to the third party according to the quantity of resources required to be allocated to the third party;

[0196] The receiving module 910 is configured to receive a second instance creation request from a second user, wherein the second instance creation request includes the number of instances that the second user needs to create;

[0197] The creation module 930 is configured to create instances on the second resource according to the number of instances that the second user needs to create.

[0198] In the above embodiment, the cloud platform can execute Figure 11 For details, see the method described in Figure 11 The records in the article will not be described in detail here.

[0199] See also Figure 13 , Figure 13 This is a schematic diagram of the structure of a management node provided by this application. The management node of this embodiment can be Figure 4A as well as Figure 4B Management node in the cloud platform. In this embodiment, the management node may include: one or more processing units 1010, one or more I / O devices 1020 and expansion interfaces 1030, etc.

[0200] The processing unit 1010 may include a processor 1011, such as a central processing unit (CPU). The CPU may adopt a complex instruction set computer (CISC) architecture (e.g., x86 architecture), a reduced instruction set computer (RISC) architecture (e.g., MIPS (microprocessor without interlocked piped stages) architecture), or the like.

[0201] The processing unit 1010 may further include an internal memory 1012 , a chipset 1013 , registers (not shown), and the like.

[0202] Internal memory 1012 is used to store instructions or data that have just been used or are recycled by processor 1011, such as a cache memory. If processor 1011 needs to use the instruction or data again, it can directly call it from internal memory 1012, reducing the waiting time of processor 1011 and thus improving system efficiency. When the contents of a memory data page in internal memory 1012 are inconsistent with the contents of a data page in memory 1021, this memory data page can be called a dirty page; when the contents of a memory data page in internal memory 1012 are consistent with the contents of a data page in memory 1021, this memory data page can be called a clean page.

[0203] The chipset may include a northbridge chip 1015, which is the chip closest to the CPU and is responsible for data transmission between the processor 1011 and the internal memory 1012. Because the northbridge chip 1015 processes a very large amount of data and generates a very large amount of heat, the northbridge chip 1015 may be covered with a heat sink or equipped with a fan to enhance heat dissipation. Optionally, the chipset may also include a southbridge chip 1014, one end of which is connected to the processor 1011 through the northbridge chip 1015, and the other end is connected to interfaces of various external devices. In some specific embodiments, the northbridge chip 1015 may be integrated into the processor 1011, or some of the functions of the southbridge chip 1014 are integrated into the northbridge chip 1015, or the southbridge chip 1014 may be integrated into the processor 1011, or the southbridge chip 1014 is integrated into the northbridge chip 1015, and so on.

[0204] Registers are high-speed storage components with limited storage capacity. They can be used to temporarily store OS status data such as instructions, data, and addresses, for example, the instruction register (IR), program counter (PC), and accumulator (ACC).

[0205] Optionally, the processing unit 1011 further includes a digital signal processor (DSP), a graphics processing unit (GPU), a neural-network processing unit (NPU), etc. When the number of processors in the processing unit is multiple, the processors in the processing unit can adopt a homogeneous structure or a heterogeneous structure. Common heterogeneous structures can be CPU+DSP, CPU+NPU, CPU+GPU, CPU+DSP+GPU, etc.

[0206] I / O device 1020 may include memory 1021, which can be used to store executable program code, including instructions. Processor 1011 executes various functional applications and data processing functions of the management node by running the instructions in memory 1021. Memory 1021 may store code for the operating system and virtual machine monitor (VMM). The operating system can be a user-installed system, such as Linux, Windows, or DOS. The VMM is optional; that is, it is not normally active and only operates during live migration. The VMM can be lightweight, requiring only basic functions such as CPU virtualization and memory virtualization, or heavyweight, such as XEN, KVM, and other VMMs capable of performing advanced functions. Furthermore, I / O device 1020 may include input devices 1022 and output devices 1023. Input devices 1022 may include a keyboard, mouse, scanner, camera, and microphone. Output devices 1023 may include speakers, amplifiers, printers, monitors, and graphics cards.

[0207] The expansion interface 1030 may include multiple interfaces, for example, a peripheral component interconnect (PCI) interface, a peripheral component interconnect express (PCIe) interface, a universal serial bus (USB) interface, a universal asynchronous receiver / transmitter (UART interface), a joint test action group (JTAG) interface, and the like.

[0208] The management node may also include a basic input / output system (BIOS) and the like.

[0209] The BIOS, also known as the Read-Only Memory (ROM) BIOS, system BIOS, or personal computer (PC) BIOS, is a component that initializes and tests hardware. It also loads a boot program from memory 1031, which then loads the operating system and VMM. If the operating system is a DOS system, the BIOS also provides a hardware abstraction layer for the keyboard, display, and other I / O devices.

[0210] It is understandable that the above-mentioned management node may also include more components, such as a clock chip, a power management chip, etc., which are not specifically limited here.

[0211] In the above embodiment, the cloud platform can execute Figures 9A-9C as well as Figure 11 For details, see the method described in Figures 9A-9C as well as Figure 11 The records in the article will not be described in detail here.

[0212] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a storage disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state storage disk Solid State Disk (SSD)).

Claims

1. A method for creating an instance, characterized in that: include: The cloud platform receives a first resource allocation request from a first user, wherein the first resource allocation request includes the quantity of resources that the first user needs to allocate; The cloud platform allocates the first resource to the first user according to the quantity of resources required to be allocated to the first user; The cloud platform receives a first instance creation request from the first user, wherein the first instance creation request includes the number of instances that the first user needs to create; The cloud platform creates instances on the first resource according to the number of instances required to be created by the first user; The cloud platform receives a first instance adding request from the first user, wherein the first instance adding request includes the number of instances that the first user needs to add; The cloud platform adds instances to the first resource according to the number of new instances required by the first user.

2. The method according to claim 1, characterized in that The cloud platform receives a first instance deletion request from the first user, wherein the first instance deletion request includes the number of instances that the first user needs to delete; The cloud platform deletes instances on the first resource according to the number of instances that the first user needs to delete.

3. The method according to claim 1, characterized in that The cloud platform receives a first query instruction from the user, The cloud platform queries the usage status of the first resource according to the first query instruction, and sends the usage status of the first resource to the user.

4. The method according to claim 1, wherein The number of instances that the first user needs to create is greater than or equal to 2.

5. A method for creating an instance, characterized in that: include: The cloud platform receives a second resource allocation request from a third party, wherein the second resource allocation request includes the quantity of resources that the third party needs to allocate; The cloud platform allocates the second resource to the third party according to the quantity of resources required to be allocated by the third party; The cloud platform receives a second instance creation request from a second user, wherein the second instance creation request includes the number of instances that the second user needs to create; The cloud platform creates instances on the second resource according to the number of instances that the second user needs to create; The cloud platform receives a second instance adding request from the second user, wherein the second instance adding request includes the number of instances that the second user needs to add; The cloud platform adds instances to the second resource according to the number of instances required by the second user.

6. The method according to claim 5, characterized in that The cloud platform receives a second instance deletion request from the second user, wherein the second instance deletion request includes the number of instances that the second user needs to delete; The cloud platform deletes instances on the second resource according to the number of instances that the second user needs to delete.

7. The method according to claim 5, characterized in that The cloud platform receives a second query instruction from the third party, The cloud platform queries the usage status of the second resource according to the second query instruction, and sends the usage status of the second resource to the third party.

8. The method according to claim 5, characterized in that The number of instances that the second user needs to create is greater than or equal to 2.

9. A cloud platform, characterized in that: include: Receive modules, assign modules, create modules, and add new modules. The receiving module is configured to receive a first resource allocation request from a first user, wherein the first resource allocation request includes the amount of resources that the first user needs to allocate; The allocation module is configured to allocate the first resource to the first user according to the quantity of resources required to be allocated to the first user; The receiving module is configured to receive a first instance creation request from the first user, wherein the first instance creation request includes the number of instances that the first user needs to create; The creation module is used to create instances on the first resource according to the number of instances that the first user needs to create; The receiving module is configured to receive a first instance adding request from the first user, wherein the first instance adding request includes the number of instances that the first user needs to add; The adding module is used to add instances to the first resource according to the number of instances required by the first user.

10. The cloud platform according to claim 9, characterized in that: The cloud platform also includes a deletion module, The receiving module is configured to receive a first instance deletion request from the first user, wherein the first instance deletion request includes the number of instances that the first user needs to delete; The deletion module is configured to delete instances on the first resource according to the number of instances that the first user needs to delete.

11. The cloud platform according to claim 9, characterized in that: The cloud platform also includes a query module, The receiving module is used to receive the first query instruction of the user, The query module is used to query the usage status of the first resource according to the first query instruction, and send the usage status of the first resource to the user.

12. The cloud platform according to claim 9, characterized in that: The number of instances that the first user needs to create is greater than or equal to 2.

13. A cloud platform, characterized in that: include: Receive modules, assign modules, create modules, and add new modules. The receiving module is used for the cloud platform to receive a second resource allocation request from a third party, wherein the second resource allocation request includes the amount of resources that the third party needs to allocate; The allocation module is configured to allocate the second resource to the third party according to the quantity of resources required to be allocated to the third party; The receiving module is configured to receive a second instance creation request from a second user, wherein the second instance creation request includes the number of instances that the second user needs to create; The creation module is used to create instances on the second resource according to the number of instances that the second user needs to create; The receiving module is configured to receive a second instance adding request from the second user, wherein the second instance adding request includes the number of instances that the second user needs to add; The adding module is used to add instances to the second resource according to the number of instances required by the second user.

14. The cloud platform according to claim 13, wherein: The cloud platform also includes a deletion module, The receiving module is configured to receive a second instance deletion request from the second user, wherein the second instance deletion request includes the number of instances that the second user needs to delete; The deletion module is configured to delete instances on the second resource according to the number of instances that the second user needs to delete.

15. The cloud platform according to claim 13, wherein: The cloud platform also includes a query module, The receiving module is used to receive a second query instruction from the third party, The query module is used to query the usage status of the second resource according to the second query instruction, and send the usage status of the second resource to the third party.

16. The cloud platform according to claim 13, wherein: The number of instances that the second user needs to create is greater than or equal to 2.

17. A management node, characterized in that: The method comprises a processor and a memory, wherein the processor executes the code in the memory to perform the method according to any one of claims 1 to 8.

18. A computer-readable storage medium, characterized in that The method comprises instructions, which, when executed on a computer, cause the computer to execute the method according to any one of claims 1 to 8.

Images