How ZhiYun Job Platform Revolutionizes Automated Operations

As cloud computing matures, enterprises from startups to government and finance are migrating to the cloud and demand robust automated operation capabilities, emphasizing efficiency, security, and auditability. The ZhiYun Job Platform was created to meet these urgent automation needs.

Getting Started – Tool Construction

Daily operations involve many repetitive tasks that require opening multiple terminals to run scripts. The story of an operations engineer, Xiao H, illustrates the pitfalls of manual processes: copying commands across terminals can lead to costly mistakes, such as accidentally restarting the wrong service.

Problems identified from a cost and security perspective:

Manual execution on machines is inefficient, lacks audit trails, and poses high risk.

Tool and script management is chaotic and hard to integrate.

Redundant development of similar tools across teams.

High learning curve; users must understand entire scripts before use.

To address these issues, the platform treats each tool as the smallest operational unit, encapsulating common tasks with metadata (e.g., execution environment, timeout) similar to functions in programming languages.

Tool details

Each tool includes comprehensive information, configurable parameters, and the actual code. By wrapping scripts as tools, users no longer need deep script knowledge; they can rely on tool descriptions and parameter definitions.

The platform provides a simple UI where users specify input parameters and target machines; the system handles distribution, execution, and result collection.

Advanced – Orchestration Integration

After tool encapsulation, users required the ability to define execution order and dependencies between tools. The platform introduces orchestration templates that allow:

Sequential execution of defined tools.

Using outputs from previous tools as inputs for subsequent ones.

Packaging execution order and parameter mappings into reusable templates.

Exposing only necessary parameters for manual input.

An orchestration template consists of basic information (name, description), user‑defined parameters, and ordered steps. Each step maps to a tool, can retrieve parameters from prior results, and may require user confirmation before proceeding.

Extension – Integrating More Module APIs

Complex workflows often need to query other systems, such as retrieving a machine list from the CMDB based on a module ID. Previously, users had to write raw HTTP calls, which were cumbersome, hard to reuse, and insecure.

The platform now wraps external APIs (e.g., CMDBService) as built‑in operations, allowing users to invoke them with simple method calls, reducing development effort and improving security.

Summary and Outlook

The Job Platform has evolved from basic task automation to full orchestration and API integration, continuously enhancing automated operation capabilities. Future development will focus on tighter integration with other automation modules, positioning the platform as a central scheduling hub for enterprise‑wide operational efficiency.