1. Project Overview

OPEN-C3To solve CI/CD/CO.

In the entire operation process, it can assist in improving operational efficiency and achieving continuous operation (CO) effects. OPEN-C3 is born to solve CI/CD/CO.

OPEN-C3 can be used as a CI/CD platform. After installation and deployment, it can be used independently. According to the description in the document, it can easily complete the installation of experience version, single-machine version, and cluster version. At the same time, it can be given a specified interface by the company, and in the case of not modifying any OPEN-C3 code, it can be connected to the company's login system, service tree, permission system, and OA approval system.

2. Open Source License

Using GPL-2.0 open-source protocol

3. Screenshots

Console interface

The front-end has two styles that can be selected, and can be switched in the connector.

Default Style

Yunyun Style

Task Platform

If only the task platform function is needed, it can be switched through the connector.

4. Feature Overview

CICD System/Publish System/Task Platform/Monitoring System/Cloud Monitoring/Fault Self-Recovery/K8S Cluster Management/CMDB/Public Cloud Resource Management/Ticket System

Features

• Efficient file transfer protocol, which is particularly effective in the face of a large number of servers.
• Powerful network proxy method, which can easily manage servers distributed in various regions around the world.
• High availability, the system does not have a core single point, easy to maintain, easy to deploy, and can be horizontally expanded.
• Independence, the system can be used independently, and can be connected to the login system, service tree OA approval system according to the company environment.
• Plug-in, which can easily add plug-ins to meet the different requirements of process composition.
• Support for job stacking, support for calling pipelines in pipelines, and calling jobs in jobs to meet more complex composition requirements.

Core Function

• Quickly execute scripts: quickly select machines for command operations.
• Quick file distribution: quickly select machines for file synchronization.
• Virtual terminal: provides a web shell for a single machine and batch operations for multiple machines.
• File sending: provides the function of uploading local files to remote servers and downloading files from remote servers to local machines.
• Job tasks: supports defining a job, and the job can use plug-ins: execute commands, synchronize files, and approve.
• Scheduled tasks: can set a job to execute at a specified time.
• Group jobs: can configure a machine to perform batch operations, batch calling jobs.
• Pipeline: completes a CI/CD process.
• Reports: provides Git code submission reports, and provides release rollback reports.

Advanced Functions

• Container publishing: publishes container services through OPEN-C3.
• Host and container hybrid publishing: publishes host services and container services simultaneously in a pipeline.
• Resource composition: composes resources through Terraform.
• Light application: OPEN-C3's light application function.
• Simultaneous publishing of application groups: how to publish/rollback multiple modules in a single release.
• Demonstration Square: a service tree node that everyone has permission to access.
• Private node: each person's private node.
• CDN refresh: refreshes CDNs from various CDN vendors.

5. Tech Stack

Architecture

Connector

OPEN-C3 system has built-in login management, user management, permission management, service tree, and approval functions. However, considering that these functions need to be integrated with the company's underlying infrastructure in the enterprise environment, OPEN-C3 has centralized these functions in the connector module. This can be modified to point to external systems through configuration.

Input

The following actions can control the OPEN-C3 system. They affect the running logic of OPEN-C3.

• Manual operation
• Users can perform operations on the console, configure pipelines, jobs, and scheduled tasks, and can batch-operate servers and batch-transfer files, etc.
• User approval operations, approval operations can be completed through mobile terminals, and the results of approval (approval or rejection) will affect the OPEN-C3 process.
• Code repository trigger
• Code changes can trigger build operations, and build operations can be linked to release.
• SVN: Triggered by tagging.
• GIT: Supports tag and webhook triggering (webhook can trigger a build every time a git push operation is performed).
• FILE: Supports triggering builds by uploading files.
• Fault self-recovery system trigger
• If there is a fault self-recovery system, it can be connected to OPEN-C3.
• File Upload
• Upload files can be uploaded not only on the console page but also through commands. It can be configured to trigger a certain process after file upload, achieving the effect of uploading and publishing immediately.
• Scheduled Tasks
• Can configure a job flow to be executed at a specified time in the console.

Output

• Generate program package
• After successful build, the compressed package will be saved in the OPEN-C3 file system, waiting for release.
• Upload image to image repository
• If it is a container release, it can be configured to build a container image and upload it to the image repository.
• Control server
• Batch-operate servers, and some built-in commands are used for publishing programs.
• Batch-synchronize files, file synchronization can cross regions, and file transfer supports multiple-to-multiple transfer.
• Control other services through built-in plugins
• Can easily add plugins, and terraform (can be used for resource orchestration) and kubectl (can be used for publishing Kubernetes applications) are built-in.

Development

If you want to develop OPEN-C3, you need to prepare a development environment, install a single-machine version, and develop on this basis.

OPEN-C3's backend is written in Perl, and the code can be modified directly without compilation.

If modified is the plugin part, the effect is direct, otherwise, you need to restart the service through the following command.

/data/open-c3/open-c3.sh restart