Resource deployment method, device and equipment, and storage medium

Abstract

Embodiments of the present application disclose a resource deployment method, device and equipment, and a storage medium, a target deployment process is obtained; the target deployment process comprises: each step required to be executed for deploying a target resource in at least two deployment modes, and an association relationship between each step; configuration information input for each step in the target deployment process is received; the configuration information input for each step indicates an execution time of the step, and / or a processing object of the step, and / or a version of a function module corresponding to the step, and / or an execution subject of the step; when a deployment condition is met, based on the target deployment process and the configuration information, a function module corresponding to each step in the target deployment process is called to execute automatic deployment of the target resource in at least two deployment modes. The present application realizes integration of different deployment modes in the same platform through configuration, and reduces complexity of user operation.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more specifically, to a resource deployment method, apparatus, device, and storage medium. Background Technology

[0002] Deploying resources such as applications or databases refers to publishing the resources to a server so that users can download the resources and install or update them.

[0003] For resources to be deployed, the deployment mode may differ depending on the operating system, front-end / back-end, or programming language. This necessitates the use of multiple deployment modes. However, current automated deployment methods can only achieve single-mode deployment. For example, they can only deploy to a specific operating system and not to other operating systems. To deploy to different operating systems, users need to manually select and start different deployment modes. In each deployment mode, users also need to determine and execute the necessary manual operations, making the user's operation quite complex. Summary of the Invention

[0004] The purpose of this application is to provide a resource deployment method, apparatus, device, and storage medium to at least partially overcome the technical problems existing in the prior art.

[0005] To achieve the above objectives, this application provides the following technical solution:

[0006] A resource deployment method, the method comprising:

[0007] Obtain the constructed target deployment process; the target deployment process includes: the steps required to deploy the target resources to be deployed in at least two deployment modes, and the relationships between the steps;

[0008] Receive configuration information input for each step in the target deployment process; the configuration information input for each step indicates the execution time of the step, and / or the processing object of the step, and / or the version of the functional module corresponding to the step, and / or the execution subject of the step;

[0009] When the deployment conditions are met, based on the target deployment process and the configuration information, the functional modules corresponding to each step in the target deployment process are invoked to automatically deploy the target resource using the at least two deployment modes.

[0010] Preferably, in the above method, obtaining the constructed target deployment process includes:

[0011] Select one of several pre-built deployment processes as the target deployment process;

[0012] or,

[0013] Select one deployment process from a set of pre-built deployment processes, edit the selected deployment process, and obtain the target deployment process.

[0014] or,

[0015] Based on the input selection instruction, a target component is selected; the target component represents the various steps required to deploy the target resource in the at least two deployment modes; based on the input relationship establishment instruction, the association relationship between the selected target components is established to obtain the target deployment process.

[0016] Preferably, in the above method, the target deployment process includes:

[0017] The first type of steps and the second type of steps required to deploy the target resources to at least two deployment modes; the first type of steps include at least a version acquisition step; the second type of steps include at least a version installation step and a verification step; wherein...

[0018] The execution time of the first type of step is earlier than the execution time of the second type of step;

[0019] In cases involving multiple Type I steps, the relationships between these Type I steps are that they are executed concurrently.

[0020] The relationship between the second type of steps corresponding to the same deployment mode is that they are executed sequentially; the relationship between the second type of steps corresponding to different deployment modes is that they are executed concurrently.

[0021] The above method, preferably,

[0022] The first type of steps also includes at least one of the following: an environmental resource inspection step, a parameter configuration step, and a data preparation step;

[0023] The second type of steps also includes at least one of the following: a business shutdown step and a resource backup step.

[0024] In the above method, preferably, the configuration information input for each step includes: the execution time of the step and the execution subject of the step;

[0025] The configuration information input for the version acquisition step also includes: the version information of the target resource and the storage address of the target resource;

[0026] The configuration information input for the parameter configuration step, the data preparation step, the service stop step, and the resource backup step also includes: whether the execution subject needs to be checked; if a check is required, the configuration information also includes a check script or check rules.

[0027] The configuration information input for the version installation steps also includes: the deployment address of the target resource, the development language of the target resource, the operating system to which the deployment is targeted, whether a front-end / back-end is involved, and if a front-end / back-end is involved, the type of the front-end / back-end.

[0028] In the above method, preferably, the executing entity includes:

[0029] Script or user; the user is represented by the user's role and the user's unique identifier.

[0030] In the above method, preferably, the configuration information input for each step also includes:

[0031] Does the execution result of this step require manual approval, and will the approval result affect the subsequent process? And / or,

[0032] For any of the second-type steps, if an error occurs in the second-type step, will it trigger a version rollback of the target resource?

[0033] A resource deployment apparatus, the apparatus comprising:

[0034] The process acquisition module is used to acquire the constructed target deployment process; the target deployment process includes: the steps required to deploy the target resources to be deployed in at least two deployment modes, and the relationships between the steps;

[0035] The configuration module is used to receive configuration information input for each step in the target deployment process; the configuration information input for each step indicates the execution time of the step, and / or, the processing object of the step, and / or, the version of the functional module corresponding to the step, and / or, the execution subject of the step.

[0036] The deployment module is used to, when the deployment conditions are met, call the functional modules corresponding to each step in the target deployment process based on the target deployment process and the configuration information, so as to automatically deploy the target resource using the at least two deployment modes.

[0037] An electronic device, comprising a memory and a processor;

[0038] The memory is used to store programs;

[0039] The processor is used to execute the program stored in the memory to implement the various steps of the resource deployment method as described in any of the above.

[0040] A computer-readable storage medium having a program stored thereon, characterized in that, when the program is executed by a processor, it implements the steps of the resource deployment method as described in any of the preceding claims.

[0041] This application provides a resource deployment method, apparatus, device, and storage medium, which obtains a constructed target deployment process. The target deployment process includes: various steps required to deploy the target resource to be deployed in at least two deployment modes, and the relationships between these steps; receiving configuration information input for each step in the target deployment process; the configuration information input for each step indicating the execution time of the step, and / or the processing object of the step, and / or the version of the corresponding functional module, and / or the execution subject of the step; when deployment conditions are met, based on the target deployment process and configuration information, calling the functional modules corresponding to each step in the target deployment process to automatically deploy the target resource in at least two deployment modes. Based on this application, different deployment modes can be integrated on the same platform through configuration, thereby enabling the simultaneous deployment of target resources through different deployment modes. Moreover, the deployment process is based on a workflow, eliminating the need for users to determine whether manual execution is required during deployment, thus reducing the complexity of user operations. Attached Figure Description

[0042] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0043] Figure 1 A flowchart of an implementation of the resource deployment method provided in this application embodiment;

[0044] Figure 2 A schematic diagram of a resource deployment apparatus provided in an embodiment of this application;

[0045] Figure 3 This is a hardware structure block diagram of the electronic device provided in the embodiments of this application.

[0046] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings are used to distinguish similar parts and are not necessarily used to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in a sequence other than that illustrated herein. Detailed Implementation

[0047] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0048] like Figure 1 The diagram shown is a flowchart of one implementation of the resource deployment method provided in this application, which may include:

[0049] Step S101: Obtain the constructed target deployment process; the target deployment process includes: the steps required to deploy the target resources to be deployed in at least two deployment modes, and the relationships between the steps.

[0050] The target resource can be an installation package for a newly developed application or a database; alternatively, the target resource can be an upgrade package for the latest version of an existing application or database.

[0051] In this embodiment of the application, the user (e.g., a version administrator) can determine the deployment mode to be used based on the deployment requirements of the target resource (the operating system to be used, the development language used, whether it involves front-end / back-end, and if it involves front-end / back-end, the type of front-end / back-end). When the target resource needs to be deployed using at least two deployment modes, a target deployment process is obtained. The target deployment process includes the various steps required to deploy the target resource to be deployed using at least two deployment modes, as well as the relationships between the various steps.

[0052] The relationships between the steps include their execution order. Each step in the target deployment process is represented by a component, which users can edit (e.g., add, delete, or configure).

[0053] The deployment process typically differs across deployment modes. This means that some steps may vary between modes. For example, deployment mode 1 might not include step 1, while deployment mode 2 might include it; or both deployment modes might include step 1, but the execution entity for step 1 might differ between them. For steps common to all deployment modes, if the step is identical across all modes, only that step needs to be configured in the target deployment process. If the step differs between at least two deployment modes, at least two versions of that step should be configured in the target deployment process. Subsequent configurations for this step can then be tailored to the specific deployment mode.

[0054] Optionally, users can view the pre-built deployment processes. If the required deployment process (i.e. the target deployment process) exists among the pre-built deployment processes, they can directly select that deployment process as the target deployment process.

