Architect's way of learning

Operation and maintenance automation development:

1. Standardization of operation and maintenance

Physical device level:

       1) Server labeling, equipment responsible person, equipment procurement details, and equipment placement standards.

        2) Network division, remote control card, network card port

        3) The server model, hard disk and memory are unified. According to business classification.

        4) Asset naming specification, numbering specification, type specification

        5) Monitoring standards,

Operating system level:

        1) OS version

         2) System initialization (DNS, NTP, kernel parameter tuning, rsyslog, hostname specification)

          3) Basic Agent equipment (Zabbix Agent, Logstash Agent, Saltstack minion)

           4) System monitoring standards (CPU, memory, hard disk, network, process)

Application service level:

            1) Web server selection (Apache, Nginx)

             2) Process startup user, port monitoring specification, log collection specification (access log, error log, operation log)

             3) Configuration management (configuration file specification, script specification)

              4) Architecture specification (Nginx+Keepalived, LVS+Keepalived, etc.)

               5) Deployment specification (location, package naming, etc.)

Operation and maintenance operation level:

                1) Computer room inspection process (cycle, content, repair reporting process)

                2) Business deployment process (test first, then production. Rollback)

                3) Fault handling process (emergency handling, fault escalation, major fault management)

                 4) Work log standard (how to write a work log)

                 5) Business online process (1. Project initiation 2. System installation 3. Nginx deployment 4. Domain name resolution 5. Testing 6. Monitoring 7. Backup)

                  6) Business offline process (who initiates and how data is processed.)

                   7) Operation and maintenance security specifications (password complexity, change cycle, VPN usage specifications, service login specifications)

 Goal: Document

Operation and maintenance knowledge system:

https://www.unixhot.com/page/ops

A line of operation and maintenance learning and development:

1. Build the service (deploy and run)

2. Make good use of services (monitoring, management, optimization)

3. Automation (services are directly related and work together)

4. Product design (how to design a monitoring system)

The core competitiveness of cloud computing is operation and maintenance!

System architect (partial management): network system database development cloud computing automation operation and maintenance management service management project management test business

focus on a field

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=325693167&siteId=291194637