incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache Community > Community Wiki Services
Date Sat, 05 Nov 2011 16:54:00 GMT
Space: Apache Community (
Page: Community Wiki Services (

Change Comment:
Corrections to task list and remove obsolete plan.

Edited by Terry Ellison:
h1. Overview

The Community wiki is hosted under the domain []
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

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

h1. Task Breakdown

# -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\]-
# -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.
# -Agree technical options for backup and cache acceleration on- _{-}Target{-}{_}-. 
See --[OOOUSERS:Community Wiki Infrastructure]- -page for details.  \[completed\]-
# -Obtain project endorsement to transfer the application content. \[completed\]-
# -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\]-
# -Integrate agreed backup and cache acceleration options on- _{-}Target{-}{_}-. \[completed\]-
# -Integrate agreed zero-admin management scripts. \[completed\]-
# -Perform load testing an project evaluation of performance on- _{-}Target{-}_ -off-production.
# -Agree branding changes to be applied to wiki and implement on- _{-}Target{-}_ -as a test
off-production. \[Deferred to production \]-
# Develop and maintain list of post-cutover improvements.
# -Obtain go-validation from project including DNS cut-over. \[completed\]-
# _-(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- -[]- -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 domain. The service
on ex\--{_}{-}Current Prod{-}_ -is now read-only. \[completed\]-
# _{-}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\]-

h1. 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

h1. Status page

| 1. | Build of Test VM | completed 02-Aug-2011 | terrye |
| 2 | Initial Build of Target VM | completed 05-Aug-2011 | gmcdonald, rbircher |
| 4 | Obtain project endorsement for test migration | completed 09-Aug-2011 | as per DL |
| 5 | Transfer the _Current Prod_ MediaWiki build and available for testing at [
|] | completed 10-Aug-2011 | terrye |
| 6 | terrye leaves project. | 04-Sept-2011 | |
| 7 | Due to possible lack of project support for MediaWiki in the future, discussion has
now turned to the possible use of Confluence (the already supported Apache wiki) for use as
the Apache OpenOffice (community) wiki | 06-Sept-2011 | |
| 8 | Wiki demise scheduled for Friday, 28-Oct-2011. -See- *{-}Salvage Plan{-}* -below.- |
21-Oct-2011 | _tj_ |
| 9 | {color:green}HURRAH\!{color} The wiki will be re-hosted intact. *Salvage Plan* now obsolete.
Terry offers to support completion of migration.  Current status will be maintained
at []
| 24-Oct-2011 | _tj_ |

h1. Salvage Plan

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

Change your notification preferences:

View raw message