CN116566813A

CN116566813A - Method and device for deploying proprietary cloud application, electronic equipment and storage medium

Info

Publication number: CN116566813A
Application number: CN202210114814.2A
Authority: CN
Inventors: 刘子哲
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2022-01-30
Filing date: 2022-01-30
Publication date: 2023-08-08

Abstract

The embodiment of the application provides a method, a device, electronic equipment and a storage medium for deploying proprietary cloud applications, wherein corresponding component task templates are configured based on at least one basic deployment operation aiming at specified component categories, so that when the proprietary cloud applications are deployed, corresponding application deployment information can be quickly generated according to corresponding component task templates of the specific proprietary cloud applications, and the deployment of the specific proprietary cloud applications is realized. Compared with the related art, the method only needs to acquire the component task templates corresponding to the application components respectively from the maintained component task template set, and can realize the deployment of the corresponding proprietary cloud application according to the basic deployment operation and the corresponding parameter information recorded by the component task templates respectively, so that the dependence on the development technical object in the related art is effectively reduced, the flexibility of the deployment of the proprietary cloud application is higher, and the corresponding deployment threshold and the deployment cost are greatly reduced.

Description

Method and device for deploying proprietary cloud application, electronic equipment and storage medium

Technical Field

The present invention relates to the field of cloud technologies, and in particular, to a method and apparatus for deploying a proprietary cloud application, an electronic device, and a storage medium.

Background

With the development of the internet, real-time data flow, and diversification of connected devices, and the pushing of demands for search services, social networks, mobile commerce, and open collaboration, cloud computing (closed computing) has been rapidly developed. Specifically, by deploying a cloud computing resource pool formed by multiple types of virtual resources (called a cloud platform for short, and is commonly called an infrastructure as a service (Infrastructure as a Service, iaaS) platform), a basic capability provider of cloud computing enables external related objects to acquire required resources at any time in a manner of using the external related objects as required and expanding at any time through an open connection network of the external related objects, so that the use efficiency of the resources is greatly improved.

Further, in an actual situation, when the basic capability provider of the cloud computing provides the cloud service for the target object, a proprietary deployment mode can be adopted to realize the floor deployment of the specified target cloud service.

Specifically, the basic capability provider often creates a corresponding proprietary cloud application according to the cloud service function customized by the target object; furthermore, in order to reduce the deployment cost of the proprietary cloud application, the basic capability provider often needs to provide a corresponding application deployment tool, so as to assist the related technical object to distribute the application code of the proprietary cloud application to the proprietary service device specified by the target object, so as to implement the deployment of the proprietary cloud application specified by the target object.

However, based on the above manner, the following drawbacks remain:

(1) In the related art, in order to implement rapid deployment of a proprietary cloud application, a basic capability provider is generally required, and a corresponding application deployment tool is designed and developed according to factors such as a system environment required by an application code of the basic capability provider, and this process needs to consume a great deal of labor cost and time cost, so that in an actual scene, the deployment cost of the proprietary cloud application is often high.

(2) In the related art, because different target objects often have different system deployment environments equipped on the proprietary service device, in an actual situation, the related technical objects often need to detect the equipped system deployment environments in the proprietary service device specified by the target objects to determine whether the current system deployment environment meets the actual deployment requirements of the customized proprietary cloud application, and because the environment detection process is often complex, in the related art, the deployment threshold of the proprietary cloud application is higher, so that portability of the proprietary cloud application is poor.

Disclosure of Invention

The embodiment of the application provides a proprietary cloud application deployment method, a device, electronic equipment and a storage medium, which are used for reducing the deployment cost of the proprietary cloud application and improving the portability of the proprietary cloud application.

In one aspect, an embodiment of the present application provides a method for deploying a proprietary cloud application, where the method includes:

acquiring resource information of a specified proprietary cloud application, wherein the proprietary cloud application comprises a plurality of application components, and each application component corresponds to at least one sub-function of the proprietary cloud application; the resource information includes at least: parameter information of each of the plurality of application components, and a corresponding component deployment order among the plurality of application components.

For a plurality of application components, the following operations are respectively executed: according to the component category of an application component, a corresponding target task template is determined from a preset component task template set, wherein at least one basic deployment operation determined for the component category is recorded in each component task template.

Based on the resource information, combining each target task template to generate corresponding application deployment information, wherein at least one basic deployment operation determined for the proprietary cloud application is recorded in the application deployment information.

And respectively executing the basic deployment operation recorded in the application deployment information to realize the deployment of the proprietary cloud application.

In one aspect, an embodiment of the present application provides a proprietary cloud application deployment apparatus, including:

The system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring resource information of a specified proprietary cloud application, the proprietary cloud application comprises a plurality of application components, and each application component corresponds to at least one sub-function of the proprietary cloud application; the resource information includes at least: parameter information of each of the plurality of application components, and a corresponding component deployment order among the plurality of application components.

The determining module is used for respectively executing the following operations for a plurality of application components: according to the component category of an application component, a corresponding target task template is determined from a preset component task template set, wherein at least one basic deployment operation determined for the component category is recorded in each component task template.

The combination module is used for combining the target task templates based on the resource information to generate corresponding application deployment information, wherein at least one basic deployment operation determined for the proprietary cloud application is recorded in the application deployment information.

And the execution module is used for respectively executing the basic deployment operation recorded in the application deployment information so as to realize the deployment of the proprietary cloud application.

