Overview

The OpenOffice.org Community wiki is hosted under the domain http://wiki.services.openoffice.org/ comprise some 10,000 content pages and 11,000 uploaded files (“Current Prod”).

The "legacy wiki" was based on a standard MediaWiki package (version 1.15.1) with some 40 installed extensions.  The wiki ran on Solaris Coolstack on a 4 core Solaris zone within a dedicated server in the Oracle Hamburg machine room (at an average 75% us+sy load under normal working periods). This was decommissioned during the weekend commencing 30th Oct 2011, with the content having an update freeze starting 24th Oct and the content transferred to ASF infrastructure on in the period 24-25th Oct.

The "new wiki" was brought up on an Ubuntu 10.04 LTS VM running on the Apache ESXi production environment, running a MediaWiki package (version 1.15.5) with 33 installed extensions (any redundant extension were removed as part of migration.) An Apache Traffic Server reverse-proxy is cohosted on the VM and front-ends the MediaWiki application.  The MediaWiki application uses both a file system and D/B (currently MySQL) to maintain application data. These are currently some 2.7GiB and 2.6 GiB in raw size respectively.  The core MediaWiki software has no special-to-OOo modifications, other than the standard use of extensions.

There were various technical issues to be addressed to enable the migration to to Apache Infrastructure so this subsidiary page, Community Wiki Infrastructure, provides a baseline for this migration and details the technical options to address said issues.

Task Breakdown

1. Build Test VM using Ubuntu VM and pull a copy of Current Prod to validate. This work will be done within the current OOo (Oracle) working practices to de-risk the migration ahead of task 3. [completed]
2. Set up initial build of Target VM under VMware ESXi. This is a bare Ubuntu 10.04 LTS VM configured as a “standard server” and including the Apache-standard security extension. [completed]
3. Agree technical options for backup and cache acceleration on Target-.  See -Community Wiki Infrastructure page for details. [completed]
4. Obtain project endorsement to transfer the application content. [completed]
5. Transfer the Current Prod MediaWiki build, with a snapshot of the wiki content from Current Prod as at 9th Aug 2011 to form the basis for full scale testing pre-prod. This will content be stale and not synced to Current Prod.  All wiki content changes with be discarded task 12. [complete]
6. Integrate agreed backup and cache acceleration options on Target. [completed]
7. Integrate agreed zero-admin management scripts. [completed]
8. Perform load testing an project evaluation of performance on Target off-production. [completed]
9. Agree branding changes to be applied to wiki and implement on Target as a test off-production. [Deferred to production ]
10. Develop and maintain list of post-cutover improvements.
11. Obtain go-validation from project including DNS cut-over. [completed]
12. (48 hrs before DNS cut-over) Bring _Current Prod offline for ~3 hrs whilst the current prod D/B and file system updates post 28th Jul 2011 are backed up, transferred to Apache and loaded onto Target. Reapply branding changes. Oracle to enable DNS redirection for all http://wiki.services.openoffice.org/ to Target’s external public IP address. Bring service back on-line: Target is now the Live Production environment, albeit though DNS redirection from the still Oracle-managed openoffice.org domain. The service on ex-Current Prod is now read-only. [completed]
13. DNS cut-over. This takes up to 24hrs to cascade globally. User access to Live Production continues whether direct or redirected via the Oracle IP addr. The now ex_Current Prod -can be decommissioned by Oracle as necessary. [completed]

Issues and Other Requirements

• All existing account-based access for legacy wiki must be disabled on this pre-prod instance. Only project-approved accounts can be enabled for update access.

• Assuming production at some point, how will accounts be initiated and managed?

• Any branding changes can be prepared and developed on the pre-prod instance. The authors can use standard MediaWiki export/import functionality to preserve such content when this D/B is overwritten at live cut-over

Status page

Salvage Plan

(This plan is now obsolete and this section is deleted.  See page history for historical content.)