1. CCA Forum Fall Meeting1 5-6 October 20061 CCA Common Component Architecture cca-forum.org Server Migration David E. Bernholdt ORNL

2. CCA Forum Fall Meeting25-6 October 2006 CCA Common Component Architecture Current Situation 2 servers ~5 years old –Beginning to see unexplained failures Hosted at LBNL Basic support provided by LBNL systems staff Routine operations managed by Allan, Armstrong, Bernholdt & Epperly

3. CCA Forum Fall Meeting35-6 October 2006 CCA Common Component Architecture Replacement System(s) 2 servers on order –1 CPU x 2 cores Intel –4 GB RAM –750 GB system disk –~2 TB RAID-5 –1 hot-spare disk for RAID To be sited in ORNL Fundamental Research Enclave (FRE) Professional sys admin support –Install, maintain OS installation (patches) –RHEL is ORNL-supported Linux distro CCA team will have sudo access

4. CCA Forum Fall Meeting45-6 October 2006 CCA Common Component Architecture Migration of Current Capabilities 1.Mailing lists 2.Web server 3.Wiki 4.CVS repositories 5.Login capability Migrated in staged fashion DNS poses some challenges to staging Use one new server

5. CCA Forum Fall Meeting55-6 October 2006 CCA Common Component Architecture Upgrading Capabilities Configure second server for Xen virtualization –Want to be able to run multiple servers from the same hardware –Easy migration of Xen VMs to alternate hardware (eventually server1 will be repurposed as backup server) –Allow easier experimentation with new capabilities for cca-forum

6. CCA Forum Fall Meeting65-6 October 2006 CCA Common Component Architecture Upgraded Software Plan CVS  Subversion Static web  Plone Wiki  Wiki? or Plone Jabber Experiments –GForge (SourceForge fork)

7. CCA Forum Fall Meeting75-6 October 2006 CCA Common Component Architecture Approximate Timeline cca-forum Migration (server1) October –New hardware delivered & OS installed –Setup Mailman November –Transition Mailman –Transition static WWW –Transition wiki December –Transition CVS, Logins –Setup Plone, build new site January –Setup Jabber Upgrade (server2) –Pending release of RHEL 5 with Xen support January –Setup Xen environment –Migrate all content from server1 February –Plone replaces static WWW in production –Repurpose server1 as Xen- based backup server –Experiment with Xen VM migration