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

PERFSCALE-2860 - Re-enable jobs on new schedule balancing #51420

Merged
merged 3 commits into from May 23, 2024
Merged

PERFSCALE-2860 - Re-enable jobs on new schedule balancing #51420

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bd84b15
PERFSCALE-2860 - configs update to keep generated configs separate
afcollins May 9, 2024
1057d4c
Remove aws-ovn-fips as per review
afcollins May 22, 2024
89b1d1e
Add generated configs
afcollins May 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 4 additions & 4 deletions .../ocp-qe-perfscale-ci/openshift-qe-ocp-qe-perfscale-ci-main__aro-4.13-nightly-x86-upi.yaml
View file
Open in desktop
Expand Up @@ -40,8 +40,8 @@ tests:
test:
- chain: openshift-qe-node-density-cni
workflow: openshift-qe-installer-azure-aro-upi
- always_run: false
as: node-density-heavy-6nodes
- as: node-density-heavy-6nodes
cron: 0 16 5 * *
steps:
allow_skip_on_success: true
cluster_profile: azure-qe
Expand All @@ -53,8 +53,8 @@ tests:
test:
- chain: openshift-qe-node-density-heavy
workflow: openshift-qe-installer-azure-aro-upi
- always_run: false
as: control-plane-6nodes
- as: control-plane-6nodes
cron: 0 15 2 * *
steps:
allow_skip_on_success: true
cluster_profile: azure-qe
Expand Down
4 changes: 2 additions & 2 deletions ...openshift-qe-ocp-qe-perfscale-ci-main__aws-4.13-nightly-x86-loaded-upgrade-from-4.12.yaml
View file
Open in desktop
Expand Up @@ -30,8 +30,8 @@ resources:
cpu: 100m
memory: 200Mi
tests:
- always_run: false
as: perfscale-aws-5nodes-loaded-upgrade-412to413-periodic
- as: loaded-upgrade-412to413-5nodes
cron: 0 9 17 * *
steps:
allow_skip_on_success: true
cluster_profile: aws-qe
Expand Down
16 changes: 8 additions & 8 deletions ...t-qe/ocp-qe-perfscale-ci/openshift-qe-ocp-qe-perfscale-ci-main__aws-4.13-nightly-x86.yaml
View file
Open in desktop
Expand Up @@ -22,8 +22,8 @@ resources:
cpu: 100m
memory: 200Mi
tests:
- always_run: false
as: control-plane-120nodes
- as: control-plane-120nodes
cron: 0 20 4 * *
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale
Expand All @@ -40,8 +40,8 @@ tests:
- chain: openshift-qe-control-plane
workflow: openshift-qe-installer-aws
timeout: 7h0m0s
- always_run: false
as: control-plane-24nodes
- as: control-plane-24nodes
cron: 0 7 2 * *
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale-qe
Expand Down Expand Up @@ -79,8 +79,8 @@ tests:
test:
- chain: openshift-qe-router-perf
workflow: openshift-qe-installer-aws
- always_run: false
as: node-density-heavy-24nodes
- as: node-density-heavy-24nodes
cron: 0 16 26 * *
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale-qe
Expand All @@ -93,8 +93,8 @@ tests:
- chain: openshift-qe-node-density-heavy
workflow: openshift-qe-installer-aws
timeout: 5h0m0s
- always_run: false
as: data-path-9nodes
- as: data-path-9nodes
cron: 0 4 1 * *
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale
Expand Down
4 changes: 2 additions & 2 deletions ...openshift-qe-ocp-qe-perfscale-ci-main__aws-4.14-nightly-x86-loaded-upgrade-from-4.12.yaml
View file
Open in desktop
Expand Up @@ -37,8 +37,8 @@ resources:
cpu: 100m
memory: 200Mi
tests:
- always_run: false
as: perfscale-aws-5nodes-loaded-upgrade-412to413to414-periodic
- as: loaded-upgrade-412to413to414-5nodes
cron: 0 6 3,17 * *
steps:
allow_skip_on_success: true
cluster_profile: aws-qe
Expand Down
20 changes: 10 additions & 10 deletions ...t-qe/ocp-qe-perfscale-ci/openshift-qe-ocp-qe-perfscale-ci-main__aws-4.14-nightly-x86.yaml
View file
Open in desktop
Expand Up @@ -22,8 +22,8 @@ resources:
cpu: 100m
memory: 200Mi
tests:
- always_run: false
as: control-plane-120nodes
- as: control-plane-120nodes
cron: 0 16 11,25 * *
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale
Expand All @@ -40,8 +40,8 @@ tests:
- chain: openshift-qe-control-plane
workflow: openshift-qe-installer-aws
timeout: 7h0m0s
- always_run: false
as: control-plane-24nodes
- as: control-plane-24nodes
cron: 0 12 2,16 * *
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale-qe
Expand All @@ -54,8 +54,8 @@ tests:
- chain: openshift-qe-control-plane
workflow: openshift-qe-installer-aws
timeout: 5h0m0s
- always_run: false
as: control-plane-etcdencrypt-24nodes
- as: control-plane-etcdencrypt-24nodes
cron: 0 14 2,16 * *
steps:
cluster_profile: aws-perfscale-qe
env:
Expand Down Expand Up @@ -108,8 +108,8 @@ tests:
- chain: openshift-qe-node-density-cni
workflow: openshift-qe-installer-aws
timeout: 5h0m0s
- always_run: false
as: node-density-heavy-24nodes
- as: node-density-heavy-24nodes
cron: 0 12 12,26 * *
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale-qe
Expand All @@ -122,8 +122,8 @@ tests:
- chain: openshift-qe-node-density-heavy
workflow: openshift-qe-installer-aws
timeout: 5h0m0s
- always_run: false
as: data-path-9nodes
- as: data-path-9nodes
cron: 0 10 1,15 * *
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale
Expand Down
4 changes: 2 additions & 2 deletions ...openshift-qe-ocp-qe-perfscale-ci-main__aws-4.15-nightly-x86-loaded-upgrade-from-4.14.yaml
View file
Open in desktop
Expand Up @@ -30,8 +30,8 @@ resources:
cpu: 100m
memory: 200Mi
tests:
- always_run: false
as: perfscale-aws-24nodes-loaded-upgrade-414to415
- as: loaded-upgrade-414to415-24nodes
cron: 0 8 3,17 * *
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale-qe
Expand Down
20 changes: 10 additions & 10 deletions ...t-qe/ocp-qe-perfscale-ci/openshift-qe-ocp-qe-perfscale-ci-main__aws-4.15-nightly-x86.yaml
View file
Open in desktop
Expand Up @@ -31,8 +31,8 @@ resources:
cpu: 100m
memory: 200Mi
tests:
- always_run: false
as: control-plane-120nodes
- as: control-plane-120nodes
cron: 0 8 4,18 * *
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale
Expand All @@ -50,8 +50,8 @@ tests:
- chain: openshift-qe-control-plane
workflow: openshift-qe-installer-aws
timeout: 7h0m0s
- always_run: false
as: control-plane-24nodes
- as: control-plane-24nodes
cron: 0 12 9,23 * *
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale-qe
Expand Down Expand Up @@ -124,8 +124,8 @@ tests:
- chain: openshift-qe-router-perf
workflow: openshift-qe-installer-aws
timeout: 5h0m0s
- always_run: false
as: node-density-heavy-24nodes
- as: node-density-heavy-24nodes
cron: 0 6 5,19 * *
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale-qe
Expand Down Expand Up @@ -166,8 +166,8 @@ tests:
- chain: openshift-qe-node-density-cni
workflow: openshift-qe-installer-aws
timeout: 2h0m0s
- always_run: false
as: data-path-9nodes
- as: data-path-9nodes
cron: 0 22 8,22 * *
afcollins marked this conversation as resolved.
Show resolved Hide resolved
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale
Expand Down Expand Up @@ -283,8 +283,8 @@ tests:
- chain: openshift-qe-node-density-cni
workflow: openshift-qe-installer-aws-cilium
timeout: 5h0m0s
- always_run: false
as: control-plane-etcdencrypt-24nodes
- as: control-plane-etcdencrypt-24nodes
cron: 0 14 9,23 * *
steps:
cluster_profile: aws-perfscale-qe
env:
Expand Down
4 changes: 2 additions & 2 deletions ...openshift-qe-ocp-qe-perfscale-ci-main__aws-4.16-nightly-x86-loaded-upgrade-from-4.15.yaml
View file
Open in desktop
Expand Up @@ -30,8 +30,8 @@ resources:
cpu: 100m
memory: 200Mi
tests:
- as: perfscale-aws-24nodes-loaded-upgrade-415to416
cron: 0 12 * * 1
- as: loaded-upgrade-415to416-24nodes
cron: 0 0 3,10,17,24 * *
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@afcollins Could you help me to understand why these dates was configured? Do you try to run different jobs on different days? What is the difference between the current config and day-of-week config like 0 0 * * 3 and 0 0 * * 4?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My idea with specifying days like this is to allow us to create a weekly/bi-weekly/monthly schedule. The day-of-week format 0 12 * * 1 means "run on Mondays", but I couldn't find any way to say "Run on every-other Monday".

By writing a weekly schedule like this, we can know the total number of jobs running on any given day/week/month.

"Month" i.e. 28 days and chop up from there.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understood, I agree it's easier to understand by having a unified format.

steps:
cluster_profile: aws-perfscale-qe
dependencies:
Expand Down
38 changes: 19 additions & 19 deletions ...t-qe/ocp-qe-perfscale-ci/openshift-qe-ocp-qe-perfscale-ci-main__aws-4.16-nightly-x86.yaml
View file
Open in desktop
Expand Up @@ -23,7 +23,7 @@ resources:
memory: 200Mi
tests:
- as: control-plane-120nodes
cron: 0 5 3,17 * *
cron: 0 0 4,11,18,25 * *
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale
Expand All @@ -42,7 +42,7 @@ tests:
workflow: openshift-qe-installer-aws
timeout: 7h0m0s
- as: control-plane-24nodes
cron: 0 2 * * 3
cron: 0 2 2,9,16,23 * *
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale-qe
Expand All @@ -54,7 +54,7 @@ tests:
- chain: openshift-qe-control-plane
workflow: openshift-qe-installer-aws
- as: control-plane-etcdencrypt-24nodes
cron: 0 0 * * 3
cron: 0 0 2,9,16,23 * *
steps:
cluster_profile: aws-perfscale-qe
env:
Expand All @@ -80,8 +80,8 @@ tests:
- chain: openshift-qe-control-plane
workflow: openshift-qe-installer-aws
timeout: 2h30m0s
- as: conc-builds-3nodes
cron: 0 0 8,22 * *
- always_run: false
as: conc-builds-3nodes
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale-qe
Expand All @@ -108,7 +108,7 @@ tests:
workflow: openshift-qe-installer-aws
timeout: 5h0m0s
- as: node-density-heavy-24nodes
cron: 0 14 * * 4
cron: 0 0 5,12,19,26 * *
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale-qe
Expand All @@ -120,8 +120,8 @@ tests:
- chain: openshift-qe-node-density-heavy
workflow: openshift-qe-installer-aws
timeout: 5h0m0s
- as: payload-node-density-heavy-6nodes
cron: 30 6 * * 2
- always_run: false
as: payload-node-density-heavy-6nodes
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale-qe
Expand All @@ -135,8 +135,8 @@ tests:
- chain: openshift-qe-node-density-heavy
workflow: openshift-qe-installer-aws
timeout: 2h0m0s
- as: payload-node-density-cni-6nodes
cron: 30 6 * * 1
- always_run: false
as: payload-node-density-cni-6nodes
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale-qe
Expand All @@ -150,7 +150,7 @@ tests:
workflow: openshift-qe-installer-aws
timeout: 2h0m0s
- as: data-path-9nodes
cron: 0 9 * * 4
cron: 0 0 1,8,15,22 * *
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale
Expand Down Expand Up @@ -215,8 +215,8 @@ tests:
- chain: openshift-qe-node-density
workflow: openshift-qe-installer-aws-ovn-fips
timeout: 5h0m0s
- as: node-density-24nodes-ovn-fips
cron: 0 9 * * 4
- always_run: false
as: node-density-24nodes-ovn-fips
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale-qe
Expand All @@ -228,8 +228,8 @@ tests:
- chain: openshift-qe-node-density
workflow: openshift-qe-installer-aws-ovn-fips
timeout: 5h0m0s
- as: cilium-data-path-9nodes
cron: 0 1 3 * *
- always_run: false
as: cilium-data-path-9nodes
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale
Expand All @@ -250,8 +250,8 @@ tests:
- chain: openshift-qe-data-path-tests
workflow: openshift-qe-installer-aws-cilium
timeout: 5h0m0s
- as: cilium-control-plane-24nodes
cron: 0 1 3 * *
- always_run: false
as: cilium-control-plane-24nodes
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale
Expand All @@ -269,8 +269,8 @@ tests:
- chain: openshift-qe-control-plane
workflow: openshift-qe-installer-aws-cilium
timeout: 6h0m0s
- as: cilium-control-plane-120nodes
cron: 0 1 3 * *
- always_run: false
as: cilium-control-plane-120nodes
steps:
allow_skip_on_success: true
cluster_profile: aws-perfscale
Expand Down
12 changes: 6 additions & 6 deletions ...qe/ocp-qe-perfscale-ci/openshift-qe-ocp-qe-perfscale-ci-main__azure-4.15-nightly-x86.yaml
View file
Open in desktop
Expand Up @@ -22,8 +22,8 @@ resources:
cpu: 100m
memory: 200Mi
tests:
- always_run: false
as: control-plane-ipsec-8nodes
- as: control-plane-ipsec-8nodes
cron: 0 10 9,23 * *
steps:
allow_skip_on_success: true
cluster_profile: azure-qe
Expand Down Expand Up @@ -52,8 +52,8 @@ tests:
- chain: openshift-qe-control-plane
workflow: openshift-qe-installer-azure-ipi-ovn-ipsec
timeout: 5h0m0s
- always_run: false
as: data-path-9nodes
- as: data-path-9nodes
cron: 0 14 8,22 * *
steps:
cluster_profile: azure-qe
env:
Expand All @@ -72,8 +72,8 @@ tests:
- ref: openshift-qe-perfscale-azu-data-path-nsg
- chain: openshift-qe-data-path-tests
timeout: 7h0m0s
- always_run: false
as: data-path-ipsec-9nodes
- as: data-path-ipsec-9nodes
cron: 0 20 8,22 * *
steps:
cluster_profile: azure-qe
env:
Expand Down
8 changes: 4 additions & 4 deletions ...t-qe/ocp-qe-perfscale-ci/openshift-qe-ocp-qe-perfscale-ci-main__gcp-4.13-nightly-x86.yaml
View file
Open in desktop
Expand Up @@ -33,8 +33,8 @@ tests:
test:
- chain: openshift-qe-control-plane
workflow: openshift-qe-installer-gcp
- always_run: false
as: data-path-9nodes
- as: data-path-9nodes
cron: 0 2 1 * *
steps:
allow_skip_on_success: true
cluster_profile: gcp-qe
Expand Down Expand Up @@ -66,8 +66,8 @@ tests:
test:
- chain: openshift-qe-node-density-cni
workflow: openshift-qe-installer-gcp
- always_run: false
as: node-density-heavy-24nodes
- as: node-density-heavy-24nodes
cron: 0 14 26 * *
steps:
allow_skip_on_success: true
cluster_profile: gcp-qe
Expand Down