Optionally, before acquiring the deployment resource information of the specific proprietary cloud application, the acquiring module is further configured to:

For each component class of the plurality of application components, the following operations are performed:

acquiring category description information determined for one component category, wherein the category description information at least records: the environment is deployed for a class determined for a component class.

Based on the category description information, at least one base deployment operation corresponding to the category deployment environment is determined from a preset base deployment operation set.

And combining at least one basic deployment operation based on a preset deployment rule to generate a corresponding component task template.

Optionally, when acquiring the resource information of the specific proprietary cloud application, the acquiring module is specifically configured to:

acquiring a deployment application tree determined for the proprietary cloud application, wherein the deployment application tree at least comprises: application versions of the proprietary cloud application, and parameter information of each of a plurality of application components contained in the proprietary cloud application.

Based on the application version of the proprietary cloud application, determining the component deployment sequence corresponding to the application version from a preset deployment sequence set.

And combining the component deployment sequence and the parameter information of each of the plurality of application components to obtain the resource information of the proprietary cloud application.

Optionally, each basic deployment operation carries corresponding operation description information, where the operation description information at least includes: the execution order of the corresponding base deployment operations; then, based on a preset deployment rule, at least one basic deployment operation is combined, and when a corresponding component task template is generated, the combination module is specifically configured to:

The at least one base deployment operation is ordered in a small-to-large order based on a respective order of execution of the at least one base deployment operation.

And combining at least one basic deployment action based on the sequencing result of at least one basic deployment operation to generate a corresponding component task template.

Optionally, based on the resource information, each target task template is combined, and when corresponding application deployment information is generated, the combination module is specifically configured to:

for the parameter information of each of the plurality of application components, the following operations are respectively executed: and combining the parameter information of one application component based on the target task template corresponding to the one application component to determine each basic deployment operation corresponding to the one application component.

Based on the component deployment sequence, sequencing the corresponding basic deployment operations of the application components, and generating corresponding application deployment information based on sequencing results.

Optionally, the operation description information further includes: the execution attribute of the corresponding base deployment operation; the deployment operations recorded in the application deployment information are respectively executed, so that when the deployment of the proprietary cloud application is realized, the execution module is specifically used for:

Based on the application deployment information, each execution order of each basic deployment operation sequentially determines each execution attribute of each basic deployment operation according to the arrangement order from small to large, wherein:

if the execution attribute of one basic deployment operation is: and can be skipped, the deployment attribute of the next basic deployment operation is read.

If the execution attribute of one basic deployment operation is: and if the deployment attribute is executable, executing one basic deployment operation and reading the deployment attribute of the next basic deployment operation.

Optionally, the execution module is further configured to:

if the execution attribute of one basic deployment operation is: and if the operation is overtime, executing the basic deployment operation within a preset overtime time range, and reading the deployment attribute of the next basic deployment operation.

In one aspect, an embodiment of the present application provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the steps of the above-described proprietary cloud application deployment method when executing the program.

In one aspect, embodiments of the present application provide a computer-readable storage medium storing a computer program executable by a computer device, which when run on the computer device, causes the computer device to perform the steps of the above-described proprietary cloud application deployment method.

In the embodiment of the application, the deployment of the proprietary cloud application is realized based on the corresponding component deployment sequence and at least one basic deployment operation contained in the target task templates determined by each application component. Compared with the related art, based on the cloud application deployment mode of the tooled, the method can realize the deployment of the corresponding proprietary cloud application according to the basic deployment operation and the corresponding parameter information recorded by each component task template by only respectively acquiring the component task templates corresponding to each application component from the maintained component task template set. According to the method for deploying the proprietary cloud application, which is disclosed by the embodiment of the application, the dependence on the development technical object in the related technology is reduced, so that the flexibility of deploying the proprietary cloud application is higher, and the corresponding deployment threshold and the deployment cost are greatly reduced.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:

Fig. 1 is a schematic view of an optional application scenario in an embodiment of the present application;

fig. 2 is a schematic diagram of a proprietary cloud application deployment platform in an embodiment of the present application;

FIG. 3 is a schematic diagram of one possible client interface in an embodiment of the present application;

fig. 4 is a flowchart of a method for deploying a proprietary cloud application in an embodiment of the present application;

FIG. 5 is a component task template diagram of a product component class in an embodiment of the present application;

FIG. 6 is a diagram of a below-list intent in a component task template in accordance with an embodiment of the present application;

FIG. 7 is a schematic diagram of special fields in a component task template according to an embodiment of the present application;

FIG. 8 is an interactive flow diagram of a proprietary cloud application deployment in an embodiment of the present application;

fig. 9 is a logic schematic diagram of a proprietary cloud application deployment scenario in an embodiment of the present application;

fig. 10 is a schematic structural diagram of a proprietary cloud application deployment device to which the embodiments of the present application are applied;

fig. 11 is a schematic diagram of an electronic device to which the embodiments of the present application are applied.

Detailed Description

In order to make the objects, technical solutions and advantageous effects of the present invention more apparent, the present invention will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.

For ease of understanding, the terms involved in the embodiments of the present invention are explained below.

