CN117492869A - Visual automatic deployment service system and method - Google Patents
Visual automatic deployment service system and method Download PDFInfo
- Publication number
- CN117492869A CN117492869A CN202311538557.6A CN202311538557A CN117492869A CN 117492869 A CN117492869 A CN 117492869A CN 202311538557 A CN202311538557 A CN 202311538557A CN 117492869 A CN117492869 A CN 117492869A
- Authority
- CN
- China
- Prior art keywords
- service
- mirror image
- deployment
- version
- information
- 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
- 230000000007 visual effect Effects 0.000 title claims abstract description 52
- 238000000034 method Methods 0.000 title claims abstract description 34
- 238000013515 script Methods 0.000 claims abstract description 72
- 238000010276 construction Methods 0.000 claims abstract description 61
- 238000012795 verification Methods 0.000 claims description 20
- 238000004590 computer program Methods 0.000 claims description 12
- 238000010191 image analysis Methods 0.000 claims description 11
- 238000004806 packaging method and process Methods 0.000 claims description 11
- 238000012360 testing method Methods 0.000 claims description 10
- 238000004458 analytical method Methods 0.000 claims description 9
- 238000001514 detection method Methods 0.000 claims description 3
- 230000008569 process Effects 0.000 abstract description 9
- 238000012423 maintenance Methods 0.000 abstract description 6
- 238000011161 development Methods 0.000 abstract description 5
- 230000003252 repetitive effect Effects 0.000 abstract description 3
- 238000012800 visualization Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 210000001503 joint Anatomy 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- 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
- G06F8/63—Image based installation; Cloning; Build to order
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a visual automatic deployment service system and a visual automatic deployment service method, which can acquire project service information and a target deployment server from a service configuration subsystem through the service deployment subsystem, automatically construct and deploy micro-services without other middleware, and have higher deployment efficiency. In addition, the system also provides a visual interface to support the visual operation of service configuration and service deployment. By adopting the combination of the front-end visual page and the background script, the construction and deployment are realized, and the system architecture is simpler. The automatic deployment function greatly improves the development and operation efficiency. Through the predefined process and script, the developer can easily deploy the application program to different environments without manual intervention, and the automatic process not only reduces repetitive work, but also shortens deployment time, reduces labor cost of deployment and maintenance, reduces operation and maintenance pressure, improves stability of the system, and reduces service interruption and loss.
Description
Technical Field
The invention belongs to the technical field of visual systems, and particularly relates to a visual automatic deployment service system and method.
Background
In the technical field of the internet, with the rapid development of IT technology, related services are more and more complex, user demands are more and more diversified, the system is expanded continuously, the technology is mixed, the service deployment workload is increased continuously, and furthermore, the external system is in butt joint much, so that the service deployment demands are difficult to respond rapidly, and the conventional service deployment cannot meet the requirements in the aspects of technology, service, management and the like.
At present, all automatic deployment is basically built based on a micro-service architecture of Kubernetes, and the system is complex, the service deployment mode is complex and the secondary development difficulty is high.
Disclosure of Invention
In view of the shortcomings of the prior art, the application provides a visual automatic deployment service system and a visual automatic deployment service method.
In a first aspect, the present application proposes a visual automatic deployment service system, including a visual console, a service configuration subsystem, and a service deployment subsystem;
the visual operation platform is used for starting version deployment service and providing a visual operation interface for the service configuration subsystem and the service deployment subsystem;
the service configuration subsystem is used for configuring service item information and server information on a management platform page in the visual operation interface, simultaneously configuring automatic deployment micro-service to perform association matching on the service item information and the server information, and obtaining configured item service information and a target deployment server according to a matching result;
The service deployment subsystem is used for acquiring the project service information from the service configuration subsystem, distributing the project service information to the target deployment server under the corresponding deployment environment, selecting the corresponding project service version number according to the project service information, transmitting the configured basic information into a packaging script to carry out mirror image construction, storing the constructed mirror image analysis into a mirror image warehouse, calling a universal release script to pull the corresponding mirror image version from the mirror image warehouse, setting a container starting parameter according to the pulled mirror image version, creating a container, starting and completing service deployment.
In some optional implementations of some embodiments, the service configuration subsystem includes a service item information configuration module, a server information configuration module, and an automatic deployment micro-service configuration module;
the service item information configuration module is used for constructing a service item information table and configuring service item information to be automatically deployed according to the service item information table;
the server information configuration module is used for constructing a server information table and configuring all server basic configuration information related to automatic deployment according to the server information table;
The automatic deployment micro-service configuration module is used for constructing an application service information table and a service version information table, configuring automatic deployment application service according to the application service information table, selecting items in the service item information table, associating the items with a server in the server information table, and storing historical information of the items according to the service version information table so as to perform item deployment rollback operation.
In some alternative implementations of some embodiments, the service deployment subsystem includes a service construction module and a service deployment module;
the service construction module is used for acquiring the project service information from the automatic deployment micro service configuration module, selecting a corresponding project service version number according to the project service information, transmitting the project service information and the project service version number into a package script for mirror construction, and storing the constructed mirror analysis into a mirror warehouse;
the service deployment module is used for acquiring the target deployment server information from the automatic deployment micro-service configuration module, calling a universal release script to pull a corresponding mirror image version from a mirror image warehouse, setting a container starting parameter according to the pulled mirror image version, creating a container, starting and completing service deployment.
In some optional implementations of some embodiments, the service building module includes a mirror building unit and a mirror analysis unit;
the mirror image construction unit is used for acquiring the project service information from the automatic deployment micro service configuration module, selecting a corresponding project service version number according to requirements, and transmitting the project service information and the project service version number into a package script for mirror image construction;
the mirror image analysis unit is used for calling a mirror image script, decompressing the constructed mirror image version to a mirror image catalog, checking whether a mirror image warehouse has a mirror image with the same version, deleting the mirror image if the mirror image warehouse has the mirror image with the same version, deleting the service version information table record at the same time, uploading the mirror image information table record to the mirror image warehouse for storage if the mirror image information table record does not have the mirror image, recording construction information in the service version information table, and recording a check value of the mirror image version.
In some optional implementations of some embodiments, the service deployment module includes a mirror verification unit, a mirror pull unit, a mirror container build unit, and a service deployment test unit;
the mirror image verification unit is used for obtaining a verification value of a mirror image version corresponding to the mirror image warehouse and verifying the integrity of the mirror image according to the verification value;
The mirror image pulling unit is used for calling the universal release script to deploy, and pulling a corresponding mirror image version in the mirror image warehouse according to the name and version information in the deployed project service information;
the mirror image container construction unit is used for creating a container according to the pulled mirror image version and through a dock, and the starting parameters of the container comprise a project service name and a project service version number;
the service deployment test unit is used for executing detection on whether each service is started to run normally or not after the container is started, finally prompting service deployment results, and recording the service deployment results into the database.
In some optional implementations of some embodiments, the visual operations interface includes a service management visualization interface and a service deployment interface;
the service management visual interface is used for loading the service item information configuration module, the server information configuration module and the automatic deployment micro-service configuration module, and carrying out input configuration on the service item information table, the server information table, the application service information table and the service version information table;
the service deployment interface is used for loading the service construction module and the service deployment module and carrying out visual operation on the mirror image construction unit, the mirror image analysis unit, the mirror image verification unit, the mirror image pulling unit, the mirror image container construction unit and the service deployment test unit.
In a second aspect, the present application proposes a method for automatically deploying a service in a visualization manner, including a service configuration step and a service deployment step;
the service configuration step includes:
the method comprises the steps of starting a version deployment service, and configuring service item information and server information in a visual operation platform;
configuring automatic deployment micro-service to perform association matching on the service item information and the server information;
obtaining configured project service information and a target deployment server according to the matching result;
the service deployment step comprises the following steps:
acquiring the project service information, distributing the project service information to the target deployment server under the corresponding deployment environment, selecting the corresponding project service version number according to the project service information, transmitting the project service information, the target deployment server information and the project service version number into a package script for mirror image construction, and storing the constructed mirror image after analysis into a mirror image warehouse; and calling the universal release script to pull the corresponding mirror image version from the mirror image warehouse, setting a container starting parameter according to the pulled mirror image version, creating a container, starting and completing service deployment.
In some optional implementations of some embodiments, the selecting a corresponding item service version number according to the item service information, transferring the item service information, the target deployment server information, and the item service version number into a package script to perform image construction, analyzing the constructed image, and storing the image in an image warehouse includes:
Calling a mirror script, decompressing the constructed mirror version to a mirror catalog, checking whether a mirror warehouse has a mirror with the same version, deleting the mirror, deleting a service version information table record at the same time, uploading the mirror version information table record to the mirror warehouse for storage if the mirror warehouse has the same version mirror, recording construction information in the service version information table, and recording a check value of the mirror version;
and acquiring a check value of the mirror image warehouse corresponding to the mirror image version, and verifying the integrity of the mirror image according to the check value.
In some optional implementations of some embodiments, the invoking the generic issue script pulls a corresponding image version from the image repository, setting the container start parameter according to the pulled image version, including:
mirror image pulling is carried out through a mirror image pulling command provided by a dock, wherein a corresponding mirror image version is pulled in the mirror image warehouse according to the name, the version number and the mirror image ID in the deployment project service information;
providing a container creation command by a docker to create a container, wherein parameters of the container creation include a project service name and a project service version number, the project service name corresponds to the container name, and the project service version number corresponds to the tag version number;
In a third aspect, the present application proposes a computer-readable storage medium, characterized in that: the computer-readable storage medium stores a computer program characterized in that: the computer program being executed by a processor to perform the steps of the method described above.
The invention has the beneficial effects that:
according to the visual automatic deployment service system, project service information and the target deployment server can be acquired from the service configuration subsystem through the service deployment subsystem, micro services are automatically constructed and deployed without other middleware, and the deployment efficiency is higher. In addition, the system also provides a visual interface to support the visual operation of service configuration and service deployment. By adopting the combination of the front-end visual page and the background script, the construction and deployment are realized, and the system architecture is simpler. The automatic deployment function greatly improves the development and operation efficiency. Through predefined flows and scripts, a developer can easily deploy an application to a different environment without manual intervention. The automatic process reduces repetitive work, shortens deployment time, reduces labor cost of deployment and maintenance, reduces operation and maintenance pressure, improves stability of a system, and reduces service interruption and loss.
Drawings
Fig. 1 is a system configuration diagram of the present invention.
FIG. 2 is a first schematic diagram of a service management visualization interface.
FIG. 3 is a second schematic diagram of a service management visualization interface.
FIG. 4 is a third schematic diagram of a service management visualization interface.
FIG. 5 is a fourth schematic diagram of a service management visualization interface.
Fig. 6 is a flow chart of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
In a first aspect, the present application proposes a visual automatic deployment service system, as shown in fig. 1, including a visual console, a service configuration subsystem, and a service deployment subsystem;
the visual operation platform is used for starting version deployment service and providing a visual operation interface for the service configuration subsystem and the service deployment subsystem;
in some optional implementations of some embodiments, the visual operations interface includes a service management visualization interface and a service deployment interface;
The service management visual interface is used for loading the service item information configuration module, the server information configuration module and the automatic deployment micro-service configuration module, and carrying out input configuration on a service item information table, a server information table, an application service information table and a service version information table;
the service deployment interface is used for loading the service construction module and the service deployment module and carrying out visual operation on the mirror image construction unit, the mirror image analysis unit, the mirror image verification unit, the mirror image pulling unit, the mirror image container construction unit and the service deployment test unit.
The service configuration subsystem is used for configuring service item information and server information on a management platform page in the visual operation interface, simultaneously configuring automatic deployment micro-service to perform association matching on the service item information and the server information, and obtaining configured item service information and a target deployment server according to a matching result;
in some optional implementations of some embodiments, the service configuration subsystem includes a service item information configuration module, a server information configuration module, and an automatic deployment micro-service configuration module;
the service item information configuration module is used for constructing a service item information table and configuring service item information to be automatically deployed according to the service item information table;
The server information configuration module is used for constructing a server information table and configuring all server basic configuration information related to automatic deployment according to the server information table;
the automatic deployment micro-service configuration module is used for constructing an application service information table and a service version information table, configuring automatic deployment application service according to the application service information table, selecting items in the service item information table, associating the items with a server in the server information table, and storing historical information of the items according to the service version information table so as to perform item deployment rollback operation.
The method comprises the steps of starting a version deployment service, configuring basic service item information and server information on a management platform page in a service management visual interface, wherein the basic service item information and the basic server information are configured, and the basic service item information and the basic server information comprise: service item information table. The server information table is used for maintaining basic configuration information, and associating service item information and server information during service deployment; the start version deployment service is a pre-step of configuring server information and project service information, firstly configuring service project information and then configuring server information. The step of configuring server information is mainly to configure server information required for deploying micro-service items.
The core field of the service item information table (service management) and its functional comments are shown in table 1 below:
| sequence number | Field English name | Field Chinese name |
| 1 | CODE | Item encoding |
| 2 | NAME | Project name |
| 3 | REMARK | Project description |
| 4 | GIT_ADDR | Version acquisition address |
| 5 | STATUS | Active state |
Table 1: service item information table
The service item information table is mainly used for configuring information of micro service items to be deployed automatically, namely service item information, related information is configured by pages in a service management visual interface, and a version acquisition address can be manually input for configuration, and the service item information table is mainly used for conveniently and uniformly managing through an item association server and a version library tag during service deployment.
The core fields of the server information table and their functional notes are shown in table 2 below:
| sequence number | Field English name | Field Chinese name |
| 1 | IP | IP address |
| 2 | HOSTNAME | Machine name |
| 3 | MAC_ADDR | MAC address |
| 4 | USER_NAME | User name |
| 5 | USER_GROUP | User group |
| 6 | PASSWD | Password code |
| 7 | SERVER_DESC | Server description |
| 8 | PROJECT | Project name |
Table 2 server information table
The server information table mainly configures basic configuration information of all servers related to automatic deployment, as shown in fig. 2-5, related information is configured by pages in a service management visual interface, and the server information table is mainly used for selecting corresponding servers for subsequent application deployment, so that unified management is facilitated.
The application service information table is executed in the step of automatically deploying micro services required by configuration and performing one-key deployment, and is used for storing deployed service information, namely project service information.
The core fields of the application service information table and their functional notes are shown in table 3 below:
| sequence number | Field English name | Field Chinese name |
| 1 | ID | Service ID |
| 2 | CODE | Service coding |
| 3 | NAME | Service name |
| 4 | GROUP_ID | Belonging to the group |
| 5 | MID_DEPLOY_ID | Middleware services |
| 6 | STATUS | Service status |
| 7 | REMARK | Service description |
| 8 | SERVER_ID | Server id |
| 9 | IP | Service address |
| 10 | PORT | Service port |
| 11 | APP_DEPLOY_PATH | Deployment path |
| 12 | VERSION_ID | Current version |
| 13 | VERSION_NO | Version number |
Table 3 application service information table
The application service information table mainly configures automatic deployment application service, when the application service information table is newly added, items in the service item information table are selected, the items are associated with the servers, a plurality of servers are supported, and when the application service information table is constructed, the items are associated with version libraries tag, so that the effect of designating the servers on which the items are deployed is achieved. The related information of the application service information table is configured by page visualization, and is mainly used for full life cycle visualization management of automatic deployment service, and is simple and easy to understand and operate.
The core fields of the service version information table and their functional notes are shown in table 4 below:
| sequence number | Field English name | Field Chinese name |
| 1 | ID | Version ID |
| 2 | SERVICE_CODE | Service coding |
| 3 | RES_NAME | Resource name |
| 4 | RES_TYPE | Resource type: war, tar |
| 5 | GROUP_ID | Belonging group id |
| 6 | VERSION | Version number, for example: YYYYMMDD001 |
| 7 | DEPLOY_TYPE | Publication type |
| 8 | CREATE_TIME | Creation time |
| 9 | VER_DESC | Version description |
| 10 | IMG_VFY | Mirror check value |
| 11 | IMG_ID | Mirror ID |
Table 4 service version information table
The service version information table is mainly used for storing history information after the application project is released, and is convenient for application deployment rollback operation.
The service deployment subsystem is used for acquiring the project service information from the service configuration subsystem, distributing the project service information to the target deployment server under the corresponding deployment environment, selecting the corresponding project service version number according to the project service information, transmitting the configured basic information into a packaging script to carry out mirror image construction, storing the constructed mirror image analysis into a mirror image warehouse, calling a universal release script to pull the corresponding mirror image version from the mirror image warehouse, setting a container starting parameter according to the pulled mirror image version, creating a container, starting and completing service deployment.
The invention discloses a visual automatic deployment service system, which can acquire project service information and a target deployment server from a service configuration subsystem through the service deployment subsystem, automatically construct and deploy micro-services without other middleware, and has higher deployment efficiency. The system also provides a visual interface to support visual operation of service configuration and service deployment.
In some alternative implementations of some embodiments, the service deployment subsystem includes a service construction module and a service deployment module;
the service construction module is used for acquiring the project service information from the automatic deployment micro service configuration module, selecting a corresponding project service version number according to the project service information, transmitting the project service information and the project service version number into a package script for mirror construction, and storing the constructed mirror analysis into a mirror warehouse;
the service deployment module is used for acquiring the target deployment server information from the automatic deployment micro-service configuration module, calling a universal release script to pull a corresponding mirror image version from a mirror image warehouse, setting a container starting parameter according to the pulled mirror image version, creating a container, starting and completing service deployment.
In some optional implementations of some embodiments, the service building module includes a mirror building unit and a mirror analysis unit;
the mirror image construction unit is used for acquiring the project service information from the automatic deployment micro service configuration module, selecting a corresponding project service version number according to requirements, and transmitting the project service information and the project service version number into a package script for mirror image construction;
The mirror image analysis unit is used for calling a mirror image script, decompressing the constructed mirror image version to a mirror image catalog, checking whether a mirror image warehouse has a mirror image with the same version, deleting the mirror image version information table record at the same time if the mirror image warehouse has the mirror image with the same version, uploading the mirror image version information table record to the mirror image warehouse for storage if the mirror image information table record does not have the mirror image version information table record, recording construction information in the mirror image version information table, and recording a check value of the mirror image version;
the service construction mainly comprises mirror image construction and uploading of mirror images to a mirror image warehouse:
the mirror image construction unit mainly involves the following steps:
(1) Selecting a newly added supporting automatic deployment service from a service deployment interface and distributing a target deployment server under a corresponding deployment environment;
(2) Selecting a corresponding deployment version number and an affiliated group according to the system requirement;
(3) And determining a back-tuning background script, transmitting the configured basic information into a package.sh script (package script) and executing construction operation.
The construction process specifically comprises the following steps: firstly, acquiring a source code of a designated release version according to selected project information and version number by using a package.sh script, compiling by a compiling tool, and integrally packaging a product after compiling is successful; the package script is an initiating script for compiling and packaging operation, and is mainly used for executing compiling according to constructed project information, and then packaging after compiling is successful. Firstly, acquiring an address, a version number and a project code by using an incoming version to acquire a project service version to be packaged, and pulling out compiling and packaging instruction steps which are specifically executed after the version is pulled out from configuration files of project services to be deployed; compiling according to the resource type in the service version information to be deployed, and reserving a compiled product in a compressed package form after the compiling is successful;
After the image construction unit compiles successfully, the package script returns an identification of successful execution after the package script is compiled and packaged, and finally returns an identification of the execution result of the compiling step called by the interface.
And the image analysis unit is used for calling an image/sh script (image script), wherein the script is mainly used for processing an initiation script of a dock image operation, the image/sh script is used for carrying out image construction on a packaged product according to information of a dock image file, uploading the image to a private service repository after the image is constructed successfully, checking whether an identical version image exists in the uploading process, directly replacing to decompress a version product generated by compiling and packaging to an image directory if the identical version image exists, checking whether the identical version image exists in the private image repository, and deleting and simultaneously deleting a service version information table record.
The Dockerfile file is generated according to project service information and template files provided by a docker official body and used for constructing a docker mirror image when a project code is established, the project code is uploaded to a mirror image warehouse after construction is completed, a record is written in a service version information table through a mirror image verification unit after the uploading is successful (including recording a current service construction result and using a status field in the service information table to indicate), and meanwhile, a check value (an ID and a Digest value of the mirror image, the Digest is the check value and the ID is a unique identification of the mirror image) of the mirror image is recorded, so that the integrity of the mirror image is verified when the mirror image is used.
In some optional implementations of some embodiments, the service deployment module includes a mirror verification unit, a mirror pull unit, a mirror container build unit, and a service deployment test unit;
the mirror image verification unit is used for obtaining a verification value of a mirror image version corresponding to the mirror image warehouse and verifying the integrity of the mirror image according to the verification value;
the mirror image pulling unit is used for calling the universal release script to deploy, and pulling a corresponding mirror image version in the mirror image warehouse according to the name and version information in the deployed project service information;
the mirror image container construction unit is used for creating a container according to the pulled mirror image version and through a dock, and the starting parameters of the container comprise a project service name and a project service version number;
the service deployment test unit is used for executing detection on whether each service is started to run normally or not after the container is started, finally prompting service deployment results, and recording the service deployment results into the database.
The method comprises the steps that in a service deployment interface operation entering a release stage, a mirror image pulling unit calls a duplicate.sh script to enter a target machine for deployment, wherein the duplicate.sh script mainly uploads an image.sh script to a mirror image in a dock private service warehouse on a server to be deployed to pull down and start a container, and a corresponding version is pulled in a mirror image warehouse according to a deployment item name and version information; pulling the mirrored version includes: pulling a corresponding mirror version in a dock private mirror image warehouse according to the deployment project name, the version number and the mirror ID, and specifically executing a mirror pulling command provided by the dock, wherein an image.sh script represents a mirror script, and a depth.sh script represents a universal release script;
Wherein the step of the image verification unit verifying the image includes: and when the service is deployed, pulling the mirror image according to the service information and the corresponding mirror image ID, then acquiring a digest value of the mirror image from the pulled mirror image, comparing the digest value with the database, and checking if the digest value is consistent with the digest value.
The mirror image container construction unit creates a container and completes starting according to the pulled mirror image version and container starting parameters set in the compiling stage; the creation container is also completed by the command provided by the docker, the parameters of the creation container include the container name, namely the project service name, the tag version number, namely the project service version number, the monitoring port of the container, the deployment path parameter is obtained from the Dockerfile file, the starting container is also completed by the command provided by the docker, and no other parameters are input.
And finally, the service deployment test unit executes each service after the container is started, and confirms whether the starting operation is normal, wherein the container is started successfully or not, an operation. Sh script returns an execution result, finally prompts a deployment result, and records the deployment result into a database, so that service deployment is completed.
When a certain service needs to be started, stopped and unloaded, clicking a corresponding service starting, stopping and unloading operation button on a service deployment page operation, calling an operation.sh script, and executing the starting, stopping and unloading operation by transmitting service names and label information, wherein the operation.sh script represents an operation script.
Therefore, the visual automatic deployment service system provided by the invention realizes construction and deployment by adopting the combination of the front-end visual page and the background script, and the system architecture is simpler. The automatic deployment function greatly improves the development and operation efficiency. Through the predefined process and script, the application program can be easily deployed to different environments without manual intervention, and the automatic process not only reduces repetitive work, but also shortens deployment time, reduces labor cost of deployment and maintenance, reduces operation and maintenance pressure, improves stability of the system, and reduces service interruption and loss.
In a second aspect, the present application proposes a method for automatically deploying a service in a visualization manner, including a service configuration step and a service deployment step, as shown in fig. 6;
the service configuration step includes:
s100: the method comprises the steps of starting a version deployment service, and configuring service item information and server information in a visual operation platform;
s200: configuring automatic deployment micro-service to perform association matching on the service item information and the server information;
s300: obtaining configured project service information and a target deployment server according to the matching result;
The service deployment step comprises the following steps:
t100: acquiring the project service information, distributing the project service information to the target deployment server under the corresponding deployment environment, selecting the corresponding project service version number according to the project service information, transmitting the project service information, the target deployment server information and the project service version number into a package script for mirror image construction, and storing the constructed mirror image after analysis into a mirror image warehouse;
t200: and calling the universal release script to pull the corresponding mirror image version from the mirror image warehouse, setting a container starting parameter according to the pulled mirror image version, creating a container, starting and completing service deployment.
The service deployment step and the association of "configure service item information", "configure server information", "configure auto deployment micro-service" in the service configuration step are: the sequence is dependent, 1-configuration service item information, 2-configuration server information and 3-configuration automatic deployment micro-service are prepared before deployment, and if no service to be deployed is newly added, the previous service configuration step can be skipped, and the service deployment step is directly started from the service deployment step, wherein the service construction T100 and the service deployment T200 in the service deployment step are necessary operations when the release version is deployed each time.
Specifically, service construction mainly includes compiling packaging and uploading images to an image warehouse:
1. compiling the packaging item mainly involves the following steps:
(1) Selecting newly added micro services supporting automatic deployment in a previous management page and distributing a target deployment server in a corresponding deployment environment;
(2) Selecting a corresponding deployment version number and an affiliated group according to the system requirement;
(3) And determining a back-tuning background script, transmitting the configured basic information into a package.sh script to execute compiling operation, and calling the image.sh script to execute constructing operation after compiling is successful.
2. And calling an image-sh script after compiling is successful to decompress a version product generated by compiling and packaging to a mirror image catalog, checking whether a private mirror image warehouse exists in the mirror image of the same version, deleting if the private mirror image warehouse exists, and deleting a database deployment information table record.
3. And constructing the mirror image according to the Dockerfile file defined by the project, uploading the mirror image to a private warehouse after the construction is completed, writing a record in a database deployment information table after the uploading is successful, and simultaneously recording a check value of the mirror image so as to verify the integrity of the mirror image when the mirror image is used.
The service deployment in the service deployment step includes:
And calling the universal release script to pull the corresponding mirror image version from the mirror image warehouse, verifying the mirror image, setting a container starting parameter according to the pulled mirror image version, creating a container, starting and completing service deployment.
Specifically, service deployment:
1. when the operation of the service deployment page is released, a release phase is entered, a depth-sh script is called to enter a target machine for deployment, and a corresponding version is pulled in a mirror image warehouse according to the name of a deployment item and version information;
pulling the mirrored version includes: pulling a corresponding mirror version in a dock private mirror warehouse according to the deployment project name, the version number and the mirror ID, and specifically executing a mirror pulling command provided by the dock;
2. performing image verification according to the pulled image version, wherein the verification step comprises the following steps: and when the service is deployed, pulling the mirror image according to the service information and the corresponding mirror image ID, then acquiring a digest value of the mirror image from the pulled mirror image, comparing the digest value with the database, and checking if the digest value is consistent with the digest value. After verification is passed, creating a container and finishing starting by combining the container starting parameters set in the compiling stage;
the creation of the container is also completed by a command provided by the docker, and parameters of the creation container are the container name, namely the project service name, the tag version number, namely the project service version number, a monitoring port of the container and deployment path parameters are obtained from a dockerfile file.
The boot container is also completed by a command provided by the docker, with no other parameters being entered.
3. After the container is started, executing whether each service is started and runs normally or not, finally prompting a deployment result, and recording the result into a database.
In some optional implementations of some embodiments, the selecting a corresponding item service version number according to the item service information, transferring the item service information, the target deployment server information, and the item service version number into a package script to perform image construction, analyzing the constructed image, and storing the image in an image warehouse includes:
calling a mirror script, decompressing the constructed mirror version to a mirror catalog, checking whether a mirror warehouse has a mirror with the same version, deleting the mirror, deleting a service version information table record at the same time, uploading the mirror version information table record to the mirror warehouse for storage if the mirror warehouse has the same version mirror, recording construction information in the service version information table, and recording a check value of the mirror version;
and acquiring a check value of the mirror image warehouse corresponding to the mirror image version, and verifying the integrity of the mirror image according to the check value.
In some optional implementations of some embodiments, the invoking the generic issue script pulls a corresponding image version from the image repository, setting the container start parameter according to the pulled image version, including:
Mirror image pulling is carried out through a mirror image pulling command provided by a dock, wherein a corresponding mirror image version is pulled in the mirror image warehouse according to the name, the version number and the mirror image ID in the deployment project service information;
providing a container creation command by a docker to create a container, wherein parameters of the container creation include a project service name and a project service version number, the project service name corresponds to the container name, and the project service version number corresponds to the tag version number;
in a third aspect, the present application proposes a computer-readable storage medium, characterized in that: the computer-readable storage medium stores a computer program characterized in that: the computer program being executed by a processor to perform the steps of the method described above.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
In the embodiments provided in the present disclosure, it should be understood that the disclosed apparatus/computer device and method may be implemented in other manners. For example, the apparatus/computer device embodiments described above are merely illustrative, e.g., the division of modules or elements is merely a logical functional division, and there may be additional divisions of actual implementations, multiple elements or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present disclosure may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated modules/units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present disclosure may implement all or part of the flow of the method of the above-described embodiments, or may be implemented by a computer program to instruct related hardware, and the computer program may be stored in a computer readable storage medium, where the computer program, when executed by a processor, may implement the steps of the method embodiments described above. The computer program may comprise computer program code, which may be in source code form, object code form, executable file or in some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the content of the computer readable medium can be appropriately increased or decreased according to the requirements of the jurisdiction's jurisdiction and the patent practice, for example, in some jurisdictions, the computer readable medium does not include electrical carrier signals and telecommunication signals according to the jurisdiction and the patent practice.
The foregoing is merely a preferred embodiment of the present invention, and it should be noted that modifications and improvements made by those skilled in the art without departing from the present technical solution shall be considered as falling within the scope of the claims.
Claims (10)
1. A visual automatic deployment service system, characterized by: comprises a visual operation table,
A service configuration subsystem and a service deployment subsystem;
the visual operation platform is used for starting version deployment service and providing a visual operation interface for the service configuration subsystem and the service deployment subsystem;
the service configuration subsystem is used for configuring service item information and server information on a management platform page in the visual operation interface, simultaneously configuring automatic deployment micro-service to perform association matching on the service item information and the server information, and obtaining configured item service information and a target deployment server according to a matching result;
the service deployment subsystem is used for acquiring the project service information from the service configuration subsystem, distributing the project service information to the target deployment server under the corresponding deployment environment, selecting the corresponding project service version number according to the project service information, transmitting the configured basic information into a packaging script to carry out mirror image construction, storing the constructed mirror image analysis into a mirror image warehouse, calling a universal release script to pull the corresponding mirror image version from the mirror image warehouse, setting a container starting parameter according to the pulled mirror image version, creating a container, starting and completing service deployment.
2. The system according to claim 1, wherein: the service configuration subsystem comprises a service item information configuration module, a server information configuration module and an automatic deployment micro-service configuration module;
the service item information configuration module is used for constructing a service item information table and configuring service item information to be automatically deployed according to the service item information table;
the server information configuration module is used for constructing a server information table and configuring all server basic configuration information related to automatic deployment according to the server information table;
the automatic deployment micro-service configuration module is used for constructing an application service information table and a service version information table, configuring automatic deployment application service according to the application service information table, selecting items in the service item information table, associating the items with a server in the server information table, and storing historical information of the items according to the service version information table so as to perform item deployment rollback operation.
3. The system according to claim 2, wherein: the service deployment subsystem comprises a service construction module and a service deployment module;
The service construction module is used for acquiring the project service information from the automatic deployment micro service configuration module, selecting a corresponding project service version number according to the project service information, transmitting the project service information and the project service version number into a package script for mirror construction, and storing the constructed mirror analysis into a mirror warehouse;
the service deployment module is used for acquiring the target deployment server information from the automatic deployment micro-service configuration module, calling a universal release script to pull a corresponding mirror image version from a mirror image warehouse, setting a container starting parameter according to the pulled mirror image version, creating a container, starting and completing service deployment.
4. A system according to claim 3, characterized in that: the service construction module comprises a mirror image construction unit and a mirror image analysis unit;
the mirror image construction unit is used for acquiring the project service information from the automatic deployment micro service configuration module, selecting a corresponding project service version number according to requirements, and transmitting the project service information and the project service version number into a package script for mirror image construction;
the mirror image analysis unit is used for calling a mirror image script, decompressing the constructed mirror image version to a mirror image catalog, checking whether a mirror image warehouse has a mirror image with the same version, deleting the mirror image if the mirror image warehouse has the mirror image with the same version, deleting the service version information table record at the same time, uploading the mirror image information table record to the mirror image warehouse for storage if the mirror image information table record does not have the mirror image, recording construction information in the service version information table, and recording a check value of the mirror image version.
5. The system according to claim 4, wherein: the service deployment module comprises a mirror image verification unit, a mirror image pulling unit, a mirror image container construction unit and a service deployment test unit;
the mirror image verification unit is used for obtaining a verification value of a mirror image version corresponding to the mirror image warehouse and verifying the integrity of the mirror image according to the verification value;
the mirror image pulling unit is used for calling the universal release script to deploy, and pulling a corresponding mirror image version in the mirror image warehouse according to the name and version information in the deployed project service information;
the mirror image container construction unit is used for creating a container according to the pulled mirror image version and through a dock, and the starting parameters of the container comprise a project service name and a project service version number;
the service deployment test unit is used for executing detection on whether each service is started to run normally or not after the container is started, finally prompting service deployment results, and recording the service deployment results into the database.
6. The system according to claim 5, wherein: the visual operation interface comprises a service management visual interface and a service deployment interface;
the service management visual interface is used for loading the service item information configuration module, the server information configuration module and the automatic deployment micro-service configuration module, and carrying out input configuration on the service item information table, the server information table, the application service information table and the service version information table;
The service deployment interface is used for loading the service construction module and the service deployment module and carrying out visual operation on the mirror image construction unit, the mirror image analysis unit, the mirror image verification unit, the mirror image pulling unit, the mirror image container construction unit and the service deployment test unit.
7. A visual automatic deployment service method is characterized in that: the method comprises a service configuration step and a service deployment step;
the service configuration step includes:
the method comprises the steps of starting a version deployment service, and configuring service item information and server information in a visual operation platform;
configuring automatic deployment micro-service to perform association matching on the service item information and the server information;
obtaining configured project service information and a target deployment server according to the matching result;
the service deployment step comprises the following steps:
acquiring the project service information, distributing the project service information to the target deployment server under the corresponding deployment environment, selecting the corresponding project service version number according to the project service information, transmitting the project service information, the target deployment server information and the project service version number into a package script for mirror image construction, and storing the constructed mirror image after analysis into a mirror image warehouse;
And calling the universal release script to pull the corresponding mirror image version from the mirror image warehouse, setting a container starting parameter according to the pulled mirror image version, creating a container, starting and completing service deployment.
8. The method according to claim 7, wherein: selecting a corresponding project service version number according to the project service information, transmitting the project service information, the target deployment server information and the project service version number into a package script to carry out mirror image construction, and storing the constructed mirror image into a mirror image warehouse after analysis, wherein the method comprises the following steps:
calling a mirror script, decompressing the constructed mirror version to a mirror catalog, checking whether a mirror warehouse has a mirror with the same version, deleting the mirror, deleting a service version information table record at the same time, uploading the mirror version information table record to the mirror warehouse for storage if the mirror warehouse has the same version mirror, recording construction information in the service version information table, and recording a check value of the mirror version;
and acquiring a check value of the mirror image warehouse corresponding to the mirror image version, and verifying the integrity of the mirror image according to the check value.
9. The method according to claim 8, wherein: the method for calling the universal release script to pull the corresponding mirror image version from the mirror image warehouse, and setting the starting parameters of the container according to the pulled mirror image version comprises the following steps:
Mirror image pulling is carried out through a mirror image pulling command provided by a dock, wherein a corresponding mirror image version is pulled in the mirror image warehouse according to the name, the version number and the mirror image ID in the deployment project service information;
and providing a container creation command by a docker to create a container, wherein parameters of the container creation comprise a project service name and a project service version number, the project service name corresponds to the container name, and the project service version number corresponds to the tag version number.
10. A computer-readable storage medium, characterized by: the computer-readable storage medium stores a computer program characterized in that: the computer program implementing the steps of the method according to any of claims 7-9 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311538557.6A CN117492869A (en) | 2023-11-17 | 2023-11-17 | Visual automatic deployment service system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311538557.6A CN117492869A (en) | 2023-11-17 | 2023-11-17 | Visual automatic deployment service system and method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117492869A true CN117492869A (en) | 2024-02-02 |
Family
ID=89674263
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311538557.6A Pending CN117492869A (en) | 2023-11-17 | 2023-11-17 | Visual automatic deployment service system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117492869A (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114398061A (en) * | 2022-01-14 | 2022-04-26 | 中国建设银行股份有限公司 | Publishing method, device, equipment and storage medium |
| CN115756748A (en) * | 2022-11-23 | 2023-03-07 | 美林数据技术股份有限公司 | Cloud construction method based on containerized service management |
-
2023
- 2023-11-17 CN CN202311538557.6A patent/CN117492869A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114398061A (en) * | 2022-01-14 | 2022-04-26 | 中国建设银行股份有限公司 | Publishing method, device, equipment and storage medium |
| CN115756748A (en) * | 2022-11-23 | 2023-03-07 | 美林数据技术股份有限公司 | Cloud construction method based on containerized service management |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8074204B2 (en) | Test automation for business applications | |
| US8108456B2 (en) | Method and apparatus for migrating the system environment on which the applications depend | |
| US20030217308A1 (en) | Distributed test harness model | |
| CN110096424B (en) | Test processing method and device, electronic equipment and storage medium | |
| US9658842B2 (en) | Application runtime expert for deployment of an application on multiple computer systems | |
| US20080244563A1 (en) | Dynamic configuration environment for setup | |
| US20090006493A1 (en) | Method For Enabling Traceability And Recovery From Errors During Migration Of Software Applications | |
| CN112486531A (en) | Method and system for updating equipment application software | |
| CN112084008A (en) | Method for rapidly deploying cloud pipe system based on container technology | |
| CN111462811A (en) | Automatic testing method and device, storage medium and electronic equipment | |
| CN111324365A (en) | Method and equipment for upgrading super-converged system | |
| CN113296795A (en) | Application deployment method, device, equipment, storage medium and program product | |
| CN117290255A (en) | Batch interface performance test method based on Python and Locut frameworks | |
| CN115357258B (en) | Application deployment method and device, storage medium and electronic device | |
| CN112527468A (en) | Alliance chain one-stop type automatic deployment and test method and system | |
| KR101252358B1 (en) | Apparatus and method for testing plc command | |
| CN117492869A (en) | Visual automatic deployment service system and method | |
| JP2007140954A (en) | Operator simulation system and operator simulation method | |
| CN116069354A (en) | Application program upgrading method, device, equipment and storage medium | |
| CN115080076A (en) | Cloud mobile phone software management method | |
| CN114356396A (en) | Service publishing method and device adaptive to multiple services | |
| CN110825645A (en) | Assembly line type full-process automatic testing method | |
| CN114610329B (en) | Solid state disk deployment method and device, readable storage medium and electronic equipment | |
| US20230050723A1 (en) | Device testing arrangement | |
| CN116360800B (en) | Deployment method and device of code branching environment and electronic equipment |
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 |