[0055] Optionally, if the required deployment process does not exist in the existing deployment processes, you can select the deployment process that is closest to the required one from the existing deployment processes, and then edit the selected deployment process to obtain the target deployment process. Editing the deployment process can include adding or deleting steps, changing the relationships between steps, etc.

[0056] Optionally, if the user believes that there is no deployment process similar to the required one among the existing deployment processes, they can construct the target deployment process themselves. Optionally, the resource deployment device can select target components based on input selection instructions; each target component represents one of the steps required to deploy the target resource using at least two of the aforementioned deployment modes; based on input relationship establishment instructions, the device establishes the relationships between the selected target components to obtain the target deployment process. Specifically, the user can select components (i.e., target components) representing the steps required to deploy the target resource using at least two of the aforementioned deployment modes from the component library as needed. Specifically, for each target component, a drag-and-drop instruction can be obtained as a selection instruction. In response to this selection instruction, the target component is dragged to the deployment process editing area. The user can establish relationships between target components in the deployment process editing area. For example, an arrow can be used to connect two steps with adjacent execution sequences to trigger a relationship establishment instruction. In response to the relationship establishment instruction, a relationship is established between the two target components connected by the arrow, where the arrow points from the first executed step to the next executed step. If one step points to multiple steps, the conditions for executing subsequent steps after one step is completed can also be configured. The deployment process that has already been built can also be built in this way.

[0057] Step S102: Receive configuration information input for each step in the target deployment process; the configuration information input for each step indicates the execution time of the step, and / or, the processing object of the step, and / or, the version information of the functional module corresponding to the step, and / or, the execution subject of the step.

[0058] The configuration information required for different steps may be the same or different. Typically, each step will configure its execution time and execution entity.

[0059] The execution time is set according to the actual business needs. For example, step 1 is to be completed before the 1st of month X, step 2 is to be completed before the 2nd of month X, step 3 is to be completed before the 4th of month X, and so on.

[0060] The objects processed in each step include: the installation package or upgrade package to be processed in the step, and / or other data.

[0061] The version of the functional module corresponding to each step is mainly determined by the deployment scenario. Different deployment scenarios require different deployment modes, and the same functional module will have different versions in different deployment modes to distinguish them. As an example, version-related information for a functional module may include, but is not limited to, the development language of the target resource, the operating system to which the deployment is targeted, whether front-end / back-end is involved, and if so, the type of front-end / back-end.

[0062] The entity executing the steps can be, but is not limited to, either a script or a user. Users can be identified by their roles (e.g., R&D, operations, testing) and unique identifiers (e.g., name, employee ID). In other words, the execution of steps can be automatic or manual, depending on the configuration.

[0063] The configuration information can be configured by the version administrator of the target resource.

[0064] Step S103: When the deployment conditions are met, based on the target deployment process and configuration information, call the functional modules corresponding to each step in the target deployment process to automatically deploy the target resources using at least two of the above deployment modes.

[0065] Optionally, meeting the deployment conditions may include obtaining a configuration completion command. As an example, after the version administrator has completed the configuration for each step, they can trigger the generation of a configuration completion command. After the resource deployment device (also known as the resource deployment platform) receives the configuration completion command, it determines that the deployment conditions are met.

[0066] Optionally, meeting the deployment conditions may include: receiving a configuration completion instruction and reaching a preset deployment time. As an example, the preset deployment time may be configured by version management for the target deployment process. That is, in step S102, in addition to receiving configuration information input for each step, configuration information for the target deployment process may also be received. The configuration information for the target deployment process includes: the execution time of the target deployment process (e.g., execution at midnight on month X).

[0067] Optionally, after configuration, the version administrator can perform a release action (such as clicking a specific button, performing a preset gesture, or speaking specific voice content) to trigger the resource deployment device to generate a configuration completion command.

[0068] The functional modules corresponding to each step are pre-packaged and used to execute the steps corresponding to that module.

[0069] The resource deployment method provided in this application provides a constructed target deployment process. The target deployment process includes: various steps required to deploy the target resource to be deployed in at least two deployment modes, and the relationships between these steps; receiving configuration information input for each step in the target deployment process; the configuration information input for each step indicating the execution time of that step, and / or the processing object of that step, and / or the version of the functional module corresponding to that step, and / or the execution subject of that step; when deployment conditions are met, based on the target deployment process and the configuration information, calling the functional modules corresponding to each step in the target deployment process to automatically deploy the target resource in at least two deployment modes. Based on this application, different deployment modes can be integrated on the same platform through configuration, thereby enabling simultaneous deployment of target resources using different deployment modes. Furthermore, the deployment process is based on a workflow, eliminating the need for users to manually determine whether manual execution is required during deployment, thus reducing the complexity of user operations.

[0070] In an optional embodiment, the target deployment process may specifically include:

[0071] The first and second categories of steps required to deploy the target resource in at least two deployment modes; the first category of steps includes at least a version acquisition step; the second category of steps includes at least a version installation step (i.e., installing the latest version of the target resource) and a verification step (i.e., verifying that the installed latest target resource is correct); wherein,

[0072] The execution time of the first type of step is earlier than the execution time of the second type of step;

[0073] The first type of step can be preparatory work before resource deployment. For example, in addition to the version acquisition step, each deployment method may also include at least one of the following: an environment resource check step, a parameter configuration step, and a data preparation step. The environment resource check may include, but is not limited to: checking information such as the operating system, hardware resources, and software resources of the deployment environment; parameter configuration may include, but is not limited to: configuring parameters such as the runtime of the operating system targeted by the deployment, and the size of the file uploaded to the target server (i.e., the server where the target resource is deployed, whose operating system is the same as the operating system targeted by the deployment); data preparation may include, but is not limited to: preparing preset files, such as whitelists, blacklists, etc. Of course, this is only an example illustrating the optional implementation methods of each step and does not constitute a limitation of this application. The specific implementation method of each step can be set according to actual needs.

[0074] The second type of step can be the work required for resource deployment. For example, in addition to the version installation and verification steps, it can also include at least one of the following: a service shutdown (i.e., controlling the target resource to stop providing services externally) step and a resource backup (i.e., backing up the existing target resource, i.e., the old version of the target resource) step. The service shutdown step is executed earlier than the resource backup step, the resource backup step is executed earlier than the version installation step, and the version installation step is executed earlier than the verification step.

[0075] In cases involving multiple Type I steps, the relationships between these Type I steps are that they are executed concurrently.

[0076] The relationships between the second-category steps within the same deployment mode are sequential execution; that is, one second-category step is executed before the next. The relationships between the second-category steps across different deployment modes are concurrent execution. For example, if different deployment modes both include a stop-service step, then the stop-service steps in both deployment modes can be executed concurrently. Similarly, different steps within different deployment modes can also be executed concurrently; for instance, the stop-service step in the first deployment mode and the backup-resources step in the second deployment mode can be executed concurrently.

[0077] Optionally, for the version acquisition step, the input configuration information may also include: the version information of the target resource (e.g., version number, version name, etc.) and the storage address of the target resource (i.e., the address of the target resource before deployment). As an example, if the target resource is deployed for N (N is an integer greater than 1) operating systems, without involving front-end / back-end, and the development language of the target resource is the same for different operating systems, then the content of the target resource may differ for different operating systems. To distinguish target resources for different operating systems, the target resources can be distinguished by different version numbers, for example, the version numbers of the target resources are 1.1, 1.2, ..., 1.N, etc., where the target resource with version number 1.1 is for operating system 1, the target resource with version number 1.2 is for operating system 2, ..., and the target resource with version number 1.N is for operating system N. The version name of the target resource is the same for different operating systems. Therefore, when a target resource has multiple versions with the same version name, these multiple versions can be obtained through multiple version acquisition steps. Different version acquisition steps will obtain different version information and corresponding storage addresses. In this case, the target deployment process can set up multiple version acquisition steps, each used to acquire one version of the target resource. Optionally, when a target resource has multiple versions with the same version name, these multiple versions can also be obtained through the same version acquisition step. In this case, only one version acquisition step is needed in the target deployment process. However, this same version acquisition step needs to obtain the version information and corresponding storage addresses of the target resource.

[0078] Optionally, for the parameter configuration step, data preparation step, business shutdown step, and resource backup step, the input configuration information may also include: whether the execution entity needs to be checked; if so, the configuration information may also include the check script or check rules.

[0079] If the check is performed manually, the configuration information includes the check rules; if it is performed automatically, the configuration information includes the check script. Checking the executing entity primarily involves checking its permissions to determine if it is a legitimate entity. Specifically,

[0080] If the execution entity of a step is a script, it can be checked by inspecting the script. Specifically, this can include verifying the script's signature of the execution entity; if the verification passes, the execution entity is legitimate; otherwise, it is deemed illegitimate. If the execution entity is a user (e.g., a technical staff member), the check can be performed manually or by a script. Both methods are based on rules, specifically: determining if the user's input identity information (e.g., user role and unique identifier) ​​matches pre-configured user identity information (which can be configured by the version administrator); if they match, the execution entity is legitimate; otherwise, it is illegitimate. Alternatively, it can check if the user's input identity information is in a pre-defined whitelist; if so, the execution entity is legitimate; otherwise, it is illegitimate.

[0081] For the version installation steps, the configuration information input may also include: the deployment address of the target resource (i.e., the address of the target resource after deployment, which may be the same address as the aforementioned storage address of the target resource or a different address), the development language of the target resource, the operating system to be deployed, whether it involves front-end / back-end, and if it involves front-end / back-end, the type of front-end / back-end, etc.

[0082] As an example, if the target resource deployment targets N (N is an integer greater than 1) operating systems, does not involve front-end / back-end, and uses the same development language for the target resource across different operating systems, then the target deployment process can have N version installation steps. The operating systems targeted in each version installation step are different. For example, version installation step 1 corresponds to operating system 1, and the target resource version for operating system 1 is version 1.1. The configuration information can include: deployment address 1 for version 1.1, the development language of the target resource, the operating system targeted for deployment is operating system 1, and it does not involve front-end / back-end; version installation step 2 corresponds to operating system 2, and the target resource version for operating system 2 is version 1.2. The configuration information can include: deployment address 2 for version 1.2, the development language of the target resource, the operating system targeted for deployment is operating system 2, and it does not involve front-end / back-end; ... version installation step N corresponds to operating system N, and the target resource version for operating system N is version 1.N. The configuration information can include: deployment address N for version 1.N, the development language of the target resource, the operating system targeted for deployment is operating system N, and it does not involve front-end / back-end.

[0083] By setting up N version installation steps, if an error occurs in a certain version installation step during resource deployment, only the version installation step with the error in the target deployment process needs to be checked and maintained, without having to check other version installation steps, thus improving maintenance efficiency in multi-deployment mode.

[0084] Similarly, if the shutdown and backup procedures differ under different deployment modes, different shutdown and backup procedures can be set for different deployment modes, which can improve deployment efficiency under multiple deployment modes.

[0085] Furthermore, in this embodiment of the application, the configuration information input for each step may also include:

[0086] Whether manual approval is required for the execution result of this step, and whether the approval result will affect the subsequent process. For each step, whether approval is required for the execution result is set according to actual needs. If leadership approval is required in the actual scenario, then the step can be configured to require approval, and whether the approval result will affect the subsequent process, and if so, what the impact is; otherwise, the step can be configured not to require approval.

[0087] Optionally, in order to achieve online approval, if manual approval of the execution result of this step is required, the configuration information can also include the approver's identification information (such as role and unique identifier), so as to send the approval request to the approver based on the approver's identification information and realize online approval.

[0088] And / or,

[0089] For any second-type step, if an error occurs in that second-type step, should a version rollback of the target resource be triggered?

[0090] As mentioned earlier, the second type of step involves performing the work required for resource deployment. If an error occurs during the business shutdown or version installation process, both the new and old versions of the target resource will become unusable. Therefore, it is necessary to trigger a version rollback of the target resource when errors occur in some steps (such as the business shutdown step, the version installation step, etc.) to ensure that the target resource can continue to provide services to the outside world.

[0091] After configuration, for ease of management, the resource deployment device can store the version information of the target resource to the file server, and store the target deployment process and other configuration information (which can also be called instance information) to the database server.

[0092] When the deployment conditions are met, the resource deployment device obtains the target deployment process and configuration information from the file server and database server, and then, based on the target deployment process and configuration information, calls the functional modules corresponding to each step in the target deployment process to automatically deploy the target resource using at least two of the above deployment modes.

[0093] In an optional embodiment, one implementation of the above-mentioned automatic deployment of at least two deployment modes of the target resource by calling the functional modules corresponding to each step in the target deployment process based on the target deployment process and configuration information can be as follows:

