...

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. Wiki Markup-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. Wiki Markup-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\]-unmigrated-wiki-markup
3. -Agree technical options for backup and cache acceleration on- _{-}Target{-}{_}-.    See --[OOOUSERS:Community Wiki Infrastructure]- -page for details. \ [completed\]-
4. Wiki Markup-Obtain project endorsement to transfer the application content. \ [completed\]-
5. Wiki Markup-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. Wiki Markup
   -Integrate agreed backup and cache acceleration options on- _{-}Target{-}{_}-. \[completed\]-

7. Wiki Markup
   -Integrate agreed zero-admin management scripts. \[completed\]-

8. Wiki Markup
   -Perform load testing an project evaluation of performance on- _{-}Target{-}_ -off-production. \[completed\]-

9. .  All wiki content changes with be discarded task 12. [complete]
10. Integrate agreed backup and cache acceleration options on Target. [completed]
11. Integrate agreed zero-admin management scripts. [completed]
12. Perform load testing an project evaluation of performance on Target off-production. [completed]
13. Agree branding changes to be applied to wiki and implement on Target as a test off-production. [Deferred to production ] Wiki Markup-Agree branding changes to be applied to wiki and implement on- _{-}Target{-}_ -as a test off-production. \[Deferred to production \]-
14. Develop and maintain list of post-cutover improvements.unmigrated-wiki-markup
15. -Obtain go-validation from project including DNS cut-over. \ [completed\]-
16. Wiki Markup_-(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\]-unmigrated-wiki-markup
17. _{-}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

...