feat(blog) add a new post about the Update Center (5th brownout) #7628
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Damien Duportal <[email protected]>
timja
approved these changes
Oct 24, 2024
gounthar
approved these changes
Oct 24, 2024
|
|
||
| Note: this is a follow up of link:/blog/2024/09/25/update-center-brownouts-4/[the 26 and 27 September 24 hours brownout]. | ||
|
|
||
| The service https://updates.jenkins.io will switch its implementation to a new system during 1 day: |
There was a problem hiding this comment.
Suggested change
| The service https://updates.jenkins.io will switch its implementation to a new system during 1 day: | |
| The service link:https://updates.jenkins.io will switch its implementation to a new system during 1 day: |
|
|
||
| The service https://updates.jenkins.io will switch its implementation to a new system during 1 day: | ||
|
|
||
| - From Thursday 24 October 2024 from 10:00am UTC until Friday 25 October 2024 10:00am UTC |
There was a problem hiding this comment.
Suggested change
| - From Thursday 24 October 2024 from 10:00am UTC until Friday 25 October 2024 10:00am UTC | |
| - From Thursday 24 October 2024 from 10:00 am UTC until Friday 25 October 2024 10:00 am UTC |
|
|
||
| ⚠️ Please, check that your organization respects the advertised DNS TTL or you might be stuck in the brownout longer than expected. | ||
|
|
||
| Under the hood, any HTTP request made to this service will be redirected to a mirror close to user locations during these brownouts. |
There was a problem hiding this comment.
Suggested change
| Under the hood, any HTTP request made to this service will be redirected to a mirror close to user locations during these brownouts. | |
| Under the hood, any HTTP request to this service will be redirected to a mirror close to the user's locations during these brownouts. |
|
|
||
| == What is the "Update Center"? | ||
|
|
||
| Jenkins link:https://updates.jenkins.io[Update Center] is a web server at the core of the Jenkins public infrastructure which distributes the plugins, tool installers, and versions index to all Jenkins servers across the world. |
There was a problem hiding this comment.
Suggested change
| Jenkins link:https://updates.jenkins.io[Update Center] is a web server at the core of the Jenkins public infrastructure which distributes the plugins, tool installers, and versions index to all Jenkins servers across the world. | |
| Jenkins link:https://updates.jenkins.io[Update Center] is a web server at the core of the Jenkins public infrastructure that distributes the plugins, tool installers, and versions index to all Jenkins servers worldwide. |
|
|
||
| From the installation wizard to regular plugin updates, if you run Jenkins, then you use this service under the hood. | ||
|
|
||
| Today, it serves around 50 Tb of data (outbound bandwidth) each month from a single virtual machine on AWS, which costs around $6,000 per month. |
There was a problem hiding this comment.
Suggested change
| Today, it serves around 50 Tb of data (outbound bandwidth) each month from a single virtual machine on AWS, which costs around $6,000 per month. | |
| Today, it serves around 50 TB of data (outbound bandwidth) each month from a single virtual machine on AWS, which costs around $6,000 per month. |
Comment on lines
+47
to
+50
| However the previous (fourth) brownout raised 2 issues: | ||
| - We've seen (and were reported) HTTP/404 errors due to broken links in some HTML pages (not used a lot) and missing endpoints used for healthchecks in link:https://github.com/jenkins-infra/helpdesk/issues/4311[] | ||
| - We've also seen HTTP/404 errors after 8-9 hours or production usage due to network file share (SMB/CIFS) issues with Apache. The service is self-healing but we are trying to fine tune this: if it fails, then we'll have to update the Apache architecture to stop using a network file share. See https://github.com/jenkins-infra/helpdesk/issues/4312 for details. | ||
|
|
There was a problem hiding this comment.
Suggested change
| However the previous (fourth) brownout raised 2 issues: | |
| - We've seen (and were reported) HTTP/404 errors due to broken links in some HTML pages (not used a lot) and missing endpoints used for healthchecks in link:https://github.com/jenkins-infra/helpdesk/issues/4311[] | |
| - We've also seen HTTP/404 errors after 8-9 hours or production usage due to network file share (SMB/CIFS) issues with Apache. The service is self-healing but we are trying to fine tune this: if it fails, then we'll have to update the Apache architecture to stop using a network file share. See https://github.com/jenkins-infra/helpdesk/issues/4312 for details. | |
| However, the previous (fourth) brownout raised 2 issues: | |
| - We've seen (and were reported) HTTP/404 errors due to broken links in some HTML pages (not used a lot) and missing endpoints used for health checks in link:https://github.com/jenkins-infra/helpdesk/issues/4311[] | |
| - We've also seen HTTP/404 errors after 8-9 hours of production usage due to network file share (SMB/CIFS) issues with Apache. The service is self-healing but we are trying to fine-tune this: if it fails, then we'll have to update the Apache architecture to stop using a network file share. See https://github.com/jenkins-infra/helpdesk/issues/4312 for details. | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to jenkins-infra/helpdesk#2649, jenkins-infra/helpdesk#4312 and jenkins-infra/helpdesk#4311
This PRs publishes a new blog post to announce the 5th brownout.
I'm short in delays (sorry, I got team member unavailable so late due to overwhelmed): I would want to publish this as soon as posible. As such, do not hesitate to commit or fix the post if you see any mistake or typo (you can push on my PR here: I'll let it in auto merge) but I'll need a quick review + approval at least.