How to Build a Scalable Operations Automation System from Standards to Deployment

Introduction

This article introduces the design and implementation of our operations automation system, emphasizing that standardization, specification, and process formalization are prerequisite steps for successful automation.

1. Operations Standardization, Specification, and Process

To achieve automation, an organization must first establish standardized, regulated, and procedural operations; otherwise, automation efforts will falter.

1.1 Understanding Operations Automation and Standardization

Different enterprises have varying interpretations, but the common goal is to make work more efficient, intelligent, rule‑based, and predictable. Two extreme attitudes are illustrated:

Extreme Type 1: Rejects processes and automation, treating them as hype, leading to chaotic, error‑prone work.

Extreme Type 2: Over‑emphasizes rigid processes, causing delays and inflexibility despite thorough documentation.

while (true): {
    research;
    meeting;
    gather_requirements;
    submit_approval;
}

The key insight is that standards and automation should serve as best‑practice enablers, not as ends in themselves.

1.2 Relationship Between Automation and Standardization

Automation cannot be deployed without underlying standards; inconsistencies in hostnames, IP schemes, or software versions inevitably break tools such as SaltStack, Zabbix, or log collectors. Proper standards reduce manual errors and prevent operations staff from being blamed for avoidable incidents.

2. Operations Automation System Design

2.1 Automation Requirements

Growing business scale makes IT environments increasingly complex, demanding scientific, standardized management that delivers more work with fewer resources.

2.2 System Overview Design

The platform integrates existing operation tools into a unified management console, covering three dimensions: IT operation processes, monitoring platform integration, and automation.

IT operation processes: asset management, knowledge‑base, security, incident, daily task management.

Monitoring integration: alarm, log, performance, reporting.

Automation: application, configuration, program execution management.

2.3 Program Function Diagram

2.4 Database Model Design

2.5 Work‑Order Process Design

Based on ITIL principles, the incident work‑order flow is illustrated.

2.6 System Architecture Diagram

3. Platform Instance Introduction

Menu hierarchy demonstrates the modules described above.

Global search allows keyword‑based fuzzy queries across all database tables, returning results to the web UI.

Performance charts are rendered with ECharts; backend serialization uses Django REST framework.

Asset management provides CRUD operations for hardware configuration, supporting bulk import from Excel via Django CBV.

Knowledge base built on a customized WordPress instance for sharing documentation.

Event module follows ITIL flow, automatically triggering processes based on event severity.

Integration layer unifies disparate monitoring tools into a single portal.

Log monitoring and security auditing use ELK stack and rsyslog/logstash shipper.

Network traffic monitoring is customized via Cacti.

Website link status monitoring tracks critical URLs.

Service status monitoring collects data from client agents and reports to the server in JSON format.

Automated deployment leverages KVM, SaltStack, and custom scripts for batch IP usage queries, client distribution, and system configuration.