cncf / cluster Goto Github PK

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

First Name

Latitia

Last Name

Haskins

Email

[email protected]

Company/Organization

IBM/ITPC/BlockChain

Job Title

software engineer

Project Title

Getting 100 fabric-peer nodes running running in an hyperledger fabric network

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

We want to verify that we can run a high number of peers in many (greater than 10) organizations. Ideally, we would be able to test this with each peer being in its own organization. We also want to reconfigure this to have more than 1 peer in each organization with 1 peer having access to a channel and the other not having access as well as the number of peers allowed in a single organization and possibly more.

Briefly describe the project

This test will allow us to find possible holes when there is a high number of organizations and peers with a certain number of channels, with only certain peers having access to a specific chaincode.

Do you intend to measure specific metrics during the work? Please describe briefly

yes, We would like to be able to track

• the number of transactions/second allowed
• at what point would degradation begin to show depending on the number of organizations and the number of peers.
• how long does it take to spin up the containers
• how long does it take for transactions to reach all peer nodes depending on the number in the organization

Which members of the CNCF community and/or end-users would benefit from your work?

• Hyperledger fabric project team members and users

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

Yes, https://github.com/hyperledger/fabric

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to do this within 2 months of cluster use?

Yes, for now, we can put the results in a README

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

Yes, we have docker images.

Are there identified risks which would prevent you from achieving significant results in the project ?

Not that I'm aware of at this time.

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

No.

Please list project titles associated with prior CNCF cluster usage.

Please list contributions to open source initiatives for projects listed in the last question. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

Please state your contributions to the open source community and any other relevant initiatives

This is for the Hyperledger-Fabric open source project.

Number of nodes requested (minimum 20 nodes, maximum ~400 nodes).

125 nodes.

Preferred node flavor, ratio if mixed (compute, storage, any).

compute nodes, but we will want to look at both TLS and non-TLS setups, so we will need to be able to save certificates for potentially 100 different nodes on each node. The specified 400GB should be more than enough.

Duration of request (minimum 24 hours, maximum 2 weeks).

2 weeks

With or Without an Operating System (restricted to CNCF predefined OS and versions as in README)?

With - Ubuntu 16.04

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

This is testing scalability capabilities for the fabric network. It will give us more concrete indications of where the network bottlenecks are located and the extent of those bottlenecks. Using this setup will not limit us to the possibility of our local system limitations, but fabric network limitations.

Any other relevant details we should know about while preparing the infrastructure?

As stated previously, we use docker images for the different containers. We would like to be able to view the containers' logs and log into certain nodes, if necessary.

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

Justin

Last Name

Garrison

Email

[email protected]

Company/Organization

Self

Job Title

Reference architecture

Project Title

Cloud Native Infrastructure book

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

Resources needed to test and set up examples of CNCF projects to verify functionallity and infrastructure topologies.

Briefly describe the project

@kris-nova and I are working on a book for O'Reilly about cloud native infrastructure. We need some resources to set up and test CNCF projects so we can create diagrams and verify functionallity of the projects and explain why specific design patterns are beneficial.

Do you intend to measure specific metrics during the work? Please describe briefly

We'll be setting up various projects (kubernetes, fluentd, linkerd, and prometheus) and need to be able to test the projects function as intended in an environment not directly tied to any cloud provider.

Which members of the CNCF community and/or end-users would benefit from your work?

Any of them who read the book (hopefully everyone 😄)

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

I do not believe the book will be open source although I will ask if it's a possibility. Otherwise the content/results will be available for anyone who is able to buy the book.

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to do this within 2 months of cluster use?

Any issues we find during testing we will open cases with the projects to discuss our issues and use cases.

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

yes, we will be deploying all projects on top of Kubernetes.

Are there identified risks which would prevent you from achieving significant results in the project ?

There is a risk the infrastructure will take to look to provision on bare metal. I am not sure what options are available for deploying into the cluster.

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

no

Please list project titles associated with prior CNCF cluster usage.

Please list contributions to open source initiatives for projects listed in the last question. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

Please state your contributions to the open source community and any other relevant initiatives

@kris-nova is an active participant in the kubernetes community and maintainer of kops
I am an active user/contributor of kubernetes

Number of nodes requested (minimum 20 nodes, maximum ~400 nodes).

30

Preferred node flavor, ratio if mixed (compute, storage, any).

any

Duration of request (minimum 24 hours, maximum 2 weeks).

2 weeks (the book is a 4 month project, we can submit multiple issues for more scheduled time)

With or Without an Operating System (restricted to CNCF predefined OS and versions as in README)?

Ubuntu

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

Provide reference architecture and examples

Any other relevant details we should know about while preparing the infrastructure?

First Name

Eli

Last Name

Mallon

Email

[email protected]

Company/Organization

Streamplace Inc.

Job Title

CEO

Project Title

Streamplace

Briefly describe the project

We're working on a cloud native compositor for live video. The core of it is a WebGL video compositor. Surrounding that core are adapters for RTMP, WebRTC, and HLS/DASH.

The incubator analogy-pitch is something like "Wordpress for livestreams" or "running your own Twitch". But that's later. For now I'm focusing on getting reliable and straightforward infrastructure for broadcasting and transcoding live video on Kubernetes.

Which members of the CNCF community and/or end-users would benefit from your work?

Any of the companies that process live video in a Kubernetes cluster. Looking over the list of CNCF members, that's more than a few.

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

Yep, everything is Apache licensed. https://github.com/streamplace/streamplace.

What kind of machines and how many do you expect to use?

A few Type 1Es would be amazing — our biggest resource hog is bandwidth. Eventually we'll want to see how high we can dial up ffmpeg's quality settings on something like a Type 2, but that can happen later.

To be clear, we don't intend to host enormous public live video broadcasts on the CNCF servers. Our clusters will be transcoding the video and broadcasting them out to YouTube/Facebook Live/Twitch/Twitter/whatever. If we are hosting our own video publicly, we'll do so through a CDN.

What OS and networking are you planning to use (see: https://help.packet.net/technical/infrastructure/supported-operating-systems)?

Container Linux Stable should be fine. Or whatever. Our current servers are running both Ubuntu and CentOS, so we're easy.

Please state your contributions to the open source community and any other relevant initiatives

Sure —

• I've contributed a variety of patches to the kube-aws project while working on setting up a HIPAA-compliant k8s cluster when I was at C-SATS.
• I wrote (possibly) the first open-source script to automate retrieval of Let's Encrypt certs for Kubernetes ingresses, since supplanted by the vastly superior kube-lego.
• I livestream development of Streamplace twice a week, with a focus on answering questions for bootcamp students and other folks that are getting into the industry.

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

Do a Google search for any combination of the words "live video kubernetes" and you'll get no results relevant to that at all, save for @jbeda's excellent TGI Kubernetes livestream. It gets worse with more specific terms, the fifth result for "RTMP server Kubernetes" is my npm account, so there's not a lot of resources out there for this sort of thing.

Streamplace is already publishing Helm charts for this sort of thing, including an RTMP server and a TURN server for WebRTC. I'd love to get all of that stuff polished enough to get into the main Charts repo.

Any other relevant details we should know about while preparing the infrastructure?

Each stream involves realtime video transcoding and bandwidth up to ~50Mbps. Should be fine given the specs but it's potentially more bandwidth-intensive than most tenants.

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

Doug

Last Name

Davis

Email

[email protected]

Company/Organization

IBM

Job Title

STSM

Project Title

Scalability for Kubernetes, Swarm, Mesos on OpenStack

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

We want to see how prevalent platforms for containers would scale on
an OpenStack infrastructure. The platforms include Kubernetes, Swarm
and Mesos. As part of the study, we expect to identify bottlenecks to
fix and best practices for operating a large scale platform for
containers. We have been working on building these platforms for the
past 1.5 years. We have made some initial benchmark runs on a smaller
scale environment.

Briefly describe the project

OpenStack provides cloud IaaS and Magnum is a service to deploy and
manage platforms for hosting containers on OpenStack. Currently it
supports Kubernetes, Swarm and Mesos. Each cluster is fully
integrated into OpenStack by leveraging services such as Keystone,
Nova, Neutron, Cinder, etc.

To support large scale container hosting, we need to understand the
scalability of these clusters from several perspective: many users
running multiple clusters, large cluster, launching many containers,
managing large number of containers, etc.

Do you intend to measure specific metrics during the work? Please describe briefly

To study these scenarios, we have developed a set of Rally benchmarks
to run the scenarios and collect performance data. Rally automatically
measures many metrics such as success rate, launch time, etc.

Which members of community and/or end-users would benefit from your work?

Several OpenStack projects will benefit from the study: Magnum, Heat, Neutron
This should also help validate upstream container platforms: Kubernetes, Swarm, Mesos
We plan to coorelate performance data published by Kubernetes to establish
the baseline.

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to this within 2 months of cluster use?

Yes, we currently have a presentation proposal on this data for the
next OpenStack summit in October 2016

Are there identified risks which would prevent you from achieving significant results in the project ?

No

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip questions 2 through 4.

No

Please list project titles associated with prior CNCF cluster usage.

N/A

Please list contributions to open source initiatives for projects listed in question 2. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

We have contributed code in OpenStack to deploy Kubernetes, Swarm, Mesos.
We have done performance study on Kubernetes networking.
We currently have 6 patches in Rally to test various container scenarios.
We have made 2 presentations at the OpenStack Summit related to containers.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

No

Please state your contributions to the open source community and any other relevant initiatives

Two of the three members of the team are core contributors in OpenStack
One member has been contributing for the past 3 years.

Number of nodes requested (minimum 20 nodes, maximum 500 nodes). In Q3, maximum increases to 1000 nodes.

50 nodes, followed by 500 nodes

Duration of request (minimum 24 hours)

50 nodes for 1 week to build OpenStack and run initial benchmarks
followed by 500 nodes for 1 week to run full scalalibity benchmarks.

With or Without an operating system (Restricted to CNCF pre-defined OS and versions)?

With Ubuntu 14.04

Any other relevant details we should know about while preparing the infrastructure?

It would be preferrable to have 2 network interface on the nodes, with separate networks.

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

Qi

Last Name

Liu

Email

[email protected]

Company/Organization

PingCAP, Inc.

Job Title

CEO

Project Title

TiDB

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

TiDB is targeting an easier deployment to provide a scalable and consistent database on Kubernetes and other container environments.

Briefly describe the project

TiDB is a distributed SQL database and it supports the best features of both traditional RDBMS and NoSQL.

Do you intend to measure specific metrics during the work? Please describe briefly

We will integrate the Prometheus metrics to measure the performance to improve the reliability, scalability and performance. We are hoping to get the load conditions on every node such as the IO , CPU, etc.

Which members of the CNCF community and/or end-users would benefit from your work?

etcd, Kubernetes, and Prometheus.

Is the code that you’re going be running 100% open source? If so, what is the URL or URLs where it is located?

Yes. https://github.com/pingcap/tidb

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to this within 2 months of cluster use?

Yes and Yes.

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

Yes. From the very beginning, the deployment and testing of TiDB depends on the containers. Currently, all the test cases and continuous integration are based on Docker.

Are there identified risks which would prevent you from achieving significant results in the project ?

No.

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

No.

Please list project titles associated with prior CNCF cluster usage.

Please list contributions to open source initiatives for projects listed in the last question. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

Please state your contributions to the open source community and any other relevant initiatives

The co-author of the following open source projects:
TiDB: https://github.com/pingcap/tidb
TiKV:https://github.com/pingcap/tikv
Codis: https://github.com/CodisLabs/codis

Number of nodes requested (minimum 20 nodes, maximum 500 nodes). In Q3, maximum increases to 1000 nodes.

100 nodes.

Duration of request (minimum 24 hours, maximum 2 weeks)

2 weeks.

With or Without an operating system (Restricted to CNCF pre-defined OS and versions)?

With. Ubuntu 14.04+ or CentOS 7. Ubuntu 14.04+ is preferred.

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

As a scalable and consistent database, TiDB deployment supports the applications and microservices on the cloud native platforms so that they don’t have to care about the state and will be very easy to scale. This testing could help us ensure that.

Any other relevant details we should know about while preparing the infrastructure?

We need to use Kubernetes and the latest Docker.

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

Thomas

Last Name

Graf

Email

[email protected]

Company/Organization

Cilium

Project Title

Cilium

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

Cilium addresses large scale policy enforcement and addressing for containers with the help of BPF and IPv6. We would love to run continuous regression tests of development Linux kernels to avoid regressions of Linux kernel code in particular involving BPF.

Briefly describe the project

Cilium provides fast in-kernel networking and security policy enforcement for containers based on eBPF programs generated on the fly. It is an experimental project aiming at enabling emerging kernel technologies such as BPF and XDP for containers.

However, we regard the testing effort to be relevant to any container related networking solution which relies on kernel functionality.

Do you intend to measure specific metrics during the work? Please describe briefly

• Network latency and throughput in comparison to scale
• Determine number of application metrics to be measurable via kprobes/BPF etc.
• Measure scalability limits of BPF based policy enforcement model

Which members of the CNCF community and/or end-users would benefit from your work?

All members with an interest in container networking or with interest in BPF technology for both instrumentation and networking.

Is the code that you’re going be running 100% open source? If so, what is the URL or URLs where it is located?

https://github.com/cilium/cilium

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to this within 2 months of cluster use?

Yes

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

Containers only

Are there identified risks which would prevent you from achieving significant results in the project ?

We require to run a very recent Linux kernel on the bare metal system (4.8.rcX) and we require IPv6 to be allowed on the network.

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

No

Please state your contributions to the open source community and any other relevant initiatives

10+ years Linux kernel development, OVS, BPF, Docker, Kubernetes, ...

Number of nodes requested (minimum 20 nodes, maximum 500 nodes). In Q3, maximum increases to 1000 nodes.

We are happy with any number of nodes we can acquire.

Duration of request (minimum 24 hours)

Ideally we can run a small number of nodes consistently to allow for regression testing as Linux kernel and BPF development progresses.

With or Without an operating system (Restricted to CNCF pre-defined OS and versions)?

We require to run a recent Linux kernel (4.8.rcX) with BPF capabilities enabled. Docker runtime.

How will this testing advance cloud native computing (specifically containerization,

orchestration, microservices or some combination).

THe kernel community currently does not include any regression or automated tests which cover the special scale and performance requirement needs of cloud native workloads. The aim is to close this gap.

Any other relevant details we should know about while preparing the infrastructure?

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

FNAME: Zachary

LNAME: Smith

EMAIL: [email protected]

COMPANY: Packet

TITLE: CEO

PROJECT: Packet On Premise Automation

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

Developer automation for fundamental, "can be anywhere" infrastructure is a critical component of cloud native computing. To date, most cloud native computing relies heavily on primitives of multi-tenant public clouds or virtualization based private clouds. Packet is eager to refine its software stack for use in on premise environments to power cloud native applications regardless of location. At Packet, we operate a public cloud that is used by many CNCF members to test, build or operate cloud native stacks without virtualization or overlay networking as a requirement. We envision that much of this could happen on the CNCF cluster.

Briefly describe the project

We would like to install and operate a Packet private rack in the CNCF cluster. This would include both server and switch automation.

Do you intend to measure specific metrics during the work? Please describe briefly

We are interested in achieving baseline capabilities, including provisioning, deprovisioning, healthchecking and metering of physical compute instances. We would use our own Docker-based canary testing for simulating thousands of provisions and measure the success rates.

Which members of the CNCF community and/or end-users would benefit from your work?

Nearly all members could leverage this. However, members known to be comfortable with the Packet API and meta data service include CoreOS/Quay, Mesosphere DC/OS, Rancher, Apprenda, ContainerSolutions, Deis, Diamanti, Nginx, Portworx, StackPoint, Mirantis, Tigera, and Virtuozzo.

Is the code that you’re going be running 100% open source? If so, what is the URL or URLs where it is located?

No, it is not currently open source. Our goal would be to evaluate the usefulness of open sourcing any of our core automation.

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to this within 2 months of cluster use?

We agree in publishing in our results.

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

Yes, our stack currently runs 100% in Docker (on Rancher).

Are there identified risks which would prevent you from achieving significant results in the project ?

Yes, the network architecture and access to control plane, IP space, routing level details, etc are unclear and could affect if this would be successful or not.

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

No.

Please list project titles associated with prior CNCF cluster usage.

Please list contributions to open source initiatives for projects listed in the last question. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

Please state your contributions to the open source community and any other relevant initiatives

We are large supporters of the Cloud Native and Open Source communities in general, regularly providing 100-1000 bare metal compute nodes to cloud native projects for load and scale testing, build operations and compatibility work.

Number of nodes requested (minimum 20 nodes, maximum 500 nodes). In Q3, maximum increases to 1000 nodes.

100 nodes, or whatever is in a logical switch group.

Duration of request (minimum 24 hours, maximum 2 weeks)

2 weeks would probably be insufficient for our use given past experiences with other infrastructure environments. Our goal would be to a) complete Packet private rack ingestions and b) offer use of the underlying compute resources to CNCF projects via the Packet API and metadata service (using a special CNCF facility code).

With or Without an operating system (Restricted to CNCF pre-defined OS and versions)?

No operating system. We would need full BMC access, bios level control (particularly if we were to test trusted computing), and privileged switch control using netconf style access.

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

Our goal is to showcase that cloud native computing can leverage fundamental bare metal compute (literally nothing else), be performed in any location and offer the same convenient DevOps interfaces that users leverage today (e.g. terraform, ansible, native cloud-init, elastic addressing, etc).

Any other relevant details we should know about while preparing the infrastructure?

Name, email, company, job title

Alan Gutierrez ~ @bigeasy ~ hacker

Cory Kaufman-Schofield ~ @allspiritseve ~ also hacker

Project Title and description

CNCF Demo on ARM ~ Get the CNCF demo applications working on ARM. Initiate a project to get the CNCF stable of hosted projects working on ARM using the CNCF demo application as a test bench. Begin by first getting the demo to work with the Packet infrastructure. This will create a patch to the demo where the AWS installation step can be replaced by a deployment Packet x86. Once working on x86 we can then begin to port the demo components to ARM on Packet peicemeal with integration testing aginst that x86 hosted components. The end result is a CNCF demo that can be hosted mix or match on x86 or ARM at Packet, verified function of the CNCF components on ARM, along with any insights gathered in porting CNCF's Go based components form x86 to ARM.

Which members of the community would benefit from your work?

Anyone working with cloud native applications. The heart of CNCF is Kubernetes, so this will be a demonstration of the ability to host a constainer orchestration environment on ARM hardware. Specifically this will be an exercise of Kubernetes container orchestration and Prometheus container monitoring.

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

Yes, the code will be 100% open source and submitted back into the CNCF demo.

