Directory
First, the operating system configuration standards 1
1 1 x84_64 operating system Centos7.5
2, Basic Configuration 1 host
security and optimization 3. The operating system (one-click optimization script configuration) 1
Second, automated deployment of standard 2
1.gitlab standard 2
2.jenkins standard 2
Third, monitoring standard 2
1. cloud service monitoring 2
2.zabbix monitoring 3
3 3 other
four 3 log building services
V. deployment Guide standard 3
1 introduces the basic requirements 3
2, 3 deployment Guide requirements
- Documents directory level 4
First, the operating system configuration standards
1. x84_64 operating system Centos7.5
2, the host Basic Configuration
2.1 Host Configuration
hostname standard project last name _ function _ip
standardization partition / boot 200M ~ 1G / swap 1G ~ 8G / All remaining
2.2 project application directory / home / cloud; basic services path: / App /
2.3 data backup and log directory
format: / data / backup / date / / data / logs / date /
all basic services (nginx, tomcat, etc.) and application services are The date was cut by the day.
2.4 operating system permissions
to all online linux server to disable the root user login server, prohibit root users to start all applications; all applications started with the cloud user; start basic services to the appropriate services to start, such as nginx nginx started with the user.
2.5 Network planning
all servers are only within the network address, network address had to go through NAT address translation; intranet server even after the adoption of the fortress Making the connection; fort address setting a single network segment, and do a separate security group restrictions.
3. Safety and optimize the operating system (one-click optimization script configuration)
3.1 software upgrade version
yum install yum EPEL-Release && Update
3.2 modify configuration files
/etc/systcl.conf;/etc/secrity/limits.conf;sshd_config etc.
3.3 pairs specific weighting process file
/etc/sudoers;/etc/passwd；/etc/shadow
Second, automated deployment standards
required system: jenkins, gitlab, jenkins plug
1.gitlab standard
1.1 git commit code branches: Develop, the Test, UNAT, Master
1.2 git format new projects: Project Name / / ..... can reference according to the project to divide large modules (develop custom)
2.jenkins standard
2.1 jenkins deploy two sets of sub-environment, develop, test, unat, set; another set of master line, can only be maintained by the operation and maintenance management.
2,2 jenkins building is divided into different projects related project developers can only see their own projects.
2.3 jenkins using master-slave mode, slave task to build each project environment a host, master just jenkins "brain."
2.4 jenkins need parametric build process, i.e. pull codes; such constructs may be selected in which the branch (develop, test, etc.).
2.5 jenkins build subsequent processes, such as packaging, publishing test referred pipeline plug-in to manage. pipeline documents are handed over to gitlab management.
Third, the standard monitoring
surveillance system: cloud service providers bring their own monitoring, zabbix
1, cloud service monitoring
1.1 to define different monitoring templates based on cloud account environment (testing, development, online)
1.2 divided according to business, related to a designated service developers and operation and maintenance personnel to obtain the alarm mail. Including testing, development of online services and resources.
1.3 Alarm media: SMS, email, nails and other alarm mode.
2.zabbix monitoring
2.1 grouped according to project into the server.
2,2 All projects use a unified host monitoring templates, create a service template, specify the appropriate service templates with different hosts. Services include monitoring ports templates and processes.
2.3 Monitoring Project interface, including whether the available rate, packet loss, timeout monitoring.
2.4 Other monitoring, such as nginx certificate monitoring.
2.5 mysql service, redis, mongo and other basic services to monitor specific parameters.
3. Other
had according to the relevant monitoring software to monitor the application log monitoring services up from the log level to achieve timely monitoring of business conditions.
Fourth, build log service
ELK building implementation, establish a centralized log collection system, the logs on all nodes in the unified collection, management, access, improve the efficiency of fault location.
Fifth, the standard manual deployment
1, the basic description required
1.1 Features and official document links
1.2 application scenarios
1.3 basic deployment
2. Deployment Guide requires
1,1 Environment Introduction (host name, ip, port, topology map), table rendering.
1.2 configuration files and notes, in order to reflect the screenshots and text.
1.3 lists service deployment location, start and stop the service content in the first few lines of the document.
1.4 document must desensitization (password replacement, replace the host name, replace the instance name, etc.).
-
Documents directory level
a,
1
1.1
1.2
2
2.1Example:
a docker installation
1, docker version
2, docker mounting step
2.1 install dependencies
2.2 yum source configured
2.3 Installation program docker
2.4 was added to start the service startup docker