[0094] In the concurrent execution of the target deployment process, each of the first-type steps is executed in the following ways: If the executing entity for each first-type step is a script, the script can be run directly. If the executing entity is a person, the communication identification code of the executing entity can be obtained based on the executing entity information configured for that first-type step (based on role and unique identifier) ​​and the correspondence between the executing entity information and the communication identification code. This communication identification code can be used to send a reminder message to the executing entity so that it can execute the first-type step. If the execution result requires approval, after completing the first-type step, the executing entity can find an approver offline for offline approval. After approval, the approved result can be photographed and uploaded to the resource deployment device. Alternatively, the approval process can be conducted online. Specifically, the resource deployment device or the executing entity can trigger the generation of instruction information indicating the completion of the first type of step in the resource deployment device. After obtaining the instruction information indicating the completion of the first type of step, if the step requires approval, the resource deployment device obtains the approver's communication identification code based on the approver's identification information and sends an approval request to the approver based on the approver's communication identification code so that the approver can approve the execution result of the first type of step. After obtaining the approval result, the resource deployment device waits for the execution results or approval results of other first type of steps.

[0095] After all the first-type steps have been executed, the second-type steps can be executed. For each second-type step corresponding to the same deployment mode, the steps need to be executed sequentially according to the association defined in the target deployment process. However, for each second-type step corresponding to different deployment modes, they can be executed concurrently.

[0096] Similar to the first type of step, for each second type of step, if the executing entity is a script, the script can be run directly. If the executing entity is a person, the communication identification code of the executing entity can be obtained based on the executing entity information configured for that second type of step (based on role and unique identifier) ​​and the correspondence between the executing entity information and the communication identification code. This identification code can be used to send a reminder message to the executing entity so that they can execute the second type of step. If the execution result requires approval, after completing the second type of step, the executing entity can find an approver offline for approval. After approval, the approved result can be photographed and uploaded to the resource deployment device. Alternatively, the approval process can be conducted online. Specifically, the resource deployment device or the executing entity can trigger the generation of instruction information indicating the completion of the second type of step within the resource deployment device. After obtaining the instruction information indicating the completion of the second type of step, if the step requires approval, the resource deployment device obtains the approver's communication identification code based on the approver's identification information and sends an approval request to the approver based on the approver's communication identification code, so that the approver can approve the execution result of the second type of step. After obtaining the approval result, if the approval result is approved, the resource deployment device determines that the next second type of step can be executed; if the approval result is not approved, it can output a prompt message indicating that the approval has not been approved, so that relevant personnel can check and maintain it.

[0097] If an error occurs during the execution of the second type of step, and a version rollback of the target resource is required, restore the target resource to its pre-deployment version.

[0098] Furthermore, if an error occurs during the execution of the first and / or second type of steps, the error information can be saved for relevant personnel to view or maintain.

[0099] Corresponding to the method embodiments, this application also provides a resource deployment device. A schematic diagram of a resource deployment device provided in this application is shown below. Figure 2 As shown, it may include:

[0100] The process obtains module 201, configuration module 202, and deployment module 203; among which,

[0101] The process acquisition module 201 is used to acquire the constructed target deployment process; the target deployment process includes: the steps required to deploy the target resource to be deployed in at least two deployment modes, and the relationship between the steps;

[0102] The configuration module 202 is used to receive configuration information input for each step in the target deployment process; the configuration information input for each step indicates the execution time of the step, and / or, the processing object of the step, and / or, the version of the functional module corresponding to the step, and / or, the execution subject of the step.

[0103] The deployment module 203 is used to, when the deployment conditions are met, call the functional modules corresponding to each step in the target deployment process based on the target deployment process and the configuration information, so as to automatically deploy the target resource in the at least two deployment modes.

[0104] The resource deployment apparatus provided in this application embodiment obtains a constructed target deployment process. The target deployment process includes: various steps required to deploy the target resource to be deployed in at least two deployment modes, and the relationships between these steps; receiving configuration information input for each step in the target deployment process; the configuration information input for each step indicates the execution time of the step, and / or the processing object of the step, and / or the version of the functional module corresponding to the step, and / or the execution subject of the step; when the deployment conditions are met, based on the target deployment process and the configuration information, calling the functional modules corresponding to each step in the target deployment process to automatically deploy the target resource in at least two deployment modes. Based on this application, different deployment modes can be integrated on the same platform through configuration, thereby enabling the simultaneous deployment of target resources through different deployment modes. Moreover, the deployment process is based on a workflow, eliminating the need for users to determine whether manual execution is required during the deployment process, thus reducing the complexity of user operations.

[0105] In an optional embodiment, the process obtaining module 201 is used to:

