CN117742730A

CN117742730A - Project deployment method and device, electronic equipment and storage medium

Info

Publication number: CN117742730A
Application number: CN202311750523.3A
Authority: CN
Inventors: 张丽彪; 马瑞源; 王晓; 饶星; 王倩; 陈炜钊
Original assignee: Agricultural Bank of China
Current assignee: Agricultural Bank of China
Priority date: 2023-12-19
Filing date: 2023-12-19
Publication date: 2024-03-22

Abstract

The invention discloses a project deployment method, a project deployment device, electronic equipment and a storage medium, wherein the project deployment method comprises the following steps: when a project deployment request of a target tenant is received, determining a project to be deployed corresponding to the target tenant according to project association information; determining at least one project configuration file corresponding to a project to be deployed, and packaging the project configuration file associated with the project to be deployed to obtain a target deployment project; determining a project deployment mode corresponding to the target deployment project, and deploying the target deployment project based on the project deployment mode. The problem that in the prior art, tenants are required to have special project deployment technology to deploy corresponding micro-service applications on a cloud platform, so that the use threshold of the tenants for BI products is high is solved, deployment difficulty of the tenants can be reduced by adopting SAAS platform-based automation to deploy according to project deployment information, and the effect of deploying the micro-service applications required by the tenants in the cloud platform in a one-click manner after the tenants provide the project deployment information is achieved.

Description

Project deployment method and device, electronic equipment and storage medium

Technical Field

The present invention relates to the field of data processing technologies, and in particular, to a project deployment method, a device, an electronic device, and a storage medium.

Background

With the development of big data technology, business intelligence (Business Intelligence, BI) has been widely used in various fields.

At present, the on-deployment flow of the BI product is complex, project group public mirror promotion, off-line deployment document delivery, tenant assembly line construction, tenant manual configuration, on-production verification and other core links are needed for tenant production, part of tenants do not know about CCE cloud and assembly line deployment process, and the project group is required to be supported by extremely large manpower, and because the on-production flow of the BI product is complex, the threshold of the tenant using the BI product is too high.

In order to solve the above problems, improvements to the BI-based project deployment method are needed.

Disclosure of Invention

The invention provides a project deployment method, a project deployment device, electronic equipment and a storage medium, which are used for solving the problem that in the prior art, tenants are required to have special project deployment technology to deploy corresponding micro-service applications on a cloud platform, so that the use threshold of the tenants for BI products is high.

In a first aspect, an embodiment of the present invention provides a project deployment method, including:

When a project deployment request of a target tenant is received, determining a project to be deployed corresponding to the target tenant according to project association information; the project association information comprises project configuration information and/or project demand information;

determining at least one project configuration file corresponding to the project to be deployed, and packaging the project configuration file associated with the project to be deployed to obtain a target deployment project;

determining a project deployment mode corresponding to the target deployment project, and deploying the target deployment project based on the project deployment mode; the project deployment mode is a transverse deployment mode or a vertical shaft deployment mode.

In a second aspect, an embodiment of the present invention further provides an item deployment apparatus, including:

the to-be-deployed project determining module is used for determining a to-be-deployed project corresponding to a target tenant according to project association information when a project deployment request of the target tenant is received; the project association information comprises project configuration information and/or project demand information;

the target deployment project determining module is used for determining at least one project configuration file corresponding to the project to be deployed, and packaging the project configuration file associated with the project to be deployed to obtain a target deployment project;

The deployment mode determining module is used for determining a project deployment mode corresponding to the target deployment project and deploying the target deployment project based on the project deployment mode; the project deployment mode is a transverse deployment mode or a vertical shaft deployment mode.

In a third aspect, an embodiment of the present invention further provides an electronic device, including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the project deployment method of any one of the embodiments of the present invention.

In a fourth aspect, an embodiment of the present invention further provides a computer readable storage medium, where computer instructions are stored, where the computer instructions are configured to cause a processor to execute the method for item deployment according to any embodiment of the present invention.

