Request infrastructure for Clusterpedia project

[Iceber]

Please fill out the details below to file a request for access to the CNCF Community Infrastructure Lab. Please note that access is targeted to people working on specific open source projects; this is not designed just to get your feet wet. The most important answer is the URL of the project you'll be working with.

If you're looking to learn Kubernetes and related technologies, please try out Killercoda or Play With Kubernetes instead.

First and Last Name

Iceber Gu

Email

[email protected]

Company/Organization

DaoCloud / Clusterpedia

Job Title

Clusterpedia Maintainer

Project Title (i.e., a summary of what do you want to do, not what is the name of the open source project you're working with)

Clusterpedia Performance tests, eg. massive Cluster pressure testing.
Clusterpedia's e2e, CI and robot.

Briefly describe the project (i.e., what are the details of what you're planning to do with these servers?)

The purpose of Clusterpedia is to support access to large scale multi-clusters, we need to simulate thousands of clusters using kwok, and each cluster needs to have more than 1000 nodes. This requires a lot of memory and cpu power!
In addition, Clusterpedia also needs access to these clusters, and in addition to memory and cpu requirements, it also needs large storage.
So we want to have some virtual or physical machines to support our stress tests, e2e tests and github runner.

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 is your association with that project?

100%

What kind of machines and how many do you expect to use (see: https://deploy.equinix.com/product/bare-metal/servers/)?

m3.small.x86 for github runner, e2e tests and ci
n3.xlarge.x86 for used to deploy clusterpedia and mysql for pressure testing
a3.large.x86 for used to simulate a large number of k8s clusters

What operating system and networking are you planning to use?

ubuntu 22

Any other relevant details we should know about?

[idvoretskyi]

@Iceber thank you!

A few notes in order to make the resources consumption more sustainable:

• would you consider consuming the GitHub-offered large runners instead of the bare metal one on Equinix (they are available for the CNCF projects for free under the CNCF GitHub Enterprise org)?
• would you be able to automate spinning on/off the machines to avoid having them powered in an idle state?

[Iceber]

Hi @idvoretskyi

1. github runner is good for fixed ci process, maybe I will use large runner after adding stress test to pre-release CI process.
   However, it may not be a good fit for some scenarios, such as flexibility tests, and stress tests that require frequent adjustments.

2. yeah, I would only turn them on when they are used
   Also m3.small.x86 is actually mainly used for small scale flexibility tests, so that we don't turn on and waste resources on other large nodes
   If a3.large.x86 isn't available, m3.large.x86 or n2.xlarge.x86 is okay