RFC: Dragonfly
|
The Dragonfly project was presented to the TOC today: They currently have one TOC sponsor, Jonathan Boulle. The Dragonfly community is seeking an additional TOC sponsor and happy to answer any questions from the community. Chris Aniszczyk (@cra) | +1-512-961-6719 |
|
|
|
Hi, Friends, It is my honor to give a presentation about Dragonfly to CNCF community. Dragonfly aims at covering all the image distribution in CNCF ecosystem. And currently it works perfectly within Kubernetes. My slides are in the attachment of this email. Please feel free to give us your feedback on Dragonfly. Any thoughts on it are welcome. In addition, I am really happy that Jonathan Boulle would like to sponsor Dragonfly to enter sandbox level. While we sincerely wish that an additional TOC member could sponsor this. How to get help from Dragonfly's team, if you are interested in this, please don't hesitate to drop questions on me. Thanks a lot. Allen Sun Alibaba Group
|
|
|
|
Deepak Vij <deepak.vij@...>
While we are on the topic of image pulling optimizations, following granular image layers level optimizations are being worked on as part of Kubernetes Scheduling SIG future release feature: 1) Layer tracking system on each machine/node discovers the layer information from local file-system and reports this information to workload scheduler (for example, K8S scheduler in our case). 2) As part of the image resolution process for an incoming container workload, image request is decomposed to underlying layer requests. 3) Scheduler uses these two pieces of information to perform workload scheduling in accordance to the layering information on the node. Regards, Deepak Vij
From: cncf-toc@... [mailto:cncf-toc@...]
On Behalf Of AllenSun
Sent: Tuesday, September 04, 2018 10:56 AM To: cncf-toc <cncf-toc@...> Subject: Re: [cncf-toc] RFC: Dragonfly
Hi, Friends,
It is my honor to give a presentation about Dragonfly to CNCF community. Dragonfly aims at covering all the image distribution in CNCF ecosystem. And currently it works perfectly within Kubernetes. My slides are in the attachment of this email.
Please feel free to give us your feedback on Dragonfly. Any thoughts on it are welcome.
In addition, I am really happy that Jonathan Boulle would like to sponsor Dragonfly to enter sandbox level. While we sincerely wish that an additional TOC member could sponsor this.
How to get help from Dragonfly's team, if you are interested in this, please don't hesitate to drop questions on me.
Thanks a lot.
Allen Sun Alibaba Group
|
|
|
|
Hi, Deepak Vij, Thanks for your feedback. Yes, it's a great job to support image pulling optimization in scheduling of Kubernetes. I think that the important feature you mentioned is
So, image pulling optimization you mentioned in on scheduling, while Dragonfly is mainly on Image Distribution. I think they are decoupled and only have few of overlapping. In addition, I think this feature and Dragonfly can co-exist very well to help improve image pulling. The feature decides the workload location by scheduling, and Dragonfly can improve the rest image distribution. Dragonfly takes over the image distribution for Kubernetes, and image pulling efficiency is only one part of distribution. Besides this, it also provides:
Currently all the three parts above consist of Dragonfly's service. Best Regards. Allen Sun Alibaba Group
|
|
|
|
Hi, Randy, Thanks for your feedback. We are very sure that all these adopters of Dragonfly are using Dragonfly in production like what I mentioned in my presentation. Since Dragonfly is very neutral, and totally a plugin component for original Architecture of Enterprises, it is invasive and easy to integrate Dragonfly. In addition, we can say Dragonfly indeed brings lots of value to help these adopters in image management. For China Mobile, their container platform is quite huge, more than a thousand nodes, Dragonfly in production helps a lot to speed up the image distribution efficiency. For iTEKFLY, the most famous speech intelligent company, they have quite huge images(more than 20GB) for speech processing, Dragonfly is the perfect one for them to reduce distribution time. For Ant Financial, sensitive business running in their datacenter, Dragonfly has also been a fundamental infrastructure tool, and tens of thousands of host are using it. For other adopters, they are also meeting the same image distribution issues, and Dragonfly is the best choice. In Alibaba, we have been using Dragonfly at large scale for more than 2 years. > how you calculated adoption We held several meetups in China, and set up good relationship with the community. Developers from these adopters have communicated with us to share their adoption and wished to seek support from the community. Currently we say more than 20+ adopters, but in fact I am afraid the amount of real adopters are larger than this number. Best Regards. Allen Sun Alibaba Group
|
|
|
|
sheng.zou@...
Really excited to see this news. It's a trend to embrace the CNCF ecosystem (k8s, docker) currently, and we are trying to build our own platform based on k8s. In image distribution part, Dragonly is the best choice for us compared with other solutions, it saves us a lot of time and efforts, and we truely believe Dragonfly will be an important role in container tech in the near future.
Looking forwarding to that day Dragonfly be a member of CNCF family, which help more people, and meanwhile make CNCF ecosystem better. |
|
|