According to the technical scheme, when a project deployment request of a target tenant is received, a project to be deployed corresponding to the target tenant is determined according to project association information; determining at least one project configuration file corresponding to a project to be deployed, and packaging the project configuration file associated with the project to be deployed to obtain a target deployment project; determining a project deployment mode corresponding to the target deployment project, and deploying the target deployment project based on the project deployment mode. In the technical scheme, when an item deployment request sent by a target tenant is received, item association information corresponding to the target tenant is acquired to determine an item to be deployed corresponding to the target tenant, further, at least one item function in the item to be deployed is determined, item configuration files corresponding to the item functions are determined, and the item configuration files are configured and packaged according to the dependency relationship among the item configuration files to obtain a target deployment item. Further, according to the service requirement corresponding to the target tenant, the requirements on the service processing speed, the data security level and the like, a project deployment mode corresponding to the target deployment project is determined, and the target deployment project is deployed based on the project deployment mode. According to the technical scheme, the problem that the tenant has a special project deployment technology to deploy the corresponding micro-service application on the cloud platform, so that the use threshold of the tenant for BI products is high is solved.

It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the invention or to delineate the scope of the invention. Other features of the present invention will become apparent from the description that follows.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a flow chart of a project deployment method according to a first embodiment of the present invention;

FIG. 2 is a flow chart of a project deployment method according to a second embodiment of the present invention;

FIG. 3 is a flow chart of a project deployment method according to a second embodiment of the present invention;

FIG. 4 is a schematic diagram of a project deployment mode according to a second embodiment of the present invention;

fig. 5 is a schematic structural view of a project deployment apparatus according to a third embodiment of the present invention;

fig. 6 is a schematic structural diagram of an electronic device implementing the project deployment method according to an embodiment of the present invention.

Detailed Description

In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above 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 of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein.

Before the technical scheme is elaborated, an application scene of the technical scheme is simply introduced so as to more clearly understand the technical scheme. Software as a service (Software as aService, SAAS) is a software architecture technology provided over the Internet, and users can implement software usage without building software dependencies. Generally, for the SAAS platform, the SAAS platform may be a multi-tenant architecture, where multi-tenant refers to a multi-tenant technology (also referred to as multi-tenancy technology), and the multi-tenant architecture is implemented to share the same system or program component among multiple enterprise users, and ensure isolation of data among the enterprise users. In practical applications, if an enterprise user wants to use the SAAS platform, a corresponding micro-service application needs to be deployed on the SAAS platform. However, because of the stricter deployment process when project deployment (i.e., BI product deployment) is performed in the SAAS platform, the deployment process is not friendly to users who do not know the deployment process, and the threshold of using BI products by tenants is improved.

Example 1

Fig. 1 is a flowchart of a project deployment method provided in an embodiment of the present invention, where the method may be performed by a project deployment device, and the project deployment device may be implemented in the form of hardware and/or software, and the project deployment device may be configured in a computing device that may perform the project deployment method, where the case of deploying a micro-service application required by an enterprise user on a cloud platform through SAAS platform automation according to project deployment information and personalized deployment requirements provided by the enterprise user.

As shown in fig. 1, the method includes:

s110, when a project deployment request of a target tenant is received, determining a project to be deployed corresponding to the target tenant according to project association information.

The target tenant may be understood as an enterprise user who needs to perform project deployment on the SAAS platform. The project deployment request can be understood as request information of the target tenant for applying for project deployment to the SAAS platform. The project association information refers to project information needed to be used when a target tenant provides a project to the SAAS platform for deployment. Wherein the project association information includes project configuration information and/or project requirement information. The item to be deployed may be understood as a micro-service application deployed by the target tenant on the SAAS platform.

In practical application, the tenant can realize the effect of using the software service under the condition of largely building the software dependence by deploying the corresponding micro-service application on the SAAS platform. Based on the requirement of the target tenant on deploying the corresponding micro-service application on the SAAS platform, a project deployment request can be sent to the SAAS platform, and when the SAAS platform receives the request, project association information corresponding to a project to be deployed of the target tenant is obtained, and the project to be deployed is deployed according to the project association information.

Optionally, determining the item to be deployed corresponding to the target tenant according to the item association information corresponding to the target tenant includes: performing project deployment qualification authentication on the target tenant according to the project deployment request to obtain a target authentication result; and if the target authentication result is that the authentication is passed, acquiring item association information corresponding to the target tenant, and determining an item to be deployed corresponding to the target tenant according to the item association information.

The target authentication result refers to an authentication result corresponding to whether the target tenant qualifies for project deployment on the SAAS platform.

In practical application, when receiving a project deployment request, a corresponding target tenant needs to perform qualification screening to determine whether the target tenant can perform project deployment in the SAAS platform. Generally, the SAAS platform needs to perform identity authentication on a target tenant, also needs to perform authentication on project deployment requirements, project deployment environments and the like of the target tenant, and obtains a target authentication result after each authentication. If the target authentication result is that the authentication is passed, the method indicates that the item to be deployed corresponding to the target tenant can be deployed in the SAAS platform; otherwise, if the authentication is not passed, the deployment exception information needs to be fed back to the target tenant, so that the target tenant performs information update according to the feedback result, and the subsequent project deployment request is convenient after the information update.

Specifically, performing project deployment qualification authentication on the project deployment request to obtain a target authentication result, including: analyzing the project deployment request to obtain tenant authentication information corresponding to the target tenant, and authenticating the identity of the target tenant based on the tenant authentication information to obtain an identity authentication result; authenticating the project deployment environment corresponding to the target tenant according to the equipment performance information corresponding to the target tenant, and obtaining a deployment environment authentication result; and determining a target authentication result corresponding to the target tenant according to the identity authentication result and the deployment environment authentication result.

The tenant authentication information may be understood as information for characterizing an authorization status of the target tenant. The project deployment environment refers to a server that satisfies various requirements of project deployment to be deployed, and generally includes a production environment, a test environment, a development environment, and the like. In the technical scheme, the project deployment environment refers to a project environment required to be provided by the SAAS platform when a project to be deployed is deployed.

In practical application, when receiving a project deployment request, the SAAS platform needs to perform identity authentication on a target tenant, and also needs to perform authentication on whether a project deployment environment of the SAAS platform meets the deployment requirement of a project to be deployed.

Specifically, the tenant authentication information may include tenant identification information corresponding to the target tenant, where the SAAS platform searches whether tenant authentication information corresponding to the target tenant exists in a preset authorized list, if so, indicates that the target tenant is an authorized object approved by the SAAS platform, and the corresponding identity authentication result is authentication passing. On the basis, the project deployment environment in the platform is required to be authenticated according to the deployment environment requirement of the project to be deployed, and when the SAAS platform meets the project deployment requirement of the project to be deployed, the project deployment environment authentication result is that the authentication is passed. Only when the identity authentication result and the deployment environment result are authentication passing, the target authentication result corresponding to the target tenant is authentication passing.

S120, determining at least one project configuration file corresponding to the project to be deployed, and packaging the project configuration file associated with the project to be deployed to obtain a target deployment project.

The project configuration file may be understood as a component configuration file corresponding to a project function in a project to be deployed. It will be appreciated that at least one project function may be included in the project to be deployed, one project configuration file for each project function. The target deployment project may be understood as a micro-service application file generated according to at least one project configuration file corresponding to the project to be deployed, which may be used for deployment on the SAAS platform.

In practical application, determining at least one project configuration file corresponding to a project to be deployed, and packaging the project configuration file associated with the project to be deployed to obtain a target deployment project, wherein the method comprises the following steps: determining at least one project configuration file corresponding to the project to be deployed from a target mapping table based on the project requirements; and carrying out encapsulation processing on the project configuration file associated with the project to be deployed to obtain the target deployment project.

The project requirement comprises at least one project function, and the target mapping table comprises at least one project function and a project configuration file corresponding to each project function.

In practical application, in order to ensure that the target tenant can meet the project requirements of the target tenant after deploying the corresponding micro-service application on the SAAS platform, the project requirements can be sent to the SAAS platform while applying for project deployment to the SAAS platform. And when the SAAS platform detects the project requirements, extracting at least one project function in the project requirements, and comparing the project functions with project functions which can be realized in the platform. If the platform supports all project functions in the project requirement, acquiring project configuration files corresponding to the project functions from a platform configuration file database based on a preset target mapping table, and packaging all project configuration files associated with the project to be deployed to obtain a target configuration file.

Note that, for each item configuration file, each item configuration file may be independent, or may have a dependency relationship. For project configuration files with dependency relationships, the SAAS platform can query the dependency relationships among the project configuration files according to a pre-stored configuration file dependency relationship table, and correspondingly deploy corresponding project deployment files according to the dependency relationships to obtain target deployment projects.

S130, determining a project deployment mode corresponding to the target deployment project, and deploying the target deployment project based on the project deployment mode.

The project deployment mode is a transverse deployment mode or a vertical shaft deployment mode.

In the technical scheme, in order to meet project deployment requirements of tenants with different scales, two different project deployment modes are provided. The transverse type deployment mode refers to a deployment mode in which target deployment items corresponding to a plurality of tenants can be set for each cloud cluster in the cloud platform when the cloud platform is deployed. The vertical shaft type deployment mode refers to a deployment mode that only one target deployment project corresponding to one tenant can be deployed in one cloud cluster.

Optionally, determining a project deployment mode corresponding to the target deployment project, and deploying the target deployment project based on the project deployment mode, including: acquiring personalized deployment requirements corresponding to target tenants; according to the personalized deployment requirements, determining a project deployment mode corresponding to the target deployment project, and deploying the target deployment project based on the project deployment mode.

For each tenant, the service content of the processing service is different, and correspondingly, when the micro service application is deployed on the cloud platform, personalized setting is required according to the service requirement of the tenant. By personalized deployment requirements is meant project deployment requirements that are specifically set to meet the business requirements of the target tenant.

In practical application, because the service scale of each tenant is different, the generated service processing volume is also greatly different, and the requirements on service processing efficiency and data security level are also different, based on the fact, a transverse deployment mode and a vertical shaft deployment mode are provided in the technical scheme.

Generally, if the service scale of the target tenant is large and the service processing volume is large, the target deployment item corresponding to the target tenant is deployed based on the transverse deployment mode. If the service scale of the target tenant is smaller and the service volume to be processed is small, the target deployment project can be deployed based on a vertical shaft type deployment mode. In addition, generally, when the requirements on service processing efficiency and data security level are common, a transverse deployment mode is adopted; on the contrary, when the requirements on service processing efficiency and data security level are high, a vertical shaft type deployment mode is adopted.

According to the technical scheme, when a project deployment request of a target tenant is received, a project to be deployed corresponding to the target tenant is determined according to project association information; determining at least one project configuration file corresponding to a project to be deployed, and packaging the project configuration file associated with the project to be deployed to obtain a target deployment project; determining a project deployment mode corresponding to the target deployment project, and deploying the target deployment project based on the project deployment mode. In the technical scheme, when an item deployment request sent by a target tenant is received, item association information corresponding to the target tenant is acquired to determine an item to be deployed corresponding to the target tenant, further, at least one item function in the item to be deployed is determined, item configuration files corresponding to the item functions are determined, and the item configuration files are configured and packaged according to the dependency relationship among the item configuration files to obtain a target deployment item. Further, according to the service requirement corresponding to the target tenant, the requirements on the service processing speed, the data security level and the like, a project deployment mode corresponding to the target deployment project is determined, and the target deployment project is deployed based on the project deployment mode. According to the technical scheme, the problem that the tenant has a special project deployment technology to deploy a corresponding micro-service application on a cloud platform, so that the use threshold of the tenant for BI products is high is solved.

