ChaosBlade is an open and active community that focuses on the exploration and practice of chaos engineering disciplines. Every willing developer is very welcome to build an open source community with us.
Here's the developer guide - on how to commit code, member ladders, related meetings, and more
The ChaosBlade community will hold video conferences every biweekly Friday 7:00pm (starting from 17th June, 2022) to discuss the current status and development plans of ChaosBlade. Participating in the bi-weekly meeting will allow you to understand what ChaosBlade is doing more quickly, which will help you better participate in the open source community, make your suggestions more easily, and clarify the direction of participation and contribution.
Regular Community Meeting:
- Thursday 8:00pm Beijing Time (First Thursday of every month, Starting 17th June, 2022).
Quickly Link:
- Meeting Calendar
- Meeting Link
- Meeting Documentation
- Meeting Recordings(bilibili)
- Meeting Recordings(youtube)
We encourage every interested developer to become a contributor to the community, which usually only takes a few simple steps to participate in the community, such as attending meetings, reporting and occasionally solving problems, or publicly promoting the project. There are also different contributor roles available with an in-depth understanding of the project, and our project team members are happy to help you along the contributor ladder. Learn more about membership requirements and responsibilities in our Community Contributor Ladder Document.
Please read CONTRIBUTING before contributing
If you meet the requirements to become a ChaosBlade member for promotion (Memeber, Reviewer, Maintainer), you can apply through Submit an issue
ChaosBlade is encapsulatd into separate projects according to the scene field, and contributions to any project will be included in the promotion requirements of the contributor ladder.
- chaosblade: Chaos experiment management tool, including commands for creating experiments, destroying experiments, querying experiments, preparing experimental environments, and canceling experimental environments. It is the execution of chaotic experiments. Tools, execution methods include CLI and HTTP. Provides complete commands, experimental scenarios, and scenario parameter descriptions, and the operation is simple and clear.
- chaosblade-spec-go: Chaos experimental model Golang language definition, scenes implemented using Golang language are easy to implement based on this specification.
- chaosblade-exec-os: Implementation of basic resource experimental scenarios.
- chaosblade-exec-docker: Docker container experimental scenario implementation, standardized by calling the Docker API.
- chaosblade-exec-cri: Container experimental scenario implementation, standardized by calling the CRI.
- chaosblade-operator: Kubernetes platform experimental scenario is implemented, chaos experiments are defined by Kubernetes standard CRD method, it is very convenient to use Kubernetes resource operation method To create, update, and delete experimental scenarios, including using kubectl, client-go, etc., and also using the chaosblade cli tool described above.
- chaosblade-exec-jvm: Java application experimental scenario implementation, using Java Agent technology to mount dynamically, without any access, zero-cost use It also supports uninstallation and completely recycles various resources created by the Agent.
- chaosblade-exec-cplus: C ++ application experimental scenario implementation, using GDB technology to implement method and code line level experimental scenario injection.
You can learn about ChaosBlade's development history and future plans through the roadmap
For bug report, questions and discussions please submit GitHub Issues.
You can also contact us via:
- Dingding group (recommended for chinese): 23177705
- Slack group: chaosblade-io
- Gitter room: chaosblade community
- Email: chaosblade.io.01@gmail.com
- Twitter: chaosblade.io