-
Notifications
You must be signed in to change notification settings - Fork 636
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
Dragonfly Incubating Stage Review #276
Conversation
RFC @cncf/toc |
What was the progress of Dragonfly being rewritten in golang from Java? It looks like it’s mostly done? dragonflyoss/dragonfly#346 |
Yes, We have finished that in 0.4.0 version. Currently Dragonfly is totally written in Golang. Now latest version of dragonfly is 0.4.3. We will release 0.5.x to add more essential features from the community. And in about October, we will launch the GA version of 1.0.0. |
Signed-off-by: Allen Sun <[email protected]>
cf628b4
to
364742d
Compare
We using dragonfly to distribute large AI resource files to cluster nodes. We hope that dragonfly enters the incubation stage. I am from iflytek. Dragonfly help us manage the resource files and Practice cloud natives to benefit us a lot |
Here is a link for Dragonfly Due Diligence Draft: https://docs.google.com/document/d/1FauIs9BXRCioUCYPdO9gfy1uiPw9ESKRu0s4bgd5Dgw/edit# |
The CNCF SIG Storage has completed a review of Dragonfly. The project presented to us August 28th 2019: https://www.youtube.com/watch?v=Sl7ZDt7rx4M We had some questions which were captured by the project here: https://github.com/dragonflyoss/community/blob/master/meetings/cncf-sig-storage-feedback.md I completed a basic test deployment in a test environment covering basic functionality and failover scenarios and, in general, Dragonfly appears to be simple to deploy and a focus on low overhead. Failover and operational maintenance seemed straightforward and operations like image pulls could complete even while some nodes where in a failed state. We had some further queries that were captured by the team and detailed responses are included here: The CNCF SIG Storage raised this on the agenda for 12th February and recommend move to incubation. |
Thanks @amye can you kick off the vote after DD is confirmed, I think we are almost there |
Waiting on a TOC member to sponsor, will coordinate with.
…On Wed, Feb 12, 2020, 1:28 PM Chris Aniszczyk ***@***.***> wrote:
Thanks @amye <https://github.com/amye> can you kick off the vote tomorrow?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#276?email_source=notifications&email_token=AAA2FGKGZTJQ235DAHOQ533RCRSZPA5CNFSM4IMOIIW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELSONZY#issuecomment-585426663>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA2FGIPJGW3VL3HX7K5NNDRCRSZPANCNFSM4IMOIIWQ>
.
|
@caniszczyk Sig Storage and @chira001 made a very detailed review for Dragonfly. While I am afraid that we still need a TOC sponsor and Due Diligence which is requested in the cncf-toc channel https://lists.cncf.io/g/cncf-toc/topic/67574577#3930. Here is a draft of Dragonfly's due diligence: https://docs.google.com/document/d/1FauIs9BXRCioUCYPdO9gfy1uiPw9ESKRu0s4bgd5Dgw/edit?usp=sharing /cc @amye |
I’m happy to do it (sponsor and run the due diligence.)
|
@sheng-liang any update with the due diligence? |
@allencloud I'm working through the documents. I will need your help connecting me with a few users and committers. I will talk to them, then summarize and post my findings publicly. I hope to verify that Dragonfly 1) is used in production by 3 end users 2) has a healthy number of committers. |
Hey @sheng-liang, checking in here on status. Thanks! |
I'm done with reviewing the project and the due-diligence. The due-diligence Google doc has been updated. What's the next step? |
Thanks for your great work. @sheng-liang |
Yes, @sheng-liang should call for a formal vote, here is fine. |
I have reviewed the project and the due diligence doc. I have talked to a number of Dragonfly end users and committers and have verified that: 1) Dragonfly is used in production by 3 end users listed in due diligence doc and 2) Dragonfly has a healthy number of committers. My feedback has been incorporated into the due diligence doc. I believe the Dragonfly project is ready for entering incubation. I'd like to call for a TOC vote. |
Thank you, I will post the vote to @cncf/toc! |
Welcome to the CNCF incubator :) https://www.cncf.io/blog/2020/04/09/toc-votes-to-move-dragonfly-into-cncf-incubator/ |
Dragonfly has been a CNCF sandbox project since October 2018. After that, Dragonfly community got lots of help from the foundation. Now it has shown the healthy growth and cloud native adoption.
After talking with @caniszczyk, we felt it was time to propose Dragonfly for the incubation level. This pull request describes the current status of Dragonfly. And Dragonfly community wishes to hear more feedback from the ecosystem. Thanks.
Signed-off-by: Allen Sun [email protected]