Example two

Fig. 2 is a flowchart of a project deployment method according to a second embodiment of the present invention, optionally, before determining, when a project deployment request of a target tenant is received, a project to be deployed corresponding to the target tenant according to project association information corresponding to the target tenant, the method further includes: inputting project application information corresponding to a target tenant in at least one information editing control on a target display panel; based on project application information, generating a project deployment request corresponding to a project to be deployed, and sending the project deployment request to a project deployment platform.

As shown in fig. 2, the method includes:

s210, inputting project application information corresponding to a target tenant in at least one information editing control on the target display panel.

The target display panel is a display interface for filling project application information of a target tenant. At least one information editing control is included in the target display panel, so that the target tenant fills corresponding project application information in each information editing control. For example, the project application information includes at least one of a user concurrency number, tenant scale information and report related information corresponding to the target tenant.

In practical application, when receiving a project deployment request of a target tenant, before determining a project to be deployed corresponding to the target tenant according to project association information corresponding to the target tenant, the target tenant may input project application information in an information editing control of a target display panel of a device connected to the SAAS platform, so as to generate the project deployment request according to the project application information, and send the project deployment request to the SAAS platform.

S220, generating a project deployment request corresponding to the project to be deployed based on the project application information, and sending the project deployment request to a project deployment platform.

The project deployment platform may be understood as a micro-service application to be deployed by the target tenant according to the project deployment request, for example, the project deployment platform may be an SAAS platform.

S230, when a project deployment request of a target tenant is received, determining a project to be deployed corresponding to the target tenant according to project association information.

S240, determining at least one project configuration file corresponding to the project to be deployed, and packaging the project configuration file associated with the project to be deployed to obtain a target deployment project.

S250, determining a project deployment mode corresponding to the target deployment project, and deploying the target deployment project based on the project deployment mode.

S260, after the target deployment project is successfully deployed, feeding back the project deployment state to the target tenant.

In practical application, in order to ensure that the target deployment project can be normally used by target tenants after the target deployment project is deployed, operation detection needs to be performed on the target deployment project. Specifically, the target deployment item is called according to tenant information of the target tenant, if the target deployment item can be normally called and operated, the deployment is successful, and a deployment success notification is sent to the target tenant, so that the target tenant can use the target deployment item subsequently.

In a specific example, as shown in fig. 3, a target tenant may input project application information corresponding to each information editing control through an information editing control of a target display panel of a device connected to the SAAS platform, so as to generate a project deployment request corresponding to the target tenant according to the project application information, and send the project deployment request to the SAAS platform. For example, the project application information includes information such as a user concurrency number, a report total number, a model total number, a maximum number of single fact tables, and a maximum number of columns of single report corresponding to the target tenant.

After receiving a project deployment request sent by a target tenant, determining at least one project configuration file corresponding to a project to be deployed, and performing file verification on each project deployment file (including identity verification of the target tenant and environment verification of a project deployment environment). Further, after verification is passed, for each item deployment file, deployment (i.e., sequential arrangement) is performed according to the dependency relationship between each item deployment file, so as to obtain a target deployment item, and the target deployment item is deployed on the cloud platform.

Further, when the target deployment project is deployed on the cloud platform, a project deployment mode corresponding to the target deployment project needs to be determined. As shown in fig. 4, taking a transverse deployment mode as an example, a target tenant generates a project deployment request by inputting project application information, sends the project deployment request to the SAAS platform, and performs resident approval (i.e., information authentication) on the target tenant based on the project deployment request. After the authentication is passed, determining a project to be deployed corresponding to a target tenant, and at least one project configuration file contained in the project to be deployed, and storing each project configuration file into a storage space corresponding to the target tenant in a cloud platform through a data connection interface pre-constructed between a pre-SAAS platform and the cloud platform, for example, the target tenant is tenant 1. On the basis, project examples corresponding to the project deployment files are constructed, if a project processing area corresponding to the tenant 1 is a processing space corresponding to the project 1, at least one project deployment file corresponding to the tenant 1 is processed in the project 1 area, project examples PODs corresponding to the project deployment files are constructed, after the project deployment files are subjected to file verification, the project is deployed according to the dependency relationship among the project deployment files, and a target deployment project is obtained and deployed. Furthermore, after the target deployment item is deployed, a deployment success notification is fed back to the target tenant, so that the target tenant can call the target deployment item from the cloud platform for use through an index tool, a report tool, a large screen tool and the like provided by the cloud platform.

