CN116107593A

CN116107593A - Cloud service deployment method based on public cloud and related equipment

Info

Publication number: CN116107593A
Application number: CN202111335824.0A
Authority: CN
Inventors: 吴强伟
Original assignee: Huawei Cloud Computing Technologies Co Ltd
Current assignee: Huawei Cloud Computing Technologies Co Ltd
Priority date: 2021-11-11
Filing date: 2021-11-11
Publication date: 2023-05-12

Abstract

The application discloses a cloud service deployment method based on public cloud, which is applied to a cloud platform and comprises the following steps: providing a registration interface, wherein the registration interface is used for respectively acquiring registration information of a plurality of cloud service deployers; recording registration information of a plurality of cloud service deployers; providing a demand acquisition interface, wherein the demand acquisition interface is used for acquiring cloud service configuration demands of a user; determining a target cloud service deployer matching the cloud service configuration requirements from the registration information, and providing the transaction order to the target cloud service deployer. In this way, the cloud platform can utilize cloud service deployer resources on the cloud platform to match a proper target cloud service deployer for the user, and establish a service relationship between the target cloud service deployer and the user through the transaction order, so that the target cloud service deployer can help the user to deploy and obtain the desired cloud service.

Description

Cloud service deployment method based on public cloud and related equipment

Technical Field

The application relates to the technical field of cloud services, in particular to a public cloud-based cloud service deployment method and related equipment.

Background

With the continuous development of information technology, users in many fields have various demands for cloud services.

At present, after a service provider develops a cloud service through a cloud platform, information such as sales price, specific functions and the like of the cloud service is released in a cloud market, and a user can select and purchase the cloud service displayed on the cloud market. If the user cannot find the required cloud service in the cloud market, the user needs to contact the service provider by himself to develop the cloud service for the user. However, it is often difficult for the user to contact with a suitable service provider by himself, so that the user cannot conveniently and effectively obtain the service provider resource to develop and obtain the cloud service wanted by the user, which results in higher difficulty for the user to obtain the wanted cloud service.

Disclosure of Invention

The embodiment of the application provides a cloud service deployment method based on public cloud, which is used for solving the problem that a user cannot conveniently and effectively obtain service provider resources to develop and obtain cloud services wanted by the user, so that the difficulty of obtaining wanted cloud services by the user is high. The embodiment of the application also provides a corresponding device, a cloud platform, a computer readable storage medium, a computer program product and the like.

The first aspect of the application provides a cloud service deployment method based on public cloud, which is applied to a cloud platform and comprises the following steps: providing a registration interface, wherein the registration interface is used for respectively acquiring registration information of a plurality of cloud service deployers, and each registration information comprises an account number of the corresponding cloud service deployer on a cloud platform, cloud service deployment skills and service prices; recording registration information of a plurality of cloud service deployers; providing a demand acquisition interface, wherein the demand acquisition interface is used for acquiring cloud service configuration demands of a user, and the cloud service configuration demands comprise types of target cloud services which the user needs to configure on a cloud platform and prices which the user can pay; determining a target cloud service deployer matching the cloud service configuration requirements from the registration information, and providing the transaction order to the target cloud service deployer.

In the first aspect, the cloud platform may be a public cloud platform, and at this time, a person with cloud resource development capability or a cloud service deployer such as a third party software developer may provide cloud services for users, where the users obtain cloud services through the internet, but do not have cloud computing resources. The registration interface and the requirement acquisition interface may be in the form of an application program interface (application programming interface, API) or a configuration interface, respectively. The number of target cloud service deployers matched with the cloud service configuration requirements can be one or at least two. If the number of target cloud service deployers is at least two, each target cloud service deployer may be used to complete a different part of the development work of the target cloud service.

As can be seen from the foregoing, in the first aspect, the cloud platform may provide a registration interface and record registration information of a plurality of cloud service deployers obtained through the registration interface. Thus, each individual and organization having cloud service deployment skills can register the cloud platform through the registration interface and become a cloud service deployment person on the cloud platform. In addition, the cloud platform can also provide a requirement acquisition interface to acquire cloud service configuration requirements of the user through the requirement acquisition interface. After obtaining the cloud service configuration requirements of the user, a target cloud service deployer matching the cloud service configuration requirements may be determined from the registration information, and a trade order may be provided to the target cloud service deployer. In this way, the cloud platform can utilize cloud service deployer resources on the cloud platform to match a proper target cloud service deployer for the user, and establish a service relationship between the target cloud service deployer and the user through the transaction order, so that the target cloud service deployer can help the user to deploy and obtain the desired cloud service.

In a possible implementation manner of the first aspect, the method further includes: providing a cloud service deployment interface, and enabling a target cloud service deployment person to deploy target cloud service on a cloud platform through the cloud service deployment interface; and sending the product information of the target cloud service which is successfully deployed to the user, wherein the product information is used for indicating the user to use the target cloud service on the cloud platform.

In this possible implementation, the cloud service deployment interface may be in the form of a designated interface or API, etc. There may be a variety of types of target cloud services, for example, the target cloud services may be cloud resource-based software products, database products, and/or data processing services, among others. Illustratively, the target cloud service deployer may access cloud resources such as virtual machines and/or containers to be deployed through a cloud service deployment interface, so as to deploy corresponding target cloud services in the accessed virtual machines and/or containers, for example, develop software in the accessed virtual machines and/or containers, perform database management and/or perform other data processing operations, so as to obtain deployed virtual machines and/or containers, where the deployed virtual machines and/or containers may serve as products of successfully deployed target cloud services, and product information of successfully deployed target cloud services may include information of the deployed virtual machines and/or containers.

In such a possible implementation, the target cloud service may be deployed at the cloud platform by a target cloud service deployer through a cloud service deployment interface. Because the target cloud service deployer usually has rich expertise in developing cloud resources. In addition, the successfully deployed target cloud service product is obtained by deploying cloud resources such as virtual machines and/or containers based on a cloud platform, so that the cloud platform can flexibly allocate various resources such as the resources of a deployer and the cloud resources, not only can the deployer resources be effectively utilized, but also the managed cloud resources can be effectively utilized based on the requirements of users.

In a possible implementation manner of the first aspect, the steps are as follows: determining a target cloud service deployer matching the cloud service configuration requirements from the registration information, providing a trade order to the target cloud service deployer, comprising: determining at least two deployment tasks corresponding to cloud service configuration requirements; determining a target cloud service deployer corresponding to each deployment task from a plurality of cloud service deployers; each target cloud service deployer is provided with a trade order obtained according to the respective deployment task.

At present, because the deployment difficulty and workload of various cloud services are generally large, only service providers such as software vendors with a certain scale can provide complete cloud services for users, and individual deployers or small service providers have difficulty in acquiring orders of clients and are difficult to be effectively utilized to deploy and develop cloud services for the clients. In the possible implementation manner, different target cloud service deployers can complete different deployment tasks, so that target cloud services required by users can be split into different development contents, and then different deployment tasks can be allocated to different target cloud service deployers, so that a plurality of deployer resources can be called to cooperatively complete target cloud services required by the users, a plurality of deployers can be flexibly organized to complete different deployment parts in one service requirement of the users, various deployer resources are effectively utilized, and the requirements on team scale and deployment capacity of the cloud service deployers are greatly reduced.

In a possible implementation manner of the first aspect, the steps are as follows: determining at least two deployment tasks corresponding to cloud service configuration requirements, comprising: determining a target preset cloud service from a plurality of preset cloud services according to cloud service configuration requirements; acquiring a configuration grade corresponding to cloud service configuration requirements; and determining at least two deployment tasks corresponding to cloud service configuration requirements according to the preset tasks corresponding to the target preset cloud service at the configuration level.