Cloud technology (Cloud technology): the cloud computing business model application-based network technology, information technology, integration technology, management platform technology, application technology and the like can be collectively called to form a resource pool, and the resource pool is flexible and convenient as required. Cloud computing technology will become an important support. Background services of technical networking systems require a large amount of computing, storage resources, such as video websites, picture-like websites, and more portals. Along with the high development and application of the internet industry, each article possibly has an own identification mark in the future, the identification mark needs to be transmitted to a background system for logic processing, data with different levels can be processed separately, and various industry data needs strong system rear shield support and can be realized only through cloud computing.

Cloud computing (Cloud computing): a computing mode distributes computing tasks over a large number of computer-made resource pools, enabling various application systems to acquire computing power, storage space, and information services as needed. The network that provides the resources is referred to as the "cloud". Resources in the cloud are infinitely expandable in the sense of users, and can be acquired at any time, used as needed, expanded at any time and paid for use as needed.

As a basic capability provider of cloud computing, a cloud computing resource pool [ cloud platform for short, generally referred to as IaaS (Infrastructure as a Service ) platform ] is established, and multiple types of virtual resources are deployed in the resource pool for external clients to select for use. The cloud computing resource pool mainly comprises: computing devices (which are virtualized machines, including operating systems), storage devices, network devices.

According to the logic function division, a PaaS (Platform as a Service ) layer can be deployed on an IaaS (Infrastructure as a Service ) layer, and a SaaS (Software as a Service, software as a service) layer can be deployed above the PaaS layer, or the SaaS can be directly deployed on the IaaS. PaaS is a platform on which software runs, such as a database, web container, etc. SaaS is a wide variety of business software such as web portals, sms mass senders, etc. Generally, saaS and PaaS are upper layers relative to IaaS.

Proprietary cloud (Proprietary cloud): a cloud computing mode provided in an oriented manner establishes private cloud of an enterprise in a data center of a cloud service enterprise, and opens up a cloud platform system meeting self business architecture and security requirements on a public cloud architecture in a manner similar to cloud hosting, so that better isolation and better flexibility than the public cloud are obtained.

Cloud application: the cloud service provider uses virtual technology to provide hardware, software and other applications for users in a network transmission interaction mode.

The following describes the design ideas of the embodiments of the present application.

In the related art, the deployment process of the proprietary cloud application often faces the following disadvantages:

first aspect: in the related technology, a corresponding application deployment tool needs to be designed and developed according to a system deployment environment required by the current proprietary cloud application, and a great deal of labor cost and time cost are required to be consumed in the process, so that the deployment cost of the proprietary cloud application is often higher in an actual scene.

Second aspect: in the related art, in order to ensure the floor deployment of the proprietary cloud application, the related technical object is often required to detect the equipped system deployment environment in the proprietary service device specified by the target object, so as to determine whether the current system deployment environment meets the actual deployment requirement of the customized proprietary cloud application, however, the above-mentioned environment detection process is often complex, so that in the related art, the deployment threshold of the proprietary cloud application is often higher, and portability of the proprietary cloud application is often poor.

In other words, in the related art, based on the instrumented cloud application deployment mode, the dependency on related research and development technical objects is strong, so that the deployment threshold of the proprietary cloud application is high, and the deployment cost is high.

In view of this, an embodiment of the present application provides a method, an apparatus, an electronic device, and a storage medium for deploying a proprietary cloud application, where in the method, a proprietary cloud application to be deployed may be divided into a plurality of application components that may be deployed independently, and each application component may correspond to a unique target task template according to its component class, where at least one basic deployment operation determined for the corresponding component class is recorded in the target task template; the method can further combine each target task template by acquiring the respective parameter information of each application component and the corresponding component deployment sequence to generate corresponding application deployment information, so that the deployment of the proprietary cloud application is realized according to the basic deployment operation recorded in the application deployment information.

In the embodiment of the application, the deployment of the proprietary cloud application is realized based on the corresponding component deployment sequence and at least one basic deployment operation contained in the target task templates determined by each application component. Compared with the related art, based on the cloud application deployment mode of the tooled, the method can realize the deployment of the corresponding proprietary cloud application according to the basic deployment operation and the corresponding parameter information recorded by each component task template by only respectively acquiring the component task templates corresponding to each application component from the maintained component task template set.

In other words, in the above manner, the basic capability provider only needs to design and maintain a sufficient number of component task templates, so that deployment of various different proprietary cloud applications can be realized, and as the above systematic proprietary cloud application deployment manner is adopted, corresponding component task templates can be obtained according to corresponding component categories of different system deployment environments, so that dependence on development technical objects in related technologies is further reduced, flexibility of proprietary cloud application deployment is higher, and corresponding deployment threshold and deployment cost are greatly reduced.

An application scenario to which the proprietary cloud application deployment method in the embodiment of the present application is applicable is described in the following, and referring to fig. 1, which is a schematic application scenario diagram applicable to the embodiment of the present application, where the application scenario diagram includes two terminal devices 101 and a server 102.

The terminal device 101 is installed with a proprietary cloud application deployment-related application, which may be a pre-installed client, web page application, or applet embedded in other applications, or the like. The terminal device 101 may be, but is not limited to, a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, a smart television, etc.

Server 102 is a background server of the relevant application described above for providing relevant services for proprietary cloud application deployment. The server 102 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or may be a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, a content delivery network (Content Delivery Network, CDN), basic cloud computing services such as big data and an artificial intelligence platform. The terminal device 101 and the server 102 may be directly or indirectly connected through wired or wireless communication, which is not limited herein.

