Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ChaosBlade incubation proposal #1278

Closed
wants to merge 1 commit into from

Conversation

MandssS
Copy link
Contributor

@MandssS MandssS commented Mar 22, 2024

This PR contains a proposal for ChaosBlade to be accepted into the CNCF Incubation stage.

ChaosBlade is a versatile Chaos Engineering platform that orchestrates chaos experiments on Kubernetes and Host environments.

By covering comprehensive fault injection methods in container, Pod, Node, network, file system, middleware, cloud vendor infrastructure, running application process, and even the kernel, ChaosBlade aims at providing a neutral, universal Chaos Engineering platform that enables cloud-native applications to be as resilient as they should be.

Signed-off-by: caimingxia <mingshao.cmx@alibaba-inc.com>
@caofujiang
Copy link

ChaosBlade是国内混沌工程领域的很优秀的工具,一个深度使用者的强烈推荐

@sshnull
Copy link

sshnull commented Jul 9, 2024

chaosblade支持多个场景的故障注入,便于开发、维护和扩展 ,chaosblade老炮推荐

@KeKe-Li
Copy link

KeKe-Li commented Jul 9, 2024

chaosblade 开源越来越棒!

@binbin0325
Copy link

ChaosBlade has developed very well in the field of cloud-native chaos engineering with rich functions. It looks forward to entering cncf incubation

@aspnetdb
Copy link

aspnetdb commented Jul 9, 2024

ChaosBlade is an open-source chaos engineering platform. It provides a comprehensive set of tools and frameworks to help developers and operations teams inject faults, monitor, analyze, and recover in distributed systems, ultimately enhancing system resilience and stability.

@houlong2015
Copy link

chaosblade can perfectly applyed to kubernet or physical injection,and with the chaosblade-box,we can easily do any experiments , very good!

@peterZhang000
Copy link

The ChaosBlade tool contains chaos experiments in many fields. Chaos experiments in different fields are implemented by different projects. gogoooooooo🚀

@ralf0131
Copy link

Hi @angellk,
I think the chaosblade project belongs to the tag-observability. Maybe the label should be tag-observability?

The project has presented the latest update with tag-observablity including @alolita on July 10. See the meeting notes for more information.

@alolita
Copy link
Member

alolita commented Jul 10, 2024 via email

@spencercjh
Copy link

spencercjh commented Jul 10, 2024

Chaosblade is one of China's earliest open-source projects in chaos engineering. Compared to similar projects like ChaosMesh or ChaosMeta, it has the largest user base and enterprise users in China. While its success is undeniable, the Chaosblade community seems to lack activities. There are several problems in the community now.

Associated data is here:

https://chaosblade.devstats.cncf.io/d/12/issues-opened-closed-by-repository-group?orgId=1&var-period=d&var-repogroup_name=All
https://chaosblade.devstats.cncf.io/d/11/issues-age-by-repository-group?orgId=1&var-period=d&var-repogroup_name=All&var-prio_name=All&from=now-1y&to=now
https://chaosblade.devstats.cncf.io/d/10/pr-time-to-engagement?orgId=1&from=now-1y&to=now&var-period=d7&var-repogroup_name=All
https://chaosblade.devstats.cncf.io/d/19/open-pr-age-by-repository-group?orgId=1&from=now-1y&to=now

  • Black box discussion of issues, no public explanation of major changes: fix: Temporarily disable server mode. chaosblade-io/chaosblade#987 which leads to many question isseus like 1.7.3版本里面blade server的命令是删除了吗 chaosblade-io/chaosblade#1007 and there are still no response from maintainers now. Most of the valid and up-to-date information is in DingTalk groups but is not updated to the associated GitHub Issues or project docs.
    image
  • Lack of maintenance staff to maintain the program. chaosblade is a mature and stable project, but that doesn't mean it doesn't need to be maintained. Especially chaosblade-operator, whose maintenance has almost come to a standstill.
  • It seems that chaosblade is a closed org with no intention of developing new committers or maintainers from outside.

I know that the above problems are not only problems of chaosblade, but also common problems of most Chinese open-source projects, but I hope CNCF can do something about it. Let's build a better chaosblade and CNCF together!

@MandssS
Copy link
Contributor Author

MandssS commented Jul 11, 2024

Chaosblade is one of China's earliest open-source projects in chaos engineering. Compared to similar projects like ChaosMesh or ChaosMeta, it has the largest user base and enterprise users in China. While its success is undeniable, the Chaosblade community seems to lack activities. There are several problems in the community now.

Associated data is here:

https://chaosblade.devstats.cncf.io/d/12/issues-opened-closed-by-repository-group?orgId=1&var-period=d&var-repogroup_name=All
https://chaosblade.devstats.cncf.io/d/11/issues-age-by-repository-group?orgId=1&var-period=d&var-repogroup_name=All&var-prio_name=All&from=now-1y&to=now
https://chaosblade.devstats.cncf.io/d/10/pr-time-to-engagement?orgId=1&from=now-1y&to=now&var-period=d7&var-repogroup_name=All
https://chaosblade.devstats.cncf.io/d/19/open-pr-age-by-repository-group?orgId=1&from=now-1y&to=now

  • Black box discussion of issues, no public explanation of major changes: fix: Temporarily disable server mode. chaosblade-io/chaosblade#987 which leads to many question isseus like 1.7.3版本里面blade server的命令是删除了吗 chaosblade-io/chaosblade#1007 and there are still no response from maintainers now. Most of the valid and up-to-date information is in DingTalk groups but is not updated to the associated GitHub Issues or project docs.
    image
  • Lack of maintenance staff to maintain the program. chaosblade is a mature and stable project, but that doesn't mean it doesn't need to be maintained. Especially chaosblade-operator, whose maintenance has almost come to a standstill.
  • It seems that chaosblade is a closed org with no intention of developing new committers or maintainers from outside.

I know that the above problems are not only problems of chaosblade, but also common problems of most Chinese open-source projects, but I hope CNCF can do something about it. Let's build a better chaosblade and CNCF together!

Thank you for your suggestion and advice on chaosblade. From your reply, I can feel your deep feelings for chaosblade, which makes me very touched. Regarding your question, I will reply here:
● The issue mentioned was not handled in a timely manner. Due to the recent busy development of new features and insufficient energy allocation, the issue reply was indeed not timely enough. But for important pr, they are basically merged in the new version.
● The server mode is deleted here for security reasons. An issue will be released later to explain the specific reasons.
● chaosblade is maintained by maintainers and community, and chaosblade-operator has also been released recently.
● Chaosblade has a complete contributor ladder, and recently a new maintainer has been successfully promoted. You are also very welcome to submit promotion proposals.

We will invest more time in issue management in the future. You are also very welcome to provide valuable comments in subsequent regular meetings. Of course, you are also welcome to join the maintenance work of chaosblade. Let's build a better chaosblade and CNCF together!

@mrbobbytables mrbobbytables added the tag-observability things related to SIG-Observability label Sep 3, 2024
@angellk
Copy link
Contributor

angellk commented Oct 28, 2024

Moved application with new template to same place in the queue as this one. Closing to de-dupe. Thank you @MandssS !

@angellk angellk closed this Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
incubation tag-app-delivery tag-observability things related to SIG-Observability
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.