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

[feed-moderation] Confluence Wiki service to be restarted #41

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[feed-moderation] Confluence Wiki service to be restarted #41

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions src/en/news/blog/2015/confluence-wiki-service-to-be-restarted/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
title: "Confluence Wiki service to be restarted"
date: 2015-06-10 08:32:13 UTC
modified_date: 2015-06-10 08:35:24 UTC
author: "Apache Infra Team"
url: "https://blogs.apache.org/infra/entry/confluence_wiki_service_to_be"
---
Hi All,<br><br>There will be a planned reboot of Confluence on Friday 12th June at 18:00 UTC+1<br><br>This is a blog post notice as recommended in our Core Services planned downtime SLA.<br><br>The Confluence wiki service configuration is stored in our Puppet configuration.<br><br>We have made some modifications to the Puppet Manifest affecting the Module that<br>Confluence uses (cwiki_asf). Some code is being moved out from the module and <br>into a host specific YAML file. This will make it easier for future hosts to re-use the <br>module (such as an upgrade host currently awaiting these changes.)<br>A twitter notification will be posted 1 hour before.<br>A planned maintenance notice will be posted on status.apache.org.<br><br>If necessary we will make use this outage window to apply any OS updates and reboot <br>the host VM.<br><br>Actual downtime should be no more than 1 hour all being well.<br><br>An email about this will be sent to infrastructure@ after the service has resumed from the planned downtime.