[0106] Select one of several pre-built deployment processes as the target deployment process;

[0107] or,

[0108] Select one deployment process from a set of pre-built deployment processes, edit the selected deployment process, and obtain the target deployment process.

[0109] or,

[0110] Based on the input selection instruction, a target component is selected; the target component represents the various steps required to deploy the target resource in the at least two deployment modes; based on the input relationship establishment instruction, the association relationship between the selected target components is established to obtain the target deployment process.

[0111] In an optional embodiment, the target deployment process includes:

[0112] The first type of steps and the second type of steps required to deploy the target resources to at least two deployment modes; the first type of steps include at least a version acquisition step; the second type of steps include at least a version installation step and a verification step; wherein...

[0113] The execution time of the first type of step is earlier than the execution time of the second type of step;

[0114] In cases involving multiple Type I steps, the relationships between these Type I steps are that they are executed concurrently.

[0115] The relationship between the second type of steps corresponding to the same deployment mode is that they are executed sequentially; the relationship between the second type of steps corresponding to different deployment modes is that they are executed concurrently.

[0116] In an optional embodiment,

[0117] The first type of steps also includes at least one of the following: an environmental resource inspection step, a parameter configuration step, and a data preparation step;

[0118] The second type of steps also includes at least one of the following: a business shutdown step and a resource backup step.

[0119] In an optional embodiment, the configuration information input for each step includes: the execution time of the step and the execution subject of the step;

[0120] The configuration information input for the version acquisition step also includes: the version information of the target resource and the storage address of the target resource;

[0121] The configuration information input for the parameter configuration step, the data preparation step, the service stop step, and the resource backup step also includes: whether the execution subject needs to be checked; if a check is required, the configuration information also includes a check script or check rules.

[0122] The configuration information input for the version installation steps also includes: the deployment address of the target resource, the development language of the target resource, the operating system to which the deployment is targeted, whether a front-end / back-end is involved, and if a front-end / back-end is involved, the type of the front-end / back-end.

[0123] In an optional embodiment, the execution entity includes:

[0124] Script or user; the user is represented by the user's role and the user's unique identifier.

[0125] In an optional embodiment, the configuration information input for each step further includes:

[0126] Does the execution result of this step require manual approval, and will the approval result affect the subsequent process? And / or,

[0127] For any of the second-type steps, if an error occurs in the second-type step, will it trigger a version rollback of the target resource?

[0128] The resource deployment apparatus provided in this application embodiment can be applied to electronic devices, such as cloud platforms, servers, and server clusters. Optionally, Figure 3 A hardware structure block diagram of the electronic device provided in an embodiment of this application is shown, with reference to... Figure 3 The hardware structure of the electronic device may include:

[0129] At least one processor 1, at least one communication interface 2, at least one memory 3, and at least one communication bus 4.

[0130] In this embodiment of the application, the number of processor 1, communication interface 2, memory 3, and communication bus 4 is at least one, and processor 1, communication interface 2, and memory 3 communicate with each other through communication bus 4;

[0131] Processor 1 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention.

[0132] Memory 3 may include high-speed RAM, and may also include non-volatile memory, such as at least one disk storage device;

[0133] The memory stores a program, which the processor can call. The program is used for:

[0134] Obtain the constructed target deployment process; the target deployment process includes: the steps required to deploy the target resources to be deployed in at least two deployment modes, and the relationships between the steps;

[0135] Receive configuration information input for each step in the target deployment process; the configuration information input for each step indicates the execution time of the step, and / or the processing object of the step, and / or the version of the functional module corresponding to the step, and / or the execution subject of the step;

[0136] When the deployment conditions are met, based on the target deployment process and the configuration information, the functional modules corresponding to each step in the target deployment process are invoked to automatically deploy the target resource using the at least two deployment modes.

[0137] Optionally, the refined and extended functions of the program can be found in the description above.

[0138] This application embodiment also provides a storage medium that can store a program suitable for execution by a processor, the program being used for:

[0139] Obtain the constructed target deployment process; the target deployment process includes: the steps required to deploy the target resources to be deployed in at least two deployment modes, and the relationships between the steps;

[0140] Receive configuration information input for each step in the target deployment process; the configuration information input for each step indicates the execution time of the step, and / or the processing object of the step, and / or the version of the functional module corresponding to the step, and / or the execution subject of the step;

