Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 39 Next »

Goal

We have 10 application servers that are used in our Dev, Test, and Production environments. We have continuous need for additional HW to either bring up additional environments, as described bellow, or to run specific support applications and or scripts.
Currently we need applications servers for the following:

  1. SmartSite Beta environment where we stage new tools and or new Sakai versions
  2. Server where we can run our support scripts such as
    • DB Helthcheck, which detects full table scans
    • Number of sites created in form of a spreadsheet
  3. Apache to host ucd-gateway and ucd-help
  4. Apache to host maintenance and outage pages
  5. Apache to host maven1/maven2 repositories
  6. Environment to host the SCORM tool while in development
  7. Having four separate environments, DEV, TEST, INTG, PROD. We always trade off one of these environments

Given the budget constraints, we are not really in a position to purchase new HW and thus need to find other solutions to accommodate our HW needs. One of the potential solutions is to virtualize one or more of our environments to optimize the use of our available HW.

All of our applications nodes have enough CPU and RAM resources in order to run more than one virtual machine. The initial goal is to virtualize the following HW/Environments:

  1. node: Sakai 2.5.x for QA and practice roll out environment. Hardware needed now. We can use smartsite_ng1 and the corresponding RAC instance for smartsite_ng for this environment now. After the roll out, we can return it to the Beta environment usage.
  2. node : sakai-dev/test/intg, not needed now (isaac)
  3. node : smartsite-beta (provided with Banner data but for users to play with), hardware needed by end of March
  4. node : most of the supporting scripts, apache to run maintenance pages, ucd-gateway, and ucd-help -- production executables, hardware needed now
  5. node : redundant of node 3, hardware needed now
  6. node : sakai-beta 2.5.x -- one release ahead of our current release, hardware needed later
  7. node : sakai contrib -- new tools that we don't have in prod yet but we want to evaluate, using stubing for this now
  8. node : smartsite contrib -- Tools: SCORM and course evaluation, hardware needed now

HW and SW Requirements

  • Application Servers
    1. stubing
    2. isaac
  • Operation System
    • RedHat v5.1
  • Virtualization SW
    • Xen : This is open source
    • VMware
  • File System
    • Stored locally
    • SAN and distributed file system such as NetApp or VMFS

Other Information

  • Indiana Running VMWare
  • Cambridge Running Xen

h3 Database Requirements

  • NOTES:
    • Consider versioning schemas, e.g. cm_test_2_4_x_1, cm_test_2_4_x_2, ...

      Schema Names

      New Schema Names

      Machine

      Comments

      sakai/sakai_external

      smartsite_prod/cm_prod

      hammer, steele

      sakai/sakai_external

      smartsite_test/cm_test

      rac-test

      sakai/sakai_external

      sakai_test/cm_test

      bricker:test

      (error) sakai/sakai_external

      sakai_dev/cm_dev

      bricker:devel

      sakai-diff

      RAC-TEST

      (used during major upgrades : 2-4-x --> 2-5-x)

      sakai_ng

      (rac-test)

      QA smartsite-test 2-5-x

      sakai

      (sakai_beta)

      bricker:devel

      smartsite_beta

      sakai_contrib

      (evaluation, ...)

      smartsite_contrib

      (SCORM, ...)
  • No labels