CT2 Development Systems and HR transition 2011

From UG

(Difference between revisions)
Jump to: navigation, search
Line 3: Line 3:
== Intro ==
== Intro ==
-
Timeline:
+
== Timeline ==
* jan 5 - 19 (or jan 31) // Paul is full time on-site
* jan 5 - 19 (or jan 31) // Paul is full time on-site
** knowledge transfer of core to Alex
** knowledge transfer of core to Alex
** servers consolidation ??
** servers consolidation ??
-
** transfer to Rackspace (CT1 server???) or another provider
+
** frwd backups to CT1 instead of in house backup server
 +
** transfer to Rackspace or another provider ( 5-6 turnaround for Rackspace to setup; DNS updates)
 +
*** (CT1 server???) CT1 runs MySQL 4, jag websites runs on Apache
 +
*** combine SVN, Mantis, Wiki, CT2 Demo&staging
 +
**** problem: during re-deploy to demo all apps will be
 +
 
* jan 19 (or jan 31) - date new CT2 Admin is found // Paul is contractor off site
* jan 19 (or jan 31) - date new CT2 Admin is found // Paul is contractor off site
-
*
+
* date new CT2 Admin is found - date new CT2 Admin is self sufficient // Paul is available to answer questions
 +
 
 +
== Checklist ==

Revision as of 18:46, 6 January 2011


Intro

Timeline

  • jan 5 - 19 (or jan 31) // Paul is full time on-site
    • knowledge transfer of core to Alex
    • servers consolidation ??
    • frwd backups to CT1 instead of in house backup server
    • transfer to Rackspace or another provider ( 5-6 turnaround for Rackspace to setup; DNS updates)
      • (CT1 server???) CT1 runs MySQL 4, jag websites runs on Apache
      • combine SVN, Mantis, Wiki, CT2 Demo&staging
        • problem: during re-deploy to demo all apps will be
  • jan 19 (or jan 31) - date new CT2 Admin is found // Paul is contractor off site
  • date new CT2 Admin is found - date new CT2 Admin is self sufficient // Paul is available to answer questions

Checklist

Personal tools