[0141] When the deployment conditions are met, based on the target deployment process and the configuration information, the functional modules corresponding to each step in the target deployment process are invoked to automatically deploy the target resource using the at least two deployment modes.

[0142] Optionally, the refined and extended functions of the program can be found in the description above.

[0143] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0144] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. Furthermore, the couplings or direct couplings or communication connections shown or discussed may be indirect couplings or communication connections through interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0145] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0146] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0147] It should be understood that in the embodiments of this application, the claims, various embodiments, and features can be combined with each other to solve the aforementioned technical problems.

[0148] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0149] The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A resource deployment method, characterized in that, The method includes: Obtain the constructed target deployment process; the target deployment process includes: the steps required to deploy the target resources to be deployed in at least two deployment modes, and the relationships between the steps; Receive configuration information input for each step in the target deployment process; the configuration information input for each step indicates the execution time of the step, and / or the processing object of the step, and / or the version of the functional module corresponding to the step, and / or the execution subject of the step; When the deployment conditions are met, based on the target deployment process and the configuration information, the functional modules corresponding to each step in the target deployment process are invoked to automatically deploy the target resource using the at least two deployment modes.

2. The method according to claim 1, characterized in that, The process of obtaining the constructed target deployment includes: Select one of several pre-built deployment processes as the target deployment process; or, Select one deployment process from a set of pre-built deployment processes, edit the selected deployment process, and obtain the target deployment process. or, Based on the input selection instruction, a target component is selected; the target component represents the various steps required to deploy the target resource in the at least two deployment modes; based on the input relationship establishment instruction, the association relationship between the selected target components is established to obtain the target deployment process.

3. The method according to claim 1, characterized in that, The target deployment process includes: The first type of steps and the second type of steps required to deploy the target resources to at least two deployment modes; the first type of steps include at least a version acquisition step; the second type of steps include at least a version installation step and a verification step; wherein... The execution time of the first type of step is earlier than the execution time of the second type of step; In cases involving multiple Type I steps, the relationships between these Type I steps are that they are executed concurrently. The relationship between the second type of steps corresponding to the same deployment mode is that they are executed sequentially; the relationship between the second type of steps corresponding to different deployment modes is that they are executed concurrently.

4. The method according to claim 3, characterized in that, The first type of steps also includes at least one of the following: an environmental resource inspection step, a parameter configuration step, and a data preparation step; The second type of steps also includes at least one of the following: a business shutdown step and a resource backup step.

5. The method according to claim 4, characterized in that, The configuration information input for each step includes: the execution time of the step and the execution entity of the step; The configuration information input for the version acquisition step also includes: the version information of the target resource and the storage address of the target resource; The configuration information input for the parameter configuration step, the data preparation step, the service stop step, and the resource backup step also includes: whether the execution subject needs to be checked; if a check is required, the configuration information also includes a check script or check rules. The configuration information input for the version installation steps also includes: the deployment address of the target resource, the development language of the target resource, the operating system to which the deployment is targeted, whether a front-end / back-end is involved, and if a front-end / back-end is involved, the type of the front-end / back-end.

6. The method according to claim 5, characterized in that, The executing entities include: Script or user; the user is represented by the user's role and the user's unique identifier.

7. The method according to claim 5, characterized in that, The configuration information entered for each step also includes: Does the execution result of this step require manual approval, and will the approval result affect the subsequent process? And / or, For any of the second-type steps, if an error occurs in the second-type step, will it trigger a version rollback of the target resource? 8. A resource deployment device, characterized in that, The device includes: The process acquisition module is used to acquire the constructed target deployment process; the target deployment process includes: the steps required to deploy the target resources to be deployed in at least two deployment modes, and the relationships between the steps; The configuration module is used to receive configuration information input for each step in the target deployment process; the configuration information input for each step indicates the execution time of the step, and / or, the processing object of the step, and / or, the version of the functional module corresponding to the step, and / or, the execution subject of the step. The deployment module is used to, when the deployment conditions are met, call the functional modules corresponding to each step in the target deployment process based on the target deployment process and the configuration information, so as to automatically deploy the target resource using the at least two deployment modes.

9. An electronic device, characterized in that, Including memory and processor; The memory is used to store programs; The processor is used to execute the program stored in the memory to implement the various steps of the resource deployment method as described in any one of claims 1-7.

10. A computer-readable storage medium having a program stored thereon, characterized in that, When the program is executed by the processor, it implements the various steps of the resource deployment method as described in any one of claims 1-7.

Images