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.

Sign up for GitHub

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

Jump to bottom

add router-scale regression script OCP-43281 #803

Merged
merged 1 commit into from
Jan 20, 2025
Merged

add router-scale regression script OCP-43281 #803

merged 1 commit into from
Jan 20, 2025

Conversation

qiliRedHat
Copy link
Contributor

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Jan 17, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiliRedHat

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 17, 2025
@qiliRedHat qiliRedHat mentioned this pull request Jan 17, 2025
Merged
@qiliRedHat qiliRedHat force-pushed the router-scale branch 4 times, most recently from 62d8532 to bd435be Compare January 17, 2025 12:37
@qiliRedHat
Copy link
Contributor Author

qiliRedHat commented Jan 17, 2025 •
edited
Loading

Did a fake test by comment out the real run command run.sh with Jenkins.

01-17 20:32:56.245  + script=router-scale.sh
01-17 20:32:56.245  + cd perfscale_regression_ci/scripts/scalability/router-scale
01-17 20:32:56.245  + chmod +x router-scale.sh
01-17 20:32:56.245  + set -o pipefail
01-17 20:32:56.245  + ./router-scale.sh
01-17 20:32:56.245  + tee /home/jenkins/ws/workspace/ibranch-pipeline_regression-test/output.out
01-17 20:32:56.245  +++ set +ex
01-17 20:32:56.245  [INFO] Patch threadCount as 4
01-17 20:32:56.812  ingresscontroller.operator.openshift.io/default patched
01-17 20:32:57.110          - name: ROUTER_THREADS
01-17 20:32:57.110            value: "4"
01-17 20:32:57.110  [INFO] run ingress-perf with thread=4, replica=2
01-17 20:32:57.365  Cloning into 'e2e-benchmarking'...
01-17 20:32:57.619  Note: switching to '5a8ba24acfc977fa0f07b109d50cd7256efad21c'.
01-17 20:32:57.619  
01-17 20:32:57.619  You are in 'detached HEAD' state. You can look around, make experimental
01-17 20:32:57.619  changes and commit them, and you can discard any commits you make in this
01-17 20:32:57.619  state without impacting any branches by switching back to a branch.
01-17 20:32:57.619  
01-17 20:32:57.619  If you want to create a new branch to retain commits you create, you may
01-17 20:32:57.619  do so (now or later) by using -c with the switch command. Example:
01-17 20:32:57.619  
01-17 20:32:57.619    git switch -c <new-branch-name>
01-17 20:32:57.619  
01-17 20:32:57.619  Or undo this operation with:
01-17 20:32:57.619  
01-17 20:32:57.619    git switch -
01-17 20:32:57.619  
01-17 20:32:57.619  Turn off this advice by setting config variable advice.detachedHead to false
01-17 20:32:57.619  
01-17 20:32:57.619  ~/ws/workspace/ibranch-pipeline_regression-test/perfscale_regression_ci/scripts/scalability/router-scale/e2e-benchmarking/workloads/ingress-perf ~/ws/workspace/ibranch-pipeline_regression-test/perfscale_regression_ci/scripts/scalability/router-scale
01-17 20:32:57.619  [INFO] Will run ingress-perf with config config/standard.yml
01-17 20:32:57.619  ~/ws/workspace/ibranch-pipeline_regression-test/perfscale_regression_ci/scripts/scalability/router-scale
01-17 20:32:57.619  ~/ws/workspace/ibranch-pipeline_regression-test/perfscale_regression_ci/scripts/scalability/router-scale/e2e-benchmarking/workloads/ingress-perf ~/ws/workspace/ibranch-pipeline_regression-test/perfscale_regression_ci/scripts/scalability/router-scale
01-17 20:32:57.619  [INFO] Will run ingress-perf with config ../../../standard-3replicas.yml
01-17 20:32:57.619  ~/ws/workspace/ibranch-pipeline_regression-test/perfscale_regression_ci/scripts/scalability/router-scale
01-17 20:32:57.619  [INFO] scale infra replicas to 4
01-17 20:32:58.575  machineset.machine.openshift.io/qili-re-9bvlb-infra-us-east-2a scaled
01-17 20:32:58.829  NAME                              DESIRED   CURRENT   READY   AVAILABLE   AGE
01-17 20:32:58.829  qili-re-9bvlb-infra-us-east-2a    2         2         2       2           3h9m
01-17 20:32:58.829  qili-re-9bvlb-infra-us-east-2b    1         1         1       1           3h4m
01-17 20:32:58.829  qili-re-9bvlb-infra-us-east-2c    1         1         1       1           178m
01-17 20:32:58.829  qili-re-9bvlb-worker-us-east-2a   2         2         2       2           4h54m
01-17 20:32:58.829  qili-re-9bvlb-worker-us-east-2b   3         3         3       3           4h54m
01-17 20:32:58.829  qili-re-9bvlb-worker-us-east-2c   3         3         3       3           4h54m
01-17 20:32:58.829  [INFO] run ingress-perf with thread=4, replica=4
01-17 20:32:58.829  ~/ws/workspace/ibranch-pipeline_regression-test/perfscale_regression_ci/scripts/scalability/router-scale/e2e-benchmarking/workloads/ingress-perf ~/ws/workspace/ibranch-pipeline_regression-test/perfscale_regression_ci/scripts/scalability/router-scale
01-17 20:32:58.829  [INFO] Will run ingress-perf with config ../../../standard-4replicas.yml
01-17 20:32:58.829  ~/ws/workspace/ibranch-pipeline_regression-test/perfscale_regression_ci/scripts/scalability/router-scale
01-17 20:32:58.829  [INFO] Patch threadCount as 8
01-17 20:32:59.083  ingresscontroller.operator.openshift.io/default patched
01-17 20:32:59.337          - name: ROUTER_THREADS
01-17 20:32:59.337            value: "4"
01-17 20:32:59.337  [INFO] run ingress-perf with thread=8, replica=4
01-17 20:32:59.337  ~/ws/workspace/ibranch-pipeline_regression-test/perfscale_regression_ci/scripts/scalability/router-scale/e2e-benchmarking/workloads/ingress-perf ~/ws/workspace/ibranch-pipeline_regression-test/perfscale_regression_ci/scripts/scalability/router-scale
01-17 20:32:59.337  [INFO] Will run ingress-perf with config ../../../standard-4replicas.yml
01-17 20:32:59.337  ~/ws/workspace/ibranch-pipeline_regression-test/perfscale_regression_ci/scripts/scalability/router-scale
01-17 20:32:59.337  [INFO] run ingress-perf with thread=8, replica=3
01-17 20:32:59.337  ~/ws/workspace/ibranch-pipeline_regression-test/perfscale_regression_ci/scripts/scalability/router-scale/e2e-benchmarking/workloads/ingress-perf ~/ws/workspace/ibranch-pipeline_regression-test/perfscale_regression_ci/scripts/scalability/router-scale
01-17 20:32:59.337  [INFO] Will run ingress-perf with config ../../../standard-3replicas.yml
01-17 20:32:59.337  ~/ws/workspace/ibranch-pipeline_regression-test/perfscale_regression_ci/scripts/scalability/router-scale
01-17 20:32:59.337  [INFO] run ingress-perf with thread=8, replica=2
01-17 20:32:59.337  ~/ws/workspace/ibranch-pipeline_regression-test/perfscale_regression_ci/scripts/scalability/router-scale/e2e-benchmarking/workloads/ingress-perf ~/ws/workspace/ibranch-pipeline_regression-test/perfscale_regression_ci/scripts/scalability/router-scale
01-17 20:32:59.337  [INFO] Will run ingress-perf with config config/standard.yml
01-17 20:32:59.337  ~/ws/workspace/ibranch-pipeline_regression-test/perfscale_regression_ci/scripts/scalability/router-scale
01-17 20:32:59.337  [INFO] Test is finished. Pleaset check results in the grafana and dittybopper dashboards.

@qiliRedHat
Copy link
Contributor Author

@SachinNinganure PTAL

@qiliRedHat qiliRedHat changed the title add router-scale regression script add router-scale regression script OCP-43281 Jan 17, 2025
@liqcui
Copy link
Contributor

liqcui commented Jan 20, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 20, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 056d2a2 into openshift:master Jan 20, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mffiedler mffiedler Awaiting requested review from mffiedler

@paigerube14 paigerube14 Awaiting requested review from paigerube14

Assignees

@liqcui liqcui

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@qiliRedHat @liqcui