CN115495107A - Version deployment method and device and electronic equipment - Google Patents
Version deployment method and device and electronic equipment Download PDFInfo
- Publication number
- CN115495107A CN115495107A CN202211228234.2A CN202211228234A CN115495107A CN 115495107 A CN115495107 A CN 115495107A CN 202211228234 A CN202211228234 A CN 202211228234A CN 115495107 A CN115495107 A CN 115495107A
- Authority
- CN
- China
- Prior art keywords
- database
- deployment
- program
- sequence
- version
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
Abstract
The application discloses a version deployment method, a version deployment device and electronic equipment, which can be applied to the financial field or other fields. Determining a task change record set based on the service requirement information, performing packaging operation on each database program in the task change record set, acquiring preconfigured deployment node information and access connectivity information between a deployment node and the database node corresponding to each database program, reading the preconfigured dependency relationship and deployment sequence of each database program, dynamically configuring the subprogram parallelism inside each database program, and performing the database program deployment operation in parallel according to the subprogram parallelism inside each database program, the dependency relationship and deployment sequence of each database program through the access connectivity information between the deployment node and the database node corresponding to each database program. Namely, the invention can perform version deployment in parallel when the versions of the heterogeneous database system are deployed, thereby improving the deployment efficiency.
Description
Technical Field
The present invention relates to the field of version deployment, and in particular, to a version deployment method, device and electronic device.
Background
Version deployment refers to a method or step for a software developer to design a test version or a formal version to run on an environment.
A common database version deployment typically requires the following steps: generally, a File Transfer Protocol (FTP) version is sent to a designated database server node, and then a database is accessed to perform installation and deployment.
However, for a composite version of a heterogeneous database system including a plurality of database systems, each database program needs to be packaged separately, and installed and deployed serially and separately, so that the software deployment efficiency is low.
Disclosure of Invention
In view of this, the present invention provides a version deployment method, an apparatus, and an electronic device, so as to solve the problem of low software deployment efficiency of a heterogeneous database system.
In order to solve the technical problem, the invention adopts the following technical scheme:
a version deployment method, comprising:
acquiring service demand information of a heterogeneous database system, and determining a task change record set based on the service demand information;
according to a preset version package strategy, packaging each database program in the task change record set;
acquiring pre-configured deployment node information and access connectivity information between the deployment node and a database node corresponding to each database program;
reading the pre-configured dependency relationship and deployment sequence of each database program;
and dynamically configuring the subprogram parallelism inside each database program, and performing the database program deployment operation in parallel according to the subprogram parallelism inside each database program, the dependency relationship and the deployment sequence of each database program through the deployment node and the access connectivity information between the database nodes corresponding to each database program.
Optionally, reading the pre-configured dependency relationship and deployment order of each database program includes:
reading the pre-configured dependency relationship and deployment sequence among the database programs, and reading the pre-configured dependency relationship and deployment sequence among the subprograms inside the database programs.
Optionally, performing, in parallel, database program deployment operations according to the parallelism of subroutines in each database program, the dependency relationship and the deployment order of each database program, through access connectivity information between the deployment node and the database node corresponding to each database program, includes:
calling a database connection program to perform database connection operation through the access connectivity information between the deployment node and the database node corresponding to each database program;
and calling an installation checking program to check the installation sequence and the program integrity based on the subprogram parallelism inside each database program, the dependency relationship and the deployment sequence of each database program, and calling different database deployment programs to perform different database program deployment operations under the conditions of correct installation sequence and complete program.
Optionally, calling different database deployment programs to perform different database program deployment operations, including:
calling the database deployment program to perform serial deployment according to the directory sequence among the read databases aiming at different databases; the directory order is determined based on the dependency relationship and the deployment order of each database program;
in the same database, calling a database deployment program to perform serial deployment operation according to a default file sequence in each read installation sequence file or a dynamically adjusted file sequence aiming at subprograms with dependency relationship, and calling the database deployment program to perform deployment operation in parallel according to the parallelism of the subprograms based on an arrangement sequence in the installation sequence files aiming at the subprograms without dependency relationship; in the same database, the subprograms with the dependency relationship are classified and placed in different installation sequence files according to the dependency relationship; the subprograms for which no dependency exists will be placed in the same installation order file.
Optionally, according to a preset version group package policy, performing group package operation on each database program in the task change record set, including:
acquiring a preset version group package strategy; the version group packaging policy comprises: different database programs are subjected to a packaging mode of independent storage according to a catalog, a program type and a classification principle of a user;
storing each database program in the task change record set to a corresponding position based on the version group package strategy;
and extracting each database program in the task change record set based on the storage position.
A version deployment apparatus comprising:
the record set determining module is used for acquiring service requirement information of the heterogeneous database system and determining a task change record set based on the service requirement information;
the group packaging module is used for performing group packaging operation on each database program in the task change record set according to a preset version group packaging strategy;
the information acquisition module is used for acquiring preconfigured deployment node information and access connectivity information between the deployment node and the database nodes corresponding to the database programs;
the data reading module is used for reading the pre-configured dependency relationship and deployment sequence of each database program;
and the program deployment module is used for dynamically configuring the subprogram parallelism inside each database program, and performing the database program deployment operation in parallel according to the subprogram parallelism inside each database program, the dependency relationship and the deployment sequence of each database program through the deployment node and the access connectivity information between the database nodes corresponding to each database program.
Optionally, the data reading module is specifically configured to:
reading the pre-configured dependency relationship and deployment sequence among the database programs, and reading the pre-configured dependency relationship and deployment sequence among the subprograms inside the database programs.
Optionally, the program deployment module includes:
the connection operation sub-module is used for calling a database connection program to perform database connection operation through the access connectivity information between the deployment node and the database node corresponding to each database program;
and the program deployment submodule is used for calling an installation checking program to check the installation sequence and the program integrity based on the subprogram parallelism inside each database program, the dependency relationship and the deployment sequence of each database program, and calling different database deployment programs to perform different database program deployment operations under the conditions of correct installation sequence and complete program.
Optionally, the program deployment sub-module is specifically configured to:
calling the database deployment program to perform serial deployment according to the directory sequence among the read databases aiming at different databases; the directory order is determined based on the dependency relationship and the deployment order of each database program;
in the same database, calling a database deployment program to perform serial deployment operation according to a default file sequence or a dynamically adjusted file sequence in each read installation sequence file aiming at the subprogram with the dependency relationship, and calling the database deployment program to perform parallel deployment operation according to the parallelism of the subprograms on the basis of an arrangement sequence in the installation sequence files aiming at the subprogram without the dependency relationship; in the same database, the subprograms with the dependency relationship can be classified and placed in different installation sequence files according to the dependency relationship; the subprograms for which no dependency exists are placed in the same installation order file.
An electronic device, comprising: a memory and a processor;
wherein the memory is used for storing programs;
the processor calls the program and is used to perform one version deployment method described above.
Compared with the prior art, the invention has the following beneficial effects:
the invention provides a version deployment method, a version deployment device and electronic equipment, which are used for acquiring service requirement information of a heterogeneous database system, determining a task change record set based on the service requirement information, performing a packaging operation on each database program in the task change record set according to a preset version packaging strategy, acquiring preconfigured deployment node information and access connectivity information between a deployment node and a database node corresponding to each database program, reading a preconfigured dependency relationship and a preconfigured deployment sequence of each database program, dynamically configuring a subprogram parallelism inside each database program, and performing a database program deployment operation in parallel according to the subprogram parallelism inside each database program, the dependency relationship and the preconfigured deployment sequence of each database program through the access connectivity information between the deployment node and the database node corresponding to each database program. Namely, the invention can perform version deployment in parallel when the version of the heterogeneous database system is deployed, thereby improving the deployment efficiency.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a version deployment method according to an embodiment of the present invention;
fig. 2 is a schematic view of a scenario of a version deployment method according to an embodiment of the present invention;
fig. 3 is a schematic view of a scenario of another version deployment method according to an embodiment of the present invention;
fig. 4 is a schematic view of a scenario of another version deployment method according to an embodiment of the present invention;
fig. 5 is a flowchart of another version deployment method according to an embodiment of the present invention;
fig. 6 is a schematic view of a scenario of another version deployment method according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a version deployment apparatus according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, belong to the protection scope of the present invention.
In order that those skilled in the art will be able to more clearly understand the present invention, certain terms of the present invention will now be explained.
Information security: the method is characterized in that technical and management security protection is adopted for a data processing system, and computer hardware, software and data are protected from being damaged, changed and exposed due to accidental or malicious reasons.
Version deployment: refers to a method or step for a software developer to design a test version or a formal version to run on an environment.
A heterogeneous database system: the method is characterized in that the method is a set of a plurality of related database systems, the sharing and transparent access of data can be realized, the database systems exist before being added into a heterogeneous database system, each component part which has the own database management system and the heterogeneous database has the autonomy of the database system, and each database system still has the own application characteristic, integrity control and safety control while realizing data sharing.
In practical applications, a common database version deployment typically requires the following steps: generally, a File Transfer Protocol (FTP) version is sent to a designated database server node, and then a database is accessed to perform installation and deployment. Such as: ORACLE database accesses the database through sqlplus command, MYSQL database accesses the database through MYSQL command, and GBASE distributed database accesses the database through gccli command.
However, with the development of domestic database products, various types of databases are emerging at present, and have been applied to various different business scenarios, and currently, a software product often includes a plurality of different types of databases. For a composite version of a heterogeneous database system comprising a plurality of database systems, each database program needs to be packaged separately, and is installed and deployed separately and serially, so that the software deployment efficiency is low, and the running error log records are incomplete.
In addition, there are also the following problems:
1) If the version relates to a plurality of heterogeneous database systems, switching back and forth between the heterogeneous database nodes is needed when the version is installed.
2) When the versions have a front-back order and a mutual dependency relationship, human errors are easily made, and the execution order of the program and the installation steps among the modules cannot be automatically controlled.
3) The common installation mode is not high in safety, and an automatic checking and confirming link is lacked before installation.
In order to solve the above problems, the present invention provides a version deployment method, a version deployment device, and an electronic apparatus, which acquire service requirement information of a heterogeneous database system, determine a task change record set based on the service requirement information, perform a package operation on each database program in the task change record set according to a preset version package policy, acquire preconfigured deployment node information and access connectivity information between a deployment node and a database node corresponding to each database program, read a preconfigured dependency relationship and a deployment sequence of each database program, dynamically configure a subprogram parallelism inside each database program, and perform a database program deployment operation in parallel according to the subprogram parallelism inside each database program, the dependency relationship and the deployment sequence of each database program through the access connectivity information between the deployment node and the database node corresponding to each database program. Namely, by the invention, version deployment can be carried out in parallel when the versions of the heterogeneous database system are deployed, and the deployment efficiency is improved.
In addition, the invention has the advantages of one-time safety authentication, one-time coverage check, noninductive node switching and repeated rereeling support, and greatly improves the installation and deployment efficiency of the version. Meanwhile, the parallelism of version deployment and the dependency relationship between versions can be flexibly set according to the difference of each required task.
It should be noted that the version deployment method, the version deployment device, and the electronic device provided by the invention can be used in the financial field or other fields, for example, can be used in a version deployment application scenario in the financial field. The other fields are arbitrary fields other than the financial field. The foregoing is merely an example, and does not limit the application fields of the version deployment method, the version deployment apparatus, and the electronic device provided by the present invention.
On the basis of the foregoing, an embodiment of the present invention provides a version deployment method, and with reference to fig. 1, the version deployment method may include:
s11, acquiring service demand information of the heterogeneous database system, and determining a task change record set based on the service demand information.
In practical application, if there is a need for version deployment, service requirement information of a heterogeneous database system provided by a user is acquired, and the service requirement information mainly needs to perform deployment operation on versions of databases.
After the service requirement information is obtained, the task change record set needs to be determined based on the service requirement information.
In this embodiment, the database programs are introduced by taking the database programs ORACEL, MYSQL, and GBASE as examples. Other database programs are consistent with the Gbase, oracle, mysql database programs, except that the way in which data is accessed is different.
And S12, according to a preset version package strategy, performing package operation on each database program in the task change record set.
In practical application, aiming at the version deployment operation corresponding to the service demand information, overall planning needs to be performed in advance: the overall architecture of the whole software product is known, and the selected data types and the selected data quantities of the software product are planned. And then manually carrying out version management strategy planning, version group strategy planning and version deployment scheme planning, and carrying out separate storage on the heterogeneous database system according to the database by categories, program types and users.
The quality and the badness of the version management strategy directly relate to the stability of the version and the convenience of the version deployment. In the product design process, user authority, types and quantity of heterogeneous databases and program types of each database are fully considered after the product is realized, a set of complete management strategies for developing dev branch streams and master streams which are mutually separated are formulated, and the specification is carried out on access authority, submission and a working directory.
And (3) version group package strategy planning: according to the version management planning strategy, the heterogeneous database programs are separately stored according to the catalog, the program type and the user. Each developer needs to perform operations with corresponding rights under the designated database main directory, program subdirectory and user directory (such as configuring the association relationship between the database program and the corresponding database node). As shown in FIG. 2, the deposit directories of the three databases are controlled by ORACEL, MYSQL, and GBASE. As shown in FIG. 3, the storage directories of bak, data, prc, syn, tab, etc. of different program types are agreed by the program types referred to by GBASE database.
Planning a version deployment scheme: whether the version deployment is convenient and quick is closely related to a version management strategy and a version group strategy. Considering that an application system may include a plurality of different database programs, the deployment order and the access rights of the different database programs may be determined according to different application scenarios. Such as: the method comprises the steps of controlling the user range of a MYSQL database program in mysqluserlist, controlling the user range of a GBASE database program in gbaseqluserlist, and controlling the user range of an ORACLE database program in oracleuserlist. As in FIG. 4, the user scope for each database type is controlled by mysqluerlist, gbaseqluerlist, and oracleuserlist. The deployment sequence of the MYSQL, GBASE and ORACLE database programs can be controlled through the main directory setting.
When the deployment sequence of the three database programs, namely MYSQL, GBASE and ORACLE, is set, the dependency relationship among the three database programs is considered, and the dependency relationship and the deployment sequence of the three database programs, namely MYSQL, GBASE and ORACLE, can also be set at the same time.
When overall planning of software products is performed, the correlation among the version management strategy, the version group packaging strategy and the version deployment scheme needs to be considered. The version management policy needs to consider feasibility and convenience of a version group package and a version deployment scheme, and in short, the version management policy provides product-level version management guidance, the version group package policy is a specific floor of the version management policy, and the version deployment scheme is a specific deployment method or step after the version group package.
In practical application, after determining the version management policy, the version group packaging policy, and the version deployment scheme, if version deployment is required, that is, after acquiring service requirement information and determining a task change record set, packaging each database program in the task change record set according to a preset version group packaging policy.
In practical applications, referring to fig. 2, "performing a group packaging operation on each database program in the task change record set according to a preset version group packaging policy" may include:
and S21, acquiring a preset version group package strategy.
Wherein the version group packaging policy comprises: and different database programs are packaged in a mode of independent storage according to the catalog, the program type and the classification principle of the user.
The specific version group policy can refer to the corresponding description above.
And S22, storing each database program in the task change record set to a corresponding position based on the version group package strategy.
And aiming at each change of the business requirement information, extracting the range of the version according to the change record set to determine the task change record set. And then the extracted database program is stored according to the planned version group package strategy by categories, program types and users.
Then, according to the characteristics of the current task, the user range of the single database version in the userlist can be modified, and the dependence relationship and the execution sequence between the subprograms in the database program and the heterogeneous database program can be controlled according to the orderlist.
And S23, extracting each database program in the task change record set based on the storage position.
After the database programs are stored in different directories, different program types and different users, before version deployment is performed, each database program in the task change record set is extracted based on the storage position of the database program, so that subsequent version deployment is performed conveniently.
S13, acquiring pre-configured deployment node information and access connectivity information between the deployment node and the database nodes corresponding to the database programs.
Specifically, one or a very few deployment nodes storing database versions are selected from a set of application products, and deployment node information is acquired. Then, manually and uniformly configuring the deployment node and the access connectivity (connectivity and access authority) of the database node corresponding to each database program, so that the distributed installation and deployment of the versions can be realized. And the environment variables do not need to be configured independently to each database server node, so that a large amount of environment configuration work is saved.
Such as: through one ETL node, environment variables related to connectivity and access rights of a MYSQL database, an ORACLE database and a GBASE database can be configured at the same time, and the function of accessing multiple database access rights by a single or a very few deployment nodes is realized.
In this embodiment, the access connectivity information between the deployment node and the database node corresponding to each database program is configured to perform subsequent connection of the database nodes.
And S14, reading the pre-configured dependency relationship and deployment sequence of each database program.
Specifically, the dependency relationship and the deployment order between the preconfigured database programs may be read, and the dependency relationship and the deployment order between the preconfigured subroutines inside the database programs may be read. The details can be referred to the corresponding description above.
S15, dynamically configuring the subprogram parallelism inside each database program, and performing database program deployment operation in parallel according to the subprogram parallelism inside each database program, the dependency relationship and the deployment sequence of each database program through the access connectivity information between the deployment node and the database node corresponding to each database program.
Specifically, if there is no dependency relationship between the subroutines in the same database program, the deployment operation of the subroutines that do not have dependency relationship may be performed in parallel. In practical application, the subprogram parallelism in the program deployment process can be dynamically set by using the subprogram set _ parallel, and the version deployment efficiency is improved.
And if the dependency relationship exists among the subprograms, performing serial deployment operation on the subprograms with the dependency relationship.
To facilitate finding subroutines at the time of software deployment. In the same database, the subprograms with dependency relationship can be classified into different installation sequence files according to the dependency relationship (for example, a first installation sequence file and a second installation sequence file, which have dependency relationship therebetween), and each installation sequence file is configured with a default file sequence or a dynamically adjusted file sequence. The subprograms for which no dependency exists will be placed in the same installation order file.
In an implementation manner of the present invention, "performing, in parallel, database program deployment operations according to the parallelism of subroutines in each database program, the dependency relationship and the deployment order of each database program through access connectivity information between the deployment node and the database node corresponding to each database program" may include:
1) And calling a database connection program to perform database connection operation through the access connectivity information between the deployment node and the database node corresponding to each database program.
Specifically, before the deployment of the database program is performed, a database connection operation needs to be performed, and at this time, the database connection operation may be performed using the database connection program set _ linkDb based on the access connectivity information.
2) And calling an installation checking program to check the installation sequence and the program integrity based on the subprogram parallelism inside each database program, the dependency relationship and the deployment sequence of each database program, and calling different database deployment programs to perform different database program deployment operations under the conditions of correct installation sequence and complete program.
In practical application, a main program install.sh can be configured, a connection access mode for accessing three heterogeneous databases, namely MYSQL, ORACLE and GBASE, is integrated through the install.sh, and parallelism control, program integrity check, sequence check and detailed deployment log recording can be performed in the version deployment process. Sh may refer to fig. 6.
Sh of the main program install comprises a plurality of subprograms, which are specifically as follows:
the subprogram set _ parallel is used for setting the subprogram parallelism in the program deployment process, and the version deployment efficiency is improved. The subprogram set _ linkDb is used for setting connection strings for accessing three databases, and the databases are accessed in a mode of designating an IP address, a user and a cipher text display password, so that the functions of one version, one-time authentication, repeated execution, safety and high efficiency can be realized. The subprogram check _ orderlist is used for checking the installation sequence and the program integrity, and when the programs in the subprogram orderlist version do not accord with each other or have omission, the subprogram is automatically prompted. The subroutines of instance _ MYSQL, instance _ oracle and instance _ GBASE are respectively used for deploying the MYSQL database, the MORACLE database and the GBASE database, and the detailed deployment log is completed through printlog.
In practical application, when version deployment is carried out, an install.sh main program is called, a set _ parallel of the subprogram is sequentially scheduled through the main program to set the parallelism of the subprogram, a set _ linkDb sets database connection, a check _ orderlist checks the installation sequence and the program integrity, and an install _ MYSQL, an install _ ORACLE and an install _ ORACLE respectively deploy a MYSQL database program, an ORACLE database program and a GBASE database program. Of course, all detailed logging is done by printlog.
When an install _ MYSQL, an install _ ORACLE and an install _ ORACLE are used for deploying a MYSQL database program, an ORACLE database program and a GBASE database program respectively, the database deployment program is called among different databases to perform serial deployment according to the order of reading directories among the databases.
Wherein the directory order is determined based on the dependency and deployment order of each of the database programs. Specifically, the directory order may be a deployment order or a target order determined based on the deployment order.
In the same database, for the subprogram with the dependency relationship, calling a database deployment program (install _ mysql, install _ oracle or install _ oracle) to perform serial deployment operation according to the default file sequence or the dynamically adjusted file sequence in each read installation sequence file, and for the subprogram without the dependency relationship, calling the database deployment program to perform parallel deployment operation according to the arrangement sequence in the installation sequence file and the subprogram parallelism.
In the same database, the subprograms with the dependency relationship can be classified and placed in different installation sequence files according to the dependency relationship; the subprograms for which no dependency exists will be placed in the same installation order file.
In practical application, serial deployment can be performed according to each installation sequence file, and parallel deployment can be performed in the same installation sequence file.
And in the deployment process, judging whether the program is deployed successfully or not. And if all the programs are successfully deployed, successfully exiting, otherwise, prompting error report or warning, and recording the whole detailed log information, and otherwise, prompting success and exiting until all the programs are successfully deployed.
In this embodiment, service demand information of a heterogeneous database system is acquired, a task change record set is determined based on the service demand information, a package operation is performed on each database program in the task change record set according to a preset version package policy, preconfigured deployment node information and access connectivity information between a deployment node and a database node corresponding to each database program are acquired, a preconfigured dependency relationship and deployment sequence of each database program are read, a subprogram parallelism inside each database program is dynamically configured, and a database program deployment operation is performed in parallel according to the subprogram parallelism inside each database program, the dependency relationship and the deployment sequence of each database program through the access connectivity information between the deployment node and the database node corresponding to each database program. Namely, the invention can perform version deployment in parallel when the version of the heterogeneous database system is deployed, thereby improving the deployment efficiency.
In addition, the invention can be distributed and deployed to different database nodes only by extracting the task change record set according to the planned version group package strategy to form a task package. The complicated version deployment work is normalized, configured and standardized, so that the version deployment work of a diversified heterogeneous database system is well met, and the working efficiency of developers and operation and maintenance persons is greatly improved.
Optionally, on the basis of the embodiment of the version deployment method, another embodiment of the present invention provides a version deployment apparatus, referring to fig. 7, which may include:
the record set determining module 11 is configured to obtain service requirement information of the heterogeneous database system, and determine a task change record set based on the service requirement information;
the packaging module 12 is configured to perform packaging operation on each database program in the task change record set according to a preset version packaging policy;
the information acquisition module 13 is configured to acquire preconfigured deployment node information and access connectivity information between the deployment node and a database node corresponding to each database program;
a data reading module 14, configured to read a dependency relationship and a deployment sequence of each preconfigured database program;
and the program deployment module 15 is configured to dynamically configure the subprogram parallelism inside each database program, and perform the database program deployment operation in parallel according to the subprogram parallelism inside each database program, the dependency relationship and the deployment sequence of each database program, through the access connectivity information between the deployment node and the database node corresponding to each database program.
Further, the data reading module is specifically configured to:
reading the pre-configured dependency relationship and deployment sequence among the database programs, and reading the pre-configured dependency relationship and deployment sequence among the subprograms inside the database programs.
Further, the program deployment module includes:
the connection operation sub-module is used for calling a database connection program to perform database connection operation through the access connectivity information between the deployment node and the database node corresponding to each database program;
and the program deployment submodule is used for calling an installation checking program to check the installation sequence and the program integrity based on the subprogram parallelism inside each database program, the dependency relationship and the deployment sequence of each database program, and calling different database deployment programs to perform different database program deployment operations under the conditions of correct installation sequence and complete program.
Further, the program deployment submodule is specifically configured to:
calling the database deployment program to perform serial deployment according to the directory sequence between the read databases aiming at different databases; the directory order is determined based on the dependency relationship and the deployment order of each database program;
in the same database, calling a database deployment program to perform serial deployment operation according to a default file sequence or a dynamically adjusted file sequence in each read installation sequence file aiming at the subprogram with the dependency relationship, and calling the database deployment program to perform parallel deployment operation according to the parallelism of the subprograms on the basis of an arrangement sequence in the installation sequence files aiming at the subprogram without the dependency relationship; in the same database, the subprograms with the dependency relationship can be classified and placed in different installation sequence files according to the dependency relationship; the subprograms for which no dependency exists will be placed in the same installation order file.
Further, the group package module is specifically configured to:
acquiring a preset version group package strategy; the version group packaging strategy comprises the following steps: different database programs are packaged in a mode of independent storage according to the catalog, the program type and the classification principle of the user;
storing each database program in the task change record set to a corresponding position based on the version group package strategy;
and extracting each database program in the task change record set based on the storage position.
In this embodiment, service demand information of a heterogeneous database system is acquired, a task change record set is determined based on the service demand information, a package operation is performed on each database program in the task change record set according to a preset version package policy, preconfigured deployment node information and access connectivity information between a deployment node and a database node corresponding to each database program are acquired, a preconfigured dependency relationship and deployment sequence of each database program are read, a subprogram parallelism inside each database program is dynamically configured, and a database program deployment operation is performed in parallel according to the subprogram parallelism inside each database program, the dependency relationship and the deployment sequence of each database program through the access connectivity information between the deployment node and the database node corresponding to each database program. Namely, the invention can perform version deployment in parallel when the version of the heterogeneous database system is deployed, thereby improving the deployment efficiency.
In addition, the invention can be distributed and deployed to different database nodes only by extracting the task change record set according to the planned version group package strategy to form a task package. The complicated version deployment work is normalized, configured and standardized, the version deployment work of a diversified heterogeneous database system is well met, and the work efficiency of developers and operation and maintenance persons is greatly improved.
It should be noted that, for the working processes of each module and sub-module in this embodiment, please refer to the corresponding description in the above embodiments, which is not described herein again.
Optionally, on the basis of the embodiments of the method and apparatus for version deployment described above, another embodiment of the present invention provides an electronic device, including: a memory and a processor;
wherein the memory is used for storing programs;
the processor calls the program and is used to perform one version deployment method described above.
In this embodiment, service demand information of a heterogeneous database system is acquired, a task change record set is determined based on the service demand information, a package operation is performed on each database program in the task change record set according to a preset version package policy, preconfigured deployment node information and access connectivity information between a deployment node and a database node corresponding to each database program are acquired, a preconfigured dependency relationship and deployment sequence of each database program are read, a subprogram parallelism inside each database program is dynamically configured, and a database program deployment operation is performed in parallel according to the subprogram parallelism inside each database program, the dependency relationship and the deployment sequence of each database program through the access connectivity information between the deployment node and the database node corresponding to each database program. Namely, by the invention, version deployment can be carried out in parallel when the versions of the heterogeneous database system are deployed, and the deployment efficiency is improved.
In addition, the invention can be distributed and deployed to different database nodes only by extracting the task change record set according to the planned version group package strategy to form a task package. The complicated version deployment work is normalized, configured and standardized, so that the version deployment work of a diversified heterogeneous database system is well met, and the working efficiency of developers and operation and maintenance persons is greatly improved.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended 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 (10)
1. A version deployment method, comprising:
acquiring service demand information of a heterogeneous database system, and determining a task change record set based on the service demand information;
according to a preset version package strategy, packaging each database program in the task change record set;
acquiring pre-configured deployment node information and access connectivity information between the deployment node and a database node corresponding to each database program;
reading the pre-configured dependency relationship and deployment sequence of each database program;
and dynamically configuring the subprogram parallelism inside each database program, and performing the database program deployment operation in parallel according to the subprogram parallelism inside each database program, the dependency relationship and the deployment sequence of each database program through the access connectivity information between the deployment node and the database node corresponding to each database program.
2. The version deployment method according to claim 1, wherein reading the pre-configured dependency relationship and deployment order of each database program comprises:
reading the pre-configured dependency relationship and deployment sequence among the database programs, and reading the pre-configured dependency relationship and deployment sequence among the subprograms inside the database programs.
3. The version deployment method according to claim 2, wherein the database program deployment operation is performed in parallel according to the parallelism of the subprogram in each database program, the dependency relationship of each database program, and the deployment order through the access connectivity information between the deployment node and the database node corresponding to each database program, and includes:
calling a database connection program to perform database connection operation through the access connectivity information between the deployment node and the database node corresponding to each database program;
and calling an installation checking program to check the installation sequence and the program integrity based on the subprogram parallelism inside each database program, the dependency relationship and the deployment sequence of each database program, and calling different database deployment programs to perform different database program deployment operations under the conditions of correct installation sequence and complete program.
4. The version deployment method of claim 3, wherein invoking different database deployment programs for different database program deployment operations comprises:
calling the database deployment program to perform serial deployment according to the directory sequence between the read databases aiming at different databases; the directory order is determined based on the dependency relationship and the deployment order of each database program;
in the same database, calling a database deployment program to perform serial deployment operation according to a default file sequence or a dynamically adjusted file sequence in each read installation sequence file aiming at the subprogram with the dependency relationship, and calling the database deployment program to perform parallel deployment operation according to the parallelism of the subprograms on the basis of an arrangement sequence in the installation sequence files aiming at the subprogram without the dependency relationship; in the same database, the subprograms with the dependency relationship can be classified and placed in different installation sequence files according to the dependency relationship; the subprograms for which no dependency exists will be placed in the same installation order file.
5. The version deployment method according to claim 1, wherein according to a preset version packaging policy, performing a packaging operation on each database program in the task change record set includes:
acquiring a preset version group package strategy; the version group packaging policy comprises: different database programs are packaged in a mode of independent storage according to the catalog, the program type and the classification principle of the user;
storing each database program in the task change record set to a corresponding position based on the version group package strategy;
and extracting each database program in the task change record set based on the storage position.
6. A version deployment apparatus, comprising:
the record set determining module is used for acquiring service requirement information of the heterogeneous database system and determining a task change record set based on the service requirement information;
the package module is used for packaging each database program in the task change record set according to a preset version package strategy;
the information acquisition module is used for acquiring pre-configured deployment node information and access connectivity information between the deployment node and the database nodes corresponding to the database programs;
the data reading module is used for reading the pre-configured dependency relationship and deployment sequence of each database program;
and the program deployment module is used for dynamically configuring the subprogram parallelism inside each database program, and performing the database program deployment operation in parallel according to the subprogram parallelism inside each database program, the dependency relationship and the deployment sequence of each database program through the access connectivity information between the deployment node and the database node corresponding to each database program.
7. The version deployment device according to claim 6, wherein the data reading module is specifically configured to:
reading the pre-configured dependency relationship and deployment sequence among the database programs, and reading the pre-configured dependency relationship and deployment sequence among the subprograms inside the database programs.
8. The version deployment device of claim 7 wherein the program deployment module comprises:
the connection operation sub-module is used for calling a database connection program to perform database connection operation through the access connectivity information between the deployment node and the database node corresponding to each database program;
and the program deployment submodule is used for calling an installation checking program to check the installation sequence and the program integrity based on the subprogram parallelism inside each database program, the dependency relationship and the deployment sequence of each database program, and calling different database deployment programs to perform different database program deployment operations under the conditions of correct installation sequence and complete program.
9. The version deployment device according to claim 8, wherein the procedure deployment submodule is specifically configured to:
calling the database deployment program to perform serial deployment according to the directory sequence among the read databases aiming at different databases; the directory order is determined based on the dependency relationship and the deployment order of each database program;
in the same database, calling a database deployment program to perform serial deployment operation according to a default file sequence or a dynamically adjusted file sequence in each read installation sequence file aiming at the subprogram with the dependency relationship, and calling the database deployment program to perform parallel deployment operation according to the parallelism of the subprograms on the basis of an arrangement sequence in the installation sequence files aiming at the subprogram without the dependency relationship; in the same database, the subprograms with the dependency relationship can be classified and placed in different installation sequence files according to the dependency relationship; the subprograms for which no dependency exists will be placed in the same installation order file.
10. An electronic device, comprising: a memory and a processor;
wherein the memory is used for storing programs;
the processor invokes the program and is operative to perform a version deployment method as claimed in any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211228234.2A CN115495107A (en) | 2022-10-08 | 2022-10-08 | Version deployment method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211228234.2A CN115495107A (en) | 2022-10-08 | 2022-10-08 | Version deployment method and device and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115495107A true CN115495107A (en) | 2022-12-20 |
Family
ID=84474273
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211228234.2A Pending CN115495107A (en) | 2022-10-08 | 2022-10-08 | Version deployment method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115495107A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116737393A (en) * | 2023-08-11 | 2023-09-12 | 腾讯科技（深圳）有限公司 | Resource deployment method and device, storage medium and electronic equipment |
| CN116737393B (en) * | 2023-08-11 | 2024-05-10 | 腾讯科技（深圳）有限公司 | Resource deployment method and device, storage medium and electronic equipment |
-
2022
- 2022-10-08 CN CN202211228234.2A patent/CN115495107A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116737393A (en) * | 2023-08-11 | 2023-09-12 | 腾讯科技（深圳）有限公司 | Resource deployment method and device, storage medium and electronic equipment |
| CN116737393B (en) * | 2023-08-11 | 2024-05-10 | 腾讯科技（深圳）有限公司 | Resource deployment method and device, storage medium and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6202207B1 (en) | Method and a mechanism for synchronized updating of interoperating software | |
| JP3385590B2 (en) | Computer-readable recording medium recording a software update program for use when updating a computer program through a computer network | |
| US7774762B2 (en) | System including run-time software to enable a software application to execute on an incompatible computer platform | |
| US5617533A (en) | System and method for determining whether a software package conforms to packaging rules and requirements | |
| US6493594B1 (en) | System and method for improved software configuration and control management in multi-module systems | |
| US20070240134A1 (en) | Software packaging model supporting multiple entity types | |
| CN106991035A (en) | A kind of Host Supervision System based on micro services framework | |
| CN109032824A (en) | Database method of calibration, device, computer equipment and storage medium | |
| US20100071066A1 (en) | System, method and program product for dynamically performing an audit and security compliance validation in an operating environment | |
| US20080222160A1 (en) | Method and system for providing a program for execution without requiring installation | |
| US20160378458A1 (en) | Method and device for system application installation package, and terminal | |
| US20040088397A1 (en) | System and method for management of software applications | |
| CN113434158B (en) | Custom management method, device, equipment and medium for big data component | |
| US20080066064A1 (en) | Computer readable storage medium for incremental application deployment | |
| CN104573497A (en) | Processing method and device for starting items | |
| US11704114B2 (en) | Data structures for managing configuration versions of cloud-based applications | |
| CN113835713B (en) | Source code packet downloading method, device, computer equipment and storage medium | |
| US11966732B2 (en) | Data structures for managing configuration versions of cloud-based applications | |
| US6966052B1 (en) | Method and apparatus for top-down testing based on end user documentation | |
| US10176011B2 (en) | Automatically generating and executing a service operation implementation for executing a task | |
| CN115495107A (en) | Version deployment method and device and electronic equipment | |
| CN117251247A (en) | Operation and maintenance audit platform deployment method and device, electronic equipment and storage medium | |
| CN115617668A (en) | Compatibility testing method, device and equipment | |
| CN112214502A (en) | User contract deployment method, device, system and storage medium of alliance chain | |
| CN114024735B (en) | Multi-task parallel feature library testing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |