Re: cluster

Camille Fournier

Sorry but is this a no or not now wrt using this cluster? I don't have time to spend on fruitless initiatives so if we're not yet clear on the purpose of this cluster yet I'm not going to spin my wheels trying to get a team of zk members spinning up work to make use of such a thing.

Just looking for clarity.


On Jul 11, 2016 6:13 AM, "Alexis Richardson" <alexis@...> wrote:

Many thanks Camille.  This is a very interesting topic.  I don't think we can throw the doors open to all projects, but I do think that your email touches on many places where interoperation & cooperation would advance the overall CNCF mission, brand, etc.  

Perhaps it would be helpful to pivot this topic in Ben's direction.  


In your view, what is a good set of shared goals for CNCF & ASF?  How do we make sure that Mesos, an ASF project, benefits from CNCF and vice versa?  Are the "cloud native needs" of Mesos the same as for other ASF projects such as: ZK, Kafka, and all the data streaming projects?


On Thu, Jul 7, 2016 at 6:55 PM Camille Fournier via cncf-toc <cncf-toc@...> wrote:
Hi folks,

So the ZooKeeper community has expressed some interest in using the CNCF cluster to set up a more sharable testing infrastructure for release verification. Are we open to this sort of thing? It looks like the cluster has a minimum 20 node request volume which is far more than the project would need, and tbh I don't really understand that minimum requirement? Even if we don't necessarily want to support release verification testing for ZK specifically, should we ever want to support it for similar systems such as etcd imposing a minimum usage seems slightly strange?

In conversations with Dan we discussed the concept that one of the most useful things CNCF could provide to teams was support beyond unit/simple integration test infrastructure, into more thorough system testing infrastructure. Anyway, I would say that a huge challenge for these cloud native distributed infrastructure components is having distributed testing environments to validate releases in a public manner, so it would be cool if we could consider supporting that.


cncf-toc mailing list

Join to automatically receive all group messages.