The terminal device 101 responds to application deployment operation triggered by aiming at a specific proprietary cloud application, and sends a deployment request to the server 102, wherein the proprietary cloud application comprises a plurality of application components, and each application component corresponds to at least one sub-function of the proprietary cloud application; and the deployment request sent by the terminal device 101 includes resource information of the proprietary cloud application, where the resource information at least includes: parameter information of each of the plurality of application components, and a corresponding component deployment order among the plurality of application components.

The server 102 may receive the deployment request sent by the terminal device 101, and generate corresponding application deployment information according to the resource information included in the deployment request and preset task templates of each component; then, the server 102 may further perform a base deployment operation recorded in the application deployment information, so as to deploy the proprietary cloud application to the terminal device 101 according to each base deployment operation, and in a preferred embodiment, the deployment request sent by the terminal device 101 may further include a device identifier of another device that creates a communication connection with the server 102, and then the server 102 may deploy the specified proprietary cloud application to the other device according to the obtained device identifier.

Further, the server 102 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a plurality of cloud servers providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, basic cloud computing services such as big data and artificial intelligence platforms, and the like.

Referring to fig. 2, the embodiment of the present application further provides a proprietary cloud application deployment platform 200, which is constructed based on the proprietary cloud application deployment apparatus 1000 described in the embodiment, where a client of the proprietary cloud application deployment platform 200 may run on the terminal device 101, and the functions of the proprietary cloud application deployment platform 200 may be implemented by a server or a cloud server or a blockchain server or a server cluster; the proprietary cloud application deployment platform 200 mainly includes a control module 201, a management module 202, and an execution module 203, where:

the control module 201 is configured to obtain a deployment request sent by an operation client, where the operation client is implemented based on a cloud service, and the deployment request includes resource information specifying a proprietary cloud application.

The management module 202 is configured to parse the resource information in the deployment request sent by the control module 201, and generate corresponding application deployment information by combining preset task templates of each component based on each parsed parameter information and a corresponding component deployment sequence, where at least one basic deployment operation determined for the specified proprietary cloud application is recorded in the application deployment information.

And the execution module 203 is configured to execute the basic deployment operations recorded in the application deployment information respectively, so as to implement the deployment of the specific proprietary cloud application.

The functions of the control module 201 may be implemented by the server 102, or may be implemented by a cloud server or a blockchain server or a server cluster, which may be oriented to an application deployment object related to the basic capability provider, where the application deployment object may send a corresponding deployment request to the control module 201 through a specified operation triggered on the running client.

Specifically, fig. 3 illustrates a possible interface schematic diagram in the above-mentioned running client, and in this client, the relevant application deployment object may send, through a triggered click operation, a deployment request for the selected proprietary cloud application 1 to the proprietary cloud application deployment platform.

The component task templates provided by the management module 202 may be, but are not limited to, static files for various application components (such as image, dbsql, product, yunapi, etc.), where each component task template has at least one base deployment operation recorded therein for a corresponding component class.

The management module 202 may be implemented by the server 102, by one or more cloud servers, or by a server cluster; the management module is used for supporting analysis of the resource information in the deployment request, and generating corresponding application deployment information by combining preset component task templates based on the analyzed parameter information and corresponding component deployment sequence.

The management module 202 also supports management of each base deployment operation recorded in each component task template, for example, management of an execution order of each base deployment operation in an actual deployment, management of an execution attribute of each deployment operation in an actual deployment, and the like. In an alternative embodiment, the management module 202 includes a template manager 2021 supporting component task template management, a deployment manager 2022 supporting application deployment information generation, and a setup interface 2203 supporting the docking execution module 203.

The setting interface 2203 may be a general and open interface for at least one basic deployment operation, and the management module 202 may interface with the execution module 203 through the setting interface 2203, so that the execution module 203 may invoke and execute the basic deployment operation recorded in the application deployment information, to implement deployment of the specified proprietary cloud application.

Based on the system architecture shown in fig. 1 or the proprietary cloud application deployment platform shown in fig. 2, the embodiment of the application provides a proprietary cloud application deployment method, which may be executed by a computer device, and the computer device may be a terminal device and a server in fig. 1, as shown in fig. 4, and the method includes:

S401: and acquiring resource information of the appointed proprietary cloud application.

Specifically, the proprietary cloud application is a cloud computing application deployed in a proprietary network environment, the proprietary cloud application comprising a plurality of application components, wherein each application component corresponds to at least one sub-function of the proprietary cloud application.

For example, in an actual situation, an application function of a proprietary cloud application to be deployed may be divided into a plurality of corresponding sub-functions, so that the proprietary cloud application is divided into a plurality of application components that can be deployed independently based on each determined sub-function, and specifically, in the embodiment of the present application, it is assumed that the proprietary cloud application includes: an application component 1, an application component 2, and an application component 3; the deployment of the proprietary cloud application may be implemented by deploying the above-described plurality of application components separately based on the above-described manner.

Further, the resource information of the proprietary cloud application may include parameter information of each of the plurality of application components and a corresponding component deployment sequence among the plurality of application components. Specifically, the above parameter information may be obtained from a determined deployment application tree, and further, in the deployment application tree, an application version of the proprietary cloud application may be further included, and by matching the determined application version with a preset deployment sequence, a component deployment sequence determined for the current application version may be obtained.