In the transverse deployment mode, the same cloud cluster can contain target deployment items corresponding to a plurality of tenants, but in practical application, even if the target deployment items are deployed in the same cloud cluster, the target deployment items are stored respectively, so that the cloud cluster has certain independence. That is, the target deployment item corresponding to tenant 1 and the target deployment item corresponding to tenant 2 are deployed in different storage areas in the same cloud cluster.

Similarly, the target tenant may also select a vertical deployment mode, where the vertical deployment mode is the same as the deployment process of the transverse deployment mode, but the target tenant may independently use one cloud cluster to meet the service requirements of the target tenant for high service processing efficiency and high data security level.

Example III

Fig. 5 is a schematic structural diagram of a project deployment apparatus according to a third embodiment of the present invention. As shown in fig. 5, the apparatus includes: a to-be-deployed project determination module 310, a target deployment project determination module 320, and a deployment mode determination module 330.

The to-be-deployed project determining module 310 is configured to determine, when receiving a project deployment request of a target tenant, a to-be-deployed project corresponding to the target tenant according to project association information; the project association information comprises project configuration information and/or project demand information;

the target deployment project determining module 320 is configured to determine at least one project configuration file corresponding to a project to be deployed, and perform encapsulation processing on the project configuration file associated with the project to be deployed to obtain a target deployment project;

a deployment mode determining module 330, configured to determine a project deployment mode corresponding to the target deployment project, and deploy the target deployment project based on the project deployment mode; the project deployment mode is a transverse deployment mode or a vertical shaft deployment mode.

Optionally, the project deployment apparatus further includes: the information input module is used for inputting project application information corresponding to the target tenant in at least one information editing control on the target display panel before determining a project to be deployed corresponding to the target tenant according to project association information corresponding to the target tenant when receiving a project deployment request of the target tenant; the project application information comprises at least one of user concurrency number, tenant scale information and report related information corresponding to a target tenant;

the request generation module is used for generating a project deployment request corresponding to a project to be deployed based on project application information and sending the project deployment request to the project deployment platform.

Optionally, the to-be-deployed project determining module includes: the target authentication result determining unit is used for carrying out project deployment qualification authentication on the target tenant according to the project deployment request to obtain a target authentication result;

the item to be deployed determining unit is used for acquiring item association information corresponding to the target tenant if the target authentication result is that the authentication is passed, and determining the item to be deployed corresponding to the target tenant according to the item association information.

Optionally, the target authentication result determining unit includes: the identity authentication subunit is used for analyzing the project deployment request to obtain tenant authentication information corresponding to the target tenant, and carrying out identity authentication on the target tenant based on the tenant authentication information to obtain an identity authentication result; and is combined with

The environment authentication subunit is used for authenticating the project deployment environment corresponding to the target tenant according to the equipment performance information corresponding to the target tenant, and obtaining a deployment environment authentication result;

and the target authentication result determining subunit is used for determining a target authentication result corresponding to the target tenant according to the identity authentication result and the deployment environment authentication result.

Optionally, the target deployment item determining module includes: the file determining unit is used for determining at least one project configuration file corresponding to the project to be deployed from the target mapping table based on the project requirements; the project requirement comprises at least one project function, and the target mapping table comprises at least one project function and a project configuration file corresponding to each project function;

the target deployment project determining unit is used for carrying out encapsulation processing on project configuration files associated with projects to be deployed to obtain target deployment projects.