What infrastructure (computing resources and network access) do you need? (see: https://www.packet.net/bare-metal/)?

The project will need access to 3 machines for the x86 portion of the port, each with a minimum of 32 GB RAM. The Packet Type 1 server should be adequate to the task. Type 1 servers are hosted in data centers with the Packet Block Storage service so it would allow us to evaulate the use Kubernetes block storage plugin for Packet Block Storage. Upon completion of the x86 evaulation, a similar number of Type 2A servers will be required for the Arm portion of the effort.

Currently the template links users to find out about supported operating systems on Packet's /bare-metal/ page. We should consider updating to a more directly informative page:

https://help.packet.net/technical/infrastructure/supported-operating-systems

The cluster is currently unavailable due to a serious issue in the frontend cluster. We are working on making it operational but currently it is not possible for tenants to access the cluster in any way. We will post updates here and on CNCF Cluster Slack channel once we have more information. I am extremely sorry for any trouble it might cause.

First Name

Timothy

Last Name

St. Clair

Email

[email protected]

Company/Organization

Red Hat

Job Title

Principal Software Engineer

Project Title

Kubernetes Scalability SIG

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

Compare and diagnose scale test results across companies.

Briefly describe the project

Scaling Kubernetes (Scalability SIG)

Do you intend to measure specific metrics during the work? Please describe briefly

Yes

Which members of community and/or end-users would benefit from your work?

The scale sig

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to this within 2 months of cluster use?

Yes

Are there identified risks which would prevent you from achieving significant results in the project ?

Not yet.

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip questions 2 through 4.

no

Please list project titles associated with prior CNCF cluster usage.

kubernetes maintainer

Please list contributions to open source initiatives for projects listed in question 2. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Active SIG lead and maintainer

Have you ever been denied usage of the cluster in the past? If so, please explain why.

n/a

Please state your contributions to the open source community and any other relevant initiatives

I'm an active kubernetes maintainer.

Number of nodes requested (minimum 20 nodes, maximum 500 nodes). In Q3, maximum increases to 1000 nodes.

~300

Duration of request (minimum 24 hours)

4 weeks

With or Without an operating system (Restricted to CNCF pre-defined OS and versions)?

Without, or RHEL

Any other relevant details we should know about while preparing the infrastructure?

Ideally I think openstack-ifying would be beneficial to the community.

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

Allan

Last Name

Naim

Email

[email protected]

Company/Organization

Google

Job Title

Product

Project Title

Cluster Federation testing

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

Briefly describe the project

Cluster Federation testing between bare metal CNCF clusters and GKE

Do you intend to measure specific metrics during the work? Please describe briefly

Which members of the CNCF community and/or end-users would benefit from your work?

Sig-federation

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

Yes

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to do this within 2 months of cluster use?

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

Yes, containerized workloads running in Kube

Are there identified risks which would prevent you from achieving significant results in the project ?

n/a

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

no

Please list project titles associated with prior CNCF cluster usage.

n/a

Please list contributions to open source initiatives for projects listed in the last question. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

no

Please state your contributions to the open source community and any other relevant initiatives

Cluster federation Kube upstream

Number of nodes requested (minimum 20 nodes, maximum ~400 nodes).

Only need about 4 nodes

Preferred node flavor, ratio if mixed (compute, storage, any).

n/a

Duration of request (minimum 24 hours, maximum 2 weeks).

2 wks

With or Without an Operating System (restricted to CNCF predefined OS and versions as in README)?

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

Benefits the cluster federation effort within Kube

Any other relevant details we should know about while preparing the infrastructure?

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

Omer

Last Name

Katz

Email

[email protected]

Company/Organization

N/A

Job Title

N/A

Project Title

Adding NUMA-aware allocator to RethinkDB's buffer cache

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

Databases have high memory throughput even in clusters of modest sizes. Data is usually cached in memory and the faster it is read the faster the database is.
On NUMA-enabled hardware, databases can swap in a way that greatly degrades performance. See https://blog.jcole.us/2010/09/28/mysql-swap-insanity-and-the-numa-architecture/

Briefly describe the project

The project will use the memkind to introduce NUMA aware allocations to the buffer cache.

Do you intend to measure specific metrics during the work? Please describe briefly

Yes, I'm going to use the YCSB benchmark provided here. This will ensure everything is working normally and that performance is enhanced.

Which members of the CNCF community and/or end-users would benefit from your work?

The RethinkDB project and its users

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

Yes. https://github.com/rethinkdb/rethinkdb

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to do this within 2 months of cluster use?

Yes absolutely. A PR will be issued to the RethinkDB repository.

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

I do not need containers. I may test RethinkDB on containers as well to see the effect of my changes on the performance of containerized RethinkDB.

Are there identified risks which would prevent you from achieving significant results in the project?

Not that I know of.

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

No

Please list project titles associated with prior CNCF cluster usage.

Please list contributions to open source initiatives for projects listed in the last question. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

Please state your contributions to the open source community and any other relevant initiatives

I maintain Celery a task manager written in Python, MongoEngine which maps Mongo documents to Python objects and oauthlib which is the standard OAuth1/2 implementation for Python.

Number of nodes requested (minimum 20 nodes, maximum ~400 nodes).

20

Preferred node flavor, ratio if mixed (compute, storage, any).

compute

Duration of request (minimum 24 hours, maximum 2 weeks).

2 weeks if possible. I'd like to repeatedly refine the performance and ensure we're getting the most out of the hardware.

With or Without an Operating System (restricted to CNCF predefined OS and versions as in README)?

Ubuntu.

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

Any other relevant details we should know about while preparing the infrastructure?

I need both machines that are NUMA-enabled and machines that are not.

Full Name

Stuart P. Bentley

Email

[email protected]

Company/Organization, Job Title

I don't really have one - I pretty much spin up a new GitHub organization for each project, so I guess that's my organization (so my org for this request would be Plushu), and my title / role would be Lead Maintainer?

Project Title

Plushu

Briefly describe the project

Plushu is a modular framework for building command-line interfaces, with an eye toward being used as the shell for a dedicated user on a dedicated server (ie. establishing a CLI for operating the server itself).

The Plusku ecosystem of Plushu modules uses Docker (with an eye toward Kubernetes, going forward) to build and run Twelve-Factor Apps, a la Heroku.

I currently have an open server where users can try this out running at sandbox.plushu.org (with the entry-point to submit a public key for access running at http://enter.sandbox.plushu.org), which is re-imaged daily via a Cron job on a remote machine. The Sandbox server itself is currently running on a Digital Ocean droplet I'm paying for out-of-pocket, and the cronjob is running on a Dreamhost server.

Which members of the CNCF community and/or end-users would benefit from your work?

Anybody looking to self-host a Heroku-style build and deployment infrastructure for their app.

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

• Everything in the Plushu project is up under https://github.com/plushu
• The script used to set up the sandbox is here
• The script currently used to reset the sandbox on a timer is here
• The app used to restore the sandbox manually (technically not part of the Plushu project) is at https://github.com/stuartpb/reshotput

What kind of machines and how many do you expect to use (see: https://www.packet.net/bare-metal/)?

I would only use the tiniest tier of machine; I would probably be using at least three of them (one for the Pluahu Sandbox, one for the watchdog service, and one for experimentation), but not many more than that (and I could potentially work toward consolidating the Sandbox and the watchdog to one machine with two IPs, where one would be in use for the host environment and the other would point to the Sandbox VM).

What OS and networking are you planning to use (see: https://help.packet.net/technical/infrastructure/supported-operating-systems)?

The Plushu Sandbox will probably run on Ubuntu 16.04 (the current sandbox is running on 14.04, only because I haven't bothered to rebuild it since 2015). I would probably experiment with RancherOS and CoreOS as well.

If I go the sandbox-as-a-nested-VM route, I may use CentOS 7 as the host environment, with something like mist.io or oVirt to manage the VM.

Please state your contributions to the open source community and any other relevant initiatives

All the work I do is open-source: some of my other big open source projects include the Open Profilogical Web Survey, the Tabalanche browser extension, and CouchDB in a Hurry.

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination)?

The Plusku ecosystem orchestrates containerized microservices (apps and addons), and working on it uncovers new ways to approach these concepts within the space of existing developer paradigms (ie. following the use patterns established by the Heroku Toolbelt).

Any other relevant details we should know about while preparing the infrastructure?

Is it possible to get an IPv6 address space? That could be useful for a possible extension to the Sandbox where, instead of having one global sandbox shared by any prospective developers, each user could be given a separate VM (within which they can provision containers), with its own IPv6 address.

Hello,

I am just curious. What is the CNCF doing to make sure there is tangible benefit(s) from use of the cluster? I see an approval process, but not really a follow up in what was improved about the software involved. Not trying to call any project out, just trying to close the loop so others can reference this as good use and an overall benefit.

I think maybe just linking back to an issue in the various projects would be a good start. (ex. software X has never ran on 500+ machines, it be good to see it work). I also realize it might not lead to some change, but should at least show a decision was made based on its usage. I can appreciate how much time(aka money) and effort goes into running clusters.

If I missed something, I apologize.

Ron

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

Andres

Last Name

Garcia Garcia

Email

[email protected]

Company/Organization

Fujitsu EST

Job Title

Senior Software Engineer

Project Title

CNCF Service Broker API

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

Definition of an standard Service Broker API

Briefly describe the project

Task force to define the Service Broker API in the context of the CNCF activities

Do you intend to measure specific metrics during the work? Please describe briefly

No

Which members of community and/or end-users would benefit from your work?

Service providers interested on implementing a standard API for service provisioning.

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to this within 2 months of cluster use?

Yes

Are there identified risks which would prevent you from achieving significant results in the project ?

No

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip questions 2 through 4.

No

Please list project titles associated with prior CNCF cluster usage.

Please list contributions to open source initiatives for projects listed in question 2. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

No

Please state your contributions to the open source community and any other relevant initiatives

Currently on the process to contribute to https://github.com/servicecatalog/development, currently developing proof of concept prototypes for the CNCF Service Broker API workgroup.

Number of nodes requested (minimum 20 nodes, maximum 500 nodes). In Q3, maximum increases to 1000 nodes.

20

Duration of request (minimum 24 hours)

3 months

With or Without an operating system (Restricted to CNCF pre-defined OS and versions)?

With

Any other relevant details we should know about while preparing the infrastructure?

We want a Kubernetes cluster to test the different PoC prototypes that we will develo for the Service Broker workgroup in the following months.

This issue will (hopefully) be updated weekly to show the current CNCF community cluster allocations.

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

Howard

Last Name

Huang

Email

[email protected]

Company/Organization

Huawei

Job Title

Senior Open Source/Standard Community Manager

Project Title

OpenSDS Kubernetes Integration Testing

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

Storage is an important part of functionality for Kubernetes, and currently there are multiple in-tree and out-of-tree volume plugins developed for Kubernetes, but it is hard to know whether the integration of storage provider is functioning as it should be without testing it. Moreover for storage that is provided from cloud provider (e.g OpenStack), there should be functional testing to prove the integration's actually working.

Briefly describe the project

OpenSDS is a fellow Linux Foundation collaborative project and aims to provide a unified storage service experience for Kubernetes. OpenSDS could provide various types of storage resource for Kubernetes (e.g OpenStack block and file service, baremetal storage device), and we want to use CNCF Cluster to :

• Verify the integration of OpenSDS and Kubernetes
• Verify the performance of the inegration via metrics such as IOPS, latency
• Utilize the Intel S3610 400GB SSD and 2TB NLSAS HDD for storage provisioning

Do you intend to measure specific metrics during the work? Please describe briefly

Yes we need to measure the storage performance (e.g IOPS, latency) to see if the integration is functioning properly.

Which members of the CNCF community and/or end-users would benefit from your work?

Kubernetes's storage-sig will get a better view on the future storage evolution. End-users could also have first-hand knowledge of the Kubernetes Storage prowess

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

Yes, please refer to the source code at https://github.com/opensds/opensds

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to do this within 2 months of cluster use?

Yes, and we will also probably need to feedback the result to the OpenStack community as well.

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

Yes we are testing with container clusters managed by Kubernetes.

Are there identified risks which would prevent you from achieving significant results in the project ?

The storage interface is not well defined in Kubernetes at the moment, and any changes in the upstream will likely break the testing. We will try to work with storage sig as much as possible

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

No

Please list project titles associated with prior CNCF cluster usage.

Please list contributions to open source initiatives for projects listed in the last question. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

Please state your contributions to the open source community and any other relevant initiatives

I've been working in the OpenStack and OPNFV community for about 3 years. My stats could be found at stackalytics website

Number of nodes requested (minimum 20 nodes, maximum ~400 nodes).

20 or less (maybe 4 or 5 node is good enough)

Preferred node flavor, ratio if mixed (compute, storage, any).

compute and storage node

Duration of request (minimum 24 hours, maximum 2 weeks).

2 weeks

With or Without an Operating System (restricted to CNCF predefined OS and versions as in README)?

Ubuntu

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

This testing could help with orchestration especially in the storage area.

Any other relevant details we should know about while preparing the infrastructure?

No

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

Russell

Last Name

Bryant

Email

[email protected]

Company/Organization

Red Hat

Job Title

Senior Principal Software Engineer

Project Title

OVN Data Plane Testing

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

Networking data plane performance is very important, and it's often difficult to know what performance characteristics to expect with different combinations of hardware, software, and protocols in use.

Briefly describe the project

We aim to do some benchmarking of OVN (from the Open vSwitch community) using the Geneve protocol as compared to other solutions. This lab has Intel X710 NICs, which support both Geneve and VXLAN offload, making it an ideal place to do this work.

Do you intend to measure specific metrics during the work? Please describe briefly

Yes, we will gather networking data plane performance metrics.

Which members of the CNCF community and/or end-users would benefit from your work?

Anyone interested in overlay network based solutions, particularly those based on OVS, would benefit from the additional insights gained by this work.

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

Yes. OVN is a part of Open vSwitch and the code is hosted at http://github.com/openvswitch/ovs. We aim to test OVN as configured by OpenStack (http://github.com/openstack/networking-ovn). We are also interested in testing with Kubernetes (http://github.com/openvswitch/ovn-kubernetes).

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to do this within 2 months of cluster use?

Yes.

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

Testing of ovn-kubernetes would involve containers.

Are there identified risks which would prevent you from achieving significant results in the project ?

Any encountered lab network or other hardware issues are the main risks.

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

No

Please list project titles associated with prior CNCF cluster usage.

Please list contributions to open source initiatives for projects listed in the last question. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

Please state your contributions to the open source community and any other relevant initiatives

I have been contributing to various open source projects since 2004. In the last couple of years I have been working on OVN (Open Virtual Network), a new network virtualization system developed by the Open vSwitch community that has been integrated with multiple systems, including OpenStack and Kubernetes.

Number of nodes requested (minimum 20 nodes, maximum ~400 nodes).

20 (or less is fine, probably 5 minimum)

Preferred node flavor, ratio if mixed (compute, storage, any).

any (primary requirement is the Intel X710 NIC, which appears to be in both compute and storage flavors)

Duration of request (minimum 24 hours, maximum 2 weeks).

2 weeks

With or Without an Operating System (restricted to CNCF predefined OS and versions as in README)?

CentOS 7, though ideally also with the option to re-provision the machines using an OpenStack deployment tool.

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

OVN is a new network virtualization option that works with Kubernetes. Having a better understanding of the performance of OVN and its use of Geneve will help better inform choices and further development in this area.

Any other relevant details we should know about while preparing the infrastructure?

No

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

First Name

Eugene

Last Name

Zilman

Email

[email protected]

Company/Organization

CNCF

Project Title

Demo

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

Testing scale on bare metal

Briefly describe the project

The goal of this project is to demonstrate each of the technologies that have been adopted by the Cloud Native Computing Foundation (CNCF) in a publicly available repository in order to facilitate their understanding through simple deployment tooling and by providing sample applications as common-ground for conversation. This project will enable replicable deployments and facilitate quantification of performance, latency, throughput, and cost between various deployment models.

Do you intend to measure specific metrics during the work? Please describe briefly

With this one we'd like to check how overlay networking performs with a high node count. Specifically we'll be benchmarking Weave and observing the behaviour with the collaboration of the Weave developers.

Which members of the CNCF community and/or end-users would benefit from your work?

People interested in running Weave and Countly on larger clusters.

Is the code that you’re going be running 100% open source? If so, what is the URL or URLs where it is located?

Yes, everything is or will be available here: https://github.com/cncf/demo

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to this within 2 months of cluster use?

Yes.

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

Containers used extensively.

Are there identified risks which would prevent you from achieving significant results in the project ?

No

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

Yes

Please list project titles associated with prior CNCF cluster usage.

Demo

Please list contributions to open source initiatives for projects listed in the last question. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

https://github.com/cncf/demo

Have you ever been denied usage of the cluster in the past? If so, please explain why.

N/A

Please state your contributions to the open source community and any other relevant initiatives

Number of nodes requested (minimum 20 nodes, maximum 500 nodes). In Q3, maximum increases to 1000 nodes.

100

Duration of request (minimum 24 hours, maximum 2 weeks)

2 weeks

With or Without an operating system (Restricted to CNCF pre-defined OS and versions)?

With CentOS7

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

It will make sure the technology demonstration ("Demo") scales from your laptop all the way to a big bare metal cluster and works as expected. Any bugs discovered will be reported upstream.

Any other relevant details we should know about while preparing the infrastructure?

No

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

First Name

Lee

Last Name

Calcote

Email

[email protected]

Company/Organization

SolarWinds

Job Title

Sr. Director, Technology Strategy

Project Title

Container Network Performance

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

Selecting the proper container network provider for a project can be difficult. We have noticed performance differences depending on the application workload.

Briefly describe the project

The SolarWinds container network performance meter initiates a bandwidth test between containers and compares to the performance between the corresponding hosts. We will configure a kubernetes cluster with various network plugins (WeaveNet, Calico, Flannel, etc.) to compare performance.

Do you intend to measure specific metrics during the work? Please describe briefly

Yes - network bandwidth throughput between containers compared to performance between hosts. Container network driver performance - CNI and CNM plugins.

Which members of the CNCF community and/or end-users would benefit from your work?

End-users will benefit from being enlighten about how their network driver choices affect connectivity and performance of their networks. Vendors will benefit from an apples-to-apples comparison from an agnostic third-party. Kubernetes itself may benefit from an understanding of the limits of its native networking scale.

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

Yes, it will be open-sourced and located here - https://github.com/solarwinds/containers

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to do this within 2 months of cluster use?

Yes, absolutely.

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

Yes, ideally testing containers from that of the CNCF Demo project

Are there identified risks which would prevent you from achieving significant results in the project ?

No

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

No

Please list project titles associated with prior CNCF cluster usage.

Please list contributions to open source initiatives for projects listed in the last question. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

No

Please state your contributions to the open source community and any other relevant initiatives

• We recently put together a few slides to facilitate the ONIF panel on container networking
• We're contributing to the CNCF WG-Networking workgroup.
• We helped create and maintain a collection of container network solutions

Number of nodes requested (minimum 20 nodes, maximum ~400 nodes).

20 nodes will work. 60 would be ideal in order elicit fully-distributed network behavior.

Preferred node flavor, ratio if mixed (compute, storage, any).

Ideally, the same compute across the nodes, so as to facilitate a uniform test. If there is variance in compute, that's fine. We'll just note this. Variance in storage is not an issue.

Duration of request (minimum 24 hours, maximum 2 weeks).

Ideally, 2 weeks, but 1 week will suffice.

With or Without an Operating System (restricted to CNCF predefined OS and versions as in README)?

CentOS 7 (any others will work, however)

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

Any other relevant details we should know about while preparing the infrastructure?

We intend to run high-volume bandwidth and latency tests between the networked hosts.

First Name

Stuart

Last Name

Williams

Email

[email protected]

Company/Organization

Weaveworks

Job Title

Director of Product Management

Project Title

Zero-downtime Upgrade Research

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

Infrastructure components are now often containerized, upgrading them without causing, or minimising downtime presents challenges that are not adequately explored in cloud native environments.

Briefly describe the project

We will try various scenarios, at scale, that upgrade container-based infrastructure and validate that applications using those services are impacted or impeded in their operation.

Do you intend to measure specific metrics during the work? Please describe briefly

Liveness of applications and error detection

Which members of community and/or end-users would benefit from your work?

Users of containerized infrastructure components will benefit from our learnings.

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to this within 2 months of cluster use?

Yes. Results will be published & changes to OSS described in a blog

Are there identified risks which would prevent you from achieving significant results in the project ?

No

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip questions 2 through 4.

No

Please list project titles associated with prior CNCF cluster usage.

n/a

Please list contributions to open source initiatives for projects listed in question 2. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

n/a

Have you ever been denied usage of the cluster in the past? If so, please explain why.

n/a

Please state your contributions to the open source community and any other relevant initiatives

All Weave products are OSS; our employees have created and contributed to many OSS projects - from Linux kernel patches, to ASF & Eclipse projects, to founding RabbitMQ.

Number of nodes requested (minimum 20 nodes, maximum 500 nodes). In Q3, maximum increases to 1000 nodes.

1000 nodes

Duration of request (minimum 24 hours)

120 hours

With or Without an operating system (Restricted to CNCF pre-defined OS and versions)?

With OS.

Any other relevant details we should know about while preparing the infrastructure?

Not yet.

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

Chris

Last Name

Aniszczyk

Email

[email protected]

Company/Organization

Linux Foundation / CNCF

Job Title

VP / COO

Project Title

CNCF Marketing Demo (using Boinc)

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

Builds a canonical marketing demo using CNCF technology

Briefly describe the project

Builds a canonical marketing demo using CNCF technology

Do you intend to measure specific metrics during the work? Please describe briefly

Application performance

Which members of community and/or end-users would benefit from your work?

All of the CNCF community looking to learn how to build a non-trivial CNCF application

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to this within 2 months of cluster use?

Everything will be open source from day 1

Are there identified risks which would prevent you from achieving significant results in the project ?

Nope

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip questions 2 through 4.

No

Please list project titles associated with prior CNCF cluster usage.

N/A

Please list contributions to open source initiatives for projects listed in question 2. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

N/A

Have you ever been denied usage of the cluster in the past? If so, please explain why.

N/A

Please state your contributions to the open source community and any other relevant initiatives

N/A

Number of nodes requested (minimum 20 nodes, maximum 500 nodes). In Q3, maximum increases to 1000 nodes.

20

Duration of request (minimum 24 hours)

A couple of weeks to start, may request permanent access

With or Without an operating system (Restricted to CNCF pre-defined OS and versions)?

With

Any other relevant details we should know about while preparing the infrastructure?

We are CNCF staff :)

For the sake of transparency it probably makes sense to lay down meeting note agenda and action items so folks that potentially miss a meeting can be kept up to date.

Documentation on cluster usage should probably live here, I've been looking for it but have been unable to find it.

/cc @rrati @jeremyeder

If you are interested in filing a request for access to the CNCF CIL, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

Rob

Last Name

Hirschfeld

Email

[email protected]

Company/Organization

RackN

Job Title

CEO

Project Title

Digital Rebar

Briefly describe the project

Automates physical network provisioning

Which members of the CNCF community and/or end-users would benefit from your work?

RackN is a CNCF member. The service works on Packet.net
We're not sure who else is consuming software

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

Yes. http://Rebar.digital
Code is github.com/digitalrebar/provision

We're talking about PROVISION only, not the v2 container stuff.

What kind of machines and how many do you expect to use (see: https://www.packet.net/bare-metal/)?

Type 0s. 10 - 15 machines per build for about 15 minutes per commit.

What OS and networking are you planning to use (see: https://www.packet.net/bare-metal/)?

CustomIPXE exclusively

Please state your contributions to the open source community and any other relevant initiatives

For CNCF, we've been working on Kubespray and Kubernetes
We have significant activity with OpenStack in the past
We have been involved in a number of projects in monior ways including Consul, Terraform, BOSH, Golang and Chef.

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

Digital Rebar is the cloud native physical provisioning alternative. This testing ensures that the community profiles work consistently. That helps users who want to use Kubernetes and other CNCF projects on bare metal deployments.

Any other relevant details we should know about while preparing the infrastructure?

We're already using Packet for this open source testing, so we'd be able to give you a very quick and visible win on using the infrastructure to support an open project with CNCF ties.

First Name

Malte

Last Name

Schwarzkopf

Email

[email protected]

Company/Organization

Cambridge Systems at Scale (CamSaS) / Firmament.io / MIT CSAIL

Job Title

Researcher

Project Title

Firmament and Poseidon scale-up evaluation

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

• Better placement decisions in cluster schedulers; e.g., to avoid “noisy neighbors” and cross-workload interference.
• Scalability of cluster scheduling using min-cost flow optimization (as in Quincy and Firmament) on a real-world cluster.

Briefly describe the project

In our research, we developed the Firmament cluster scheduler, on which we have an upcoming paper appearing in OSDI 2016. In this paper, we evaluate the scalability of Firmament’s min-cost flow optimization-based scheduling by replaying workload traces, and in a small-scale test-bed deployment. We would like to perform a real-world scale-up evaluation to further validate our results, and to explore the benefit of Firmament’s scheduling policies for real workloads running on a larger-scale clusters than we currently have access to.

Poseidon (https://github.com/camsas/poseidon) is an integration of Firmament’s scheduling logic with Kubernetes: we have developed Poseidon as a drop-in replacement for the default Kubernetes scheduler (kube-scheduler). We would like to deploy Poseidon at scale and measure its performance in order to compare it against our own stand-alone research cluster manager and ensure that there are no undue performance penalties in either implementation.

Do you intend to measure specific metrics during the work? Please describe briefly

Yes, we hope to measure the following:

1. Scheduling latency / placement delay, which quantifies the time between workload (pod/container) submission and the execution on a node.
2. Placement quality / performance degradation over ideal, which measures the runtime on shared infrastructure compared to the ideal runtime on an otherwise idle machine or cluster.
3. Packing efficiency, which measures the quality of a scheduling policy by shrinking the cluster until the workload no longer fits (see source).

Which members of the CNCF community and/or end-users would benefit from your work?

The Kubernetes project, via the Poseidon scheduler, which we are making available for anyone to use. Poseidon is API-compatible with kube-scheduler and can be deployed on existing Kubernetes clusters.

Is the code that you’re going be running 100% open source? If so, what is the URL or URLs where it is located?

Yes, see https://github.com/camsas/firmament and https://github.com/camsas/poseidon.

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to this within 2 months of cluster use?

Yes, we open-source all of our work on Firmament and Poseidon under the Apache 2.0 license. Our experimental results will be published as part of a peer-reviewed paper, a blog post, or a technical report.

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

Yes, Poseidon schedules containers (via Kubernetes). Firmament’s standalone cluster manager has alpha support for container execution; we hope to improve this in the near future.

Are there identified risks which would prevent you from achieving significant results in the project ?

The only main risk is that the timing of cluster access may not work out well, e.g., coinciding with a major deadline, teaching, or a conference. We are a small team of two researchers, so our cycles are limited. We may also discover previously unknown scalability bottlenecks as a result of the testing, although we would consider this a success rather than a risk.

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

No.

Please state your contributions to the open source community and any other relevant initiatives

Our research software, data sets, experimental infrastructure, and scripts are open-source (https://github.com/camsas), and we contribute to the Kubernetes SIG-scheduling interest group.
If we use the CNCF cluster for a scale-up experiment mentioned in a research publication or blog post, we will acknowledge the support by the CNCF as we would acknowledge any other industrial support of our research.

Number of nodes requested (minimum 20 nodes, maximum 500 nodes). In Q3, maximum increases to 1000 nodes.

100, with possibility to increase to 500.

Duration of request (minimum 24 hours, maximum 2 weeks)

1 week.

With or Without an operating system (Restricted to CNCF pre-defined OS and versions)?

With OS, if Ubuntu (14.04 LTS or 16.04 LTS) is available.

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

It will provide better container scheduling, potentially tighter packing of workloads with reduced interference, and validate the scalability of the min-cost flow optimization scheduling approach in a real-world environment.

Any other relevant details we should know about while preparing the infrastructure?

Some of our experiments involve running applications that generate a high network load (i.e., saturating a 10 Gbit/s link).

If you are interested in filing a request for access to the CNCF CIL, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

Sambo

Chea

[email protected]

SETEC Institute

Student

Cloud Infrastructure

Briefly describe the project

Which members of the CNCF community and/or end-users would benefit from your work?

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

What kind of machines and how many do you expect to use (see: https://www.packet.net/bare-metal/)?

What OS and networking are you planning to use (see: https://help.packet.net/technical/infrastructure/supported-operating-systems)?

Please state your contributions to the open source community and any other relevant initiatives

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

Any other relevant details we should know about while preparing the infrastructure?

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

Ken

Owens

[email protected]

Cisco

CTO Cloud Native Platforms

Devnet Cloud Native Creations

Create an easy onboarding capability for CNCF cluster and CNCF projects to create an ecosystem of sample demos and appliations leveraging CNCF projects and microservices architectures.

Devnet coud native creations will provide a simple, easy to use, developer experience to enable the creationg of cloud native applications in a sandbox e4nviornment on the cluster. The types of creations are focused around innovative projects leveraging CNCF projects to discovering all the cool ideas around cloud native projects. Play with any demos and stay tuned to the latest ideas from the CNCF community. The last objective to to gather feedback and create a collaborative contributor environment. The CNCF community can take the feedback from these creations to to improve their projects. Engage in the community and give feedback to help each other creating a better product.

Metrics will be measured in terms of projects leveraged, line of code developed, PRs and Issues, as well as services created and modified.

Which members of the CNCF community and/or end-users would benefit from your work?

All projects, current and interested, all members - companies and end users.

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

yes. Today at ciscoshipped.com. Please to update and modify to be vendor agnostic and fully open sourced.

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to do this within 2 months of cluster use?

Yes

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

Yes

Are there identified risks which would prevent you from achieving significant results in the project ?

No

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

Please list project titles associated with prior CNCF cluster usage.

Please list contributions to open source initiatives for projects listed in the last question. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

Please state your contributions to the open source community and any other relevant initiatives

Mantl, Shipped, Kubernetes, Consol, Terreform, Traefik, Cloud Foundry

Number of nodes requested (minimum 20 nodes, maximum ~400 nodes).

400 Nodes

Preferred node flavor, ratio if mixed (compute, storage, any).

80%compute

Duration of request (minimum 24 hours, maximum 2 weeks).

2 weeks

With or Without an Operating System (restricted to CNCF predefined OS and versions as in README)?

RHEL or Centos

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

provide a ecsosystem for developing, creating, and collaborating cloud natives architecutures

Any other relevant details we should know about while preparing the infrastructure?

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

Last Name

Email

Company/Organization

Job Title

Project Title

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

Briefly describe the project

Do you intend to measure specific metrics during the work? Please describe briefly

Which members of the CNCF community and/or end-users would benefit from your work?

Is the code that you’re going be running 100% open source? If so, what is the URL or URLs where it is located?

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to this within 2 months of cluster use?

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

Are there identified risks which would prevent you from achieving significant results in the project ?

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

Please list project titles associated with prior CNCF cluster usage.

Please list contributions to open source initiatives for projects listed in the last question. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

Please state your contributions to the open source community and any other relevant initiatives

Number of nodes requested (minimum 20 nodes, maximum 500 nodes). In Q3, maximum increases to 1000 nodes.

Duration of request (minimum 24 hours, maximum 2 weeks)

With or Without an operating system (Restricted to CNCF pre-defined OS and versions)?

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

Any other relevant details we should know about while preparing the infrastructure?

If you are interested in filing a request for access to the CNCF CIL, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

Thomas

Last Name

Felder

Email

[email protected]

Company/Organization

N/A

Job Title

dev

Project Title

analyticssandbox

Briefly describe the project

data-mining / social sentiment analysis experiements / container orchestration etc

Which members of the CNCF community and/or end-users would benefit from your work?

data scientists

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

yes – https://github.com/tfmolch

What kind of machines and how many do you expect to use (see: https://www.packet.net/bare-metal/)?

3 midsize VMs

What OS and networking are you planning to use (see: https://help.packet.net/technical/infrastructure/supported-operating-systems)?

debian

Please state your contributions to the open source community and any other relevant initiatives

none worth mentioning yet – I'm a self-taught programmer!

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

well at the very least I'll be testing/bug reporting

Any other relevant details we should know about while preparing the infrastructure?

SAN storage shared between the nodes would be a plus!

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

Xiang

Last Name

Li

Email

[email protected]

Company/Organization

CoreOS Inc.

Job Title

Project Title

etcd

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

Distributed reliable key-value store for the most critical data of a distributed system

Briefly describe the project

Distributed reliable key-value store for the most critical data of a distributed system

Do you intend to measure specific metrics during the work? Please describe briefly

Improve reliability, scalability of etcd

Which members of the CNCF community and/or end-users would benefit from your work?

Kubernetes and other distributed system in general.

Is the code that you’re going be running 100% open source? If so, what is the URL or URLs where it is located?

Yes. https://github.com/coreos/etcd

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to this within 2 months of cluster use?

Yes.

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

Yes.

Are there identified risks which would prevent you from achieving significant results in the project ?

No.

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

No

Please list project titles associated with prior CNCF cluster usage.

Please list contributions to open source initiatives for projects listed in the last question. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

Please state your contributions to the open source community and any other relevant initiatives

Maintainer of etcd, Kubernetes.

Number of nodes requested (minimum 20 nodes, maximum 500 nodes). In Q3, maximum increases to 1000 nodes.

80

Duration of request (minimum 24 hours)

open ended

With or Without an operating system (Restricted to CNCF pre-defined OS and versions)?

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

etcd is the critical part of distributed system, including orchestration and microservices.

Making etcd more reliable and scalable improves other applications that rely on it.

Any other relevant details we should know about while preparing the infrastructure?

If you are interested in filing a request for access to the CNCF CIL, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

Marc

Chisinevski

[email protected]

F5 Networks

Solution Architect

Project Title

Kubernetes in hybrid environments, please see https://kccncna17.sched.com/event/CU7L/kuberneters-in-hybrid-environments-using-cloud-interconnect-a-marc-chisinevski-f5-networks

Which members of the CNCF community and/or end-users would benefit from your work?

Istio/Envoy/Kubernetes

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

https://github.com/F5Networks/k8s-bigip-ctlr/

What kind of machines and how many do you expect to use (see: https://www.packet.net/bare-metal/)?

Type 1E

What OS and networking are you planning to use (see: https://www.packet.net/bare-metal/)?

Public Internet

Please state your contributions to the open source community and any other relevant initiatives

https://sourceforge.net/projects/assetmng/files/assetmng/
https://sourceforge.net/projects/assetmng/files/assetmng/v1.0/Asset_Management_and_Risk_Assessment___Functional_and_Technical_Specifications___plus_Linux_installation.pdf/download

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

Ease migration to managed Kubernetes environements (Google Container Engine, Azure Container Services etc) and enabling hybrid deployments.

Any other relevant details we should know about while preparing the infrastructure?

First Name

Ihor

Last Name

Dvoretskyi

Email

[email protected]

Company/Organization

CNCF

Job Title

Developer Advocate

Project Title

All existing (and related) CNCF projects - https://www.cncf.io/projects/

Which members of the CNCF community and/or end-users would benefit from your work?

Everyone would!

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

Yes. GitHub links are available here - https://www.cncf.io/projects/

What kind of machines and how many do you expect to use (see: https://www.packet.net/bare-metal/)?

1 * TYPE 1

What OS and networking are you planning to use (see: https://www.packet.net/bare-metal/)?

Ubuntu 16.04 LTS

Please state your contributions to the open source community and any other relevant initiatives

https://github.com/idvoretskyi
https://github.com/kubernetes/community/blob/master/sig-product-management/README.md
https://github.com/kubernetes/community/blob/master/sig-openstack/README.md
https://www.cncf.io/blog/2017/09/18/meet-cncfs-newest-developer-advocate/

Any other relevant details we should know about while preparing the infrastructure?

Not yet.

First Name

David

Last Name

Aronchick

Email

[email protected]

Company/Organization

Google

Job Title

Product Manager

Project Title

Kubernetes

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

Testing scale on bare metal

Briefly describe the project

We want to test scale on bare metal.

Do you intend to measure specific metrics during the work? Please describe briefly

Yes, whether or not we pass kubemark.

Which members of community and/or end-users would benefit from your work?

All

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to this within 2 months of cluster use?

Yes, we will change benchmarks.

Are there identified risks which would prevent you from achieving significant results in the project ?

No

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip questions 2 through 4.

no

Please list project titles associated with prior CNCF cluster usage.

Please list contributions to open source initiatives for projects listed in question 2. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

Please state your contributions to the open source community and any other relevant initiatives

Number of nodes requested (minimum 20 nodes, maximum 500 nodes). In Q3, maximum increases to 1000 nodes.

10000 Nodes

Duration of request (minimum 24 hours)

72 hours

With or Without an operating system (Restricted to CNCF pre-defined OS and versions)?

With

Any other relevant details we should know about while preparing the infrastructure?

No

First Name

Jeremy

Last Name

Eder

Email

[email protected]

Company/Organization

Red Hat

Job Title

Engineer

Project Title

Deploying 1000 nodes of OpenShift on the CNCF Cluster (Part 2)

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

We are interested in:
Working through the operational concepts necessary to handle a large bare metal scale-out environment.
Comparing the behavior of Kubernetes on OpenStack with Kubernetes on bare metal.
Run our newly developed workload generators and test suite
Utilizing newer features in Kubernetes to make use of bare metal hardware features.

Briefly describe the project

To compliment our earlier work on the CNCF lab (https://cncf.io/news/blogs/2016/08/deploying-1000-nodes-openshift-cncf-cluster-part-1) we would like to propose a full-lab scale test scenario once the CNCF lab is at full capacity. We will look to quantify improved performance when running on bare metal instead of virtualized. We will conduct some specific HTTP load testing and storage (persistent volume) performance testing.

Do you intend to measure specific metrics during the work? Please describe briefly

Yes, we will use our pbench framework https://github.com/distributed-system-analysis/pbench to capture metrics on each run. We expect this to involve Prometheus, a CNCF project, to the extent that we use it for gathering Kubernetes API server metrics.

Which members of the CNCF community and/or end-users would benefit from your work?

Kubernetes, Prometheus, end users who are looking to run high performance workloads on bare metal environments. Also fluentd if that is accepted (OpenShift uses fluentd for logging).

Is the code that you’re going be running 100% open source? If so, what is the URL or URLs where it is located?

Yes: https://github.com/openshift

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to this within 2 months of cluster use?

Yes, we have already open-sourced everything we write and we have shared significant amounts of data via blog and public-speaking engagements at industry conferences.

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

Yes.

Are there identified risks which would prevent you from achieving significant results in the project ?

Not that we are aware of. We have good experience handling OpenShift at scale and we are proposing a two-phase approach where we prototype on 100 nodes (this proposal) with an adjacently-scheduled phase at full-lab scale of 1000 nodes.

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

Yes.

Please list project titles associated with prior CNCF cluster usage.

Deploying 1000 nodes of OpenShift on the CNCF Cluster (Part 1)

Please list contributions to open source initiatives for projects listed in the last question. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Over 30 bugs were filed across projects such as Kubernetes, OpenShift and Ansible.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

No.

Please state your contributions to the open source community and any other relevant initiatives

Red Hat is a fully open-source company. Red Hat is a platinum founding member of CNCF, a contributor to docker, kubernetes, openshift origin, and many more.

Number of nodes requested (minimum 20 nodes, maximum 500 nodes). In Q3, maximum increases to 1000 nodes.

1000 nodes. (We realize that there will be slightly less than 1000 available for us to use).

Duration of request (minimum 24 hours, maximum 2 weeks)

2 weeks at least.

Please schedule this immediately after #21 so that we can retain our existing environment, and expand it on to the additional nodes.

With or Without an operating system (Restricted to CNCF pre-defined OS and versions)?

With, RHEL7.3

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

We are working to push beyond control plane scalability to simulate realistic bare metal scenarios. This will include loading applications that represent an accurate mix of what we have seen in the wild. Being able to do this at higher scale levels will help us to discover best practices from an architecture standpoint as well as to help validate capacity planning formulas to see if they hold up at higher scale and load levels.

Any other relevant details we should know about while preparing the infrastructure?

First Name

Jeremy

Last Name

Eder

Email

[email protected]

Company/Organization

Red Hat

Job Title

Engineer

Project Title

Deploying 1000 nodes of OpenShift on the CNCF Cluster (Part 2)

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

We are interested in:
Working through the operational concepts necessary to handle a large bare metal scale-out environment.
Comparing the behavior of Kubernetes on OpenStack with Kubernetes on bare metal.
Run our newly developed workload generators and test suite
Utilizing newer features in Kubernetes to make use of bare metal hardware features.

Briefly describe the project

To compliment our earlier work on the CNCF lab (https://cncf.io/news/blogs/2016/08/deploying-1000-nodes-openshift-cncf-cluster-part-1) we would like to propose a full-lab scale test scenario once the CNCF lab is at full capacity. We will look to quantify improved performance when running on bare metal instead of virtualized. We will conduct some specific HTTP load testing and storage (persistent volume) performance testing.

Do you intend to measure specific metrics during the work? Please describe briefly

Yes, we will use our pbench framework https://github.com/distributed-system-analysis/pbench to capture metrics on each run. We expect this to involve Prometheus, a CNCF project, to the extent that we use it for gathering Kubernetes API server metrics.

Which members of the CNCF community and/or end-users would benefit from your work?

Kubernetes, Prometheus, end users who are looking to run high performance workloads on bare metal environments. Also fluentd if that is accepted (OpenShift uses fluentd for logging).

Is the code that you’re going be running 100% open source? If so, what is the URL or URLs where it is located?

Yes: https://github.com/openshift

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to this within 2 months of cluster use?

Yes, we have already open-sourced everything we write and we have shared significant amounts of data via blog and public-speaking engagements at industry conferences.

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

Yes.

Are there identified risks which would prevent you from achieving significant results in the project ?

Not that we are aware of. We have good experience handling OpenShift at scale and we are proposing a two-phase approach where we prototype on 100 nodes (this proposal) with an adjacently-scheduled phase at full-lab scale of 1000 nodes.

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

Yes.

Please list project titles associated with prior CNCF cluster usage.

Deploying 1000 nodes of OpenShift on the CNCF Cluster (Part 1)

Please list contributions to open source initiatives for projects listed in the last question. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Over 30 bugs were filed across projects such as Kubernetes, OpenShift and Ansible.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

No.

Please state your contributions to the open source community and any other relevant initiatives

Red Hat is a fully open-source company. Red Hat is a platinum founding member of CNCF, a contributor to docker, kubernetes, openshift origin, and many more.

Number of nodes requested (minimum 20 nodes, maximum 500 nodes). In Q3, maximum increases to 1000 nodes.

Phase 1 (this request) 100 compute nodes and 10 storage nodes.
Phase 2 (upcoming request) 1000 compute nodes.

Duration of request (minimum 24 hours, maximum 2 weeks)

Phase 1 two weeks. Phase 2 two weeks. Both phases must be adjacent in order for us to get what we need done in the 2 week periods.

With or Without an operating system (Restricted to CNCF pre-defined OS and versions)?

With, RHEL7.3

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

We are working to push beyond control plane scalability to simulate realistic bare metal scenarios. This will include loading applications that represent an accurate mix of what we have seen in the wild. Being able to do this at higher scale levels will help us to discover best practices from an architecture standpoint as well as to help validate capacity planning formulas to see if they hold up at higher scale and load levels.

Any other relevant details we should know about while preparing the infrastructure?

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

Thanatas

Last Name

Pongpanotkorn

Email

[email protected];[email protected]

Company/Organization

@github

Job Title

Developer

Project Title

xaxiclouddev,.inc.co.th

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

Oomnoi Krathumban Thailand 74130

Briefly describe the project

Auto deployer

Do you intend to measure specific metrics during the work? Please describe briefly

No, i don't have knowhow.

Which members of community and/or end-users would benefit from your work?

[email protected]

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to this within 2 months of cluster use?

Yes

Are there identified risks which would prevent you from achieving significant results in the project ?

Undentified it.

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip questions 2 through 4.

Please list project titles associated with prior CNCF cluster usage.

Please list contributions to open source initiatives for projects listed in question 2. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

ZiplineStatusChecker
hubot
xaxiclouddev.com

Have you ever been denied usage of the cluster in the past? If so, please explain why.

I don't know howto and don't have more free day.

Please state your contributions to the open source community and any other relevant initiatives

Number of nodes requested (minimum 20 nodes, maximum 500 nodes). In Q3, maximum increases to 1000 nodes.

Duration of request (minimum 24 hours)

With or Without an operating system (Restricted to CNCF pre-defined OS and versions)?

Any other relevant details we should know about while preparing the infrastructure?

Hi, it would be useful if cluster users could have (read-only) visibility into:

• per-port utilization and statistics (such as error counters) from both ToR and core/interconnect switches
• syslog data from networking gear

Without this, debugging performance, link issues, driver/firmware issues at the host level becomes very difficult. Cluster users could make more progress if they had such visibility and would reduce turn-around time for resolving issues.

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

Camille

Last Name

Fournier

Email

[email protected]

Company/Organization

ZooKeeper

Job Title

Project Title

ZooKeeper

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

Distributed coordination service

Briefly describe the project

Distributed Coordination Service

Do you intend to measure specific metrics during the work? Please describe briefly

This will be used to help create a reproducible process for vetting release candidates

Which members of the CNCF community and/or end-users would benefit from your work?

Anyone using Apache ZooKeeper, which is a very long list

Is the code that you’re going be running 100% open source? If so, what is the URL or URLs where it is located?

Yes, zooeeper.apache.org

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to this within 2 months of cluster use?

Anything that becomes a reusable artifact will be published as source code, and I certainly hope we can get something done in the next 2 months

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

Maybe? Maybe? Maybe?

Are there identified risks which would prevent you from achieving significant results in the project ?

Fully volunteer group is busy

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

no

Please list project titles associated with prior CNCF cluster usage.

Please list contributions to open source initiatives for projects listed in the last question. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

Please state your contributions to the open source community and any other relevant initiatives

TOC member for CNCF
PMC member for Apache ZooKeeper

Number of nodes requested (minimum 20 nodes, maximum 500 nodes). In Q3, maximum increases to 1000 nodes.

50 nodes

Duration of request (minimum 24 hours)

open-ended

With or Without an operating system (Restricted to CNCF pre-defined OS and versions)?

with

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

reproducible end-to-end and stress testing of distributed systems is a good thing for all of us

Any other relevant details we should know about while preparing the infrastructure?

JVM

Everyone,

Due to the expansion process going on we will be scheduling a maintenance window soon. We are not yet sure about the exact schedule but it will probably take time around end of January / beginning of February and last up to a few days.

Because of this, no new requests will be accepted until after the maintenance window. If required, the current requests will be allowed to extend their work week by week until we are sure about the date.

Feel free to reach us here in case of questions!

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

Ben

Last Name

Kochie

Email

[email protected]

Company/Organization

Prometheus Team

Job Title

Project Title

Benchmarking

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

• Update comparison benchmarks with competing systems.
• Provide a stable test ground for testing for scaling issues

Briefly describe the project

We would like to build a Prometheus test setup for making performance optimizations that are not possible to test in standard CI pipelines.

Do you intend to measure specific metrics during the work? Please describe briefly

• CPU use for Prometheus and exporter(s)
• IOPs used by Prometheus server when ingesting and doing maintenance operations.

Which members of the CNCF community and/or end-users would benefit from your work?

Prometheus community in general.

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

https://prometheus.io

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to do this within 2 months of cluster use?

Yes

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

Yes, we would use and monitor containers as part of the workload test.

Are there identified risks which would prevent you from achieving significant results in the project ?

None expected.

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

No

Please list project titles associated with prior CNCF cluster usage.

Please list contributions to open source initiatives for projects listed in the last question. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

Please state your contributions to the open source community and any other relevant initiatives

Prometheus Team member

Number of nodes requested (minimum 20 nodes, maximum ~400 nodes).

50-100

Preferred node flavor, ratio if mixed (compute, storage, any).

• 4-5 storage nodes.
• The rest can be compute.

Duration of request (minimum 24 hours, maximum 2 weeks).

2 weeks.

With or Without an Operating System (restricted to CNCF predefined OS and versions as in README)?

Ubuntu 16.04

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

It will improve Prometheus performance and efficiency.

Any other relevant details we should know about while preparing the infrastructure?

If you are interested in filing a request for access to the CNCF CIL, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

VIJAY

Last Name

PRAKASH

Email

[email protected]

Company/Organization

CGE

Job Title

SC

Project Title

SC

Briefly describe the project

Migration project for application from on prem to cloud

Which members of the CNCF community and/or end-users would benefit from your work?

Small and Mid business members

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

What kind of machines and how many do you expect to use (see: https://www.packet.net/bare-metal/)?

I haven't decided one, but would start with something small

What OS and networking are you planning to use (see: https://help.packet.net/technical/infrastructure/supported-operating-systems)?

Linux and Windows

Please state your contributions to the open source community and any other relevant initiatives

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

Vm to Containers

Any other relevant details we should know about while preparing the infrastructure?

We should eventually have a clickthrough.

If you are interested in filing a request for access to the CNCF Community Cluster, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

Frank

Last Name

Scholten

Email

[email protected]

Company/Organization

Container Solutions

Job Title

Senior Software Engineer

Project Title

Mesos Elasticsearch

What existing problem or community challenge does this work address? ( Please include any past experience or lessons learned )

Deploying and running Elasticsearch on a Mesos cluster

Briefly describe the project

Deploying and running Elasticsearch on a Mesos cluster

Do you intend to measure specific metrics during the work? Please describe briefly

Which members of the CNCF community and/or end-users would benefit from your work?

Anyone using Mesos and/or Elasticsearch

Is the code that you’re going be running 100% open source? If so, what is the URL or URLs where it is located?

Yes. https://github.com/mesos/elasticsearch

Do you commit to publishing your results and upstreaming the open source code resulting from your work? Do you agree to this within 2 months of cluster use?

Yes

Will your testing involve containers? If not, could it? What would be entailed in changing your processes to containerize your workload?

Yes. Mesos Elasticsearch can run in Jar mode or in Docker mode by specifying a flag when running the scheduler.

Are there identified risks which would prevent you from achieving significant results in the project ?

Contributors are busy

Have you requested CNCF cluster resources or access in the past? If ‘no’, please skip the next three questions.

No

Please list project titles associated with prior CNCF cluster usage.

Please list contributions to open source initiatives for projects listed in the last question. If you did not upstream the results of the open source initiative in any of the projects, please explain why.

Have you ever been denied usage of the cluster in the past? If so, please explain why.

Please state your contributions to the open source community and any other relevant initiatives

Committer on Apache Whirr (now in attic). Committer on Apache Mahout (currently inactive). Creator of minimesos: https://github.com/ContainerSolutions/minimesos

Number of nodes requested (minimum 20 nodes, maximum 500 nodes). In Q3, maximum increases to 1000 nodes.

100

Duration of request (minimum 24 hours)

One week

With or Without an operating system (Restricted to CNCF pre-defined OS and versions)?

With a Linux operating system that supports Docker

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

End-to-end testing of deployment, scaling and failover scenarios will help us improve the quality of Mesos Elasticsearch framework and provide information that is useful for other projects.

Any other relevant details we should know about while preparing the infrastructure?

We will be running on Mesos

If you are interested in filing a request for access to the CNCF CIL, please fill out the details below.

First Name

Lauri

Last Name

Ojansivu

Email

[email protected]

Company/Organization

http://www.xet7.org/about-me

Job Title

CEO of my one person company

Project Title

Wekan

Briefly describe the project

Open Source Trello-like kanban

Which members of the CNCF community and/or end-users would benefit from your work?

All that want to self-host kanban board and have control of the data.

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

Website:
https://wekan.github.io

Repo:
https://github.com/wekan/wekan

MIT License:
https://github.com/wekan/wekan/blob/devel/LICENSE

Current platforms where Wekan runs:
https://github.com/wekan/wekan/wiki/Platforms

What kind of machines and how many do you expect to use (see: https://www.packet.net/bare-metal/)?

Servers at Europe, Amsterdam.

Type 3, Type 1E and Type 2A

1. Type 3:

• Trying to simulate and find fixes for large scale usage to make Wekan more scaleable, for example by having DTrace running on Triton on your provided hardware. Running Docker containers.

2. Type 1E:

• Trying to build Proxmox LXC version of Wekan. Wekan is usually built on Debian 8.9 or Ubuntu 14.04.

3. Type 2A:

• Trying to build ARM version of Wekan. Debian 8 or 9, depending what is available.

Other uses:

• Building VirtualBox images etc for Wekan releases, like I currently do on my laptop and have release at https://wekan.github.io
• Building and testing with crosscloud to multiple clouds
• Add more tests and have building for different platforms work for every new pull request and commit, having results integrated to GitHub
• Add more platforms and tests for them like Ubuntu LXD, install scripts to various operating systems

What OS and networking are you planning to use (see: https://www.packet.net/bare-metal/)?

Internet.

Please state your contributions to the open source community and any other relevant initiatives

I have 920 contributions to various repos at GitHub in the last year:
https://github.com/xet7

I'm maintainer of Wekan, 444 commits:
https://github.com/wekan/wekan/graphs/contributors

I have helped to keep Wekan alive, by continuing Wekan in a fork, and got a chance to merge it back:
https://github.com/wekan/wekan/wiki/FAQ#what-was-wekan-fork--wefork

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

Wekan has many integrations coming with IFTTT with Huginn or Flogo, Gogs git repo hosting, etc at Integrations wiki page.

For these, advancement is in having Docker Compose script and other ways to orchestrate on various public and private cloud platforms, easy ways make more integrations, and easy deployment and management of Wekan and other integrated Open Source software.

Wekan wiki press page has link to Hacker News article where someone did say that they use Wekan to store confidential patient data in Wekan, so Wekan is mission critical for some.

Any other relevant details we should know about while preparing the infrastructure?

I have worked as SysAdmin and AWS Cloud Architect, so most things I could probably be able to setup myself, though help is very welcome, like in setting up Triton, Proxmox etc environments. If you have some example Terraform or Ansible scripts to help with setting up various different environments, it would help.

For Google Cloud, I currently don't know how to enable websockets so Wekan works. I also have not tried Wekan yet at Azure. More about this at Platforms wiki page.

First Name

Stephen

Last Name

Day

Email

stephen at docker dot com

Company/Organization

Docker, Inc/CNCF/containerd

Job Title

Maintainer/Software Engineer

Project Title

containerd

Briefly describe the project

An open and reliable container runtime: https://containerd.io.

At this time, the cluster resources requested will be used to support alternative platform builds, including but not limited to ARM, s390x and power systems. While we would like to use hosted services, the support for less popular architectures.

Which members of the CNCF community and/or end-users would benefit from your work?

These resources will be used to build containerd on every pull request, merge and build releases on alternative platforms. This will allow contributors to have confidence in their changes without having to try them across platforms. This will benefit maintainers by ensuring that testing is equal across platforms. Users will benefit from a better tested container runtime.

We hope to also benefit the kubernetes community by providing a stable container runtime that will work across any platform.

The ARM community is steadily growing and we see stability there as an important part of containerd's offering. s390x and power are heavily used in enterprise applications.

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

Yes, https://github.com/containerd/containerd

What kind of machines and how many do you expect to use (see: https://www.packet.net/bare-metal/)?

• 1x Type 2 as an amd64 head node for running builds.
  • This will run gitlab CI (or jenkins, if necessary)
  • Required large, redundant storage to provide head room for build database (postgres)
• 1x Type 2A will run gitlab-runner for ARM builds

We'll also need a place to back up build database in case of catastrophic failure. We will not require hot standby, as impact of failure will be low.

What OS and networking are you planning to use (see: https://www.packet.net/bare-metal/)?

Ubuntu 17.04

Please state your contributions to the open source community and any other relevant initiatives

I am a maintainer on Moby, OCI Image Spec, containerd, SwarmKit, Docker Registry and other smaller projects.

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

With containerd at the base of containerization, it is a critical component of the cloud native "water cycle". Having solid cross-platform support is a must.

Any other relevant details we should know about while preparing the infrastructure?

Thanks to all those that have helped with getting this proposal together!

cc @containerd-maintainers

I'm not entirely certain if this is the appropriate place to put this, but I believe it will leverage these resources.

The CNCF hosts a fair number of different projects which are controlled by a number of different vendors. The purpose of this request is to start the conversation about the establishment of a shared infrastructure (vendor neutral) area that can be used as a test bed for these projects. This ensures that releases have to go through a common set of shared resources that no-one vendor can explicitly control but they can all contribute to. ~= apache-infra

/cc @caniszczyk @spiffxp

If you are interested in filing a request for access to the CNCF CIL, please fill out the details below.

If you are just filing an issue, ignore/delete those fields and file your issue.

First Name

Rom

Last Name

Bob

Email

[email protected]

Company/Organization

CICD XYZ

Job Title

DevOps

Project Title

Infrastructure management

Briefly describe the project

Infrastructure management toolset for opensource projects CICD solutions not requiring hosted CI services for SDLM

Which members of the CNCF community and/or end-users would benefit from your work?

Is the code that you’re going to run 100% open source? If so, what is the URL or URLs where it is located?

Yes, TBD

What kind of machines and how many do you expect to use (see: https://www.packet.net/bare-metal/)?

What OS and networking are you planning to use (see: https://www.packet.net/bare-metal/)?

Please state your contributions to the open source community and any other relevant initiatives

How will this testing advance cloud native computing (specifically containerization, orchestration, microservices or some combination).

Any other relevant details we should know about while preparing the infrastructure?

CIL_proposal_pullen.pdf