As an embodiment, the resource information may further include application description information of the proprietary cloud application, and specifically, the application description information may include: an application version of the proprietary cloud application, an application programming ID, and the like, thereby further indicating deployment of the proprietary cloud application.

S402: for a plurality of application components, the following operations are respectively executed: and determining a corresponding target task template from a preset component task template set according to the component category of one application component.

Specifically, when the corresponding target task templates of the application components are obtained, determining from a preset component task template set based on the respective component category of each application component; wherein each component task template records at least one base deployment operation determined for the component category.

For example, depending on its corresponding deployment environment, the component categories may include: image, dbsql, product, yunapi, etc., then for each component class, a corresponding component task template may be defined and maintained, which is regarded as a corresponding target task template, in other words, for each component class, at least one corresponding basic deployment operation may be quickly determined according to the above manner.

It should be understood that, in the specific implementation, an independent component task template may be defined and maintained for some specific application components, and the above manner is only illustrative and not described herein.

S403: and combining all target task templates based on the resource information to generate corresponding application deployment information.

Specifically, at least one basic deployment operation determined for the corresponding component class is recorded in each target task template, so that application deployment information corresponding to the proprietary cloud application can be generated by combining the obtained resource information with each target task template according to a corresponding combination rule, wherein the application deployment information records at least one basic deployment operation determined for the proprietary cloud application, and represents the deployment of the proprietary cloud application and each basic deployment operation to be executed required.

S404: and respectively executing the basic deployment operation recorded in the application deployment information to realize the deployment of the proprietary cloud application.

Specifically, the basic deployment operations recorded in the application deployment information can be executed respectively through modes such as Http call and the like, so that the deployment of the proprietary cloud application can be realized through orderly execution of each basic deployment operation.

In the embodiment of the application, the deployment of the proprietary cloud application is realized based on the corresponding component deployment sequence and at least one basic deployment operation contained in the target task templates determined by each application component. Compared with the related art, based on the cloud application deployment mode of the tooled, the method can realize the deployment of the corresponding proprietary cloud application according to the basic deployment operation and the corresponding parameter information recorded by each component task template by only respectively acquiring the component task templates corresponding to each application component from the maintained component task template set. Because the above-mentioned systematic proprietary cloud application deployment mode, to different system deployment environments, can all obtain the correspondent assembly task template according to its correspondent assembly classification, therefore, the above-mentioned mode has reduced the dependence on the technical object of research of the related technology effectively, make the flexibility of the deployment of proprietary cloud application higher, correspondent deployment threshold and deployment cost greatly reduce.

Optionally, in the step S402, the embodiment of the present application provides at least the following implementation manner to generate the component task template:

for each component class of the plurality of application components, the following operations are performed: acquiring category description information determined for a component category, wherein the category description information at least records: a category deployment environment determined for a component category; and then, determining at least one basic deployment operation corresponding to the category deployment environment from a preset basic deployment operation set based on the category description information, and combining the at least one basic deployment operation based on a preset deployment rule to generate a corresponding component task template.

As one example, the component task template may be a corresponding static file designed and developed for a class deployment environment that specifies a class of components. And each component task template includes at least one base deployment operation determined for a specified component class.

For example, assuming that the application component 1 is a product component type, please refer to fig. 5 for a component task template of the product component type, wherein the component task template may include five basic deployment operations adapted to the product component type deployment environment, which are respectively material preparation, configuration preparation, script deployment, application deployment and service registration; in particular, the above-described base deployment operations may be represented as one atomic deployment operation performed during one component deployment task.

As an embodiment, in the component task template, each basic deployment operation may further carry corresponding operation description information, where the operation description information at least includes: the execution order of the respective base deployment operations.

Based on the mode, the method can support the related management objects to adaptively change the execution sequence of each recorded basic deployment operation in the component task template aiming at different deployment conditions, so that finer granularity control on the proprietary cloud application deployment is realized.

For example, referring to fig. 6, in the component task template shown in fig. 5, the execution order of each base deployment operation may be defined by a list index; specifically, the following table 1 shows:

TABLE 1

In the above example, each list subscript corresponding to each base deployment operation defines the execution order of the base deployment operation in the actual deployment, for example, for the base deployment operation "configuration ready", the corresponding list subscript "2" can define the execution order of the base deployment operation in the actual deployment to be the second bit, and then the execution order shown in the above example can be defined as: "Material preparation-configuration preparation-script deployment-application deployment-service registration"; this means that in a practical scenario, the related management object can implement the modification of the execution sequence between the corresponding base deployment operations by modifying the list index corresponding to each base deployment operation, so as to achieve the purpose of finer granularity control on the deployment of the proprietary cloud application.

As one embodiment, the operation description information carried by each basic deployment operation may further include an execution attribute of the corresponding basic deployment operation, for example, may be skipped, may be executed, etc.; in particular, the execution attributes described above may be defined by special fields carried by the underlying deployment operation.

Based on the mode, the method can support the related management objects to adaptively change the execution attribute of each recorded basic deployment operation in the component task template aiming at different deployment conditions, so that finer granularity control on the proprietary cloud application deployment is realized.

For example, referring to fig. 7, in the component task template shown in fig. 5, the execution attribute of each base deployment operation may be defined by a special field carried by each base deployment operation; specifically, the following table 2 shows:

TABLE 2

