Skip to content

Conversation

@derekhiggins
Copy link
Contributor

These jobs were recently added and use the equinix profile
to provide a baremetal host. This profile is only intended to run
CI jobs for baremetal ipi and we are under a lot of pressure to reduce
it usage(and remove all workloads off equinix). Remove these jobs as
they represent about 12% of our usage.

@openshift-ci openshift-ci bot requested review from QiWang19 and wgahnagl August 2, 2022 17:07
@derekhiggins
Copy link
Contributor Author

derekhiggins commented Aug 23, 2022

pinging OWNERS @giuseppe @haircommander @kolyshkin @mrunalp @nalind @saschagrunert @umohnani8 @vrothberg
Can we remove these (or can you find an alternative? ) it looks to me that these jobs are not ipi related but are using the ipi equinix profile which is way over subscribed.

@saschagrunert
Copy link
Member

saschagrunert commented Aug 23, 2022

@wgahnagl @rphillips, can we remove those jobs?

@haircommander
Copy link
Member

we do have plans of migrating these jobs to gcp, but we have not yet done so. we will need them until we do. I would say in a sprint or two we can remove them. Is that a reasonable timeline @derekhiggins

@derekhiggins
Copy link
Contributor Author

we do have plans of migrating these jobs to gcp, but we have not yet done so. we will need them until we do. I would say in a sprint or two we can remove them. Is that a reasonable timeline @derekhiggins

I'll find out but I'm under a lot of pressure to eliminate almost all of the usage on this account ASAP.

@derekhiggins
Copy link
Contributor Author

we do have plans of migrating these jobs to gcp, but we have not yet done so. we will need them until we do. I would say in a sprint or two we can remove them. Is that a reasonable timeline @derekhiggins

I'll find out but I'm under a lot of pressure to eliminate almost all of the usage on this account ASAP.

Migrating would be great as soon as possible, in the meantime anything that could be done to reduce usage would be appreciated e.g. consolidating jobs ?

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 3, 2022
@openshift-merge-robot
Copy link
Contributor

@derekhiggins: PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Now that the internal ofcir has cihosts, re-organise
the ofcir calls to mke it more clear whats happening.
These are hanging around idle, use them for something.
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 9, 2022

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: derekhiggins
Once this PR has been reviewed and has the lgtm label, please assign mrunalp for approval by writing /assign @mrunalp in a comment. For more information see:The Kubernetes Code Review Process.

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

Details 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

@derekhiggins
Copy link
Contributor Author

No longer needed, jobs migrated to gcp #30733
thanks.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 9, 2022

@derekhiggins: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/deprecate-templates 4c52a7f link true /test deprecate-templates
ci/prow/owners 4c52a7f link true /test owners
ci/prow/step-registry-shellcheck 4c52a7f link true /test step-registry-shellcheck
ci/prow/core-valid 4c52a7f link true /test core-valid
ci/prow/ordered-prow-config 4c52a7f link true /test ordered-prow-config
ci/prow/ci-operator-registry 4c52a7f link true /test ci-operator-registry
ci/prow/ci-operator-config 4c52a7f link true /test ci-operator-config
ci/prow/yamllint 4c52a7f link true /test yamllint
ci/prow/step-registry-metadata 4c52a7f link true /test step-registry-metadata
ci/prow/config 4c52a7f link true /test config
ci/prow/build-clusters 4c52a7f link true /test build-clusters
ci/prow/generated-config 4c52a7f link true /test generated-config
ci/prow/check-gh-automation 4c52a7f link true /test check-gh-automation
ci/prow/ci-operator-config-metadata 4c52a7f link true /test ci-operator-config-metadata
ci/prow/prow-config-filenames 4c52a7f link true /test prow-config-filenames
ci/prow/correctly-sharded-config 4c52a7f link true /test correctly-sharded-config

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants