Versions Compared

Old Version 8

changes.mady.by.user Terry Ellison

Saved on

compared with

New Version 9

changes.mady.by.user Terry Ellison

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Add tracking of technical issues

...

  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\]
  3. Wiki Markup
    Obtain project endorsement  to transfer the application content. \[completed\]
  4. Wiki Markup
    Transfer the _Current Prod_ build, with a snapshot of the form 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 forum content changes with be discarded at task 10. \[complete\]
  5. Integrate agreed backup options on Target.
  6. Integrate agreed zero-admin management scripts
  7. Agree branding changes to be applied to forums and implement on Target as a test off-production.
  8. Develop and maintain list of post-cutover improvements and fixed
  9. Obtain go-validation from project including DNS cut-over.
  10. (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://wikiuser.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 offline.
  11. 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.

Technical Issues

...

  • ACM Cache. ACM caching is required, given the usage volumes on the forum. Because of Solaris/Coolstack issues, we previously could not use any of the standard memory variant ACM modules, so TerryE developed a mysqli-based ACM module. With moving to a standard LAMP stack, this is no longer required. acm_acp will be adopted, retiring *acm_mysqli.
  • Version 3.0.9 upgrade. This new version of phpBB was released last month. The forums are currently running at the previous version 3.0.8. Upgrade to version 3.0.9 is not viewed as a high priority issue, and will only be scheduled once the wiki performance issues have been effectively addressed.

External Requirements