In the above example, each base deployment operation corresponds to a carried special field, and defines an execution attribute of the base deployment operation in an actual deployment, for example, for the base deployment operation "application deployment", a specified special field "TimeOut" is carried, and then based on the special field, the execution attribute of the base deployment operation in the actual deployment can be defined as "to be executed", that is, in the actual deployment, the base deployment operation "application deployment" can be skipped, and subsequent other base deployment operations can be executed.

Specifically, if the execution sequence of each basic deployment operation in the above example may be defined as "material preparation-configuration preparation-script deployment-application deployment-service registration", after the basic deployment operation "script deployment" is executed, the basic deployment operation "application deployment" may be skipped, and the basic deployment operation "service registration" may be further executed; in other words, in the above example, only the "material preparation-configuration preparation-script deployment-service registration" recorded in the corresponding component task template needs to be sequentially executed, which means that in an actual scenario, the related management object can implement the modification of the execution attribute between the corresponding base deployment operations by modifying the special fields carried by each base deployment operation, so that the execution process of each base deployment operation is more structural, and the purpose of finer granularity control on the proprietary cloud application deployment is achieved.

Optionally, in the step S403, the embodiment of the present application provides at least the following implementation manner to generate the application deployment information:

for the parameter information of each of the plurality of application components, the following operations are respectively executed: based on a target task template corresponding to an application component, parameter information of the application component is combined, each basic deployment operation corresponding to the application component is determined, each basic deployment operation corresponding to a plurality of application components is sequenced based on the component deployment sequence, and corresponding application deployment information is generated based on sequencing results.

Specifically, for an application component, the target task template and the parameter information are combined based on matching fields in the target task template and the parameter information, for example, component material information contained in the parameter information is combined with corresponding basic deployment operations based on matching fields in the target task template and the component material information.

Further, as the deployment of the proprietary cloud application is the deployment of a plurality of application components contained in the proprietary cloud application, each application component corresponds to a plurality of corresponding basic deployment operations; therefore, by sequencing the obtained component deployment sequence, the corresponding basic deployment operations of the application components can generate corresponding application deployment information, and it is noted that the component deployment sequence can be obtained from the resource information, i.e. defined by the externally connected deployment object, or custom-set by the related management object according to the actual situation, which is not described herein.

For example, the component deployment order may be determined in advance via related management object settings, e.g., according to the component category dbsql, yunapi, image of each application component mentioned above, the related management object may set the component deployment order as follows: the expression "dbsql-yuneapi-image" means that in each application component deployment, each application component corresponding to the dbsql component class is deployed preferentially according to the component deployment sequence, and each application component corresponding to the image component class is deployed in a hysteresis manner, so as to further improve the arrangement flexibility of the component task template.

In order to better explain the embodiments of the present application, a method for deploying a proprietary cloud application provided in the embodiments of the present application is described below in conjunction with a specific implementation scenario, where a flow of the method may be interactively executed by a terminal device 101 and a server 102 shown in fig. 1, and the method includes the following steps, as shown in fig. 8:

s801, the terminal equipment sends resource information specifying the proprietary cloud application to the server.

Specifically, the server comprises a database and a service module, wherein the service module is used for providing proprietary cloud application deployment automation service. When executing the proprietary cloud application deployment automation service, the server acquires resource information of the appointed proprietary cloud application through a preset scheduling interface; the proprietary cloud application comprises a plurality of application components, and each application component corresponds to at least one sub-function of the proprietary cloud application; the resource information includes at least: parameter information of each of the plurality of application components, and a corresponding component deployment order among the plurality of application components.

S802, the server performs the following operations for the plurality of application components, respectively: and determining a corresponding target task template from a preset component task template set according to the component category of one application component.

Specifically, at least one basic deployment operation determined for the component category is recorded in each component task template.

For example, depending on its corresponding deployment environment, the component categories may include: image, dbsql, product, yuanpi, etc., a corresponding component task template may be defined and maintained for each component class, which is regarded as a corresponding target task template, in other words, for each component class, at least one corresponding basic deployment operation may be quickly determined according to the above manner.

S803, the server combines all target task templates based on the resource information to generate corresponding application deployment information.

Specifically, the server combines the target task template and the parameter information based on the matching field in the parameter information of the target task template and the application component, for example, combines the component material information contained in the parameter information with corresponding basic deployment operations based on the matching field in the component material information in the target task template, and generates corresponding application deployment information.

S804, the server respectively executes basic deployment operations recorded in the application deployment information to realize the deployment of the proprietary cloud application.

Specifically, the server executes the basic deployment operation recorded in the application deployment information through a preset scheduling interface respectively, so as to realize the deployment of the proprietary cloud application.

Optionally, the above method for deploying a proprietary cloud application may further include:

s805, the server returns a deployment result of the specific proprietary cloud application to the terminal equipment.

Specifically, the server can return the deployment result of the current appointed proprietary cloud application to the terminal equipment through the scheduling interface so as to ensure the accuracy of the deployment of the proprietary cloud application.

Referring to fig. 9, a logic schematic diagram of a proprietary cloud application deployment method provided in an embodiment of the present application is first obtained, where the proprietary cloud application includes a plurality of application components, and each application component corresponds to at least one sub-function of the proprietary cloud application. Taking a proprietary cloud application 'Tcenter' as an example, the proprietary cloud application comprises a plurality of application components, namely an application component 'product-Tcenter-X1'; an application component "dbsql-tcenter-X2" and an application component "product-tcenter-X3", wherein the component categories of the application components are "product", "dbsql", "product", respectively; then, each application component can determine a corresponding target task template from the preset component task templates according to the corresponding component category, and specifically, each application component determines the target task template as shown in the following table 3:

