Automated Integrated deployment udeployer one-key batch installation deployment and udeployer one-key

Automated Integrated deployment udeployer one-key batch installation deployment and udeployer one-key
Build a project through jenkins; version Control; udployer automated integration; ucop business inspection to achieve efficient and highly available automation system. Version 1.0:

Separation of logic and businessTo perfectly separate the logic from the business, implement unified shell script development for the business, and be called by the python framework in a unified manner.

Concurrent multi-thread deploymentNo matter how many servers and services are there, and initiate threads to update, deploy, and start them at the same time.

Increase the DIY level of list rule filesTo reduce the code modification caused by new services and implement automated integration and deployment of scan config.

Version 2.0:

Version Control, Associate Jenkins to automate version submission for testing

Backup and rollbackTo implement real-time rollback.

SQL script updateTo execute common scripts and incremental scripts.

Version 3.0:

MP multi-site automated Integration

 

1Introduction

Automated integration and unified installation and upgrade, applicable to multi-resource distribution/separate deployment projects.
The company has many projects and deployment requires a lot of manpower and time, and many human errors may occur during the manual deployment process. through automated integration, it can be automatically deployed on different projects and multiple servers with less manpower, reducing human problems and saving deployment time. In the later stage of automated integration, automated testing will be integrated into the entire system to achieve the goal from deployment to testing.

1.1 Purpose

Continuous integration and packaging, automated integration and Update Services, real-time monitoring of server status and automated testing

Range: 1.2

The scope of use of this project includes:

-Multi-resource-based development projects

-Wide range of project-related services

-Service Multi-dependency

1.3 readers

Readers of this requirement specification or other stakeholders include the platform Director, product manager, Project Director, Project Manager, developer, tester, O & M personnel, and user experience designer.

2. Overall project description

2.1 Overall system function framework

Before performing the unified installation, first back up the previous project and extract the configuration files involved, then check the SVN update version, and then perform the unified installation.

One-click unified installation and presentation of service processes and related versions after execution.

2.2 System Function list

No.	Module	Function	Description
Udeployer _ T001	Autotest	Public component platform	Working component for automated integration and Testing
Udeployer _ T002	Bin	Execute automated integration Master Directory	Execute Automated Integrated master program and support multi-thread execution
Udeployer _ T003	Bak		Directory used to store configuration files to be replaced by each program
Udeployer _ T004	Common	Store execution components (kill process, START process, etc)	Stores independent execution Components
Udeployer _ T005	Config	Service configuration file. The master program parses this file to read the configuration.	The configuration file is in. ini format.
Udeployer _ T006	FileStore		Directory used to store the downloaded war package
Udeployer _ T007	PID	Save the obtained PID output file
Udeployer _ T008	Logs	Unified log output and log format for all operation inputs. Input friendly prompts
Udeployer _ T009		Complete Monitoring Service and Robust Automatic Integration

 

3. Function Description

3.1 obtain the configuration file

It is very easy to install and deploy the system in a unified manner. You only need to provide the service list based on the list template. The service list is as follows:

Glossary:

1 #-*-coding: UTF-8-*-2 3 [HTTPSERVER] 4 # IP address deployed in the war package name svn address tomcat directory test version 5 SERVER = prior preemptive version 192.168.20.19/home/prior 1.3.2.1

 

Run the script. The config directory automatically generates the configuration file to be modified. The configuration file is generated after filtering. Therefore, no matter how many files need to be configured for a service, only one file is generated here, easy to modify and manage. The Configuration File follows the configuration file of the previous version. If no configuration item is added in the new version, skip this step.

3.2 Automation System

Build a project through jenkins; version Control; udployer automated integration; ucop business inspection to achieve efficient and highly available automation system.

Advantages of automated integration: