...
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:
...
- 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.
- node : sakai-dev/test/intg
...
- , not needed now (isaac)
- node : smartsite-beta (provided with Banner data but for users to play with), hardware needed by end of March
...
- node : most of the supporting scripts, apache to run maintenance pages, ucd-gateway, and ucd-help -- production executables
...
- , hardware needed now
- node : redundant of node 3
...
- , hardware needed now
- node : sakai-beta 2.5.x -- one release ahead of our current release
...
- , hardware needed later
- node : sakai contrib -- new tools that we don't have in prod yet but we want to evaluate, using stubing for this now
...
- node : smartsite contrib -- Tools: SCORM and course evaluation, hardware needed now
HW and SW Requirements
- Application Servers
- stubing
- 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
- Indian Indiana Running VMWare
- Cambridge Running Xen
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
Current Machine
Proposed Machine
Comments
sakai
smartsite_prod
hammer, steele
no change
Production
sakai_external
cm_prod
hammer, steele
no change
Production
sakai
smartsite_test
RAC-TEST
Luigi
Smartsite-Test (2.4.x), should be called QA
sakai_external
cm_test
RAC-TEST
Luigi
Smartsite-Test, should be called QA
sakai
sakai_dev_1
bricker:devel
bricker
Development environment, host sakai OOTB for schema upgrade diffs
N/A
Sakai_dev_2
?
bricker
Extra space for internal database only.
N/A
Sakai_dev_3
?
bricker
Extra space for internal database only.
sakai_external
cm_dev
bricker:devel
bricker
Development environment, host sakai OOTB for schema upgrade diffs
sakai_diff
sakai_diff
RAC-TEST
Luigi
used during major upgrades : 2-4-x --> 2-5-x
*sakai_ng
sakai_ng
RAC-TEST
Luigi
QA smartsite-test 2-5-x. Use Mario as the app server.
N/A
sakai_beta
bricker:devel
Luigi
Need new schema since we use bricker:devel
N/A
smartsite_beta
?
Luigi
provided with Banner data but for users to play with
N/A
sakai_contrib
?
Luigi
The evaluation of an OOTB contrib Sakai tool.
N/A
smartsite_contrib
?
Luigi
The evaluation of the Course Evaluation tool, SCORM and other Sakai tools that are adapted to our local environment.
N/A
smartsite_staging
?
Luigi
Stage ongoing production updates (TAGS)
N/A
smartsite_fallback
prod
Not required.
Steel is hot spareUse during database modifications during maintenance upgrades.
- Consider versioning schemas, e.g. cm_test_2_4_x_1, cm_test_2_4_x_2, ...
*Highest priority
Hardware suggestions:
- Use Luigi as a database server for all of the above schemas, internal and external.
- Use Caje for smartsite-test application node.
- Use Saunder for smartsite-test application node.
- Use Littlejohn a third application server in the smartsite-test cluster.
- Use Braddock as the application server for smartsite-beta.
- Use Mario (ng) for the application server. Luigi or the RAC can be the database for this.
-