TABLE 3 Table 3

Application component	Component task template
		product-tcenter-X1	formwork_product
dbsql-tcenter-X2	formwork_dbsql
		product-tcenter-X	formwork_product

Further, in the form_product component task template, five basic deployment operations determined for the "product" component type are recorded, which are "material preparation", "configuration preparation", "script deployment", "application deployment" and "service registration", respectively; in the formwork_dbsql component task template, three basic deployment operations determined for the "dbsql" component type are recorded, and the three basic deployment operations are respectively "material preparation", "configuration preparation" and "application deployment", and based on the basic deployment operations recorded in each component task template and the respective parameter information (for example, component material information, component planning ID, component region information and the like) of each application component in the resource information, the application deployment information corresponding to the proprietary cloud application "Tcenter" can be generated, and further, the deployment of the proprietary cloud application "Tcenter" can be realized by respectively executing the basic deployment operations recorded in the application deployment information.

Based on the mode, the application deployment information for the specified proprietary cloud application 'Tcenter' can be quickly generated based on the preset formwork_dbsql component task template and the formwork_product component task template, and compared with the related art, the mode avoids a great deal of labor cost and time cost caused by repeated design and development of application deployment tools, so that the deployment cost of the proprietary cloud application is greatly reduced; on the other hand, in the above manner, each component task template includes at least one basic deployment operation for a specified component class, and for different system deployment environments, the corresponding component task template can be obtained according to the corresponding component class, so that the method for deploying the proprietary cloud application further reduces excessive dependence on the development technical object in the related technology, so that the flexibility of deploying the proprietary cloud application is higher, and the corresponding deployment threshold and the deployment cost are greatly reduced.

Based on the same technical concept, the embodiment of the present application provides a structural schematic diagram of a proprietary cloud application deployment apparatus, as shown in fig. 10, the apparatus 1000 includes:

an obtaining module 1001, configured to obtain resource information specifying a proprietary cloud application, where the proprietary cloud application includes a plurality of application components, and each application component corresponds to at least one sub-function of the proprietary cloud application; the resource information includes at least: parameter information of each of the plurality of application components, and a corresponding component deployment order among the plurality of application components.

A determining module 1002, configured to, for a plurality of application components, perform the following operations respectively: according to the component category of an application component, a corresponding target task template is determined from a preset component task template set, wherein at least one basic deployment operation determined for the component category is recorded in each component task template.

The combination module 1003 is configured to combine the target task templates based on the resource information to generate corresponding application deployment information, where at least one basic deployment operation determined for the proprietary cloud application is recorded in the application deployment information.

The execution module 1004 is configured to execute the basic deployment operations recorded in the application deployment information respectively, so as to implement the deployment of the proprietary cloud application.

Optionally, before acquiring the deployment resource information of the specific proprietary cloud application, the acquiring module 1001 is further configured to:

Optionally, when acquiring the resource information of the specific proprietary cloud application, the acquiring module 1001 is specifically configured to:

Optionally, each basic deployment operation carries corresponding operation description information, where the operation description information at least includes: the execution order of the corresponding base deployment operations; then, based on the preset deployment rule, at least one basic deployment operation is combined, and when a corresponding component task template is generated, the combining module 1003 is specifically configured to:

Optionally, based on the resource information, each target task template is combined, and when corresponding application deployment information is generated, the combining module 1003 is specifically configured to:

Optionally, the operation description information further includes: the execution attribute of the corresponding base deployment operation; the executing module 1004 is specifically configured to:

Optionally, the execution module 1004 is further configured to:

Based on the same technical concept, the embodiment of the present application provides a computer device, which may be the target device and/or the server shown in fig. 1, as shown in fig. 11, including at least one processor 1102, and a memory 1101 connected to the at least one processor, where a specific connection medium between the processor 1102 and the memory 1101 is not limited in the embodiment of the present application, and a bus connection between the processor 1102 and the memory 1101 is exemplified in fig. 11. The buses may be divided into address buses, data buses, control buses, etc.

In the embodiment of the present application, the memory 1101 stores instructions executable by the at least one processor 1102, and the at least one processor 1102 may perform the steps of the above-described proprietary cloud application deployment method by executing the instructions stored in the memory 1101.

Where the processor 1102 is a control center of a computer device, various interfaces and lines may be utilized to connect various portions of the computer device, through execution or execution of instructions stored in the memory 1101 and invocation of data stored in the memory 1101, to thereby effect proprietary cloud application deployment. Alternatively, the processor 1102 may include one or more processing units, and the processor 1102 may integrate an application processor that primarily processes operating systems, user interfaces, application programs, and the like, with a modem processor that primarily processes wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 1102. In some embodiments, the processor 1102 and the memory 1101 may be implemented on the same chip, and in some embodiments they may be implemented separately on separate chips.

The processor 1102 may be a general purpose processor such as a Central Processing Unit (CPU), digital signal processor, application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, that can implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution.

