- Followup: Today's CNCF TOC Call + Project Next Steps
Re: Followup: Today's CNCF TOC Call + Project Next Steps
toggle quoted messageShow quoted text
+1 for containerd and rkt.
I don’t know enough about Heron and the related ecosystem to have an on that opinion yet.
<cncf-toc-bounces@...> on behalf of Brian Grant via cncf-toc <cncf-toc@...>
Reply-To: Brian Grant <briangrant@...>
Date: Thursday, March 16, 2017 at 20:45
To: Chris Aniszczyk <caniszczyk@...>
Cc: CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] Followup: Today's CNCF TOC Call + Project Next Steps
On Wed, Mar 15, 2017 at 9:05 AM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:
We had a full TOC meeting today with three community presentations!!!:
The next steps would be for a TOC member to sponsor and invite the project for a formal proposal. If you're interested in doing this, please let us know by replying here.
I'd like to sponsor both containerd and rkt. It's important for CNCF to own and foster the foundational technology for cloud-native computing. Having both containerd and rkt in CNCF would be a great outcome for the CNCF, for Kubernetes,
and for the container and cloud ecosystems. Kubernetes and other container orchestrators need reliable, community-driven container runtimes scoped to container execution. Each runtime has its own strengths and use cases, and I hope that induction into CNCF
unlocks opportunities for broader collaboration.
As for Heron, I'm not seeing the demand for Storm/Heron. For example, Google trends:
Spark still has a lot of steam, and AIUI the trend (e.g., using
Apache Beam) is towards unified batch and streaming.
More broadly, though, I would like to see CNCF become a good home for container/orchestrator-friendly data-processing platforms, as that critical category of workloads benefits from closer integration with the underlying orchestration platform.
Join email@example.com to automatically receive all group messages.