Optionally, the deployment mode determining module includes: the acquisition unit is used for acquiring personalized deployment requirements corresponding to the target tenants;

the deployment mode determining unit is used for determining a project deployment mode corresponding to the target deployment project according to the personalized deployment requirement and deploying the target deployment project based on the project deployment mode.

Optionally, the project deployment device is further configured to feed back a project deployment state to the target tenant after the target deployment project is successfully deployed.

The project deployment device provided by the embodiment of the invention can execute the project deployment method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.

Example IV

Fig. 6 shows a schematic structural diagram of the electronic device 10 of the embodiment of the present invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic equipment may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.

As shown in fig. 6, the electronic device 10 includes at least one processor 11, and a memory, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, etc., communicatively connected to the at least one processor 11, in which the memory stores a computer program executable by the at least one processor, and the processor 11 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from the storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 may also be stored. The processor 11, the ROM 12 and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.

Various components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, etc.; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.

The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 11 performs the various methods and processes described above, such as the project deployment method.

In some embodiments, the project deployment method may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as the storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the project deployment method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the project deployment method in any other suitable manner (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.

A computer program for carrying out the project deployment method of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.

The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.

It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present invention may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solution of the present invention are achieved, and the present invention is not limited herein.

The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.

Claims

1. A method of project deployment, comprising:

2. The method of claim 1, wherein before the determining, at the time of receiving the project deployment request of the target tenant, the project to be deployed corresponding to the target tenant according to project association information corresponding to the target tenant, further comprises:

inputting project application information corresponding to a target tenant in at least one information editing control on a target display panel; the project application information comprises at least one of user concurrency number, tenant scale information and report related information corresponding to the target tenant;

and generating a project deployment request corresponding to the project to be deployed based on the project application information, and sending the project deployment request to a project deployment platform.

3. The method of claim 1, wherein the determining the item to be deployed corresponding to the target tenant according to the item association information corresponding to the target tenant comprises:

performing project deployment qualification authentication on the target tenant according to the project deployment request to obtain a target authentication result;

And if the target authentication result is that the authentication is passed, acquiring item association information corresponding to the target tenant, and determining an item to be deployed corresponding to the target tenant according to the item association information.

4. The method of claim 3, wherein performing project deployment qualification on the project deployment request to obtain a target authentication result comprises:

analyzing the project deployment request to obtain tenant authentication information corresponding to the target tenant, and authenticating the identity of the target tenant based on the tenant authentication information to obtain an identity authentication result; and is combined with

Authenticating the project deployment environment corresponding to the target tenant according to the equipment performance information corresponding to the target tenant, and obtaining a deployment environment authentication result;

and determining a target authentication result corresponding to the target tenant according to the identity authentication result and the deployment environment authentication result.

5. The method of claim 1, wherein the determining at least one project configuration file corresponding to the project to be deployed, and performing encapsulation processing on the project configuration file associated with the project to be deployed, to obtain the target deployment project, includes:

Determining at least one project configuration file corresponding to the project to be deployed from a target mapping table based on the project requirements; the target mapping table comprises at least one project function and project configuration files corresponding to the project functions;

and carrying out encapsulation processing on the project configuration file associated with the project to be deployed to obtain a target deployment project.

6. The method of claim 1, wherein the determining a project deployment pattern corresponding to the target deployment project and deploying the target deployment project based on the project deployment pattern comprises:

acquiring personalized deployment requirements corresponding to the target tenants;

according to the personalized deployment requirements, determining a project deployment mode corresponding to the target deployment project, and deploying the target deployment project based on the project deployment mode.

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

and after the target deployment project is successfully deployed, feeding back the project deployment state to the target tenant.

8. An item deployment apparatus, comprising:

9. An electronic device, the electronic device comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the project deployment method of any one of claims 1-7.

10. A computer readable storage medium storing computer instructions for causing a processor to implement the project deployment method of any one of claims 1-7 when executed.