The memory 1101 is a non-volatile computer-readable storage medium, and can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The Memory 1101 may include at least one type of storage medium, and may include, for example, flash Memory, a hard disk, a multimedia card, card Memory, random access Memory (Random Access Memory, RAM), static random access Memory (Static Random Access Memory, SRAM), programmable Read-Only Memory (Programmable Read Only Memory, PROM), read-Only Memory (ROM), charged erasable programmable Read-Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), magnetic Memory, magnetic disk, optical disk, and the like. The memory 1101 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto. The memory 1101 in the embodiments of the present application may also be a circuit or any other device capable of implementing a storage function, for storing program instructions and/or data.

Based on the same inventive concept, the embodiments of the present application provide a computer-readable storage medium storing a computer program executable by a computer device, which when run on the computer device, causes the computer device to perform the steps of the above-described proprietary cloud application deployment method.

Based on the same inventive concept, embodiments of the present application provide a computer program product comprising a computer program stored on a computer readable storage medium, the computer program comprising program instructions, which when executed by a computer, cause the computer to perform the steps of the above-described proprietary cloud application deployment method.

It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, or as a computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the invention.

It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims

1. The method for deploying the proprietary cloud application is characterized by comprising the following steps of:

Acquiring resource information of a specified proprietary cloud application, wherein the proprietary cloud application comprises a plurality of application components, and each application component corresponds to at least one sub-function of the proprietary cloud application; the resource information includes at least: parameter information of each of the plurality of application components and a corresponding component deployment sequence among the plurality of application components;

for the plurality of application components, respectively performing the following operations: determining a corresponding target task template from a preset component task template set according to a component class of an application component, wherein each component task template records at least one basic deployment operation determined for the component class;

based on the resource information, combining each target task template to generate corresponding application deployment information, wherein at least one basic deployment operation determined for the proprietary cloud application is recorded in the application deployment information;

2. The method of claim 1, wherein prior to obtaining the resource information specifying the proprietary cloud application, further comprising:

For each component class of the plurality of application components, respectively performing the following operations:

acquiring category description information determined for a component category, wherein the category description information at least records: a category deployment environment determined for the one component category;

determining at least one basic deployment operation corresponding to the category deployment environment from a preset basic deployment operation set based on the category description information;

and combining the at least one basic deployment operation based on a preset deployment rule to generate a corresponding component task template.

3. The method of claim 1 or 2, wherein the obtaining resource information specifying a proprietary cloud application comprises:

acquiring a deployment application tree determined for the proprietary cloud application, wherein the deployment application tree at least comprises: the application version of the proprietary cloud application and the parameter information of each of a plurality of application components contained in the proprietary cloud application;

based on the application version of the proprietary cloud application, determining a component deployment sequence corresponding to the application version from a preset deployment sequence set;

4. The method of claim 1 or 2, wherein each base deployment operation carries corresponding operation description information, the operation description information comprising at least: the execution order of the corresponding base deployment operations; combining the at least one basic deployment operation based on a preset deployment rule to generate a corresponding component task template, wherein the method comprises the following steps:

sorting the at least one base deployment operation according to a small-to-large arrangement order based on respective execution orders of the at least one base deployment operation;

and combining the at least one basic deployment action based on the sequencing result of the at least one basic deployment operation to generate a corresponding component task template.

5. The method according to claim 1 or 2, wherein the combining each target task template based on the resource information to generate corresponding application deployment information includes:

for the parameter information of each of the plurality of application components, respectively executing the following operations: based on a target task template corresponding to one application component, combining parameter information of the one application component, and determining each basic deployment operation corresponding to the one application component;

And sequencing the corresponding basic deployment operations of the application components based on the component deployment sequence, and generating corresponding application deployment information based on sequencing results.

6. The method of claim 4, wherein the operation description information further comprises: the execution attribute of the corresponding base deployment operation; the base deployment operations recorded in the application deployment information are executed respectively to realize the deployment of the proprietary cloud application, including:

based on the execution sequence of each basic deployment operation in the application deployment information, determining the execution attribute of each basic deployment operation in turn according to the arrangement sequence from small to large, wherein:

if the execution attribute of the basic deployment operation is: if the operation can be skipped, the deployment attribute of the next basic deployment operation is read;

if the execution attribute of the basic deployment operation is: and if yes, executing the basic deployment operation and reading the deployment attribute of the next basic deployment operation.

7. The method as recited in claim 6, further comprising:

if the execution attribute of the basic deployment operation is: and if the operation is overtime, executing the basic deployment operation within a preset overtime time range, and reading the deployment attribute of the next basic deployment operation.

8. A proprietary cloud application deployment apparatus, comprising:

the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring resource information of a specified proprietary cloud application, the proprietary cloud application comprises a plurality of application components, and each application component corresponds to at least one sub-function of the proprietary cloud application; the resource information includes at least: parameter information of each of the plurality of application components and a corresponding component deployment sequence among the plurality of application components;

a determining module, configured to, for each of the plurality of application components, perform the following operations: determining a corresponding target task template from a preset component task template set according to a component class of an application component, wherein each component task template records at least one basic deployment operation determined for the component class;

the combination module is used for combining all target task templates based on the resource information to generate corresponding application deployment information, wherein at least one basic deployment operation determined for the proprietary cloud application is recorded in the application deployment information;

9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method of any of claims 1-7 when the program is executed.

10. A computer readable storage medium storing computer instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1-7.