Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

perf test env setup enhancement works #1036

Closed
yb01 opened this issue Mar 18, 2021 · 4 comments · Fixed by #1212 or #1332
Closed

perf test env setup enhancement works #1036

yb01 opened this issue Mar 18, 2021 · 4 comments · Fixed by #1212 or #1332
Assignees

Comments

@yb01
Copy link
Collaborator

yb01 commented Mar 18, 2021

This issue intends to capture needed improvements in perf test tools, namely, kube-up, kubemark, clusterloader etc. for Arktos 430 or beyound.

  1. reduce test env setup time: such as parepare VMs in parallel, start hollow-nodes in parallel, cleanup VMs in parallel
  2. variable naming consistency
  3. make clear cut for AWS cloud providers -- currently some logic are in start-kubemark.sh which can be moved to AWS related libs
@sonyafenge
Copy link
Collaborator

these two files need be deleted when run stop-kubemark.sh, this will caused start-kubemark failed if already existing.
/tmp/haproxy_cfg_generator
/tmp/saved_tenant_ips.txt

@sonyafenge
Copy link
Collaborator

Detailed design information for this enhancement attached:
kubeup-kubemark.script.pptx

@sonyafenge
Copy link
Collaborator

sonyafenge commented Oct 20, 2021

Steps and plans for this enhancement tasks:

@sonyafenge
Copy link
Collaborator

Keep this issue opened, still working on related items.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants