Quick Start Guide for DevOps Environment Construction

The DevOps environment is composed of multiple tools or tool chains, and generally includes the following parts according to the delivery process:

Coding: code writing, review, continuous integration
Build: version control, code merge, build status
Test: automated test and test report
Packaging: Binary warehouse, Docker image warehouse
Release: Change management, automatic release
Configuration: Infrastructure configuration and management
Monitoring: performance monitoring, user behavior feedback
The following lists the tools and environments that I use in my daily work. For specific installation and configuration methods, please refer to the official manual or search engine.

RouterOS

RouterOS (ROS for short) is a Linux-based soft routing system. I generally use the following functions of ROS:

VLAN-can distinguish the company's internal development, testing, and office networks to ensure the availability of the network in the R & D environment
L2TP / IPSEC VPN-Everyone can access the company network at any time, convenient for debugging outside
DNS——Access all internal services of the company through the domain name, no need to remember the IP address
DHCP-used with PXE network installation environment
VMware ESXi

Virtualization weapon, not much introduction. Just add enough memory to the machine.

FreeNAS

Reliable storage is the foundation of other services. I personally prefer to use independent SAN / NAS devices instead of local storage of the server.

There are two main reasons:

ESXi only supports high-end hardware RAID cards with high cost
Need to plan the needs of each machine from the beginning, cannot share
Using FreeNAS can provide iSCSI Target for ESXi, and at the same time can provide everyone with an independent Samba space-shared access through Windows.

Another important reason for choosing FreeNAS is ZFS.

OpenLDAP

OpenLDAP is used to store the organizational structure tree and corresponding permissions. GitLab, MediaWiki, and FreeNAS all support LDAP-based user authentication.

GitLab

GitLab provides Git repository, Code Review (through Merger Request), Issue Tracker and other functions.

I think GitLab is more practical than traditional tools such as Git Server and Visual SVN. Everyone has their own space management rights.

For example, many small projects or individual projects that have not yet been established require version control but are not required to be hosted on the department's warehouse. With GitLab, you can play on your own acre and three points.

GitLab-CI

The continuous integration tools provided by GitLab are generally used to compile, build and run automated tests.

Simple and enough, yml syntax is also very simple.

Docker Registry

Docker image warehouse, the packages packaged from GitLab-CI will be pushed directly into the registry.

MediaWiki

GitLab has a wiki function for each project, but we need a knowledge base independent of the project, so we chose MediaWiki.

PXE / Mirrors

Since my work is based on Linux, I often have to install different distributions. It is very necessary to deploy a PXE installation service within the company.

The PXE environment is generally implemented by a combination of three services: DHCP, TFTP, and HTTP. DHCP is provided by ROS.

ShadowSocks

Equipped for special national conditions, rent an overseas VPS, and then deploy ShadowSocks, then deploy Privoxy to convert socks5 to http proxy.