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 5 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. Environment to host the SCORM tool while in development
  6. 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 resources in terms of CPU and RAM, to run more than one virtual machine. To start, the goal is to virtualize the following HW/Environments:

  • stubing to run
    • node 1: sakai-dev
    • node 2: sakai-test
    • node 3: sakai-dev-scrom
  • isaac to run
    • node 1: smartsite-beta
    • node 2: most of the supporting scripts
    • node 3: apache to run maintenance pages, ucd-gateway, and ucd-help
  • No labels