letsencrypt / letsencrypt/boulder
Add windows which ARI renewal intervals avoid
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
We have two categories of times that we would like ARI renewals to "avoid" (perhaps by constraining the jitter interval added in #8576)
-
Recurring peaks, especially at UTC midnight
-
Planned maintenance windows, which are time periods when we know we're going to have some reduced capacity
I'm not sure what exactly the right way to configure this is, but even without a firm design I figure we could start with a ticket to brainstorm ideas.
Eg, if the jitter window overlaps with a configured peak time or maintenance window, we could constrain the jitter window to whichever side is bigger. Or perhaps just always prefer to move it to the "sooner" side. Or we might want to move the jitter window instead of constraining it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the jitter work in #8576 and the current ARI renewal scheduling entry point; the issue names no files or tests. Clarify how recurring UTC-midnight peaks and planned maintenance windows should be configured and how overlapping jitter windows should move, then define tests and acceptance criteria for the chosen design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100