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

core-services/prow/02_config/_boskos: Shard AWS, Azure, and GCP by region #12589

Merged
merged 2 commits into from
Oct 15, 2020

Conversation

wking
Copy link
Member

@wking wking commented Oct 9, 2020

With some guessing about what we support. No consumers yet, but consumer rehearsals run against the production Boskos server, so we need to land these before we can consume them.

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 9, 2020
The names are used for custom resources, so we need unique names for
each entry [1].  Consuming jobs will have to split on the --, which is
hopefully unique enough, to get the raw name (if they plan to use it
to select a region or similar).  I'm not using '-', because:

a. I wanted to avoid enumerating single-count entries.
b. I wanted consumers to not have to care about whether they were
   drawing from a single-count or multi-count entry.

Using a separator that is not part of the raw names means that
consumers can always split on that separator without having to worry
about whether they were drawing from a single-count or a multi-count
name.

[1]: openshift#12589 (comment)
…gion

With some guessing about what we support.  No consumers yet, but
consumer rehearsals run against the production Boskos server [1], so
we need to land these before we can consume them.

[1]: openshift#12584 (comment)
wking added a commit to wking/ci-tools that referenced this pull request Oct 14, 2020
To allow for the suffixed lease names from [1] without exposing the
suffixes to consuming steps.

[1]: openshift/release#12589
Copy link
Contributor

@alvaroaleman alvaroaleman left a comment

Choose a reason for hiding this comment

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

/hold
until the corresponding ci-tools pr is merged and rolled out

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 14, 2020
@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 14, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alvaroaleman, wking

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

@wking
Copy link
Member Author

wking commented Oct 14, 2020

ci-tools postsubmit:

2020/10/14 21:34:40 Resolved source https://github.com/openshift/ci-tools to master@c4a0d926
...
2020/10/14 21:51:09 Promoting tags to ci/${component}:latest: ... ci-operator, ...

Looks like the local consumers are all image: ci-operator:latest, so that should be enough to pull the hold, right?

@wking
Copy link
Member Author

wking commented Oct 15, 2020

4h since my last comment. Surely it has made it over by now, and even if it hasn't, nobody is consuming the -- entries yet.

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 15, 2020
@openshift-merge-robot openshift-merge-robot merged commit 9a08d5f into openshift:master Oct 15, 2020
@openshift-ci-robot
Copy link
Contributor

@wking: Updated the following 2 configmaps:

  • resources configmap in namespace ci at cluster app.ci using the following files:
    • key boskos.yaml using file core-services/prow/02_config/_boskos.yaml
  • resources configmap in namespace ci at cluster api.ci using the following files:
    • key boskos.yaml using file core-services/prow/02_config/_boskos.yaml

In response to this:

With some guessing about what we support. No consumers yet, but consumer rehearsals run against the production Boskos server, so we need to land these before we can consume them.

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.

wking added a commit to wking/openshift-release that referenced this pull request Oct 15, 2020
…CP by region"

This reverts commit 0cb81d0, openshift#12589.

Telemetry isn't showing any free leases on these platforms, which is
freaking me out a bit.  It's possible that the dashboards just don't
handle static names gracefully, but I'm going to float a revert in
case something breaks and we want to buy some time for a post-mortem.
@wking wking deleted the per-region-leases branch October 21, 2020 20:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

Successfully merging this pull request may close these issues.

4 participants