In the possible implementation manner, through the information of at least two dimensions such as the type and the configuration level of the cloud service, the service can be split more accurately according to the preset cloud service and the preset tasks corresponding to the different configuration levels of each preset cloud service, and each deployment task which accords with the division conditions in the deployment process can be obtained.

In a possible implementation manner of the first aspect, the steps are as follows: determining a target cloud service deployer corresponding to each deployment task from a plurality of cloud service deployers, including: according to the task information of each deployment task and the registration information of each cloud service deployer, determining cloud service deployers respectively matched with each deployment task, wherein the task information comprises task prices and/or task categories; and determining a target cloud service deployer corresponding to each deployment task from cloud service deployers matched with each deployment task.

In this possible implementation, determining that the deployment task matches a certain cloud service deployer may include at least one of: 1. the task category of the deployment task is matched with the cloud service deployment skill of the cloud service deployment person; 2. the task price of the deployment task matches the service price of the cloud service deployer. Through the possible implementation manner, the target cloud service deployer corresponding to each deployment task can be more accurately matched.

In a possible implementation manner of the first aspect, the steps are as follows: from cloud service deployers matched with each deployment task, determining a target cloud service deployer corresponding to each deployment task comprises the following steps: sending order request information to at least one cloud service deployer matched with the deployment task, wherein the order request information is used for requesting to generate a transaction order of the corresponding cloud service deployer about the deployment task; and taking the cloud service deployer corresponding to the received first confirmation information of the first order request information as a target cloud service deployer of the corresponding deployment task.

In this possible implementation manner, by way of example, the target cloud service deployer using the cloud service deployer corresponding to the received first confirmation information for the order request information as the corresponding deployment task may be: and taking the cloud service deployer corresponding to the first confirmation information of the received first order request information as the target cloud service deployer corresponding to the corresponding deployment task within a preset time period from the moment of sending the order request information. Through the possible implementation manner, the corresponding target cloud service deployer can be determined for each deployment task more quickly.

In a possible implementation manner of the first aspect, the steps are as follows: determining at least two deployment tasks corresponding to cloud service configuration requirements, comprising: determining a first cloud service deployment person according to cloud service configuration requirements; receiving second confirmation information sent by the first cloud service deployer, wherein the second confirmation information comprises information of at least two deployment tasks; the steps are as follows: determining a target cloud service deployer corresponding to each deployment task from a plurality of cloud service deployers, including: receiving third confirmation information sent by the first cloud service deployer, wherein the third confirmation information comprises information of target cloud service deployers corresponding to each deployment task, the target cloud service deployers comprise the first cloud service deployers, and the operation authority of the first cloud service deployers for cloud service configuration requirements is higher than that of other cloud service deployers except the first cloud service deployers in the target cloud service deployers; the steps are as follows: providing each target cloud service deployer with a trade order obtained according to a respective deployment task, comprising: and generating a corresponding trade order of each target cloud service deployment according to the second confirmation information and the third confirmation information, and providing the corresponding trade order for each target cloud service deployment.

In this possible implementation manner, the first cloud service deployer may be considered as a leader among the plurality of target cloud service deployers, after obtaining the cloud service configuration requirement, the first cloud service deployer corresponding to the cloud service configuration requirement may be determined first, each corresponding deployment task is determined by the first cloud service deployer according to the cloud service configuration requirement, and the target cloud service deployer corresponding to each deployment task is determined. In this possible implementation manner, a temporary deployer team can be constructed by the first cloud service deployer to cooperatively complete the target cloud service required by the user, so that individuals with cloud service deployment skills can be flexibly combined to complete the cloud service required by the user according to actual requirements.

A second aspect of the present application provides a public cloud-based cloud service deployment apparatus, which may be applied to a cloud platform, where the public cloud-based cloud service deployment apparatus has a function of implementing the foregoing first aspect or any one of the possible implementation manners of the first aspect. The functions can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above, such as: the device comprises a first interface module, a recording module, a second interface module and a processing module.

A third aspect of the present application provides a cloud platform comprising at least one processor, a memory, a communication interface and computer-executable instructions stored in the memory and executable on the processor, the processor performing the method as described above for the first aspect or any one of the possible implementations of the first aspect when the computer-executable instructions are executed by the processor.

A fourth aspect of the present application provides a computer readable storage medium storing one or more computer executable instructions which, when executed by a processor, perform a method as described above or any one of the possible implementations of the first aspect.

A fifth aspect of the present application provides a computer program product storing one or more computer-executable instructions which, when executed by a processor, perform a method as described above or any one of the possible implementations of the first aspect.

A sixth aspect of the present application provides a chip system comprising a processor for supporting a cloud platform to implement the functions involved in the first aspect or any one of the possible implementations of the first aspect. In one possible design, the chip system may further include a memory to hold program instructions and data necessary for the cloud platform. The chip system can be composed of chips, and can also comprise chips and other discrete devices.

The technical effects of the second aspect to the sixth aspect or any one of the possible implementation manners of the second aspect may be referred to technical effects of the first aspect or technical effects of different possible implementation manners of the first aspect, which are not described herein.

Drawings

FIG. 1 is a schematic diagram of a system architecture according to an embodiment of the present application;

FIG. 2 is a schematic diagram of an embodiment of a public cloud-based cloud service deployment method according to an embodiment of the present application;

FIG. 3 is an exemplary schematic diagram of virtual machine resources corresponding to a determined target cloud service according to an embodiment of the present application;

FIG. 4 is a schematic diagram of information interaction regarding deployment and processing of virtual machine resources provided by embodiments of the present application;

FIG. 5 is a schematic diagram of an embodiment of a public cloud-based cloud service deployment method according to an embodiment of the present application;

FIG. 6 is a schematic diagram of an embodiment of a public cloud-based cloud service deployment apparatus according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a cloud platform according to an embodiment of the present application.

Detailed Description

Embodiments of the present application will now be described with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some, but not all embodiments of the present application. As a person of ordinary skill in the art can know, with the development of technology and the appearance of new scenes, the technical solutions provided in the embodiments of the present application are applicable to similar technical problems.

The terms first, second and the like in the description and in the claims of the present application and in the above-described figures, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Fig. 1 shows a schematic diagram of a system architecture according to an embodiment of the present application.

The embodiment of the application can be applied to a cloud platform. The cloud platform is described below in conjunction with a system architecture diagram shown in fig. 1.

The cloud platform may also be referred to as a cloud management platform, which is a platform capable of providing computing and storage services. Cloud platforms are typically composed of clusters of cloud servers, which refer to physical servers capable of providing elastic computing services (Elastic Compute Service, ECS). In the embodiment of the application, the cloud platform may be a public cloud platform, and at this time, a person with cloud resource development capability or a cloud service deployment person such as a third party software developer may provide cloud services for users, and the users acquire cloud services through the internet, but do not have cloud computing resources.

The cloud platform interacts with one or more servers (e.g., server 1 and server 2 in fig. 1) via a data center internal network. The server includes a hardware layer and a software layer, the hardware layer includes hardware configured by the server, where the PCI device may be, for example, a network card, a graphics processor (graphics processing unit, GPU), an offload card, or a device that may be plugged into a peripheral device interconnect standard (peripheral component interconnect, PCI) or a peripheral device high-speed connection standard (peripheral component interconnect express, PCIe) slot of the server, the software layer includes an operating system (an operating system of a relative virtual machine may be referred to as a host machine operating system) installed and running on the server, and a virtual machine manager (also referred to as a hypervisor) is disposed in the host machine operating system, where the virtual machine manager functions to implement computing virtualization, network virtualization, and storage virtualization of the virtual machine, and is responsible for managing the virtual machine. Wherein a virtual machine (virtual machine) refers to a complete computer system that runs in a completely isolated environment with complete hardware system functionality through software emulation.

In the embodiment of the application, the user of the cloud platform refers to a cloud platform user who needs to purchase cloud services from the cloud platform. Each user may be identified by a name, number, cell phone number to which the account is bound, or mailbox to which the account is bound, on the cloud platform. Cloud service deployers refer to cloud platform users that are able to deploy cloud services at a cloud platform. The actual identities of the user and cloud service deployer may be individuals, or may be businesses or other organizations. The user and the cloud service deployer can be distinguished through the types of account numbers of the cloud platform user on the cloud platform.

In some examples, the cloud platform may also have an account number that can implement both a user's function and a cloud service deployer's function, where the account number may be used as a user in the embodiments of the present application when switching to the user mode, and may be used as a cloud service deployer in the embodiments of the present application when switching to the cloud service deployer mode.

The cloud service deployer and the user of the cloud platform can log in the cloud platform through the client, and create, manage, log in and operate the virtual machine in the cloud data center through the cloud platform.

By way of example, the client may be a mobile phone (mobile phone), a tablet (pad), a computer with wireless transceiving functionality, a Virtual Reality (VR) terminal, an augmented reality (augmented reality, AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned driving (self driving), a wireless terminal in telemedicine (remote media), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation security (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), a wireless terminal in internet of things (internet of things, ioT), or the like.

In some examples, the cloud architecture of the cloud data center may be an infrastructure as a service (infrastructure as a service, iaaS) based service architecture. In this way, the cloud data center may provide internet technology (Internet technology, IT) infrastructure as a service to users over a network. The cloud resources such as the physical server, the virtual machine, the machine room infrastructure and the network can be managed by the cloud platform. In this service model, users do not build a cloud data center themselves, but use infrastructure services including servers, storage resources, networks, and the like, by renting.

In the embodiment of the application, cloud service deployers can acquire cloud resources such as servers, virtual machines, storage resources, networks and the like from a cloud platform, and develop and manage the cloud resources based on the acquired cloud resources. For example, a cloud service deployer may install an operating system on cloud resources, develop a database, perform data processing, and develop application software, thereby obtaining a cloud service. The cloud service deployer may then sell the cloud service to the user through the cloud platform. In this way, cloud service deployers can exploit the infrastructure provided by the cloud data center to provide platform-as-a-service (platform as a service, paaS) level services to users who can purchase the desired cloud services without knowing the specific development details.

In one application scenario, the cloud service developed by the cloud service deployer may be a cloud service developed by the cloud service deployer based on a development idea of the cloud service deployer itself. At this time, the cloud service deployer may sell cloud services of the same function to a plurality of users through the cloud platform.

In another application scenario, the cloud service deployer may develop based on the customized configuration requirement information submitted by the user to provide the personalized cloud service for the user.

Therefore, through the cloud platform, operations such as display, transaction, management, operation and maintenance of the cloud service can be realized, and user management, cloud service deployment management, transaction arbitration and the like can be realized.

The cloud service deployment method based on public cloud provided by the embodiment of the application is described below with reference to the accompanying drawings.

As shown in fig. 2, an embodiment of a public cloud-based cloud service deployment method provided by the embodiments of the present application may be applied to the cloud platform, where the method includes:

step 201: a registration interface is provided.

The registration interface is used for respectively acquiring registration information of a plurality of cloud service deployers, and each registration information comprises an account number of the corresponding cloud service deployer on the cloud platform, cloud service deployment skills and service prices.

The registration interface may be in the form of an application program interface (application programming interface, API) or a configuration interface, etc. And the cloud service deployer uploads the registration information from the client to the cloud platform through the API or the configuration interface.

The registration information may include an account number of the corresponding cloud service deployer on the cloud platform, cloud service deployment skills, and service prices.

Wherein cloud service deployment skills may be described in the form of one or more skill tags. The cloud service deployment skills and service prices can be changed according to information such as transactions completed by cloud service deployers through the cloud platform. For example, cloud service deployment skills may include skills submitted by a cloud service deployer at registration, skills submitted by a cloud service deployer in the process of using an account, and skills automatically generated by a cloud platform based on transactions of cloud services completed by the cloud service deployer through the cloud platform. The service price can also be determined according to information such as registration time of cloud service deployers, historical cloud service conditions completed through a cloud platform and the like.

In addition, in some examples, the registration information may further include information such as identity authentication information, regional information, account scores, and deployer ratings of the cloud service deployer. The deployer level can be determined by one or more of information of the number, efficiency and user evaluation of deployment tasks completed in the cloud platform by the cloud service deployer. The particular form of the deployer-level is not limited herein. Illustratively, the deployer grade may include primary, medium, and advanced, or may also include bronze grade, silver grade, gold grade, platinum grade, and diamond grade. In the cloud platform, the functions provided for different deployer grades may also be different, for example, the upper limits of quotations of cloud services completed by cloud service deployers of different deployer grades on the cloud platform may be different, and the higher the deployer grade, the higher the upper limit of quotations of corresponding cloud services. Furthermore, different deployer tiers may differ in the maximum number of cloud service deployment skills that may be selected in the cloud platform. The account score of the cloud service deployer can be determined based on at least one of registration time of the cloud service deployer, the number of completed historical deployment tasks, evaluation of the cloud service deployer by a user corresponding to the historical deployment tasks, and the like.

Step 202: registration information of a plurality of cloud service deployers is recorded.

The registration information can be stored in a memory or a memory of the cloud platform, and also can be stored in a storage device externally connected with the cloud platform. The manner in which registration information of cloud service deployers is recorded is not limited herein. In some examples, registration information of each cloud service deployer may be recorded in a database corresponding to the cloud platform in the form of a cloud service deployer list or the like.

Step 203: a demand acquisition interface is provided.

The demand acquisition interface is used for acquiring cloud service configuration demands of the user, wherein the cloud service configuration demands comprise types of target cloud services which the user needs to configure on a cloud platform and prices which the user can pay.

The demand acquisition interface may be in the form of an application program interface (application programming interface, API) or a configuration interface, etc. And uploading cloud service configuration requirements from the client to the cloud platform by a user through an API or a configuration interface.

The specific form of cloud service configuration requirements is not limited herein. The cloud service configuration requirements may be described by at least one of text information, voice information, image information, video information, and links, for example.

In one example, the requirement acquisition interface is a designated requirement configuration interface, and when a user accesses the requirement configuration interface through a client, cloud service configuration requirements are input in the requirement configuration interface and submitted to a cloud platform by clicking an option button on the requirement configuration interface, inputting characters or files in a designated input box, and the like, wherein the files can be text files, voice files, images and/or videos. In addition, the requirement configuration interface can limit the number of characters input by the user and the size of the file.

The user may be identified by at least one of a name, a number of an account registered on the cloud platform, an international mobile equipment identity (international mobile equipment identity, IMEI) of the user-bound device, a user-bound cell phone number, and the like.

For example, the account number of the user on the cloud platform may also have a corresponding user level, user score, and user evaluation.

The cloud platform records information such as user level, technical field of interest, historical transaction, highest payable price and the like of the user. The field of interest may include, among other things, one or more technical field tags. In addition, the cloud platform can obtain user points according to the user grade, the highest payable price, historical transactions and other information.

The specific form of the user level may be the same as or different from the deployer level. The functionality provided by the cloud platform for different user classes may also be different, e.g., different user classes may obtain different trade discounts in electronic transactions, and different user classes may have different maximum payable prices.

The type of target cloud service may take many forms, and is not limited herein. By way of example, the types of target cloud services may include at least one of the following types. Website construction, data services, cloud services, software deployment, and design services. Further, in some examples, the types of target cloud services may also include multiple levels of types of progressive refinement. For example, a first hierarchical type "website building" may include multiple second hierarchical sub-types such as e-commerce websites, applets, and the like. While the first level of type "design services" may specifically include a plurality of second level sub-types such as user interface designs, product designs, and the like.

Step 204: determining a target cloud service deployer matching the cloud service configuration requirements from the registration information, and providing the transaction order to the target cloud service deployer.

In the embodiment of the application, there may be one or at least two target cloud service deployers. If the number of target cloud service deployers is at least two, each target cloud service deployer may be used to complete different parts in the development work of the target cloud service, or may also be used to be responsible for the same part in the development work of the target cloud service.

There may be a variety of ways to determine a target cloud service deployer from the registration information that matches the cloud service configuration requirements. For example, the target cloud service may be respectively matched with each cloud service deployer according to the cloud service deployment skill and the deployer level of each cloud service deployer, and the type of the target cloud service and the price payable by the user, and then the target cloud service deployer corresponding to the target cloud service is determined based on the matching result of each cloud service deployer and the target cloud service (for example, the cloud service deployer with the highest matching degree with the target cloud service may be used as the corresponding target cloud service deployer, or the deployer with the highest matching degree higher than the preset degree may be used as the target cloud service deployer). Or, a leader account number may be determined for the cloud service configuration requirement, and then the target cloud service deployer corresponding to the cloud service configuration requirement is determined by the leader account number. The leader account can be used as a target cloud service deployment person corresponding to the cloud service configuration requirement.

The trade order indicates that an electronic trade contract is made between the user and the target cloud service deployer with respect to the target cloud service. Generally, based on the trade order, the target cloud service deployer needs to deliver the corresponding target cloud service to the user, who needs to pay the corresponding trade amount to the corresponding target cloud service deployer. It will be appreciated that the trade order is in an unfinished state until the target cloud service deployer and the user have not delivered the corresponding targets and determined in the cloud platform that delivery has been completed.

In the embodiment of the application, the transaction order can be provided to the user and the target cloud service deployer through the cloud platform, so that the corresponding user and the cloud service deployer can view the corresponding transaction order through the designated interface in the corresponding client.

In the embodiment of the application, the cloud platform can provide a registration interface and record registration information of a plurality of cloud service deployers obtained through the registration interface. Thus, each individual and organization having cloud service deployment skills can register the cloud platform through the registration interface and become a cloud service deployment person on the cloud platform. In addition, the cloud platform can also provide a requirement acquisition interface to acquire cloud service configuration requirements of the user through the requirement acquisition interface. After obtaining the cloud service configuration requirements of the user, a target cloud service deployer matched with the cloud service configuration requirements can be determined according to the registration information, and a transaction order is provided for the target cloud service deployer. In this way, the cloud platform can utilize cloud service deployer resources on the cloud platform to match a proper target cloud service deployer for the user, and establish a service relationship between the target cloud service deployer and the user through the transaction order, so that the target cloud service deployer can help the user to deploy and obtain the desired cloud service.

Optionally, the method further comprises:

providing a cloud service deployment interface, and enabling a target cloud service deployment person to deploy target cloud service on a cloud platform through the cloud service deployment interface;

and sending the product information of the target cloud service which is successfully deployed to the user, wherein the product information is used for indicating the user to use the target cloud service on the cloud platform.

The cloud service deployment interface may be in the form of a designated interface or application program interface (application programming interface, API), or the like. The types of the target cloud service may be various, and the target cloud service may be a software product based on cloud resources, a database product, a data processing service, or the like. For example, the product information of the successfully deployed target cloud service may be information of a successfully deployed cloud resource-based virtual machine or container.

Illustratively, the target cloud service deployer may access cloud resources such as virtual machines and/or containers to be deployed through a cloud service deployment interface, so as to deploy corresponding target cloud services in the accessed virtual machines and/or containers, for example, develop software in the accessed virtual machines and/or containers, perform database management and/or perform other data processing operations, so as to obtain deployed virtual machines and/or containers, where the deployed virtual machines and/or containers may serve as products of successfully deployed target cloud services, and product information of successfully deployed target cloud services may include information of the deployed virtual machines and/or containers.

The specific configuration of the virtual machine and/or the container to be deployed may be determined by the cloud platform based on cloud service configuration requirements, or may be determined by a target cloud service deployer or a user.

In one example, the cloud service configuration requirements include at least one of bandwidth, expected usage time of virtual machine resources required by the target cloud service, size of storage space, core number of a central processing unit (central processing unit, CPU), size of memory, and/or expected usage time of container resources required by the service, size of storage space, core number of a central processing unit (central processing unit, CPU), size of memory, and network flow rate of the virtual machine resources to be deployed, so that the cloud platform can determine cloud resources such as virtual machines and/or containers for the target cloud service. In this way, the target cloud service deployer can access cloud resources such as virtual machines and/or containers to be deployed through the cloud service deployment interface to perform deployment.

In another example, as shown in fig. 3, taking a virtual machine resource as an example, a server may determine 3 levels of to-be-selected virtual machine resources (primary virtual machine resources, intermediate virtual machine resources, and advanced virtual machine resources respectively) according to cloud service configuration requirements, where at least one of storage space size, memory size, and bandwidth of the to-be-selected virtual machine resources of different levels may be different, and corresponding prices may also be different. The user can view the information of the 3 levels of virtual machine resources to be selected sent by the cloud platform through the interface 1 of the client, then can select from the 3 virtual machine resources to be selected according to the budget and the service requirement, and the cloud platform can determine the virtual machine resources corresponding to the target cloud service according to the corresponding selection result (namely, the target selection key corresponding to the primary virtual machine resources selected by the user in the interface 2). After determining the virtual machine resource corresponding to the target cloud service, a cloud service deployment interface capable of accessing the virtual machine resource can be provided for the target cloud service deployer.

The product information of the successfully deployed target cloud service may include an access interface of the successfully deployed virtual machine and/or container, and at least one of host domain name, internet protocol (Internet Protocol, IP) address, storage space size, core number of the CPU, size and bandwidth of the memory, effective duration, etc. of the successfully deployed virtual machine and/or container.

Exemplary, as shown in fig. 4, an information interaction diagram related to the deployment and processing of virtual machine resources in the embodiment of the present application is shown. After receiving a cloud service configuration requirement sent by a user, the cloud platform can determine virtual machine resources required by a corresponding target cloud service according to the cloud service configuration requirement, and further can provide a cloud service deployment interface for a target cloud service deployment person, so that the corresponding target cloud service deployment person can access a virtual machine to be deployed through the cloud service deployment interface. The target cloud service deployer can develop the virtual machine to be deployed to obtain the virtual machine with the value-added function, and the virtual machine with the value-added function can realize the related functions of the target cloud service required by the user. The information of the virtual machine with the value-added function can be used as product information of the target cloud service which is successfully deployed to be fed back to the cloud platform, and then the cloud platform feeds back the product information to the user.

In the embodiment of the application, the target cloud service can be deployed on the cloud platform through the cloud service deployment interface by the target cloud service deployer. Because the target cloud service deployer usually has rich expertise in developing cloud resources. In addition, the successfully deployed target cloud service product is obtained by deploying cloud resources such as virtual machines and/or containers based on a cloud platform, so that the cloud platform can flexibly allocate various resources such as the resources of a deployer and the cloud resources, not only can the deployer resources be effectively utilized, but also the managed cloud resources can be effectively utilized based on the requirements of users.

Optionally, as shown in fig. 5, step 204 described above: determining a target cloud service deployer matching the cloud service configuration requirements from the registration information, providing a trade order to the target cloud service deployer, comprising:

step 501, determining at least two deployment tasks corresponding to cloud service configuration requirements.

Step 502, determining a target cloud service deployer corresponding to each deployment task from a plurality of cloud service deployers.

Step 503, providing each target cloud service deployer with a trade order obtained according to the corresponding deployment task.

The above steps 501-503 are described in detail below.

In the embodiment of the present application, there may be multiple ways of determining at least two deployment tasks corresponding to cloud service configuration requirements.

In one example, keywords may be extracted from a cloud service configuration requirement, and then a preset task corresponding to each keyword corresponding to the cloud service configuration requirement is searched from a keyword library. The keyword library may include a plurality of preset keywords and a corresponding relationship between each preset keyword and a preset task, where the plurality of preset keywords may generally include keywords corresponding to cloud service configuration requirements. Then, according to the searched preset task corresponding to each keyword corresponding to the cloud service configuration requirement, a deployment task corresponding to the cloud service configuration requirement can be obtained. For example, a preset task corresponding to each keyword may be used as a deployment task; or, after the preset tasks corresponding to the keywords are classified, combined and the like, a deployment task is obtained, for example, a plurality of design tasks are included in the preset tasks corresponding to the keywords, and then the design tasks can be combined to obtain a deployment task, and the content of the deployment task includes the content of the design tasks.

In another example, a preset cloud service list may be generated in advance, where a plurality of preset cloud services and preset tasks corresponding to each preset cloud service may be recorded in the preset cloud service list. After the type of the target cloud service required by the user in the cloud service configuration requirement is obtained, if the type of the target cloud service is matched with a certain preset cloud service in a preset cloud service list, a preset task corresponding to the matched preset cloud service can be used as a deployment task corresponding to the cloud service configuration requirement.

The method for determining the target cloud service deployer corresponding to each deployment task from the cloud service deployers can be various. For example, according to the cloud service deployment skill and the level of the deployer of each cloud service, and the task description information (such as the task keywords and the task level) of the deployment task, the deployment task is respectively matched with each cloud service deployer, and then the target cloud service deployer corresponding to the deployment task is determined based on the matching result of each cloud service deployer and the deployment task (for example, the cloud service deployer with the highest matching degree with the deployment task can be used as the corresponding target cloud service deployer, or the cloud service deployer with the highest matching degree higher than the preset degree can be used as the target cloud service deployer). Or, a leader account is determined for the service corresponding to the cloud service configuration requirement, and then each deployment task corresponding to the service and the target cloud service deployer corresponding to each deployment task are determined by the leader account. The leader account can be used as a target cloud service deployer corresponding to at least one deployment task corresponding to the service.

Multiple target cloud service deployers corresponding to one cloud service configuration requirement can form a deployer team, so that the target cloud service corresponding to the cloud service configuration requirement can be completed through the deployer team. Wherein the deployer levels of the plurality of target cloud service deployers may be the same, or a gap between the deployer levels of the plurality of target cloud service deployers does not exceed a specified level difference, e.g., the gap does not exceed 2 levels.

In the embodiment of the present application, the specific form of the trade order is not limited herein. In one example, a trade order may be generated for each target cloud service deployer separately from the user, where the trade orders for each target cloud service deployer are independent of each other. In yet another example, the trade order may include a trade total order and a trade sub-order. The trade total order may include trade information, such as a trade total amount, for the user and all corresponding target cloud service deployers regarding the target cloud service. Each trade sub-order corresponds to each target cloud service deployer one by one, and each trade sub-order can comprise trade information of a user and the corresponding target cloud service deployer, such as trade amount of the user and the corresponding target cloud service deployer and information of deployment tasks corresponding to the corresponding target cloud service deployer.

In some examples, the generated trade orders may include trade amounts between the user and respective target cloud service deployers, respectively. The transaction amount may be determined in accordance with at least one of the following ways.

1. The transaction amount may be generated from a price payable by the user in the cloud service configuration requirements. For example, the transaction amount corresponding to each target cloud service deployer is equal to the value of the price payable by the user divided by the number of target cloud service deployers in the cloud service configuration requirements.

2. The transaction amount corresponding to each target cloud service deployment person can be determined according to the preset amount corresponding to the corresponding deployment task, and the preset amount can be preset in the cloud platform. For the same deployment task, the preset amounts corresponding to different task levels may be different. For example, for a web page design task, the electronic transaction program may determine that the preset amount corresponding to the primary level is 1000 yuan, and the preset amount corresponding to the intermediate level is 2000 yuan.

3. The transaction amount may be determined by negotiations between the respective target cloud service deployer and the user. For example, before generating the transaction order, a communication group may be established through a designated interface or application, where each target cloud service deployment person and user may be included in the communication group, each target cloud service deployment person and user may communicate information about the relevant deployment task in the communication group, where the information about the transaction amount is included, after the communication is completed, the user or a certain target cloud service deployment person may submit the information about the transaction amount to a cloud platform, and after the cloud platform obtains the information about the transaction amount, the cloud platform may generate the transaction order according to the transaction amount information.

The transaction amounts corresponding to the target cloud service deployers can be the same or different.

The trade orders may be sent to the user and the target cloud service deployer through the cloud platform, so that the respective user and the target cloud service deployer can view the respective trade orders through a designated interface in the respective client.

At present, because the deployment difficulty and workload of various cloud services are generally large, only service providers such as software vendors with a certain scale can provide complete cloud services for users, and individual deployers or small service providers have difficulty in acquiring orders of clients and are difficult to be effectively utilized to deploy and develop cloud services for the clients.

In the embodiment of the application, different target cloud service deployers can complete different deployment tasks, so that target cloud services required by users can be split into different development contents, and then different deployment tasks can be distributed to different target cloud service deployers, so that a plurality of deployer resources can be called to cooperatively complete target cloud services required by the users, a plurality of deployers can be flexibly organized to complete different deployment parts in one service requirement of the users, various deployer resources are effectively utilized, and requirements on team scale and deployment capacity of the cloud service deployers are greatly reduced.

Optionally, the steps above: determining at least two deployment tasks corresponding to cloud service configuration requirements, comprising:

determining a target preset cloud service from a plurality of preset cloud services according to cloud service configuration requirements;

acquiring a configuration grade corresponding to cloud service configuration requirements;

and determining at least two deployment tasks corresponding to cloud service configuration requirements according to the preset tasks corresponding to the target preset cloud service at the configuration level.

According to cloud service configuration requirements, a plurality of ways of determining the target preset cloud service in the plurality of preset cloud services can be provided. In one example, a preset cloud service list may be generated in advance, where a plurality of preset cloud services and preset keywords corresponding to each preset cloud service may be recorded in the preset cloud service list. The cloud platform can match keywords in the cloud service configuration requirements with preset keywords of each preset cloud service, and takes the preset cloud service with the highest keyword matching degree as a target preset cloud service corresponding to the cloud service configuration requirements. In another example, the target cloud service selected by the user may be used as the target preset cloud service corresponding to the cloud service configuration requirement.

The configuration level corresponding to the cloud service configuration requirement can be contained in the cloud service configuration requirement, or the cloud platform can be determined according to the cloud service configuration requirement. For example, it may be determined based on budget information and/or keywords in cloud service configuration requirements. In one example, the configuration level may be determined based on keywords such as large, medium, or small in cloud service configuration requirements.

In an example, the preset cloud service list may record not only preset keywords corresponding to each preset cloud service of the plurality of preset cloud services, but also preset tasks corresponding to each preset cloud service at different configuration levels. After determining the configuration level corresponding to the cloud service configuration requirement and the target preset cloud service, searching a preset task corresponding to the configuration level of the target preset cloud service in a preset cloud service list, so as to determine at least two deployment tasks corresponding to the cloud service configuration requirement according to the preset task corresponding to the configuration level of the target preset cloud service.

In an exemplary scenario, in the preset cloud service list, one preset cloud service stored in advance is a website deployment service, and the configuration level of the preset cloud service may include three levels of simplicity, generality and complexity.

The preset tasks corresponding to the simple-level website deployment service are as follows: a webpage design task and a code deployment task;

the preset tasks corresponding to the common-level website deployment service are as follows: a webpage design task, a code deployment task and a content editing task;

the preset tasks corresponding to the complex-level website deployment service are as follows: a web page design task, a code deployment task, a content editing task and a network security maintenance task.

In practical application, if the target cloud service selected by the user on the designated interface of the cloud platform is the website deployment service, and the selected configuration level is the simple level, the cloud platform can search in a preset cloud service list according to the website deployment service and the simple level included in the cloud service configuration requirement, find that the matched preset task is the website deployment service, and the preset task corresponding to the website deployment service of the simple level is recorded in the preset cloud service list as follows: a web page design task and a code deployment task. Therefore, it can be determined that the target cloud service required by the user can be split into two deployment tasks, which are respectively: a web page design task and a code deployment task.

If the service class selected by the user on the designated interface of the cloud platform is the website deployment service, and the selected configuration level is the complexity level, then the target cloud service required by the user can be determined to be divided into four deployment tasks by presetting a cloud service list, which are respectively: a web page design task, a code deployment task, a content editing task and a network security maintenance task.

According to the method and the device, services can be split more accurately through information of at least two dimensions such as the type of cloud service, the configuration level and the like, and according to preset cloud services and preset tasks corresponding to each preset cloud service in different configuration levels, each deployment task meeting the division conditions in the deployment process can be obtained.

Optionally, the steps above: determining a target cloud service deployer corresponding to each deployment task from a plurality of cloud service deployers, including:

according to the task information of each deployment task and the registration information of each cloud service deployer, determining cloud service deployers respectively matched with each deployment task, wherein the task information comprises task prices and/or task categories;

and determining a target cloud service deployer corresponding to each deployment task from cloud service deployers matched with each deployment task.

In the embodiment of the application, the cloud platform can determine at least one cloud service deployer matched with each deployment task according to the task information of each deployment task. The task information includes a task price and/or a task category, and further, the task information may further include task description information for describing deployment contents of the respective deployment tasks. The task description information can comprise information extracted from cloud service configuration requirements, can also comprise other information submitted by a user except the cloud service configuration requirements, and can also comprise preset description information which is stored in a cloud platform in advance and aims at the deployment task.

According to the cloud service deployment method and device, cloud service deployers matched with each deployment task can be respectively determined according to cloud service deployment skills and service prices of the cloud service deployers and task information such as task prices and/or task categories of each deployment task.

In some examples, determining that the deployment task matches a condition of a cloud service deployer may include at least one of:

1. the task category of the deployment task is matched with cloud service deployment skills of the cloud service deployer.

The task category of the deployment task and the cloud service deployment skill of the cloud service deployer are matched, and the task category of the deployment task is found in the cloud service deployment skill of the cloud service deployer. Alternatively, the task category of the deployment task and a cloud service deployment skill of the cloud service deployer may be close terms (e.g., web page deployment and website deployment).

2. The task price of the deployment task matches the service price of the cloud service deployer.

For example, the task price of the deployment task is no greater than the service price of the cloud service deployer.

After obtaining at least one cloud service deployer matched with the deployment task, determining that the cloud service deployer with the highest matching degree is the target cloud service deployer corresponding to the deployment task from the at least one cloud service deployer matched with the deployment task, and determining the target cloud service deployer corresponding to the deployment task from the at least one cloud service deployer matched with the cloud service deployer based on conditions such as a good score of the cloud service deployer, probability of accepting the deployment task and the like. In addition, order request information can be sent to at least one cloud service deployment person which is matched, and then the cloud service deployment person which confirms the order request information is used as a target cloud service deployment person corresponding to the deployment task.

Optionally, determining the target cloud service deployer corresponding to each deployment task from cloud service deployers matched with each deployment task includes:

sending order request information to at least one cloud service deployer matched with the deployment task, wherein the order request information is used for requesting to generate a transaction order of the corresponding cloud service deployer about the deployment task;

and taking the cloud service deployer corresponding to the received first confirmation information of the first order request information as a target cloud service deployer of the corresponding deployment task.

For example, the target cloud service deployer using the cloud service deployer corresponding to the received first confirmation information for the order request information as the corresponding deployment task may be: and taking the cloud service deployer corresponding to the first confirmation information of the received first order request information as the target cloud service deployer corresponding to the corresponding deployment task within a preset time period from the moment of sending the order request information.

In an example, the order request information may be sequentially sent to the corresponding cloud service deployers according to the order of the matching rate corresponding to at least one cloud service deployer matched with the deployment task from high to low, until first confirmation information of the cloud service deployer receiving the order request information is obtained, and the cloud service deployer corresponding to the received first confirmation information is used as the target cloud service deployer corresponding to the corresponding deployment task.

Or in another example, the order request information may also be randomly sent to a plurality of cloud service deployers matched with the deployment task, until first confirmation information of the cloud service deployer receiving the order request information is obtained, and the cloud service deployer corresponding to the received first confirmation information is used as a target cloud service deployer corresponding to the corresponding deployment task.

Alternatively, in yet another example, the order request information may also be sent randomly to one cloud service deployer matched with the deployment task, and if the first confirmation information for the order request information is received within a specified period of time (for example, 5 minutes), the cloud service deployer corresponding to the first confirmation information may be used as the target cloud service deployer corresponding to the corresponding deployment task. If the first confirmation information for the order request information is not received within the appointed time period, excluding the cloud service deployer, and then sending the order request information by one cloud service deployer selected randomly from the cloud service deployers matched with the deployment task.

In this way, through the embodiment of the application, the corresponding target cloud service deployer can be determined for each deployment task more quickly.

Optionally, determining at least two deployment tasks corresponding to cloud service configuration requirements includes:

determining a first cloud service deployment person according to cloud service configuration requirements;

receiving second confirmation information sent by the first cloud service deployer, wherein the second confirmation information comprises information of at least two deployment tasks;

determining a target cloud service deployer corresponding to each deployment task from a plurality of cloud service deployers, including:

receiving third confirmation information sent by the first cloud service deployer, wherein the third confirmation information comprises information of target cloud service deployers corresponding to each deployment task, the target cloud service deployers comprise the first cloud service deployers, and the operation authority of the first cloud service deployers for cloud service configuration requirements is higher than that of other cloud service deployers except the first cloud service deployers in the target cloud service deployers;

providing each target cloud service deployer with a trade order obtained according to a respective deployment task, comprising:

and generating a corresponding trade order of each target cloud service deployment according to the second confirmation information and the third confirmation information, and providing the corresponding trade order for each target cloud service deployment.

In this embodiment of the present application, the first cloud service deployer may be considered as a leader among the plurality of target cloud service deployers, after obtaining the cloud service configuration requirement, the first cloud service deployer corresponding to the cloud service configuration requirement may be determined first, each corresponding deployment task is determined by the first cloud service deployer according to the cloud service configuration requirement, and the target cloud service deployer corresponding to each deployment task is determined. It can be seen that in the embodiment of the present application, each target cloud service deployer may form a temporary deployer team to cooperatively complete the target cloud service required by the user.

In the embodiment of the present invention, the operation authority of the first cloud service deployer for the cloud service configuration requirement may be set higher than that of other cloud service deployers except the first cloud service deployer in the target cloud service deployer, so that the first cloud service deployer can execute some online organization operations about each target cloud service deployer through the cloud platform in the deployment process. For example, in some examples, a first cloud service deployer may establish a communication group based on the cloud platform during deployment based on the trade order, where each target cloud service deployer and user may be included in the communication group, such that each target cloud service deployer and user may communicate with each deployment task in the communication group.

In addition, the target cloud service deployer and/or the user can also create a communication record file such as a form or a text in the communication group, and record deployment information of each deployment task, transaction amount of the transaction order and other information in the communication record file. The deployment information may include: the deployment progress of each deployment task in each deployment stage and the communication result aiming at a certain object in the deployment task. The communication record file can be stored in the cloud platform and/or the client and can be used as a certificate for generating a transaction order.

In this embodiment of the present application, there may be multiple ways to determine the first cloud service deployer according to the cloud service configuration requirement.

In one example, a keyword may be extracted from cloud service configuration requirements, and then the keyword may be matched with cloud service deployment skills of each cloud service deployer to obtain a first matching degree of each cloud service deployer for the cloud service configuration requirements. After obtaining the first degree of matching, a first cloud service deployer may be determined from the plurality of cloud service deployers according to the respective first degree of matching. For example, the cloud service deployer with the highest first matching degree may be used as the first cloud service deployer. Or, the cloud service deployer with the highest account number level can be determined to be the first cloud service deployer from a plurality of cloud service deployers with the first matching degree higher than the specified matching threshold.

In addition, a leader tag can be set for some cloud service deployers in advance according to personal setting information of the cloud service deployers and/or the completion condition of historical deployment tasks, and the leader tag indicates that the cloud service deployers can be set as first cloud service deployers. After obtaining the first degree of matching, a certain cloud service deployer including the leader tag may be determined as the first cloud service deployer from among the plurality of cloud service deployers whose first degree of matching is higher than the specified matching threshold.

In this embodiment of the present invention, before the first cloud service deployer sends the third acknowledgement information, the cloud platform may further send cloud service deployer recommendation information to the first cloud service deployer, where the cloud service deployer recommendation information may include information of a plurality of cloud service deployers to be selected. These candidate cloud service deployers may include at least one of the following: the method comprises the steps of enabling account friends of a first cloud service deployment person, historical team members of the first cloud service deployment person, cloud service deployment persons marked in advance by the first cloud service deployment person and cloud platforms to find out the best matched cloud service deployment person aiming at each deployment task. The historical team member refers to a cloud service deployer corresponding to different deployment tasks of the same historical service with the first cloud service deployer in the historical electronic transaction.

The cloud service deployer recommendation information is sent to the first cloud service deployer through the cloud platform, so that the first cloud service deployer can be helped to build a deployer team which is more matched with the cloud service configuration requirements and is more convenient to develop cooperation.

Therefore, according to the embodiment of the application, a temporary deployer team can be constructed through the first cloud service deployer to cooperatively complete the target cloud service required by the user, so that individuals with cloud service deployment skills can be flexibly combined according to actual requirements to complete the cloud service required by the user.

In the above, the embodiments of the present application introduce a cloud service deployment method based on public cloud from multiple aspects, and in the following, a cloud service deployment device based on public cloud of the present application is described with reference to the accompanying drawings.

As shown in fig. 6, an embodiment of the present application provides a cloud service deployment device 60 based on public cloud, where the cloud service deployment device 60 based on public cloud may be a cloud platform in the foregoing embodiment, or may be a part of hardware modules and/or software modules in the cloud platform in the foregoing embodiment.

An embodiment of the public cloud-based cloud service deployment apparatus 60 includes a first interface module 601, a recording module 602, a second interface module 603, and a processing module 604.

The first interface module 601 is configured to provide a registration interface, where the registration interface is configured to obtain registration information of multiple cloud service deployers, where each registration information includes an account number of the corresponding cloud service deployer on the cloud platform, a cloud service deployment skill, and a service price;

a recording module 602, configured to record registration information of a plurality of cloud service deployers;

a second interface module 603, configured to provide a requirement acquisition interface, where the requirement acquisition interface is configured to acquire a cloud service configuration requirement of a user, and the cloud service configuration requirement includes a type of a target cloud service that the user needs to configure on a cloud platform and a price payable by the user;

A processing module 604, configured to determine, from the registration information, a target cloud service deployer that matches the cloud service configuration requirement, and provide the transaction order to the target cloud service deployer.

Optionally, the public cloud-based cloud service deployment apparatus 60 further includes a third interface module 605;

the third interface module 605 is configured to provide a cloud service deployment interface, through which a target cloud service deployer deploys a target cloud service on the cloud platform;

the processing module 604 is further configured to send product information of the target cloud service that is successfully deployed to the user, where the product information is used to instruct the user to use the target cloud service on the cloud platform.

Optionally, the processing module 604 is configured to:

determining at least two deployment tasks corresponding to cloud service configuration requirements;

determining a target cloud service deployer corresponding to each deployment task from a plurality of cloud service deployers;

each target cloud service deployer is provided with a trade order obtained according to the respective deployment task.

Optionally, the processing module 604 is configured to:

according to the task information of each deployment task and the registration information of each cloud service deployer, determining cloud service deployers respectively matched with each deployment task, wherein the task information comprises task grades and/or task categories;

Optionally, the processing module 604 is configured to:

sending order request information to at least one cloud service deployer matched with the deployment task, wherein the order request information is used for requesting to generate a trade order of a user and the corresponding cloud service deployer about the deployment task;

Optionally, the processing module 604 is configured to:

And generating a trade order of each target cloud service deployment according to the second confirmation information and the third confirmation information, and providing a corresponding trade order for each target cloud service deployment.

Fig. 7 is a schematic diagram of a possible logic structure of a cloud platform 70 according to an embodiment of the present application. The cloud platform 70 includes: memory 701, processor 702, communication interface 703, and bus 704. The memory 701, the processor 702, and the communication interface 703 are connected to each other by a bus 704. The cloud platform 70 may be the cloud platform in the above-described embodiments.

The Memory 701 may be a Read Only Memory (ROM), a static storage device, a dynamic storage device, or a random access Memory (Random Access Memory, RAM). The memory 701 may store a program, and when the program stored in the memory 701 is executed by the processor 702, the processor 702 and the communication interface 703 are configured to perform steps 201 to 204 and steps 501 to 503 of the above-described public cloud-based cloud service deployment method embodiment.

The processor 702 may employ a central processing unit (Central Processing Unit, CPU), microprocessor, application specific integrated circuit (Application Specific Integrated Circuit, ASIC), graphics processor (graphics processing unit, GPU), digital signal processor (Digital Signal Processing, DSP), application Specific Integrated Circuit (ASIC), off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or any combination thereof, for executing related programs to implement the functions required to be performed by the first interface module, recording module, second interface module, and processing module in the public cloud-based cloud service deployment apparatus of the present embodiments, or to perform steps 201-204 and steps 501-503 of the public cloud-based cloud service deployment method embodiments of the present embodiments, and the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in the memory 701, and the processor 702 reads the information in the memory 701, and performs steps 201 to 204, 501 to 503, and so on of the public cloud-based cloud service deployment method embodiment in combination with the hardware thereof.

The communication interface 703 enables communication between the cloud platform 70 and other devices or communication networks using a transceiver device such as, but not limited to, a transceiver. For example, a registration interface, a demand acquisition interface, a cloud service deployment interface may be provided for the user through the communication interface 703, and a trade order, product information of a target cloud service that is successfully deployed, and the like may be sent to the user.

Bus 704 may implement a pathway for information among the various components of cloud platform 70 (e.g., memory 701, processor 702, and communication interface 703). Bus 704 may be a peripheral component interconnect standard (Peripheral Component Interconnect, PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 7, but not only one bus or one type of bus.

In another embodiment of the present application, there is also provided a computer readable storage medium having stored therein computer executable instructions that when executed by a processor perform the steps performed by the processor of fig. 7 described above.

In another embodiment of the present application, there is also provided a computer program product comprising computer-executable instructions stored in a computer-readable storage medium; the steps performed by the processor in fig. 7 described above are performed when the processor executes the computer-executable instructions.

In another embodiment of the present application, a chip system is provided, where the chip system includes a processor, where the processor is configured to support a computer device to implement steps 201 to 204, steps 501 to 503, and so on of the foregoing public cloud-based cloud service deployment method embodiment. In one possible design, the system on a chip may further include a memory, the memory storing program instructions and data necessary for the means for writing data. The chip system can be composed of chips, and can also comprise chips and other discrete devices.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the embodiments of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in the embodiments of the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of elements is merely a logical functional division, and there may be additional divisions of actual implementation, e.g., multiple elements or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be essentially or, what contributes to the prior art, or part of the technical solution may be embodied in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods of the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RandomAccess Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The above is merely a specific implementation of the embodiments of the present application, but the protection scope of the embodiments of the present application is not limited thereto.

Claims

1. A cloud service deployment method based on public cloud, wherein the method is applied to a cloud platform, the method comprising:

providing a registration interface, wherein the registration interface is used for respectively acquiring registration information of a plurality of cloud service deployers, and each registration information comprises an account number, cloud service deployment skills and service price of the corresponding cloud service deployer on the cloud platform;

recording registration information of the cloud service deployers;

providing a demand acquisition interface, wherein the demand acquisition interface is used for acquiring cloud service configuration demands of a user, and the cloud service configuration demands comprise types of target cloud services which are required to be configured by the user on the cloud platform and prices which can be paid by the user;

and determining a target cloud service deployment person matched with the cloud service configuration requirement from the registration information, and providing a transaction order for the target cloud service deployment person.

2. The method according to claim 1, wherein the method further comprises:

providing a cloud service deployment interface, wherein the target cloud service deployer deploys the target cloud service on the cloud platform through the cloud service deployment interface;

and sending product information of the target cloud service which is successfully deployed to the user, wherein the product information is used for indicating the user to use the target cloud service on the cloud platform.

3. The method of claim 1 or 2, wherein the determining, from the registration information, a target cloud service deployer that matches the cloud service configuration requirements, providing a trade order to the target cloud service deployer, comprises:

determining at least two deployment tasks corresponding to the cloud service configuration requirements;

determining a target cloud service deployer corresponding to each deployment task from the plurality of cloud service deployers;

providing each target cloud service deployer with the trade order obtained according to the corresponding deployment task.

4. The method of claim 3, wherein the determining at least two deployment tasks corresponding to the cloud service configuration requirements comprises:

determining a target preset cloud service from a plurality of preset cloud services according to the cloud service configuration requirements;

acquiring a configuration grade corresponding to the cloud service configuration requirement;

and determining at least two deployment tasks corresponding to the cloud service configuration requirements according to the preset tasks corresponding to the target preset cloud service at the configuration level.

5. The method of claim 3 or 4, wherein the determining, from the plurality of cloud service deployers, a target cloud service deployer corresponding to each deployment task includes:

According to the task information of each deployment task and the registration information of each cloud service deployment, determining cloud service deployers respectively matched with each deployment task, wherein the task information comprises task prices and/or task categories;

6. The method of claim 5, wherein the determining a target cloud service deployer corresponding to each deployment task from cloud service deployers matched to each deployment task comprises:

and taking the cloud service deployer corresponding to the received first confirmation information aiming at the order request information as a target cloud service deployer of the corresponding deployment task.

7. The method of claim 3, wherein the determining at least two deployment tasks corresponding to the cloud service configuration requirements comprises:

Determining a first cloud service deployment person according to the cloud service configuration requirement;

receiving second confirmation information sent by the first cloud service deployer, wherein the second confirmation information comprises information of the at least two deployment tasks;

the determining, from the plurality of cloud service deployers, a target cloud service deployer corresponding to each deployment task includes:

receiving third confirmation information sent by the first cloud service deployer, wherein the third confirmation information comprises information of target cloud service deployers corresponding to each deployment task, the target cloud service deployers comprise the first cloud service deployers, and the operation authority of the first cloud service deployers for the cloud service configuration requirements is higher than that of other cloud service deployers except the first cloud service deployers in the target cloud service deployers;

the providing the trade order obtained according to the corresponding deployment task to each target cloud service deployment person comprises the following steps:

and generating the corresponding trade orders of each target cloud service deployment person according to the second confirmation information and the third confirmation information, and providing the corresponding trade orders for each target cloud service deployment person.

8. A public cloud-based cloud service deployment apparatus, wherein the apparatus is applied to a cloud platform, the apparatus comprising:

the cloud service deployment system comprises a first interface module, a second interface module and a third interface module, wherein the first interface module is used for providing a registration interface, and the registration interface is used for respectively acquiring registration information of a plurality of cloud service deployers, and each registration information comprises an account number, cloud service deployment skills and service price of the corresponding cloud service deployer on the cloud platform;

the recording module is used for recording the registration information of the cloud service deployers;

the second interface module is used for providing a demand acquisition interface, wherein the demand acquisition interface is used for acquiring cloud service configuration demands of a user, and the cloud service configuration demands comprise types of target cloud services which are required to be configured on the cloud platform by the user and prices which can be paid by the user;

and the processing module is used for determining a target cloud service deployment person matched with the cloud service configuration requirement from the registration information and providing a transaction order for the target cloud service deployment person.

9. The apparatus of claim 8, further comprising a third interface module;

the third interface module is used for providing a cloud service deployment interface, and the target cloud service deployer deploys the target cloud service on the cloud platform through the cloud service deployment interface;

The processing module is further configured to send product information of the target cloud service that is successfully deployed to the user, where the product information is used to instruct the user to use the target cloud service on the cloud platform.

10. The device according to claim 8 or 9, wherein,

the processing module is used for:

11. The apparatus of claim 10, wherein the device comprises a plurality of sensors,

the processing module is used for:

12. The device according to claim 10 or 11, wherein,

The processing module is used for:

according to the task information of each deployment task and the registration information of each cloud service deployment, determining cloud service deployers respectively matched with each deployment task, wherein the task information comprises task grades and/or task categories;

13. The apparatus of claim 12, wherein the device comprises a plurality of sensors,

the processing module is used for:

sending order request information to at least one cloud service deployer matched with the deployment task, wherein the order request information is used for requesting to generate a transaction order of the user and the corresponding cloud service deployer about the deployment task;

14. The apparatus of claim 10, wherein the device comprises a plurality of sensors,

the processing module is used for:

and generating the trade orders of each target cloud service deployment person according to the second confirmation information and the third confirmation information, and providing the corresponding trade orders for each target cloud service deployment person.

15. A cloud platform comprising at least one processor, a memory, and instructions stored on the memory and executable by the at least one processor, the at least one processor executing the instructions to implement the steps of the method of any one of claims 1 to 7.

16. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method of any of claims 1 to 7.